stucking keys on midi
You will keep Sequencer out to synths (Seq. MIDI source--->Device), Cubase track will send to the synth what you are recording into it, while you record it and after when you playback.On 2005-10-30 09:39, ARCADIOS wrote:
alfonso, yoou suggest connecting directly from midi hardware to sequencer, without any merger and sequencer midi out to synths. but what about recording effects after a finished midi track?
When instead you are only using Scope to play a synth without using a sequencer you connect it directly....
Cubase has a through function, that's very convenient, because you can have a MIDI keyboard that transmit on channel 1 or whatever, if you connect it directly to Cubase (Card MIDI source--->Seq. MIDI destination, the notes you play will be send back to Scope synths from cubase only in the MIDI channel of the active track, so you just change MIDI track (and MIDI channel) and you automatically play only the synth that receives on that channel.
You have obviously to remember to assign a MIDI channel for every different synth you load in Scope.
at this point when you playback the song, you can assign all the effects you want, but you can have them assigned in any moment, also when you record, they are just in the Scope mixer, always affecting the sound from the synth, I don't understand the problem really.
Alfonso! i think i solved the problem.
i connect midi directly to sequencer and sequencer sends to synths. as many synths as dsps can hold. yes!!but midi channels in scope must be matched with midi channels in nuendo otherwise two or three midi channels sending signal at the same time cause system freeze. only one midi channel must be played or recorded at the time, and you turn on the synths you want to be heard from the monitor bottons. this way if you record one synth, the others do not give signal to scopes mixer, much better!!
and now i can tell you that i do not have stucks.
when i used merger it was difficult to understand why i had the stucks because sometimes i had just one midi channel that was ok, but when the channel was in playback and i recorded another midi channel there were midi signals from two sources, midi keyboard and sequencer. now it is all sent from sequencer.
and i must say that i need 2 midi filters. even if there is one on scope midi in, after all connections, sequencer when it sends midi from a recorded midi channel needs to be filtered as well.(i saw it with monitor for sure).
there was someday that i managed to change instruments from the midi cannels banks inside nuendo. do you know how?
and what about the midi selection of scope mixers? what do i need it for? what is the usage of midi in/out on the mixer (1632 for ex.)?
i hope it will not stuck again
i connect midi directly to sequencer and sequencer sends to synths. as many synths as dsps can hold. yes!!but midi channels in scope must be matched with midi channels in nuendo otherwise two or three midi channels sending signal at the same time cause system freeze. only one midi channel must be played or recorded at the time, and you turn on the synths you want to be heard from the monitor bottons. this way if you record one synth, the others do not give signal to scopes mixer, much better!!
and now i can tell you that i do not have stucks.
when i used merger it was difficult to understand why i had the stucks because sometimes i had just one midi channel that was ok, but when the channel was in playback and i recorded another midi channel there were midi signals from two sources, midi keyboard and sequencer. now it is all sent from sequencer.
and i must say that i need 2 midi filters. even if there is one on scope midi in, after all connections, sequencer when it sends midi from a recorded midi channel needs to be filtered as well.(i saw it with monitor for sure).
there was someday that i managed to change instruments from the midi cannels banks inside nuendo. do you know how?
and what about the midi selection of scope mixers? what do i need it for? what is the usage of midi in/out on the mixer (1632 for ex.)?
i hope it will not stuck again
Great!On 2005-10-30 15:21, ARCADIOS wrote:
Alfonso! i think i solved the problem.
....what about the midi selection of scope mixers? what do i need it for? what is the usage of midi in/out on the mixer (1632 for ex.)?
i hope it will not stuck again
I was sure of that!The mixer is just as any other device, give it a dedicated MIDI channel and connect it's MIDI input to the Sequencer MIDI source as well.
Then you can assign CC# to the faders and pots and automate them from a MIDI track in Cubase that sends on the same MIDI channel of the mixer.
Like every other device, each knob or fader gets a different MIDI CC#.
have you seen any difference on standard pc instead of acpi on midi stability?
when i first started using creamware cards i always installed on standard pc. in fact there was no need for midi filtering.
with acpi i use filters. is this the same according to stability or standard pc really works like a rock solid?
when i first started using creamware cards i always installed on standard pc. in fact there was no need for midi filtering.
with acpi i use filters. is this the same according to stability or standard pc really works like a rock solid?
I'm forced to use standard pc, because I have an old Tusl2c mobo with the 815e chipset and PIII-s, that has the old acpi scheme that's not good.On 2005-10-31 13:05, ARCADIOS wrote:
have you seen any difference on standard pc instead of acpi on midi stability?
when i first started using creamware cards i always installed on standard pc. in fact there was no need for midi filtering.
with acpi i use filters. is this the same according to stability or standard pc really works like a rock solid?
<font size=-1>[ This Message was edited by: alfonso on 2005-10-31 15:33 ]</font>
