0.16 - tiny update!
Thank you for sharing your experience.
Indeed the RenderDisconnectCallback message needs to be explaned a bit. It say the maiko
is aware of the selected device was hot-unplugged, that is the native feature of Vista. I could not reverse the unplugging process but in theory i can properly shut down the playback or redirect the playback to the next default device. That is just a theory, the winamp never meant to do such a thing. The playback is complex and asynchronous process whereas the device shutdown is always sudden and unavoidable. Оne day I will find some smart solution how to change the device instanly without stopping the device, so i hope. Thats is known long-standing problem.
is the true kernel driver. As you may notice the maiko
always keeps the device opened. By design. When winamp is stopped the device do anything and consume no resources but the windows kernel is aware that winamp is still there, lurking for hot kernel news. The plugin was designed for almost instant fire-up and seamless playback. It plays different sample rates, channels, bit rates - all of them without gaps like a whole.
catch device shutdown callback from kernel (aka ultimate kick off) and without any proper code to react, it crush
. Also worth to mention when maiko
is just lurking the device, the winamp can be booted off by exlusive mode application.
Sorry, you have to close the winamp before any exclusive mode activity. I'm aware of the problem and looking for inspiration to fix it.