Somehow the comment from February slipped under my radar. However, in
looking at it, I don't understand why the external site was referenced:
I'm not having a problem with Banshee sending MP3 files to my phone.
It's just having them sent to my phone in the correct _bitrate_, if the
file is _already_ an MP3 (but at a bitrate different from what the phone
supports). The HAL specification that the referenced document talks
about simply states how to put a file on the drive to indicate its
supported MIME types—not bit rates.
Maybe I need to re-state the problem by way of example: I have two
files, A.ogg and B.mp3. They are both encoded in stereo, 256kbit rate.
I'd like to put them onto my phone. When I do this, Banshee will encode
A.ogg into a 128Kbit MP3 file before putting it on the phone. However,
seeing that B.mp3 is already an MP3, it just puts it on the phone as-is,
using the 256kbit rate, and not the 128 that I specified in the
preferences for the device (again, within Banshee). My (uneducated)
guess would be that the problem is that since it sees that it is already
the proper MIME type of file, it doesn't even inspect it to see if the
bitrate is correct.
** Changed in: banshee (Ubuntu)
Status: Invalid => New
--
Support forced audio format for broken devices
https://bugs.launchpad.net/bugs/182467
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
