Robin S. kurz
Forum Replies Created
-
[Loren Risker] “New options in the speed change menu (I think).”
No changes to retiming. All that was already there.
[Loren Risker] “Now you can auto jump cut wherever you place a marker.”
Ditto. That came with 10.1.
-
Wow. Your response speaks novels. Reduced to 4th grade level personal attacks. Bummers. But I never actually expected a real answer, so all’s good. 😀
-
[Craig Alan] “First: why have you not updated to the latest version. FC has been improved since 10.0.6 … a lot.”
I was wondering that, too. But he wrote 10.0.2 not 6, so I just gave him the benefit of the doubt and assumed it was a typo. But if it is in fact 10.0.2 then I think there’s only one logical assumption as to why that is.
-
So, again, your proof and confidence for such a obscure matter-of-fact claim comes from where?
Either way I certainly enjoyed the equating of “doughnut” with that of some obscure, arcane niche terminology and its alleged “social importance” immensely. 😀
-
[James Ewart] “but it is the single greatest barrier to entry for most people”
:-))))
Sorry, but that’s just ludicrous conjecture. As a teacher at various schools and academies I can’t confirm that even remotely. So I’d be very curious where you have gathered that “knowledge”. Not once in the last 2+ years has a single student of mine spent so much as a second of their time thinking about it. It took me (an editor of 20+years) a full 5 mins. to adjust. There are truly much bigger fish to fry and that topic is just a silly, typical “old solipsistic pro” waste of time imo.But again… if THAT’S X’s biggest issue… hooray! ;-D
-
And I thought we were way past the (rather nonsensical IMHO) nomenclature gripe. If semantics is FCP’s biggest problem, then I’d say we’re doin’ pretty well! 😀
-
Sure. Like I said, they are most definitely listening. But I know for a fact that certain things have been long planned. Features and functions which user feedback has helped further form and optimize in the making, but not create per se, as I stated above. 😉 So yes, feedback is important on every level.
There are certainly some things that were first considered due to feedback. What we will never know for sure. 🙂
Keep in mind that some feature’s stand on their own, other’s require that huge parts of the rest of the app need to be changed/adapted for them to work right consistently, which is why some of the seemingly smallest things will take far more time and effort to implement than you would suspect. One such component e.g. being the underlying XML…
-
Exactly. Whereby the Used Media Ranges only apply to the current open/active timeline. If none of the visible clips in the event are used in the active timeline, then you won’t see the orange bars anywhere either.
-
It’s been exactly 3 years as of the 21st. And you clearly don’t know/remember how long legacy FCP needed before it was widely accepted. Roughly FOUR if not FIVE YEARS, so I’d say we’re doing pretty well.
And you’ve been able to easily cycle though any number of projects that you have opened since day one. Be it via the Timeline History buttons or their respective shortcuts. I personally am glad to be rid of the unnecessary screen clutter of tabs. You only need them if you *don’t* have shortcuts or buttons, which legacy in fact never had. So it’s in fact an improvement. Habit ≠Good or better.
And like I said, you describe what I consider to be a logical progression. Start small and work your way up and make it that much better on the way. I’d say that was the plan from day one, with a little input from users here and there accordingly. But still it all has extremely little to do with how legacy FCP worked. Other than maybe a few optical similarities. If you were a programmer you’d also know how complex such seemingly minute changes are on a coding level.
-
[Craig Alan] “For myself I could bring the original media cards home with me and make a copy on my home system and leave a copy on my work station and then email the xml back and forth as needed.”
First off I would make archives of everything with FCP X and move those around AND import from them. Not only does that give you a (unchangeable) backup, but also let’s you use “Reimport from Camera/Archive” should anything be missing. Then when you set up your library, simply have *everything* stored externally. That way you simply need to transfer the (now very small, manageable) library itself, instead of an XML, which ensures that you aren’t losing anything in translation. If footage is offline in either location, simply use the above command. I’d venture to say that moving e.g. libraries around will be a cinch with the upcoming iCloud Disk, too, btw.
[Craig Alan] “But I can’t think of a way to have the original media for hundreds of projects at two locations. The cloud is just too slow.”
Like I said, I’d archive everything. That’s kinda what it’s for.
[Craig Alan] “If we set up some sort of remote access can the media lab computers log into the studio computers and see media on the attached raids?”
I don’t understand, if “the cloud” is too slow, how a remote connection could be any better? BOTH are limited by the exact same component: your connection speed. But I don’t think either scenario is in any way feasible.