Interface issue, PT10

[Jesse Peterson]

I'm using a Cheap Presonus Firewire 8x8 while I save for something else.

For the last few days, I'm getting this pop up periodically while stopped.

ASIO device properties have been changed by the device control panel. Pro Tools must be restarted for these changes to take effect. Please restart Pro Tools.

But I have not touched the control panel, nor have I changed any Playback engine settings.

There is a preference in the main windows sound control panel that says I can let apps take exclusive control over the presonus.. the error happens whether that is checked or not.

If anyone can suggest anything, it's driving me crazy.

thanks

j

[cananball]

hmm. I can't answer your question but I'm glad you brought it up. I've been thinking of moving my 003 to another system with PT8 and using a Presonus Firepod I have laying around for a new PT 10 system. Think i might reconsider that now.

[jonathanh]

Try using ASIO4ALL drivers instead maybe? I had to with my old Presonus Firebox for it to work at all with PT9/10.

[Jesse Peterson]

Originally Posted by jonathanh

Try using ASIO4ALL drivers instead maybe? I had to with my old Presonus Firebox for it to work at all with PT9/10.

Not the first time I've heard this. I think I'll look into it.

Thanks

[Jesse Peterson]

Originally Posted by cananball

hmm. I can't answer your question but I'm glad you brought it up. I've been thinking of moving my 003 to another system with PT8 and using a Presonus Firepod I have laying around for a new PT 10 system. Think i might reconsider that now.

Output 3&4 are dead, they broke when I insterted TRS plugs, I could hear pieces rattling arround.

Cheap is cheap, but I thought it would last longer lol

[BIGBANGBUZZ]

Personus are the new Berringer...
Build quality of a communist Russian era motor car or if you believe Jeremy Clarkson a current American built Motor Vehicle

[Brian B]

Originally Posted by BIGBANGBUZZ

Personus are the new Berringer...
Build quality of a communist Russian era motor car or if you believe Jeremy Clarkson a current American built Motor Vehicle

Oh Clarkson hates everything that isn't Astin or Jag.

On topic, I'd start with just reinstalling drivers. Do you have any other windows or apps running at the same time? It's possible that they're taking control of your driver and asking it to change sample rates, etc.

[Jesse Peterson]

Originally Posted by Brian B

Oh Clarkson hates everything that isn't Astin or Jag.

On topic, I'd start with just reinstalling drivers. Do you have any other windows or apps running at the same time? It's possible that they're taking control of your driver and asking it to change sample rates, etc.

Sometimes yes, sometimes no. But it happens either way. I tried to make it happen on command but deliberately running other audio stuff at the same time and everything went fine. Go figure.

Going to uninstall, re-install and see how it goes.

[Andrew Mottl]

Hey Jesse,

As you are on Win 7, have you disabled the Presonus as a playback (and maybe recording?) device in the Windows audio devices settings? Maybe the system is interfering with sample rates (though that wouldn't be via asio).

Hope you get it sorted!!

[huub]

It sounds like maybe the samplerate in the devices settings is different from the samplerate of your PT session?

[Jesse Peterson]

I had actually been using the presonus for system sounds and protools. It had been working great with no issues for a while. I suspected that to be the problem initially and switch over to another card for system stuff. Error still happens.

[Jesse Peterson]

Originally Posted by huub

It sounds like maybe the samplerate in the devices settings is different from the samplerate of your PT session?

This is what I'm thinking too. But what could be changing it in the background.

Big mystery

I'm about find the balls to shell out for an RME800.

[DigitalBrownNote]

Originally Posted by huub

It sounds like maybe the samplerate in the devices settings is different from the samplerate of your PT session?

hmm... This may not help, as of now i still run PT9 , but are you getting that particular error on the same session? do others cause the same problem? If not, try creating a new session (checking to make sure you stay within the sample bit/sample settings) and importing the one that is giving you trouble. I have had sessions corrupt before and your session file has the ability to change playback engine settings.

Also check the hardware engine settings, as well as your system setting for your sound driver.

Those would be the 1st 2 things i would check.

cheers

[Jesse Peterson]

Originally Posted by DigitalBrownNote

hmm... This may not help, as of now i still run PT9 , but are you getting that particular error on the same session? do others cause the same problem? If not, try creating a new session (checking to make sure you stay within the sample bit/sample settings) and importing the one that is giving you trouble. I have had sessions corrupt before and your session file has the ability to change playback engine settings.

Also check the hardware engine settings, as well as your system setting for your sound driver.

Those would be the 1st 2 things i would check.

cheers

I did not know that the session had that ability. Red Flag here..

This particular session is the only one that it's doing this on.. and.. this particular session has a few tracks imported from a PT8 session. I'm going to rebuild it all today.

thank you

[DigitalBrownNote]

well i dont see just importing the audio causing the problem. But, who knows, sometimes its just the ghost in the machine.

[Jesse Peterson]

Originally Posted by DigitalBrownNote

well i dont see just importing the audio causing the problem. But, who knows, sometimes its just the ghost in the machine.

Early on I got some very strange errors after importing v9 session data. PT10 seems to like it if you first save the older session as ptx.. then import it.

On a few occasions today.. changing the automation mode on a track will cause the error. this is the first time that I've noticed that it's happening during a specific action

RME400 on the way.. been meaning to pick this up anyway

[DigitalBrownNote]

Hmmm, that automation problem wouldn't be caused by your interface. It gives you the same error message as before with that change in automation?

I would assume the session is corrupt. If importing the session does not work. And you find out the the interface isn't somehow causing this error.... This may be one of those terrible moments when all you can do is import the audio, and start the mix over from scratch.

cheers

[Jesse Peterson]

RME fireface400 installed now. I may not have needed it however. (wanted it though)

problem looks like it was a combination of a bad driver and a bad firewire port. The port that the presonus used would not work with the RME. I suspect that the presonus was losing connectivity randomly and causing the pop up.

Outputs 3/4 on the presonus were broken and I always knew I'd have to replace it eventually. Lesson learned though.. I'll try a new port before spending $1300 bucks next time.


The one thing that I'm not getting with the RME that I hoped for was a longer hardware buffer. I used an EMU 1820m since 2003 which finally broke a couple months ago. It offered an asio hardware buffer of 100ms. I don't really record anything here so it was always maxed. On my largest jobs I never pushed the CPU past 60-70 percent. I new that the RME went up to 4096 but as it turns out, that is only if you're running at 192k. So, at 48k I'm stuck with 1024 max.


Anyone know of an interface with massive hardware buffer sizes?