NYC Composer
Senior Member
Actually just kidding, but clearly, you CAN remove quantize. I understand how it’s not perfect for your workflow.
Why did you leave Cubase?
- Thread starter Pier
- Start date
jononotbono
Luke Johnson
WTF are you all talking about? 
NYC Composer
Senior Member
Quantizing and removing quantization?
Per Boysen
Active Member
I'm actually trying to get back into Cubase now because I want to use my Seaboard with MPE, Divisimate, my breath control, and my EWI in all projects. That is not possible in my favorite DAW Bitwig, because of its limitation to only 512 note input channels. I have done a lot of work in Logic (2.0 to 10.x), Reaper, Live, and S1, but for the mentioned setup Cubase seems to be the best tool (I love Logic too, but my Macs are too old now).
Unfortunately, there is a highly annoying thing going on now in Cubase; if I hit STOP, click on the timeline, or unmute a muted track, Cubase sends out a high G# MIDI note through all MIDI port's channels... and with a VEP server based orchestra that comes back as a massive BANG through the audio system. It's so bizarre that I don't know if I want to laugh or cry
Almost one day is now spent on cruising the internet and the manual looking for a possible explanation and fix to this in Cubase. Any ideas?
I think DivisiMate with Loopback tracks is a nice workflow also in S1, but I really want full MPE compliance (as a newborn Seaboard lover). So that makes me dream about Bitwig fixing the note stream input limitations since that DAW is my absolute favorite with MPE. I also like to keep Bitwigs 2nd sequencer open on the side loaded with MIDI clips for all key-switches; if you keep that window neatly organized like a spreadsheet, you get the option to fire off compatible articulation switches in all instrument groups you are currently playing/recording utilizing DivisMate (by triggering the entire scene rather than just one instrument's KS clip). THAT is something I am missing in all other DAWs! This morning I fiddled with deleting two more divisi mate channels to make room for plugging in the TEControl, it worked like a charm, but I would of course prefer having 32 DivisiMate channels rather than 28 :-(
Unfortunately, there is a highly annoying thing going on now in Cubase; if I hit STOP, click on the timeline, or unmute a muted track, Cubase sends out a high G# MIDI note through all MIDI port's channels... and with a VEP server based orchestra that comes back as a massive BANG through the audio system. It's so bizarre that I don't know if I want to laugh or cry
Almost one day is now spent on cruising the internet and the manual looking for a possible explanation and fix to this in Cubase. Any ideas? I think DivisiMate with Loopback tracks is a nice workflow also in S1, but I really want full MPE compliance (as a newborn Seaboard lover). So that makes me dream about Bitwig fixing the note stream input limitations since that DAW is my absolute favorite with MPE. I also like to keep Bitwigs 2nd sequencer open on the side loaded with MIDI clips for all key-switches; if you keep that window neatly organized like a spreadsheet, you get the option to fire off compatible articulation switches in all instrument groups you are currently playing/recording utilizing DivisMate (by triggering the entire scene rather than just one instrument's KS clip). THAT is something I am missing in all other DAWs! This morning I fiddled with deleting two more divisi mate channels to make room for plugging in the TEControl, it worked like a charm, but I would of course prefer having 32 DivisiMate channels rather than 28 :-(
I tried Cubase rigorously for a month and gave up in disgust. When I encountered an issue, I would search online for an answer and I found forum posts going back DECADES complaining about the same problems/bugs.
It takes a seriously messed up corporate philosophy to ignore problems for 20 years or more!
I've been happily using Studio One for 6 months now and loving it. As a newer DAW, it wasn't encumbered by previous versions like Cubase -- which is so bloated and inelegant. (I moved over from Logic because of all the bugs and crashes.)
It takes a seriously messed up corporate philosophy to ignore problems for 20 years or more!
I've been happily using Studio One for 6 months now and loving it. As a newer DAW, it wasn't encumbered by previous versions like Cubase -- which is so bloated and inelegant. (I moved over from Logic because of all the bugs and crashes.)
Eulenauge66
Member
Well, I've been working with Studio One for months and returned to Cubase. Despite it being the less stable program.
The workflow on Cubase is for me faster and (in direct contrast to the previous post) more elegant. In Studio One I never achieved the same feeling of "flying" with the program.
Expression Maps in Cubase are better since the articulations are glued to the events. Sound Variations are cumbersome in several ways.
Cubase likes to crash (I think the main culprit is VEP), but Studio One as well. The latter crashed reproducably when changing the meter of a song. Although I must say, answers from support were quick and thorough.
Overall, I prefer the GUI of Cubase way more, and that's important to me since I have to stare at those programs all day.
But, like it was mentioned here so often: I think every DAW works and has also the same problems. One has to identify the third party plugin causing the problem and then look for a workaround.
The workflow on Cubase is for me faster and (in direct contrast to the previous post) more elegant. In Studio One I never achieved the same feeling of "flying" with the program.
Expression Maps in Cubase are better since the articulations are glued to the events. Sound Variations are cumbersome in several ways.
Cubase likes to crash (I think the main culprit is VEP), but Studio One as well. The latter crashed reproducably when changing the meter of a song. Although I must say, answers from support were quick and thorough.
Overall, I prefer the GUI of Cubase way more, and that's important to me since I have to stare at those programs all day.
But, like it was mentioned here so often: I think every DAW works and has also the same problems. One has to identify the third party plugin causing the problem and then look for a workaround.
dzilizzi
Senior Member
A bit of a problem if it is VEP. That said, I kind of wonder if the first DAW one becomes good at will always be the favorite. I like ProTools. I don't like their pricing. And Cubase has better midi tools. But I still end up going back to ProTools because I like the flow.
Obi-Wan Spaghetti
Senior Member
It was Cubase that left me. Cubase 12 didn't even want to start. I'm pretty sure it's their new authorization system that was the problem. It's an older Pc not powerful enough to make music on really so maybe that didn't help either. I'll try C12 again when i finally built my new DAW.
Eulenauge66
Member
A little advice regarding VEP: Cubase doesn't like in my case when I have the VEP PlugIn in a project, but the server is not running. It happens that at starting a project, Cubase is stuck in a loop looking for the VEP server. Since I have my Slave PC running all day, Cubase is super - stable.
Not sure I see the superiority of Cubase's expression maps over S1' s sound variations. What do you dislike about the later?
EgM
Game music!
Not a problem here in Studio One, as long as VEP server is running it will populate the plugin for the track. Sucks if Cubase can't handle this.
Eulenauge66
Member
With Expression Maps the articulations are glued to the event. I can move them and the articulations move with them. Also, I can play an event not only from the start, but also from the middle - with sound variations I’ve noticed that the last event is not being played at all.
Also, I change articulations while I’m playing. With sound variations a lot of missed or overwritten articulations happen and I needed to edit a lot afterwards.
Also, I change articulations while I’m playing. With sound variations a lot of missed or overwritten articulations happen and I needed to edit a lot afterwards.
Yes unfortunately sound variations are still direction based (also available in cubase) what’s still missing is attribute based articulations like it is available in cubase and Logic. This way an articulation stays attached to the notes.
Hopefully PreSonus will update this feature set including negative delay.
I believe enabling "Select Part Automation with Notes" is what you want to move events.
I'd have to test more, but I'd try to enable "Chase long notes" in Options / Advanced / MIDI for playing anywhere in an event.
ALittleNightMusic
Professional Amateur
I think my template is getting too big and Cubase just sucks up CPU even with nothing going on with that template loaded. I wish Cubase had a better track preset approach that saved routing and expression map settings. Then I would use the browser of presets to build up my template with just the needed tracks. So far only Studio One does this perfectly.
X-Bassist
Senior Member
I’m with you. Tryed Cubase for the midi but found too many things it doesn‘t do thats easy in Pro Tools.
And Protools hasn’t crashed for me in over a decade. It had crash issues 1992-1998 but steadily got more stable after they rewrote it for AAX. Which pissed many off at the time (an entirely new plugin standard) but it has been very stable since.
mjsalam
Active Member
Feel exactly the same. So frustrating.
