You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an epub with media overlays for some pages, but not others, and none of the <audio> elements in the .smil file use the optional clipBegin/clipEnd attributes. In both Thorium 3.0 and 3.1 only the first audio file on a page plays, whether by pressing the Play button or advancing to the next page - in other words, there is no continuous playback. But with other readers, such as Adobe Digital Editions and Colibrio Reader, there is continuous playback with the same epub.
The epub meets all EPUB3.3 requirements as validated with EPUBCheck, so it would appear that Thorium is not handling audio correctly if these optional attributes are not included - would that be a valid assumption or could there be another cause?
The text was updated successfully, but these errors were encountered:
Hello, the SMIL clipBegin/End attributes are unlikely to be the cause of the problem. Are you able to privately share the EPUB so I can take a look and test at my end? (I wrote the playback engine in Thorium, and some of my "old Readium" code is probably in Adobe Digital Edition too, so I will be able to troubleshoot this quickly).
My email is public: [email protected]
I have an epub with media overlays for some pages, but not others, and none of the
<audio>
elements in the .smil file use the optionalclipBegin
/clipEnd
attributes. In both Thorium 3.0 and 3.1 only the first audio file on a page plays, whether by pressing the Play button or advancing to the next page - in other words, there is no continuous playback. But with other readers, such as Adobe Digital Editions and Colibrio Reader, there is continuous playback with the same epub.The epub meets all EPUB3.3 requirements as validated with EPUBCheck, so it would appear that Thorium is not handling audio correctly if these optional attributes are not included - would that be a valid assumption or could there be another cause?
The text was updated successfully, but these errors were encountered: