Brian Petersen
Forum Replies Created
-
[Heath Alseike] “When I relinked the files; all clips with the name “clip #1” for example were linked to a single “clip #1” video file. Not each “clip #1” to the correct corresponding “clip #1” in each event. Even though they were different files, in different folders, have different durations, and different file sizes. Yet some how final cut relinked all “clip #1″files with different info than the originals. Except for the one that happened to match up.
When I go to re relink an incorrect file link to the correct clip, final cut then relinks all the files with the same name to the next one I choose. Including the one that was correct previously in a different event. So now the one that was linked to the correct “clip #1” is now the new other one I tried to link. So I can only have one “clip #1” linked correctly at a time. I have gone back and forth trying to relink all the files too many times. Even though they are in different events and I am only telling it to replace the one.
I thought final cut would only auto relink files with the same name, duration, and info? It even tells me when I try to link the file to the original video clip, it is suppose to be, it wont link to the correct file because the audio and length doesn’t match the incorrect one it auto linked incorrectly and, thinks it should be. Final cut linked all the wrong files and wont let me relink to the original correct file because the original file was in an edit and then it put the new incorrect linked video file in the edit, and now when I try to put the original one back in it won’t because it didn’t match the wrong one Final Cut put there incorrectly.
“This exact same thing just happened to me.
I moved some folder of media to a new drive because space was getting full. I relinked media and it’s connected some clips to the wrong clips, even though they are in different folders. When I try to relink again to the correct one, which is the actual correct one, FCPX says that clip doesn’t match length, etc. UGH.
When FCPX was relinking, I’m surprised it didn’t honor the folder structure that it was in. It went looking for C0006.mp4 which it thought was in the “Day 7” folder, but the Day 7 Folder wasn’t on the drive, so it instead relinked to C0006.mp4 from in “Day 2” folder.
Trying to move everything back onto drive and open up backup and see if I’m good. But I still need to move my media without having this happen again.
Even thought it was looking for C0005.mp4 in “Day 15” folder, it relinked to C0005.mp4 in “Day 2” folder.
-
[Eric Strand] “You might find this helpful https://www.provideocoalition.com/transcode-before-color-premiere“
YES! Very helpful, thank you!
The biggest part to me was the Dither aspect of transcoding in Resolve vs Premiere.
So now my plan in to edit in Native but NOT transcode my final clips via Premiere for color, but rather simply Project Manage in Premiere to create trimmed clips of my native files. Then bring those native files into Resolve for transcoding and color.
-
Good call. I think my plan is to edit in native and then export a media managed master sequence in ProRes422 with handles on the clips (I’m assuming I can do something like that). Then those ProRes clips will be used for FX and color.
-
I tested out LT, 422, and HQ. Might be in my head but I thought I saw a difference between LT and 422, but I couldn’t tell a difference between 422 and HQ. Seems 422 is the sweet spot.
In Premiere I did switch the playback Renderer to Mercury – OpenCL (from CUDA) and was suddenly able to playback native files quite smoothly. I was impressed. So I may just skip the transcode all together unless you foresee any issue later down the road? when it’s time to color or anyhing?
Thanks!
-
I agree with you. That seems to be the case. I adjusted my gamma and I can get it to match up fairly well now. Everything else about the program (timeline, buttons, etc) is pretty washed out now, but that doesn’t matter much.
I assume FCX is 2.2 based, but I’m not too excited to switch over to that.
-
okay.
It’s an annoying topic, because I’ve sifted through threads on the apple discussion boards and people say that FCP 7 does NOT apply the gamma multiplier. But I have to assume they are wrong and go with what you are saying.
-
Thank you…
And I guess there is no way to the gamma multiplier off?
You would think with Snow Leopard changing the gamma to 2.2 that FCP would allow users to use that gamma in FCP. I like operating in a 2.2 world with SL and now Lion.
So when I go into FCP, I should change my display profile to 1.8 while in FCP. Then when out of FCP go back to 2.2?
Kind of annoying, but if there is no other way.
-
As I mentioned in the post, the QuicktimeX version, the one the left, is image that best reflects what is seen once put up on the YouTube, Vimeo, and other sites and then viewed on a number of different computers and browsers.
The one on the left (the one viewed in quicktimeX) is the base to look at. That file, when uploaded and then viewed on various computers looks like it does when viewed in Quicktime X.
It’s the FCP image that is the odd-man-out so to say.
-
apologies to the moderators. I reposted this as a reply in another thread. I didn’t know this actually went through because I was a new member.
-
Is there no way to tell FCP to NOT shift the gamma. Does FCP 7.0 assume that you are in 1.8 space?
I tried to post this topic below, but I just joined the forum so it didn’t let me. Only replies. My questions is below… Thanks.
Hello all,
I know this topic has been covered before, but the answers never seemed to address what I’m trying to get to here. Every response was always a “get a proper broadcast external monitor”.
I am putting together videos for the web (will never be seen on a broadcast monitor) and I’m concerned with the massive contrast difference I get from the FCP viewer and canvas compared to the final output in Quicktime.
I KNOW that FCP and quicktime use different methods of showing video on the screen. But take a look at this screen shot…
The image on the left is in quicktimeX. The image on the right is the same movie file in FCP canvas. There is obviously a MASSIVE difference between these two.
The way the video looks in QuicktimeX is the generally how the video file looks when uploaded and then viewed on YouTube, Vimeo, and other website across multiple browsers and platforms, with slightly variances here and there. It never looks like the image on the right (FCP canvas).
To all the people that want to write back saying “Get a broadcast external monitor” are you saying that if I plugged in a broadcast external monitor that the monitor image would look similar to the image on the left (the one in quicktime)? And so any color changes would match up correctly when put on the web (generally speaking)?
I’m not looking for the FCP canvas to be pixel perfect, but the amount of difference in this screen shot is wildly unacceptable. I often shoot, edit on laptop only, then post to web. I can’t have an external monitor around. As is, if I want to do anything with color I have to tweak, output to qt to see what it looks like, tweak again, output to qt to see if it looks good, and then go from there.
FCP is obviously doing something the video. I’m running Lion and was running SL and had the same issue. I’m running FCP 7.0. Since I’m in 2.2 gamma across the board, is FCP still adjusting my video for display thinking that I’m in 1.8? Because that would probably do this.