For anyone struggling with this problem and searching for workarounds, the
upstream discussion is a good read. Apparently, it is possible to entirely
disable the housekeeping mechanism that is responsible for this problem:
https://bugzilla.gnome.org/show_bug.cgi?id=625609#c6
Doing so will
(1) di
Ah, so you mean the new parameters are poorly documented???
BTW, xingmux only adds a header, it doesn't touch or affect the audio in any
way:
http://www.gstreamer.net/data/doc/gstreamer/head/gst-plugins-ugly-plugins/html/gst-plugins-ugly-plugins-xingmux.html
It would be clearer and technically mo
I also submitted a patch upstream which processes the file
gnome-audio-profiles.schemas.in.in , from which gnome-audio-profiles.schemas is
generated at compile time. The package maintainer is free to choose whichever
patch they find most convenient to use. ;)
http://bugzilla-attachments.gnome.or
I attached a patch to be applied to /usr/share/gconf/schemas/gnome-
audio-profiles.schemas
> What's the next step to get the bug solved?
The next step is to get this patch into Maverick. In an ideal world,
gnome-media should adopt it, then Ubuntu should simply pull it in from
the upstream repo's.
- This is not about bit rate, this is about quality. Getting a higher bit rate
does not automatically equal getting a higher quality. In fact, botching the
psychoacoustics model with a load of settings is a good recipe to get similar
or higher bit rates but a lower quality.
- For assessing quali
** Also affects: gnome-media via
https://bugzilla.gnome.org/show_bug.cgi?id=619642
Importance: Unknown
Status: Unknown
--
Sound Juicer - MP3 quality doesn't change
https://bugs.launchpad.net/bugs/195483
You received this bug notification because you are a member of Ubuntu
Desktop Bug
BruceR, the things you're saying are simply not true. This is complex
business and I can understand it confuses you, but please don't make
stuff up. Browse Gnome Bugzilla (links at the end of this post). Look at
the source code. Encode the same sample with gstreamer and with
standalone LAME and do
The gstreamer bug is fixed but the implementation of this fix depends on
sound juicer - updated remote watch accordingly.
** Changed in: sound-juicer
Importance: Critical => Unknown
** Changed in: sound-juicer
Status: Fix Released => Unknown
** Changed in: sound-juicer
Remote watch: G
Bruce R, please read all the posts carefully. The "lame" element is known to be
broken, and has been superseded by "lamemp3enc". Stop encouraging people to use
the "lame" element.
https://bugzilla.gnome.org/show_bug.cgi?id=494528
(FYI, Gabriel Bouvigne is one of the core LAME developers).
I did
OK, this might be getting confusing. Just a summary for people who are
new to this bug, and some suggestions for future directions:
- People initially filed this as a sound-juicer bug, while *at that time*, it
was actually a gstreamer bug; the "lame" element, which was responsible for
encoding m
Seems that I was was a bit too quick on the trigger with my "nobody
takes it serious" statement. Sebastian Dröge essentially fixed the bug
upstream, and I have good hopes that it won't be long before the fix
comes to an Ubuntu repository near you :)
--
Sound Juicer - MP3 quality doesn't change
ht
** Also affects: gstreamer via
http://bugzilla.gnome.org/show_bug.cgi?id=494528
Importance: Unknown
Status: Unknown
--
Sound Juicer - MP3 quality doesn't change
https://bugs.launchpad.net/bugs/195483
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
They rightly marked that bug report "resolved" because (just like here on
launchpad) it was filed as a Juicer bug, while it really is a bug in the
gstreamer LAME plugin, not in Juicer. The actual bug that causes all our misery
is here:
http://bugzilla.gnome.org/show_bug.cgi?id=494528
The proble
@Christian Niemeyer: I believe vbr-mean-bitrate actually requests ABR
encoding, which conflicts with vbr-quality=4, the switch that requests
VBR encoding.
@tigerdog: Nyquist's theorem dictates that the lowpass frequency needs
to be significantly lower than half of the bitrate (44100) to avoid
alia
Things are actually worse than they seem. As a matter of fact, LAME should only
be invoked with a handful of simple "master" options (like -V4), each of which
activates myriads of internal encoder parameters. Manually setting those
parameters through "advanced" switches will disrupt the carefull
15 matches
Mail list logo
