Too quiet around here...

0 views
Skip to first unread message

simX

unread,
Jan 31, 2011, 5:07:24 PM1/31/11
to Tagalicious Beta Users
Hey testers --

Anyone still checking out the messages in this Google group after the
1.1 release? Sent out a few betas for 1.1.1, but have only gotten one
response. Have more betas to follow, but need serious testing before
the next version can be released.

Please respond if you're still interested in testing betas of
Tagalicious. Thanks.

-- Simone

ahar...@gmail.com

unread,
Jan 31, 2011, 5:32:26 PM1/31/11
to tagalicious...@googlegroups.com
I'll test the 1.1.1 beta this evening when I'm at home.

ahar...@gmail.com

unread,
Feb 1, 2011, 3:59:47 PM2/1/11
to tagalicious...@googlegroups.com
I played with the latest beta last night, and it was working stably for me.

One annoying thing I'm finding when I tag music is the fact that I can only choose between the original tags and the proposed new tags. There are many situations in which I am reviewing songs, then I see a song where both the old and new tags are wrong, but I know the correct info. Being able to choose something different altogether would be a good feature to have. It would also be good to be able to choose no album art if neither the original art nor the proposed new art are correct.

The other thing I noticed is that the app is unresponsive when you're tagging a lot of music at once, which it to be expected, but I think that optimizing that performance is an area that should be focused on. The Finder doesn't hang when I select 300 files to copy to another volume, and it's not reasonable to expect users to put up with the app hanging just because they gave it a lot of data. It's okay for the app to take time to do things, but the UI should still always be responsive. Spawn off any nontrivial work into a secondary thread.


On Jan 31, 2011, at 2:07 PM, simX wrote:

simX

unread,
Feb 2, 2011, 2:51:15 PM2/2/11
to Tagalicious Beta Users
We didn't allow customization of the suggested tags because we wanted
to keep Tagalicious simple, at the cost of flexibility. That is one
of our biggest request from users, and we're considering adding it in
future versions, but not for 1.1.2 or 1.2. Maybe in 1.5. We also
didn't allow users to transfer blank tags to iTunes because of the
ease with which users could completely wipe out the tags in iTunes.
We may also reconsider that decision as well.

As for the hanging, Tagalicious *does* spin off as much as possible to
the secondary thread. When you say it "is unresponsive when you're
tagging a lot of music at once", do you mean when you first click
"Check All For Tags", or after it's marked all of the selected songs
as processing and it's going through the process of actually tagging
your tracks? When you encounter a hang like this, please open up the
Terminal application (located in /Applications/Utilities ), type in
"sample Tagalicious 15" (without the quotes), and then press return
*while Tagalicious is hanging*. Once it's done sampling, it will let
you know where it saved the file (usually to /tmp , you can use
Finder's [Go --> Go to Folder...] menu item to retrieve the file in /
tmp ). Send it by e-mail to simone [at] tlaf [dawt] com.

Thanks!

-- Simone

MClark

unread,
Feb 2, 2011, 2:51:18 PM2/2/11
to Tagalicious Beta Users
I went away from Tagalicious for a while because the betas were
horrible. After giving the latest a try, I'm back for good. I guess
that's why they call them betas ;)

I'm still getting a good number of album art that combines two
pictures in one. I have a library of ~2500 songs and don't experience
any lagging when selecting them all for tagging. Seems to be running a
lot smoother.

Nice work on fixing the bugs.

Annifey

unread,
Feb 1, 2011, 12:10:56 PM2/1/11
to Tagalicious Beta Users
I'm still testing but right now I'm trying to find out If there is
something wrong with my files or something cause quite many keep
the ! ...
Except from that it works fine for me...

/Annifey

simX

unread,
Feb 8, 2011, 3:09:30 AM2/8/11
to Tagalicious Beta Users
Hi Annifey --

I found a bug in the beta that may be causing a lot of your tracks to
be marked with the red exclamation point. Please try out 1.1.2b6 (see
the other thread) to see if it helps.

-- Simone
Reply all
Reply to author
Forward
0 new messages