How long till we get support for VST3 presets?
- KVRAF
- Topic Starter
- 37488 posts since 14 Sep, 2002 from In teh net
It didn't when I took that screenshot above - when did that change?
-
- KVRAF
- 1790 posts since 30 Dec, 2012
In 8.0.24, released in April.
8.0.24
- Improved the file-based plugin preset list structure to follow directory structure
-
- KVRer
- 24 posts since 30 Aug, 2017
I don't know if it's related, but i have a project that uses Sonimus Tuco. It was started on a Mac and later imported on a PC. They both have Tuco. The only diference is that on the Mac i created a preset inside Tuco.dRowAudio wrote:In 8.0.24, released in April.
8.0.24
- Improved the file-based plugin preset list structure to follow directory structure
When i click on Tuco on the PC it close Waveform 8.2.27 without notice. When i insert Tuco it doesn't crash. I suspect it only crash Waveform on the PC when i choose the Tuco instance that was using that preset.
Should i report this to Sonimus too?
- KVRAF
- Topic Starter
- 37488 posts since 14 Sep, 2002 from In teh net
Cool - I'd stopped using the AU because of this so hadn't noticed, much better thanksdRowAudio wrote:In 8.0.24, released in April.
8.0.24
- Improved the file-based plugin preset list structure to follow directory structure
Can't wait to try this with VST3
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Cool, let me know what kind of coverage you get. I can't quite figure out why Padshop doesn't load presets for me but could be something to do with the trial I guess?
- KVRAF
- Topic Starter
- 37488 posts since 14 Sep, 2002 from In teh net
- KVRian
- 1313 posts since 3 May, 2005 from Victoria, BC
- KVRAF
- Topic Starter
- 37488 posts since 14 Sep, 2002 from In teh net
OK thanks - looks like I can browse Padshop Pro presets but they don't do anything when I try and load one
- KVRAF
- Topic Starter
- 37488 posts since 14 Sep, 2002 from In teh net
Not just Padshop pro - same issue with my Softube VST3s
Waldorf seem to no longer be using vstpresets so can't test with those any more (they were when I first asked for this ironically)
Waldorf seem to no longer be using vstpresets so can't test with those any more (they were when I first asked for this ironically)
- KVRAF
- Topic Starter
- 37488 posts since 14 Sep, 2002 from In teh net
-
- KVRAF
- 1790 posts since 30 Dec, 2012
I'll have to wait until Fabian is back on the JUCE team in February to investigate this further.
- KVRAF
- Topic Starter
- 37488 posts since 14 Sep, 2002 from In teh net
Annoying that I'll now have to pay to upgrade just to get the fix - which I presume is still to come?
-
- KVRAF
- 1790 posts since 30 Dec, 2012
The fix should have been in the last version of the public beta and is in the full released version.
You can download the 30-day demo to check it works but I verified it with Padshop Pro Trial and a few other plugins.
There is still a remaining Steinberg VST3 bug on the Mac where Steinberg plugins will crash if removed and then added back to an Edit. I'll hopefully be looking in to that this week.
You can download the 30-day demo to check it works but I verified it with Padshop Pro Trial and a few other plugins.
There is still a remaining Steinberg VST3 bug on the Mac where Steinberg plugins will crash if removed and then added back to an Edit. I'll hopefully be looking in to that this week.
- KVRAF
- Topic Starter
- 37488 posts since 14 Sep, 2002 from In teh net
Just tried, it's not. I can browse presets but they don't load with either Padshop Pro or Softube pluginsdRowAudio wrote:The fix should have been in the last version of the public beta and is in the full released version.
You can download the 30-day demo to check it works but I verified it with Padshop Pro Trial and a few other plugins.
- KVRAF
- Topic Starter
- 37488 posts since 14 Sep, 2002 from In teh net
Is it fixed in the new beta?
And tbh I do find it annoying that I've waited 4 years (this thread goes back to 2014) and paid for 3 updates already waiting for this fix and now have to pay for another to even get a possibility of a fix
And tbh I do find it annoying that I've waited 4 years (this thread goes back to 2014) and paid for 3 updates already waiting for this fix and now have to pay for another to even get a possibility of a fix
