Tagalicious 1.1b13
8 views
Skip to first unread message
simX
Dec 20, 2010, 9:51:22 PM12/20/10
to Tagalicious Beta Users
So, I think I've fixed the constant crashing problem that some people
have been encountering. Please try 1.1b13, and see if things have
been fixed: http://files.thelittleappfactory.com/tagalicious/Tagalicious-1.1b13.zip
.
As always, please submit crash reports.
(FWIW, we want to release version 1.1 as soon as possible, barring
unacceptable problems like the constant crashers that have been
reported. There will be no more interface changes in the 1.1 betas,
just crasher fixing.)
-- Simone
have been encountering. Please try 1.1b13, and see if things have
been fixed: http://files.thelittleappfactory.com/tagalicious/Tagalicious-1.1b13.zip
.
As always, please submit crash reports.
(FWIW, we want to release version 1.1 as soon as possible, barring
unacceptable problems like the constant crashers that have been
reported. There will be no more interface changes in the 1.1 betas,
just crasher fixing.)
-- Simone
ahar...@gmail.com
Dec 20, 2010, 9:55:56 PM12/20/10
to tagalicious...@googlegroups.com
Simone,
The app seems to hang less, but still fails to tag any music for me just like b11.
The app seems to hang less, but still fails to tag any music for me just like b11.
Why don't you e-mail me directly and I can feed you any information you need to track down this issue?
Russ
Dec 22, 2010, 4:20:04 AM12/22/10
to Tagalicious Beta Users
Simone,
The app is *much* more stable now. I used it for about 30 minutes
straight with no crashing. Nice job, and thank you.
One more bug I noticed, as seen in the screenshot (http://
picasaweb.google.com/russ.goldin/Tagalicious#5553427376373451074), one
of my songs was tagged as having blank information. I have no way of
unselecting the blank information. Not sure if this is song related,
but it is the first time I've seen it. It would be good to be able to
reset/ignore all tags at the song level (or at least unselect blank
tags).
Here are some of my requests for future versions...
1. Limit CPU usage so this can be run in the BG and not bring the
computer to a halt
2. Rename "Tagged, Needs Updating" to "Tagged, Need to send to
iTunes" or something more accurate
3. Songs that have the red exclamation should not show up in
"Untagged, Missing Info" because they have been tagged. Maybe make a
new category like "Not recognized"
4. Songs that have no new tags should not be queued when hitting the
"Send all to iTunes" button since there are no changes.
5. "Send all to iTunes" button should be labelled more accurately,
because it may not actually send all songs to itunes. It only sends
selected songs.
6. Make an option to check tags when clicking on a new song. This
slows down the UI and is sometimes frustrating if you are just
navigating around using the keyboard.
7. Make option(s) to ignore trivial changes like a difference in caps
between the current tag and retrieved tag.
8. The workflow to review changes isn't easy. If I select 30 songs
and tag them, I then need to go back and manually click on each title,
look up the changes, click on the next title, etc, and then when I'm
done with that go back and select the 30 songs and click 'send all to
itunes'. I think there is some room for improvement on the review/
approve process.
9. An option to automatically look up all the tags in the background
(similar to #1), but I'm lazy. I just want all the tags to be
retrieved and then review them when it is at my leisure. I don't
really care if it takes 30 minutes or 30 days but it would be nice for
the software to do this and notify my (would it be asking too much for
growl integration?) and then review. Do most people buy the software
to look up 30-40 tracks, or will they want to review their entire
collection at some point. I would go so far as to say (along with #8)
the UI should even be designed for reviewing/approving changes to tags
instead of being based around selecting which songs to be tagged.
Does that make sense? The tag lookup process should happen in the
background for all my songs, automatically... then let me review/
change/approve in an easy to use app.
Thank you, and look forward to more releases...
Russ
The app is *much* more stable now. I used it for about 30 minutes
straight with no crashing. Nice job, and thank you.
One more bug I noticed, as seen in the screenshot (http://
picasaweb.google.com/russ.goldin/Tagalicious#5553427376373451074), one
of my songs was tagged as having blank information. I have no way of
unselecting the blank information. Not sure if this is song related,
but it is the first time I've seen it. It would be good to be able to
reset/ignore all tags at the song level (or at least unselect blank
tags).
Here are some of my requests for future versions...
1. Limit CPU usage so this can be run in the BG and not bring the
computer to a halt
2. Rename "Tagged, Needs Updating" to "Tagged, Need to send to
iTunes" or something more accurate
3. Songs that have the red exclamation should not show up in
"Untagged, Missing Info" because they have been tagged. Maybe make a
new category like "Not recognized"
4. Songs that have no new tags should not be queued when hitting the
"Send all to iTunes" button since there are no changes.
5. "Send all to iTunes" button should be labelled more accurately,
because it may not actually send all songs to itunes. It only sends
selected songs.
6. Make an option to check tags when clicking on a new song. This
slows down the UI and is sometimes frustrating if you are just
navigating around using the keyboard.
7. Make option(s) to ignore trivial changes like a difference in caps
between the current tag and retrieved tag.
8. The workflow to review changes isn't easy. If I select 30 songs
and tag them, I then need to go back and manually click on each title,
look up the changes, click on the next title, etc, and then when I'm
done with that go back and select the 30 songs and click 'send all to
itunes'. I think there is some room for improvement on the review/
approve process.
9. An option to automatically look up all the tags in the background
(similar to #1), but I'm lazy. I just want all the tags to be
retrieved and then review them when it is at my leisure. I don't
really care if it takes 30 minutes or 30 days but it would be nice for
the software to do this and notify my (would it be asking too much for
growl integration?) and then review. Do most people buy the software
to look up 30-40 tracks, or will they want to review their entire
collection at some point. I would go so far as to say (along with #8)
the UI should even be designed for reviewing/approving changes to tags
instead of being based around selecting which songs to be tagged.
Does that make sense? The tag lookup process should happen in the
background for all my songs, automatically... then let me review/
change/approve in an easy to use app.
Thank you, and look forward to more releases...
Russ
Russ
Dec 22, 2010, 4:26:23 AM12/22/10
to Tagalicious Beta Users
One more bug. In the view at (http://picasaweb.google.com/russ.goldin/
Tagalicious#5553434945862297922), the artist/album/genre/year are
missing on the right even though they are tagged on the song. Quiet a
few songs are missing the information in this view. Seems like it
only happens with songs that have already been sent to iTunes.
Tagalicious#5553434945862297922), the artist/album/genre/year are
missing on the right even though they are tagged on the song. Quiet a
few songs are missing the information in this view. Seems like it
only happens with songs that have already been sent to iTunes.
pdb
Dec 22, 2010, 2:01:20 PM12/22/10
to Tagalicious Beta Users
Trying out 1.1b13, seems it doesn't crash anymore, but what's really
missing is an "Activity" window that tells me that it's actually doing
things. I selected all my songs (around 18000), and apart from the
blue recycle logo (and a few red exclamation logos) in front of my
songs, I can't see any progress. Not sure if it's doing anything at
all. Something in the bottom that updates what's going on, or a
separate Activity window like in Aperture would really help.
Otherwise, at this point (after waiting 10 minutes without any kind of
update on the screen), I have to assume it's not working.
peter
missing is an "Activity" window that tells me that it's actually doing
things. I selected all my songs (around 18000), and apart from the
blue recycle logo (and a few red exclamation logos) in front of my
songs, I can't see any progress. Not sure if it's doing anything at
all. Something in the bottom that updates what's going on, or a
separate Activity window like in Aperture would really help.
Otherwise, at this point (after waiting 10 minutes without any kind of
update on the screen), I have to assume it's not working.
peter
Chase Rickman
Dec 22, 2010, 3:57:38 PM12/22/10
to Tagalicious Beta Users
im having the same problem it will show the red ! for like half of
them and then the rest is the blue spinning wich is not doing anything
at all.. would be nice to know whats going on but, because it's not
crashing i cant send it in..
them and then the rest is the blue spinning wich is not doing anything
at all.. would be nice to know whats going on but, because it's not
crashing i cant send it in..
simX
Dec 23, 2010, 1:27:22 AM12/23/10
to Tagalicious Beta Users
pdb, Chase: Did you delete your database.sql file? You'll need to do
that before running b13 in order for it to work correctly. It's
located at ~/Library/Application Support/Tagalicious/database.sql .
Please delete it, re-run b13, and let me know if things work
correctly.
-- Simone
that before running b13 in order for it to work correctly. It's
located at ~/Library/Application Support/Tagalicious/database.sql .
Please delete it, re-run b13, and let me know if things work
correctly.
-- Simone
Chase
Dec 23, 2010, 1:31:17 AM12/23/10
to tagalicious...@googlegroups.com
That's the problem I can't find it in the application support folder.. Not sure why
Sent from my iPhone
simX
Dec 23, 2010, 1:41:59 AM12/23/10
to Tagalicious Beta Users
Yay! Glad it's not crashing anymore. Regarding some of your
suggestions:
1. Tagalicious should automatically use less CPU usage in the
background when you're doing other things. The amount of CPU it uses
is automatically determined by the Cocoa frameworks. It does tend to
constantly read from the disk while it's working, so that may be the
cause of the slowdown with your other apps.
2. "Needs Updating" seems accurate to me. We named the button "Send
to iTunes" to make it clear that Tagalicious was going to change
something in your iTunes database, but it's not so critical for the
name of the smart group. What's your rationale here?
3. I don't think we want to create yet another smart group for this,
especially because it's an error doesn't necessarily mean that the
song can't be found in the database. It could be that the lookup
failed because of a slow internet connection, or the Tagalicious
database is down. If you don't want to try to retag those songs, you
can sort by status.
4. Hm, that's a good point.
5. We're already cramped for space, so titling the button "Send
selected to iTunes" is both longer and sounds more awkward. Also, I
think it's clear that songs that have not been tagged or have errors
won't change anything in iTunes.
6, 8, 9. You mention that the workflow to make changes isn't easy.
Automatically tagging songs when you select them was done with that in
mind -- since the workflow is always: 1. Tag a song, 2. Review
changes, 3. Send to iTunes; it seemed natural to just have step 1 be
automatically done for you. The only reason it isn't done for
multiple songs is because it starts taking up much more CPU/memory,
which may not be desirable.
I'm also interested in hearing how you would change the interface to
make it easier to review changes. How, exactly, would we make
reviewing changes more prominent? One improvement that I have planned
is that the details pane could reflect the details of all songs
selected, rather than the first song selected. While the songs would
likely have multiple values for each tag, it would at least allow you
to change the selected tags for a batch of songs all at once, and in
the case of albums, there would be a number of tags that *would* have
the same value across all the tracks.
We're considering adding an "album mode", where songs will be
automatically grouped into albums, but this wouldn't modify the
current three-paned interface too much. It would just automatically
group songs in the selection view, and then represent the details of
each album in the right hand pane rather than just the info for a
single song.
7. This is interesting, but we've also had complaints in the other
direction... some people were complaining about inconsistent
capitalization. Not sure if it's really worth making an option,
because if you don't care about capitalization, you can see that for
yourself in the details pane at a glance.
-- Simone
suggestions:
1. Tagalicious should automatically use less CPU usage in the
background when you're doing other things. The amount of CPU it uses
is automatically determined by the Cocoa frameworks. It does tend to
constantly read from the disk while it's working, so that may be the
cause of the slowdown with your other apps.
2. "Needs Updating" seems accurate to me. We named the button "Send
to iTunes" to make it clear that Tagalicious was going to change
something in your iTunes database, but it's not so critical for the
name of the smart group. What's your rationale here?
3. I don't think we want to create yet another smart group for this,
especially because it's an error doesn't necessarily mean that the
song can't be found in the database. It could be that the lookup
failed because of a slow internet connection, or the Tagalicious
database is down. If you don't want to try to retag those songs, you
can sort by status.
4. Hm, that's a good point.
5. We're already cramped for space, so titling the button "Send
selected to iTunes" is both longer and sounds more awkward. Also, I
think it's clear that songs that have not been tagged or have errors
won't change anything in iTunes.
6, 8, 9. You mention that the workflow to make changes isn't easy.
Automatically tagging songs when you select them was done with that in
mind -- since the workflow is always: 1. Tag a song, 2. Review
changes, 3. Send to iTunes; it seemed natural to just have step 1 be
automatically done for you. The only reason it isn't done for
multiple songs is because it starts taking up much more CPU/memory,
which may not be desirable.
I'm also interested in hearing how you would change the interface to
make it easier to review changes. How, exactly, would we make
reviewing changes more prominent? One improvement that I have planned
is that the details pane could reflect the details of all songs
selected, rather than the first song selected. While the songs would
likely have multiple values for each tag, it would at least allow you
to change the selected tags for a batch of songs all at once, and in
the case of albums, there would be a number of tags that *would* have
the same value across all the tracks.
We're considering adding an "album mode", where songs will be
automatically grouped into albums, but this wouldn't modify the
current three-paned interface too much. It would just automatically
group songs in the selection view, and then represent the details of
each album in the right hand pane rather than just the info for a
single song.
7. This is interesting, but we've also had complaints in the other
direction... some people were complaining about inconsistent
capitalization. Not sure if it's really worth making an option,
because if you don't care about capitalization, you can see that for
yourself in the details pane at a glance.
-- Simone
simX
Dec 23, 2010, 2:18:04 AM12/23/10
to Tagalicious Beta Users
Chase: Are you sure you're looking in the Library folder inside your
home folder, not the one that's on the root folder of your hard
drive? Make sure you go to your home folder first, then look in
Library/Application Support/Tagalicious/ and there should be a
"database.sql" file. This will always be created when you launch
Tagalicious, so if you can't find it, either something really weird is
going on or you're looking in the wrong place.
-- Simone
On Dec 22, 10:31 pm, Chase <oneamerican...@gmail.com> wrote:
> That's the problem I can't find it in the application support folder.. Not sure why
>
> Sent from my iPhone
>
home folder, not the one that's on the root folder of your hard
drive? Make sure you go to your home folder first, then look in
Library/Application Support/Tagalicious/ and there should be a
"database.sql" file. This will always be created when you launch
Tagalicious, so if you can't find it, either something really weird is
going on or you're looking in the wrong place.
-- Simone
On Dec 22, 10:31 pm, Chase <oneamerican...@gmail.com> wrote:
> That's the problem I can't find it in the application support folder.. Not sure why
>
> Sent from my iPhone
>
Chase Rickman
Dec 23, 2010, 5:19:14 AM12/23/10
to Tagalicious Beta Users
*facepalm* sigh... i was writing that on a few hours of sleep lol..
now that im a little more awake.. yes its working again and much
better so far, i've set it on the task of my library (22K songs) so
guess we'll see what happens! :)
now that im a little more awake.. yes its working again and much
better so far, i've set it on the task of my library (22K songs) so
guess we'll see what happens! :)
Chase Rickman
Dec 23, 2010, 5:32:13 AM12/23/10
to Tagalicious Beta Users
okay little update.. it crashed. about 20 minutes(ish) after starting
so it's improving but still there! :(
so it's improving but still there! :(
Chase
Dec 23, 2010, 6:15:01 AM12/23/10
to tagalicious...@googlegroups.com
Interesting after the crash I removed the database again and tried the same songs and it work tge whole way through. I'm now testing the D's wich is about the same amount as tge abc wish ne luck
Sent from my iPhone
simX
Dec 24, 2010, 6:17:22 AM12/24/10
to Tagalicious Beta Users
Russ: I've fixed this bug in beta 14. Please test and see if it fixes
it for you, too.
Chase: beta 14 has a fix that might solve the crashing issues that you
continue to have. Please test it out. Thanks!
-- Simone
it for you, too.
Chase: beta 14 has a fix that might solve the crashing issues that you
continue to have. Please test it out. Thanks!
-- Simone
Reply all
Reply to author
Forward
0 new messages