wrong transfer sizes with transkode

Bug #107289 reported by drberg1000
6
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.

Revision history for this message
Andrew Ash (ash211) wrote :

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

Changed in amarok:
importance: Undecided → Wishlist
status: Unconfirmed → Confirmed
status: Unconfirmed → Confirmed
Revision history for this message
Andrew Ash (ash211) wrote :

Actually, I think the best approach would be to file a bug in the bugs.kde.org bugtracker so the Amarok devs can be aware of the problem. Could you please do so and then link to that bug from here? Thanks

Changed in amarok:
assignee: nobody → ash211
status: Confirmed → Incomplete
Revision history for this message
drberg1000 (drberg1000) wrote :

While I still think it would be a good addition to Amarok, I'm not currently using the iRiver, Amarok or Ubuntu. Would you mind filing the bug as I don't have any version info or the software on my system?

--Dave

Revision history for this message
Andrew Ash (ash211) wrote :
Changed in amarok:
status: Confirmed → Unknown
Changed in amarok:
status: Unknown → Invalid
Revision history for this message
Harald Sitter (apachelogger) wrote :

Closing this report, since that feature would be too big of size to be maintained by Ubuntu as patch against Amarok, and the Amarok Project itself doesn't have any intention to implement this right now (as stated in the linked upstream bug report).

Thanks for your suggestion nonetheless.

Changed in amarok:
status: Incomplete → Won't Fix
Changed in amarok:
status: Invalid → Unknown
Changed in amarok:
importance: Unknown → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.