Aom 0.5.5 released

[PetriW]

Code: Select all

03-08-2005 version 0.5.5.240 ALPHA public release
- PetriW  - Quickfix for special episode numbers. They will be too high but at least the program won't blow up.

Code: Select all

03-08-2005 version 0.5.5.239 ALPHA public release
! PetriW  - Bitrate auto creq temporarily disabled, I have enough data to start looking into what files are creqed wrong and the mods have had enough for now. ;) 
! PetriW  - A minor sanity check has been made to length creq, it will now simply not creq length on very short files. This will probably change in 0.5.6.
+ PetriW  - If a change request is submitted for a file AoM will now wait at least 6 hours before trying again. The timer resets if you restart the client.

!IMPORTANT NOTICE!
This version of AoM will creq file length and bitrates of avi files.
This is not guaranteed to be correct (and what's correct in the world of bitrates anyway?), there are already a few files marked to be ignored by AoM.

If you notice a file being creqed incorrectly you can add the text "!AOMSKIP!" to it's description and AoM will ignore it. Once it's been marked you don't really need to notify me as I can find marked files with ease.
I'll use the files marked !AOMSKIP! to trace down what's wrong.
!IMPORTANT NOTICE!

Should fix a little:

Code: Select all

01-08-2005 version 0.5.5.238 ALPHA public release
+ PetriW  - AoM will now creq video bitrate for avi files if it's off by more than 10%.
+ PetriW  - AoM will now creq audio bitrate for avi files if it's off by more than 5%.
+ PetriW  - AoM will now creq length for avi files.
+ PetriW  - Cache now stores file length, this requires a fresh dump from AniDB.
- PetriW  - The AniDB API connection might no longer raise an exception when an anime is removed.
- PetriW  - The AniDB API line buffer is now larger.

It's available in #aom on chatsociety until I get ahold of exp.

[PetriW]

The new version of aom will probably give you this error:

Code: Select all

[2005-08-02 02:09:16] + Unknown status code 597, ignoring...

This was something I skipped to save time. What it means is simply that your client tried to file a change request based on an outdated copy of anidb.

The client will automatically correct itself within 2 hours and the error (for that particular change request) will go away. Restarting the client will also fix it but that's quite unnecessary.

[rowaasr13]

It could be good to make it not request length change if difference is only 1 second, as it may generate lots of changes that depend on people rounding length or just throwing miliseconds away in past. I've already got plenty of one second change notifications.

[egg]

Yay!!! Thank you. This was some of the stuff I wanted from 0.6 the other auto-creqs...

[PetriW]

It could be good to make it not request length change if difference is only 1 second, as it may generate lots of changes that depend on people rounding length or just throwing miliseconds away in past. I've already got plenty of one second change notifications.

I decided to let it change those since they're actually incorrectly rounded.
It'll fix itself pretty fast I think.

[PetriW]

Please notice there'll be a new version with better codec support asap. If lucky I'll include MKV support.
Thus please don't rush away an scan your DVD collection.

[e-Viper]

Thx alot PetriW

[Daemon]

Thank you very much Petriw.. keep up the good work!

[Skywalka]

I thought something was going on when I got 940 system messages this morning.

Damn you PetriW

This is what I've been waiting for for a long long time. Thx a ton!

[Rar]

Right, I'm currently automating creq handling based on the following parameters, please say if you want anything changed/added petri. Only checking length at the moment, but can add whatever as you see fit.

Code: Select all

if now < 15: # file duration less than 15 seconds, lock creq
	grant = False
elif was == 0: # current time is 0, grant
	pass
elif abs(now - was) == 1: # change of one second, grant
	pass
else: # time change greater than one second, send message to confim
	grant = False
	comment = 'Can you please check the file duration change'

Full wotsit available for masochists,

Rar

[Andemon]

Nifty; thanks. ^_^

(I do feel pretty stupid now for making similar creqs manually in the past, though...)

[PetriW]

Right, I'm currently automating creq handling based on the following parameters, please say if you want anything changed/added petri. Only checking length at the moment, but can add whatever as you see fit.

Code: Select all

if now < 15: # file duration less than 15 seconds, lock creq
	grant = False
elif was == 0: # current time is 0, grant
	pass
elif abs(now - was) == 1: # change of one second, grant
	pass
else: # time change greater than one second, send message to confim
	grant = False
	comment = 'Can you please check the file duration change'

Full wotsit available for masochists,

Rar

You also need to sanity check the bitrates. (size / length kinda)

[Rar]

I would have already, but unfortunately the encoders never do...

Sure, so do a overall bitrate vs filesize and length thing?

Rar

[PetriW]

I would have already, but unfortunately the encoders never do...

Sure, so do a overall bitrate vs filesize and length thing?

Rar

It should be detailed in a tracker item instead, thus we'll get autogranting.

[Skywalka]

So do the CREQs show up in myplace?

I currently can't judge whether I am generating CREQs from the AoM log and have already hashed 550 GB of files (450 pending).

I don't want to do that all over again...