-
Media 100HDe to DVD studio pro
Posted by Greg Ball on February 14, 2007 at 4:10 amWhen ever I try to create a DVD using Media HDe to BitVice then to DVD studio pro, the fade up and out from black jumps and is not a smooth fade. Everything else seems fine. Does anyone have a solution? Can’t DVD tudio pro read Media 100’s black clip?
Greg Ball replied 19 years, 3 months ago 5 Members · 14 Replies -
14 Replies
-
Arthur Dent
February 14, 2007 at 4:36 pmTry to force render the black clips. Find the Rendered Media file on you video drive and bring that into a bin – use that media clip when doing the export.
Not sure if this will fix your problem, but it’s worth a try.
A.D.
-
Kieran Matthew
February 14, 2007 at 5:27 pmHi Greg,
Which codec are you using and how are you exporting it?
Is the problem evident if you play back the m2v file from bitvice in QT before DVDSP gets hold of it?
Just a thought, when you encode with Bitvice, is “use studio RGB” enabled? If so try encoding without it. I’m wondering if this is a black level clipping issue.
K
-
Greg Ball
February 14, 2007 at 5:40 pmHi Kieran,
I’m just exporting it as a reference file from M100 HDe. Not sure which codec I’m using. Do you have a suggestion? The problem is apparent in BitVice before I send it to DVD SP. It’s also apparent in the DVD SP in the test phase.
I do use Studio RGB as everyone here as always suggested that. I’m not sure what it’s real purpose is. Any advice?
-
Kieran Matthew
February 14, 2007 at 6:02 pmHi Greg,
Studio RGB scales the levels of Media100i’s legal range (16-235) with black at 16 and white at 235 to meet Apple’s prefered RGB (0-255) range with black at 0. This was crucial when using Media 100i’s codec, but with the other codecs available in HDe I’m not so sure – Perhaps Floh can jump in here?
Using the Studio RGB button on media that is already 0-255 might have clipping effects like you decribe as the early stages of a fade would be crushed to the same level and create a jump. That said, I’m speculating here so experimentation is the key.
I do remember something being said about Media 100 changing the quicktime export to Apple colourspace rather than the usual media 100 colourspace, but I didn’t think that affected “by-ref”.
K
-
Joe Hayden
February 14, 2007 at 6:32 pmHave you tried substituting a black pict file for the M100 black?
L.O.A.
-
Greg Ball
February 14, 2007 at 6:58 pmI’ve seen that suggestion herein searching through the posts, but there should be no reason why one can’t fade up from black cleanly with the software the way it is.
Thanks for the suggestion though.
-
Floh Peters
February 14, 2007 at 9:57 pm[Kieran Matthew] “Studio RGB scales the levels of Media100i’s legal range (16-235) with black at 16 and white at 235 to meet Apple’s prefered RGB (0-255) range with black at 0. This was crucial when using Media 100i’s codec, but with the other codecs available in HDe I’m not so sure – Perhaps Floh can jump in here?”
This still is the case with the Media 100 codecs (844/X, Media 100 HD and Media 100 i), but it is not true for “generic” QuickTime codecs. So one reason for your problem could be a jump between 2 different codec color spaces. Say you have digitized into Media 100 i codec and you are rendering into Uncompressed 8bit 4.2.2 codec you would create luma jumps in an Quicktime (by ref or self-contained) export as soon as the rendered part starts. The Media 100 i codec file would use 16-235 RGB values and the transition would use 0-255 RGB, causing a jump as soon as a transition starts and ends. To avoid this, make sure that you work in one “class” of codecs (either in the Media 100 codecs or in the standard QuickTime codecs). But from your description I am not really sure if this is what you are seeing.
-
Greg Ball
February 16, 2007 at 5:16 pmFloh-
I’m digitizing into the Media 100i codec, and rendering into the same. So this isn’t the case. Any other thoughts?
-
Kieran Matthew
February 16, 2007 at 6:19 pmHi Greg,
What exactly does the problem look like? Can you post a short segement?
I assume by jump you mean “one-minute black, next almost full video”, rather than the usual stepping you get from viewing interlaced MPEG2 fades on a progressive computer screen.
Are there any other problems with the video?
K
-
Greg Ball
February 17, 2007 at 4:27 amKieran,
On this video I had a client who taped a short intro onn Mini DV. I added a 20 frame dissolve from black to his image. As it fades up it goes brighter than it’s video level for 1 frame then to normal. It’s an ugly fade up.
I also notice a slight verticle shift on the top of the frame of video. I can’t figure out how to post the clip here or I would. Any thoughts on posting an m2vclip here? I tried BitVIce with and without RGB…it looks the same.
Reply to this Discussion! Login or Sign Up