Avoiding manually rebuilding the database?

After about 8 months I'm now catching up on uploading music to my empeg and I have something in the region of 50 albums still to upload, mostly due to buying remastered copies or simply re-ripping and compressing with Lame's APX option.

I was already aware of the bug where emplode appears to crash and the player reports Sigkill through Hijack at the rebuilding database stage and leaving me to do a manual rebuild, but it's getting tedious now. I started with 12 albums and that caused a crash, then 8 albums and eventually 5. 5 albums appeared to work ok for a while but I've just had 2 crashes/rebuilds with that number.

Strictly speaking I know this can't be fixed but I'm interested in any workarounds that I've probably missed here. I tried skipping the manual rebuild but emplode then gets stuck in that Rebuilding Database procedure - I quitted out because it looked like I could rebuild manually quicker. I was hoping to skip the rebuilding database stage until I have my new music uploaded where I could start creating playlists etc.

Does anyone have any suggestions on how I could make this procedure a bit less interactive?

Should I just queue up the 50 odd albums in emplode safe in the knowledge that the database rebuild will fail? That just occurred to me and it seems too easy; I'm sure that I remember folks on here advising against hefty uploads?

Mk2 30+40GB, V3.0 A11, Hijack 438 and my preferred OS is WinXP.

Does anyone have any suggestions on how I could make this procedure a bit less interactive?

I may be way off base here... but I think that if you installed the v2.0 final software in place of the v3.0A11 shown in your sig, that your problems would go away.

I have synched over 60 GB at a time with 2.0 and had no problems...

tanstaafl.

Go for the hefty upload, and get things over with with less hassle.

You likely will also have better luck with v2.0 / v2.01 software installed for the upload phase, but I don't have any direct evidence one way or the other.

Cheers

Note: If you still have this problem even under the 2.0/2.01 versions of the player software, there is another known problem with very large capacity players. If you see emplode crashing even with 2.0/2.01, apply Mark's maxfid FID patch. This fixed it for me...

Quote:
I started with 12 albums and that caused a crash,

You should be able to upload many more albums than that. It should be rock-stable. There's something wrong there.

Now, if you're running alpha software, then yeah, I understand why you're getting crashes. I got tons of upload crashes when I used the alpha software. In fact, I've had the alpha software completely corrupt my playlist tree during uploads. Just say no.

Definitely switch to 2.0 final (both emplode and the player firmware) as others have already suggested, do an FSCK and a manual database rebuild at the start of the process before you start uploading, and then after that you should have no problems.