Audio files from DP are to slow in Pro Tools RESOLVED

[lito]

I have recorded two Ac-Guitars on DP10.11 and now the Project is finished. I've send the pure Audio Tracks for Mixing and Mastering to another studio that works with Pro Tools 2020/11 on Mac 10.15.7 But the problem is, my tracks are running only in a slow motion on PT, the guy have said. (The tracks are not in the correct tempo and running like in "Half Time" )
The files are in 44.1 kHz and 24 bit rendering version.
Is here anyone how know's the problems between this two DAW's ? What mistakes are possible maybe on my working ?

[Bobbyd]

If for some odd reason he's doing the playback at 22.05 kHz that would do it.

[CharlzS]

Just speculating here - How did you get the files out of DP? If you play what you sent them in iTunes (or something other than DP), is the audio correct or slow? If slow in iTunes, maybe you have 'Stretch' engaged on the tracks and that may be a problem if exporting soundbites. Try bouncing the tracks rather than exporting.

[HCMarkus]

I ran into similar issues with a Cuebase user; his software was importing my tracks and automatically adjusting them to a different tempo. Does Pro Tools have such a "feature?"

[lito]

Thanks a lot for your answers. ( BTW: I've send the files with WE TRANSFER )
I make a try to bounce once more my files and look what happens. I will give you a response !

Greets

[FMiguelez]

Yeah, it sounds like a Profools mistake on their end. See this>
viewtopic.php?f=1&t=67806

[Killahurts]

It is because of the different ways these DAWs handle Broadcast Wave files. I have run into it many times with Cubase and Protools users I've sent files to. With Cubase, it's every single time.

The solution is to export the B-Wave files as Core Audio Wave files (i.e. regular wave files) to send to the other people's DAWs. For timing I always do a zero bounce (bounce the tracks from 00:00:00), since clips can't be automatically placed with just a regular Wave file, like they can with B-Waves.

If they have the sample rate and project tempo set correctly, it works every time.

[lito]

So, the problem is solved now. The guy from the studio has done a wrong import. Supposedly he must open a separate window in PT and there it's possible to drag in the files, PT does spot the files and than drag to the DAW. O.K. I don't know PT but for me it's important that the mistake wasn't by me
Many Thanks to all of you, who gave me a response

Merry Christmas !

[mikehalloran]

So, the problem is solved now. The guy from the studio has done a wrong import. Supposedly he must open a separate window in PT and there it's possible to drag in the files, PT does spot the files and than drag to the DAW. O.K. I don't know PT but for me it's important that the mistake wasn't by me
Many Thanks to all of you, who gave me a response

Merry Christmas !

Yep, this is an old issue and many PT operators always think it’s the other guy. Glad to see it was resolved.

DP’s ability to convert nearly anything upon import (if the Preferences are set correctly) insulates us from most of these issues.

I don’t know anymore how many apps and DAWs are being used to generate the tracks I mix every week. I drag the files in, the conversion window opens & closes and I’m ready to go—takes a couple of seconds or less on my iMac Pro. Glad I’m not doing this on my old 2010 iMac where that conversion could take a couple minutes or more per track — Yikes!

[dix]

I came across this issue a while back when sending .wav files to PT users. There's a pref for ProTools' Elastic Audio, buried somewhere in PT's maddeningly counterintuitive preference structure, that needed to be disabled. When enabled, EA was trying to conform the tempo info of my DP wavs with the PT session's tempo. The workaround is to export as AIFs (which don't embed tempo info i don't think) before sending.

DP10.13 had a bug fix mentioned that might address this:

DP no longer writes average tempos into soundfile metadata. This addresses issues where third party editing software may use the average tempo approximation to time-stretch sound files incorrectly.

I've stuck with the AIF export workaround so I don't know if this fix had any affect on this phenomena.

[Todzilla]

SOLVED.

When the wav files are explicitly imported from the import menu, they’re fine. When they’re imported into ProTools via drag and drop, PT tries to stretch them to fit tempo.

Explicit import via menu avoids this and preserves timing integrity.

[mikehalloran]

SOLVED.

When the wav files are explicitly imported from the import menu, they’re fine. When they’re imported into ProTools via drag and drop, PT tries to stretch them to fit tempo.

Explicit import via menu avoids this and preserves timing integrity.

Really? Even GarageBand and Performer Lite get this right.

Anyway, glad to know—thanks for reporting back.

[Todzilla]

SOLVED.

When the wav files are explicitly imported from the import menu, they’re fine. When they’re imported into ProTools via drag and drop, PT tries to stretch them to fit tempo.

Explicit import via menu avoids this and preserves timing integrity.

Really? Even GarageBand and Performer Lite get this right.

Anyway, glad to know—thanks for reporting back.

ProTools answers to no mortal.