Adam Welch
Forum Replies Created
-
Do you mean to type ProRes HQ? not sq?
No, I meant what I said. Mpegstreamclip has two different ProRes 422 settings: (HQ) & (SQ) Unfortunately they don’t have either labeled, so I didn’t figure it out until I started having other transition problems that ended up being a result of mixing (HQ) & (SQ) footage.
Adam Welch
-
The problem is much more distinct when viewed in high resolution (in any of the delivery formats).
Yes they’re all the same size and frame rate.
1920×1080 23.98 prores 422(sq) no field dominance
Adam Welch
-
Here’s a link to a short sample exhibiting the problem:
password is “creative cow”
The problematic transitions seem to be softened by the additional compression that vimeo applies. Notice the brightened flash between clip changes, and then how the close-up dress shot brightens before fading out with the transition.
Adam Welch
-
Are you certain that “Full” is checked in the Render All drop-down menu?
Yes, full render is checked
Adam Welch
-
The media, rendered, inside that dissolve is not getting that color or brightness adjustment.
Good thought.
Yes I’m fully rendering. Yesterday I tried trashing all the render files and getting a clean render. Problem still exists.
I’ve already done Trash Pref, Reboot, Repair Permissions, problem still exists.
When my exported quicktime is complete I will preview the finished file with finder’s quick look feature. It’s never given me problems before. However, the quicktime that plays improperly in quick look also plays improperly in the stand-alone quicktime application. Said file plays properly inside of FCP’s viewer window. It looks like the problem still exists when I upload to vimeo though…
Self contained quicktimes direct from the timeline should be a carbon copy of the timeline….at least that’s my understanding.
I keep thinking that it could be an issue with the original transcode operation on the .h264 files. Perhaps I’ll try a fresh transcode on a test batch of my original video files.
Thanks for your time!
Adam Welch
https://www.curtisnemetz.com -
I did more troubleshooting today, and it seems that I have found the issue.
My workflow includes transcoding my .h264 files in mpegstreamclip using the prores 422 codec. For those of you whom don’t know, mpegstreamclip has 2 options for the prores 422 codec, and ordered from top to bottom they are:
Prores 422(HQ)
(and)
Prores 422Mpegstream clip does not delineate between the two options in their codec labeling, and this has been a source of some of my confusion. If you check your individual clip(s) attributes from within FCP (by scrolling across the browser window, and expanding the “compression” tab) you can see if you transcoded your clips with the HQ or standard version.
FCP is showing me that that the difference between clips converted at these two codecs is about 8mb/sec. [Prores 422(HQ) averages 22.0mb/sec while Prores 422 averages 14.1mb/sec] I can see no difference (visually) between the two clips (after rendering, played back from the timeline.
With this knowledge, I can now reproduce the problem using identical footage across multiple computers. For now, I will just use the ProRes 422 NON (HQ) version.
If anyone has more conclusive evidence I’d love the additional input! Hope this helps!
Adam
Adam Welch
-
Has anyone found a solution to this problem? I believe I’ve been experiencing the same thing:
https://www.vimeo.com/25875539
I did more troubleshooting today, and it seems that I have found the issue.
My workflow includes transcoding my .h264 files in mpegstreamclip using the prores 422 codec. For those of you whom don’t know, mpegstreamclip has 2 options for the prores 422 codec, and ordered from top to bottom they are:
Prores 422(HQ)
(and)
Prores 422Mpegstream clip does not delineate between the two options in their codec labeling, and this has been a source of some of my confusion. If you check your individual clip(s) attributes from within FCP (by scrolling across the browser window, and expanding the “compression” tab) you can see if you transcoded your clips with the HQ or standard version.
FCP is showing me that that the difference between clips converted at these two codecs is about 8mb/sec. [Prores 422(HQ) averages 22.0mb/sec while Prores 422 averages 14.1mb/sec] I can see no difference (visually) between the two clips (after rendering, played back from the timeline.
With this knowledge, I can now reproduce the problem using identical footage across multiple computers. If anyone has more conclusive evidence I’d love the additional input! Hope this helps!
Adam
Adam Welch
-
I just brought the project onto a different machine, and the same problem persists.
I’m going to attempt to do a fresh transcode of the original video and see if anything changes
Adam Welch
-
Also, I’ve trashed render files & re-rendered, same problem persists
Adam Welch
-
I’ve read other’s similar posts describing the same issue. The only headway I’ve made with it, is that some editors have been able to resolve the issue by extending/shortening their transitions by 1 frame. Apparently there is some issue with the codec or frame-rate that is causing this problem. That solution however, is not working for me this time.
Adam Welch