Length and Quality
 

I'm a recent convert to LimeWire Pro from the fiasco that is Morpheus and the spy-scam that is Grokster - but there are two features I've been looking for that don't seem to exist on LimeWire.

1) On those other services, you can tell the recording quality of audio files by looking at whether a file is, say, 96 or 128 or 256. The higher that number, the larger the file, but also the better the quality. Is there any way to find this info using LimeWire, or can it be programmed in as an option? When I download something from LimeWire and then open it up in Grokster, all that info is there.

2) Track length. Again, the info is there when I open a file from LimeWire in Grokster. This is important, because I want to know what version of a song I'm getting, to tell whether I'm getting the original. Is there any way to find this info before a download?

These are the two features that I would love to see. Otherwise, the interface is very neat, and the experience is a welcome relief from those other programs!

Hello,

You'll be pleased to find that the latest version of LimeWire already supports these features! When you search for an audio file, the bitrate column will display the bitrate. Just click on the column heading to sort the results by bitrate. You will also find that if you right click those column headings, you can choose from a wide variety of criteria with which to sort your results.

Enjoy!
Avi

I saw the bitrate column after I'd played around with LimeWire for a while - perhaps the sixth song I searched for - nothing obscure, I was trying out my searches on standard stuff like the Beatles - had a few returns that listed "Bitrate". However, the great majority don't seem to list bitrate, unlike on the other services. Since the info is embedded in most of the files (for example, S n G's "S of S" had no info in the bitrate column when I downloaded it from LimeWire, but told me the bitrate in the "Quality" column when I transfered it and opened it in Grokster), it seems that somehow LimeWire isn't presenting all of the useful info that is available.

And the length of the track is nowhere to be found on LimeWire, right?

No specific names which may suggest infringement of copyright, please.
Any specific file names are not important in regards to your question.
thanks

The length as well as other useful information can be displayed by rightclicking the column headers. Also, please leftclick the bitrate column header and you will be able to sort all the files with "embedded" bitrate to the top.

Additionally, if you select the "Audio" choice while doing a search, and check "More Search Options", you can even enter search criteria depending on these factors you have mentioned.

I will also mention this to the developers. We've had a few requests more advanced search criteria.

Hope that helps!
Avi

Thanks - it's good to learn about the length feature! However, now that I can see where the length info ought to be, I see that for some reason LimeWire seems to not find length info for most of the files that are distributed with that data available.

While I can't say for sure, I would venture LimeWire can only display the data it's supplied by the host. If there's no bit rate or length (or any of the other fields), it's most likely because the client hosting that file didn't provide that info in the search return.

test
 

test

OK, now it's 3 YEARS from the time when this thread was created.

But still ... (4.4.5)

- length is in SECONDS, making it a huge pain to always re-calculate the time by hand to find out the length of a track
Why isn't this fixed after 3 years when this feature was requested?!

- it seems that the length (and other) column(s) are always *individual* for every search tab.
That is, if you have 10 search tabs, you will have to enable the length column 10 time, which is a pain in the neck.

No way yet to set the columns I always want by DEFAULT?!

Apart from those annoyances, LimeWire is great! :D

Nevermind, problem found why length had to be readjusted all the time. (3rd party app)

OK, yet "length in timecode" request still applies. :)