KVR Audio

mandolarian · Post by **mandolarian** » Wed Oct 26, 2011 8:52 pm

Will this update fix the crash in Vegas 10? I know! I'll test it. This EQ is almost ideal for video foley work...as well as the artistic music stuff too.

MeldaProduction · Post by **MeldaProduction** » Thu Oct 27, 2011 1:46 am

mandolarian wrote:Will this update fix the crash in Vegas 10? I know! I'll test it. This EQ is almost ideal for video foley work...as well as the artistic music stuff too.

What crash? And what is Vegas 10? Ok, I'll try to check, because frankly I have never heard of it.

mandolarian · Post by **mandolarian** » Thu Oct 27, 2011 5:54 am

Sony Vegas - video editing software (also an unlimited track DAW)
http://www.sonycreativesoftware.com/vegaspro
from the same company that brought you Acid.

Anyhow, I can report that both versions of of your EQ are either non-functional or make the host unstable. Similar to the user.

Sony Vegas is my video editor of choice and since it's a multi-track DAW as well, I like to use it to tweak audio tracks while editing video - and your new EQ is ideal for that sort of work. Except for the not working too well part.

MeldaProduction · Post by **MeldaProduction** » Thu Oct 27, 2011 10:27 am

mandolarian wrote:Sony Vegas - video editing software (also an unlimited track DAW)
http://www.sonycreativesoftware.com/vegaspro
from the same company that brought you Acid.

Anyhow, I can report that both versions of of your EQ are either non-functional or make the host unstable. Similar to the user.

Sony Vegas is my video editor of choice and since it's a multi-track DAW as well, I like to use it to tweak audio tracks while editing video - and your new EQ is ideal for that sort of work. Except for the not working too well part.

Ok, I checked and it really doesn't work well - so far I have found that when you use sonogram or analyzer, it starts lagging and then stopps completely. But to me it looks like Vegas's fault, so I'll be contacting their support. Anyway do you have any other issues? Because otherwise it seems working fine.

mandolarian · Post by **mandolarian** » Fri Oct 28, 2011 12:06 am

Vegas is not the most stable VST host. I'm using Vegas 10, where the plugin more often than not doesn't even get initialized before Vegas locks up. I'll be upgrading to 11 very soon, however.

When it does load, as soon as I attempt to use the 'auto' dynamic section, Vegas slows down and freezes 90% of the time.

Thanks for checking into this - MAutoDynamicEq has great potential for video post work. I'll be buying it soon, even if I have to tweak audio in a 'proper' VST host.

MeldaProduction · Post by **MeldaProduction** » Fri Oct 28, 2011 12:08 am

mandolarian wrote:Vegas is not the most stable VST host. I'm using Vegas 10, where the plugin more often than not doesn't even get initialized before Vegas locks up. I'll be upgrading to 11 very soon, however.

When it does load, as soon as I attempt to use the 'auto' dynamic section, Vegas slows down and freezes 90% of the time.

Thanks for checking into this - MAutoDynamicEq has great potential for video post work. I'll be buying it soon, even if I have to tweak audio in a 'proper' VST host.

Okey dokey, thanks, I'll contact their support, let's see what they find out. So far my debugging experimented ended in locks/crashes inside the host, so it's hard to say what causes this. We'll see.

pheeleep · Post by **pheeleep** » Fri Oct 28, 2011 12:17 am

In the second to last version (no time yet to download the latest), if I right click a band another window opens with more settings. In Studio One V2 Pro, if auto scroll is on, as soon as the GUI refreshes (time line moves on past what is viewable in the GUI), the Melda window disappears and I have to reopen it after. I only get a few seconds I can edit the settings if I am playing in Studio One and have the scroll option on. Probably happens with all the plugins. Need to check.

Any solution aside from turning off auto scroll? Or having to zoom out all the way (so the time line never scrolls)?

Windows 7 64-bit
Using Presonus Studio one Pro V2 32-bit version.
Using the 32-bit VST 2 and 3 versions of your plugin.

On another note, should I be using Vst2 or 3? I thought VST3 was just for Cubase users but both hosts that I use (also FL Studio) support VST3. What is the advantage of using VST3 in those hosts?

Thanks!

MeldaProduction · Post by **MeldaProduction** » Fri Oct 28, 2011 7:49 pm

