Created attachment 132288 [details]
Checkerboard, 0.75s (PPTX)
The attached PPT/PPTX files have Checkerboard slide transition with 0.75s duration.
When they are opened in LibreOffice, they are shown with 2s duration.
I'm not sure what the number depends on, a PPTX with a 1.75s-duration transition opens with 3s duration in LO, just like a 10.75s one.
The behavior might be originating from the old, predefined Slow/Medium/Fast values (in 5.1).
Observed with v220.127.116.11 / Windows 7.
Created attachment 132289 [details]
Checkerboard, 0.75s (PPT)
For checkerboard slide transition the basic transition speeds are: fast/med/slow = 0.5s/0.75s/1s.
It seems to be different for different transitions.
If the speed fits a predefined option, it's saved like this:
If the speed is different, it's saved like this:
<mc:Choice xmlns:p14="http://schemas.microsoft.com/office/powerpoint/2010/main" Requires="p14">
<p:transition spd="slow" p14:dur="1050">
It's fairly easy to get a list of predefined values for each of the transitions, just have to have a transition with each of the predefined durations, and switching between transitions will show the exact value in the Duration field.
- Version: 18.104.22.168.alpha0+
Build ID: 6152bf9ee9b2e348dee854921a5a5db1cfc72995
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
- Version: 22.214.171.124.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
- Version 126.96.36.199.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
- LibreOffice 3.3.0
I was wrong about this, slow/med/fast always seems to be 1/0.75/0.5 s, it's just the defaults on the UI that are different, eg. Fade is 0.7 s, while Reveal is 3.4 s.
So with an irregular default timing, the exact timing is saved together with the closest predefined timing.
Szymon is working on a very similar bug report (bug 115394), if that covers PPT as well, this can be closed as duplicate.
Szymon's taken care of the PPT part as well, let's close this as duplicate.
*** This bug has been marked as a duplicate of bug 115394 ***