Closed GoogleCodeExporter closed 8 years ago
Hadn't heard of that encoder, but I'll give it look. Also, could you provide
me with
the pipeline that you added to gnome-audio-profiles-properties for the helix mp3
encoder? Thanks!
Original comment by bdpep...@gmail.com
on 14 Jan 2009 at 11:40
[deleted comment]
Hey, great!
My pipeline is
audio/x-raw-int,rate=44100,channels=2 ! xingenc bitrate=128
at the moment. I’m not sure whether a "! id3v2mux" is needed at the end. I
didn’t get that far.
In case you are interested, here’s a recent listening test. I was very
surprising. From the look of it, the Helix
encoder is at least not largely defective and should do it for on the road
listening. 90× real time encoding
speed is much better than Lame after all.
http://www.listening-tests.info/mp3-128-1/results.htm
Original comment by towolf
on 15 Jan 2009 at 10:33
Most likely you should have the 'id3v2mux' element in your pipeline, since it
adds an
ID3v2 header to the beginning of MP3 files using taglib.
I looked into this a bit the other night, and I'm probably going to need to
read the
source for the gnome-media audio profile widget to get a better understanding
of how
it is getting the list of gstreamer plugins available. Currently, when I
create a
new audio profile for the xing plugin, n-s-c doesn't recognise the new profile.
Original comment by bdpep...@gmail.com
on 17 Jan 2009 at 12:55
Is there a possibility that "you" link to gstreamer in some sort of deprecated
way? I asked on #gstreamer and
#banshee about this, and the most informed guess seemed to be that "gstreamer"
is not dynamically linked
correctly.
One more datapoint may be that Banshee, the player which hosts this codec, can
also use the Helix/Xing
element for transcoding and ripping. (Unfortunately it will only transcode onto
a portable device, not to just
any destination folder). But as far as I can tell it does not use the
gnome-media profiles but a custom profile
system.
Original comment by towolf
on 17 Jan 2009 at 6:27
Attachments:
I don't really don't think it's due to the linking, otherwise the more
traditional
plugins wouldn't be working also. Right now it's looking like a problem is
occurring when gnome-media is being initialized.
In the meantime, I would suggest using the lame plugin and use the bitrate
option,
and not the vbr option. Based on my informal tests, this is almost as quick as
the
gst-xing plugin.
Original comment by bdpep...@gmail.com
on 19 Jan 2009 at 3:15
Closing, and re-opening on the GNOME infrastructure.
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=633307
Original comment by bdpep...@gmail.com
on 27 Oct 2010 at 11:14
Original issue reported on code.google.com by
towolf
on 14 Jan 2009 at 10:16