Post deleted by rob

Can I vote for 'Clock has never kept proper time ... ever !' ?

Seriously it hasn't. I'll be honest i've only ever noticed 2 of that list of bugs, so it goes to prove what a great product the empeg is.

I think you should buy them ALL a beer instead, only the winner gets a Stella and a whisky chaser instead of just plain Fosters

Damn, I tried to edit my sig ... it's 50gb now folks ,,, ran out of space

How about emplode fails to synch 3/4 of the time?

Huh... I have to say I don't really care much about any of those and I didn't know most of them existed (shows you how good the product is when the biggest bugs don't affect most users). I would much rather have a "vote for your favorite new feature" poll where we could vote for new feature should be added (or backported) first in your "copious free time (tm)".

-Mike

Oops, I missed some stuff out. We'll start over in a new thread!

How about emplode fails to synch 3/4 of the time?

We don't have a reported bug of that nature, and if that was the case in general don't you think there would be an outcry on here?

Please report your specific issues in an appropriate thread. If you're running over USB with Windows XP don't bother reporting anything, that's #1 on the list of blatted bugs.

Rob

That seems shockingly like something my wife would have whined about if it happened, so I'll guess it's not very widespread. She never uses serial or USB, though, only ethernet. (All the empegs dhcp on a private internal network, and
I have a "docking area" for them now)

It would have been nice if we could have got into the spirit of the thread, which was intended to be fun. A bunch of developers have put in several hours of unpaid time to clear out some straggling bugs so we could release 2.0-rc1 - the competition for a bottle of wine is intended to be light hearted. So even if you don't care about the bugs, choose the one that looked like hard work!

Rob

I'm using ethernet on my computer. I've had two Empegs and tried it on 4 different computers, always with the same results. I have also tried it with USB, but it crashes there too. It can usually accomplish a small synch (just a few ID tags), but very rarely accomplishes anything large, such as moving a few hundred songs. For those large synchs, it typically requires 3 or 4 tries to get everything transfered.

This could be related to the crashes from having the clock enabled all the time. I guess I could try to disable the clock and try again.

-Biscuits

I appreciate the Empeg team. Y'all have always been good to the community. You have continued to release new software versions after the product has been discontinued. You have also helped people troubleshoot problems and listened to their suggestions.

I appreciate all you've done for the community and did not wish to appear ungrateful.

-Biscuits

"Can I vote for 'Clock has never kept proper time ... ever !' ?"

You probably have a bad battery (watch size, inside the empeg). At least that is what the problem generally is on electronic devices. It is highly doubtful that this is related to the software

-Biscuits

Are you running Beta13?

There's something very odd going on there. I don't remember the last time I had a failed sync - it must be well over a year ago.

Rob

Yep. I went back to beta11 a few months ago, but I had some other bug that I can't remember now, so I came back to beta13.

I'll try to test things out tomorrow and post more information then. I'm pretty sure this bug has been around for the entire time I've had an empeg (a little over a year now), but I really can't be certain.

-Biscuits

I synced about 20GB onto my player with Beta13 - took a while, but no errors. I alternate between USB and Ethernet on Windows 2000.

I don't believe there is a general 75% error rate with synchronisation, so we need to determine what the common factor is. If it's not interface or PC then perhaps you're using emplode in a different way to others, somehow.

Do you know if 1.03 works OK for you?

Rob

Yeah, "clock doesn't keep proper time" is not a software bug, it's a hardware bug, it's in the FAQ...

It would have been nice if we could have got into the spirit of the thread, which was intended to be fun. A bunch of developers have put in several hours of unpaid time to clear out some straggling bugs so we could release 2.0-rc1 - the competition for a bottle of wine is intended to be light hearted. So even if you don't care about the bugs, choose the one that looked like hard work!

You are completely right of course and I didn't mean to belittle any of the work that went into squashing those bugs. I'll go vote for that winXP USB bug because I certainly wouldn't want to have to use winXP long enough to troubleshoot and fix that one

..I certainly wouldn't want to have to use winXP long enough to troubleshoot and fix that one

LOL, now that's funny!

I'll do some testing tomorrow to give you more information. If you can solve this for me, do you know if there is any way to send the team money for a beer? Paypal or such?

Bribary is not necessary.

We'll talk kick backs after your problem is fixed

Rob

Hehe. I didn't mean that as a bribe, but no matter.

Yeah I also get problems in syncronization also. About the same problems that BiscuitsJam gets. Little one or 2 file syncs work fine, but I can never do a large amount without having errors. I thought this was normal and just learned to deal with it.

last night i uploaded over 6000 songs onto a freshly built player -- over 52GB. i've never had a failure during synchronization, ever, in the past year and a half. i'm running win2k over ethernet, for what it's worth.

--dan.

This could be related to the crashes from having the clock enabled all the time. I guess I could try to disable the clock and try again.

Yes, synchronising to beta 13 would fail almost every time if the clock was enabled. This was fixed ages ago -- too long to qualify for the winebottle thing!

Peter

I think in the year I've had my empeg it's only failed twice when using ethernet. Both times it worked perfectly once I tried again. The only other times it had failed was because of the issues with USB in XP.

- Trevor