Misha Aranyshev
Forum Replies Created
-
I want multi-seat FCP solution since version 2. I understand this means dumping whatever database engine the app is running now and putting in a much more robust and flexible one. Side-effect – fixed Media Manager. Hopefully.
-
Mixer window in FCP must be open for surface control to work but it does not need to be on the foreground. Tascam with FCP would be much better setup if in addition to transport controls and faders Mute, Solo and Track Arming buttons worked too. Like they do in Soundtrack Pro
-
All Avid greybeards will correct me if I’m wrong but I think QuickTime was not yet around when Avid was designing an NLE. That’s why they had to create OMF. QuickTime is not the source of MM problems. Media Management is simply broken by design in FCP. The app’s database engine is weak and slow and should’ve been replaced as soon as Apple realized FCP sells well. Version 1.2.5 that is.
-
Tascam FW1082 here too since yesterday. I like it so far. A lot of functionality in a single package. Intuos 3 is coming soon. The pen is for Photoshop because I rarely need to mouse around FCP.
On a related question – is it possible to use control panel track-arming buttons in FCP? It seems the answer is no but is it the final answer? Could Apple add this function in the future? How about Shuttle? The Shuttle button on Tascam has no effect right now.
-
[Robert Brown] “I then did some correction of the clips in After Effects and all of the clips had a significant gamma shift after coming out of AE.”
There are two sides of this problem. First, FCP is YUV and AE is RGB. Second, 709 HD color space support in QuickTime 7 is totally messed up:
Create an orange to blue left to right gradient in FCP 5.
Drop onto the High-Def Uncompressed 8-bit YUV timeline.
Create white to black top to bottom gradient.
Superimpose over the first gradient. Set Composite Mode to Add.
Export QuickTime Movie with current settings, import the movie back into FCP and compare.In Standard Def. the exported clip has no shifts but in Hi Def it is clamped.
-
[Oliver Peters] “Sorry you’re having a tough time with this”
Not a bit. I’m asking for details because this “hovering” thing appears to me as very isolated interface element, without anything similar in the rest of the UI and thus is just another layer of complexity. The app does not prepare you to the fact you gonna need some “hovering” for the specific task. You actually said it yourself:
[Oliver Peters] ” The matched clip is loaded as a source and the cursor has nothing to do with the target tracks for the edits. Those are assigned in standard track mapping used in that UI as in most others.”
-
[Oliver Peters] “You can then insert or overwrite as needed.”
To what track? The one the mouse cursore is still hovering over? What about the clip loaded in source monitor from bin, not via Match Frame? Basically, is this “hovering cursor” used widely or is it just for Match Frame?
-
[Oliver Peters] “Compare that to Velocity, where instead you simply hover the mouse cursor over the designated clip on any track and hit Match Frame.”
Does that mean the clip from the source monitor will go to the track the mouse cursor is hovering over with insert or overrecord command? What about a clip in pasteboard?
Also, what about the timeline cursor – the playhead? Match frame supposed to call up the exact frame, not just the master clip.
-
Nine out of ten FCP editors never got the idea of Replace edit. Does that mean it is poorly implemented in FCP? OK, ask a dozen Discreet edit* grey-beards to show you Q-edit and results will be similar. The only mistake Apple did with AutoSelect is the thing is turned on for all tracks by default. If it was off for all tracks people would respect FCP a bit more. The app is too forgiving to lousy work-style.
-
[Oliver Peters] “It’s the single biggest impedement I see to working as a power editor because it counteracts natural and intuitive ways of deleting and trimming in the timeline from the keyboard.”
Without examples it sounds very hollow. Besides there are no “other apps”. There is Avid. Discreet edit* is dead long time ago. Liquid combines the worst interface decisions from edit* and Avid and it is soon to be dead too. Velocity? Edius?