[Toke]

[toke lahti] “Can Color handle well 1440×1080 proresHQ or does it have to be 1920×1080?”
Pretty old thread, but the problem came up again recently, so can anybody clarify?
Is there any decrease in performance in Color if you’re using non-square pixels like 1440×1080 with prores?

Or have anybody noticed if this “Hidden & mandatory deinterlacing in Media Manager” bug is removed in FCP7?

[Toke]

Shoot 720p60 with shutter off or 1/60.
That way you can get the best quality when converting to:
1) 1080p30, dropping every other frame and resize
2) 1080i60, one frame becomes one field and resize
3) 1080p60 (maybe used in future), just resize
4) 1080p24, inverse telecine might result some stutter if lots of movement

[Toke]

Red?

[Toke]

Nobody care to comment here?
Or just nobody had this problem?

[Toke]

You can choose AR in DvdSP’s video track’s settings.
You can even choose if the 16:9 picture is letterboxed or pan&scanned when wieved on 4:3 device or choose user’s preference.

16:9 (sd-)dvd’s are the most common here in Europe and almost all here in Finland are 16:9, since all new sd-broadcasts have been done in 16:9 for few years now.
I think it’s mainly in US that people think that SD = 4:3 & HD = 16:9.

[Toke]

Only way:
https://imnotbruce.blogspot.com/2009/09/snow-leopard-and-firewire-problems.html
https://www.macosxhints.com/article.php?story=20090922213608468
?

[Toke]

I noticed back then, that if the resolution (1440×1080) is not changed (to 1920×1080), media manager does not do any altering to video.
Can Color handle well 1440×1080 proresHQ or does it have to be 1920×1080?

[Toke]

Don’t know if there’s anybody interested about this, but I did another test and found out that deinterlacing happens only when there’s scaling involved.
When I did a test with hdv1440i50->proresHq1440x1080i50 there was no deinterlacing.
So, with hdv1440i50->proresHq1920x1080i50 there is some quick and dirty deinterlace which produces pretty ugly quality.
I reported the problem to Apple before, but got no answer, so maybe they are not so interested about this solution either…

[Toke]

Hmmm, I can’t login to Apple’s discussion so maybe I’m banned because this was too insulting to them:
“Pretty amazing that almost every update to QT has broken something in Pro apps (Apple’s own or Adobe’s) in last half a year.”

Andy,
would it be good idea if Apple just updated Pro versions later than noPro?
Or is it that most QTPro users want all the latest capabilies?
I feel a bit like beta tester to do all this reaserch “Will it work” after QT updates.

Have I understood right that in FCS2 & CS3 enviroment only problem with current QT is AC3 passthrough and some LT bouncing?

I need to playback 1 hr long document from my MP in next monday’s premiere in digital cinema theater and I’d really like to use DD5.1 sounds…

[Toke]

My FCP was also constantly crashing, but problem seems to be now solved by making a new account.
Old account was made in Tiger and maybe there is some legacy/compability issues with accounts in .4 & .5.
This might also help others, if their accounts were made in Tiger.