Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[@l@n]

aTagger v1.0.10 is available for download at http://atagger.auldridge.biz (if you have v1.0.6 or later installed, press the [Check Now] button on the "Processing Options" tab to update automatically.  The ReadMe for the current version of aTagger is available at http://atagger.auldridge.biz/downloads/ReadMe.txt.

A summary of the fixes/updates include:
    - Don't reset the user's options to their default values when upgrading
      (unfortionately, upgrading to 1.0.10 will reset the user's options to the
      default values one last time)
    - Bug storing Year [imjustagamer, Doof, udeups & others]
    - Store Album Rating [imjustagamer & udeups]
    - Store Album Review [imjustagamer]
    - Allow all of the library field names to be set (including Artist, Album,
      and Genre) [udeups]
    - Add an option to specify the delimiter for Styles and Tones [clout & udeups]
    - Add option to disable "3 consectutive errors" prompt [Tweener] (Yes to All
      button added)

The items in my ToDo list that I'll start working on next are:
    - Any bugs reported
    - Option to add "The" and "A" prefix to lookup and try lookup again if the
      lookup failed [TimB]
    - Option to strip "The" and "A" prefix when storing
    - Use artist's Styles and Tones if the album doesn't list any [skeeterfood]
    - Option to only store the Album Review in track number 1

Enjoy...  @l@n

[pipsqueak]

alan

"Add option to disable "3 consectutive errors" prompt [Tweener] (Yes to All button added)"

THANKYOU - that was killing me...

will let you know if i find anything new. Now i jut need someone to write a visualisation that displays the reviews...does this exist already?

[skeeterfood]

Great work!

Another suggestion:  If a field currently contains data, but your search turns up nothing, please don't wipe the data currently in the field.

-John

[@l@n]

Another suggestion:  If a field currently contains data, but your search turns up nothing, please don't wipe the data currently in the field.

This is a bug that I'll fix ASAP.

Sorry...  @l@n

[skeeterfood]

This is a bug that I'll fix ASAP.

Sorry...  @l@n

Not a problem.  I'm still just running it on my Laptop's mini version of my real database, so no harm done

-John

[c1c9k72]

@l@n,

Thanks for the "3 consecutive" fix.  I was able to do my whole collection in a couple of hours, and as near as I can tell, it's done perfectly.  This is a great piece of software, and it's eliminated the need for quite a few cumbersome taggers I've had clogging up my hard drive.

If I wanted to be greedy, though, I'd ask if it's possible to get track numbers for a given artist/album/song ?  If it's not possible, that's fine.  It's just the last of the big four tags most people have.

Keep up the great work.

[@l@n]

Thanks for the "3 consecutive" fix.  I was able to do my whole collection in a couple of hours, and as near as I can tell, it's done perfectly.  This is a great piece of software, and it's eliminated the need for quite a few cumbersome taggers I've had clogging up my hard drive.

Youre welcome!  I'm glad you're finding aTagger useful.    

If I wanted to be greedy, though, I'd ask if it's possible to get track numbers for a given artist/album/song ?  If it's not possible, that's fine.  It's just the last of the big four tags most people have.

I plan on upgrading aTagger to validate the track numbers and song names but I have'nt figured out how I'm going to handle the track numbers for multi-disc albums.  I re-number every disc starting at one but the data that I have available numbers continiously across discs.

If you find any problems or think of any other features please let me know.

[pipsqueak]

alan

im still getting error messages when i click on atagger, they generally go away after a few tries and then the thing works fine:

most recent error messages nclude:

 "object reference not set to an instance of an object"

"external object has thrown an exception"

"the process cannot access the file ........\atagger_rpt.txt because it is being used by another process"

[@l@n]

im still getting error messages when i click on atagger, they generally go away after a few tries and then the thing works fine:

most recent error messages nclude:

"object reference not set to an instance of an object"

"external object has thrown an exception"

"the process cannot access the file ........\atagger_rpt.txt because it is being used by another process"

Is anyone else having simular problems?  

Until version 1.0.3 there was a timing bug that caused "object reference not set to an instance of an object" messages to occur the first execution after a new install.  I've not had any problems since that version.  

