[Andy Mees]

These issues have been reported over and over again … including to Apple.
One can only assume that it is a extremely complicated fix that would include fundamental design changes to the software’s code base, why else would it remain unfixed?

I am one of those that happily report that MM works consistantly and reliably for me, but always with the caveat that one needs to manually manage any speed affected clips (including stills and variable or constant speed changes including reverses) and rebuild the effect post MM. Similarly you need to avoid nested sequences. FWIW another issue is that Media Manager can not move clips greater than 2GB in size between network locations. Anyway, the point here is that many large organisations are using MM effectively on a daily basis, but all that are doing so are fully aware of the limitations and so take steps to avoid them.

It aint pretty. In fact its a royal pain in the proverbial. There’s no way Apple are not aware of these issues and their very specific causes. Hence my conclusion above … there must be some fundamental reason for not addressing the problem.

And don’t hold your breath waiting for it either, this is not a minor point release issue, no way (although I’d be ecstatic to be proved wrong).
Many were hoping FCP5 was the major rewrite that would fix it. Now many are hoping that it will happen in FCP6.

Just my 2 cents.

[Andy Mees]

DVCPRO50 is widely regarded as equivalent in picture quality to Digibeta.
as far as compressed 8 bit codecs go, IMX50 is suppsed to be a little better.

We’ve been using DVCPRO50 to master all our promos since the start of the year … fwiw we broadcast over 50 television services in eight languages to more than 300 million viewers across 53 Asian countries … I’m not aware if any of our viewers ever noticed the difference (but then some of our viewers are probably watching in balck and white)

[Andy Mees]

unfortunately, beyond the capabilites of Apple’s FXScript architecture, I don’t know what might be possible…
as i understand it, the DV Start/Stop detection is something implemented by Apple and is not a ‘filter’ per se ?

certainly, the statistical analysis of the frame content could be used to indicate potential whip pans and crash zooms
but as an FCP plugin i don’t see how this could be implemented effectively

and you’d STILL have to look through your footage anyway, its such a fundamental part of the process … and in a non-linear world we don’t even have to spool through it. we just scrub real quick hitting the m key where the good shots start and stop. BAM. we’re marked up and good to go, we’ve filtered out the the crash zooms and whip pans along with all the other crap too.

everyone may (or may not) have one great idea/invention in them … but this isn’t yours, Martin. 🙂

[Andy Mees]

in 10.4 the max RAM FCP can address is 2.5GB … previously i had understood it was 2 GB but i could have been wrong

[Andy Mees]

Martin

it was a poorly thought through idea that betrays a certain level of inexperience … hence the less than constructive replies.

regarding the practical implementation of such a filter … have you ever seen an FCP filter that actually cuts your footage, or flags it in any way other than by triggering a ‘render bar’? i haven’t, but that doesn’t mean that such filters don’t exist.

end of the day, you’ve got to look through your footage anyway … might as well just mark it up by hand

cheers
Andy

[Andy Mees]

https://fxscript.org/

[Andy Mees]

when you saved it out of photoshop, what did you save it as? did you flatten it?

check out these free guides for using photoshop images with fcp
https://www.kenstone.net/fcp_homepage/basic_ps.html
https://www.geniusdv.com/photoshop%20final%20cut%20pro.php

hope it helps
Andy

[Andy Mees]

hi Eric

which edl format did you export to? not that it should matter.
when exporting and importing edls FCP should definitely preserve the reel info , and always has in my experience.

i’d say give it another try … if in doubt try, using a diferent edl format
then check for reel info again (select clip then choose Edit>Item Properties>Logging Info..)

cheers
Andy

[Andy Mees]

hi Mark

sounds like you already found the audio outputs tab inder the sequence settings … where you set the grouping to dual mono.

now before you output, you need to assign the track output channels… right click in the lock/autoselect area of each track, the first option in the drop-down menu is audio outputs, select the apropriate output track from the submenu. do this for each track and you should be good to go.

hope it helps
Andy

[Andy Mees]

hey Stuart

you didn’t mention how you exported, settings etc – those kind of details really help to narrow down the problem.
however, when you do the export, one thing you might want to make sure of is that you have checked “make self-contained” … else if the file is opened from a different machine which does not have the access to the origina media, you make get a “file missing” error

hope that helps
Andy