[okular] [Bug 436709] New: Autoplaying of renditions (audio/video)

[Michal Vlasák]

https://bugs.kde.org/show_bug.cgi?id=436709

            Bug ID: 436709
           Summary: Autoplaying of renditions (audio/video)
           Product: okular
           Version: 21.04.0
          Platform: Archlinux Packages
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: PDF backend
          Assignee: okular-devel at kde.org
          Reporter: lahcim8 at gmail.com
  Target Milestone: ---

Created attachment 138202
  --> https://bugs.kde.org/attachment.cgi?id=138202&action=edit
Example file, mentioned in the bug description.

I think that the current handling of "AutoPlay" is wrong for Renditions.
Currently, Okular obeys "/A" field from
https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#G12.2318501.
Although the difference is subtle, I think that this field shouldn't correspond
to Okular's notion of autoplay:

The activation itself is handled by Rendition actions, like with Movie
annotations. "/A" field controls behaviour after annotation is activated and
may be used to prevent playing (the only use is probably to display first frame
of video instead of normal apperance, although even this seems weird).

The following patch makes Okular not respect the /A field (which has no
equivalent in Okular).

--- a/generators/poppler/generator_pdf.cpp
+++ b/generators/poppler/generator_pdf.cpp
@@ -237,7 +237,7 @@ Okular::Movie *createMovieFromPopplerScreen(const
Poppler::LinkRendition *popple
         movie->setPlayMode(Okular::Movie::PlayLimited);
         movie->setPlayRepetitions(rendition->repeatCount());
     }
-    movie->setAutoPlay(rendition->autoPlay());
+    movie->setAutoPlay(false); // will be triggered by external
RenditionAction
     return movie;
 }

However this means that there is now a problem of how to handle the autoplay. I
would expect Screen annotations additional actions (/AA) to work, but it
currently doesn't. I didn't yet discover the cause.

To illustrate how autoplay with additional actions doesn't work after applying
the above patch I attach an example. (It can also be used to confirm the wrong
handling of autoplay, when `/A false` is removed.)

-- 
You are receiving this mail because:
You are the assignee for the bug.