Quote: Originally Posted by phat_bastard
Seriously, "Looks like the time has come to find another frontend" as a thread subject, and "Sorry ME, I'm going to find someone else." sounds more like a plea to be flamed to death than a plea for help. We maintain / publish M/E as a hobby, and couldn't give two sh_ts whether you or anyone else uses it or not. Get a new attitude or disappear. Nuff said...
I'll look through the recursion code first thing monday and make sure there are error handlers in there, but I'm 99.9% sure there are. That means if you're not seeing something in debug.log then this is going to be really tough to track down. Out of curiosity, how much memory do you have in this setup?
I thought I was going to find something else, but even after a year not much has developed by way of other front ends. I love the beta but since I ditched the 2 gig machine and gone to a Epia it's kicking my ***. I spend 2 hours on the road a day, of which I end up trying to recurse a directory (by not thinking) and having to try to kill ME and relaunch it on the freeway (with a stylus and the winamp tray icon). That's what is driving me nuts. Winamp is running but no window. Heres a break down of how i have it and had it
Old system: Iwill 845 p4 board with 2 gig Northwood, 256 megs of ddr, 80 gig Seagate 7200rpm 3.5 inch drive(running ata mode 5), using SB Live 24bit sound card, all running off a 400 watt inverter. Worked perfect. Skins everything. I fell in love with the new Beta abilities and the beta sealed the deal with me and ME. Xp Sp1, dx9c, Mp9, all music in 'Media folder' on d partition. The video was handled via 845g chipset onboard.
New system: (still ****ing me off) M1000, 60 gig 5400rpm WD 2.5 drive(2meg buffer, running ata mode 5), 512 megs Corsair DDr 266, 2.5 timing (6,3,3), Using SB Live 24bit sound card, DC powered via Itps and 200-v PS. XP SP1, DX9c, mp9, all music in 'Media' folder on d partition. All critial updates, drivers yada ya. What happens is ME will flash 'busy' for about 1/2 second then drop to the deaktop, music still playing, IR functions gone, can't launch a second instance. Now up until a few days ago when I stuck another 3 hours in the driveway into it I was able to double click the ME icon on the desktop and it would relaunch and recover. I made a change to it 'sorting directory based playlists by file name' and can no longer recover that way. m3u's were set to mp9 as the default player, I changed it to Winamp, should it be the ME exe?
Other system: (worked up until the M1000 blew up, different car)
M1000, Samsung 8 meg buffer(running mode 5), 40gig, 5400 rpm hd, same corsair memory from above, XPsp1 all updates, same drivers as above. recurses fine. I didn't try swaping hd's as the m10000 just 'died' the day before I had the chance to see. This machine was using onboard ac97 audio.
Winamp from within the ME dir launched externally will recurse. The ID3 or name tagging takes a while but it does work. It almost looks like there is a time out where ME attempts to display the recursed dir names before they are loaded. really quite odd. I've checked logs, event log, the winamp ini, settings ini and anything i can see that might effect it, no luck. The odd part is the display size will not stick unless I manually edit the settings.ini. Otherwise it resets to auto. I'm only running 800x600 so I'd figure no problem there, I was just trying to force it to 800. Looked to me like the settings.ini might have been read only but that wasn't the case. I did use the reset.exe to attempt to clear it and start fresh but even when I first installed the app it flopped to the desktop when recursing. It doesn't matter if it is a folder with 2 songs or 4000 songs the client acts the same. Color depth doesn't matter either.
I'm pulling my hair out as it's not power related because the same thing happens when running off a 350 watt PS in my computer room. It looks to me like it is specificlly Winamp but I can't pin why. Externally it works fine. I don't know if you caught the other issues I'm having with the skins, only the ones supplied with the ME beta work with it. I had other skins working previously on the other systems, just not this one. Now all I get is a skin error using default. so no skin works for me other than torque. I could have swore all the previous skins worked in 2.3
Yes I'm long winded and a QA engineer so I've done a bit more than just had it disappear once and freak out. Total I have about 9 hours into trying to figure out why this one won't work. If you need something specific I can grab it as I'm only 30 seconds from it now. I had given up hope as all I could find on ME in thie Message board was from over a year ago. My bad for not treating this like my own software and giving some background before throwing stones.