Видео

Nice audio info 😊

one more time

Great! I am just getting into vcpkg

Very interessting approach.

☕Did I help you with this video? Consider buying me a coffee at www.buymeacoffee.com/janwilczek Thanks!

Great video, will surely be helpful in a future project. The videos you're doing here and on the JUCE channel are great.

Work for Windows app using kotlin???

Your explanation is good but please get a lapel mic.

A very good, intuitive insight you're explaining very kindly!

Nice i like to have a DAW one day 😊😊

Cześć Jan! Masz może na kanale odcinek jak zacząć działać w audio programmingu? Jakieś pierwsze projekty, które warto robić na początku? Albo, polecasz jakieś książki, które są wartę uwagi? Bardzo by mi pomogły odpowiedzi na te.pytania :D

great list. I had the Computer Music Tutorial, Design Patterns, Clean code, but not several of the others. Treasure Trove of resources right here.

dawe rowland

Nice talk! Thanks! 👌

Hi

Speaking from experience - doing stuff on the audio thread is a dantean experience in rust. It's definitely not for beginners. So you know like in C/C++ you can prealloc an arena or maybe an object pool and just use it? In rust custom allocators are unstable and prepare yourself for wrapping every single one of your objects in MaybeUninit. Shared mutable state is kinda unavoidable in audio - hence you will end up using RefCell or UnsafeCell more than a healthy amount. Slice accesses are bound checked unless the compiler can prove that it's impossible to get out of bounds, So you either go with processing every sample in a foreach loop using maps and zips or have to agree to making a wrapper type around a raw pointer that overloads the [] operator which is a footgun waiting to fire (rust is way more strict about aliasing than c++). And the solution is to actually place asserts that will be present in your release build as well, which check if your input and output buffers have the same length - how would one guess that?

nim has been around since 2008, it's been a stable esolang for quite some time

Thanks for valuable course

Thank you, sir. I was really wondering but I am now set and feel secure in choosing C++

😍😍😍😍

Many thanks for the video! When the next video is planned?

Yup

Hi

Regarding what you say at the 42:00 minute mark, I don't seem to actually get that much aliasing for the square and saw on my physical devices. Maybe I need to listen more carefully :)) Anyway, great tutorial series! It was really rewarding to me and I learned a lot of C++, Kotlin and design patterns in general. It's really helpful to someone who's still in college and feeling like college isn't helping enough on the software engineering side.

C++ is tying to do all and exceeds in none. I agree and there is even more like 'never use new and delete in modern C++' , obfuscated templates that literally do nothing but mask your code, RVO and copy elision are not guaranteed by many, you can still mix C and C++ code in C++ projects. C has a standard and is easy to use without obfuscation. Also I'd not advice boost on modern C++, it's a mess, boost must go, there are Juce, Qt and Poco nowadays for big projects. I am not familiar with Rust or Carbon but C++ is becoming the new COBOL. I am professionally programming in C++ and it's just not good anymore.

At 47:44, the fact that you said "please don't do anything right now" in such a professorial way was really cool. Leaving in the "mistakes" done when coding (rather than editing them out) really makes this a more genuine experience. Thank you for that!

Thanks for your detailed analysis for C++ ( mostly bad side) . When I see the Juce sponsorship in the end of the video , it comes to my mind that maybe you can give detailed information about Juce's license management in another video.

So you not very experienced in C++ and got lead developer? I think somebody put you in a bad position.

Third party warning are easily surpressed if the includes are system includes. CMake has support for that.

my beef with C++ is less with the language itself than the culture surrounding it. too many devs I've worked with treat C++ as ersatz Java, over-relying on virtual functions and dynamic polymorphism as the first and only solution to any given problem. next is the lack of a good dependency management and build system, as you say. I want the build system to be an afterthought, like it is in rust. it downloads, installs, and links all dependencies, no problem. I don't have to munge my way around header files to get templated code to compile, it just works, out of the box, on every platform it is supported on. on that point, I would like true pattern matching to be built in to C++. no, std::variant doesn't cut it, not nearly. it's a pale imitation of what pattern matching is in languages like prolog, ocaml, haskell, i.e. declarative and recursive syntactical destructuring of values. variant just matches on the outermost type, missing most of the expressive power of proper pattern matching.

To me, the ugliest ugliness in the language is macros. It's an extraordinary mess. There's a reason why Stroustrup doesn't recommend it. While it's great flexibility, it can also be a big problem. It also becomes very difficult when you want to use libraries that were created with different build systems. The "Import Export" in modules is also very funny.

What really can a compiler to do offer defaults and the most fully-featured standard library possible? Even if they recommend defaults and provide a standard library that doesn't mean 3rd party options aren't better and should be used instead. In fact people often complain about the standard library in C++ and recommend other alternatives. Not saying your points aren't problems but I don't think C++ can help you here more than other language. Btw, I'm not a C++ programmer by any means and these problems you mention seem to exist with all compilers, just some more than others.

Sometimes???? Cpp always sucks. We just put up with it because of the control over the code and speed of the final program. Compile time really kills it.

I've used pascal for years which has declaration/definition split in modules where you need to modify the declaration in 2 locations. It's annoying but I like it creates ledgers for the type at least. In other languages I've used like Swift/C# there are no modules or forward declarations and it's all just dumped into files and the compiler figures out how to link it together. The downsides to this are it's slower to compiler since the compiler needs to resolve types and it's kind of messy to have all the code and types mixed together, although practically this hasn't been a problem it's just not as orderly I would say. Hard to say which is best for me personally.

what a hidden gem

I know about nothing about C++ but here on RUclips i saw at least few very good presentations(most from some C++ conferences) about co-routines, which even i understood (with code examples)

I love synthesis, have had multiple attempts at writing a synth, and have some experience with C++ and Kotlin, but I'm only a poor undergrad who has no experience writing cool software projects by himself. Needless to say, I had to pinch myself when I saw that this video series existed. Thank you for making this content!

Slow compile time, difficult to set up modern environment, have to learn another language for cross-compilation (CMake), too many ways to do the same thing, etc.

Also, I don't understand why dependency management should be part of the language. Strictly speaking it is out of scope.

I really don't understand the anger with header/source split. I get it only when the objection revolves around using the preprocessor. But the split is beneficial in 2 areas that I find helpful in practice: 1. The header gives you a helpful summary/overview of the class. It helps with readability because you are onboarded quickly when you understand the shape of the class at once glance. It also helps with maintainability because it outlines the shape of the class and lets you better think about refactoring it when looking only at the outline. 2. Sometimes definitions can be lengthy. You might need to split the definition of methods into two source files to help with maintainability. Also this might be a code smell if you have many methods are too long. PS: Modules are heralded as the bane of headers but in actuality modules also support the split between declaration and definition. However, they get rid of the preprocessor which is the actual bad thing about headers.

i have a prototype of my vst, its already being used in the chicano hiphop scene. CAN I GET IT BUILT ON MY OWN ENGINE.

Sine 2:35 Triangle 3:18 Square 4:36 Sawtooth 5:31 Pulse 7:19

Linting problem is a compile languages problem. Can't be fixed. If Rust lives long enough it too is gonna have a pile of style guides from all the lovely ends of the universe. It seems your mic picks up some background or side crackling events. Which is very confusing at moments.

this video about c++ sucks and rust do better 😂

thanks

❤

Thank you for this. I am however very lost where to go after this. I know how to make simple changes to PluginProcessor.cpp, and I can try out my plug in if I load it to an external test host, or load it in Ableton, but I cannot manage to run and debug it in vscode. Is this just a matter of tweaking my launch.json/task.json and settings.json files to get them to work?