Bruno de Souza Lino

https://www.izotope.com/en/shop/exponential-audio-phoenixverb.html

This is an old issue some developers have, which is thinking User Interfaces are just a beauty tack on top of functionality. Then you either end with the worst skeumorphic abominations to mankind (Like Butch Vig Vocals) or interfaces that only make sense and are intuitive to the person that created them (Like Ardour/Harrison).

What I'm actually sending to the entire mix is something I've done already...When I mixed the track. And that's what comes out of the hardware outputs. Next thing you'll tell me is you actually have to do another mix using what you selected at the export window. Can we return to the old audio export thing where it just worked and didn't introduce extra hurdles that make no sense?

It makes no sense for the "Entire Mix" preset to require you to select which tracks have to be exported or to select none at all, especially considering it's grabbing audio from the hardware outputs.

I experienced this bug as well. Apparently, if you don't select all tracks before opening the export window, the mp3 export doesn't work.

I mean, maybe one could get someone like Dan Worrall to make a video about it or something?

Usually people that do plugins for Mac have Macs as their development machines. You can't create AU plugins anywhere else.

There's not much info about, videos or otherwise. By videos, I mean stuff done by people which aren't the person who created the plugin. I was also under the impression that the only people who know how LUFS work are the EBU and the people that develop meters that display it.

Except you'd be sued for copying 31 bars of John Cage's 4'33"

Could we have posts close automatically once nobody has responded to them after some period like a month or a year?

Why are we responding to a thread from 2019?

It's in the module comparison (Mini Plugin Host). That module is only available for Core and you can't purchase it for any other version. It doesn't even show on the store.

Waves does their plugins like that because that's how ProTools has its tracks. As per usual, they're still stuck in 1995, where plugins had to be specifically built to be either mono, stereo or convert mono to stereo as separate processes. There's only a single dll of each plugin though. They just appear like that because of Waves witchcraft.

Apparently, the funky thing running in the background only affects Cakewalk? Doing this operation in REAPER is instantaneous. I just apply it and it happens.

In my case, I wanted a single clip to be played at half the speed, so I used "Process-Length" and set that to 200%. On a 4 minute mono track, that took about 5 minutes to happen. Then I go on Reaper, with the exact same clip, open its properties, set the playback rate to half and as soon as I confirm it, it's done. No mixing down of audio or progress bar.

It's not that we ignore T-Racks. Much like every IK Multimedia product, our interest in it only lasts 180 seconds. After that, IK has to pay us 20 bucks to have 180 seconds more.

And probably makes it some essential feature from it require a download in 180 days or you have to pay ransom to have it back.

I had to change the length of some tracks for a project and the slow behavior was worse. Then I went to Reaper and doing the exact same thing is instantaneous, even on all tracks at once.

I tested running the plugin under a different wrapper inside Cakewalk (Waves Studio Rack and Element) and it opens.

Well, that feature works and I only had to download the v9 apps to get SuperTap to work. Granted....It still screws up with Cakewalk's auto scan and you have to disable it to not have WavesShell scanned every time you open it.

It's great how companies are not happy with versioning their products with numbers to the point they need to have two different versions. I wonder if we'll get a T-Racks 5 v2 mkII or something.

One of the primary issues with Melda plugins is you have to read manuals even for the stuff which should be straight forward. All plugins have controls with different names than you'd see somewhere else and there's extra stuff you can click and see no effect yet it leeks like it's doing something. There's also some annoying UI quirks, like not being able to type numerical values using your keyboard, every single thing that could be condensed into a single interface always seems to open a popup with even more settings you didn't even know existed and so on. Sure these plugins are powerful and full of features but your stuff is only as useful as how easily others can learn it.

Then they release T-Racks 6 later for cheaper.

When you focus on specific instances at a given time, you can listen over and over and over and speak of some different things each time. But that's often the problem. If I play you the same thing twice and you listen for two different things, you'll remember two different things. This isn't hallucination, this isn't deception. This is how our brains work. The problem is, if you expect a difference, you're gonna listen for different things and you'll hear different things even if you have the same stimulus. And this is one of the really important points of doing any kind of auditory testing. If you listen for something differently for different features, you'll remember different things. That because you extracted a little piece out of that sea of data. And if you have a reason to assume things are different, you're likely to listen to differently, you're likely to focus on different things and you're likely to remember different things. Or maybe if you convinced yourself everything sounds the same, you'll steer yourself that way. Whenever you do auditory testing, or any test for auditory stimuli, it must have a falsifiable design. Meaning you have to actually be able to tell if there's something you actually detected or if there's something you consciously or subconsciously steered yourself into noticing. You have to be able to test that. What that basically means is you have to do a blind test because, if you know what the two things are, your brain is gonna use that information. Doesn't matter how smart you are, how trained you are, who you are...There hasn't been an example of someone who can avoid it. It's just life.

For reference, only the Behringer interfaces with HD in their model name have their own ASIO drivers. You'll need ASIO4ALL for the others. See if you can change to a UMC202HD. It seems to be only slightly more expensive than the UM22.