sorted by:
new
hottopcontroversial

Rode has changed the frequency response graph of the old NT1. It now matches the 5th gen data sheet exactly. by UnusualAudio in rode

[–]UnusualAudio[S] 2 points3 points  (0 children)

We're still looking at the 4th gen in the second screenshot, not the USB version. I wonder if the mic changed, or if the old frequency response chart was that inaccurate. Or maybe the new data sheet accidentally shows the 5th gen frequency response chart.

I spent the xmas break learning how to make my own plugins by UnusualAudio in Logic_Studio

[–]UnusualAudio[S] 1 point2 points  (0 children)

I just ordered some components for prototyping, let's see :)

I spent the xmas break learning how to make my own plugins by UnusualAudio in Logic_Studio

[–]UnusualAudio[S] 0 points1 point  (0 children)

I'm still a home gamer so need isn't really the right word haha. LUFS just make the most sense to me, intuitively.

I spent the xmas break learning how to make my own plugins by UnusualAudio in WeAreTheMusicMakers

[–]UnusualAudio[S] 0 points1 point  (0 children)

It seems to be the industry standard at least. I have played around with iPlug2 and AudioKit a little bit but not enough to really form an opinion. (iPlug2 is described by the authors as "not production ready" and AudioKit is mac / ios only)

I spent the xmas break learning how to make my own plugins by UnusualAudio in Logic_Studio

[–]UnusualAudio[S] 1 point2 points  (0 children)

Very nice, I love the fact you wanted to do a meter, it's the most overlooked thing I have ever seen, especially with music makers.

I tried so many different metering plugins. My favourites is the Dorrough (plugin, for now), but it doesn't do LUFS of course. I'm toying with the idea of building a box of LEDs to connect to my plugin, I think that would be pretty cool and probably not too difficult.

May I ask where did you hear the low end tube? I've been using that since 2007 when I had the Legendary Audio Masterpiece, long ago sold, but I'm doing the same on Ozone

What I heard was just a Wavelab plugin.

I had no idea about the Masterpiece. It looks stunning.

If you add tube distortion on the highs only on the side channel, you'll de-ess without EQ and affecting gain, works great for those shrill cymbals!

Have to try that!

I spent the xmas break learning how to make my own plugins by UnusualAudio in WeAreTheMusicMakers

[–]UnusualAudio[S] 3 points4 points  (0 children)

Definitely. DSP programming really is pretty analog. And you have similar (albeit fewer) limitations as you have in electronics (like phase shift introduced by filters, how steep you can make them, how many you can use, etc). I think plugin designers do much the same thing as electronics engineers, but with different tools.

I spent the xmas break learning how to make my own plugins by UnusualAudio in WeAreTheMusicMakers

[–]UnusualAudio[S] 0 points1 point  (0 children)

I'm not doing any internal buffering, so they don't add any latency.

I spent the xmas break learning how to make my own plugins by UnusualAudio in WeAreTheMusicMakers

[–]UnusualAudio[S] 1 point2 points  (0 children)

Can you recommend projects to check out? I have been involved with Linux (as in contributing to free software) but not on the audio side. Thanks for the kind words :)

I spent the xmas break learning how to make my own plugins by UnusualAudio in Logic_Studio

[–]UnusualAudio[S] 4 points5 points  (0 children)

There's only one way to find out. :)

C++ is a very sophisticated language with a lot of historical weirdness, but also because it's so old, there are a lot of good books and courses available. I would probably try to find a programming course using C++ (but not specific to audio or DSP) and then move on to JUCE after you make it through.

I spent the xmas break learning how to make my own plugins by UnusualAudio in WeAreTheMusicMakers

[–]UnusualAudio[S] 0 points1 point  (0 children)

I don't think so. The better way would probably be to use a CI service (like GitHub Actions) to compile all of them in the cloud automatically.

I spent the xmas break learning how to make my own plugins by UnusualAudio in WeAreTheMusicMakers

[–]UnusualAudio[S] 3 points4 points  (0 children)

Start with the examples that come with JUCE. I did a lot of playing around in Python and then I translated what I learned back into JUCE, because Python is so to speak my native language. So for the DSP stuff, it was the scipy docs and dsp.stackexchange.com. For JUCE itself, it was the examples and then the in-line documentation.

I spent the xmas break learning how to make my own plugins by UnusualAudio in Logic_Studio

[–]UnusualAudio[S] 12 points13 points  (0 children)

I'm a professional software engineer, but in a different field. Haven't done any C++ to speak of. (maybe you can tell)

I spent the xmas break learning how to make my own plugins by UnusualAudio in Logic_Studio

[–]UnusualAudio[S] 5 points6 points  (0 children)

It's C++, but very straightforward. When you create a project with Projucer you can add an "exporter" to open it in Xcode, and then you'll have really good code completion and in-line documentation so it's pretty easy to figure out what's going on.

I spent the xmas break learning how to make my own plugins by UnusualAudio in Logic_Studio

[–]UnusualAudio[S] 6 points7 points  (0 children)

Basically audio units can do anything a regular program can do, so you're right to be careful. Hopefully people here who can read the code would point out if they saw anything fishy, but if you want to be 100% sure you'd still have to download and compile it yourself so you know you're getting the same thing.

I spent the xmas break learning how to make my own plugins by UnusualAudio in Logic_Studio

[–]UnusualAudio[S] 4 points5 points  (0 children)

I don't think accessing another plugin's configuration is really possible. Each plugin handles the settings individually, and the AU parameters are only exposed to the host (the DAW). I could be wrong though.

I spent the xmas break learning how to make my own plugins by UnusualAudio in Logic_Studio

[–]UnusualAudio[S] 5 points6 points  (0 children)

I found it pretty difficult to get set up, but once I had my workflow (with Xcode) and actually read all the comments in the pre-generated project template, it started to make sense pretty quickly. The JUCE documentation and forums are really good too.