[Greg Day]

just tried importing both the original client OMF as well as the new one from the files I imported (and gave a Reel name in FC). Both open up fine in Soundtrack, but neither have any timecode information in the clips. If I do a “Send To Soundtrack” the timecode is there in the clips.

So it appears that FC indeed does not send timecode information with an OMF.

That’s bad.

Director of Visual Media
Sonic Media Studios
Portland

[Greg Day]

the challenge is, this project we’re trying to conform came from somewhere else. We did an audio mix on a first cut, gave them split tracks, they imported those splits and have re-edited their show. Now they gave us a new OMF with those splits as the source media. Our audio guy is trying to line up the splits in the re-edit with the original raw audio to do a proper mix. But without the timecode, it’s a difficult process.
So to help figure out the problem, I’ve taken the audio files we provided to them and created a new project/sequence in Final Cut. Gave the audio reel names, cut a few pieces into a fresh timeline, then exported the OMF. Open it in ProTools, no Timecode, plus the “Out of Range” message in the Spot function. Wondering if it’s a setting in PT that we’re missing.
Our audio guys usually work with OMFs from Avid and never have had a problem. And I am stuck trying to find a way to make it work for them.
It still doesn’t make sense to me why it wouldn’t work. So I’m hoping it is as simple as a setting preference.

Director of Visual Media
Sonic Media Studios
Portland

[Greg Day]

Thanks everyone for the suggestions.
Tried giving the audio file a Reel name, but still wouldn’t work. Pro Tools just doesn’t see the TC and gives an “Out of Range” message when trying to spot the clip.
Guess I’ll go for the Duck. Another Value-Add we can sell our clients!

Director of Visual Media
Sonic Media Studios
Portland

[Greg Day]

I also have been using the Beta update, but I noticed that I had to re-authourize the account (resubmit my serial number/name) in order for it to not be in demo mode.

Don’t know if that’s the problem for you or not, but it might help to check to be sure you aren’t running in demo mode.

g

Dog Day Editing
Creative Editorial & Directing Services
Rose City

[Greg Day]

so what’s the last??

Dog Day Editing
Creative Editorial & Directing Services
Rose City

[Greg Day]

well after conferring with Sonnet, they suggest it’s the Western Digital Caviar SE16 drives I’m using that aren’t happy being used in a RAID. It makes as much sense as anything – I can’t get the RAID to show up at all anymore and there’s a long list of error messages in my console log.

I’m now awaiting a response from WD to see what they have to say…

Dog Day Editing
Creative Editorial & Directing Services
Rose City

[Greg Day]

There must be some conflict, or my Sonnet card is dead. I tried booting in Verbose mode and there were a bunch of errors related to the Sonnet card. This setup worked in another quad G5, but isn’t working in the current system. Unfortunately, I can’t try again in the previous machine as it’s no longer here. Everything was working yesterday (after many reboots and utilities), but I have not had any success today.

Whenever the RAID is turned on, it won’t mount. The system will boot, but there is no disk file access. What I mean by that is – if I try to do a file find/spotlight, nothing happens; if I run Disk Utility, it hangs; if I run Cocktail Disk Check, it hangs. When I try to shut down or restart, it hangs. If I turn off the RAID, everything works. And the same results no matter which slot the Sonnet or Kona cards are in (so likely not a slot issue??)

Guess it’s time to call Sonnet…

Dog Day Editing
Creative Editorial & Directing Services
Rose City

[Greg Day]

OK, to catch up and recap.

Yes, I do shut down every night. And yes, I shut down all peripherals as well. I’d leave things on, but this is a new room and I’m not 100% confident on power yet (even though I’m attached to a ups).

Things have now gotten worse. I can get the Kona to load OR the Sonnet RAID, but not both. I’m having a harder time getting the RAID to mount and whether or not it does, often the system hangs when trying to shut down or restart. My first boot in the morning again missed the Kona, but the RAID loaded. Next boot – vice versa. Actually got both going the next time, but then after working for about a half hour, everything locked up. Had to force reboot and haven’t had any luck since.

I’ve run every utility I can think of – disk utility, fsck, reset-nvram, TechTool. Everything checks out.

I am going to try reverting to the Kona 1.3 drivers since I’ve always had issues with the Kona not loading even before I added the Sonnet card. FWIW, the Sonnet card is now in Slot 2 and the Kona in 4. Tried Sonnet in 4, Kona 3 and Sonnet 4, Kona 2 – no difference.

Last resort, I will reinstall the entire system.

thanks all for your input

Greg (fka dogdayediting)

Dog Day Editing
Creative Editorial & Directing Services
Rose City

[Greg Day]

yeah, got the Sonnet in Slot 4. That’s why I was wondering if it made a difference with the Kona.
I thought it was interesting that one card specifically called for certain slots while the other didn’t – especially with both being “high bandwidth” hardware.

thanks.

Dog Day Editing
Creative Editorial & Directing Services
Rose City

[Greg Day]

cool. That’s what I figured, but thought I’d check with those more in the know.

Thanks!

Dog Day Editing
Creative Editorial & Directing Services
Rose City