midex zooi
- Thread starter trash
- Start date
trash
Ouwe rot
- Lid sinds
- 24 juli 2002
- Berichten
- 4.564
Ok nieuwe dag
Fris begonnen,ff test gedaan,geen cubase aan,dus ff kijken hoe de midex zich verhoud.
Conclusie,blijft lopen.
Dus,dacht ik dan moet het wle aan cubase liggen,dus verse install.
Midex blijft nu al een hele tijd goed lopen.
Keep u posted
Fris begonnen,ff test gedaan,geen cubase aan,dus ff kijken hoe de midex zich verhoud.
Conclusie,blijft lopen.
Dus,dacht ik dan moet het wle aan cubase liggen,dus verse install.
Midex blijft nu al een hele tijd goed lopen.
Keep u posted
trash
Ouwe rot
- Lid sinds
- 24 juli 2002
- Berichten
- 4.564
Check dit ook eens:
Wel nuttig
PC MIDI Timing and Nuendo
Updated January 3, 2005 05:00 PM
Users of Steinberg’s Nuendo and Cubase often run into trouble with MIDI timing. I’m not affiliated with Steinberg, but I am a programmer, and I’ve done a lot of experimenting with MIDI timing on the PC. Here is, I hope, the definitive list of problems and workarounds. Note that I talk mostly about Nuendo here, but Nuendo and Cubase SX are the same application under the covers, and everything I write applies to both. The explanations are lengthy, but it’s a complicated topic, where many problems can cause the same system, and I think it’s important to understand the background; if you think I should provide a long and short version of this FAQ, leave a comment to that effect.
1. Emulated Ports
By far, the most common cause of MIDI timing problems is using emulated MIDI ports. Once upon a time, there was only one type of MIDI driver, known as Windows MIDI. Later on, Microsoft introduced a new driver type, DirectMusic, which could theoretically offer better timing, but due to some limitations, this was mostly taken advantage of by gaming cards, not pro-audio cards.
To encourage application developers to switch from Windows MIDI to DirectMusic, Windows provides “emulated” DirectMusic ports for all Windows MIDI drivers; as far as the application knows, it’s talking to a genuine DirectMusic driver, with Windows doing the translation under the covers. This means that an application like Nuendo can, in theory, be written solely to the DirectMusic interface, and if your card doesn’t actually support DirectMusic, Windows will cover for it.
The reality is more complicated; sometimes the emulated DirectMusic drivers don’t work at all, or only work in one direction. Sometimes the emulated ports don’t work but the original Windows MIDI ports do. Sometimes the timing is off on one port or the other. Sometimes there are actually both Windows MIDI and genuine DirectMusic drivers for a device. So if there is both a Windows MIDI and DirectMusic version of a port, Nuendo tries to guess which one is the right one, and it filters out the other. Sometimes—usually, in my experience—it guesses wrong, especially where emulated ports are involved. And on some systems, though certainly not all, the emulated ports have timing problems.
(By the way, these two driver types—driver APIs, really—have nothing to do with WDM vs. MME drivers. Those are driver models, and affect how a driver is built, not what API it uses. A WDM driver can be either Windows MIDI or DirectMusic, and I believe the same is true of MME. We don’t care about WDM vs. MME here.)
The fix
Nuendo keeps a zero-length file called ignoreportfilter in the directory C:\Program Files\Steinberg\Nuendo\MIDI Port Enabler. Using Windows Explorer, you can drag this file up one level to the Nuendo directory, restart Nuendo, and you will now see both the emulated and non-emulated ports. In my experience, you nearly always want the non-emulated ports; you should go into Device Setup and set “Show” to “No” for the emulated DirectMusic ports so that you don’t accidentally use them.
This will only solve your problem if yours is a system where the emulated ports have timing issues. On my system, they don’t.
2. The two-clock problem
All MIDI interfaces on Windows timestamp their data before providing it to the application. This avoids timing problems when the application doesn’t immediately see the incoming notes, perhaps due to higher-priority interrupts, or things chewing up CPU time, or simply a burst of notes too quick for the app to process. The app just looks at the timestamp, does a quick calculation, and poof: instant latency compensation for all MIDI. This has been part of the MIDI driver spec forever.
But Windows provides two different multimedia timers - specifically, one called timeGetTime, or TGT, and one called QueryPerformanceCounter, or QPC. The QPC timer is more precise (although the actual precision is up to the motherboard), and often more accurate, but it’s only available on newer versions of Windows, and there were some motherboards a while back that had major inaccuracies with it, and some current dual-CPU boards still don’t keep the two CPUs in sync.
So drivers, especially Windows MIDI drivers, that descend from older code, or have to work on older OS’s, or that are simply more cautious, are likely to use TGT, which is what Nuendo normally uses; the VST and ASIO specs are based on TGT. Newer drivers, especially those written under DirectMusic, are likely to use QPC. Since the two end up out of sync on most PCs, you’ll end up with timing problems in Nuendo if your MIDI driver uses QPC.
This problem is likely to affect any sequencer, not just Nuendo - although some sequencers might be based around QPC instead of TGT, and thus they’ll have problems with exactly the interfaces that work fine on Nuendo and vice versa. Sonar does have a hidden option that lets you ignore ALL timestamping from the interface, which is fine unless Sonar can’t keep up with the interface, at which point you’ll have really sloppy timing on ANY interface.
The fix
Nuendo and Cubase 2.20 provide an option in the DirectMusic settings called “Use system timestamp”. This tells Nuendo that for MIDI tracks, they should keep track of time using QPC, not TGT. This affects only DirectMusic drivers. That means that if you have a Windows MIDI driver that uses QPC, you’ll have to use the emulated DirectMusic drivers, which is the exact opposite of what is normally recommended! Hopefully future versions will offer this option in both DirectMusic and Windows MIDI flavors. Meanwhile, hopefully your system isn’t one of those that has timing problems on the emulated ports. My system, an Asus P4C800-E, doesn’t, but certainly some do. A future version of MIDITime will test DirectMusic emulated ports as well, so you’ll know exactly what you’re up against.
The test
If you want to be certain that this is the problem you’re having, and help out the user community at the same time, you can download my MIDITime Utility. You take a cable from a MIDI output port to a MIDI input port, and run the utility until your clocks get out of sync; it then tells you which clock is correct, and thus what setting to use. Simple and definitive.
And please, if you run the utility, and your interface isn’t already listed below, e-mail me the results so I can share them! (I’d prefer that you not leave them as comments, so others don’t have to wade through the details.) The utility can take up to an hour to run (it waits that long to decide that your clocks are staying in sync), but more often takes about 5 minutes.
If there are any Windows programmers out there interested in slapping a simple GUI on this app, drop me a line. I never bothered to learn MFC, and with Windows.Forms and .NET coming of age, it’s not really worth it now.
The results
The following MIDI interfaces will work best with the DirectMusic emulated ports and the “Use System Timestamp” option checked:
Echo Mia
Frontier Design Dakota
M-Audio Audiophile 2496
MOTU 828 MKII
MOTU Express XT
MOTU MTP-AV
Steinberg MIDEX-8
Yamaha SW1000XG
The following MIDI interfaces will work best with the native DirectMusic ports and the “Use System Timestamp” option checked:
Wami Rack-24
The following MIDI interfaces will work best with the “Use System Timestamp” option unchecked:
Aardvark LX6
Aardvark Q10
Edirol UMT-880
Emagic Unitor8 MK1
Emagic Unitor8 MK2
Emagic AMT-8
M-Audio MIDISport
RME Digiface
RME 9632
The following lucky motherboards have clocks that don’t drift, and so can use any interface with any setting:
Asus A7V333
Asus A7N8X-X
Asus P4D-800D
Asus P4T-533C
Asus TUSL2-C
3. Constrain Latency Compensation
One person has reported that using the Constrain Latency Compensation option—which should, in theory, affect only audio—also improved his MIDI timing. This has not been confirmed by other reports, but it’s certainly easy enough to try. If you find this setting to be helpful, please let me know.
Posted by Jay Levitt at May 15, 2004 12:55 AM | TrackBack (0)
bron
Wel nuttig
PC MIDI Timing and Nuendo
Updated January 3, 2005 05:00 PM
Users of Steinberg’s Nuendo and Cubase often run into trouble with MIDI timing. I’m not affiliated with Steinberg, but I am a programmer, and I’ve done a lot of experimenting with MIDI timing on the PC. Here is, I hope, the definitive list of problems and workarounds. Note that I talk mostly about Nuendo here, but Nuendo and Cubase SX are the same application under the covers, and everything I write applies to both. The explanations are lengthy, but it’s a complicated topic, where many problems can cause the same system, and I think it’s important to understand the background; if you think I should provide a long and short version of this FAQ, leave a comment to that effect.
1. Emulated Ports
By far, the most common cause of MIDI timing problems is using emulated MIDI ports. Once upon a time, there was only one type of MIDI driver, known as Windows MIDI. Later on, Microsoft introduced a new driver type, DirectMusic, which could theoretically offer better timing, but due to some limitations, this was mostly taken advantage of by gaming cards, not pro-audio cards.
To encourage application developers to switch from Windows MIDI to DirectMusic, Windows provides “emulated” DirectMusic ports for all Windows MIDI drivers; as far as the application knows, it’s talking to a genuine DirectMusic driver, with Windows doing the translation under the covers. This means that an application like Nuendo can, in theory, be written solely to the DirectMusic interface, and if your card doesn’t actually support DirectMusic, Windows will cover for it.
The reality is more complicated; sometimes the emulated DirectMusic drivers don’t work at all, or only work in one direction. Sometimes the emulated ports don’t work but the original Windows MIDI ports do. Sometimes the timing is off on one port or the other. Sometimes there are actually both Windows MIDI and genuine DirectMusic drivers for a device. So if there is both a Windows MIDI and DirectMusic version of a port, Nuendo tries to guess which one is the right one, and it filters out the other. Sometimes—usually, in my experience—it guesses wrong, especially where emulated ports are involved. And on some systems, though certainly not all, the emulated ports have timing problems.
(By the way, these two driver types—driver APIs, really—have nothing to do with WDM vs. MME drivers. Those are driver models, and affect how a driver is built, not what API it uses. A WDM driver can be either Windows MIDI or DirectMusic, and I believe the same is true of MME. We don’t care about WDM vs. MME here.)
The fix
Nuendo keeps a zero-length file called ignoreportfilter in the directory C:\Program Files\Steinberg\Nuendo\MIDI Port Enabler. Using Windows Explorer, you can drag this file up one level to the Nuendo directory, restart Nuendo, and you will now see both the emulated and non-emulated ports. In my experience, you nearly always want the non-emulated ports; you should go into Device Setup and set “Show” to “No” for the emulated DirectMusic ports so that you don’t accidentally use them.
This will only solve your problem if yours is a system where the emulated ports have timing issues. On my system, they don’t.
2. The two-clock problem
All MIDI interfaces on Windows timestamp their data before providing it to the application. This avoids timing problems when the application doesn’t immediately see the incoming notes, perhaps due to higher-priority interrupts, or things chewing up CPU time, or simply a burst of notes too quick for the app to process. The app just looks at the timestamp, does a quick calculation, and poof: instant latency compensation for all MIDI. This has been part of the MIDI driver spec forever.
But Windows provides two different multimedia timers - specifically, one called timeGetTime, or TGT, and one called QueryPerformanceCounter, or QPC. The QPC timer is more precise (although the actual precision is up to the motherboard), and often more accurate, but it’s only available on newer versions of Windows, and there were some motherboards a while back that had major inaccuracies with it, and some current dual-CPU boards still don’t keep the two CPUs in sync.
So drivers, especially Windows MIDI drivers, that descend from older code, or have to work on older OS’s, or that are simply more cautious, are likely to use TGT, which is what Nuendo normally uses; the VST and ASIO specs are based on TGT. Newer drivers, especially those written under DirectMusic, are likely to use QPC. Since the two end up out of sync on most PCs, you’ll end up with timing problems in Nuendo if your MIDI driver uses QPC.
This problem is likely to affect any sequencer, not just Nuendo - although some sequencers might be based around QPC instead of TGT, and thus they’ll have problems with exactly the interfaces that work fine on Nuendo and vice versa. Sonar does have a hidden option that lets you ignore ALL timestamping from the interface, which is fine unless Sonar can’t keep up with the interface, at which point you’ll have really sloppy timing on ANY interface.
The fix
Nuendo and Cubase 2.20 provide an option in the DirectMusic settings called “Use system timestamp”. This tells Nuendo that for MIDI tracks, they should keep track of time using QPC, not TGT. This affects only DirectMusic drivers. That means that if you have a Windows MIDI driver that uses QPC, you’ll have to use the emulated DirectMusic drivers, which is the exact opposite of what is normally recommended! Hopefully future versions will offer this option in both DirectMusic and Windows MIDI flavors. Meanwhile, hopefully your system isn’t one of those that has timing problems on the emulated ports. My system, an Asus P4C800-E, doesn’t, but certainly some do. A future version of MIDITime will test DirectMusic emulated ports as well, so you’ll know exactly what you’re up against.
The test
If you want to be certain that this is the problem you’re having, and help out the user community at the same time, you can download my MIDITime Utility. You take a cable from a MIDI output port to a MIDI input port, and run the utility until your clocks get out of sync; it then tells you which clock is correct, and thus what setting to use. Simple and definitive.
And please, if you run the utility, and your interface isn’t already listed below, e-mail me the results so I can share them! (I’d prefer that you not leave them as comments, so others don’t have to wade through the details.) The utility can take up to an hour to run (it waits that long to decide that your clocks are staying in sync), but more often takes about 5 minutes.
If there are any Windows programmers out there interested in slapping a simple GUI on this app, drop me a line. I never bothered to learn MFC, and with Windows.Forms and .NET coming of age, it’s not really worth it now.
The results
The following MIDI interfaces will work best with the DirectMusic emulated ports and the “Use System Timestamp” option checked:
Echo Mia
Frontier Design Dakota
M-Audio Audiophile 2496
MOTU 828 MKII
MOTU Express XT
MOTU MTP-AV
Steinberg MIDEX-8
Yamaha SW1000XG
The following MIDI interfaces will work best with the native DirectMusic ports and the “Use System Timestamp” option checked:
Wami Rack-24
The following MIDI interfaces will work best with the “Use System Timestamp” option unchecked:
Aardvark LX6
Aardvark Q10
Edirol UMT-880
Emagic Unitor8 MK1
Emagic Unitor8 MK2
Emagic AMT-8
M-Audio MIDISport
RME Digiface
RME 9632
The following lucky motherboards have clocks that don’t drift, and so can use any interface with any setting:
Asus A7V333
Asus A7N8X-X
Asus P4D-800D
Asus P4T-533C
Asus TUSL2-C
3. Constrain Latency Compensation
One person has reported that using the Constrain Latency Compensation option—which should, in theory, affect only audio—also improved his MIDI timing. This has not been confirmed by other reports, but it’s certainly easy enough to try. If you find this setting to be helpful, please let me know.
Posted by Jay Levitt at May 15, 2004 12:55 AM | TrackBack (0)
bron
thanks!
de 1e tip kende ik, de 2e nog niet ;P
een andere leuke site met veel tips,
http://www.musicxp.net
de 1e tip kende ik, de 2e nog niet ;P
een andere leuke site met veel tips,
http://www.musicxp.net
trash
Ouwe rot
- Lid sinds
- 24 juli 2002
- Berichten
- 4.564
Hij stopte er weer mee.
Nu ff hulp geroepen van de mannen achter de schermen van steinberg.
Probleem lag aan een oude chipset driver,
Dus kabels eruit,nieuwe driver,kabels er in
Hij blijft het doen,nu 2 dagen,wat een genot.
Nu maar hopen dat het zo blijft.
Nu ff hulp geroepen van de mannen achter de schermen van steinberg.
Probleem lag aan een oude chipset driver,
Dus kabels eruit,nieuwe driver,kabels er in
Hij blijft het doen,nu 2 dagen,wat een genot.
Nu maar hopen dat het zo blijft.
ELectronic SKIL
Sound center
Bij mij was het juist andersom.
Mijn midisport toen der tijd werkte de helft van de keren maar. Usb stekker vier keer in en uit en toen deed die het weer
is een keer.
Die heb ik eruit gedaan en daarvoor in de plaats een midex 8x8 gekocht.
En dat werkt perfect, nooit geen gezeik mee. Werkt altijd dat ding.
Dus zo zie je maar.......
Het zal altijd wel een combinatie van factoren zijn. Mischien een simpele tip. Probeer gewoon een ander merk.
(ik heb trouwens ook windows xp)
Vergelijkbare discussies
