I have had the same experience Srik describes. This has been batted
around for months on the forums at
http://ubuntuforums.org/showthread.php?t=608034&highlight=vbr+mp3. VBR
mp3 encoding just doesn't work in sound juicer. I have the same problem
that Srik has in that I only have one cd/dvd drive
I tried it, except I changed vbr-max-bitrate=192 to vbr-max-bitrate=256.
The cd ripped just fine, but Amarok reports a bitrate of 128 for all the
tracks. This is something that's definitley broken in g-streamer as is well
documented in the ubuntu forums, it's definitly not fixed, I don't know how
I wonder how to even begin figuring out what my problem is.
On Sun, Mar 23, 2008 at 11:17 AM, jorns <[EMAIL PROTECTED]> wrote:
> I tried the above mentioned sentence:
>
> audio/x-raw-int,rate=44100,channels=2 ! lame name=enc mode=0 vbr=4 vbr-
> quality=0 vbr-min-bitrate=160 vbr-max-bitrate=192 !
I should have made my plaintive query about what I should do next a "reply
to all."
On Sun, Mar 23, 2008 at 9:15 PM, Cliff Hall <[EMAIL PROTECTED]> wrote:
> I wonder how to even begin figuring out what my problem is.
>
>
> On Sun, Mar 23, 2008 at 11:17 AM, jor
PROTECTED]> wrote:
> I've had the same experience as Cliff Hall; however I'm using
> SoundJuicer 2.22 with Ubuntu 8.04 (beta).
>
> The xingmux parameter makes no difference to how the CD rips--I still
> end up with 128 cbr files instead of 160-192 vbr or 160-256 vbr
Does that work for you? Are you using vbr? I've tried it and it didn't
work for me.
On 3/5/08, Srik <[EMAIL PROTECTED]> wrote:
>
> Forwarded. They provided a solution: adding the "xingmux" parameter to
> the "Pipeline Gstreamer". I think this parameter should be inserted by
> default in the prof
I'll give it a try as soon as I get a CD to burn. I'm working out of town
without my CD's. I'll let you know what happens. Thanks.
On 3/5/08, Srik <[EMAIL PROTECTED]> wrote:
>
> This is the functional line:
> audio/x-raw-int,rate=44100,channels=2 ! lame name=enc mode=0 vbr=4
> vbr-quality=0 vbr
Can you refer me to a source of definitions for these pipeline arguments.
For example, I don't know what "encoding-engine-quality=2!" means. Thanks.
On Tue, Jan 5, 2010 at 4:56 PM, Tristan Hill wrote:
> I'm using a gstreamer pipeline of
>
> audio/x-raw-int,rate=44100,channels=2 ! lamemp3enc nam
Thanks.
On Wed, Jan 6, 2010 at 1:54 AM, Tristan Hill wrote:
> Options available can be seen from "gst-inspect-0.10 lamemp3enc":
>
> Element Properties:
> name: The name of the object
>flags: readable, writable
>String. Default: nul
The trouble with the misleading reporting by apps theory is that the apps
report expected values correctly when tracks are ripped using Ruby Ripper or
Grip. Seems to point the finger at g-streamer?
On Mon, Jul 12, 2010 at 3:30 AM, Bruce R <195...@bugs.launchpad.net>
wrote:
> Fascinating !
> Re-r
10 matches
Mail list logo
