Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mark_h]

I mentioned this previously, but never followed up...

When doing a conversion using DSP, third party VSTs do not seem to be part of the conversion even though they would normally affect the sound.

Matt previously said he thought this should work...

Today I added another third party VST that I wanted to test via conversions (to see what difference they make) and again the VST wasn't part of the resulting conversion...

So this does seem to be broken?

[Awesome Donkey]

Is it this issue you're referring to?

[Matt]

I'm guessing the same DLNA fix will carry through to the converter.

If it's still an issue after you try the next build (it's not out yet), just let us know.

I just realized this is the beta board, so the build might be out.  It didn't get put in history (darn it) so I'm not certain.  After more checking, it's not in the build that's out to beta yet.

Thanks.

[Matt]

The build to test is live now.

It has this:
NEW: Third party DSP plugins (like VST effects) are now enabled for DLNA.

I think it will carry through, but like I said, just let us know.  If it is still goofed, at least we know where to look!

Thanks.

[mark_h]

Yup, working now.  Many thanks.

[Matt]

Thanks for letting us know.

Can we add another feature:
NEW: VST plugins work when converting.

Or is that being greedy

[mark_h]

Go for it  

But can I ask for something else while we're on VST?

I just paid for registration of of VST and have received my key but I cannot copy/paste in the DSP dialogue and so am having to enter by hand.  Inevitably I made a typo and cannot now edit either... if I hit delete, for instance, MC asks me do I really want to delete 11,000+ tracks from MC (the current playlist)!!

So I'm now stuck with a VST I cannot register because text editing doesn't work well.

Is this a VST thing or an MC thing??

I'll try reinstalling the VST to clear the text and then attempt to reenter the code.

[mark_h]

Also, while we're talking VST  

I want to stick an waveform analyzer before the Volume Leveling control so that I can see what's going in to the DSP chain, and one at the end, so I can see what's coming out, but MC won't allow me to put a VST there.  Is that restriction absolutely necessary?  I get that a VST that changes the volume could mess up Volume Leveling, but shouldn't that be at the user's control...?

[edit]Actually, I'd like to request this change more strongly...  I want to put Perfect Declipper in front of Volume Leveling so that it can work with the unaltered data stream.  The VST attenuates the volume by 6dB to give headroom for unclipping which  I can add back either prior to or on the other side of Volume Leveling to restore the volume to the correct adjusted level...  I wonder if there are other VSTs that would also prefer to work with unattenuated data and would be more appropriately placed before Volume Leveling?[/edit]

[mojave]

I want to stick an waveform analyzer before the Volume Leveling control so that I can see what's going in to the DSP chain, and one at the end, so I can see what's coming out, but MC won't allow me to put a VST there.  Is that restriction absolutely necessary?  I get that a VST that changes the volume could mess up Volume Leveling, but shouldn't that be at the user's control...?

Click Options at the top right of the DSP and select "Process independently of internal volume." You still can't put them before Volume Leveling or Adaptive Volume, but you can see what is happening before any additional DSP.

[mark_h]

That only turns off the volume slider not the DSP changes...

Which is what you said.

With the declipper (and perhaps some other VST) it really should go before levelling to get the unattenuated data. 

[mark_h]

And now I'm wondering whether the conversion is working completely correctly...

It's certainly working *partially*, but if I run multiple conversions I am seeing different results every time with the more conversions I do the later the conversion starts...

Is there some sort of pre-buffering going on where the data isn't going through the VSTs?

[mark_h]

OK, further to the above: an example of the problem using the Perfect Declipper VST

First, the original waveform:



Now the correct conversion (done in Adobe Audition)



And the faulty conversion, done in MC:



You can see that MC doesn't start converting via DSP until towards the end of that first big chunk of data.

And here is a second conversion of exactly the same track, through exactly the same DSP chain.



You can see the conversion starts slightly later this time.  And subsequent conversions seem to start later and later in the same track.

I *hear* the same thing through the DLNA DSP chain - the track starts playing without DSP and then partway through the track the DSP kicks in.

So it looks like: NEW: Third party DSP plugins (like VST effects) are now enabled for DLNA. isn't functioning quite correctly yet...

And it's not just third party VST - the same thing happens with MC's own DSP.

[mark_h]

So I hope there's a solution to this.  The more I think about this feature, the more I realise how great it is - to be able to apply various VST/MC DSP to all conversions, eg Convert Format, via DNLA, via handheld transfers, is incredibly powerful, a game changer even, and a major feather in MC's cap... a feather that is currently slightly bent and broken...

[Hendrik]

Next build:
Fixed: VST effects were not being properly applied during the beginning of tracks for DLNA or format conversions.

[mark_h]

/cheer

[mark_h]

Confirming that Convert Format definitely works now with VST.  Will test DNLA later but am assuming that will also work.

Thanks so much.  This really is a big thing, for me at least
 

[mark_h]

As per the release thread - this is working for Convert Format but not for Handheld conversions.