Hello !! Could someone kindly suggest me where to find the *instrumentation tools* available on Gnu/Linux, to avoid Jitter ( as suggested at 26:10 ) ? Are GDB and Valgrind the right ones ? I'm new to C++ programming :) tnx ! =)
This is a great top-level overview. As someone starting out, I feel like I've been massively pointed in the right direction. Fun guy, and good quotes. The Mr T one was standout.
The audio thread is probably standard C within C++. You wouldn't want the OOP overhead to get in the way. I use only C. C++ is probably great for graphics programmers but it seems like a nasty mess of a language to me.
Hard stuff - even a bit discouraging because you have to set yourself so much limits (e.g. speed) - to realise a idea of signal processing. But this guy is an expert in what he does
Unfortunately, the algorithm presented at 44:18 is vulnerable to tearing and has undefined behaviour: If *currentCoefficients is switched quickly enough, it's possible for a and/or b to be read and written to at the same time from different threads.
I'm at 17:00 through the talk. And although what this man says makes sense, I don't feel very educated. I hope the pace picks up a bit and we get example code.
From a guy with 10 years' worth of embedded real time s/w experience: This guy really knows, what he's talking about!
Because you are this guy =)
Am I right?
35:16 shoutout to all of the developers that are 4years into an audio project without applying these tips, that line had to hurt
this is a great package of teachings, and the quotes were placed very wisely. I Hope become an audio programer one day
I enjoyed th video very much! Thanks a lot!
Hello !! Could someone kindly suggest me where to find the *instrumentation tools* available on Gnu/Linux, to avoid Jitter ( as suggested at 26:10 ) ?
Are GDB and Valgrind the right ones ?
I'm new to C++ programming :)
tnx ! =)
This is a great top-level overview. As someone starting out, I feel like I've been massively pointed in the right direction. Fun guy, and good quotes. The Mr T one was standout.
His books are great. I always recommend them to beginners. The styles is great, the examples, the pace etc.
as a newbie myself, i learned alot! Thank you for sharing this!
Alot of cans
The rules are clear here, i was never taught them in school, but i , like others, have had the rules passed down from mentors
"Mutexes... NOOOO!!" ... instant classic
Loved his presentation
h o n k
I have been a Software Engineer for 20 years. This guy has filled an hour with mostly waffle - don't waste your time!
I do want to ask, why is C not used to do audio?? Why only C++???? Great talk....
The audio thread is probably standard C within C++. You wouldn't want the OOP overhead to get in the way. I use only C. C++ is probably great for graphics programmers but it seems like a nasty mess of a language to me.
I though c++'s whole thing are the zero cost abstractions?
Hard stuff - even a bit discouraging because you have to set yourself so much limits (e.g. speed) - to realise a idea of signal processing.
But this guy is an expert in what he does
i hope i understand what all this means soon
How's it going?
The only thing I hate about this video is the marvellous job done by the camera guy!!!
Unfortunately, the algorithm presented at 44:18 is vulnerable to tearing and has undefined behaviour: If *currentCoefficients is switched quickly enough, it's possible for a and/or b to be read and written to at the same time from different threads.
18:09
He didn't mention, why denormal floats are bad.
11DaT11 operations on denormals are way slower
Workload goes up
I'm at 17:00 through the talk. And although what this man says makes sense, I don't feel very educated. I hope the pace picks up a bit and we get example code.
I thought that was a pickle in his hand.
It would be very useful to add subtitles for Hispanics who do not have English as fluent
that won't help the chinese
this guy is kind of scary
Zoom out the fucking camera
Lively presentation, but too much moving around, too much waffle, too many pointless quotations.
Omg get on with it and for God sake be still you're making me nervous! Geez!
It's like 50 minutes of stating the obvious.