You’re mixing up something and that is MIDI and audio. Cubase transmits MIDI data to the instrument (I say MIDI even though with VST3 it is converted MIDI data). The plugin outputs audio streams.
Cubase, as the host, has no idea what is the relationship between the MIDI data and the audio data. This is totally up to the plugin.
You can be mad at this shortcoming and you are even addressing the correct company - but as far as I can see it we would need a change in the VST3 specification rather than in Cubase only. Then this change would need to be supported by both the host and the plugin.
No matter which solution Steinberg chooses to adapt, some customers will be unhappy with it. The current solution puts you on the unhappy side.
In your own words: Too bad for you
my manner was joking, but it pointed to something that I think is obvious.
You have a midi track assigned to instrument “x”, with a midi channel “Y”, assigned to output “Z”…
if you SOLO that track it works, right?
You’re not telling me "well, how does Cubase know which Instrument/Midi/Output channel you want to hear in Solo, the path is difficult or impossible to follow…
He just does it.
I expect that if I select a MIDI block and want to render it Cubase will render that Midi block. How to do it is a problem that for obvious reasons I cannot solve.
But if it’s just me who sees the usefulness and necessity of a function that works in this way you can easily call me an idiot
This thing drives me crazy.
So, how would you feel if they told you that your water will be turned off tomorrow because a neighbor inadvertently left the tap running and flooded his apartment?
Since some users may be distracted, we cut off everyone’s water… you can obviously wash anyway, just go to the nearest fountain, at the end of the street!
Make the same reasoning with the gas, with the electricity… since a user went out leaving the electricity/gas on…
Do it with cars, do it with words, because it might offend, do it with your hands, because they might hit…
The function of a software is to provide a service as long as the user puts the software in the correct conditions to work well.
If I’m wrong, according to your logic, please remove the ability to use the space bar for start and stop, because inadvertently some user accidentally touched it while putting down his coffee cup at 3:00 PM it made him jump. the family sending cubase to play…
while you’re at it, remove the possibility of recording, because some users don’t empty the unused files from the Pool folder and have filled up their hard disk…
cubase knows which instrument output I selected in the inspector… this is the condition that many distracted users do not set correctly.
in my request, if I make a mistake setting the instrument output in the inspector I get an empty track, currently I get 16!! if you have an orchestral model it means that for 50 tracks on the sequencer you get 800 render tracks…
I wonder why users would be unhappy with the fact that render in place ONLY renders selected events. really, I would like someone to clarify to me the usefulness of the current way of working of rendering in place
Incorrect. When you create a multichannel instrument track, you enable the AUDIO CHANNELS IN CUBASE. NOT THE PLUGIN.
Oh and by the way, I’ve been using MIDI for over 25 years. Please don’t assume I’m getting ‘MIDI and audio confused’. I’m pretty sure I know this stuff at a much deeper technical level than you. You can stop talking as well.
Is there anyone around here who knows what they’re talking about? Ugh. I’m done with this thread. Thanks for nothing everyone.
First of all - I never said that you guys have an unreasonable feature wish. I merely pointed out the way to do export single outputs right now and that really good = user friendly solution would probably take more than an update of Cubase but also a new VST3 version and updated plugins.
However, if somebody doesn’t get a concept right I will reply to that.
Like this one:
That is just not the way it works. Only the plugin can create audio channels, that are inside itself. Cubase just provides the user interface part. Cubase will also create a connection to its mixer for every audio output that the plugin creates, so that the signal has a place to go to.
An easy option for Cubase developers would be to check if a generated audio track is empty (are they?), and delete it automatically (maybe with a warning message saying “Some tracks were empty and therefore not generated”). Maybe this can also be done using PLE…
