wrong transfer sizes with transkode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Amarok |
Unknown
|
Wishlist
|
|||
amarok (Ubuntu) |
Won't Fix
|
Wishlist
|
Andrew Ash |
Bug Description
Binary package hint: amarok
I use an iRiver ifp device and transKode with Amarok. When trying to cram a specific playlist onto the 128MB device at the highest possible quality I stumbled upon a minor user interface bug. The status bar immediately under the Transfer Queue container gives the size of the files on disk regardless of the settings chosen in transKode.
For example, adding a 20 MB flac file to the queue with transKode set to convert it to a 64kbps mp3 file results in a queue size of 20MB. Of course the resulting mp3 file will be about 1/10th the size of the flac.
My suggestions: If there is a way for Amarok to know what size the playlist will be after transKoding that number should be used instead. If not, an estimated guess would be useful. If nothing else a note in the tooltip or status bar that the transfer size may change depending on transkode settings would make it clear where the number comes from.
Changed in amarok: | |
status: | Unknown → Invalid |
Changed in amarok: | |
status: | Invalid → Unknown |
Changed in amarok: | |
importance: | Unknown → Wishlist |
That is a great idea. The more information that Amarok can provide to the user the better.
The problem now is that Amarok is in the middle of development for the Amarok 2.0 release in a few months, and the 1.4.5 series will only have simple bugfixes included. I think this sort of change would require either more work done on the transkode script or integrating it more into the Amarok core. I'd love to see tranksode integrated into Amarok, though, since it provides some great functionality.
Once Amarok 2.0 is released, make sure to bug me on this so I can see if I can get the developers to include it, if they haven't already.
Thanks