Am I with a good workflow ? I’ve got jagged pixels on final DVD ….

[Fredy Schwerdtner]

Thanks Brian for your response.
I was looking all over the places on internet for similar problems and nobody says a thing about it. I read only one guy saying that once my material is 1080i to be put on a SD DVD (intelaced), it is not necessary to deinterlace it.
I will check all you have said and will let you know.
Thanks to everybody.

MacBook Pro 17″
2.5 GHz Intel Core 2 Duo
4GB 667 MHz DDR2 SDRAM
(2) External HD LaCieMac (400/800 FW and USB)with 500GB -(2) USB External HD Western Digital (in cases) with 750GB
OS X 10.5.7
Final Cut Studio 2

[Daniel Low]

Oh my! – Brian, your mileage may vary but I think you’re getting a few things wrong!

Here’s a post from David Newman, CTO of Cineform when asked what’s the best workflow going from 1080i to SD DVD

“Personally I avoid interlaced, so my suggestions will be limited. Others can chime in.

Try this :

Complete a 1080i60 export from Premiere. Load that new 60i AVI in HDLink and set the perferrences to High (at least), Progressive, Remove 3-2 pulldown, Deinterlace and scale to NTSC 16×9. The resulting conversion will be 720×486 16×9 progressive 23.976p — load that in EncoreDVD (or similar) for NTSC master. For PAL DVD use High (at least), Progressive, Remove 3-2 pulldown, Deinterlace and scale to PAL 16×9 and add Rate Change “23.976p to 25p (+4.1%)” and check “Maintain audio pitch.” This will produce a 720×576 16×9 25p output.”

Did you notice his reference to Deinterlcing!

Link Here

__________________________________________________________________
Sent from my iPad Nano.

[John Heagy]

Hi Fred,

You do not need to de-interlace. That reduces temporal resolution, 60i to 30p in your case. However, since you’re using Compressor ANY interlaced footage will get de-interlaced by Compressor if scaled down. Compressor relies on QT, and QT cannot scale fields independently. Now… FCP does scale fields so you could make a 720×480 60i timeline and drop your 60i HDV seg into it… presto 60i SD. Use Compressor to encode that to MPEG2 with any scaling needed.

Now… having said that, if someone has found a combination of settings that does scale HD 60i to SD 60i in Compressor… I’ll gladly eat my words.

Good luck
John

[Fredy Schwerdtner]

Hi John,
My seq is a PRORES. Will it make any difference ?

MacBook Pro 17″
2.5 GHz Intel Core 2 Duo
4GB 667 MHz DDR2 SDRAM
(2) External HD LaCieMac (400/800 FW and USB)with 500GB -(2) USB External HD Western Digital (in cases) with 750GB
OS X 10.5.7
Final Cut Studio 2

[John Heagy]

[John Heagy] “Compressor to encode that to MPEG2 with any scaling needed.”

That should be WITHOUT any scaling.

Ted if your HDV footage is in a ProRes seq all the better. Make sure the new SD seq you make is set to anamorphic if you want a 16×9 DVD

[Patricia Buskirk]

Hi Fred,

I came across the same jagged pixels issue with pretty much the same workflow you used. Did you ever find a good solution? I’ve tried most of the suggestions with no luck. The entire project is 2 hours, so I would appreciate any ideas that would help deal with the jagged pixels as well as the cumbersome file size/ render issues. (even troubleshooting with small sections is very time consuming)

I recorded with my Sony HDV Z5U camera. Captured as ProRes 422, edited as ProRes, inserted titles from LiveType and exported as a QuickTime movie. Then used Compressor “best quality” encoding settings and then used DVD Studio Pro to create the DVD.

I like the quality of using DVD Studio Pro over iDVD and had success with Compressor and DVD Studio Pro when importing footage using Apple Intermediate Codec. I thought I’d use the ProRes codec to increase the quality, and now am running into this problem. (I used the Matrox MXO hardware to input using the ProRes Codec)

Also, my FCP (7.0.3) sequence setting is 1920×1080 HDTV 1080i 16:9, SQUARE Pixel aspect, UPPER (odd) Field dominance, and 29.97 edit timebase.

My computer is a MacBook Pro 17″
Processor: Intel Core i7
Processor Speed: 2.66 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache (per core): 256 KB
L3 Cache: 4 MB
Memory: 8 GB

Perhaps, is the issue that is in the Square pixel aspect? Wouldn’t Compressor take care of that with its ‘best quality’ settings? Again, I appreciate any suggestions. thanks.
Patricia