re: the locked atagger_rpt.txt.  This leads me to beleive that a 2nd copy of MC/aTagger was running and that the second copy had the report file locked.  This could have happened if MC was closing down due to a plug-in error but had not completely closed down before a 2nd copy of MC/aTagger was started.

Please let me know if you continue to have simular problems.  BTW, what OS are you using?

[DJ_Hazelwood]

Hi Alan!

I've tried the new version (1.0.10) and it works fine for me.
Just one question: What is the sort-order in the playlist-combobox ?  ?

[@l@n]

I've tried the new version (1.0.10) and it works fine for me.

Great!  

What is the sort-order in the playlist-combobox ?

Currently it is unsorted.  I display them in the order that I receive them from the MC API.  I've added a ToDo item to sort them in ascending order to make them more useable.

If you find anything else, please let me know.

Thanks again for your testing effort!

[DJ_Hazelwood]

Currently it is unsorted.  I display them in the order that I receive them from the MC API.  I've added a ToDo item to sort them in ascending order to make them more useable.

Thanks !

If you find anything else, please let me know.

I've planned to (a)Tag my whole library tomorrow. I will let you know the results  

Thanks again for your testing effort!

Was a pleasure  

[TimB]

The items in my ToDo list that I'll start working on next are:
    - Any bugs reported
    - Option to add "The" and "A" prefix to lookup and try lookup again if the
      lookup failed [TimB]
    - Option to strip "The" and "A" prefix when storing
    - Use artist's Styles and Tones if the album doesn't list any [skeeterfood]
    - Option to only store the Album Review in track number 1

Enjoy...  @l@n

That'll teach me to not read, I missed the "ToDo" part and started running aTagger against my "Band" MP3s and was about to report a bug.

Thanks Alan, great program!

-=Tim=-

[c1c9k72]

alan

im still getting error messages when i click on atagger, they generally go away after a few tries and then the thing works fine:

most recent error messages nclude:

 "object reference not set to an instance of an object"

"external object has thrown an exception"

"the process cannot access the file ........\atagger_rpt.txt because it is being used by another process"

I got the "object reference" error once when I renamed the smartlist that aTagger was using to populate it's list.  But, when I restored the name, the error went away.

I also got the "process cannot access..." before, but that was after the plug-in was halted by an internal error and I tried to restart it without shutting off Media Center first.  But, neither error has resurfaced lately (the last three hours)

[LonWar]

I ran this against my Test library and all is amazing.... I had no errors and got exactly what I expected...

The only thing that I did have a problem with is already on your To DO list... The, and A at the end of the album or artist.


And now for more requests... (You can shoot me at any time...   )

Any way to get the Albums of a artist and the Credits of a album??  

Man o man is this ever gonna save me time....

Thanks for the time in creating/developing this!

[c1c9k72]

@l@n,

Another thing you may want to try, though it's not necessary by any means, is extracting the full release dates from whatever data sources you're using.  Not only the years, but some album's have their exact release dates online.  But even if it was left just as it is, this software is probably my most indispensible tagger now.

[pipsqueak]

XP pro SP1

will let you know if i get it again

[@l@n]

aTagger v1.0.11 is available for download at http://atagger.auldridge.biz (if you have v1.0.6 or later installed, press the [Check Now] button on the "Processing Options" tab to update automatically.  The ReadMe for the current version of aTagger is available at http://atagger.auldridge.biz/downloads/ReadMe.txt.

A summary of the fixes/updates include:
    - (Default) If a field currently contains data, and the search returns
      nothing, don't overwrite the existing data [skeeterfood]
    - Add option to force overwrite of existing data (will be useful if the
      program ever puts bad data in fields)
    - Sort the list in the Playlist ComboBox
    - Add Save button on the Options pages

I started but did not finish working on (the options are disabled) the following:
    - Option to add "The" and "A" prefix to lookup and try lookup again if the
      lookup failed [TimB]
    - Option to strip "The" and "A" prefix when storing
    - Use Artist's Styles and Tones if the album doesn't list any [skeeterfood]
    - Add online help -- possibly a Users Guide too

As always, please let me know if you have any problems or you think of any cool features.  

Enjoy...  @l@n

[@l@n]

BTW, is anyone willing and able to help me create some HTML help files?  I would really appreciate some assistance with this.  

PlEaSe, PLEASE, P-L-E-A-S-E!!!

Thanks...  @l@n

[Jonas]

I just downloaded aTagger to try it out for the first time.

I opened aTagger, realized I had too many files in Playing Now, went back to Playing Now to remove most of them, added some new files to Playing Now, went back to aTagger (which still displayed the full list of about 1200 files), clicked one of the files (which had been removed from Playing Now), and got this:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at aTagger.ctlATagger.ProcessSong(Boolean parmUpdate)
   at aTagger.ctlATagger.lbSongs_SelectedIndexChanged(Object sender, EventArgs e)
   at System.Windows.Forms.ListBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.ListBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.ListBox.WndProc(Message& m)
   at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/winnt/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
aTagger
    Assembly Version: 1.0.11.0
    Win32 Version: 1.0.11.0
    CodeBase: file:///C:/Program%20Files/aTagger/aTagger.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/winnt/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
Interop.MediaJukebox
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/aTagger/Interop.MediaJukebox.DLL
----------------------------------------
System.Drawing
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/winnt/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
AMS.Profile
    Assembly Version: 1.1.1553.1401
    Win32 Version: 1.1.1553.1401
    CodeBase: file:///C:/Program%20Files/aTagger/AMS.Profile.DLL
----------------------------------------
Accessibility
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/winnt/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------
System.Xml
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/winnt/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.

[@l@n]

I opened aTagger, realized I had too many files in Playing Now, went back to Playing Now to remove most of them, added some new files to Playing Now, went back to aTagger (which still displayed the full list of about 1200 files), clicked one of the files (which had been removed from Playing Now), and got this:

Thanks for the bug report.  It looks like I need to double check that the playlist has not been renamed (mentioned previously by Tweener) or that it's contents have not been changed.   These conditions won't happen often but I'll fix this in the next build.

Thanks again...  @l@n

[pipsqueak]

im trying to work out a way to store things album reviews and then see them in dreamstate - my prefered display. i mapped the reviews to notes, which dreamstate displays under tab 3, but it doesnt use character returns so its just one line of text.

any way to fix this or does anyone have better ideas?

[Quisp]

BTW, is anyone willing and able to help me create some HTML help files?  I would really appreciate some assistance with this.  

PlEaSe, PLEASE, P-L-E-A-S-E!!!

Thanks...  @l@n

Hi Alan,

If you give me the content, I can take care of the rest, let me know...

[Jonas]

Apart from that first bug I encountered, the tagger seems to work great!  I do have quite a lot of albums it can't find but that's only to be expected I guess.

Anyway, a couple of suggestions for minor improvements:

1) Right now you have a case-sensitive comparison when you check whether this artist/album is the same as the previous artist/album.  There are a few albums where for some reason I have differences in case and then I get asked whether to update information every time there is a case change.  Maybe you could use a case-insensitive comparison there instead?

2) There are a few items with false matches.  There's probably no point in trying to get rid of those matches because it would be difficult to do without being so strict that you miss a lot of potential matches, but how about adding the possibility of automatically setting a "don't process with aTagger" field (or adding to a "don't process with aTagger" playlist) for files where you say "no" to the interactive "update tags?" dialog?  That way I can then automatically filter out those files if I want to run aTagger again (to see whether new albums have been added into the database, or to re-run the tagger if you add more new fields to be filled automatically, or whatever).

I'm sure many of the existing improvements on the list are more important, though.

[@l@n]

a couple of suggestions for minor improvements:

1) Right now you have a case-sensitive comparison when you check whether this artist/album is the same as the previous artist/album.  There are a few albums where for some reason I have differences in case and then I get asked whether to update information every time there is a case change.  Maybe you could use a case-insensitive comparison there instead?

2) There are a few items with false matches.  There's probably no point in trying to get rid of those matches because it would be difficult to do without being so strict that you miss a lot of potential matches, but how about adding the possibility of automatically setting a "don't process with aTagger" field (or adding to a "don't process with aTagger" playlist) for files where you say "no" to the interactive "update tags?" dialog?  That way I can then automatically filter out those files if I want to run aTagger again (to see whether new albums have been added into the database, or to re-run the tagger if you add more new fields to be filled automatically, or whatever).

Jonas, those are both great ideas.  I'll add them to my ToDo list.

[Jonas]

Still tagging my songs...  :-)

