3.70 beta 4

[MAzE5h1p69wB]

Sure.

What settings do you want me to use?

Given that we understand that trying to read or write from more than one file at a time is like trying to play two songs on a gramophone at the same time, meaning it has some overhead - which is undesirable to the point that it doesn’t need to be done.

EDIT: Well, I used a different set of files, but with the same settings as previously mentioned.

With these files, and the error “couldn’t connect to amplifind server”, I got a throughput of 1.1 seconds per file.
I got the impression that saving files, at the end, was faster and also less “stuttery”, if you follow. Previously this saving had created a queue of 5, now there wasn’t any queue.

EDIT2: Also it seems that the correcter is working much more “smoothly” now, there aren’t any long pauses in between each song, and there are no sudden, inexplicable stops in processing.
And for about the first time, I can use the harddisk that jaikoz is working with, to also do other things, such as watching a movie.

[paultaylor]

Okay, thanks a good result then.

[MAzE5h1p69wB]

Well it seems that the various instances of genpuid.exe can still build up a queue when reading files for the generation of accustic ids.

It seems to be down to a queue of 10, which is better than the disk-max of 50 before, but if these instances can’t talk to eachother but floods the disk, I’m just going to have to move music-files to a temporary harddisk that I don’ need to access, and let them fight it out between themselves.

EDIT: Also if you are running any other tasks that use the disk even minimally, whilst Jaikoz is whelming it with its queue-buildup, all of the generating accusticid ids FAILS because the queue becomes saturated and Jaikoz times out.

So could we at least have a PAUSE-button or something for Jaikoz?