[Ken Botelho]

That works too… I guess us Unix heads can never let go of the command-line 🙂

[Ken Botelho]

Hmmm try the simple things first like trashing your prefs and trying again, or another quick and dirty way to find out if its a software issue, create a new OS X user and then trying the batch capture under that account… Worth a shot

PS: you can also monitor your system in real-time by typing “tail -f /var/log/system.log” in the terminal, maybe you might catch the crash in the act

[Ken Botelho]

And if your in the market for a new affordable and simple mixer, get yourself a Mackie Big Knob… I just love this thing

https://www.mackie.com/products/bigknob/

[Ken Botelho]

Ok, A/V sync is entirely different from FireWire delayed output. And I can tell you I also have been struggling with this issue on 3 different ioHD boxes since the initial release, and its not caused by the driver/firmware version either.

A few steps that I always take to help with the sync issues until AJA takes can address this problem.

– Check that all equipment is properly Genlocked, including the ioHD
– Verify AJA audio output/input is not selected in the “OS X system preferences” (change to line or built-in input/output)
– Be sure to power up AJA before powering up computer
– Attach AJA to your system bus and not a firewire ExpressCard or Firewire pci card
– Recapture any previously captured video to verify its capturing in sync
– Playback from timeline to verify A/V playback sync
– At last test your quicktime playback with AJA VTR Xchange, to rule out any Final Cut configuration issues

[Ken Botelho]

Is it an A/V sync issue or just a delayed output?

[Ken Botelho]

[Mark Delbridge] “TBH I think the delay is just a firewire processing delay problem. The Avid Adrenaline suffers an even worse firewire related ‘delay’ artefact to the point of Avid now changing the hardware. No amount of firmware updates ever resolved the problem.

Personally I see any firewire connected Io ‘BOB’ as a device to do playouts to VTR or to output to a client monitor. You need to be cutting from the viewer and delaying the Io audio to match and accept that while it offers fantastic connectablility, it isn’t perfect.

We use Io’s and Kona’s here. The PCI connected Kona’s dont have this problem and can be set to a delay value of’0′.

Just the way it IMO…”

Ahhh, ya beat me to it! Kudos..

[Ken Botelho]

[Jorge Goizueta] “Hello to everyone

Im working on a sd project using ntsc APR HQ codec w/ MBP 2g ram 2.4 ghz core 2
ok my problem is that my external monitor has a delay compare to my viewer on final cut if someone experiencing the same problem or it is something on my system

thanks in advance

p.s im sorry for my english”

Unfortunately Jorge, this is the nature of the beast, and the beast being firewire. Unlike the Kona devices… when you go to view your output on an external video monitor, the Firewire output must be converted into a standard NTSC or PAL video signal. This is accomplished by using a DV camcorder, VTR, or converter box (such as the AJA IoHD) as an intermediate link between your computer and your video monitor.
When viewing video with the External Video option enabled, the computer’s built-in speaker is disabled (or at least should be) and the audio will play out of the DV device used for conversion from FireWire. You should also know that this external audio is synchronized specifically to the external video coming out of the same converter, and that there is a delay in the sync between video displayed on the computer monitor and audio coming out of a DV converter box.

So when you see a delay between what is on your Final Cut Pro output viewer and what is being recorded/outputted, this is normal. This is because there is a delay in transferring the data via the firewire cable into a video source. All will still function properly and everything should be fine when you play back the master tape.

I know its quite the annoyance but I have never seen such a workaround for this without adhering to a single output source or using a non firewire device (ie. Kona). Hope this helps.

-KennyB

[Ken Botelho]

[Navarro Parker] “Yup, tried different FW800 cables. And I can’t blast the firmware, because the io isn’t seen on the Firewire bus. The Aja control panel and firmware updater say no devices can be found.”

Do you have another machine to connect the AJA to? Your system may be the culprit.

[Ken Botelho]

The next best thing would be to blast the firmware, either re-write it, or upgrade it.

[Navarro Parker] “Is there a way to do a hard reset of the io HD box? We have a unit that seems to completely locked up. System profiler doesn’t see it on the Firewire bus. And while the LED panel on the box shows “Aja”, the power light doesn’t come on. “

[Ken Botelho]

[jose pantin] “When I print to video sound is displaced by one frame. How can I correct this? I’ve tried with “playback offset” in the Device Control Preset menu of the Audio Video Settings and with the “frame offset” of the Playback Control in the System Settings menu to no avail.

Many thanks to whoever can can help me.
“

I too suffer from chronic audio lag for both capture and playback with the ioHD, a dirty workaround but to ensure proper playback, make sure your AJA is not set as either an input or output devices for system (OS X) audio, check something else instead in the preferences like a line-out device….secondly make sure your both audio and video is originating from the AJA to the deck, preferably SDI embedded audio/video is my choice. Next thing before output, check to refresh A/V devices in FC and set the AJA to freerun genlock in the AJA control panel, Mix-down the audio and render the timeline to ensure no dropped frames should occur and then let er rip. Hopefully this issue can be resolved in the next software release. Let me know if this helps. If not…. back to the drawing board