vitSince the latest update (previous versions were OK) I have noticed that the SD3 plugin does not respond correctly to the PLAY command in Cubase 12. (Windows 10, x64). Sometimes it’s ok, sometimes it doesn’t play at all, sometimes it reacts with a pause of several seconds, i.e. no drums in playback during that time. The same applies to rendering audio. Sometimes it’s OK. Other times the plugin won’t start until a minute later and the resulting audio is missing half od the drums. Sometimes the render starts senselessly from the point where the cursor is in the project, the previous part of drums is missing. In the same project. Sometimes the render doesn’t go through, other times the same project does. If I simply open the project, wait for loading all libraries and try to export audio mixdown, the plugin usually sleeps – generates no audio. Does anyone notice similar behavior?
ElMojoI have been saying this for weeks. You are the first to notice this issue too.
1
Thanked by: vit
leachydSame for me, after updating to to 3.3.2 the drums will stop playing back at times in Cubase 12 (Windows 11). I have to open the SD3 Gui Toggle the Follow host button and hit the play button to get SD3 to resync with Cubase. This never happened in the last version. Please fix it.
Dave
1
Thanked by: ElMojo
Neil_28Not just me, then. It’s stopping me write, mix or export, and support hasn’t responded. Anyone know how to go back to 3.2.8?
1
Thanked by: ElMojoElMojoNot that easy unless you still have the last version saved. Which I did. If and only if you have the last version saved on disk locally. Then uninstall SD3 3.3.2 in Windows App. Then go back into to the last version of SD3 in Toontrack Product Manager it will work. It gets you away from this maddness Toontrack have created. That is how to simply remove this incredible marketing screw up. If you don’t have a local version then contact Toontrack. I would call it Toonrack support but they don’t deserve that title.
1
Thanked by: Neil_28ElMojoOoops! Do not unistall any add in stuff. Just uninstall the core SD3 only. Phew!
1
Thanked by: Neil_28
ScottThanks guys. I’ll forward these reports to the Toontrack programmers.
Scott Sibley - Toontrack
Technical Advisor
Neil_28God – don’t remove the current version, then install the old, like I did, unless you want all your drum parts to disappear! Five songs royally knackered. All back when I updated back to 3.2.8, TF.
ElMojoNeil_28
Ouch! I am glad you got your songs back. It worked for me, although I hadn’t used anything new from the latest release. I did get a dialogue box telling me that the project was from a later version. After that everything worked perfectly. You make a very good point that you should backup your projects before making any changes. I have raised a support request related to Cubase 12.0.30 and this issue. I am still waiting for some feedback.
1
Thanked by: Neil_28Neil_28Weird thing was, I’m always backed-up, but it made no difference, cos the programming exists in SD3, not Cubase, so as soon as I changed the SD3 version, the part blocks vaporised from it. I am now striping to audio as a flawless drum back-up – at least, I would, if SD3 would let me bloody export!
Olof HermanssonI have examined this 3.3.2 issue in Cubase more closely now. It seems to behave like this: If the plug window has not been opened since the Cubase project was opened, every time you stop playback in Cubase, the position is remembered by the SD3 and the next time you start playback (or export), MIDI from the song track inside the plug will not be played until the playhead comes past that position. If the SD3 window has been opened at least once after opening the project, also moving the playhead in Cubase updates the remembered position.
Before we release an update with a fix, here are some possible workarounds:
Olof Hermansson - Toontrack
Coder
3
Thanked by: Jeffrey Sheppard, ElMojo and Neil_28Neil_28Cheers. I’ll try this later. Let us know when a fix is issued, please.
John HarrisI may have some additional info on this issue. I’m a new SD3 user and encountered this problem on day one. It does >not< seem to be related to the status of the plugin window (open/closed etc).
The following seems to be true for me (at least) regarding the “CB12/SD3 stuck pointer” issue.
I’ve done a short vid using a simply Cubase 12 project with SD3 and my ageing copy of BFD3. Both products use a similar groove assembly window and the SD3 stuck “playhead” can be seen while BFD3’s playhead tracks with the host. I’m using a marker track and the num keys to jump from point to point. Again, using the mouse to position the Cubase playback head also results in a stuck SD3 playback head.
First error – https://youtu.be/0f3w7zbIAP8?t=34
Second – https://youtu.be/0f3w7zbIAP8?t=60
Third and fourth – https://youtu.be/0f3w7zbIAP8?t=84
And here, notice that I’ve started jumping to other positions before either selecting the same marker where SD3 has halted or allowing the host to catch up to SD3 position. SD3 won’t move until either I send a STOP command or I RE-select the marker where SD3 has stopped. – https://youtu.be/0f3w7zbIAP8?t=101
Hope it helps somewhere.
JD
ElMojoThis problem seems to just get worse and worse. Now I am finding that the C Suite C Vox is screwed up too. It starts in the left lower 25% lower corner of the plugin until yet again. I have to click on it to make it take up the full screen. Please lets go back to when this all worked. Stop trying to polish a turd! I just want a working system. That is not to much to ask is it! If I pay the money you people want I expect the scaling to work perfectly. You have had issues with this from when I first purchased this system and still no progress. Give me the source code and I will fix it. Now it is driving me mad. How much longer before we get a fix. Are you just trying to prove your nag screen works despite what I have said.
1
Thanked by: Neil_28
Stephen HarrisonThis issue is getting on my nerves. Obviously I’m using Cubase too.
I found pressing space bar 3 times normally gets the drums going but I’m not accepting that going forward, it’s just too annoying.
2
Thanked by: ElMojo and Neil_28ElMojoI have tried to avoid being savage about this. But you leave me no choice. This is the second time I have been left having to find a work around for weeks. The first was on EzKeys and the expression pedal issue. When support tried to convince me it was just me. As it turned out I was right and it got fixed. But I had to work with it for weeks until Olof finally tried it out for himself. He then tried the same tactic of saying I hadn’t reported it properly as he has again on my thread. On another thread as again this time he eventually said this is a bad bug. Really! I had being saying this for weeks. How can an issues (two) really bad bugs get through testing on Cubase 11 and 12. What are you developing the system on and why are problems based on regression testing getting missed. I buy a product learn and set it up. I don’t expect to go back to a recording and find it doesn’t work because of poor testing. I have spent a fair amount of money with Toontrack and now find gaping holes in their development process. Just give me something that starts when it should and I can forget about. If it turns out that this is down to Windows messages getting lost on the Nag Screen I will be very, very annoyed! This is the second time your regression testing has completely failed on a very serious issue. I left Pro Tools Ultimate you would be a walk in the park.
No products in the cart.