MeldaProduction freezes With VIP
-
- KVRer
- Topic Starter
- 8 posts since 19 Mar, 2007
After loading the plugin And change the preset or any of the controls on the plugin it freezes. Not just the plugin but also the VIP program. Then I have to do the control alt delete thing.
-
- KVRist
- 246 posts since 14 Nov, 2016 from Berliner Umland
You are using VIP 3.0 on Windows, right? Because for me the freeze does not happen on OSX. The plugins are usable but do not have full preset management functionality.saint45 wrote:... Then I have to do the control alt delete thing...
-
- KVRian
- 509 posts since 28 Oct, 2012 from Argentina
Just came across this in another place in KVR discussing VIP 3.0. Perhaps it helps?
“I'm not saying this is the case here, but I've seen some plugin crash if you ask them to load a preset, or play something while their UI is being closed. You can work around that by disabling the 'smooth preset transition' and/or the plugin caching option in VIP, for that particular plugin (gear icon in the lower right when that plugin is loaded).
More generally, VIP uses VST's single-preset setChunk calls. This is not something that you do very often in other DAW's, and because of that, it's not something that developers test a lot.”
“I'm not saying this is the case here, but I've seen some plugin crash if you ask them to load a preset, or play something while their UI is being closed. You can work around that by disabling the 'smooth preset transition' and/or the plugin caching option in VIP, for that particular plugin (gear icon in the lower right when that plugin is loaded).
More generally, VIP uses VST's single-preset setChunk calls. This is not something that you do very often in other DAW's, and because of that, it's not something that developers test a lot.”
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Well, we are certainly using setChunk, but from what you wrote I fear it could actually do that repeatedly for each processing block (for this 'smooth preset transition'). I hope that's not true, because that would be a plain stupidity (sorry). No CPU would handle that in general... Of course, it's super easy to implement from the host's point of view, but just completely wrong... But maybe that's not what happens there.
Anyways again I'd recommend reporting it to them. I'll check when possible.
Anyways again I'd recommend reporting it to them. I'll check when possible.
-
- KVRian
- 509 posts since 28 Oct, 2012 from Argentina
I am not an Akai boy, nor was I complaining, since I am not using VIP so much, much less with FX plugins. No need to apologise!MeldaProduction wrote:(sorry)
-
- KVRist
- 246 posts since 14 Nov, 2016 from Berliner Umland
I checked on OSX with MXXX and MFlanger. The 'smooth preset transition' setting makes no difference. Works on OSX with all settings. But be aware that 'smooth preset transition' is a per instrument (not Effect) setting. Maybe it matters what synth you are using? For me it works with all I have but maybe some do not work. But that is independent from Melda plugins.pumafred wrote:... disabling the 'smooth preset transition' and/or the plugin caching option in VIP... setChunk calls...”
For the record my AKAI VIP Preferences: Tooltips ON, Enable store OFF, Enable Demo Mode OFF, Items/Page 500, Auto-tag patches ON, Enable hardware auto-select ON, Plugin cache size 32, Multicore ON/4, Full bypass mute OFF, Setlist control edit ON, Boost 0db
Instrument preferences: Everything ON
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Ok, so on Win 10, they for some reason disable the ability for the plugin to get activated/focused after a change of presets. I have fixed it on our end and will be released with the next update, but it's more like a bug in VIP. I have let them know.
Anyways the solution is simple - after you change a preset, use alt+tab to switch to another app and back
. Then it starts working again .
Anyways the solution is simple - after you change a preset, use alt+tab to switch to another app and back
. Then it starts working again .-
- KVRian
- 509 posts since 28 Oct, 2012 from Argentina
Vojtech: Always impressed by you.MeldaProduction wrote:I have fixed it on our end and will be released with the next update, but it's more like a bug in VIP. I have let them know.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Thanks! 
-
- KVRAF
- 3388 posts since 29 May, 2001 from New York, NY
Nah of course we're not calling setChunk() in processing blocks. setChunk() is supposed to be called only from the UI thread anyway.MeldaProduction wrote:Well, we are certainly using setChunk, but from what you wrote I fear it could actually do that repeatedly for each processing block (for this 'smooth preset transition'). I hope that's not true, because that would be a plain stupidity (sorry). No CPU would handle that in general... Of course, it's super easy to implement from the host's point of view, but just completely wrong... But maybe that's not what happens there.
Anyways again I'd recommend reporting it to them. I'll check when possible.
The smooth preset transition thing, creates a second instance of the plugin, calls setChunk() on it, then adds it to mixer engine so you have 2 instances running (the old one which will eventually be faded out, and the new one).
-
- KVRAF
- 3388 posts since 29 May, 2001 from New York, NY
Yeah well, that's because I spend most of my time on it 
-
- KVRian
- 509 posts since 28 Oct, 2012 from Argentina
So, how did it go?saint45 wrote:Great thank you let’s hope this all works out, will let you know.
With Vojtech and Big Tick (sounds like a comedy duo!) here, you couldn´t hope for more qualified help!