Odd MIDI problem with Cubase SX3 & Scope Luna
-
- Posts: 204
- Joined: Sun Apr 22, 2007 5:07 pm
Odd MIDI problem with Cubase SX3 & Scope Luna
Hi,
I'm using Scope LunaII card with Cubase SX3. I have problem with timing of recorded midi tracks.
Cubase somehow moves back all recorded midi notes so during playback they play a slice earlier then recorded! In edit i can see that all of them began earlier than I have played.
I have done test with synchronising quantized M1 sequencer notes to Cubese SX3 – it is the same.
Beside this problem, I'm playing virtual instruments with 1ms latency without problem in Cubase SX.
Any idea on what could be wrong?
I'm using Scope LunaII card with Cubase SX3. I have problem with timing of recorded midi tracks.
Cubase somehow moves back all recorded midi notes so during playback they play a slice earlier then recorded! In edit i can see that all of them began earlier than I have played.
I have done test with synchronising quantized M1 sequencer notes to Cubese SX3 – it is the same.
Beside this problem, I'm playing virtual instruments with 1ms latency without problem in Cubase SX.
Any idea on what could be wrong?
go into asio mutimedia setup and run a buffer sync simulation,you might find they're out of sync.
good luck
rich
good luck
rich
Core2Quad Q9400 2.66Ghz, Asus P5Q EPU,Radeon HD4350 4Gb Ram,320Gb 7200Rpm,Windows 7 Pro 32 bit,Cubase 4+5,NI Komplete 5+6, Scope 5 - Mix&Master - Synth&Sampler,Pulsar II Classic - PulsarII XTC,.Core2duo 3.00Ghz.Presonus Firestudio Tascam FW1884
-
- Posts: 204
- Joined: Sun Apr 22, 2007 5:07 pm
Hi,
The problem is that when I open ASIO Dxfdsetup.exe and Wpsetup.exe in Steinberg folder, I can't run a buffer sync simulation. I'm getting following errors:
“Not all the selected devices in the current configuration were successfully started with their selected options. If this card (...)”
When I click on 'Check Buffers and Sync' I'm getting following:
“Errorcode: FF8-5-000C
Info: Device could not be opened”
Same thing when I click on 'Detect Buffer Size'.
Any idea how to solve this. That is the first problem.
I'm using ASIO Multimedia Setup v. 1.7.0.8
When I use Scopes card midi ports without straight WITHOUT 'use system timestamp' unchecked, the midi notes records a bit late with appr. 5-7. So instead of 0.0.0.0 it is recorded at 0.0.0.5.
When I use Scopes card midi ports without straight WITH 'use system timestamp' unchecked, the midi notes records a bit late with appr. 5-7. So instead of 0.0.0.0 it is recorded at 0.0.0.5.
Is it better to use Mdi devices as Emulated maybe?
I will appreciate any help.
The problem is that when I open ASIO Dxfdsetup.exe and Wpsetup.exe in Steinberg folder, I can't run a buffer sync simulation. I'm getting following errors:
“Not all the selected devices in the current configuration were successfully started with their selected options. If this card (...)”
When I click on 'Check Buffers and Sync' I'm getting following:
“Errorcode: FF8-5-000C
Info: Device could not be opened”
Same thing when I click on 'Detect Buffer Size'.
Any idea how to solve this. That is the first problem.
I'm using ASIO Multimedia Setup v. 1.7.0.8
When I use Scopes card midi ports without straight WITHOUT 'use system timestamp' unchecked, the midi notes records a bit late with appr. 5-7. So instead of 0.0.0.0 it is recorded at 0.0.0.5.
When I use Scopes card midi ports without straight WITH 'use system timestamp' unchecked, the midi notes records a bit late with appr. 5-7. So instead of 0.0.0.0 it is recorded at 0.0.0.5.
Is it better to use Mdi devices as Emulated maybe?
I will appreciate any help.
-
- Posts: 204
- Joined: Sun Apr 22, 2007 5:07 pm
-
- Posts: 204
- Joined: Sun Apr 22, 2007 5:07 pm
In your scope startup project, which asio and wave drivers are going into the mixer ,as the asio driver syncs off the wave driver buffer ?
Core2Quad Q9400 2.66Ghz, Asus P5Q EPU,Radeon HD4350 4Gb Ram,320Gb 7200Rpm,Windows 7 Pro 32 bit,Cubase 4+5,NI Komplete 5+6, Scope 5 - Mix&Master - Synth&Sampler,Pulsar II Classic - PulsarII XTC,.Core2duo 3.00Ghz.Presonus Firestudio Tascam FW1884
-
- Posts: 204
- Joined: Sun Apr 22, 2007 5:07 pm
Garyb:
- Yes now I can do a 'Check buffer and sync' but I can't do 'Run Simulation'. Test returns no problem for C-Media Wave Device.
On 'CreamWare Rec/Play 1' test I'm very often getting one synch lost – at the beginning of test. Error code: FE6-2-0700.
Just be sure: Which devices shall I check / uncheck in Wpsetup.exe and Dxfdsetup.exe for optimal performance?
H-Rave:
I'm not using Wave driver at all, just ASIO source into mixer and ASIO destination on the other side if mixer. When Windows start I have not add any start up project. Shall I do so?
I'm a bit confused now. Everything is working OK with ASIO in Cubase SX3, beside the midi part. Midi notes are recorded 5-7 measure units (25ms?) earlier.
Maybe If I use some external Midi interface (USB?) this problem will be fixed?
I will appreciate your help.
- Yes now I can do a 'Check buffer and sync' but I can't do 'Run Simulation'. Test returns no problem for C-Media Wave Device.
On 'CreamWare Rec/Play 1' test I'm very often getting one synch lost – at the beginning of test. Error code: FE6-2-0700.
Just be sure: Which devices shall I check / uncheck in Wpsetup.exe and Dxfdsetup.exe for optimal performance?
H-Rave:
I'm not using Wave driver at all, just ASIO source into mixer and ASIO destination on the other side if mixer. When Windows start I have not add any start up project. Shall I do so?
I'm a bit confused now. Everything is working OK with ASIO in Cubase SX3, beside the midi part. Midi notes are recorded 5-7 measure units (25ms?) earlier.
Maybe If I use some external Midi interface (USB?) this problem will be fixed?
I will appreciate your help.
- Attachments
-
- Asio files
- asio.jpg (27.03 KiB) Viewed 3927 times
-
- Asio setup
- asiosetup.jpg (84.59 KiB) Viewed 3929 times
-
- Cubase setup
- cubasesetup.jpg (36.29 KiB) Viewed 3929 times
-
- Posts: 204
- Joined: Sun Apr 22, 2007 5:07 pm
i think the wave modules must be connected to the mixer to run the test.
for the dx thing, go to start/run and enter dxdiag. you can experiment with dx acceleration on the audio tab and you can try disabling direct draw acceleration on the display tab(change one thing at a time, first). if this doesn't help, set everything back the way it was.....
for the dx thing, go to start/run and enter dxdiag. you can experiment with dx acceleration on the audio tab and you can try disabling direct draw acceleration on the display tab(change one thing at a time, first). if this doesn't help, set everything back the way it was.....
-
- Posts: 204
- Joined: Sun Apr 22, 2007 5:07 pm
what exactly did you test?
dxdiag is not for testing, it's for controilling the dx setup.
have you tested for midi latency by lowering dx acceleration and/or video acceleration?
possibly you might have better results with another midi interface, but i don't have any of your problems with any of my machines....
dxdiag is not for testing, it's for controilling the dx setup.
have you tested for midi latency by lowering dx acceleration and/or video acceleration?
possibly you might have better results with another midi interface, but i don't have any of your problems with any of my machines....
you need a wave source module connected into your mixer, and a wave dest module linked to the out , put them in(yes that's an order)otherwise the asio WON'T sync.Oh and dxdiag always says that.The wave source and dest are in software io's,don't go for 24 bit wave source.Oh and in your mixer turn them to stereo inputs as opposed to 2 monos panned L and R.And one last thing Dxdiag reads out of the windows registry(Run,Regedit(Look but don't touch))whether or not the hardware is there,it will appear,(I may stand corrected by another user).
Core2Quad Q9400 2.66Ghz, Asus P5Q EPU,Radeon HD4350 4Gb Ram,320Gb 7200Rpm,Windows 7 Pro 32 bit,Cubase 4+5,NI Komplete 5+6, Scope 5 - Mix&Master - Synth&Sampler,Pulsar II Classic - PulsarII XTC,.Core2duo 3.00Ghz.Presonus Firestudio Tascam FW1884
-
- Posts: 204
- Joined: Sun Apr 22, 2007 5:07 pm
- I have done per your instructions but I still can't check the C-Media Wave Device.
- In ASIO Multimedia setup panel, what shall I set as sync reference: 'C-Media Wave Device' or 'CreamWare Play/Rec 1'? Please tell me that.
Is there any tool that can actually check the really midi latency and return result as digits? In Cubase I can see the latency for Audio but not for MIDI.
I have disabled hardware acceleration for graphics. My midi notes are still recorded late or early.
The only thing I can check buffer for is 'CreamWare Play/Rec 1' in Input Ports panel.
I still can't run simulation because of some strange reason.
Any idea what I can check next?
I send over a screen so that you can see how midi are recorded despite the fact that it is done from another sequencer with sync clock from Cubase.
Maybe Cubase is messing around with midi data that comes in???
- In ASIO Multimedia setup panel, what shall I set as sync reference: 'C-Media Wave Device' or 'CreamWare Play/Rec 1'? Please tell me that.
Is there any tool that can actually check the really midi latency and return result as digits? In Cubase I can see the latency for Audio but not for MIDI.
I have disabled hardware acceleration for graphics. My midi notes are still recorded late or early.
The only thing I can check buffer for is 'CreamWare Play/Rec 1' in Input Ports panel.
I still can't run simulation because of some strange reason.
Any idea what I can check next?
I send over a screen so that you can see how midi are recorded despite the fact that it is done from another sequencer with sync clock from Cubase.
Maybe Cubase is messing around with midi data that comes in???
- Attachments
-
- connection.jpg (79.31 KiB) Viewed 3880 times
-
- cubaselatency.jpg (70.14 KiB) Viewed 3881 times
-
- latency.jpg (52.59 KiB) Viewed 3882 times
-
- Posts: 204
- Joined: Sun Apr 22, 2007 5:07 pm
it shouldn't be a concern, i never bothered about it.
The only thing that should bother is the latency you experience when playing 'life'.
13 ms is what you would expect these days.
Other timing problems shouldn't be related to 'latency', I'd say it's related to priority settings and the like, or even bugs.
I can remember this strange 'timing' problem was reported befor, but not on mac, so I don't know.
It just shouldn't be there, you have to tweak
The only thing that should bother is the latency you experience when playing 'life'.
13 ms is what you would expect these days.
Other timing problems shouldn't be related to 'latency', I'd say it's related to priority settings and the like, or even bugs.
I can remember this strange 'timing' problem was reported befor, but not on mac, so I don't know.
It just shouldn't be there, you have to tweak

-
- Posts: 204
- Joined: Sun Apr 22, 2007 5:07 pm