This is interesting, I'm using a Midisport 8X8 and have been having no end of problems with MIDI since I've started using it. For instance, the notes are shifted in time (by the same amount) when I record any MIDI. In the future I'm going to just hook a keyboard directly into the scope card when I want to record MIDI. The MidiEx 8X8 works fine for live performances, but for PC synchronization it doesn't seem to work properly (and that was supposed to be one of its selling points). I don't think it's related to the Creamware card (unless it can affect the totally separate drivers for the Midisport).
I also have had the same problems with not being able to quantize, the notes are out of position, I hit Q and it doesnt quantize. WTF?
SX3 - MIDI latency problem
-
Liquid Len
- Posts: 652
- Joined: Tue Dec 09, 2003 4:00 pm
- Location: Home By The Sea
In some cases, though, the emulated ports are in fact better. There's a lot of information about the windows midi vs direct music ports here:
http://www.jay.fm/blog/pc-midi-timing-and-nuendo.html
Then, quantisation works fine on my system. So, what you want to check is that you haven't got any notes selected or, alternatively, all notes are selected, before pressing q (better yet, go to the Midi menu and select Over Quantise. Check also that your grid setting is on (it's that drop menu immediately after all the tool buttons at the top of the project screen).
http://www.jay.fm/blog/pc-midi-timing-and-nuendo.html
Then, quantisation works fine on my system. So, what you want to check is that you haven't got any notes selected or, alternatively, all notes are selected, before pressing q (better yet, go to the Midi menu and select Over Quantise. Check also that your grid setting is on (it's that drop menu immediately after all the tool buttons at the top of the project screen).
-
Bracelet Z
- Posts: 82
- Joined: Sat Jan 24, 2004 4:00 pm
- Contact:
Hello again.
Sorry. Ones more:) Do You guys use VST freeze? Is it worth to use. You know, I would almost like to buy SX3 because of VST freeze function, to save CPU. Because I'm already tired of making a new audio files after putting a "hungry" vst:)
Thank You very much.
And maybe tell me more motivating things, why I should change my SX2 to SX3. I use XTC mode. And for MIDI I connect my old YAMAHA PSR 630 (ha ha) to Pulsar 2 MIDI.
I would really appreciate.
Sincerely,
Bracelet Z
Sorry. Ones more:) Do You guys use VST freeze? Is it worth to use. You know, I would almost like to buy SX3 because of VST freeze function, to save CPU. Because I'm already tired of making a new audio files after putting a "hungry" vst:)
Thank You very much.
And maybe tell me more motivating things, why I should change my SX2 to SX3. I use XTC mode. And for MIDI I connect my old YAMAHA PSR 630 (ha ha) to Pulsar 2 MIDI.
I would really appreciate.
Sincerely,
Bracelet Z
This is definitely an SX3 bug. See here:
http://forum.cubase.net/phpbb2/viewtopic.php?t=3266
http://forum.cubase.net/phpbb2/viewtopic.php?t=3266
-
Basic Pitch
- Posts: 627
- Joined: Fri Aug 15, 2003 4:00 pm
Hi all,
Im running Nuendo3 with a Midex8 and have zero issues, Intell P4 3.2c, Intex D875PBZ, Scope Pro, UAD-1, TC Powercore PCI.
Everything runs amazingly well consider allthe DSP cards in the box, but here is a link to when I first got my scope card and had massive midi issues, it may be of some help.
This was my 1st thread rarding midi timing issues, it has 2 pages of info: http://www.planetz.com/forums/viewtopic ... 28&forum=5
But the motherload and I believe the resolve for me was found here in these 4 pages of info: http://www.planetz.com/forums/viewtopic ... 22&forum=5
Hope this helps your issues, I know the gang here helped me greatly and their is ALOT of very good info regarding midi and CW with Steinberg products, though one hting to note, this is pree SX3/Nuendo3, but it still could prove quite usefull for you.
Cheers!
Im running Nuendo3 with a Midex8 and have zero issues, Intell P4 3.2c, Intex D875PBZ, Scope Pro, UAD-1, TC Powercore PCI.
Everything runs amazingly well consider allthe DSP cards in the box, but here is a link to when I first got my scope card and had massive midi issues, it may be of some help.
This was my 1st thread rarding midi timing issues, it has 2 pages of info: http://www.planetz.com/forums/viewtopic ... 28&forum=5
But the motherload and I believe the resolve for me was found here in these 4 pages of info: http://www.planetz.com/forums/viewtopic ... 22&forum=5
Hope this helps your issues, I know the gang here helped me greatly and their is ALOT of very good info regarding midi and CW with Steinberg products, though one hting to note, this is pree SX3/Nuendo3, but it still could prove quite usefull for you.
Cheers!
-
Basic Pitch
- Posts: 627
- Joined: Fri Aug 15, 2003 4:00 pm
I almost forgot to mention a couple minor things that may help.
Do NOT use the ignoreport filter with cubase even though some say it may help, in SFP do not use the sequencer midi option instead send a direct midi cable out of your midex8 to the input of your Scope card and the the Direct Midi A or what ever its called (sorry not at the PC at the moment and its been a while since I have bothered with it since it all works very well).
These were some key things me and CW had come to conclusions with, also to note when I had used my AMD processor with my setup I found the ONLY way to cure my midi issue was to use a standard PC instalation, with my Intel I can use APCI mode and everything is perfect but the AMD was touchy ashell and doing standard install made everything tight as you would expect it to be.
Read the 2nd link carefully, that has the real info in it, I had 2 CW cards over 2 periods of time since I got rid of the 1st one and ended up keeping the 2nd one. Scary thing is these days I couldnt even imagine how I worked with music before having my Scope card lol.
Cheers!
Do NOT use the ignoreport filter with cubase even though some say it may help, in SFP do not use the sequencer midi option instead send a direct midi cable out of your midex8 to the input of your Scope card and the the Direct Midi A or what ever its called (sorry not at the PC at the moment and its been a while since I have bothered with it since it all works very well).
These were some key things me and CW had come to conclusions with, also to note when I had used my AMD processor with my setup I found the ONLY way to cure my midi issue was to use a standard PC instalation, with my Intel I can use APCI mode and everything is perfect but the AMD was touchy ashell and doing standard install made everything tight as you would expect it to be.
Read the 2nd link carefully, that has the real info in it, I had 2 CW cards over 2 periods of time since I got rid of the 1st one and ended up keeping the 2nd one. Scary thing is these days I couldnt even imagine how I worked with music before having my Scope card lol.
Cheers!
Basic Pitch -
Thanks very much to you for your detailed response and to everyone who has pitched in here and with your problem. This is a really great board - what did we do before the internet?
On my system, midi timing, aside from the latency, is not too bad with the biggest timing discrepancies in the sub 4ms range. I set out a fairly detailed test report here:
http://forum.cubase.net/phpbb2/viewtopi ... 5836#25836
The key thing I learned from my testing is that you have to start with a benchmark and the easiest way to do this is to create a midi loopback - record the output of one midi port into another. When you compare the recording with the original in a list editor, you will be able to see how much latency, delay, timing inconsistency, etc you have on your midi interface alone.
Then, record an external synth on one side of a stereo track and a sample accurate audio reference onto the other. They must be playing exactly the same (quantised) rhythm. Then you can see how much the recorded midi part deviates from the sample accurate audio part just be looking at the resulting wave. Since you already know what your basic interface performance looks like you can also find out what latency, jitter, etc there is on the particular instrument you recorded.
Thanks very much to you for your detailed response and to everyone who has pitched in here and with your problem. This is a really great board - what did we do before the internet?
On my system, midi timing, aside from the latency, is not too bad with the biggest timing discrepancies in the sub 4ms range. I set out a fairly detailed test report here:
http://forum.cubase.net/phpbb2/viewtopi ... 5836#25836
The key thing I learned from my testing is that you have to start with a benchmark and the easiest way to do this is to create a midi loopback - record the output of one midi port into another. When you compare the recording with the original in a list editor, you will be able to see how much latency, delay, timing inconsistency, etc you have on your midi interface alone.
Then, record an external synth on one side of a stereo track and a sample accurate audio reference onto the other. They must be playing exactly the same (quantised) rhythm. Then you can see how much the recorded midi part deviates from the sample accurate audio part just be looking at the resulting wave. Since you already know what your basic interface performance looks like you can also find out what latency, jitter, etc there is on the particular instrument you recorded.
I have reported midi-timing problems to the nuendo and sx-forum. in nuendo I am playing in time with the audio click (no vsti's involved) - but nuendo records the midi events 1/16th too early as far as I can see it in the midi editor.
with SX things are even worse. midi is just NOT in time.
never had a midi problem with Nuendo 2.x or SX 2.x.
I use CW midi I/O of my pulsar 2 cards.
just my 2 cents. I can't believe that only few people having this problem. I will do some further testing ...
cheers
tom
with SX things are even worse. midi is just NOT in time.
never had a midi problem with Nuendo 2.x or SX 2.x.
I use CW midi I/O of my pulsar 2 cards.
just my 2 cents. I can't believe that only few people having this problem. I will do some further testing ...
cheers
tom
-
wernercarrasco
- Posts: 12
- Joined: Mon Aug 02, 2004 4:00 pm
Hi all,
I have just upgraded from sx 2 to 3.
i love all the new features, BUT, and it is getting to be a big one, MIDI start moving to the left as i program sequences. To the point that, after every take, I have to go intp the editor, and physically move the notes to their right place.
It starts off just a few milliseconds off, and after while, it has moved almost an entire bar. Restaring sx3 resolves the issue for a few minutes, and then the whole things keeps moving again.
My workaround?
I start Cubase sx 2, which is still installed, and..well..no MiDI problems at all!
Cubase sx 3, does also, seem to come with a few bugs that i cannot experience in cubasd 2. Programs changes, even loading some instruments are lost, at times, and i have to reload them. I can live with those things, but te MIDI issue, well, that's another story.
Any suggestions, anyone?
werner
I have just upgraded from sx 2 to 3.
i love all the new features, BUT, and it is getting to be a big one, MIDI start moving to the left as i program sequences. To the point that, after every take, I have to go intp the editor, and physically move the notes to their right place.
It starts off just a few milliseconds off, and after while, it has moved almost an entire bar. Restaring sx3 resolves the issue for a few minutes, and then the whole things keeps moving again.
My workaround?
I start Cubase sx 2, which is still installed, and..well..no MiDI problems at all!
Cubase sx 3, does also, seem to come with a few bugs that i cannot experience in cubasd 2. Programs changes, even loading some instruments are lost, at times, and i have to reload them. I can live with those things, but te MIDI issue, well, that's another story.
Any suggestions, anyone?
werner
Dude,
This is just basic latency issues. In your VST system setup pages there is a thing that shows your ASIO IN latency, mine is 7.3ms or so.
I don't use NEGATIVE latency on my external/asio devices, instead i use POSITIVE latency on my cubase/internal/VSTi devices. I set all of them at 7.5.
Does anyone know how cubase can compensate for latency automatically? I've not read into the manual about it yet because i'm not too worried about it.
This is just basic latency issues. In your VST system setup pages there is a thing that shows your ASIO IN latency, mine is 7.3ms or so.
I don't use NEGATIVE latency on my external/asio devices, instead i use POSITIVE latency on my cubase/internal/VSTi devices. I set all of them at 7.5.
Does anyone know how cubase can compensate for latency automatically? I've not read into the manual about it yet because i'm not too worried about it.
/**/ 8-Bit /**/
Liquid Mathematics
Liquid Mathematics
Hi. I have SX3 running no Win XP Home; 2.4 GHz PC, and a Pulsar II with Scope 4.0. I am suffering MIDI latency problems. I have been playing sounds in through a Midisport 4x4 using the serial connection rather than USB. The same setup works fine with my MOTU soundcard and M-Box but results in unplayable latency on the Pulsar. It is the same in Cubase and Logic, which suggests there may be an issue with the card.
I love the sounds I can get from this card but it seems so difficult to integrate into a home studio setup if you are using other gear as well.
If anyone has any hints or tips please do let me know where I might be going wrong.
I love the sounds I can get from this card but it seems so difficult to integrate into a home studio setup if you are using other gear as well.
If anyone has any hints or tips please do let me know where I might be going wrong.