[Bug 945987] Re: No Settings are available in "Preferred format", only preset defaults are used

[Doug McMahon]

As far  as I can tell, (& I've never used  transmageddon before), the
new package in 12.10 is broken & will not transcode anything.

"$ transmageddon
Traceback (most recent call last):
  File "transmageddon.py", line 863, in on_transcodebutton_clicked
    self._start_transcoding()
  File "transmageddon.py", line 736, in _start_transcoding
    self.videopasstoggle, self.interlaced, self.inputvideocaps)
  File "/usr/share/transmageddon/transcoder_engine.py", line 60, in __init__
    Gst.preset_set_app_dir("/usr/share/transmageddon/presets/")
NameError: global name 'Gst' is not defined "

If I were to purge RB* & install the previous transmageddon then it appears to work fine in a limited test.
Does that need a new bug or is this break known & or expected?

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/945987

Title:
  No Settings are available in "Preferred  format", only preset defaults
  are used

Status in The GStreamer Multimedia Framework:
  Incomplete
Status in “rhythmbox” package in Ubuntu:
  Fix Released
Status in “transmageddon” package in Ubuntu:
  Fix Released
Status in “rhythmbox” source package in Precise:
  In Progress
Status in “transmageddon” source package in Precise:
  Triaged

Bug description:
  = Transmageddon =

  [ Description ]

  Transmageddon ships gstreamer preset files in a shared directory,
  /usr/share/gstreamer-0.10/presets. As these presets have fixed names,
  this is unhelpful. An upstream commit included in 0.21 moves these to
  a private location.

  [ Development fix ]

  Fixed in Quantal in an identical way.

  [ Regression potential ]

  If the fix doesn't work then it's possible that transmageddon won't be
  able to find its presets and will not be able to encode anything.

  [ Testing ]

  There should be no functional difference. Test with both the old and
  new transmageddon that you can still transcode some videos using a
  variety of settings, and that the settings you choose are the ones
  which are pplied.

  = Rhythmbox =

  [ Description ]

  No encoding preset is shipped with Rhythmbox, meaning that subpar
  defaults for encoding are selected.

  [ Development Fix ]

  Quantal's Rhythmbox has support for custom encoding settings. There,
  we've shipped the same set of "ubuntu-default" presets, but have set
  the default (in rhythmbox.gep) to use the user's selected custom
  settings.

  [ SRU fix notes ]

  We Break and Replace old transmageddons, which have a file conflict
  with this version.

  ** Thus, the Rhythmbox SRU MUST NOT be accepted, both into -proposed
  and -updates, without the transmageddon one. Otherwise we will
  introduce upgrade failures. **

  [ Regression potential ]

  Perhaps the new settings will fail to apply and Rhythmbox will pick up
  a worse set than it had before.

  [ Testing ]

  Rip a CD with the new Rhythmbox with the default settings and
  determine that the quality and other encoder parameters are what they
  should be.

  [ Original Description ]

  This has been going on since 11.10 dev, maybe should be addressed

  In Edit > Preferences, on the Music tab the Settings button for Preferred Format is greyed out & unavailable. So there is no user available means to adjust encoding for vorbis, mp3, mp4, ect.
  Even using something like sound-juicer to change the very same 'Preferred.. '  is of no use, Rhythmbox doesn't  use.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: rhythmbox 2.95-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
  Uname: Linux 3.2.0-17-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94-0ubuntu1
  Architecture: i386
  Date: Sat Mar  3 19:25:18 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120302)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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