Hello all!

I haven't expected Encspot 2 to come that soon (could be that someone posted it a while ago but I wasnt here lately very often) So I was surprised when looking at Guerillasoft that it had already been released. I downloaded the new version to test it out and compare it to the previous one.

What made me wonder is that Encspot 2 makes different guesses compared to version 1. Especially there are a lot of "Gogo" guesses. Has this something to do with the new algorithm? But then this raises the question which version made the better guesses?!

And I found a bug. Lets say Encspot 1 detected a file to be Blade. Encspot 2 shows in the details of the same file also Blade but in the directory view it displays another encoer. Strange. I thought about reporting it to John but I mailed him once and since I never received an answer I don't think this would be worth it.


greets
foo

When I launch Encspot2 during encoding (--APS or APE with LAME 3.92), files who aren't finished are labelled as « gogo 3 ». Even when more than 15000 frames were scanned ! When the encoding is done, Encspot give the correct result.

Encspot 1 did the same, but guess correctly after scanning a few frames.

But this ocurrs to me with many entire files!! For example some Blade become Gogo, all Lame old files are now Gogo, and even Lame Ksi files are now displayed as Gogo files. I once read in a post that Ksi uses Lame and only changed the text string identifier. Could someone clearify this confusing puzzle?

Yeah, I am getting lots of gogo guesses as well. For me the biggest bug in version 2 is that when I drag and drop a single file to be analysed, the entire directory is then scanned.

This never used to be the case.

Price is right though:)

Yea, my Blade files have turned into Gogo's too. Problem is that I don't know if they actually are Gogo files or that EncSpotv2 is guessing wrongly. Wonder if we should go back to v1...

hi...



hehe it's not a bug. Someone complained that when you drag a file to EncSpot it is a pain to find (within EncSpot) the directory containing it. So I made it so that the directory is automatically opened. But I agree that it doesnt work very well for the reason you mention. Here's what Ive done in version 2.1:

there is now a 'Pause' button, which you can toggle. This pauses the scan of the current directory. When you double-click an mp3 in EncSpot (to get the Details Dialog) the Pause button is automatically pressed (but you can 'Unpress' it if you want). Once the Details dialog has finished its own scan then the Pause button automatically releases, and the current directory scan resumes. This has the added benefit that the details dialog scans faster (cos the HDD has to do less work).

The Pause button also goes down when you drag-and-drop to EncSpot.

I'll look into these blade/gogo issues. EncSpot guesses Gogo if it cannot find a 'Lame' string in the file. For CBR files Lame puts this string at the end, so maybe the file is truncated. The is certainly what is happening with 'partially encoded' files like guruboolez talks about above.

EncSpot can't be expected to correctly identify _fragments_ of mp3s! But it will have a go anyway.....

Hmm... hope to get 2.1 out soon.....I'm afraid the block-switching problems will have to wait till 2.2 though:(

cheers,
-jon