posties: any issues with Apple Lossless?

I had a client complain yesterday that a mix I sent was pulled down,
and drifting long over the course of a ~22 minute TV show.

This was a completely 29.97/48 job. No pullups or downs anywhere in the
workflow. It was, in fact, a remix of a job I'd done last week... which
synced perfectly.

---

The show was cut in FCP and shipped to me as OMF. I mixed at 48k
against a 29.97/48 Quicktime reference. I shipped back via FTP as an
Apple Lossless .mov, converted from an AIFF with 2-pop in Peak. When
the client dropped my new mix into their copy of QTPro, it synced
perfectly.

This is a basic workflow I've used with this and other FCP clients for
a couple of years. It also works perfectly when they have me mix
against BetaSP/Doremi, either drop or non, so I'm sure it's not a QT
video issue here.

I'm suspecting something went wrong in FCP's conversion when they
dropped my .mov mix in, and it's just a coincidence that when the
editor measured the drift at the end, it looked like a pull down issue.
I had a similar loss once before, when doing conversion in an early
version of SoundGrinder.

I suggested they re-convert the .mov to AIFF in QTPro - or any
competant audio software. The client called back to say it got fixed,
but didn't know exactly what their editor did to fix it.

Anybody see anything like this? Any ideas what was really going on?

--
Jay Rose CAS
tutorials and other sound goodies at dplay.com
email is "jay@" plus the dot-com in the previous line.

On May 23, 7:16 am, Jay Rose <see_sigf....DeleteThis@nowhere.com> wrote:
> I had a client complain yesterday that a mix I sent was pulled down,
> and drifting long over the course of a ~22 minute TV show.
>
> This was a completely 29.97/48 job. No pullups or downs anywhere in the
> workflow. It was, in fact, a remix of a job I'd done last week... which
> synced perfectly.
>
> ---
>
> The show was cut in FCP and shipped to me as OMF. I mixed at 48k
> against a 29.97/48 Quicktime reference. I shipped back via FTP as an
> Apple Lossless .mov, converted from an AIFF with 2-pop in Peak. When
> the client dropped my new mix into their copy of QTPro, it synced
> perfectly.
>
> This is a basic workflow I've used with this and other FCP clients for
> a couple of years. It also works perfectly when they have me mix
> against BetaSP/Doremi, either drop or non, so I'm sure it's not a QT
> video issue here.
>
> I'm suspecting something went wrong in FCP's conversion when they
> dropped my .mov mix in, and it's just a coincidence that when the
> editor measured the drift at the end, it looked like a pull down issue.
> I had a similar loss once before, when doing conversion in an early
> version of SoundGrinder.
>
> I suggested they re-convert the .mov to AIFF in QTPro - or any
> competant audio software. The client called back to say it got fixed,
> but didn't know exactly what their editor did to fix it.
>
> Anybody see anything like this? Any ideas what was really going on?
>
> --
> Jay Rose CAS
> tutorials and other sound goodies at dplay.com
> email is "jay@" plus the dot-com in the previous line.

Find out what their project vs import setting were. I'll bet they did
it on the import side. You've probably read about the various changes
in how FCP imports now, and if it thinks what you are importing is at
a different SR or TC than the project it assumes you want a "pull" on
the way in. (Loaded gun.) There was a mention (I think) that going
back to the FCP as a QT .mov was safer since FCP didn't try to do the
"magic" mentioned above to QTs. (Check @ DUC.)

Philip Perkins