Quote
Hi Alan et al -
I just did a little test here, since we're weighing up using converted files or PDR's shadow files. I understand from Alan's posts that the .MOV files from his dashcam take "too long" to generate shadow files... hence considering conversion in a separate application.
I don't know what the camera is so I don't have sample files to test. Instead I used 6 short 4K/UHD .MOV clips from Canon DSLRs - 5D MkIV, 6D MkII & C200. The clips range in VBR from 520 - 2,298 Mbps (so they'd be demanding to edit in that form). Total duration of the 6 clips is 00:01:57:26.
In Handbrake (free & does batch conversion), the 6 clips were converted to 1080p MP4. It took 5:50, after an initial scan time of ~30sec.
I imported the same clips into PDR, with shadow files enabled. It took 5:55.
From that little test, there is no time advantage. Other converters may do the job faster.
Alan - for your final production, do you intend to use the original clips or the converted ones? If original, you can do that with file substitution shown in this little tutorial. If not, don't click that link
Cheers - Tony
I just did a little test here, since we're weighing up using converted files or PDR's shadow files. I understand from Alan's posts that the .MOV files from his dashcam take "too long" to generate shadow files... hence considering conversion in a separate application.
I don't know what the camera is so I don't have sample files to test. Instead I used 6 short 4K/UHD .MOV clips from Canon DSLRs - 5D MkIV, 6D MkII & C200. The clips range in VBR from 520 - 2,298 Mbps (so they'd be demanding to edit in that form). Total duration of the 6 clips is 00:01:57:26.
In Handbrake (free & does batch conversion), the 6 clips were converted to 1080p MP4. It took 5:50, after an initial scan time of ~30sec.
I imported the same clips into PDR, with shadow files enabled. It took 5:55.
From that little test, there is no time advantage. Other converters may do the job faster.
Alan - for your final production, do you intend to use the original clips or the converted ones? If original, you can do that with file substitution shown in this little tutorial. If not, don't click that link
Cheers - Tony
Hi Tony - thanks for getting involved - just to add a little background info - my primary motivation was to reduce the size of the raw materials, as my dashcam makes .mov files that were about twice as large as equivalent duration .mts files I am used to working with. Really impressed with the HD quality of the dashcam footage - and as such see it becoming an interesting part of our holiday movies providing an insight into what we are driving through to get where we are likely to be filming. Never thought of that at purchase time. PD16 is an ideal tool to speed up video over the boring (motorway) parts.
So - reduced filesize of raw material is the prime mover. Reduced shadow file creation time is a welcome bonus - which triggered off this task as I had not really noticed how much larger .mov clips were until I started playing in PD and noticed the longer shadow file creation times. If you see what I mean.
On holiday I need to reduce filesizes as dashcam will not hold all we will film so I will need to upload dashcam footage to laptop and whilst I am not sure how much storage we might need by the end of a 2 week motoring holiday I am in with a fighting chance if I can reduce the storage required by dashcam footage. All worked well last year with Canon footage over 10 days, but this year we are off for two weeks and have dashcam adding to storage requirements.
You know I just had to click "that link" despite not planning file substitution - neat little technique though.
See next post for detailed results of VLC player conversions.
Thanks for your input - much appreciated,
Alan.