When avidemux' Tools/Preferences/Audio/AudioDevice selector shows : Alsa, And Alsa default output redirected to Jack via appropriate declarations in asound.conf, Playing any multimedia file under avidemux leads to the correct playing of a few frames (sound included) then avidemux freezes definitely. Reproducible: Always Steps to Reproduce: 1.Log into a system which asound.conf is set as described further on, 2.Start Jack's daemon 3.Start Avidemux with Audio Output set to Alsa 4.Load and play any multimedia file Actual Results: Plays a few frames correctly then freezes. Expected Results: Go on playing or at least display some error message. 1/ Software information : - avidemux-2.5.1_p5428 USE="aac aften alsa amr dts gtk jack libsamplerate mp3 nls qt4 sdl truetype vorbis x264 xv xvid -esd -oss -pulseaudio" - jack-audio-connection-kit-0.118.0 USE="alsa mmx sse -3dnow (-altivec) (-coreaudio) -cpudetection -debug -doc -examples -oss" 2/ Listing for asound.conf : pcm.!default { type plug slave { pcm "jack" } } pcm.jackplug { type plug slave { pcm "jack" } } pcm.jack { type jack playback_ports { 0 alsa_pcm:playback_1 1 alsa_pcm:playback_2 } capture_ports { 0 alsa_pcm:capture_1 1 alsa_pcm:capture_2 } } 3/ Traces from console after starting the playbackXv init ok Xv init ok [Alsa]ALSA EAGAIN ... (Preceeding log entry repeated n times) [Alsa]ALSA EAGAIN jack_client_thread zombified - exiting from JACK [Alsa]ALSA EAGAIN ... (Preeceeding log entry repeated... ad libitum ! 4/ I do agree that this can be seen as a ridiculous way to use avidemux as long as avidemux supports an output to jack. This support is however not fully functionnal.
5/ Additionnal observations on the Jack's side : 5.1/ The number of frames played by Avidemux before it freezes is proportional to the value of Jackd's Frames/Period (--period) parameter 5.2/ Extract of jackd's traces when Avidemux freezes : ... load = 0.2769 max usecs: 29.000, spare = 11580.000 22:55:26.550 JACK connection graph change. server thread back from poll marking client alsa-jack.jackP.19874.2 with SOCKET error state = Not triggered errors = 0 trying to lock graph to remove 1 problems we have problem clients (problems = 1 ++ Removing failed clients ... client alsa_pcm error status 0 client alsa-jack.jackP.19874.2 error status 10000000 removing failed client alsa-jack.jackP.19874.2 state = Not triggered errors = 10000000 removing client "alsa-jack.jackP.19874.2" client qjackctl error status 0 ++ jack_sort_graph ++ jack_rechain_graph(): +++ client is now alsa_pcm active ? 1 client alsa_pcm: internal client, execution_order=0. +++ client is now qjackctl active ? 1 client qjackctl: start_fd=7, execution_order=0. client event poll on 111 for qjackctl starts at 51850194528 back from client event poll after 3 usecs client qjackctl: wait_fd=18, execution_order=1 (last client). -- jack_rechain_graph() -- jack_sort_graph -- Removing failed clients ... after removing clients, problems = 0
Can you please test 2.5.4 and see if this problem is fixed or not?
(In reply to comment #2) - 2.5.3-r3 QT : Problem not solved - 2.5.4 GTK : Problem not solved - 2.5.4 QT : Cannot test because of Bug 342909 ====== As Bug 338798 appears in a good way for resolution with avidemux >= 2.5.3-r3, this specific audio setting (alsa as avidemux audio output + alsa default output redirected to Jack) can appear useless => A clean stop of the video playback in addition with a message box showing some alert when detecting the zombification of Jack's client thread sound reasonable for closing this bug.
I can't understand your last comment. Can you please elaborate?
(In reply to comment #4) Thank you Markos for doing your best with Avidemux. I suggested to upstream this enhancement I would consider correcting a (limited) lack of error management from Avidemux. A month ago now and they do not seem to care. (I can understand as I prefer them working on new features) I think you can close this bug according to your wishes (CANTFIX / UPSTREAM...) Thank you again for your help.
Closing per comment #5
