And speaking of things I don’t fully understand,,,

[Jeremy Garchow]

[TImothy Auld] “In understood exactly what you were saying David, and I did not take that personally in any way. But thanks.

bigpine”

David said what I meant, Timothy. I was not attacking or vilifying you, I was seriously trying to help you out.

I am sorry if I offended you in some way, it was not my intention.

[Jeremy Garchow]

[Bill Davis] “Why can’t you just select the original clip, clone it with “new compound clip” – detach the audio from that and if you need to “re-attach it” just replace the un-synced one with the original?”

The nice thing about detach audio is that it allows you to keep any audio adjustments already made (as opposed to break apart items). It also allows you to assign multiple roles to individual audio tracks, which will probably be pretty crucial to multicam, and other workflows. A reattach audio would, theoretically, then allow you to reattach any new adjustments and roles back to the video leaving anything in place. As far as I can tell, a compound clip can’t have these separate roles, and if you replace the audio, you would lose the roles and the audio adjustments, unless you preassigned the roles in the browser.

Like with a lot of things in FCPX the foundation seems to be there, we just need more control of it.

[Jeremy Garchow]

[Andreas Kiel] “Current FCPXML is pretty poor (also with documentation) – I even would say it’s not a version 1 release. Anyway it’s there and it’s a step forward.”

At this point, would you say FCPXML rather incomplete?

Do you see a chance of it getting any better?

If the underlying language is broken, that’s a pretty telling sign.

[Timothy Auld]

Thanks.

bigpine

[Herb Sevush]

After looking at your post again I realized I had a few more things to say.

Currently Legacy handles 16 angles with live updates and up to 124 angles in all, with only the first 16 being updated live in the viewer. There is no difference coding for 16 than for 25 live angles, it’s just a matter of how much bandwidth your system can handle. With modern drive arrays and Thunderbolt connections 25 proxy angles should be possible. You just show your ignorance of multi-cam workflows when you get so flustered.

[Bill Davis] ” I don’t want to turn my laptop into your idea of a multi-cam monster. At ALL.”

#1 – nobodies asking you to do anything with your laptop,
#2 – as for your wants, last I looked you weren’t a member of the design team. At ALL.

[Bill Davis] “Maybe at some distant future point, we’ll have some kind of UBER-WiFi that lets some kid sit at their laptop and grab 25 plus real-time feeds from the cel phones surrounding a BMX race, but I’m not holding my breath for that.”

That distant point is now. For a “futurist” like yourself I’m surprised you don’t understand that. And it’s not a BMX race, it’s more likely a protest at Zucoti park and the kid is downloading clips from YouTube and syncing them by audio.

[Bill Davis] “Anyway, I personally I don’t want the dev team to spend a minute coding in stuff that only a tiny fraction of the users will ever really need.”

[Bill Davis] “It’s starting to sound like I’m listening to a parent for whom it doesn’t matter how decent and accomplished the kid the daughter brings home might be – that kid will never, ever, EVER be “good enough.””

And your starting to sound like someone who thinks X was designed expressly for him. It wasn’t, it isn’t.

Herb Sevush
Zebra Productions

nothin’ attached to nothin’

[Andreas Kiel]

Jeremy,

I would say current XML is pretty incomplete and if I would have the time I would take the same approach done by the foolcut people.

If you look at the XML documentation of FCPXML and remove empty pages, the disclaimers and those pages which link to nothing or just have 1 line of text you end up with 5 pages, while the legacy XML documentation (doing the same things) is above 100 pages. So I think there is a lot of stuff missing with this release.
Quite a good example are subtitles with FCPXML. As soon as you are export a project you are loosing any custom formatting. You could some back if you do have the matching Motion assets. But at this point of time there is no documentation for that. Legacy version of FCP XML allowed to extract the basics (font, size, style and alignment) of a subtitle even if you didn’t have the generator installed. Now every kind of subtitles are Motion based and formatting (same as in FCP with Motion based text generators, but at least some stuff came over). With FCPX you can’t import an FCPXML when you changed base formatting for subtitles, everything will be reset to some kind of default. Export XML and don’t change anything within the XML and import that XML you exported a second ago and you are screwed up. That’s poor from my point of view.

You know me long enough to know that I quite often was not happy with the different versions of FCP and the XML handling and did say it loud. At the moment I regret I have to say this new version doesn’t look very promising.
Regarding subtitles PPro is more or less as same as bad. Multicam limited to 4 might not be enough for many people – but at least some basic stuff is there.

As said before the only thing we can do is to sit and wait for the next version – but for me I’m not that confident. Big things need to be done.

Regards
Andreas

Spherico
https://www.spherico.com/filmtools

[Jeremy Garchow]

[Andreas Kiel] “As said before the only thing we can do is to sit and wait for the next version – but for me I’m not that confident. Big things need to be done.”

Thanks for weighing in. Do you think big things CAN be done, or will simply not be done? 🙂