2018.7 So Far...

[climber]

Originally Posted by innesireinar

Just wondering why someone still working at 192 khz. There are many papers by Paul Frindle, Nika Aldrich and Dan Lavry that say that a optimum sr would be something around 60 Khz (that doesn't exist) and 96khz is the higher sr to go. Higher than this causes a loss of definition in the bass freq. due to the dac reconstruction

Not appropriate for this thread. It has been debated ad nauseum other places...

Focus

[TNM]

Originally Posted by Emi

512, but did run a while at 256 with no issues also.

at those sample rates you would have had the issues at 64 and 128 buffer.. so you are not experiencing anything out of the ordinary here.. 10.13.4 and up only broke ultra low latency performance with PT.

[Emi]

Originally Posted by TNM

at those sample rates you would have had the issues at 64 and 128 buffer.. so you are not experiencing anything out of the ordinary here.. 10.13.4 and up only broke ultra low latency performance with PT.

I repeat, @ 192 kHz sample rate. I could run at 128 (min. @ 192 kHz) but was unstable. 256 is stable @ 192 kHz, but for safety I left it at 512. Did I say @ 192 khz?!?

Divide to 4 the buffer size for 48khz behavior.

[xmission]

Some problems that I am having since upgrading to .7

1. Sometimes when I drag audio, it appears about 3 lanes below the track I am dragging it in.

2. I can't duplicate a track, it tells me I don't have enough memory. I have 32G and am running at about 9G when it happens.

3. I went to run an autotune capture of a small (about 6 second) clip of audio. As soon as I try to capture, Autotune complains that it has reached the extent of it's buffer, which is set at 240 seconds. Maybe this is related, and PT .7 isn't reporting or seeing memory correctly?

4. If PT is in the background, and I try to bring it to the foreground by clicking the icon on the bar at the bottom, it just dings at me. If I try to alt-tab, it pulls up on the screen while I am tabbing, but disappears when I let go. It's as if it thinks at has focus when it does not.

I'm on win7 Pro with a 6850 processor, and 32g of ram

[xmission]

Also, Setup/Preferences window either doesn't open, or is hidden somehow.

Setup i/o acts normal.

[B.J.]

Originally Posted by xmission

Some problems that I am having since upgrading to .7



1. Sometimes when I drag audio, it appears about 3 lanes below the track I am dragging it in.



2. I can't duplicate a track, it tells me I don't have enough memory. I have 32G and am running at about 9G when it happens.



3. I went to run an autotune capture of a small (about 6 second) clip of audio. As soon as I try to capture, Autotune complains that it has reached the extent of it's buffer, which is set at 240 seconds. Maybe this is related, and PT .7 isn't reporting or seeing memory correctly?



4. If PT is in the background, and I try to bring it to the foreground by clicking the icon on the bar at the bottom, it just dings at me. If I try to alt-tab, it pulls up on the screen while I am tabbing, but disappears when I let go. It's as if it thinks at has focus when it does not.



I'm on win7 Pro with a 6850 processor, and 32g of ram

Win7 is not supported at 2018.7

Regards
B.J.

[innesireinar]

Originally Posted by climber

Not appropriate for this thread. It has been debated ad nauseum other places...

Focus

Can't resist when seeing people working at these unuseful high SRs

[innesireinar]

Originally Posted by Emi

Because I, repeat, I hear differences between 96 and 192 for classical music recordings. More realistic space and depth.

For pop music I stay at 48

Sorry but can't believe it. Even on classical music.

[Emi]

Originally Posted by innesireinar

Sorry but can't believe it. Even on classical music.

And I’m not trying to convince anyone. All good.

[Philthy]

Originally Posted by B.J.

Win7 is not supported at 2018.7

Regards
B.J.

Well there's terrible news for a company shedding market share