CUBASE SX 2 Problem

[TAD]

need help with a glitch. when playing back recorded midi files, they don't play back exactly where i recoreded them. they seem to be offset by 1/2 a beat. i have to then copy & paste the notes where i want them. and no i am not off beat. i play keys so my timing is tight. any suggestions?

[Bold Soul]

Sounds like midi latency. What MIDI interface and controller are you using?

[TAD]

my controller is a korg m1

[djyoavb]

same problem here

[TAD]

Originally posted by djyoavb:
same problem here i'm on the phone with someone trying to sort out the problem. i'll let you know what happens. thing is i'm not having this problem with reason.

[jerry santiago]

same here ive been goint to the midi edit list to put the notes on time.this is alot different for vst5.1.

[djyoavb]

the basic problem is that there's no sync betwin what u play and what u get, i tried to mess with the properties, sometimes i got latency sometime the notes came before time... graemlins/conf44.gif

[Bold Soul]

Is there an offset required?

I have to offset tracks by a set number of beats when sequencing Reason from Digital Performer. There may be something like this going on in Cubase.

[drilla]

im having the same problem...havent tried to fix it yet though..

please post any fix you may find...thanks!

[O'love]

try to *not* use the "emulated" midi ports...

check this out:

[b]MIDI port filter - Important note regarding MIDI Interfaces

Cubase SX has 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 both would show up. Since DirectMusic mirrors the Windows MIDI ports as "emulated" DirectMusic ports by itself, it would be possible that the MIDI ports show up even 3 times in the MIDI device list in Cubase SX. These multiple appearances of the MIDI ports are actually "multiple versions" of the same physical MIDI port.

To avoid this, Cubase SX 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 of Cubase SX may be the ones that actually do not work as the MIDI interface driver doesn't support the DirectMusic architecture the way Cubase SX 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 application folder (usually C:\programs\Steinberg\Cubase SX)
and locate the folder "MIDI Port Enabler"
- Open this folder
- Pick the file "ignoreportfilter" and move it into the Cubase SX application folder (one directory up)
- Start Cubase SX

Now all available MIDI ports provided by the MIDI interface driver will appear in the MIDI device list of Cubase SX - 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.

[ January 12, 2004, 11:29 AM: Message edited by: O'love ]

[drilla]

cool. thanks.

[altrrdst8]

SX2 is a problem itself, ive just reverted back to 1.xx

oh for my atari. im >< this far from buying a 1024

[jerry santiago]

im using sx2 with motu 2408 and a o2r board with two adat cards.im getting a digital pop every 2 seconds on my 2408 when using cubase only,i dont get it when using reason's or any other program.can anybody help me please.this shit is driving me crazzzzzzyy.

[TAD]

Originally posted by O'love:
try to *not* use the "emulated" midi ports...

check this out:

[b]MIDI port filter - Important note regarding MIDI Interfaces

Cubase SX has 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 both would show up. Since DirectMusic mirrors the Windows MIDI ports as "emulated" DirectMusic ports by itself, it would be possible that the MIDI ports show up even 3 times in the MIDI device list in Cubase SX. These multiple appearances of the MIDI ports are actually "multiple versions" of the same physical MIDI port.

To avoid this, Cubase SX 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 of Cubase SX may be the ones that actually do not work as the MIDI interface driver doesn't support the DirectMusic architecture the way Cubase SX 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 application folder (usually C:\programs\Steinberg\Cubase SX)
and locate the folder "MIDI Port Enabler"
- Open this folder
- Pick the file "ignoreportfilter" and move it into the Cubase SX application folder (one directory up)
- Start Cubase SX

Now all available MIDI ports provided by the MIDI interface driver will appear in the MIDI device list of Cubase SX - 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. i did this but now i'm getting even more latency.

[dennis f]

Phew...ok....this is a problem I had when I first went to 1.06...I've been at 2 and haven't had an issue...i'll explain....I was also getting the same latency issue you were but it had to do with the way I set up windows during a fresh install. You see with certain mother boards that have ACPI there have been some issues with SX not liking it. Therefore creating timing instabitlities and unexplained midi latency. If you happen to get this..well....the suggested cure is to reinstall windows xp as a standard config. If you go here they'll show you how to do it and more....www.musicxp.net When I did this it solved everything...like magic. Though you definitely still have to do the midi port enabler routine and get rid of all emulated ports. VIA equipped motherboards are notorious for problems like these. Hope this helps.....

peace
dee

[<NENA>]

Originally posted by jerry santiago:
same here ive been goint to the midi edit list to put the notes on time.this is alot different for vst5.1. smile.gif smile.gif :( graemlins/cussing.gif

[<NENA>]

Originally posted by jerry santiago:
same here ive been goint to the midi edit list to put the notes on time.this is alot different for vst5.1. smile.gif smile.gif :( graemlins/cussing.gif congrats on all your success

[<NENA>]

congrats on all your success graemlins/cheering.gif graemlins/cheering.gif graemlins/cheering.gif graemlins/snoopy.gif graemlins/OLA.gif graemlins/OLA.gif graemlins/OLA.gif

[drilla]

Originally posted by Cosmic T:
</font><blockquote>quote:</font><hr />Originally posted by O'love:
try to *not* use the "emulated" midi ports...

check this out:

[b]MIDI port filter - Important note regarding MIDI Interfaces

Cubase SX has 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 both would show up. Since DirectMusic mirrors the Windows MIDI ports as "emulated" DirectMusic ports by itself, it would be possible that the MIDI ports show up even 3 times in the MIDI device list in Cubase SX. These multiple appearances of the MIDI ports are actually "multiple versions" of the same physical MIDI port.

To avoid this, Cubase SX 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 of Cubase SX may be the ones that actually do not work as the MIDI interface driver doesn't support the DirectMusic architecture the way Cubase SX 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 application folder (usually C:\programs\Steinberg\Cubase SX)
and locate the folder "MIDI Port Enabler"
- Open this folder
- Pick the file "ignoreportfilter" and move it into the Cubase SX application folder (one directory up)
- Start Cubase SX

Now all available MIDI ports provided by the MIDI interface driver will appear in the MIDI device list of Cubase SX - 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. i did this but now i'm getting even more latency. </font>[/QUOTE]not to rub it in or anything but i did this and it did in fact work for me...i can play my keyboard and the notes are on time....there is not more latency in my setup.

thanks again for posting this...

sorry cosmic. :(

[DJ Keith Porter]

Thanks for this info.

I have been having this same problem and it makes making a track longer.

I will try these things and I hope some good magic happens because Im so tired of having to edit my key strokes all the way through the track.

I will get back to yall and let you know how it worked out for me.

Good luck everyone with this problem? graemlins/thumbsup.gif

[DJ Keith Porter]

Originally posted by DJ Keith Porter:
Thanks for this info.

I have been having this same problem and it makes making a track longer.

I will try these things and I hope some good magic happens because Im so tired of having to edit my key strokes all the way through the track.

I will get back to yall and let you know how it worked out for me.

Good luck everyone with this problem? graemlins/thumbsup.gif OMFG!

First I want to say thanks all of you here that contribute valuable information and ideas here in the producer’s corner. graemlins/acclaim.gif

I want express the steps I took to clear up this latency problem that I’ve been having in Cubase using samples / synths etc.

The advice and directions O’Love provided where simple and direct. I followed these steps and found that I still had the latency problem, which Cosmic T experienced after following the aforementioned procedure.

I then began to follow Denis F continued instructions only to come to a prompt halt!
Denis instructions were if after following O’love’s direction and you were still having the latency problem then the final step was to reinstall windows XP. Great no problem. I thought. Wrong! graemlins/nono.gif

Come to find out the XP had upgraded it’s self while being online over the period of time I had this OS. When I went to reinstall XP with the CD that I had it prompted me and said that the CD was an older version and it could not install. I was going crazy at this point. (Yes cursing and my monitor, keyboard, mouse and all other pieces I had connected to the PC.) mad1.gif

Using the brain that God gave me I decided to go to the “System Tools” and reset my PC to an earlier time. This was the smartest thing I could’ve thought of that day because like magic keystrokes played back in Cubase exactly how I played them while in record mode. I can explain how happy I was and now am that I finally fixed this long drawn out problem. graemlins/snoopy.gif

I can now make tracks a lot quicker by not having to edit keystrokes after every got-dam take. I feel liberated and free from tedious operations that were not necessary in the first place. graemlins/jpshakehead.gif

I hope for those of you that are still having this (latency) problem that the path that I took helps you. :D

Again, I thank everyone for their helpful information, Ideas, and sharing their art here in the producer corner, but most of all I want to thank Denis F and O’love for their superior expertise on this issue and their continuous will to share information that helps other people. hail.gif

Ok, Back to the Music.
Happen producing yall!

[ September 01, 2005, 12:41 PM: Message edited by: DJ Keith Porter ]