Any way to stop Pro Tools from changing sample rate automatically?

[robpertraymond]

Hey folks,

I have a Pro Tools 12 session at 96K. As I was playing the session, my headphones got unplugged accidentally. This caused the audio to start playing at a slower speed, and so I exited the session and accidentally hit Save as I did. I didn't realize but this ended up saving the session at 44.1K. I had to go back to a backup session that was still at 96K in order to get my audio to play back at the correct sample rate. I understand that I could also have created a new session at 96K and then imported the old session data (unchecking SMC), but from what I understand, this would just be importing the 44.1K tracks into a 96K session, so I would have a substation reduction in audio quality.

Anyways, my point in posting this is to ask if anyone knows why the hell this happened in the first place? I just began using Pro Tools 12, but in Pro Tools 10, if my headphones got unplugged, the session would just stop—it wouldn't automatically convert the sample rate. Is there a setting that stops this from happening? I got lucky that I had a backup that was essentially up-to-date, or else this could have been a major issue.

Thanks.

[BScout]

You can't change the session sample rate once it is created. I don't know what you've done (everything you've written seems weird -- where are these headphones plugged in? What is your audio interface?) but Pro Tools doesn't change sample rates for a created session. Not possible.

I would check two things: did you change your audio interface's sample rate? Did you just hit 1/2 speed playback? (shift+spacebar or from the dropdown menu of the transport)

[robpertraymond]

Sorry for the confusion. I'm not using an interface, just going through the Pro Tools Aggregate I/O on my macbook pro. My headphones were plugged into my laptop directly. Definitely didn't hit shift+spacebar.

The sample rate was at 96K, it's now at 44.1K. Pro Tools definitely changed it without notice. I was as surprised as you are.

[BScout]

Where are you seeing this sample rate change? In session setup, top left corner?

[robpertraymond]

Yup, exactly.

[BScout]

can you post a screenshot of your Audio Midi Setup window with the ProTools aggregate interface having focus?

Removing /plugging in headphones should have no effect on Pro Tools.

What macOS version are you running and which exact Pro Tools version (2018.4 ?)

[L-Dogg]

This has been happening to me recently and it's driving me nuts. I have been learning a bunch of tunes for a new band I am in....what I did was record them all into PT so I could have the set list all on one track to play along to.

Believe it or not it made songs in iTunes play back slowly.

I have an 8 channel stereo mixer connected to my Eleven Rack, it's outs to powered Event 20/20 BAS's. I use this to connect different sources, CD, DAT, Numark turntable etc and to play these back through the computer/powered monitors....independent of opening a PT session.

So anyway, the computer was on but Pro Tools was not open...and I connected my iPhone to channel 1 on the mixer, opened iTunes and started playing tunes and they came out slow. I think I had gone into System Pref's in the Mac Pro to select the output and I may have selected PT Aggregate I/O.

I can see this affecting playback speed in PT (not really but just say for arguments sake)......... but iTunes? It seems like such a separate deal and PT wasn't even open etc.

[robpertraymond]

Screenshot 1 was taken when Pro Tools was not open. The second screenshot (with the 96K sample rate) was taken when the session is question was open.

I'm using Pro Tools 12.8.3 and running it on High Sierra 10.13.3.

[arn87]

Hi Robpert, I'm having the exact same issue, this is driving me nuts! How did you fix it?? Thanks

[musicman691]

Originally Posted by arn87

Hi Robpert, I'm having the exact same issue, this is driving me nuts! How did you fix it?? Thanks

System info?
There's a lot of good people here but without system info we can't help. Not to mention you're reopening a year-old thread.