|
Title: 09-z5 quirks Post by: CoenP on May 17, 2011, 11:04:08 am Hi,
I would like to report some quirks I found. - the xx stuck on taskbar issue is not completely solved. XX still sticks to the taskbar sometimes, but it is easier solved than with 09-z4. You only have to restart XX and kill the existing xx. - sometimes after playing music for a while I hear a loud 'PLOP' when a new track starts and the sound disappears (silence). When I stop the track there is a 'PLOP' again. The track plays fine on the second run. - The volume control does not allways work. When this happens XX won't stop and several error messages pop-up. I have to kill XX and engine3 to start playing again. - In unattended XX is very slow with reacting on hot-keys. For serveral other reasons (special mode very critical and strait C not liking to go to the next track) I predominantly use XX in attended mode. regards, Coen Title: Re: 09-z5 quirks Post by: PeterSt on May 18, 2011, 08:42:06 am Quote the xx stuck on taskbar issue is not completely solved. XX still sticks to the taskbar sometimes, but it is easier solved than with 09-z4. You only have to restart XX and kill the existing xx. Yea, you mean to auto-option to kill the running instance; I thought it would at least be more convenient this way (assuming it keeps on happening). Quote sometimes after playing music for a while I hear a loud 'PLOP' when a new track starts and the sound disappears (silence). When I stop the track there is a 'PLOP' again. The track plays fine on the second run. First off, you can only mean Attended (otherwise there's no logic in your literal expression :)); Then, to me this tells that it takes too much time to load the next track, that stopping XXEngine3, and that by itself stopping your DAC. Right after that all starts again, and the DAC makes this noise. ... But I merely think your description is not 100% correct, which makes my thinking on what happens invalid ... Quote The volume control does not allways work. When this happens XX won't stop and several error messages pop-up. I have to kill XX and engine3 to start playing again. Assuming Attended again, it must be me to blame somewhere. I mean, I know that for me too often that doesn't work. Must sort it out. But Coen, if this is all with UnAttended, something is wrong. So please let me know. Quote In unattended XX is very slow with reacting on hot-keys. For serveral other reasons (special mode very critical and strait C not liking to go to the next track) I predominantly use XX in attended mode. I'm afraid your Atom, well, slow. And you mean this all happens with an SFS of 12 ? hmm ... Chances are fair that you managed the SFS=12/SC in a forced fahsion (without you knowing). This looks similar to me being able to get 120 SC or something on Vista, which worked by itself but left me with a totally unresponsive PC. So ... What happens when you make MC of that ? Peter PS: Please keep in mind that with an abnormally slow PC you really have to pay attention to when commands have been processed, or otherwise things will get worse and worse. Also, the "error messages" you mention, may be normal messages telling you something normal. But not sure. So, with any messages which normally shouldn't be there, please let me know what they are, ok ? |