cubase SL3 issue

[ugo]

im setting up cubase SL3 on my new computer and i've run into an odd issue that i've never seen before. whenever i record incoming midi (from my keyboard), all the notes are getting automatically quantized to the first beat of the first bar. i've even got auto quantize turned off, and even if it was on i believe i've got it properly set for 16th notes. but even on an 8 bar loop, all incoming notes are getting shoved back to the first beat of the first bar.

is there some setting i need to change to stop this from happening? has anyone ever heard of this problem? i've been using SL for years and i had never experianced this before.

edit: im also getting stuck notes in the sequence. one or two notes (usually just one) seem to be missing or lagging on the note-off.

[m@tte]

im setting up cubase SL3 on my new computer and i've run into an odd issue that i've never seen before. whenever i record incoming midi (from my keyboard), all the notes are getting automatically quantized to the first beat of the first bar. i've even got auto quantize turned off, and even if it was on i believe i've got it properly set for 16th notes. but even on an 8 bar loop, all incoming notes are getting shoved back to the first beat of the first bar.

is there some setting i need to change to stop this from happening? has anyone ever heard of this problem? i've been using SL for years and i had never experianced this before.

This sound similar to the classic midi timing issue. You need to enable "use system timestamp". It's a checkbox somewhere in the device setup area.

//m@tte

[loveless]

(This applies to SX, but I assume it is the same for SL as well) Are you using an emulated Midi port? For some reason moving the "portfilter" file from the "Midi Port Enabler" folder and dropping it into the Cubase folder fixed this problem for me - hope that helps

[ugo]

This sound similar to the classic midi timing issue. You need to enable "use system timestamp". It's a checkbox somewhere in the device setup area.

i havent found that setting yet. on the transport, the sync is set to internal though, if thats related at all.

(This applies to SX, but I assume it is the same for SL as well) Are you using an emulated Midi port? For some reason moving the "portfilter" file from the "Midi Port Enabler" folder and dropping it into the Cubase folder fixed this problem for me - hope that helps

emulated? at least not knowningly. (and not that i can see...where should i look?) my midi is coming in through something new though. im currently using the midi port on my presonus firebox, which i just got. on my old machine i was using an old motu midi express (parallel) which i havent hooked up yet, and the midi in on my old echo layla. (also not on this new machine, since it developed problems.)

in the midi section of the device setup, the presonus is listed and active and its also selected as the default input.

so far i've recorded midi through the firebox with no troubles using project5 and energyXT. i've been assuming its not a compatibility issue with cubase though since presonus actually packages cubase SE along with the firebox. (im using my own copy of SL3 though.)

however, i havent tried installing the old motu yet to see if the problem still occurs with that.

[m@tte]

This sound similar to the classic midi timing issue. You need to enable "use system timestamp". It's a checkbox somewhere in the device setup area.

i havent found that setting yet. on the transport, the sync is set to internal though, if thats related at all.

It's under Devices/Device Setup/MIDI/Windows MIDI. Only applicable if you use Windows though I guess Try it, worked for me...

//m@tte

[ugo]

It's under Devices/Device Setup/MIDI/Windows MIDI. Only applicable if you use Windows though I guess Try it, worked for me...

ah ha!
yes indeed, that fixed the problem. many thanks for the help, that was baffling me.

[m@tte]

It's under Devices/Device Setup/MIDI/Windows MIDI. Only applicable if you use Windows though I guess Try it, worked for me...

ah ha!
yes indeed, that fixed the problem. many thanks for the help, that was baffling me.

See? I told ya! Seriously though, this "feature" made me crazy before I found it. I tried EVERYTHING to get rid of the timing issues. Simple solution huh!?

Cheers

//m@tte