PlanetZ forums - scopeusers.com

I have AMD2000 mhz athlon processor.
Gigabite,mobo GA-7DXR+
amd.761.
cubase sx v3.+ scope+pulsar1.
Win xp.

MIDI timing problems, shifted notes, wrong MIDI events recorded occur.
Can anyone who has such EXPERIENCE help me with this problems.
I have try the MIDI Port Enabler & the other concept concern this midi probloms,non doe's not work.
cheers

Me too, tried evrything

My experience with this was due to wrong quantization or bad playing.
But I had some very subtle shifting during playback of tracks containing perfecly quantized notes with my previous PC.
With my actual system this seems go better.
(Or it's my nervous breakdown goin better )

<font size=-1>[ This Message was edited by: Cochise on 2005-06-17 11:12 ]</font>

Hi Cochise did you understood my post ? Im talking about unexpected midi event shifting !
cheers

In a little more detail, because it is starting to do my head in..!

When I first load Cubase, midi is sometimes fine. If I close a project and open a new one it seems to have got worse, phantom notes, random notes in the chord in the wrong place, double notes, usually at start.

Interestingly a Chord played before the count-in finishes will appear at the start of the recorded part, as if by magic.

If I reset midi in Cubase it sometime goes back to being ok.

It's not like a latency issue, it seems like there is midi activity seemingly having a mind of its own! I have tried everything and was wondering what it could be down to..

help

I hope you don't mind me hijacking the post okantah, but it seems we have the same problem??

Sorry, guys.
It don't happen here.

Hi guys below is the exact problems lm talking about!

MIDI timing issues when using emulated MIDI ports

Answer
MIDI port filter - Important note regarding MIDI Interfaces and Midi timing

On certain systems MIDI timing problems, shifted notes, wrong MIDI events recorded or similar MIDI related issues can occur when the default emulated Midi ports are used.

This is how to change the used MIDI ports to a more compatible solution.

Cubase SX (since 1.02)/SL/SE and Nuendo 2 (since 2.01) have a function to filter out redundant MIDI ports provided by the MIDI interface driver. For instance if the MIDI interface driver installs both Windows MIDI ports and DirectMusic ports, these ports used to both show up. Since DirectMusic mirrors the Windows MIDI ports as "emulated" DirectMusic ports by itself, it was possible that the MIDI ports showed up even 3 times in the MIDI device list. These multiple appearances of the MIDI ports were actually "multiple versions" of the same physical MIDI port.

To avoid this, the application provides an option to remove these redundant entries utilizing the MIDI port filter. However, in some cases the non-filtered, left over MIDI ports that will show up in the MIDI device list can be the ones that actually do not work as the MIDI interface driver doesn't support the DirectMusic architecture as Cubase SX/SL/SE and Nuendo would expect.

These cases were for example found with the following MIDI Interfaces:
- MIDIMAN MIDIsport 8x8
- MOTU MIDITimepieceAV
- Emagic MIDI interfaces

In this case, you can re-enable the filtered MIDI ports by proceeding as follows:

- Browse to the Cubase SX/SL/SE or Nuendo application folder (usually C:programssteinberg...)and locate the folder "MIDI Port Enabler"
- Open this folder
- Pick the file "ignoreportfilter" and move it into the application folder (one directory up)
- Start Cubase SX/SL/SE or Nuendo 2

Now all available MIDI ports provided by the MIDI interface driver will appear in the MIDI device list - the non emulated Windows MIDI ports as well. Please be aware that the MIDI ports now can show up 2 or 3 times in the list. If you're used to manage your MIDI IN by setting "All MIDI Inputs" in
the MIDI IN selector, you should go to the Device Setup/All MIDI Inputs and disable the unwanted ports. Otherwise you will record MIDI from multiple ports which results in double MIDI notes.

The non emulated MIDI ports might provide a far better timing than the emulated DirectMusic ones.

Since Cubase SX/SL 2.2 and Nuendo 2.2 another additional option is available.
In Devices -> Device Setup -> DirectMusic you can find the option "use system timestamp"

This option basically uses a different time as the timing reference. So instead of using the older non-emulated Windows MIDI ports checking this option might also improve the timing depending on the system and the components used.

Some additional background:

The physical MIDI port of the interface can be supported by one of three
different driver models:
(1) "Old" NT4 Kernel mode driver
(2) WDM Model driver
(3) WDM Streaming Model driver "real DM", used by our Steinberg Midex devices
It depends on the MIDI interface manufacturer, which drivers they deliver.

If DirectX 8 or higher is installed in the system (Win XP includes DX 8.1), drivers (1) and (2) can be adopted by emulating the MIDI ports.
So if a device has these sorts of drivers, Cubase/Nuendo will find the original and the emulated ports.
The result is that a note coming in on one physical input is delivered via two "drivers" and thus two apparent MIDI ports at once.
By disabling the emulated ports, only the original input will be regarded.

In case (3) a driver supports two sorts of ACCESS METHODS.

I've tried everything concerning Ignore port filter etc. I am only using creamware midi in/out not emulated ports. Has anyone any idea why if I play midi before cubase in the count-in starts recording it show up in the recorded part, surely this is very strange..I never used to have this problem??

I had found SOLUTION,it's certainly hardware problem.
One can imagine Im busy fighting this (mobo)problems from dec.2004
It's very strang that win xp cannot work with old mobo for music production.
Im yet to discover exact reason.............................

Barry if you have the same problems like the one i had,change your mother board,

I have a new mobo Intel D865 Perl

I still can't understand why notes played during the click count-in before cubase starts recording all jump to the start of the 1st bar of the recorded part.

For me whatever is causing this must be the source of the problem of timing and duplicate notes I am having, but I can't think of a reason why this happens...

If anyone has any idea at all I would love to hear.

the 'count-in' part isn't record time yet (it's before), so anything captured in the buffers is moved to the first valid time position.
While it makes no sense with your 'accidental' notes, it's important for sysex stuff which could be applied during the count in phase.
at least that's my guess... btw you don't have to waste creative energy to understand this - it just happens, is predictable and doesn't harm

