Re: Batch Capture Digi Beta Problems

Ramona,
Thanks for your reply, and your story with Xena and Digi Beta.(also thanks Tim for your reply)
Today I did a complete system rebuild and made sure everything (drivers/software) was up to date and all requirements for the XENA install were followed meticulously.
I have now tested XENA with 3 different decks and have achieved a lot more insight to my problem.
Here goes… I’ll try to be brief
System: Microsoft Windows XP Pro, Service Pack 2.
RAM: 1.50 GB
Computer: HP XW8000 Workstation
CPU: Xeon 2.8GHz
1.5 Tb Array
Separate Internal Audio Drive
Xena 2K Machina: 3.1.1.0
Premiere Pro2

Problem: Can’t accurately capture and master.
I chose settings I thought may be causing my problems (listed below) and tried all sorts of combos.
PremPro Preferences: Capture - Use device control timecode
Media - In out points show media offset
PremPro Project Settings - AJA Capture Options - timecode input
AJA Device control-TC Source, Offset, Embedded SDI TC in/out capture

When capturing I found that there were only a couple of settings that affected anything, the main one was AJA Capture Options-timecode input. Basically anything you batch capture displays the correct codes in the bin/project window but always gives a 1 frame delay in the source window. When laying it down to a timeline and creating an EDL, the list supports the 1 frame delay. I tried to add an offset but this only affected the bins timecode data, it always showed the 1 frame delay everywhere else. (Batch only works with 422 TC input, if you use embedded it captures all tape motion for the clips duration as soon as you hit go)
Crash capturing can only be done using embedded as the TC input. This gives correct codes everywhere, the only problem is that when you make media offline then batch, which you have to do with 422 TC as the input, you get a lovely 1 frame delay again.
When insert mastering the GUI seems to have a locked duration, unchangeable, the deck seems to pre roll and do its stuff correctly but as the duration on the GUI is locked to 1 frame that’s all it does 50% of the time. Sometimes it doesn’t do it all. Assemble just seems to go back and crash in anywhere, irrelevant of TC ins/outs etc.
So there you have it Ramona… I would be interested to know if you or anyone can suggest anything now I have explained my issues clearer.
Cheers
Butch


Helping others gives you good cowma.