problema con amarok

[PhantomX]

ciao,

ho provato con tutti gli engines (arts,xine,gsstreamer) ma non riesco a fare andare l audio.

la mia scheda audio è integrata su una K7M-RM e da lspci risulta essere vt82c686 ac97 controller.

la distro è ubuntu. se uso ad esempio xmms funziona perfettamente l audio.

se uso gsstreamer mi avvisa che non è in grado di riprodurre il file, arts non dice nulla, mentre con xine sembra partire la riproduzione, anche se il tempo scorre + velocemente e comunque non si sente nulla

avete qualche consiglio?

[Scoperchiatore]

Originariamente inviato da PhantomX

ciao,

ho provato con tutti gli engines (arts,xine,gsstreamer) ma non riesco a fare andare l audio.

la mia scheda audio è integrata su una K7M-RM e da lspci risulta essere vt82c686 ac97 controller.

la distro è ubuntu. se uso ad esempio xmms funziona perfettamente l audio.

se uso gsstreamer mi avvisa che non è in grado di riprodurre il file, arts non dice nulla, mentre con xine sembra partire la riproduzione, anche se il tempo scorre + velocemente e comunque non si sente nulla

avete qualche consiglio?

Hai provato a testare gstreamer secondo le istruzioni del sito?

Q: Ok, I've installed GStreamer. What can I do next ?

A: First of all, verify that you have a working registry and that you can inspect them by typing

$ gst-inspect fakesrc

This should print out a bunch of information about this particular element. If this tells you that there is "no such element or plugin", you haven't installed GStreamer correctly. Please check how to get GStreamer If this fails with any other message, we would appreciate a bug report.

It's time to try out a few things. Start with gst-launch and two plug-ins that you really should have : fakesrc and fakesink. They do nothing except pass empty buffers. Type this at the command-line :

$ gst-launch -v fakesrc num-buffers=3 ! fakesink

This will print out output that looks similar to this :

RUNNING pipeline ...
fakesrc0: last-message = "get ******* (fakesrc0:src)gt; (0 bytes, 0) 0x8057510"
fakesink0: last-message = "chain ******* (fakesink0:sink)lt; (0 bytes, 0) 0x8057510"
fakesrc0: last-message = "get ******* (fakesrc0:src)gt; (0 bytes, 1) 0x8057510"
fakesink0: last-message = "chain ******* (fakesink0:sink)lt; (0 bytes, 1) 0x8057510"
fakesrc0: last-message = "get ******* (fakesrc0:src)gt; (0 bytes, 2) 0x8057510"
fakesink0: last-message = "chain ******* (fakesink0:sink)lt; (0 bytes, 2) 0x8057510"
execution ended after 5 iterations (sum 301479000 ns, average 60295800 ns, min 3000 ns, max 105482000 ns)

(Some parts of output have been removed for clarity) If it looks similar, then GStreamer itself is running correctly.

Q: Can my system play sound through GStreamer ?

A: You can test this by trying to play a sine tone. For this, you need to link the audiotestsrc element to an output element that matches your hardware. A (non-complete) list of output plug-ins for audio is

*

osssink for OSS output
*

esdsink for ESound output
*

artsdsink for aRTs output
*

alsasink for ALSA output
*

jacksink for JACK output

First of all, run gst-inspect on the output plug-in you want to use to make sure you have it installed. For example, if you use OSS, run

$ gst-inspect osssink

and see if that prints out a bunch of properties for the plug-in.

Then try to play the sine tone by running

$ gst-launch audiotestsrc ! osssink

and see if you hear something. Make sure your volume is turned up, but also make sure it is not too loud and you are not wearing your headphones.

In GNOME, you can configure audio output for most applications by running

$ gstreamer-properties

which can also be found in the start menu (Applications -> Preferences -> Multimedia Systems Selector). In KDE, there is not yet a shared way of setting audio output for all applications; however, applications such as Amarok allow you to specify an audio output in their preferences dialog.

Q: How can I see what GStreamer plugins I have on my system ?

A: To do this you use the gst-inspect command-line tool, which comes standard with GStreamer. Invoked without any arguments,

$ gst-inspect

will print out a listing of installed plugins. To learn more about a particular plugin, pass its name on the command line. For example,

$ gst-inspect volume

will give you information about the volume plugin.

Also, if you install the gst-editor package, you will have a graphical plugin browser available, gst-inspect-gui.

Q: Where should I report bugs ?

A: Bug management is now hosted on GNOME's Bugzilla at http://bugzilla.gnome.org, under the product GStreamer. Using bugzilla you can view past bug history, report new bugs, etc. Bugzilla requires you to make an account here, which might seem cumbersome, but allows us to at least have a chance at contacting you for further information, as we will most likely have to.

Q: How should I report bugs ?

A: When doing a bug report, you should at least describe

*

your distribution
*

how you installed GStreamer (from cvs, source, packages, which ?)
*

if you installed GStreamer before

It also is useful for us if you attach output of the gst-feedback command to your bug report. If you're having problem with a specific application (either one of ours, somebody else's, or your own), please also provide a log of gst-mask by running

myapp --gst-mask=-1 > mask.log 2>&1
gzip mask.log

(interrupting the program if it doesn't stop by itself) and attach mask.log.gz to your bug report.

Prova a seguire questa guida per filo e per segno: se gstreamer NON suona, allora è un problema suo. Se suona con wav e ogg, ma non con gli mp3, è un problema di codec. Se suona sempre, allora è colpa di amarok (mi sembra molto difficile, dato che amarok non ha alcun controllo reale sul suono, ma delega tutto ai plugin)