Comments

mjn3 wrote on 4/27/2020, 11:43 AM

I've had this happen twice with ACID 7. It'll be working fine and one day then out of nowhere this happens. No hardware changes, no Windows updates installed, nothing different from one day to the next. It seems ACID gets confused working with the audio driver. Nothing but an uninstall/re-install fixes this for me. After the last time this happened I set ACID to run as administrator and to run in compatibility mode for Windows 7. Will see over time if it makes a difference.

Kelly-Springer wrote on 4/27/2020, 4:10 PM

Thanks for the insight. I uninstalled and reinstalled my software and it worked. Don’t plan to continue using if this is a regular fix.

mjn3 wrote on 4/28/2020, 10:59 AM

I think it's a Windows 10 thing. I used ACID 7 for many, many years under Windows 7 and never saw this behavior. What version of ACID this happening with for you?

Kelly-Springer wrote on 4/28/2020, 12:40 PM

I'm currently using ACID 9. I upgraded last fall.

mjn3 wrote on 4/29/2020, 10:51 AM

Well, so much for my idea that upgrading from ACID 7 will solve this :-)

sheppo wrote on 4/29/2020, 12:06 PM

It's not something crazy like... you have a cable resting on a key on the keyboard, or something like that is it?

mjn3 wrote on 4/29/2020, 3:50 PM

Thanks Sheppo, but what happens is that the blinking playback line, or cursor, does not track along with playback. I learned that switching my audio device from my hardware's ASIO driver to a generic choice on the list like Microsoft Sound Mapper (or maybe it' s WDM) will allow the cursor to function properly. Switching back to ASIO and it's broken again. Nothing fixes it except a reinstall. The kicker is nothing changes in my system to trigger this. Something is confusing ACID from working under the ASIO driver (that doesn't fix with a re-boot) but who knows what.

Like I said, I went many years running ACID under Windows 7 and ASIO without any issue. I thought the problem was the older ACID 7 running under Windows 10, but now I'm surprised to learn ACID 9 also exhibits this.

sheppo wrote on 4/30/2020, 4:26 AM

Interesting. Are you able to provide more detailed information about the build of Acid, audio device, driver version, and device-specific ASIO driver version? A video demonstrating the problem that would help, i can then reach out either via the beta forums or a message to hopefully get it logged as a bug.

In the meantime, is using ASIO4ALL an option for your hardware? I'm using ASIO4ALL 2.14 and can confirm it has worked with the last few major versions of Acid without issue.

mjn3 wrote on 4/30/2020, 10:29 AM

Thanks sheppo, maybe Kelly-Springer or someone using a current version of ACID can provide detailed information or a video. I doubt details from my old version 7 would be helpful. Note that it is an infrequent problem. It'll run fine for many months in-between instances.

I don't think I would try an optional ASIO driver. ACID is just a sketch pad for me. Music I sketch out there ultimately ends up in a modern full featured DAW which is working quite well for me.