The demo (including the used host) recently crashed for me in Wavelab 7 (32bit). But probably due to the 2x oversampling mode. After I loaded the very same plugins sans oversampling enabled, no crash after the file was played from start to end and/or constant loops of more than 20minutes.
I'd love to see a container function like with Plogue Bidule. Else it does what it should, and definitely better than a certain competition.
DDMF Metaplugin needs a...
-
- KVRAF
- 14740 posts since 19 Oct, 2003 from Berlin, Germany
-
- KVRian
- 669 posts since 2 Apr, 2005 from out there
Which plugin was that that seemed to cause a crash in oversample mode?
Talking about competitors: since this tool is freely available (as far as I can see) I think I should mention that http://www.xlutop.com/buzz/zip/shell2vst.zip can be used to split up wrapped plugin bundles like Waves into their components (hats off to Frank for this!). Which means Waves plugins can be loaded as well. Still have to try for Uhbik, but the same principle should apply.
Talking about competitors: since this tool is freely available (as far as I can see) I think I should mention that http://www.xlutop.com/buzz/zip/shell2vst.zip can be used to split up wrapped plugin bundles like Waves into their components (hats off to Frank for this!). Which means Waves plugins can be loaded as well. Still have to try for Uhbik, but the same principle should apply.
-
- KVRAF
- 14740 posts since 19 Oct, 2003 from Berlin, Germany
IIRC it was TB EBULoudness or MeldaProduction MLoudnessAnalyser.
I was using an earlier version of TB which did not really work with Wavelab. I accidentally hit 2x, played a song from start to end - crash. Next test I did was flawless.
You got a mail from me the other day where I got no answer so far.
I was using an earlier version of TB which did not really work with Wavelab. I accidentally hit 2x, played a song from start to end - crash. Next test I did was flawless.
You got a mail from me the other day where I got no answer so far.
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRian
- 669 posts since 2 Apr, 2005 from out there
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRAF
- 14740 posts since 19 Oct, 2003 from Berlin, Germany
Indeed the spamfilter, could clear why I don't get answers from firms recently.docdued wrote:Sent it this morning... spam filter maybe?
Thanks for answering.
-
- KVRAF
- 1895 posts since 13 Oct, 2002
I've had a few stupid crashes with Metaplugin with Nuendo 5.5.3 64-bit. It always happens when I close a plugin GUI instance within Metaplugin, but I've been unable to repro. It happened to me once in my repro tests and it seems that I clicked "unusually", like "tripping" with the mouse (multiple spastic clicks and some movement around the close button), but I tried many times and just couldn't get it to happen again. I'll try to be more careful with it in use. By the way this happened with Sonalksis's FreeG, both in use and in tests, so it's free to try, if anyone cares to.
I have a few feature requests:
1. Could it be obvious which version DDMF is running (32 or 64), by indicated it in some form in the GUI? That way we immediately know which version the host is running.
2. Could the plugin favorites (the ones that build automatically as you load new plugins) only add plugins that have been instantiated successfully? That way they wouldn't be littered with plugins that won't load. Currently not all plugins are identified as 64-bit by their name and it's easy to load an incompatible version.
3. Could we be able to define which plugin folders are accessible to each version? That would solve point 2 neatly.
4. This one's somewhat more complex, but Metaplugin is useful to instantiate multiple identical plugins for multi-channel effects. When doing this, it would be really cool to link all the same parameters to one GUI so they could all be changed by one instance.
Thanks!
I have a few feature requests:
1. Could it be obvious which version DDMF is running (32 or 64), by indicated it in some form in the GUI? That way we immediately know which version the host is running.
2. Could the plugin favorites (the ones that build automatically as you load new plugins) only add plugins that have been instantiated successfully? That way they wouldn't be littered with plugins that won't load. Currently not all plugins are identified as 64-bit by their name and it's easy to load an incompatible version.
3. Could we be able to define which plugin folders are accessible to each version? That would solve point 2 neatly.
4. This one's somewhat more complex, but Metaplugin is useful to instantiate multiple identical plugins for multi-channel effects. When doing this, it would be really cool to link all the same parameters to one GUI so they could all be changed by one instance.
Thanks!
-
- KVRer
- 20 posts since 16 May, 2005 from Warsaw, Poland
Hi, Waves Abbeyroad Saturator VST3 in MetaPlugin v4.01/02 crashes Cubase 11 (PC, Ryzen 5900X, 64GB RAM ) after playback start. MetaPlugin is useless for me at the moment.
Should I revert to some earlier version? Not so many time for experiments now. I've not had such problems with Metaplugin before.
Cheers, K
Should I revert to some earlier version? Not so many time for experiments now. I've not had such problems with Metaplugin before.
Cheers, K
Kuba