[Carsten Orlt]

easy done.
select one of the dvd presets. i always use the 120min one because of being most compatible even with older dvd players.
switch all to ntsc in the video setting tab. (ntsc, 29.97, choose aspect – rest as is!)
now switch on the frame controls and for a quicker but ok conversion set the rate conversion to ‘good’ (one higher then default). If you want better quality you can go one higher to ‘better’ but the time to convert increases dramatically. for short pieces ok, but for an hour program not really workable. all other settings can stay the same. save this new preset to something you’ll find again in your custom settings.

audio export normal because you’re not changing the length of you film so audio stays the same.

in dvd studio just select dvd sd ntsc before you import any mpegs and build as normal. good idea to test in a player that can play ntsc and doesn’t convert to pal tv to check the result.

carsten

[Carsten Orlt]

David

Thanks the eyes and monitors are doing fine 🙂

I think its more a question about post economics. Why would I waste disk space for more quality that you can’t see and that will never be broadcast? And you need faster CPU’s too…

Unless somebody can tell me the hidden secret (and I do mean facts not theory) why to use HQ for HD broadcast I’m happy to save space and cpu power and get the same result.

Cheers
Carsten

[Carsten Orlt]

Jeremy
where exactly did you read this as it is not in their white paper on ProRes. There it just states that ProRes normal is good for normal life, and HQ is only the option if you want more.
Also I did tests and don’t see any difference between HQ and not.
Now I know HQ is better quality in term of higher bit rate BUT in real life for television, I don’t see the point.
Cheers
Carsten

[Carsten Orlt]

thanks Jeremy.
just relaunching FCP doesn’t help here.
have to wait to what Aja will come up with.
cheers
Carsten

[Carsten Orlt]

yes prores normal, not (HQ)
yes did uninstall 1.0 first.
went actually through the drive and made sure there is not a Aja file left 🙂
not sure what you mean by just quit and reopen as you have to restart and the Aja installer deletes the FCP pref files?
going by your questioning you don’t have any problems and do not see this behaviour?
cheers
Carsten

[Carsten Orlt]

1080i25.
the glitches happen only on the compi monitor not on any output.
I installed vers 1.1 on Tiger as well and no problems there.
drives are fast enough too, because when start and stop it doesn’t come back for the loaded clip and all clips play fine in Tiger.
all reported to Aja already.
was just wondering if I’m the only one…
Cheers
Carsten

[Carsten Orlt]

if it is not hardware related the only thing I can think of is that the pan settings for your audio clips in the timeline are not set correctly.
now you might already checked this so if you did I’m at a loss too..
but if not check the following:
double click the audio clip from the timeline to open it in the viewer. check where the pan setting is at. if for this clip on track 2 the pan is set to middle then it will play back out on both output channels. it should be set to 1 (all the way to the right). track 1 clips should be set to -1 in the pan slider (all the way to the left).
by the way the right channel should be on channel 2 on your vtr and the left on track 1.
also make sure that your audio output for your seq is set to 1+2.
That’s really all I can think of…

[Carsten Orlt]

just be aware that the fcp release notes state that you can’t open a 6.0.2 project in 6.0.1.
so don’t close the door behind you just yet 🙂

[Carsten Orlt]

could it be that you recording to tape in dvcam format and not mini dv?
dvcam and mini dv are the same codecs – dv – but the tape runs at different speed. the idea was that through wider spacing on the tape dvcam is less error prone and therefor better for professional applications. some dv decks play back mini dv and dvcam recorded tapes, but only record in dvcam. Like the the dsr40 which i have. a 60 min dv tape will only record about 40 min in dvcam mode.

i doubt that it is a frame conversion issue as the only possibility of a changed duration would be if you converted the 25 fps from pal 1 to 1 to ntsc’s 30 (29.98) but his would mean you running time would be shorter as you pack 25+5 pal frames into the 30 frames per second ntsc.

that’s all i can think of right now.
cheers
carsten

[Carsten Orlt]

Gary
I’m still waiting for my ioHD in Australia…
Anyway you state your offset for Leopard, though Aja saya that their drivers are not qualified for Leopard. Do you have a beta or do you just use the 1.0 version with success?
Cheers
Carsten