I'm doing my first big sync (around 1Gb) on USB using 2.0b3. I'm doing it mainly as a test of 2.0b3 as I realised I hadn't tried any big syncs with it yet (and I usually had problems with big syncs on 1.x).

I'm now part of the way through (can't tell how far, as the overall progress bar doesn't work) and things aren't going too well.

It started out well, but after half an hour I started to see problems very similar to those I had on 1.x of emplode. What happens is emplode starts to pause part of the way through uploading a tune. When it does this the player is outputting the following on the serial port:

endpoint stall(clear stall on ep5)
endpoint stall(clear stall on ep4)
endpoint stall(clear stall on ep5)
endpoint stall(clear stall on ep4)

This carries on for 20 minutes or so before emplode gives up and outputs "blah could not be synchronised., Data error (cyclic redundancy check). (error 0x80070017)" in the warning list. Emplode 2.0b3 is better than 1.x in that it manages to carry on, in 1.x it would do this to a couple of tunes and then eventually stop dead.

This has happened on about eight tunes so far.

There was another problem, about an hour in I got a whole bunch of "connection timed out 0x8004003e" warning messages.

I've been getting the same: "connection timed out 0x8004003e"

Just did a search (actually the search is what lead me to this thread) and it seems like this is being addressed in 2.00 final....

Same results here: "Synchronise failed while writing player configuration. Connection timed out (error 0x8004003e)."

I'm doing a USB sync from a Windows 2000 machine to a Mark 2 running 2.00b3. Interestingly, it's failing after it transfers tunes and rebuilds the database, so I have a semblance of a working sync. However, it doesn't complete, and I have to cycle the machines to get them to agree on a new cookie. Attempting to re-sync after this failure is no good, because one end (I suspect the empeg) is expecting to finish the previous sync.

Same results here: "Synchronise failed while writing player configuration. Connection timed out (error 0x8004003e)."

This specific error message is a known bug that will be fixed in the next release.

It is a cosmetic bug only. When you get this message, the configuration was actually written correctly. If you exit emplode and re-start it, you will see your configuration changes are there.

Any idea when we will be seeing the final version ? or at least another beta ?

Maybe I'm dreaming, but I thought someone said "maybe" late this week. Though that could be one of the many other things I'm currently waiting for new versions of. :)

Bruno

I got the error using USB and I don't recall the wendy filter settings making their way over? I remember trying a couple of times, switched back to ethernet and had no problems writing. I assumed the configuration not being written was the wendy filters?

Calvin