Playback Engine Settings Do Not Persist

[kathleen.elizabeth.west]

Hello,

Everything was beautiful and working a few weeks ago when I was playing with my Pro Tools First software. I logged in today and the software must had updated something and I was hearing no audio. I saw that it is now recognizing my monitor as an audio output device and set to that. When I change it back to my speakers , it validates and allows me to press ok. But the audio output settings do not persist. I am not getting any errors. My next thought was to try this and run the software in administrator mode. But I observe the same results. I attempt to change the settings, click ok, and the settings do not persist to use my Speakers as the audio output device. The speakers are working with other applications. All other applications using the speakers are closed when Pro Tools runs, or so I am aware. Anyway to test if there are any hidden programs using the device?

I am not sure how to troubleshoot or fix this issues. Has anyone else experienced this problem or have advice?

Thanks,

-Kathleen

[Darryl Ramm]

Hard to follow what devices you are talking about, nobody here knows what "my monitor" or "my speakers" are etc.

Hold down the 'N' key while Pro Tools is starting and keep it held until the Playback Engine Dialog appears and then select the correct audio interface.

If other interfaces are showing up as playback engine options that you don't use, then delete them (or at least any ASIO driver) using the Windows Device Manager.

---

You should ideally have an interface to use by Pro Tools which has a native ASIO (i.e. not using ASIO4ALL) driver and dedicate that to Pro Tools. Windows sound, and other applications should not be set to use it at all.

[kathleen.elizabeth.west]

This is the setting that persists


This is the setting I want to use my speakers.

[Darryl Ramm]

Holding down N each time you start Pro Tools is a work around.

Again, you are much better off getting a dedicated audio interface for Pro Tools with a native ASIO driver.

[kathleen.elizabeth.west]

Hi There,

Sorry if I did not clarify but I followed the instructions that you recommended in your reply. The software still has a bug and the settings do not persist after setting them. At this point, I am only wanting to mix songs to output to my speakers and not purchase an audio interface. Maybe in the future, but I am not optimized for recording, only playing back.

I think this issue happened after a software update and it recognizes now 3, instead of two output devices. Have you tried this setting after with 3 or more selection options (output) with Pro Tools First ? I would like to know if this problem affects only me.

Thanks,

-Kathleen

[Darryl Ramm]

I was not claiming this would change the behavior, I was giving you a work around. *every* time you start Pro Tools First, hold down N and set what you need, thats often quicker that trying to use PT then finding the playback engine settings are wrong.

I (and most other users here) do not use First, and almost all of us use an ASIO compatible dedicated audio interface when running on Windows, it's totally unclear what actual interface you have. Pro Tools of all types losing it's mind about what the last interface used was is not uncommon.

[maalikanderson]

I have a mackie fx 22 mixer and protools 12 is not reading my mic input. I went to my i/o settings and did the delete and default process but still I get no input signal I have the correct interface option on and have it on stero mix and no read for mic input.
I connected my foursite interface and the input reads fine I use my mackie for logic so I know all my inputs work. I perfer to use my mackie mixer for protools instead of my foursite.
How do I fix this problem?

[Darryl Ramm]

Originally Posted by maalikanderson

I have a mackie fx 22 mixer and protools 12 is not reading my mic input. I went to my i/o settings and did the delete and default process but still I get no input signal I have the correct interface option on and have it on stero mix and no read for mic input.
I connected my foursite interface and the input reads fine I use my mackie for logic so I know all my inputs work. I perfer to use my mackie mixer for protools instead of my foursite.
How do I fix this problem?

What exact operating system? What exact driver do you have installed for the fx22? ... Start at “Help us Help You” up the top of every DUC web page and try to provide the type of information asked for there.

What “mic input” are you talking about. What channel is that on the Mackie? How exactly are you determining this is not working? Not seeing a waveform? Now hearing anything when monitoring though Pro Tools? Is anything recorded when you play back? Is Pro Tools working at all? Able to play back prerecorded content when connected to the fx22? If you are monitoring though Pro Tools is track input monitoring enabled? (If that makes no sense Google track input monitoring with Pro Tools).

It may be your question has nothing to do with this thread? Or is there a specific reason you think it does?

Are your trying to run PT 12 on macOS on Mojave?

Post screenshots of your IO input/output/bus pages and playback engine page.

[Darryl Ramm]

Doh, scratch that for now.

Your fx22 is only a 2 input, 2 output interface. There will be no individual mic channel available. You have to mix down that mic input on your fx22 to get it to the stereo USB output. The fx22 manual should describe how to do that. In routing that signal mix to the USB correctly is your likely problem. I can’t guess if you realize that already, but hope you do if it’s working with Logic (or maybe it was configured correctly by accident). If not start there with the fx22 manual. If you cannot get that to work then provide the info asked for before. if you have it working with Logic then without changing fx22 routing exit logic and run Pro Tools.... what happens?