David Cherniack
Forum Replies Created
-
[Jeremy Garchow] “I guess it wouldn’t be any different than constantly having to rearrange tracks, except it would be easier and more dynamic.”
Who has to constantly rearrange tracks? Once I start my actual editing I set my tracks and add clips to them as approriate. By assigning or dropping on zones you’re doing the exact same thing. So how is it easier unless you’re making incorrect assumptions about my workflow? ‘Dynamic’ I can see. Marginally more flexible also. I’m not sure that it’s better because of the rippling issue that I’ll address in my response to Simon.
David
AllinOneFilms.com -
[Chris Harlan] “[Jeremy Garchow] “I think that underneath the primary storyline, audio clips should be “click sortable” by roles.” and the rest.
Interesting ideas! I could see an answer being somewhere in that direction.”
Yes, it’s an interesting idea. But it basically makes the magnetic timeline behave like another visually organized metaphor – the fixed track timeline…with some marginal added flexibility. But would the added flexibility be offset by the constant re-arranging of the zones forcing the editor to constantly adjust to shifting patterns? I don’t know but it seems to me the real issue here is not spatial organization, it’s whether editing in ripple mode can ever be efficient with complex timelines.
I don’t ever edit in ripple mode unless I’m doing a simple assembly. Once I’m multi tracked with all kinds of independent audio layers I’m out of ripple faster than a jackrabbit with tail on fire. No matter how you slice it up the magnetic timeline by definition is a rippling structure behaving by simple rules. It just can’t have the intelligence of a human – at least not in the foreseeable future.
This argument has seen the light of day here before but it keeps getting subsumed in ideas how to improve the magnetic timeline. If there’s a way to turn off ripple and maintain trackless re-organization I haven’t seen it yet. I think Apple may have painted themselves into a corner by going this way. Then again it’s an engineer’s folly to create solutions that turn out to be bigger problems than what they were trying to improve. All signs point to the liklihood that that’s what’s happened here.
David
AllinOneFilms.com -
[Herb Sevush] “Really Craig, this argument is ridiculous”
Has that ever stopped Craig? C’mon Herb, he loves it. 🙂
David
AllinOneFilms.com -
Yeah, I didn’t mean my ‘whining’ comment to be taken as disparaging of Avid. I know they were badly hosed by Apple and the User Meet people who perhaps should have been less willing to do Apple’s bidding.
David
AllinOneFilms.com -
[Dennis Radeke] “Truth be told, we both had slots that night I believe, but Avid did indeed have the bigger exposure for that night.”
And most of the entire industry thought it was just Avid that got elbowed out of the way. Kudos to Adobe for not whining and playing the sympathy card. 🙂
David
AllinOneFilms.com -
[Bill Davis] “And if the ADOBE clan (who, BTW were the ones pre-empted at the eleventh hour that night) ended up a bit pissed and that gave them any extra impetus look gleefully on any narrative that FCP-X is deeply flawed OVERALL rather than in a very narrow range at the top end of the user base – well, it’s a competitive world – and that’s how business has always been played at a certain level.”
Ahh…Bill…I do believe it was Avid, not Adobe that Apple pushed out of the Las Vegas meet. I also don’t think that Avid, or for that matter Adobe, is gleeful that Apple may have laid a turd with the release of X. I think, as you say, they’re both just happy to see their bottom line increase.
David
AllinOneFilms.com -
[Aindreas Gallagher] “but they need a functional prores delivery codec of some sort.”
Aindreas, I agree that PPro needs good a cross platform delivery codec, but are you aware that if you’ve got FCP, X, or Motion on your Mac you can render to any version of Prores?
David
AllinOneFilms.com -
Jason, why do you have the Nvidia 8800 in the system? At this point Pr can only use one GPU. There may be a conflict with the 4000. First thing I’d try is pulling the 8800 and running the 4000 for the Pr display and CUDA. I’d also look at the issue that the AJA folks were having with selecting the audio hardware. It may be the same issue with BM cards on the Mac. The last thing I can think of to check is the version of nVidIA drivers. The latest is not necessarily the best. With Matrox on the PC we’re finding that 275.33 is working well.
David
AllinOneFilms.com -
[Gerald Baria] “have’nt we learned anything the past decade?! This is Apple. That’s their thing. They make things infinitely better, they do things right. Sometrimes they do it so fast that we are initially caught stunned for some period but eventually realize that its the most awesome thing ever.”
To answer the question you ask in the first sentence, as judged by the following sentences, apparently not.
David
AllinOneFilms.com -
Hi Franz,
I wish I could help. I’m not on a Mac. One thing I have noticed is that many of the complaints, both Mac and Win, seem to be related to the PrPro 5.51 update which I found does have some issues with overlay and and the Matrox 5.51 drivers. It may be the same on the Mac.
I’ve reverted back to PrPro 5.50 and the 5.5 Matrox drivers until the issues get sorted out over the next little while.
David
David
AllinOneFilms.com