cheers, Tom

<font size=-1>[ This Message was edited by: astroman on 2005-06-18 05:34 ]</font>

I am sure i remember reading something on the Steinberg site in some release notes for Cubase SX updates regarding fixes of some MIDI (timing) problems....

Just to tick all the boxes, i ask....

Have you obtained and installed the latest updates for the version of Cubase SX that you are using?

<font size=-1>[ This Message was edited by: deejaysly on 2005-06-20 03:18 ]</font>

Done all that, I can only assume now that it is not cubase related, but something to do with my midi setup. I have ordered some new midi cables to see if that helps. Either that or it could be my controller keyboard..Oh well

I'm sorry to come back to this but I am almost starting to cry it's been going on so long with no solution and is so disrupting. I used to have rock solid midi timing, no probelms at all, bang on. I also used to be able to play what I liked during a count in without it showing up in the actual recorded part. I understand that other sysex date may be registered in the count in but recording of note on/off data always used to only start at the start of the bar.

I have just sat and recorded a midi drum part through an external drum machine, simple bass kick and high hat bang on with the metronome and the result is that notes are all over the place.

Is there anyhing I could have missed, at a guess it seems to me like my midi drivers are messed up, that what I play on my keyboard is being interrupted in some way and throwing it off time. Also this is an intermittent problem, sometime seems ok sometimes not.

I've noticed that the total input latency in ASIO settings in cubase is 7.279ms and output latency 13.084ms, could this be the cause, is this in any way related to midi data.

As I said midi used to be perfect, audio was my my main problem with odd clicks & pops but never midi, now it is all over the shop! If anyone has any idea please let me know. It all seems to have started since I upgraded my mobo (Intel D865PERL) so perhaps there is a setting there I have missed, or a conflict.

Any advice would be welcome as I have hit a brick wall and not made any music for months

Another point is that a restart of Cubase ususally fixes at least the timing problem for a while, notes played in the count in still magically appear at the start of the bar (never used too!) but the timing gradually gets worse and worse, until I restart again.

format and reinstall. something is corrupt. i use cubase all the time without these extreme timing errors.

I agree and did this last night, I completely re-formatted, only intstalled scope and cubase. Recorded a part and no difference.

I have no idea anymore, could it be hardware related, is there any chance that the midi on the Pulsar board has gone astray?

really doubtful that it's broken(slight chance). if it works at all....
is it possible you have some kind of feedback loop going?

have you turned all the eyecandy off in xp(sliding and animated icons,toolbars etc)?
how about motherboard drivers(don't mean to be insulting, just clutching at straws)?

another possibility is that the new motherboard is bad. SOMEONE is going to get it even if the company only makes one bad one EVER. i have seen so many bad motherboards(not that model, but like i said, there's gotta be at least one, sometime), that i wouldn't find that impossible to believe......

how about dirty contacts on the card? perhaps you accidentally touched them when you switched mobos, try cleaning with 99% or purer alcohol, or at least try reseating the card.

is the whip and it's connector in good shape? try wiggling(gently) it and see if errors happen. try reseating it.

strange, but it must be fixable....

fwiw-the cubase latency report is pretty meaningless, except to tell you that you chose 7ms in your ulli settings....

<font size=-1>[ This Message was edited by: garyb on 2005-06-30 09:51 ]</font>

Will try cleaning the contacts..it's quite an old card and has been in and out of a few PC's. What exactly am I cleaning, the contacts where the card connect to the mobo, or the ones on the edge of the cad, or both..? Think the mobo might be ok as it runs fine otherwise.