Here’s how to get audio from a 96kHZ session using PreSonus gear.
On a recent session, I was given 24-bit 96kHz stems to which I need to add acoustic guitar. Since I nearly always record 24-bit 48kHz, the higher sample rate is not familiar territory for me, but it didn’t seem like it would be an issue.
To set up for the session, I switched both my RM32AI and Pro Tools to the higher sample rate and restarted Pro Tools. I thought that was enough.
On the CS18AI I could see the meters bouncing, but no audio was passing to the speakers. I tried switching back to 48kHz and everything worked fine. Audio simply would not pass through at 96kHz.
After troubleshooting using every bit of Google foo I knew, I finally found a forum post that enlightened me. One of the shortcomings of AVB networking is that it can only pass audio at 48kHz or lower sample rates. Boom.
I had been using the monitor outputs of the CS18AI to send mains audio to my studio speakers. The CS18AI receives it’s audio feed via AVB, which is why audio was passing fine at 48kHz, but not 96kHz.
The fix was simple: unplug the cables from the monitor outputs of the CS18AI and plug them into main outputs of the RM32AI. Problem solved.
Here’s hoping this prevents some hair-pulling frustration for you.
No Comments >
Here is how I fix this Pro Tools error.
Really? A typo in the error? Grrrrr…
Ever get this error? Canâ€™t open your session, right? Not only is it a major workflow stopper, but the double punctuation typo at the end is annoying as well.
Luckily, the solution is quite simple.
This is the quick fix that works for me and my particular setup of hardware/software. Your mileage may vary.
- Quit Pro Tools
- Restart Pro Tools
- Open the session that wouldnâ€™t open before
- Get back to work
The IT mantra â€œHave you tried turning if off and on again?â€ waves the problem away like a magic wand, but why is this problem happening in the first place?
The last time this error occurred for me, I noticed that it was after I had ejected my audio hard drive, removed my iLok, and left Pro Tools open, but put my machine to sleep before Pro Tools could issue the panic message: â€œHey! Whereâ€™s your iLok, buddy?! Thatâ€™s it! Weâ€™re shutting this whole thing down.â€ Then when I went to reopen the last session I was working on, boom, the error in question occured.
Iâ€™m guessing that between the time I ejected everything and the time I plugged it all back in and tried to fire it up again, Pro Tools had switched its default sample rate from whatever my Mbox 2 Pro says it was to whatever my MacBook Pro thinks it should be. Then when I try to open a session with a particular sample rate that doesnâ€™t jive with what the current rate is, Pro Tools freaks out because it thought it knew what was right, but doesnâ€™t even know anymore, man.
Disclaimer: I donâ€™t actually know how or why the error is occurring. These are just my slightly educated stabs in the dark. If you know anything more about this error, why it happens, and, most importantly, why thereâ€™s a typo in it, please leave your thoughts in the comments section below.
No Comments >