Aindreas Gallagher
Forum Replies Created
-
Aindreas Gallagher
April 28, 2012 at 5:40 pm in reply to: Apple engineers versus an editor’s ability to set persistent in to out points in their footage.GTD = Get Things Done, relates to a class of productivity and notetaking App that generally relies heavily on semantic tagging for organisation.
https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
Aindreas Gallagher
April 28, 2012 at 5:18 pm in reply to: Apple engineers versus an editor’s ability to set persistent in to out points in their footage.but isn’t the use of favourites really just a patch?
In a sense doesn’t it distort the use of favourites? – say if I have set an in to out so I can loop playback on a shot of a skaters move – I’m just analysing it right?
The final in to out represents the result of that edit test – but that’s just me nodling – I want the in and out points associated with that action to remain – but this does not mean that it is in any way a nominated favourite.
If we are going to start default using favourites as the function of retaining in to out ranges, then it is no longer a favourite function. It is the “retain in to out” by pressing an extra key every single time.
The favourites list is no longer a favourites list, it is a random assemblage of every time I set an in to out point.
What it means is that it is an unsatisfactory hack, that distorts the feature.
Apple, as designer and publisher of the software should be able to resolve this, unless, as Phillip Hodgetts surmises – they are simply not in a position to do it, even if they wanted to.
To quote him; he views it as likely “impossible”, which leads to other interesting questions about what road Apple have taken this editing software down, and whether there actually is an architectural problem with the database itself.The reason I found the comment thread so interesting is that Andy Mees directly poses the question of whether or not Apple have made a fundamental mistake in the database model:
Andy Mees:
Is it your feeling that Apple’s FCPX designers have built the entire FCPX database model in a rigid or inflexible (and unrelational) manner?That’s the really interesting question here – this software is so unusual, it cannot retain in to out points without user intervention. If something as basic as the database model itself is wrong, then Apple will have some real problems rectifying it at this stage.
https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
Aindreas Gallagher
April 28, 2012 at 1:03 am in reply to: Apple engineers versus an editor’s ability to set persistent in to out points in their footage.[Jeremy Garchow] “”you can argue that it is marvellous in a GTD application, but I believe it is a miscue in a narrative assembly environment.”
OMG what’s a GTD? “
dude, jeremy sorry – it’s you, as in one bud, i just refuse to say one because I’m Irish mate – whenever I say you in that fashion, it’s a thought experiment, there is no you!
(although I am bitterly serious about data object entry and the need for a simplistic IO memory, spatial arrangement etc – needless to say ) 🙂
https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
Aindreas Gallagher
April 27, 2012 at 11:43 pm in reply to: Apple engineers versus an editor’s ability to set persistent in to out points in their footage.[Jeremy Garchow] “you can have more than one favorited range per clip, and that clip can be represented across multiple keyword collections. “
yes, maybe, but not really.
If you have an editing system, with objects entering into it that you apprehend – either they are entities that you recall prior actions to, or they are not.
I think FCPX is very clever, but I’m not sure the intellectual throughput refers to, or respects, the chain of events regarding specific video object entry.
FCPX feels like it wants to disperse all object entries into an undifferentiated tag data cloud.
that’s interesting, but I find it a cold paradigm as an editor.
you can argue that it is marvellous in a GTD application, but I believe it is a miscue in a narrative assembly environment.
https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
Aindreas Gallagher
April 26, 2012 at 8:48 pm in reply to: A Question for Working Professional Editors Using FCPX.[Jim Giberti] “Unattributed of course.”
well, that goes without saying..
https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
Aindreas Gallagher
April 26, 2012 at 7:30 pm in reply to: A Question for Working Professional Editors Using FCPX.[Andrew Richards] “The Project and Event database files are CoreData-based and leverage SQLite (one of the persistent data stores that CoreData can address). So there is some OS-level stuff that could be to blame for the problems we’ve seen reported, or it could be app-level stuff incorrectly calling CoreData. Or both. Only the dev team could know.
One thing I find really interesting is that Lion added a new CoreData class (NSIncrementalStore) that looks like it could be used to point FCPX at shared Events and even shared Projects on a shared database like a SQL server.
“there you go see? – someone who actually honest to God knows what they are talking about.
I bookmarked this reply – next time I bluff the database, I’ll sound more knowledgable like.https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
me FCP boy too – a pretty substantial shift to premiere wouldn’t surprise me greatly – it looks the ticket to me, and its got a fair bit of a head of old steam going on – proof in pudding though – if we all sit down to it and find ourselves rocking away fairly merrily in a couple of weeks, then that’ll probably start to accumulate as a shared experience.
If it tastes as good as the spec sheet, GUI and trimming tools look – we’re all going to start saying it to each other aren’t we? If it becomes self evident that it’s up for it, and its the easiest reach over from FCP… …..well, we’ll see – we won’t know for months yet probably?
I just got a full retail license design premium CS5 for two hundred and fifty quid off gum tree – that’s me upgrading to production premiere before may 7th to 5.5 for 380 quid and getting 6.0 into the bargain.
Don’t anyone please ask me what I was using before this. It was shameful but now I am legit –
thus do we see the power of CS6.https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
sure, of course – that stands to reason. 6 isn’t even out yet. anyone who is going to be premiere is say six months or so away from being premiere in anger? FCP7 will take quite a while to bleed out anyway.
The point though is that switching to premiere as you put it there… involves booting up PPro CS6, which you presumably will have anyway. And it just sits there gathering steam while you ride out FCP7 and roadtest CS6. Runs on the same hardware, can (more or less) speak to the same input video hardware and monitoring, I think its the natural successor to FCP in a broad range of FCP scenarios because it was built specifically to replace FCP. And it was built by Adobe, who know how to put this stuff together.
https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
Aindreas Gallagher
April 25, 2012 at 11:33 pm in reply to: A Question for Working Professional Editors Using FCPX.[Thomas Frank] “For the RAM yeah a clear RAM function would be cool. “
The application sucking up RAM like crazy as it does, may -*may?* be an architectural problem – Apple may have overshot realistic workflow and hardware – if so, the problem could prove persistent. I’m making all this up, but it could be akin to the potential database flaws occasionally mentioned by others. If it’s real, and its a problem, Apple may not be in a position to unpick certain problems without gnawing at fundamental threads.
the things that freak me out as a goggling half observer are: incidents of project corruption, incidents of event corruption, autosave fails, project bloat, and a possibly incorrect approach to the database substructure itself. Some people on here really know what the FCPX database is made of, there were discussions, I don’t recall them being cut and dried.
there was also a ‘rollercaoster’ post a bit back that dealt with a pretty much scarifying, completely irrecoverable failure of the application that destroyed both projects and events in progress with multiple attempts by apple to resolve it.
CC attributes with power masks in realtime on 2K – cool. range based keywording – cool. Timeline – having a laugh. Chrome – laid on with a trowel. Industry pickup – near Kelvin zero.
It’s early doors, its a deadly serious software initiative, but yet –
in afficionados like Evan Schechtman and the financially invested trainers like Jordan and the ripple training guys, third parties like Hodgett et al, Apple have a fairly reliable chorus, but this software can only drop its pants for so long in this kind of a market, you’d have to think.
https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
James Murdoch, Rupert Murdoch, Jeremy Hunt, David Cameron.
Four little Indians had a nice little plan to kneecap the BBC and serve its head on a platter to BSkyB.
Not looking so rosy now!
Didn’t the BBC make the odd on air mistake pronouncing Hunt’s name? something about the first consonant getting swapped out? 🙂
https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics