[Robin S. kurz]

Wow. Thank you Ronny! I’m truly flattered! And after all that work it’s very nice to hear that!

But… seeing that there already are several very competent offerings (who are also friends), such as Ripple Training and others, I’m not too sure how that would fly. But believe me, you’re not the first to suggest doing an english version. Only it’s just a *huge* amount of work and with the german version I’m at least (currently) the ONLY one with comprehensive training. So kinda the big fish in a little pond as opposed to the other way around, as it would be in the english language market. And even though I have a finished product, the english version would only be nominally less work… and just the thought of that right now…. eek. 😀

I still have a german multicam training to release next week, then I just want to take a friggen BREAK! 😀 After that I still want to finally do a MOTION training, which is really my true pet project, coming more from a compositing background.

But again, thank you very much for your input and I’ll certainly keep your suggestion in mind and ponder it (again) when the (spare) time comes! 😉

Cheers!
Robin

[Robin S. kurz]

[jean mathis] “This should be answered if you read the title of the post (share menu greyed) it’s hard to be more accurate I guess.”

You’re right. My bad and apologies.

But the share menu having been greyed out can’t actually have had anything to do with reimporting the material. That will most likely simply have meant that you had the wrong window active when you pulled the menu. E.g. the Event viewer and not the Project timeline. This can ironically easily happen *on your way to the menu* by passing over the event too slowly, therewith shifting the focus to it. Has happened to me (too) many times in the past also. Which is why I exclusively use the Share menu in the toolbar. It can’t happen to you there. It’s much closer anyway. 🙂

[Robin S. kurz]

I personally highly doubt you have anything to worry about. Whereby after the import/conversion FCP gives you the explicit option to SAVE the old versions of all the projects (whilst barely adding any data btw, because the files are hard-linked). So if you choose to do that and push comes to shove and something actually DOES go horribly wrong, then you can always just pop back to the old version(s). That of course would also entail your archiving the old version of FCP first…

[Robin S. kurz]

[Martin Leroy] “Why is FCPx always displaying sounds TC as 60fps? “

I wouldn’t say “always”. That’s simply the fps it will in fact been recorded at, i.e. what the recoding device was set to.

[Robin S. kurz]

Just curious: is there a particular reason why you chose to take the (usually, from experience, unnecessary and bug prone) detour through PE?

[Robin S. kurz]

Maybe try re-exporting an AAF (or even OMF or XML) from Resolve. But it will more than likely be due to the fps discrepancy, yes.

[Robin S. kurz]

The one has nothing to do with the other, in case that’s what you were thinking. The red line, as already stated, merely indicates a “rejected” clip, which is done by selecting it and hitting the delete key. So you probably tried deleting it, only THAT is done with CMD-DELETE. It is just the opposite of a “Favorite”, so for the sake of organization within the event. Hit CTRL-H (i.e. “Hide Rejected”) and it will disappear.

One would need to know what error message you are getting when it comes to the export. As they say, “doesn’t work” isn’t a useful or constructive error description.

[Robin S. kurz]

I highly recommend reading this first: https://www.philiphodgetts.com/2013/12/upgrade-your-events-and-project-to-fcp-x-10-1-libraries-the-better-way/

I personally haven’t had any issues worth mentioning and I’ve upgraded a very large amount of events/projects/libraries. Some from nearly the first version to just the previous version.

[Robin S. kurz]

[Bill Davis] “the default is that holding the shift key while dragging constrains movement to the horizontal or vertical axis. “

Nope. Not for published OSCs.

[Patrice Freymond] “Go by numbers in the inspector ?”

Also a no-go, since the individual points do not have a parameter value. These were not published (for some odd reason). But one could simply go into the Mask filter with Motion and publish the individual position parameters of the four “Crosshair” layers oneself, after which they’d be available in FCPX.

[Robin S. kurz]

[Bill Davis] “Yes, IIRC that works for compounds that you create in a storyline. But I’m not sure it works for compounds you pre-creates in the Event Browser. I think the changes you make there are inherited across all instances of the compound placed in any storyline across Events.”

Changes made to ANY compound clip (however that is relevant here) is recursive to it’s existing instances, even across multiple projects, yes. It’s irrelevant how and where you created it.