Forum Replies Created
-
[Jeremy Garchow] “Bloat…I think that’s been solved, time to move forward.”
Bloat with compound clips has been solved well. I’m talking about this:
[Oliver Peters] “Absolutely. One of X’s very big weak points. Right now there is no way to effectively manage (within the application) a production that would generate 100 Events and 100 Projects. I don’t mean the software can’t handle it (though I have my doubts) – rather that the interface does not effectively support it for the operator.”
I think there’s a potential bloat problem with the event and project library databases in situations like Oliver describes. What’s the largest number of projects you’ve had in a library? How was the load performance? I’m curious because I even though I only have a handful of simple test projects, my project library load time is not great.
[Jeremy Garchow] “I am just curious as to why it’s all of a sudden a bad idea to make an NLE a hub. Isn’t that what everyone was so pissed about on day 1? You couldn’t get data in or out of it?”
Can you get tags and keyword collections out of it?
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Oliver Peters] “it feels like Apple is trying to do the same thing as they tried with iTunes – namely make it a hub for everything. Not sure it that’s really the best approach.”
[Jeremy Garchow] “Why?”
Bloat and proprietary vendor lock-in for starters, maybe?
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Aindreas Gallagher] “As you say – like a lot of people I like a lot of what is in FCPX – but the timeline is beyond problematic, and the timeline is where I do my job.”
Bingo.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
David Lawrence
October 30, 2012 at 2:40 pm in reply to: Big Shakeup At Apple – Scott Forstall Is Out[Chris Harlan] “Whoa. Disagree? I think you are reading more into my statement than I meant to have there. Sorry, if I was unclear. I simply meant give examples of where it exists in editing software, and to say that it doesn’t really add much value at all. “
Oops! My bad. I completely misread your statement. Sounds like we’re on the same page 😉
[Chris Harlan] ” tend to hate audio plugins that look and function like racked equipment, especially when there are GUI metaphors that could offer much better control. I’m also not a fan of fake brushed metal buttons–say the Launch Pad icon, for instance.”
Ever play with Propellerhead’s Reason? https://www.propellerheads.se/products/reason/
Flip the rack and use animated virtual patch cables! It’s the ultimate in meta-racked-audio-skeuomorphism!
At least you can make cool sounds with it…
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
David Lawrence
October 30, 2012 at 6:42 am in reply to: Big Shakeup At Apple – Scott Forstall Is Out[Chris Harlan] “Other than an icon that looks like a razor blade to signify a tool that makes cuts, a mixer that has all the visual flair of an actual plastic and wood mixer, or audio plugins that look like tubes or rack-mounted units, not much. VCR-like buttons, perhaps, for play/FF/RWD/REC. And that little red light, when you are recording, of course. “
I disagree. The same design attitude that wallows in the comfortable literalism of ugly skeuomorphic control surfaces is the same design attitude that ignores the science of color theory in a color-correction UI for the sake of comfortable simplicity. In so far as these are the tools we use for movie making, these design decisions affect us as movie makers. I will not miss Forstall’s influence on Apple UI design.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
David Lawrence
October 30, 2012 at 5:56 am in reply to: Big Shakeup At Apple – Scott Forstall Is OutMore reporting and links here:
https://www.macrumors.com/2012/10/29/scott-forstall-reportedly-forced-out-of-apple/
and
https://bits.blogs.nytimes.com/2012/10/29/apples-mobile-software-and-retail-chiefs-to-depart/
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
David Lawrence
October 30, 2012 at 1:48 am in reply to: Big Shakeup At Apple – Scott Forstall Is Out[Steve Connor] “This could be very good news, I’m looking forward to what Mr Ive does with Apple’s interfaces”
Agreed. I think this is a ballsy move by Cook and huge win for Apple. I’m very optimistic.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Jeremy Garchow] “But, since there’s PIOPs, only the PIOP range gets rejected, not the entire clip, so when I go to hide rejected, only the PIOP ranges disappear instead of whole clips.”
Would a “Forget Ranges” command that could be applied after selecting clips in the event browser fix it for you?
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Jeremy Garchow] “In even more playing around, this isn’t very fun.
I appreciate the need for PIOPs, I use them all the time in other NLEs.
But FCPX doesn’t work that way.
I think this breaks (or significantly hampers) a really strong suit of FCPX and that is the organization methods.”
Jeremy, when you have a free moment, I’d love to read a more detailed post on why you feel this way (and perhaps what might fix it for you.) I’m genuinely curious.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Bill Davis] “Sorta reminds me of back during Legacy V1. In FCP’s very first version, JKL transport controls weren’t supported. I got used to doing timeline transport using the non-standard keys – then had to take a couple of weeks to re-train myself when they finally implemented JKL to accommodate the AVID folks.
Kinda the same deal here, I think.”
From a UI design perspective, there’s actually a subtle but important difference.
In the case of Legacy’s transport, you could use other keys to accomplish the exact same result.
In the case of PIOPs, that functionality simply didn’t exist. Until today!
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl