ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

DonationCoder.com Software > N.A.N.Y. 2009

NANY 2009 Release: Trout (audio player)

<< < (89/174) > >>

skwire:
I guess I should explain myself a bit further...

I have, currently, around 87,000 tracks in my music collection.  foobar, with the database enabled and that many tracks scanned in, uses several HUNDRED megs of RAM on my computer and generally slows everything down.  Furthermore, it's rather slow to start and be ready to play music with that large of a database.  So, I only load it up when I want to do some serious music listening.  I also use it to playback my emulated video game music files and convert my lossless files to other formats when necessary. 

I use Trout for all the other times I listen to music on my computer...working, surfing, coding, IRC, etc.  As I've said before, I wrote Trout partly as a challenge to myself to see how far I could take AutoHotkey as a language.  Trout is hardly the technical player that foobar is and I'm not even in the same ballpark as Peter Pawlowski (foobar's author) when it comes to coding.  That being said, I'm still humbled at the response it's received over this past year; I released it on January 1st as part of last year's NANY.

Does that help to explain things?

skwire:
v1.0.3 build 257 - 2009-12-11
    * Made a change to how the main listview sorts accented characters e.g.
      "Édith Piaf" should now sort with "E" and not to the bottom of the list.
      (Thanks, Leif Larsson)

Greybrow:
My foobar takes 28MB of ram and starts within 1 second wait time, kind of 10x less than firefox. So it's still very usable. But I understand you that with bigger collection it takes much more.

I was wondering how much would it take, with library turned off. So I checked :) 14MB
Trout was 8MB empty, and 20MB with all files loaded as playlist.

I tried to drag&drop files to trout, and it failed for the first time. It shown me an icon with plus sign, when I hovered the gray menu zone, but after I dropped it there it didn't add them to the playlist. So I tried second time but dropped files to the playlist zone, and it started to add them.
It is nice, that I could play music that was already loaded while the files were in the queue. But list kept jumping to the beginning while loading and that was bit annoying.

I wondered what would happen, if I exit program, while still loading files. So I closed and reopened trout. And there were only those files, that were already read before exiting.

After I read all the files from disk to playlist, and then reopened program. It took about 3 seconds to open. So it seems slower than foobar with library.
It took lots of time opening them for the first time, probably the same as foobar importing files to the library for the first time.

Strangely I like trout interface better :)

skwire:
I was wondering how much would it take, with library turned off. So I checked :) 14MB-Greybrow (December 11, 2009, 07:27 PM)
--- End quote ---

Same here.  Without the database enabled, foobar is extremely quick to start up.  However, I like having a searchable database within my audio players.

Trout was 8MB empty, and 20MB with all files loaded as playlist.-Greybrow (December 11, 2009, 07:27 PM)
--- End quote ---

How many files?

I tried to drag&drop files to trout, and it failed for the first time. It shown me an icon with plus sign, when I hovered the gray menu zone, but after I dropped it there it didn't add them to the playlist. So I tried second time but dropped files to the playlist zone, and it started to add them.-Greybrow (December 11, 2009, 07:27 PM)
--- End quote ---

Correct, you need to drop onto the playlist.

It is nice, that I could play music that was already loaded while the files were in the queue. But list kept jumping to the beginning while loading and that was bit annoying.
I wondered what would happen, if I exit program, while still loading files. So I closed and reopened trout. And there were only those files, that were already read before exiting.-Greybrow (December 11, 2009, 07:27 PM)
--- End quote ---

This is normal behaviour.  When you drop files onto Trout, it has to read the files' tags to be able to populate the list.  So, if you close down Trout while it's scanning through the dropped files, it a) doesn't have a chance to read them all and b) doesn't have a chance to save the playlist when it's done scanning.

After I read all the files from disk to playlist, and then reopened program. It took about 3 seconds to open. So it seems slower than foobar with library.
It took lots of time opening them for the first time, probably the same as foobar importing files to the library for the first time.-Greybrow (December 11, 2009, 07:27 PM)
--- End quote ---

Trout's opening speed will depend on how many files are in the list.  I rarely keep more than 30 or 40 items in my playlist.

I've been working on a database functionality within Trout that has file/tag searching and Shoutcast/Icecast browsing.  It's not nearly as slick as foobar's auto-updating database but it uses one HELLUVA lot less RAM.  For instance, with my database of 87,000 tracks loaded and searchable, Trout uses 32 megs of RAM (with an empty playlist).  The tag searching is of the find-as-you-type type and is pretty darn fast (if I may be so bold).  Here are some screenshots:

NANY 2009 Release: Trout (audio player)NANY 2009 Release: Trout (audio player)
NANY 2009 Release: Trout (audio player)NANY 2009 Release: Trout (audio player)

Note the search time in the status bar of the first screenshot.

skwire:
v1.0.3 build 258 - 2009-12-12
    * Trout will now unmute itself if changes are made to the volume while it's muted.  (Thanks, lanux128)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version