[Rikki Blow]

I’m the world’s idiot on codecs, but I’ll throw in a crazy idea that might just work.

I export 1080 movs from FCPX regularly, but require an mp4 version for posting on twitter – MOVs simply don’t upload on that platform.

So, on a Mac, I simply rename the .mov to .mp4, and say yes when the warning pops up, and hey presto, it uploads to twitter and plays fine.

Clearly no data loss with that method.

Whether it will work on files your client needs, I don’t know, but it might just be worth a try.

Happy for someone to point out why this is working for me on twitter, and/or the general error of my ways.

[Rikki Blow]

yep the two adapters in a row have been working absolutely fine for me here – loads of legacy firewire drives needing connecting to my 2016 touch bar jobbie.

[Rikki Blow]

thanks. certainly seems to be the case.

i’d normally agree with you totally, but as these were straightforward IVs with no other sounds/music etc to be mixed in, but some editing to be done, it just seemed that if i could set up the eq and slight compression on the events, as well as select the correct audio channel (lapel rather than top mic), then i could go through and favourite all the sections i wanted to use, and chuck the favourites on the timeline. also if i then want to throw in some other bits to try, they’re all ready too.

instead, i’m having to set up the first clip on the timeline the way i want it, and then copy/paste attributes every time i add another clip to the project.

it’s only a small annoyance, but when you’re trying to work fast, any little advantage helps, and if i could copy and paste attributes on the whole clips in the event browser, there’s be, in certain circumstances, a few less key strokes.

no biggie, just wondered if i was missing a trick, but appears not.

[Rikki Blow]

…oh AND, a biggie.

when i expand audio on two adjacent clips to do some fine editing, the two audio parts will only sometimes seperate out to lie above or below eachother – often they’ll stay on the same horizontal, so i can’t easily compare their fade ins/outs where they overlap, having to switch from one to the other to get access to their respective fade handles.

this never used to happen before 10.3, and it’s a really annoying UI glitch.

[Rikki Blow]

After working with 10.3 for some time, have found following bugs recurring.

Just occasionally the pop-up data balloons on moving clips or adjusting audio volume etc will go blank and gove no info.

Quite often, some of my keyboard short-cuts just stop working – eg Command-tilda no longer hides browser, and Shift-? no longer plays round a point. Quitting and opening gets them back, but it happens quite a lot and I use these often, so quite annoying.

Sometimes clip names in browser just disappear – just shows a load of blanks – most often come back by clicking around.

[Rikki Blow]

ha. well i wasn’t going to pay to do this little job! have handed back the files to originator and said he’ll have to convert them if he wants me to do something with them. best option.

[Rikki Blow]

yep, this seems to be new to 10.3.
FCPX always used to remember exactly the state you left it, but now it opens libraries with its own choice of project.
i’m sure there must be some logic rather than random, but i certainly haven’t figured it out yet.
noah’s advice is sound. another quirk you need to remember to work around.

[Rikki Blow]

i got all hopeful seeing this post.
i assumed they were blackmagic, yes.
however, i downloaded RawMagicLite, and it just doesn’t recognise any of the mlv files – they’re all greyed out, so i guess they’re either corrupt, or they’re some other kind of mlv file – is that a thing?

[Rikki Blow]

thanks for the pointers jeff.

searching for mlv_dump took me to some nerdy forums where people were having difficulty getting command line instructions to work on sierra.

what fun?

i think in future i’ll follow your principle and demand that the originator does the conversion!

meanwhile, if anyone can suggest a simpler solution on sierra, i’d be very grateful, otherwise, i’ll have to wade into these murky fora and get my terminal chops going!

[Rikki Blow]

i have a similar issue (on 10.2.3 – maybe it’s fixed in 10.3?) with importing from cards from audio recorders.

Once imported, FCPX tells me it’s complete and offers me the option to EJECT the card.

I click EJECT, but then on actually removing the card from my laptop card slot, I get the OS message that I should have ejected it first.

But if I try to eject it first using Finder, I’m told FCPX is using it – even though FCPX apparently gave me option to eject it after the import was complete.

I wish FCPX would let the OS know it had ejected the card!

My only option to keep the OS happy is to quite FCPX and then go back in. When I’ve got 2 or 3 audio recorders on an event, this is a bit annoying.

Not wishing to hijack the thread, but it sounds like the same issue in a slightly different guise, and it seems to be more of a bug than an attempt to maintain data security. Why give the option to eject if you still can’t?