User

Finally the real deal! Thanks again M Carter, love the no nonsense approach.

Thanks Tupp. I've now got ffmpeg and will have a look at your tutorial on the road ahead

Good option KrisAK. Thanks. And if I understand you correctly, you are saying that you know that clips are only 'copied' or 'consolidated' and not re-compressed because the ProRes encoder is not on your system. Right? But what if you are on a Mac with PPro and ProRes and you did the same... would it consolidate clips by re-encoding with ProRes because it has access to the script?

Yes, it seems that ffmpeg can split files without re-encoding. Now if only I can figure out the correct terminal commands Thanks Tupp.

Thanks for the input Tupp. My only concern is that you using words like "I think' and "Fairly sure' and this does not exactly inspire great confidence. It would be beneficial to have an authority weigh in with fact. I have a lot of material in front of me and it would be good to know for sure and get this right. I will see what info I can find on ffmpeg. Axel: I state you can completely neglect recompression artifacts with ProRes. Sorry but if I understand your English correctly, do you mean to say that: 'the re-compression artifacts will be negligible using ProRes'.

Thanks again Axel. So if I understand you correctly, when splitting an interframe codec such as ProRes, there will always be re-compression regardless of the software used. And that compression will eventually lead to artifacts that may of may not be visible after one or more generations. Can someone actually confirm this as well? Sorry to keep coming back at it but my remaining question: is there 'newer' software that does not re-compress ProRes when a file is split apart?

Thanks Axel! Can anyone kindly confirm?

71 views and only one response. Really?

I started with AVCHD and transcoded to ProRes 422. Now I want to split the clip while keeping it as ProRes 422 without having to re-encode. I imported the ProRes 422 file into MPEG Streamclip, marked in/ out points, exported as ProRes 422. Has the file been re-encoded?

It's been slow for me as well here in Berlin over the past week. Maybe a server issue, backup etc.

Thanks JG. Appreciate the tips. When I look a the ProRes transcodes done using 'Full Range' on the YC Waveform, the super whites riding up to 110 IRE. So I think that must be a good thing.

Spending for mediocre tech is unnerving, but in some ways limitations can be a great thing. One part of me likes it that we can not always have the biggest, best, fastest camera all the time. These limits sometimes appear as reminders to focus on what I 'can have' and very often that means focusing on people story and storytelling.

Sent.

Most everyone has an axe here, normally it's in the form of a mouth. Or a snout, if you will.

Hmmm. I almost never use After Effects... though someone might bring these skills to the film down the road and I hope they wouldn't be limited as I have transcoded a fairly large chunk of material since beginning the render. I guess it can always rendered again. I guess at the end of the day, I'm happy to see that with the 'Full Range' setting the IRE is touching 110 IRE and in PPro I've seen in the past that there is a percentage of highlight detail in that range retained. Maybe at 'Broadcast Range' (100 IRE) that detail may not be so easily accessible anymore. I don't know... ya know?

Thanks Andrew. Living in Berlin, I know it wasn't you.

Why, does After Effects not see anything above 100 IRE?

Transcode example using 5DtoRGB Both jpegs were exported from PPro CC2015. No grading/ correction. 1st jpeg: Original AVCHD 2nd jpeg: Original AVCHD transcoded to ProRes using 5DtoRGB using 'Full Range'. 3nd jpeg: Original AVCHD transcoded to ProRes using 5DtoRGB using 'Broadcast Range'. The difference between jpeg 1 and jpeg 2 is easily discernible. The only perceivable difference between jpeg 2 and jpeg 3 is seen in the YC Waveform. Broadcast Range brings the 110 IRE down to 100 IRE. Comments?

An EOSHD moderator felt it necessary to censor (delete) a comment directed towards an amazing member here. The moderator then proceed to apply restrictions on my future posts. My question at the top of this post was to try and understand how long this 'moderating' was going to last? It seems that the restriction has been lifted. Joy.

Thanks Joema 2013 Macbook Pro Retina Intel HD Graphics 4000 - VRAM (Total) 512MB NVIDIA GeForce GT 650M - VRAM (Total) 1024MB I used PPro CS6 for 3 years and found the Mercury Playback Engine to be unstable. I went with OpenCL. I have been using CC 2015 (8.2.0). After installation (6 months ago), I remember getting the same buggy freezing action. So again I went with OpenCL. I will have another try at Mercury on this machine but I'm not optimistic. I'll report back afterwards.

Sorry if it wasn't clear, and thanks for the insight, but as mentioned twice in this thread, I am on CC. I went ahead with the transcode to ProRes because of the 4.2.2 space and because I will grade and add effects. Moreover, I have had issues with the Mercury Playback Engine while using 8.2.0 (Creative Cloud 2015). Also because another member suggested that it makes round-tripping between other programs easier.

x

I'm about to start the process of transcoding the C100 MkII AVCHD material using 5DtoRGB. My settings will be: ProRes 4.2.2 Rec709 Full Range No Post Processing. Gamma 1.0 The C100 MkII material was shot in WDR picture profile so it won't be as 'flat' as C-log. As such, do you still recommend 'Full Range?' Like you said earlier, after transcoding, the material can still be tweaked to broadcast norms. Correct? Cooling fans about to kick in...

I actually started this 'Topic' in relation to an event that had nothing to do with Chinese/ Russian spammers. Please disregard my association.

Nice breakdown and explanation Joema. Good to finally have some solid insight... thanks! I'm actually on PPro CC 8.2.0. And with regards to the Mercury Engine using 8.2.0, I remember feeling like there were stability issues so I kept using OpenCL. Maybe I should switch back to see how stable things are?