Nikolas Bäurle
Forum Replies Created
-
I agree. But for most productions I prefer keeping one event, not for performance, simply to keep my event library simple.
When I started out at Promiflash and we were still figuring things out we had the problem of too many events. At first producers would create one event per shoot, for a daily production with two shoots per day thats 60 events per month and 30 Projects. It didn’t affect performance too much, but beach balling happened more often as far as I remember. Keeping our producers organized with that many events didn’t work well, too often footage was imported into the wrong event, which happens very easily when you have long event lists and hectic producers.
Once we started doing one event per week, so 30 Projects referencing 4 Events, organizing our footage became a lot less convoluted.
-
Generally you should keep events to a minimum. Having footage spread over too many events will become a hassle once you need to archive and off/online projects.
-
Correcting my last answer: X creates a clip when auto syncing not a compound, sorry, tired
“Always look on the bright side of life” – Monty Python
-
No, no linking. I would not de-nest your CCs, its best for sync audio to stay connected (blue). you can double click them to expand the audio or expand the audio components for more precision so you don’t need to de-nest or detach the audio (green). You simply need to rename your compounds so you don’t have to keep de-nesting.
It just crossed my mind that when X autosyncs it creates compounds anyway. Since I haven’t used it very often and am still at my Avid job right now I’m not thinking straight. I’ll check that in a minute.
-
Using CCs for syncing is really too much of a workaround for something that X makes very easy.
The method you are using works, but syncing audio as it is supposed to be done in X is much faster, and you won’t have the hassle of having to de-nest everything all the time.
Since X doesn’t use a timeline like in 7, you don’t have the ability to link like in 7. But since the sound in the secondary is connected to the video in the primary, whenever you move a clip in the primary everything connected to it moves along. So you kind of have half a 7 link, you just need to be careful moving the audio in the secondary since that will change the position it has.
-
The audio sync is best for one video / one extra audio like in in feature films or in case you have interviews with separate sound if you only have one camera, which in my experience is rarely the case since for TV the sound is usually connected directly to the camera. For music videos it doesn’t really make much sense, when editing you should have the studio quality track anyway, at least thats how I’ve always done it. For a performance music video multicam is the way to go. Have each camera record sound , then sync it to the studio track with Multicam. The only problem you could encounter with music videos is when the shooting in large halls you do get some drifting out of sync issues depending on where the sound source is in relation to the camera and the performance, that would need to be adjusted manually in the multiclip itself.
“Always look on the bright side of life” – Monty Python
-
You can’t group like in 7. What you can do is sync your audio to the video files, as long as it has audio to match. Highlight both files you need, ctrl+click, synchronize clips. X creates a new file with the master sound and the camera sound from the video, then you can turn on the tracks you need in the inspector or expand your audio components in the timeline. In this case I would leave the audio connected.
“Always look on the bright side of life” – Monty Python
-
Moving projects and events is very easy within X. You can copy an event from one drive to the next by simply dragging the event icon to the drive. X asks you for a new name, after its done delete the old event. When duplicating projects you get the option of consolidating your footage by creating new events with the footage you used.
Personally I like moving things manually most of the time. As Tim pointed out, as long as you adhere to the folder structure X needs you shouldn’t have any problems, and don’t take any files out of the event or project folders
“Always look on the bright side of life” – Monty Python
-
When you open FCP you should see the connected scratch disk. Then you pull the event icon from your internal drive to the scratch disk icon. FCP will ask you for a new name, when its done duplicating you can delete the old event.
“Always look on the bright side of life” – Monty Python
-
Craig, I agree with you that most problems with Keyframes that many have been having are easily solvable. The default Bezier movement between keyrames that many are complaining about are is simply a matter of clicking on the control frame in the viewer and changing it back to linear, or using the inspector. In my opinion the keyframing is very fast.
Now, I have been having discussions with Bret Williams and he pointed out that if you do a scale and position move you do get a small s-curve before it hits the next keyframe. You do not have this problem in AFX and in Motion you get a curve if you scale that you can change back to linear in the keyframe editor
I’m currently doing a lot of MTV style, fast curvy moves, making stills look like handheld camera moves etc. I love it for that and I get it done much faster, than Avid or FCP7. And this is one of the reasons I got the job as head editor at Promiflash in Berlin. They didn’t want too many linear moves, do something different. And when I do need something linear the Ken Burns effect is pretty good.
When you need that organic look, as if images are being thrown into the frame or fall out, X is very good.
True linear move in X is still kind of quirky, but not a reason for some of the angry reactions we’ve bee seeing. There still is the option of Motion, very easy to learn and AFX. Most Avid and Premiere editors I know use AFX, there must be a reason.
I like the Keyframing interface in X better than in 7, but I’m hoping we get an improved keyfame editor, where I could also ad a temporal interpolation not just for opacity. Some curve control in the timeline would be nice.
“Always look on the bright side of life” – Monty Python