Changing sample rates causing loss of inputs..?

[john1192]

ok .. to Jes, the OP .. what changed in your setup ?? did you upgrade to PT 12 or 12.4 recently ?? i mention this because you said this below ..

" I have never experienced it before using the Apollo as my interface"

something changed !!

have you installed anything lately that is messing with your Audio Midi Setup ??

a new driver ??

[DJ Hellfire]

It's pro tools 12 period. Happened to me in 12.3 as well.

[john1192]

damn, that sucks .. not a good Roll Out for everyone for PT12 ..

Originally Posted by DJ Hellfire

It's pro tools 12 period. Happened to me in 12.3 as well.

[JuanPC]

Originally Posted by DJ Hellfire

It's pro tools 12 period. Happened to me in 12.3 as well.

Works here, from 96KHz to 48KHz, & from 48KHz to 96KHz, No channel loss because Lynx AES16 is AES/EBU, I have the LS-ADAT card but ProTools does not see any channel loss, because ADAT channels mirror, go through AES/EBU channels in the soundcard DSP mixer.

Anyway...
Here I have:
HD12.3.1 Windows 7.
Problem is OSX,
Make a video...

Is a bit tricky... To make it work....
Because I have an external MasterClock.
If I'm at 96KHz,
I Change the SampleRate of the Ext.Clock, to 48KHz.

Start ProTools,
Create a New Session at 48KHz, "same as ext.clock"
Save the empty session... "Will not play or record."
Exit ProTools.

Wait a second.
Restart ProTools, & load the recent session...

Works again at the New SampleRate...

ProTools does not change SampleRate on the Fly...
Like a Switch... If I'm in external clock, or any other different than internal clock.

If I
Exit ProTools.
Start PT
And open a session at 96KHz, but soundcard is set to internal clock & No RateLock, works again at 96KHz.
No problem.

I must select internal clock to change ProTools SampleRate, then switch to external with same SampleRate.

Bouncing at 96KHz is 7.7x, and at 48KHz is 13.something x
Same template, same plugins, same settings.

If I Exit PT,
Start again PT,
Open a session at 48KHz or 96KHz, works again, flawless if soundcard is set to Internal Clock.

I must Remeber to Change Bounce Sample Rate, ProTools template remembers the last setting...
If was 96KHz, but new session was created at 48Khz with a template created at 96KHz.


If I close a session without exiting ProTools, and open another session at another sample rate, works flawless, if soundcard is set to internal clock.

Simply: It Works.

48KHz sounds brighter because harmonics bounce back at nyquist frequency.
Making a kind of built-in aural exciter that 96KHz does not have, because harmonics do not bounce at 24KHz when working at 96KHz.

[YYR123]

Those kind of things used to happen all the time....b/c of the 3rd party interface ...issues IMHO.

I have an Avid interface and it's so nice....to not have to deal with that....

At least they got that stuff right......(Knock on wood)

[jes]

->So perhaps this is a 3rd party interface issue?

Wasn't the entire point of dongling to an Ilok instead of Digidesign hardware to be able to use 3rd party interfaces?

And come on, this is UA we're talking about.

[jes]

Originally Posted by JFreak

So perhaps this is a 3rd party interface issue?

That would explain it IF Pro Tools actually did what it said it would do in the dialog box, if there weren't also the issue of Pro Tools then taking hours to close the session track by track over minutes each, and if it actually ever finished doing that and opened the session again. It doesn't. I've let it sit closing the session for an hour, even if it does, it goes into permanent death spiral at that point.

So I doubt it's just the hardware.

[JuanPC]

Buy another SSD...
http://ssd.userbenchmark.com

256GB recommended, but 128GB works if not partitioned.
turn-off.
install SSD,

install Bootcamp
install Windows 7 64-bit Pro or Ultimate with Service Pack 1
install soundcard/interface drivers
install ProTools 12.3.1 for Windows, set scroll to page.
install same plugins for Windows.
open same session .ptx
create a new session, do the same

if has the same problem is a Hardware Problem.
if does not, is OSX problem.

before this, test memory...
for PC´s there is a MemTest+,
better than Windows Memory Diagnostic.
http://www.memtest.org

don´t know how good or bad is this for OSX:
http://www.memtestosx.org

[jes]

no thanks, not interested in using Windows.

I have memtested memory, it's all fine. All 32GB of it.