XXHighEnd

Hi Peter,


So its correct that using Engine#3 with external (SATA) harddisk via USB2 gives (at the first cd I am playing) no capless playback? Small hickups are still there!

Regards,

Johan

As long as a "hickup" is a small skip of the track, yes (but I must solve that). If it's a small piece of silence, no, I don't know about that.

Which of both do you mean ?

By the way, currently I give room for 5 seconds loading time for the track. This is too few for an USB disk and larger tracks. It is enough for SATAII and a full CD.
In a next version this will be approached more "intelligently", and for example anticipate on the tracklength (and a kind of self learning from the speed of the previously loaded track).

Hi Peter,


A break of 1 second.

Regards,

Johan (I'll don't reply for 14 day's. 8) :bye: :rules: :party: :sleeping: )

Hi Peter :smile:

I've have mixed results with 0.9g obtaining a faultless gapless playback and can be summarised as follows:

• Using Engine#3, and accessing local SATA harddrives only, I can progress seemlessly between tracks of about 5 to 5 1/2 minutes duration. Tracks in excess of that produce a perceptible break and become more noticeable as the track length increases, as you might expect. Under the same conditions, using Engine#1 has NO issues.
• Using Engine#3, and accessing drives on other PC's on my gigabit network, results in a noticeable pause for ANY track duration. Note: this may be an issue with my network configuration running under Vista. I've noticed while doing file copying between my networked PC's and my HTPC when running Vista, that transfer is considerably slower than doing the same transfer running under XP ( same hardware ). It's possibly the additional layers of "protection" that Vista is using that is slowing things down, and is something I need to investigate. Using Engine#1, I have NO problems in continuity when accessing those same networked drives.

I haven't noticed any change to the sound quality between this version and the previous few  :veryhappy:

BTW ... may I suggest a little ergonomic change to impliment if you haven't already thought of it? Being able to double click (left mouse button ) on a playlist entry to start a track would be so much easier than having to hunt for the play button each time.

Cheers for now  :bye:

Russ

Thank you Johan. And have a nice holiday !

I don't know what you guys are doing to have all so slow. It seems kind of impossible to me that you can't read a, say, 70MB track in 5 seconds. Even over 100Mb ethernet that would be almost possible, let alone an internal SATA drive ...
Anyway, obviously I can test myself over ethernet, just to experience what you do, and I will sort it out.


This is actually strange. I have a hunch that something else is going on.
When the track is loading over the ethernet, does your disk lamp lit from the Vista PC (the one where the track is uploaded to) ? It should not of course, but does it for the duration of the loading, or consistently longer after that (after = when the disk lamp of the source disk stops litting (hehe)) ?


You may. I don't see a problem why not implementing that.

Thanks Russ.
Peter

Actually I do ...   :(
When (double) click would be used in order to get a track played, it would undo a made selection in the Playlist Area (maybe you didn't know, but you can do that).

Ok ... nothing about "slow" ... just my bad ... :whistle:

I found that effectively you have 1.5 seconds to load the track. This really would be too few for a 100Mbit network connection.
In the next version this will be solved.

Congratulations, version 0.9h is now capless! Even with external (SATA) harddisk via USB2. Thats nice listening! :good:

Regards, Johan