nonlocal wrote:I am in the process of going through all my Cubase 7/7.5 projects and bouncing out all audio and midi so that I can remake them in a different DAW, and when I am done, I am going to sell Cubase, I have wasted too much of my life with this *flower* program.
matjones wrote:I just go and make a drink or have a quick vape for a few minutes and contemplate the earth going around the sun.......... and not me
nonlocal wrote:So I feel like doing some music for the first time in a couple of weeks, boot up Cubase and it has decided to scan EVERY SINGLE PLUGIN again.
I have a lot.
I am still waiting..............
And before anyone mentions time changes, it is irrelevant, it doesn't happen in any other DAW I have used, and Steinberg have had years to correct the issue.
This is a common thing with Cubase, random, pointless things happening at inconvenient times that just kill my will to make music.
In Live, I can get started faster and get ideas down much faster, but the mixing/ sound is not as good, so I prefer Cuabse overall, but it is so frustrating when Cubase freezes, blue screens (Yes in 2014!) and generally throws a spanner in the works.
Steinberg are so completely oblivious to how annoying it is when they don't fix simple issues of workflow.
Sort simple things out before adding more bells and whistles.
But I know this will never happen, as they are either negligent, or purposely making there product half finished so that everyone buys the next update in the hope it will be fixed..............
I am in the process of going through all my Cubase 7/7.5 projects and bouncing out all audio and midi so that I can remake them in a different DAW, and when I am done, I am going to sell Cubase, I have wasted too much of my life with this *flower* program.
My plugins have finally finished scanning, rant over...........
msy wrote:Clearly, you need help with your setup. Try a clean install of Cubase 64-bit on a fresh installed OS.
I have exactly 481 VST2 plugins and 92 VST3 plugins installed. It took exactly 3 minutes 4 seconds to re-scan everything today.
About blue screens: hardware, drivers or memory issues (out of memory within the 32bit limits) causes blue screens, not Cubase itself. I had blue screens while using the Virus TI hardware via USB with Cubase 32bit. The issue was the memory limit of the 32bit version of Cubase (as with all 32bit programs). I switched to 64bit and I haven't had a problem since.
If you think Ableton is better for your needs then go ahead, good luck!
so that I can remake them in a different DAW, and when I am done, I am going to sell Cubase, I have wasted too much of my life with this *flower* program.
estrica2000 wrote:I feel the same! i will wait for the next update and i will sell my cubase if it is not stable in day 9 april.
You mean, imposing your own absolute horribly devastating situation on another fellow human being?
Nice observation.silhouette wrote:Another DAW will give you different things to complain about and you will eventually build those faults into a deal breaker.
7.5 is slower than 5.5 and 6.5
nonlocal wrote:But it's over now, I can't take any more, I have seen through Steinbergs game after all these years, they will never get it right because then no one will upgrade.
good luck to you if it's working well for you though, but I think you are viewing things through rose tinted glasses.
7.5 is slower than 5.5 and 6.5
Users browsing this forum: Martin789 and 3 guests