I use the LaTeX 'multimedia' package to include movie files into my pdf presentations. 'multimedia' has an option 'showcontrols' which switches on the controls of the movie player. This mostly works, but the progress bar of the control field does not advance while the movie plays. It remains on the far left. Also, there is a 'pause' button which does what it is supposed to do. During pause, I would expect to be able to pull the progress slider to jump to different parts of the movie. This also does not work. The progress slider cannot be moved anywhere. Is this a bug or do I have wrong expectations here? Reproducible: Always
Created attachment 82917 [details] Example pdf file
Created attachment 82918 [details] The movie
Created attachment 82919 [details] The corresponding tex sources
Works here, only the first time i play, the second time i don't get the controls at all, but that'd be bug 326194 Which poppler, okular and phonon versions do you have? Also which phonon backend are you using?
I am using poppler & okular compiled from git master. My phonon backend is phonon-backend-vlc version 0.6, from Debian stable.
Can you give the gstreamer backend a try?
With the gstreamer backend 4.6.0 from Debian stable it does indeed work. Moving around in the movie is quite uncomfortable and laggy, but not worse than when I look at the movie directly in totem or vlc. So definitely not an okular issue. Thanks for giving me the hint. Should this be reassigned to the vlc backend, or simply closed?
Let's try to reasign to the phonon-vlc people
Cannot reproduce with Phonon masters unfortunately. Perhaps a debug log [1] would shed some light on the cause. Alas, I can not even think of why this would not work with 0.6. [1] http://techbase.kde.org/Development/Tutorials/Debugging/Phonon#Environment_Variables
Feel free to simply close this if you think that is has been fixed between 0.6 and master. Meanwhile I can use the gstreamer backend after all. If you are interested in investigating, then I'll try my best to help you. Attached you'll find the desired debugging log.
Created attachment 82962 [details] phonon backend debugging log This is a log of okular during - starting okular from the console with the test file - clicking on the movie - waiting until it has finished playing - closing okular
(In reply to comment #11) > This is a log of okular during > - starting okular from the console with the test file > - clicking on the movie > - waiting until it has finished playing > - closing okular One with the problems would help :P i.e. please try to seek around and pause/unpause You could also grab phonon-vlc 0.6.2 and test with that, there are quite some bug fixes between .0 and .2 and at least one could potentially play into the issue at hand.
The log is "with the problems": the movie plays, but the slider doesn't move. Pause/unpause does work. I'll attach a new log where I have paused and unpaused a few times. Trying the pull the slider in paused state (which doesn't work -- the slider doesn't move) does not create any debugging output.
Created attachment 82967 [details] Another log, this time with pause/unpause
(In reply to comment #13) > The log is "with the problems": the movie plays, but the slider doesn't move. That is probably because of [1] and also the reason why seeking does not work while paused (pausing however does work as expected per your last log). As a matter of fact you may suggest to the Debian packagers that have a look at the phonon vlc changes between .0 and .2 [2] and cherry pick what they deem qualifying for stable. [1] https://projects.kde.org/projects/kdesupport/phonon/phonon-vlc/repository/revisions/271761a8510bc2a62405e77fc9e5e13dc22155de [2] http://quickgit.kde.org/?p=phonon-vlc.git&a=log&h=4348517b34cf5703b92344181542502c7d466a87
Thanks for the pointers. However, I just backported the phonon-backend-vlc-0.6.2 package from Debian testing, and it did not solve the problem. The slider continues to not move.
Very curious. I'll have to look at the okular side of things then.
Hi Harald, Albert, I updated my entire system to Debian testing today, and the error is gone. Thank you very much for your help.