Aindreas Gallagher
Forum Replies Created
-
yes, the apple FCPX white paper outlining ongoing critical failures in the FCPX plug-in architecture, resulting in render corruption, with said white paper referencing compressor as an open ended stop gap for all FCPX users was enlightening.
Either that or Apple never said a word about this, for three months and counting.
An awful, awful lot of people use MB Looks Craig. Not to mention the other plug-ins that got hit.come on – seriously? Apple’s silent carry on is almost becoming a joke.
What is the benefit? It’s not leaking a new iphone is it?
It goes to the developers cited at the verge on Core Data – they have no clue when, and if, Apple will get on top of it.Red Giant have no clue when, and if, Apple will resolve critical failures in their plug-in architecture.
A blog would be nice. But sure then the mystique is gone right?
https://blogs.adobe.com/kevinmonahan/
so that’s one PPro guy.
to point out: Adobe are a yellowstone faithful geyser of info on their product, flaws included, with the direct involvement of about the entire PPro team.
Apple’s silent Wizard of Oz schtick, to all comers including professional partners-
that act feels like it is getting rapidly old.https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
[Franz Bieberkopf] “PPro projects are structured”
badly is the answer. It’s basically AE in effect – which is close to unusable in a modern editing system.
My completely ill informed perception is that its literally prehistoric project management architecture. One project at a time, relinking is a nightmare…that said, a birdie told me that is about to very, very radically change.
Also If DRW is on the money, we’re going to see an end to .5 releases – and a fundamental re-ordering of project sharing management in PPro.
If he is right, we go direct to PPro 7, and adobe lay down fairly serious cards.
that said – from the hints on here from reps – the audio channel oddities with assignment and audio channel based keyframing are here for a bit.
Also part of me isn’t sure whether the benefits of anywhere are bedded into day to day single user basic software operation.
I would be really surprised if the current project limitations survive the advent of adobe anywhere tho.I don’t think they could leave that AE style edit project handling crud in the next version – I’m presuming anywhere does bleed down to all basic footage and project handling architecturally in 7, outside of the specifics of the anywhere proposition.
Project handling in PPro cannot stay as it is.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
[Charlie Austin] “it would be nice to temporarily “disconnect all” if you need to.”
god rather yes please. I throw pies at the software as a hobby really at this point – but there is a lot I like.
that said – the timeline behaviour will honestly never be one of those things. It really does form a brick wall of no thank you please.https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
two cents in – I bookmarked this one a few months ago too – interesting that the early impression was that they had based it on the FCP server engine. there are implications for project sharing in core data apparently. he also… does say some positive things about core data.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
Perhaps if you were just to re-read this section steve.
There is no inherent superiority in FCPX due to is use of Core Data, and indeed I think it contributes to a lot of the sluggishness observed when a project gets complex and necessarily performs a lot more I/O on its SQLite database for each new timeline input.
As pointed out – its the core data model pointing to the SQL database that may be a source of problems – the larger question relative to the verge article is whether Apple have the manpower assigned or basic competence to resolve the issues arising.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
Magic bullet and many other plug ins still outputting random bad frames apparently. I’m sure apple are on it. A few months later.
https://www.redgiantsoftware.com/blog/2013/01/24/looks-mojo-fcpx-10-0-7/
There is a serious bug in FCPX that causes many plug-ins (not just Red Giant’s) to output bad frames. We have been working with Apple to help them figure out a fix, but so far nothing is forthcoming.
Gee.. almost sounds like all those developers wondering what’s happening with core data syncing and hearing absolutely nothing at all.
Nothing quite like a mysterious corporation as a professional partner is there?Today is my day for piling on apparently.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
oh indeed -I’m totally making all this up myself. As you say – the only voice I would buy would be Andrew Richards.
In the quote he does cast doubt on the repeated calls to the SQL database from the timeline tho. there – don’t I almost sound plausible there like.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
Salford itself is apparently moving to Fife.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
you don’t have any truck with david’s reading of the point that the fundamental issue might lie with the core data model itself?
not to mention that there’s four guys and a cat at apple handling the whole thing?https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
good god – we’re pushing too hard. ease off everyone – they’re getting dangerously dramatic. 🙂
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics