45 postsPage 3 of 3
1, 2, 3
I found a workaround (for me anyway).
Put all the waveshells in the VST3 folder into their own folder (say "Waveshells").
Then, when you want to burn a DDP image, move that folder somewhere else (of course you can't use vst3 waves plugins but vst2 ones still work)
Now you can burn an DDP image.
Don't forget to move the "Waveshell" folder back when you're done.

Presonus:
Surely this can be addressed?
User avatar
by carlman on Fri Mar 27, 2020 7:39 am
I have the same problem in the last version of 3. Has this issue been fixed in v4?
User avatar
by Bbd on Fri Mar 27, 2020 8:05 am
Try downloading the latest version of Studio One in a new folder and test. If you don't like it, you can go back to your normal install.

Bbd

Please add your specs to your SIGNATURE.
Search the STUDIO ONE 4 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


OS: Win 10 x64 Home, Studio One Pro 4.x, Notion 6, Series III 24, Studio 192, Haswell CPU: i7 4790k @ 4.4GHz, RAM: 16GB, Faderport 8/16, Central Station +, PreSonus Sceptre S6, Eris 3.5, Temblor 10, ATOM
User avatar
by carlman on Fri Mar 27, 2020 12:24 pm
I demoed 4 a while ago so I can't try it again. Some said Cd burning in 4 works, others say it doesn't. Did it actually get fixed by now or is the problem still user dependent (on Win 10 here btw)
User avatar
by echopark on Sun May 10, 2020 8:27 am
I had this "CD Burning service not installed" problem with Studio One 2.6.5. Someone had given the tip with vst 3 shells. It worked for me. Apparently the files WaveShell1.vst3 - WaveShell6.vst3 from Waves caused this burning problem. As soon as I remove them from the VST3 folder everything works again.

45 postsPage 3 of 3
1, 2, 3

Who is online

Users browsing this forum: AriAhrendt, BobF, garybowling and 21 guests