ElMojo
Blocked (Banned)
Topics Started: 6
Replies Created: 110
Has Thanked: 24
Been Thanked: 13
ElMojoFinally fixed. The release notes say that this issue has been fixed for Steinberg DAW software. I have read that one person had this issue on Cubase 9.5. I myself tested on Cubase 11 and 12 and both had the issue. The only conclusion I am left with. Is that those on here that said there was no problem on Cubase. Are actually lying or to stupid to see the problem. The bazaar instance of when I was accused of Anti-Semitism only makes it worse. Drumjack52 is full of nonsense and obviously trying to be an expert and look good. I would take what he says with a pinch of salt. The logo is another issue. I hate it but if Toontrack think it is good then good luck. Toontrack are not listening to their customers and think they know better. That is the road Avid have gone down and are now starting to suffer. They are now giving it away with Carbon.
ElMojoApart from the issues you have highlighted. Which are all true. Since SD3 version 3.3.2 the transport in Cubase is broken. When you press play. The drums do not start until you reach the location of the previous stop. The development team are saying this has nothing to do with the new splash/nag screen. They have said that the start location is not being stored correctly between plays. If that is the case you would have thought it would an easy fix. But no we have being waiting for the fix for weeks. No doubt they working on keeping the unwanted splash/nag screen and fixing the broken transport. So you can follow this whole circus of insanity on the threads below.
SD3 plugin (latest update) in Cubase – PLAY/MIXDOWN unstable
SD3 not always starting when play button is pressed in host DAW
I don’t think they understand what work flow is. Since finally admitting that there is a problem they have said nothing. Leaving us Cubase users with a broken and very annoying bug. Plus the fact the new splash screen gets in the way anyway.
ElMojodrumjack52: This is now a confirmed bug. It is not just me as many people have the issue across platforms. Plus the issue is in Cubase 9.5 all the up to 12.0.40. How you guys on this thread could say your system is working beats me. Here are the other two threads.
SD3 plugin (latest update) in Cubase – PLAY/MIXDOWN unstable
SD3 not always starting when play button is pressed in host DAW
So it is not my system and you saying it is my system has been very unhelpful! Look at the versions before you make sweeping statements like this.
ElMojoSo seven weeks on we still have no fix to the transport issues with SD3. I have heard it is not a issue with adding a stupid nag/splash screen. It is about how the start point for execution is not being stored correctly between subsequent plays. Does the splash screen go away yes it does. But the system is still screwed up. So what was the point of even asking that question? If it is just a problem with saving the current location of the next play point. It should have being an easy fix and we should now all be good and happy. But No! We have to wait for someone who missed the most obvious problem in the first place to get the splash screen and Cubase working so they don’t look bad. You do realise that your users are paying real money for your exercise in gross stupidity. Just fix this and we can all go back to mis-trust might be the issue here. WHAT ARE YOU THINKING AND DOING!
ElMojoAlso for the record. I don’t blame you ‘Neil_28’ for the delay. This should have been found in regression testing by Toontrack. Given that it wasn’t and mistakes do happen to the best. The bug is so obvious and fundamental. If they had bothered to try it they would have found it. I started this issue on the 1st July and it still has not been fixed. There are three threads on this issue including this one. The other two are:-
SD3 not always starting when play button is pressed in host DAW
ElMojoThe level of gross stupidity has reached amazing levels.
Above users Daron and Mark King are both on Windows 11 machines with Cubase 11/12 are are both reporting no issues.
Scott Sibley – Toontrack
Technical Advisor
What version were they using because nobody using Cubase 12 had a working transport system Then beyond all human belief. I then got accused of being Anti-Semitic. Because of an accidental spelling mistake. How the hell would I know if someone was Jewish or not. Toontrack have a major problem with regression testing. In that they do not do it. They charge top Doller and have a poor development team. FULL STOP! I am now using the latest version of Cubase which is 12.0.40. It still doesn’t work. It seems Olof thinks we are complete fools and any old crap will fend us off. This is a show stopper bug that could have been fixed weeks ago. If they had any respect for their users.
I started this on the 1st of July 2022 and still they are trying to prove me wrong. They need to look very closely at the development team and decide if they know what they are doing. I said back out the Logo/Nag screen weeks ago and get the system working for users. They decided to try and prove me wrong and get the Nag Screen working. I have only been developing software/firmware for over 37 years what do I know. This is simple back out what has broken the system until you figure out what is broken. But no we will prove you wrong! Here is the link to my first report of this horrific bug….Topic: Why! The logo. | Toontrack
ElMojoI 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.
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_28ElMojoYes it does. However, I was looking at it as different from all the previous versions. I was expecting a drum kit or mixer. That should have not caused the fact that it was not starting to get lost in the fog!
ElMojoOk! It seemed the most likely given that clicking on it got the SD3 plugin to at least start. That was the only change I could see.
ElMojoThank you Olof. This is the problem that I highlighted in ‘Why the logo’. So I will track the issue on this thread from here on in. Even after going in to the plugin and playing again it can still be a bit random. As mentioned above, it is most annoying when using export.
ElMojoThis issue is now going to be fixed!
It is difficult when you are being told there is no issue. After a process of elimination. It was obvious to me that this was problem with the update. Then having people tell me it was not a problem with the update is very annoying. I now know this problem only seems to happen in Cubase. Please do not be so quick to write off problems reported on here so quickly.
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_28ElMojoYour response says it all!
ElMojoYes you wrong were then and you are wrong now. It is simple you should not be a support person as you have no logic! You have based all your communications on systems that are not the same and are actually old. You even suggested that being on the cutting edge is the problem. Which is just plain wrong. Listen to your customers or lose them. This is the same problem as the other thread. It is simple SD3 has problems in Cubase 12. What the hell do you need to confirm it! You don’t even use our system you are taking it from third parties that still don’t use the same system. You should be sacked!
No products in the cart.