Tony Silanskas
Forum Replies Created
-
Ditto Geoff! It’s been a blast seeing what they come up with and then playing with it myself. Such a great way to learn this new stuff.
tony
-
The only success I have had (besides manually cutting each clip) is to the Compound Clip method. Agreed we need an easy way to do this. Also, I couldn’t tell from you video if the Compound Clip method worked on not for you. Are you having problems with Compound Clip blades not going through all the clips? I haven’t had this problem yet.
tony
-
So a few more days and this is becoming pretty annoying for me and hoping someone has found a fix. Now it seems to do it about a minute before the end of a Compound Clip when the Compound Clip is more than 5mins long.
tony
-
-
Maybe I’m over simplifying this but I don’t see this as a bug and am fine with the lack of sync indicators in regards to an original clip. In FCPX, to “Break Apart” a clip is the same thing as “Make Clip Independent” in FCP 7 and therefore there is no need for sync indicators. If you want to see a clip like you normally would in FCP 7 then you just “Expand” a clip (Control + S). If anything, FCPX actually adds something to this by being able to “Expand” and “Collapse” clips for less clutter on the timeline. And there is absolutely no way you can make that clip out of sync when it’s just Expanded and therefore makes sync indicators unnecessary for these clips. Plus you can still trim the audio independently from the video it is synced to.
So what I haven’t seen mentioned is that FCPX should have moved sync indicators to a different role. Now that FCPX has clip connections it’s much easier to sync totally independent video and audio clips (something pretty much impossible with FCP 7), but these can be moved out of sync unintentionally sometimes with no warning so I’d liked to see a “LOCK SYNC” or just “Show/Warn When this Group of Clips might get out of Sync” option. That’s where sync indicators (though I’d rather see something better) are needed and not in the way FCP 7 used them as it seems to be in discussion here.
And Compound Clips are not the answer to this because I can’t “Expand” all the clips in a Compound Clip (therefore keeping sync) as it just expands to one video and one audio track representing all the clips.
A semi-related bug, though minor and it’s probably just the wrong way of doing it, is when you want to “Break Apart” a Compound Clip that contains a clip that was only “Expanded” and has its audio trimmed. If you “Detach” the audio AND then “Break Apart” the audio clip the audio that belonged to the “Expanded” isn’t trimmed. It is the full audio of the clip but has the sections not used Muted in a blue color (something I’ve yet to notice anywhere else). So technically it trims but there doesn’t seem to be a way to get rid of the Muted blue so you can’t add audio at either end. Annoying but can be easily avoided if you never “Detach” the audio in the first place.
tony
-
[sven geudens] “Doing this the official way (via the options in the fcpx menus) crashed my application.”
Thanks for sharing your workaround. Just curious, when you say official do you mean “Move” or “Duplicate” Event? I’ve tried this on some smaller Events and haven’t had a crash.
tony
-
[Frank Stäudtner] “There were regular lags of about 15 secs where everything just halted…. That happened maybe twice per hour….”
You sound pretty upbeat for someone experiencing two crashes an hour. =)
Or did it hang and then unhang?Where did most of your crashes happen? I seem to get a lot when switching back an forth from a Project to a Compound Clip and lot working in a Compound Clip compared to just working in a Project. And I get the 15+ freeze-ups a lot but sometimes if I wait longer enough it fixes itself. Problem is sometimes it’s 20secs and sometimes it’s over a minute so I just end up Force Quitting. Just a bunch of bugs that need working out.
tony
-
+1 to your +1. Well, at least two us think it needs work so that might be enough for Apple to fix this.
tony
-
I gave up trying to work with XDCAM EX natively in FCP because of the constant crashes like you describe. The bugs were never worked out by Apple. Transcoding to ProRes fixed the crashes problem and I haven’t looked back.
As far as slower performance with ProRes than XDCAM EX, it could be a few things but we need more info about your project to see if there is a problem or your just experiencing normal performace with ProRes:
– Can you explain a bit more when you say “much poorer” real-time performance? You didn’t say the playback was worse with your example, just that the bar turned green and green bars play back fine most of the time for me.
– What version of ProRes did you transcode to? ProRes Proxy, ProRes 422, ProRes 422 HQ, etc.? What frame size? 1080p, 720p, etc.? XDCAM EX has an average bitrate of 35mbps while standard ProRes 422 is about 147mbps so ProRes needs faster drives to playback in realtime. And since ProRes is a larger-size (less compressed) codec it will take longer to render for some things because the files are larger. A small price to pay for a superior codec (in FCP eyes at least).
[Ken Pugh] “Now I would have expected the opposite – given XDCAM is a predictive Mpeg codec – and ProRes a single frame codec.”
– This is a bit of a common misconception since XDCAM EX is a pretty efficient codec and isn’t bogged down by the Mpeg factor nearly as much as some people say. Just try it in Adobe Premiere and it’s much smoother to work with than FCP since most of the FCP bugs aren’t there. And with the much smaller bitrate than ProRes you get faster performance all around. This is why many news stations use XDCAM EX.
tony
-
Have the Cow gods thought about something like:
https://people.redgiantsoftware.com/
Seems like it would be a good fit with all your tutorials.
tony