I haven't tried to reinstall the driver yet. I'll try putting it to sleep and see if it remembers it.
I'll check on the driver version when I get home. I only recently downloaded it so I suspect I do have the latest version.
My normal procedure when using the hiFace is to first boot up the computer, then connect the hiFace, then open Foobar2000. When I'm done, I shut down Foobar2000, then remove the hiFace, then shut down the computer. Is there something different I should be doing?
I chose to us kernel streaming to minimize the load on my laptops resources. I might try WASAPI and see how well it works for me.
Thank you both for the feedback. I'll let you know how it goes.
I checked the driver, and yes, I'm using the most current version.
After a little experimenting, it seems the problem stems from my bootup sequence. Instead of the above bootup sequence, this time I plugged in the hiFace first, booted up the laptop, then started Foobar2000. Using this sequence Foobar had the correct output device set.
Out of curiousity, I tried WASAPI, but I can't say I heard any difference. I had read that WASAPI uses the cpu more than kernel streaming, but I found it seemed to depend on content. With some music files, WASAPI used less cpu resources and with others kernel streaming used less, so I just consider WASAPI vs kernal streaming a wash.
You guys are great. This forum was much more helpful than the Foobar forum. Thanks.
