-
ClipWrap adding “warbles” to DVCProHD encoded footage, but not to ProRes LT
I was about to burn a DVD, but then noticed some odd sort of sideways warbling/distortion (can’t think of a better way to describe it), on the footage most noticable on camera pans. It looked as if those portions were shot through some sort of dimpled glass. I had used ClipWrap to encode my NX-5 data and went with DVCProHD, though i normally do everything in ProRes. After seeing this anomaly, i guessed it might be the codec that was the problem, so i did a test from ClipWrap encoding one offending clip to ProRes LT. Voila! No more warbles! So re-encoding the whole batch. Have any of you seen something like this before???
thanks for helping out a bonehead!
__________________________FCS3
2.66 GHz Quad-Core Mac Pro
6GB RAM
NVIDIA GeForce GT 120
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!) -
5 Replies
-
No, I only encode to ProRes. Why did you go to DVCPRO HD? It’s 8 bit, thin raster…ProRes is 10-bit, full raster.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
It’s hard to say for sure, but two things spring to mind that might be described as “warbles” – interlacing artifacts, or some sort of moire from downressing. Since dvcpro (assuming your content is 1080) is only 1280×1080 internally, you’re scaling your 1920 wide content down to 1280. That could potentially introduce some scaling artifacts.
Additionally, interlaced content being treated as progressive can sometimes look warbly, especially when further downrezzed to SD. It may be that whatever did your dvd encodes didn’t tread the dvcprohd content as interlaced properly?
In any case, feel free to shoot us an email at support@divergentmedia.com if you want to dig in further.
-Colin
-
Hey Shane…ya, i’m pretty much a 99% ProRes guy, just went to DVCProHD as a sort of experiment. This is when it’s nice/good to have a repeatable workflow – just do it like normal and all is well. It’s all re-encoded now, and the DVDs should look better.
thanks for helping out a bonehead!
__________________________FCS3
2.66 GHz Quad-Core Mac Pro
6GB RAM
NVIDIA GeForce GT 120
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!) -
Collin,
Thanks for your reply here. I didn’t bug your tech support because it wasn’t that big of an issue for me…but maybe if it helps someone else that would be dandy. I must say, you and Divergent Media have probably THE best most responsive tech support for ClipWrap. THANK YOU! I NEVER use FCP’s Log & Transfer method when converting these NX-5 clips anymore. Too many hassles, AND i can’t edit another project using L&T anyway….so ClipWrap is the way to go and i’ve pointed several people to it over this past year.
Thanks again for a very robust product! I can drag the data folders into it from anywhere and i haven’t seen read or write problem yet…EXCEPT now for this pesky DVCProHD thing…which i don’t really need anyway.
Take care!
thanks for helping out a bonehead!
__________________________FCS3
2.66 GHz Quad-Core Mac Pro
6GB RAM
NVIDIA GeForce GT 120
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!) -
COLIN,
Please pay no attention as to how the previous poster replied to you. He has a head made of bone…and realizes there really is only one “l” in your first name…to which this post attests…
Sorry about that
: (
thanks for helping out a bonehead!
__________________________FCS3
2.66 GHz Quad-Core Mac Pro
6GB RAM
NVIDIA GeForce GT 120
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)
Reply to this Discussion! Login or Sign Up