Matt Lee
Forum Replies Created
-
Thanks for the input Tim. Will continue moving forward towards CineForm.
-
Thanks for your response. In doing my own comparison between DNxHD and CineForm, I couldn’t see any visual difference, but I did see quite a bit of difference when looking at the waveform monitor…..DNxHD had a LOT of missing data in the waveform vs the CineForm codec.
One of my complaints about the CineForm codec in an MOV wrapper (to which I’m not sure if there is any other option for CineForm) is that it won’t play back in my preferred media player on Windows which is VLC player. They do play back fine in QuickTime, but have a significant gamma shift compared to what I see in Premiere. Within Premiere, the gamma looks to be identical to the original RED files, as does the DNxHD, so I assume it’s just a QuickTime player playback issue. Probably not a big deal as long as you know what you’re looking at going into it….but quite jarring if you are unaware of the shift.
Can DNxHD in a MXF wrapper play back in the Windows Explorer environment well….specifically in VLC player? I want to make sure that we have quick and easy way of watching the files without having to go into Premiere each time.
Thanks again!
-Matt
-
I have a live production coming up and have been researching this exact subject….with no definitive answer. We’ll be shooting multiple different formats and editing in Premiere Pro CC on Windows 7 64bit systems. We’ll have DLSR footage, GoPro, 5k RED and then the live production feed. The live production company can give us “any format we want” and I’m trying to find out what would be best. I’d like to transcode the RED footage for editing and have the ‘live’ footage be in the same codec. We’ll need to be able to edit the footage each night for a ‘daily recap’ but ultimately have the footage for future projects (promotions for future events, event recap using ‘never before seen footage’, etc)
Previously the live feed footage came to me in a ridiculously large overkill version of 1080 60i DNxHD. The files were massive and unwieldy for editing. My solution was to convert everything after the fact to MP4 so the files were much easier to handle, however the quality was not good (as you could imagine). This year we are early enough in the process to be able to tell them what we want.
Wondered what your opinions were between the aforementioned CineForm and DNxHD (in a more reasonable compression ratio). The DSLR and GoPro footage we’ll leave as-is, just looking for a common core for the RED and live feed.
I read somewhere that the DNxHD codec is limited in performance due to the 32bit architecture of the QuickTime helper plugin for Windows. I read that ONE place and wondered if there was any merit to it.
If this was your project, what would you do and why? Thanks everyone!
-
True, it SHOULD be independent of Codec, but in this case it certainly was not. In the tests that I did, I only ran into the issue when using ProRes QuickTimes as the source material. Should it do that….no. Did it do that…yes. It’s a mystery.
-
I’ve run into this as well, the issue is that you are checking the box that says ‘relink others automatically’. You need to UNCHECK that box. Premiere doesn’t understand that you want to link to NEW media, so when it sees the existing media, it will relink to it. If you uncheck that box, it will require you to relink each file individually…..huge pain but it works. This way you can force Premiere to link to the file you tell it to. One issue is that it won’t change the clip name, so it will still look like it’s linked to the wrong media until you do a ‘reveal in finder’ then you’ll see that it has linked to the appropriate files. If you keep your original media in the same folder as your transcoded media, it will be easier to find everything.
-
Problem pinpointed. The issue only happens when I use ProRes QuickTime files as source elements. I just encoded two long form videos for Blu-ray and the AVCHD footage and XDCAMHD footage acted as they should, using the allotted amount of RAM. I threw a ProRes file at AME and it creeped up to 23.2GB of RAM consumed. So, I know what the problem is and it appears there is nothing I can do about it aside from not working with ProRes. Thanks for your time and input, not sure if I would have figured that one out on my own.
-Matt
-
Problem pinpointed. The issue only happens when I use ProRes QuickTime files as source elements. I just encoded two long form videos for Blu-ray and the AVCHD footage and XDCAMHD footage acted as they should, using the allotted amount of RAM. I threw a ProRes file at AME and it creeped up to 23.2GB of RAM consumed. So, I know what the problem is and it appears there is nothing I can do about it aside from not working with ProRes. Thanks for your time and input, not sure if I would have figured that one out on my own.
-Matt
-
I certainly understand the concept of having a workstation dedicated to video encoding and doing other tasks on a lesser computer. I don’t have that luxury of multiple workstations, so I try to be as efficient as I can with one. When I upgraded my RAM to 24GB it still uses nearly all of it, but fortunately it did help with multitasking during my tests yesterday. I didn’t feel any lag or hesitation while encoding and writing posts/checking email as I had with only 12GB RAM.
Interesting to note that my preferences were already set to reserve 8GB RAM for other processes, yet AME/Headless still used 23.2GB. I was intrigued by your comment in the Premiere forum about different Codecs using up resources. I’ll try to do some more tests today, but the one common denominator seems to be the Apple ProRes codec as the source video. I’ll encode something for Blu-ray today that doesn’t use ProRes as the source and see if it makes any difference.
-Matt
-
I certainly understand the concept of having a workstation dedicated to video encoding and doing other tasks on a lesser computer. I don’t have that luxury of multiple workstations, so I try to be as efficient as I can with one. When I upgraded my RAM to 24GB it still uses nearly all of it, but fortunately it did help with multitasking during my tests yesterday. I didn’t feel any lag or hesitation while encoding and writing posts/checking email as I had with only 12GB RAM.
Interesting to note that my preferences were already set to reserve 8GB RAM for other processes, yet AME/Headless still used 23.2GB. I was intrigued by your comment about different Codecs using up resources. I’ll try to do some more tests today, but the one common denominator seems to be the Apple ProRes codec as the source video. I’ll encode something for Blu-ray today that doesn’t use ProRes as the source and see if it makes any difference.
-Matt
-
Strange, I am having the opposite problem here: https://forums.creativecow.net/readpost/3/935395
My computer is using far too much RAM making my computer unusable while encoding. I wonder if there is a happy medium that can be found.I hope you can find a solution, although like Walter says, if your CPU is maxed out, adding RAM as a resource may not be to any advantage.
-Matt