AutoRateAccurate 2.4.3 (22/10/2009) - for MM3

[Big_Berny]

@nyn: 2.2 should be affected too from this problem as there's no change in this section. I'll try to solve it.

@MoDementia: Thanks a lot! I'll have a look! These SQL-problems since MM3 are really annoying and need a lot of time...

[nynaevelan]

Berny:

I think I figured out what the problem was. When I installed v2.3 it reverted back to the default formula, since that was not the formula I was using, alot of tracks were being re-rated so that was trying to run as I was trying to run a sync or two. But now that I changed the formula back to the one I was using, re-rated my tracks, now my syncs are running without any conflicts with ARA.

Nyn

[Big_Berny]

Yeah, this could be the reason why the error doesn't appear anymore. But the bugs is still there just the time-frame in which the error can appear is much shorter now.
The problem: When the script has to modify ratings it has to open a query. Now if you sync your mp3-player MM also opens a query so that error appears because it's not possible to open multiple querys at the same time. And if the script has to modify a lot of tracks the query is much longer opened and that's why the probability that the two queries get opened at the same time increases.

As I said I'll try to solve that problem. With MoDementia's help this shouldn't be to difficult.

Big_Berny

[nynaevelan]

Ok:

In the meantime I will try not to sync while ARA is rating, but as you stated this shouldn't be a problem for two reasons...1 - I usually don't sync until I am away from the 'puter and 2 - the ratings should be caught up now.

Nyn

[JuBe]

I'm getting the "COMMIT" error mentioned earlier.

[Big_Berny]

Hi,
just released version 2.3.1 which should (could) fix the mentioned problems.

Changes since 2.3
-Changed: SkipDetection and Incremental PlayCounter are more accurate now.
-Fixed: SQL-problems with locked database. (Thanks for reporting nynaevelan and JuBe, and a special big thanks to MoDementia for helping to fix that problem! )

Please tell me if the problem still occurs or new ones appear.

Have a nice weekend!
Big_Berny

[nynaevelan]

Berny:

Is it possible that when a user is installing an updated version and the user is not using the default formula, the installer could either leave the formula as it is or give the user a warning that the formula is being changed? The way it is now the installation is changing my formula and then a lot of tracks are being re-rated based on the default formula.

Nyn

[Big_Berny]

? This shouldn't happen and doesn't happen here. Only from 2.2 to 2.3.x the formula could be changed because the old one has been removed.

Which formula did you chose before the setup changed it back to default?

[nynaevelan]

I'm using Big_Berny's Formula v1.5 (PlayCounter instead PlayedTime) but each time I installed the 2.3 versions it reverted back to the default formula.

Nyn

[spacefish]

I haven't installed 2.3.1 yet, but I just noticed that my formula has also changed to PlayCounter instead of PlayTime. I was using BerniPi's formula. If I change it back BerniPi's formula it runs Autorate and then I get an access violation error and the formula reverts to the previous again.

I have stopped MM now and I'm going to install 2.3.1 so I will post back with news.

Nope. Installed 2.3.1, restarted MM and the formula was set to PlayCounter instead of PlayTime (left that way from previous installation). Set the formula to BerniPi's and autorate ran, no error but the formula didn't stick. Also after selecting BerniPi's formula and autorate, clicking Tools > Options took several seconds to pop-up the options window which was already pointed ARA > Advanced.

For now, the issue seems to be that I cannot select BerniPi's Formula.

[Big_Berny]

Thanks nynaevelan and spacefish for detailed report. The problem wasn't actually that updating removed the formula but that the formula wasn't saved correctly after closing the optionsheet.

It should be solved in 2.3.2.

Big_Berny

[nynaevelan]

I assume you are going to upload v2.3.2??

Nyn

[Big_Berny]

Sure, just forgot to modify the first post.
With MM's built-in updatechecker you'd have found the new version.

Anyway it's there now!

[nynaevelan]

With MM's built-in updatechecker you'd have found the new version.

Anyway it's there now!

Gonna take me a little while to get used to that feature, but will try it now. Besides this option does not allow the user to save a copy locally, and I am anal about having backups....

Nyn

[spacefish]

The last 2 versions have caused track change to be really slow or not happen altogether. The problem goes away with 2.3; unfortunately, 2.3 uses the wrong formula (I'll live). I am using MonkeyRok, Auto Album DJ and Auto Crossfade which only kicks in between albums. Right now I'm having to end process so I can reinstall 2.3. Changing tracks manually doesn't even work so I guess there's something locked up in there.