Ok, I'll be probably contacting Studio One devs about this. I haven't experienced it, but this happens when the host tries to activate some of its windows. The thing is, the plugin must let him do that and close the window, because some of the hosts (e.g. Live) tend to destroy plugins and a plugin with open modal window being destroyed, that's an inevitable crash.

About VST2 vs. VST3. That's a question. VST3 is definitely better (it knows sidechains and other multichannels, is maybe slightly faster), VST2 on the other side doesn't know sidechains and has lots of compatibility problems with older hosts. It usually takes some time, before an interface "settles" in some stable form. VST2 is now quite settled, but there are lots of hacks for the older hosts. VST3 on the other isn't settled yet, but there aren't many problems expected as it is quite well designed. Though for example FL Studio is very problematic (at least last time I checked), so with FL Studio I recommend using VST2. It's basically the only host, in all others I recommend using VST3. I'd rather avoid AU, and never use RTAS unless necessary (but even Avid finally realized that RTAS is just too much and so it will be deprecated soon).

pheeleep · Post by **pheeleep** » Fri Oct 28, 2011 9:42 pm

I am still confused because I use many VST2 with sidechain in FL Studio. Sidechain works with VST2...

I will follow your advice though (although your VST3 plugins seem to work just fine in FL Studio).

MeldaProduction · Post by **MeldaProduction** » Fri Oct 28, 2011 9:57 pm

pheeleep wrote:I am still confused because I use many VST2 with sidechain in FL Studio. Sidechain works with VST2...

I will follow your advice though (although your VST3 plugins seem to work just fine in FL Studio).

Well, when the side-chain epidemy

started, some countermeasures have been taken, so that VST2 works. But the standard doesn't support it natively, or it's better to say that the sidechain support is quite "hybrid". The trouble is that since it originally wasn't there, hosts didn't adjust to it, so that for example Cubase SX has quite fatal problem with plugins with sidechain.

Our VST3 does work fine in FL Studio? Very well, they probably fixed it

. We were solving it some time ago, but the conversation kind of faded out

.

contrary · Post by **contrary** » Sat Oct 29, 2011 1:09 am

Another nice one Vojtech ,

The GUI's is another step in the right direction; more succinct and crisp . Seems to be more easy on my eyes. The pop up for the filter selection is a great Idea . Overall hit with us here !

MeldaProduction · Post by **MeldaProduction** » Sat Oct 29, 2011 1:09 pm

contrary wrote:Another nice one Vojtech ,

The GUI's is another step in the right direction; more succinct and crisp . Seems to be more easy on my eyes. The pop up for the filter selection is a great Idea . Overall hit with us here !

musicbynumbers · Post by **musicbynumbers** » Sun Oct 30, 2011 3:21 pm

MeldaProduction wrote:Ok folks, another update, this time very small, is available. It basically improves the highlighting and a few other things. The main reason was that it was crashing on surround in some hosts. For change list check:

meldaproduction.com/mautodynamiceq/?page=changes

It's not needed, just if you like updates or have troubles .

Thanks for this !!

Just tried the smoothing parameter and it definitely helps.

I still get some very quick jumps in frequency which cause some "soft popping" noises which seem like they could be sorted out if there was a parameter for a kind of "portamento" slew function so that this abrupt changes happened over a defined (but short) period of even a millisecond should stop these glitches.

Hope that makes sense, will keep experimenting to try and get it right but I could also make a quick screen capture if you want to give you an idea of what I mean?

MeldaProduction · Post by **MeldaProduction** » Sun Oct 30, 2011 3:28 pm

My pleasure

.

About the abrupt changes - could you send me a short wave clip? I'd check it for myself. The thing is, the detection without is basically impossible. The variety of parameters (like frequency range, smoothing and threshold) are there simply to adjust to the specific type of signal (like voice or guitar for example). The voice is especially tricky as it contains lots of short burts of variating frequencies, and in this case the smoothing should help I believe.

musicbynumbers · Post by **musicbynumbers** » Sun Oct 30, 2011 7:53 pm

Thanks

Will send a clip sometime this week when I have time.

The smoothing helps to stop it randomly jumping to false notes but would be great if instead of changing frequency instantly (As in 0 amount of time between changing frequency) if it had an ability to glide so It took say few milliseconds to get to the new detected frequency it might not make the pops.

Will attempt to post visit at some point to explain it better

MDynamicEq and MAutoDynamicEq released with riddiculous introductory prices! - LAST CHANCE!