Beta Builds of Xion. These are builds that are not quite ready for Release, but need feedback and bug submissions in order to move it to Release Status
I just updated to the 122 beta and noticed that Xion is keeping handles to .wma files open even when not playing. Yes, I know, .wma is evil and should be purged -- some have snuck into my 120 gig collection ):
I noticed this when trying to eject the removable drive upon which is my music -- I couldn't. I used the Unlocker utility to find that Xion was holding open handles to many many .wma files -- even though I hadn't played them. I assume that the files were opened at the load of the playlist and just not properly closed.
This bug, apart from making it difficult to remove a removable drive Xion was playing from, is probably causing an unwanted use of memory.
There is no shame in not knowing. The shame lies in not finding out. (Russian proverb)
I just updated to the 122 beta and noticed that Xion is keeping handles to .wma files open even when not playing. Yes, I know, .wma is evil and should be purged -- some have snuck into my 120 gig collection ):
I noticed this when trying to eject the removable drive upon which is my music -- I couldn't. I used the Unlocker utility to find that Xion was holding open handles to many many .wma files -- even though I hadn't played them. I assume that the files were opened at the load of the playlist and just not properly closed.
This bug, apart from making it difficult to remove a removable drive Xion was playing from, is probably causing an unwanted use of memory.
Thanks for the report davydm, I'll have to see if I can reproduce this and get it fixed
Dont know if it is just me being dumb or something, but the crossfading on my player was active after I installed the build 122. I do not like crossfading so I went to the settings to turn it off, and noticed that crossfading was not activated in the settings menu, but was active on the player. So I tried to activate it in the settings menu and it was deactivated then. So Crossfading (as it is at my comp) is active at the player when its not in the settings menu
My VC++ Runtime error has returned. I'm going to need the crash log-enabled build from you, Cliff, since it seems i'm the only one who gets this, and i have no idea how to reproduce.
logokas Wrote:My VC++ Runtime error has returned. I'm going to need the crash log-enabled build from you, Cliff, since it seems i'm the only one who gets this, and i have no idea how to reproduce.
Same problem ! Revert to build 121.
Windows 7 version = "6.1.7600.16385"
I too will be moving to Win7 Pro very shortly, managed to evade Vista crap even though I had it since Oct 2006 (used it a few times in 3 years lol).
Win7 has to be the way forward, if they f**k it up this time then they are doomed.
Will still be keeping the XP hdd as standby tho lol
hmm logokas I know this doesn't help with your error but repeat that error in an Arnie voice And that's how I imagine it heheh 2 verbose or not 2 verbose
Check eventvwr, it might be able to shed a little more light on it
krt16 Wrote:Dont know if it is just me being dumb or something, but the crossfading on my player was active after I installed the build 122. I do not like crossfading so I went to the settings to turn it off, and noticed that crossfading was not activated in the settings menu, but was active on the player. So I tried to activate it in the settings menu and it was deactivated then. So Crossfading (as it is at my comp) is active at the player when its not in the settings menu
Nah, you're not going crazy; I have this problem too. A simple workaround until it's fixed: enable crossfading, but with time set to 0.