** Changed in: rhythmbox
       Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/148672

Title:
  USB mass storage and rhythmbox problems

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  Using gutsy latest:

  My music library is stored as FLAC.  I have a Nokia N770 that I
  occasionally sync music to.  HAL correctly recognizes this device, and
  mounts it as USB storage.  However, when I drag and drop songs/albums
  onto it in rhythmbox, a few problems occur:

  1.  It transcodes music to the device as directed by the HAL config
  file (which tells it to use aac).  However, the resulting M4A audio
  files are mostly static (you can kinda hear the music once in a
  while).  If I change the HAL config files to use MP3 and re-burn to
  the device, the MP3s play fine.  That said, it seems the AAC
  transcoder in gutsy is broken.

  2.  Why isn't there a UI in rhythmbox to set the
  format/bitrate/extension used for the transcode?  Hacking the HAL
  config files isn't very user friendly, and as far as I can tell, it
  only allows you to set the mime-type, and not the bitrate, or
  extension.  Having both these latter two items hardcoded by the
  HAL/Banshee code is problematic.  For example, the N770 media player
  can playback AAC - but it wants the extension to be AAC, not the M4A -
  and I think it is always using 128kbit, which is fine for MP3, but
  64kbit would be ok for AAC.  I'd like to be able to specify both the
  extension and bitrate, in addition to the format.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/148672/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to