In the "update tags?" dialog, would it be possible to show which tags would be changed (as opposed to just being set)?  For example, if I already have a year set and aTagger finds a different year, it would be nice if the old year could be color-coded red or if the "year:" label could be prefixed by "***" or something, to make it easier to see that this old information will be changed.  This would make me more confident that I'm not overwriting any information that I would like to keep.

[Bartabedian]

very cool plug dude,

If this has been mentioned b4  , if not:

it would be great if I could select which data I want it to update and which I don't. I use my genre field in a very basic way for my own hair-brained cataloging, so I don't want that messed with,, but I love getting the styles and tones info...

thanks,

B

[@l@n]

In the "update tags?" dialog, would it be possible to show which tags would be changed (as opposed to just being set)?  For example, if I already have a year set and aTagger finds a different year, it would be nice if the old year could be color-coded red or if the "year:" label could be prefixed by "***" or something, to make it easier to see that this old information will be changed.  This would make me more confident that I'm not overwriting any information that I would like to keep.

Jonas, let me make sure I understand...

On the "Interactive Processing dialog (which lists "Current Album Info:" and "Proposed Album Info:") you would like the current fields that will be updated to be identified (with color, asterisk, etc.)?

[@l@n]

very cool plug dude

Thanks!!!

it would be great if I could select which data I want it to update and which I don't. I use my genre field in a very basic way for my own hair-brained cataloging, so I don't want that messed with,, but I love getting the styles and tones info...

Bartabedian, I think what you're asking for already exists...

From the Tagging Options tab, you can specify which tags are updated.  If you don't want your custom Genres to be updated, remove the check that is in fromt of the Genre.

Please let me know if i've misunderstood your question/request, or if this fixes you up.

[@l@n]

Tweener & Jonas, in previous posts you reported errors...

I got the "object reference" error once when I renamed the smartlist that aTagger was using to populate it's list.  But, when I restored the name, the error went away. <Tweener>

I opened aTagger, realized I had too many files in Playing Now, went back to Playing Now to remove most of them, added some new files to Playing Now, went back to aTagger (which still displayed the full list of about 1200 files), clicked one of the files (which had been removed from Playing Now) <Jonas>

I'm unable to reproduce this serious bug.  If I start aTagger, then leave, then return, the list of songs to process is automatically reloaded (and is current with Media Center).  How are you able to return to aTagger without reselecting aTagger from under the plug-ins section of the tree view?

I really need your help on this one!

Thanks...  @l@n

[c1c9k72]

@l@n,

I have a new smartlist called "Empty STYLES" which I used to populate the list.  I selected it in the plug-in, then left to the Playlist section of the tree and renamed that smartlist to "Empty STYLES2."  Before, this is what would have caused the error, however this time, it simply defaulted back to "Playing NOW," avoiding the error altogether.  The playlist listing is also updated so it reflects the changed name of the smartlist.

So, I would guess that something you did (possibly in the sorting of the playlist listings) has eliminated that particular error.

I hope this helps.

[@l@n]

So, I would guess that something you did (possibly in the sorting of the playlist listings) has eliminated that particular error.

Thanks for the update Tweener.  I was hoping that you would'nt be able to reproduce the problem.

Thanks again...  @l@n

[Jonas]

On the "Interactive Processing dialog (which lists "Current Album Info:" and "Proposed Album Info:") you would like the current fields that will be updated to be identified (with color, asterisk, etc.)?

Yes, for those fields that already have some information which will be altered if I click "yes".  For example, if I already have a year filled in and aTagger wants to change this year to another year, I'd like this fact to be highlighted, but if the year wasn't filled in and aTagger finds a year, then I don't want a highlight because there is no risk of overwriting good information with bad information.

[@l@n]

On the "Interactive Processing dialog (which lists "Current Album Info:" and "Proposed Album Info:") you would like the current fields that will be updated to be identified (with color, asterisk, etc.)?

Yes, for those fields that already have some information which will be altered if I click "yes".  For example, if I already have a year filled in and aTagger wants to change this year to another year, I'd like this fact to be highlighted, but if the year wasn't filled in and aTagger finds a year, then I don't want a highlight because there is no risk of overwriting good information with bad information.

Thanks for the clarification.  I'll make that update in an upcoming version.

Thanks again...  @l@n