Cubase 10.0.20 released
- Thread starter AllanH
- Start date
Guy Rowland
Senior Member
And for those of us long suffering souls - after many years, CAN13024 is fixed! Multi out Track Archives and Disabled Tracks now work reliably.
Rob Elliott
Senior Member
Great news - thanks for the heads up.
EDIT: on large orch templates does 10 close without having to completely close it in the task mgr? (W7)
EDIT: on large orch templates does 10 close without having to completely close it in the task mgr? (W7)
Last edited:
jneebz
Senior Member
Link to Version History PDF:
https://download.steinberg.net/down...10/10.0.20/Cubase_10.0.20_Version_History.pdf
https://download.steinberg.net/down...10/10.0.20/Cubase_10.0.20_Version_History.pdf
benmrx
Senior Member
What the what?!?! You can confirm this is 100% reliable now? If so that's a HUGE deal!!!!
Another nice touch, and something that always irked me as missing (coming from PT) is this:
My only hope is that there's a command to 'reset' the waveforms back to their standard/default size. Hopefully all these new features make it into Nuendo 10..., cause I don't have Cubase anymore!!
jneebz
Senior Member
Thanks for all your work getting the Steinberg folks to take notice!
Guy Rowland
Senior Member
I've been using the 10.0.20 beta for quite a few weeks now. I've moved my VE Pro stuff to Racks, but still use Instrument multi-outs disabled in the projects for synths, beats etc. It's been rock solid for me, no issues at all. I did a bunch of stress tests initially and couldn't break it when creating new archives or disabled tracks, only existing ones sometimes caused a problem.
The only issue I have found is related but different, sometimes VST3 midi ports seem to get scrambled, all defaulting to port 1. I think this is another old bug, but I've always found it even harder to reproduce than CAN13042 - if anyone has any ideas, do flag them up! Truth is that this is now out of my workflow on Track Archives / Disabled Tracks so I likely won't be able to track this one down very easily on my own
(and thanks jneebz)
Emmanuel Rousseau
Senior Member
jaketanner
Senior Member
I am in desperate need of your help..lol. I am switching to Cubase 10, (have already), JUST for scoring work, and not mixing. SO I too come from PT, and it's mind boggling to me, that there are the simplest routing features missing. So what I want to do is simply record my VST instrument track, to a stereo audio track. I do not wish to render in place, or any other thing that's offline...I want to physically route the outs of one track to the ins of another just like we do in PT...it's like the simplest thing in the world. How does this not exist in a program so advanced for MIDI? Please...help. LOL
I did however, try the render in place, and it does not render the correct mixer volume I have the VST set to..I am pre-mixing my levels as MIDI, and want to simply transfer the MIDI to audio...also so I can further mix it and then export the mix with the video that I have scored...apparently, this TOO is missing from Cubase 10 Pro.
Thanks in advance!!
jaketanner
Senior Member
I just upgraded to 10.0.15 like 2 days ago...I do not see .20 out? Is it available today?
benmrx
Senior Member
Yeah..., Cubase is kinda wonky in this regard. I'm at work right now.. so only in front of PT, so bare with me as this comes from memory. You want to open your 'VST Connections' window (I think that's what it's called) and create a new path, almost as if you were going to create a new output for routing audio out of your interface, but instead of choosing any physical outputs, you just leave it blank (or maybe it gets set to 'none'). Then in Cubase you can route your VST out of that path, and then create a new audio track and set it's input to be that same path.
FWIW, as someone that works all day in PT every day, and only in Cubase for scoring/music/heavy MIDI work is that Cubase/Nuendo is NOT set up to be 'fast' right out of the gate. It's 100% dependent on you creating your own templates, quick keys, macros, etc. for tasks that are specific to your workflow. PT is like a tank..., everyones system is basically the same. Cubase/Nuendo is like a sports car that needs to be customized to your specific needs.
Tatu
Lannister
Spitfire's HZ Strings stopped working; Failed to load patch on all sections.
Anyone else having issues with either HZS, or other instruments ft. Spitfires player?
EDIT: Spitfire Audio app's repair -function got it back up and running!
EDIT2: Serious lag on both HZS's UI and Cubase introduced, when opening UI for HZS.
Anyone else having issues with either HZS, or other instruments ft. Spitfires player?
EDIT: Spitfire Audio app's repair -function got it back up and running!
EDIT2: Serious lag on both HZS's UI and Cubase introduced, when opening UI for HZS.
Last edited:
Markus Kohlprath
Senior Member
I do this via group tracks. It’s an unnecessary complication but you can set the input from audio tracks from every group track. I can print all my midi instruments via group tracks to audio tracks. But you have to route the output of the midi instrument to a group track and this one can be recorded by an audio track. Why it is not possible to record an instrument or rack midi output directly to an audio track is beyond me. Should certainly be possible and not a big deal to programm for the steinberg team.
If Guy hadn't put in the effort this wouldn't have happened guaranteed.
Sometimes it's how bad you want something, and in this case I think fellow beta testers had simply given up on this for whatever reasons. I remember reading one of Guys older posts in the Cubase public forum, then last summer restlessly testing a fix, and thought it was fixed for the release of C10. It turned out we were addressing similar but ultimately different problems...his much more deep. The fix wasn't even scheduled this soon so thanks Steinberg. Thanks to Guy and Kavinsky for clear step-by-step repros, and Guys perseverance.
Edit: The color issues have been improved. Also the option to give the color a name.
Michael Antrum
Only the good die young....
Had it crash four times on two different Macs whilst changing Fabfilter FX inserts to create thumbnails....
colony nofi
Senior Member
So others have given great responses as to how to do it in Nuendo. I personally do it using a group just because that used to be the old way of doing it. I've also been known to do it thru my sound card - though that's certainly not any easier (but works all the same!). Many ways to skin a cat and all that.
I guess a piece of advice I could offer is to be open to slightly different workflows to achieve the same thing. In many many cases things are different in cubase/nuendo vs protools but the outcome can be the same. Some are quicker in PT, others in cubase. I know a lot of time and effort is put in from the SB side of things to make things logically consistent to the paradigms of the program; this can be something that trips up PT guys but once you get your head around it, most things settle into workflows that feel ok.
However - I did want to ask about your render in place issue. There is no reason I can see as to why this isn't working for you. In Nuendo at least, there is a render in place menu that asks how you want the render in place to work. Ie : JUST the output from the VSTI, or using the channel settings (including channel volume / inserts etc) or using the entire signal chain including sends, groups, master channels etc. I'm wondering what use scenarios there are where this doesn't work? Could you provide a step by step repro on what you are doing / what the unexpected result is and I can try my best to point you in the right direction (or indeed maybe you've found a hole in the SB way of doing things.). I've delivered stems for a number of features using render in place without any issues at all, though this might be a very different use case to yours.
I personally do not see any difference in recording the output of a VSTi to an audio track and the current implementation of render in place other than workflow / keypresses. The results to me are identical. I figure I'm missing something.
jaketanner
Senior Member
Thank you for your reply. I have managed to send the VSTis to a group, then the group to an Audio channel to record internally. That worked, and it's not a big deal to set up really. Just wish that audio was passed through various different buses and sends as in PT...but no big deal, since I am not going to mix in Cubase really..it's just for composing and rendering the audio so that I can mix in PT, than bounce out with video.
As for the render in place...so I had it set to DRY, and apparently, it didn't recognize the mixer volume...once I set it to Channel settings, the volume and automation worked..the issue then became, that I got double automation. So it recorded the automation from the mixer, THEN, it gave me the same volume automation on the rendered audio...I had to then set it yet again to not separate, and used the "As one Event" option and I think it worked then.
I'll get used to it...Side note, I do love that I can create my own colors
shomynik
Active Member
Yeah, that's something wrong on your end as render in place shouldn't behave like that. Maybe try trashing prefs and try again? The DRY setting should transfer everything(plugs, automations, etc...), but with other options you should get your fader on 0, no automation transfer.
