Problems after bouncing to disk

[jjwonk]

Recently upgraded to DP 10.11, new MOTU 828 ES interface, on a new 27” IMac
Was working on preserving some old cassette tapes (in real time) of my former band digitally.
Stereo L & R out of cassette deck into 828 mic/line 1&2. Simple enough. After recording and editing 5 or 6 tunes, I bounced as mp3’s to a desktop folder, songs bounced fine and played back well. Once bounced, I deleted the soundbites in the project, to start over with the rest of songs that were on the tape, (instead of opening a new template.) I noticed when I re-started the cassette deck to record the remaining songs, I no longer had any playback sound coming through my monitor speakers. I had input levels on the 828, but no sound. ? I do realize I jumped to quite a learning curve with my recent upgrade, but I never experienced this kind of behavior after a simple bounce, all the way back to DP3. I worked around this by quitting and restarting DP, but that shouldn’t be a necessity now should it ? Could this be a bug in DP 10, an interface setting, or am I missing some kind bounce setting that would cause this behavior ? Any help is appreciated, I do quite a bit of this kind of editing and saving old stereo files from different sources digitally, hopefully it’s a user error I’m missing and not aware of. Thanks !

[mikehalloran]

First: reboot and see if you still have a problem. There’s an old app I run now and then—if left on too long, I have no audio out. Everything looks good but only a reboot restores the audio — weird, I know.

I have accidentally engaged the Solo button and have gone nuts trying to solve the problem — even to the point of reading the manual to find all the many ways it interacts with other settings.

If that doesn’t do it...

No idea what you did but, if you have Time Machine turned on and no other Mac OS installed (partition etc.), you can turn back the clock to a point within the last 24 hours — takes a few minutes.

viewtopic.php?f=4&t=64689

If this happened over 24 hours ago then you may have to restore from backup or retrace all your steps to diagnose the real problem.

[jjwonk]

Thanks Mike
A total reboot helps the issue as well. I did that first. Simply quitting DP and reopening does the trick too. First time I ever experienced that type of issue, It's weird. Should get time machine up and running as well.
I have a feeling I have some kind of solo/ monitoring, or other button that is engaged or not engaged somewhere. Still getting used to things with the recent upgrades.