Saturday, March 17, 2007

TIPS: Midi recording problem in Nuendo 3.2 with Edirol FA-66 FireWire audio interface

Problem: Last week one of my client faced a peculiar problem in Nuendo 3.2 while sequencing ( recording midi tracks ). The midi notes would not get recorded despite being played and heard while recording.

The nature of symptoms for such problem are :

  1. Persistent timing problems (shifted notes etc.) while using native or emulated Direct Music midi ports.
  2. Using emulated Direct Music midi ports often results in shifted MIDI events while recording (events are recorded too late or too early).
  3. After recording for a while the MIDI events are not recorded at all despite of being played and heard while recording.
  4. Sometime after recording you find that all the notes have been shifted to the beginning of the sequenced event.

The system was based on Intel D945GNT motherboard with 3.4Mhz dual core processor having 1Gb DDR2 533Mhz RAM and 2 x 250GB SATA Seagate Hard disk. The sound card he was using was Edirol FA-66 FireWire audio interface connected through Iogear "Texas Instrument" based PCI FireWire card. It seems D945GNT is not suitable for FireWire audio interfaces as I have faced audio problems using Tascam audio hardware also on the similar type of setup.

I connected FA-66 to other system and found working properly without any midi loss at all. I even tried VIA based FireWire card in the same system with no success. The problem is that Nuendo 3 midi port handling is not compatible with D945GNT motherboard as you encounter the problem while using this motherboard only.

Ads by AdGenta.com

Solution:See that you should have DirectX 9.0c installed properly if you are using emulated Direct Music Midi ports.
  • If you are using Direct Music midi Ports then you should enable (check) the option “Use System Timestamp” provided in the Direct Music midi section of the Device Setup dialogue. This option uses another timing reference in your system when enabled.
  • If you are using Windows midi port then you should enable (check) the option “Use System Timestamp” provided in the Windows Midi section of the Device Setup dialogue. This option uses another timing reference in your system when enabled.
Just check the box as shown above in the figure and it should solve all your midi timing and recording problems.

9 comments:

D. Moreira said...

I've been facing a similar problem but with Nuendo 2.0. The MIDI sometimes stops responding and the program crashes. I have the latest drivers and software updates and can't find a solution.

Sarvesh said...

Please give me details of your system and sound card. Use winXp with service pack 2 and all latest update fixes.

D. Moreira said...

I'm using Windows XP SP2 with all the latest updates, the latest driver and software updates. I believe the problem occurs when my dual-core processors get drift appart in timestamp, so the midi can't be correctly understood by two processors with different timmings. I think I have been able to solve this problem by making Nuendo only use on processor. I have an Edirol FA-66, Nuendo 2 with the lates updates, Reason 3 (rewired) with no updates (I don't know if there are any).

Sarvesh said...

The solution which I have provided is available only in Nuendo 3.

In your case please let me know which motherboard you are using ?

Are you using onboard 1394 ?

If you are using a pci card for firewire port - just try to change the slot.

Open device manager and in view select "Resourses by type" & check if the IRQ used by 1394 port is also used by any other device or not ?

Lastly if your problem is still not solved then I will put an article about setting firewire port speed to 400 - which is wrongly set in winxp SP2 and has to be manually configured.(if you are aware of "SidSpeed" reg entry).

D. Moreira said...

I'm using an ASRock 4CoreDual-VSTA.
I have tried before to change the slot of the pci card and nothing changed.
And the IRQ used by 1394 isn't in use by another device.
I usually use Edirol's power supply, but the problem persists anyway. Although the option to use System Timestamp is also available in Nuendo 2, it doesn't solve anything.

Sarvesh said...

First check which midi ports you are using - i.e. DirectX or windows midi. If you are using directX then disable the windows midi ports in nuendo device setup. The option of System Timestamp is available for both windows and directX ports separately - so if you are using directX then you should enable (tick) the option in directX only.(i.e. select the directX page in nuendo device setup and then enable the system timestamp box.)

You can try vice versa by enabling the windows midi ports instead and disabling the directX ports.

If this also doesn't work, do let me know so that I can give you one more tip to try.

Lastly have you set the "SidSpeed" of your firewire port properly as I have mentioned in my recent post?

D. Moreira said...

I'm using de Asio 2.0 drivers and the emulated port for Edirol FA66, wich is the one with the least latency. Aboute the SidSpeed, I don't know how to do it. By the way, thank you for your interest on this! ;)

sandy said...

Thx A lot Sarvesh For solving the midi problem....

Anonymous said...

Sarvesh, thanx a lot for your suggestion about the "Use system timestamp" option, I've saved a lot of time getting crazy with this midi problem. Greeting from Rome-Italy and thanx again.Rocco