• Products
    • Isadora
    • Get It
    • ADD-ONS
    • IzzyCast
    • Get It
  • Forum
  • Help
  • Werkstatt
  • Newsletter
  • Impressum
  • Dsgvo
  • Press
  • Isadora
  • Get It
  • ADD-ONS
  • IzzyCast
  • Get It
  • Press
  • Dsgvo
  • Impressum

Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags

    [SOLVED] Movie Player Output Position

    Troubleshooting and Bug Reports
    5
    12
    3122
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Michel
      Michel Izzy Guru last edited by

      @rodgy_fr

      Yes that is true, the output actually never matches the position input but if you play the movie to the end and set the loop enable to off you will see that the movie position output will reach 100%. I did file a bug report once (quite long ago). Maybe it helps if you do that as well.

      Best Michel

      Michel Weber | www.filmprojekt.ch | rMBP (2019) i9, 16gig, AMD 5500M 8 GB, OS X 10.15 | located in Winterthur Switzerland.

      1 Reply Last reply Reply Quote 0
      • rodgy_fr
        rodgy_fr last edited by

        @Michel

        Thanks for your answer. I have the same issue with the loop enable to off.

        MacBook Pro 15'' 2016 core i7 2,9Ghz - 16 Go Ram - Radeon Pro 460 4096 Mo
        Hackintosh core i& 4Ghz - 32 Go Ram - Radeon Vega 64
        MacBook Air 11'' 2014 - MacBook Pro retina 13'' 2014 - and old computers !

        1 Reply Last reply Reply Quote 0
        • Skulpture
          Skulpture Izzy Guru last edited by

          If my memory is correct isn't this something to do with the codec?

          I'm sure you've seen but you can use the loop end trigger if you need it. 

          Graham Thorne | www.grahamthorne.co.uk
          RIG 1: Custom-built PC: Windows 11. Ryzen 7 7700X, RTX3080, 32G DDR5 RAM. 2 x m.2.
          RIG 2: Laptop Dell G15: Windows 11, Intel i9 12th Gen. RTX3070ti, 16G RAM (DDR5), 2 x NVME M.2 SSD.
          RIG 3: Apple Laptop: rMBP i7, 8gig RAM 256 SSD, HD, OS X 10.12.12

          1 Reply Last reply Reply Quote 0
          • jhoepffner
            jhoepffner last edited by

            Hello,

            It depend of your "optimize" setting. 
            – with "interactive", position output reach 100 and send 1 trigger on "loop end" output
            – with "performance", it never reach 100 and send multiple trigger on "loop end" output
            I will fill a bug report for the trigger.
            Jacques

            Jacques Hoepffner http://hoepffner.info
            GigaByte 550b / Ryzen 7 3800X / Ram 64 Go / RTX 3090 24 Go / SSD 2 To / raid0 32 To
            MBP 13' i5 2.6 Ghz 16 Go / Intel Iris / macOs 10.11.6 / izzy 2.6.1 + 3.0.3b2
            MBP 15' i7 2.6 Ghz 16 Go / GTX 650M 1Go/ MacOs10.13.3 / Izzy 2.6.1
            MSI GS65 i7 3.6 Ghz 32 Go / GTX 1070 8 Go / Windows 10 / Izzy 3.0.3b2

            1 Reply Last reply Reply Quote 0
            • rodgy_fr
              rodgy_fr last edited by

              Thanks @jhoepffner for your explanation. I understand why I had problem

              MacBook Pro 15'' 2016 core i7 2,9Ghz - 16 Go Ram - Radeon Pro 460 4096 Mo
              Hackintosh core i& 4Ghz - 32 Go Ram - Radeon Vega 64
              MacBook Air 11'' 2014 - MacBook Pro retina 13'' 2014 - and old computers !

              1 Reply Last reply Reply Quote 0
              • mark
                mark last edited by

                Dear @rodgy_fr

                Regarding your report about the Movie Player's position output never reaching 100%, this is to be expected. Let's consider a 5 frame movie as an example. These are the values that would be reported at the position output as the movie plays. Here's what the position output would say for each frame:
                Frame 1 = 0.00% (0 / 5)
                Frame 2 = 0.20% (1 / 5)
                Frame 3 = 0.40% (2 / 5)
                Frame 4 = 0.00% (3 / 5)
                Frame 5 = 0.80% (4 / 5)
                ** LOOP TO START **
                Frame 1 = 0.00% (0 / 5)
                Frame 2 = 0.20% (1 / 5)
                As you can see, the position output reports the position of the starting point of each frame based on the number of frames within the movie. The _starting_ time of the last frame will always be at some percentage before 100%... 100% is never reported  because 100% is would be the starting time of the last frame plus the frame's duration... but before this is reported, the movie has looped back to the beginning.
                Only if you set the 'loop enable' to off will you see the position output reach 100%.. because the movie plays it's entire duration and then stops.
                I hope that explains what's happening.
                Best Wishes,
                Mark

                Media Artist & Creator of Isadora
                Macintosh SE-30, 32 Mb RAM, MacOS 7.6, Dual Floppy Drives

                1 Reply Last reply Reply Quote 0
                • Michel
                  Michel Izzy Guru last edited by

                  @mark

                  one thing that is disturbing is, that most of the time the postion output does not matches the position input.

                  Best Michel
                  6a2646-postion-inputoutput.png

                  Michel Weber | www.filmprojekt.ch | rMBP (2019) i9, 16gig, AMD 5500M 8 GB, OS X 10.15 | located in Winterthur Switzerland.

                  1 Reply Last reply Reply Quote 0
                  • rodgy_fr
                    rodgy_fr last edited by

                    Hi @mark thanks for your answer. But I have the same issue that explain by @jhoepffner.

                    MacBook Pro 15'' 2016 core i7 2,9Ghz - 16 Go Ram - Radeon Pro 460 4096 Mo
                    Hackintosh core i& 4Ghz - 32 Go Ram - Radeon Vega 64
                    MacBook Air 11'' 2014 - MacBook Pro retina 13'' 2014 - and old computers !

                    1 Reply Last reply Reply Quote 0
                    • mark
                      mark last edited by

                      @Michel,

                      Well, Michel, It's a matter of rounding by the AVFoundation/Quicktime/DirectShow subsystems. When you enter a value in the position input of 50%, I can assure you this is exactly where I tell those systems to go. The thing is, they make their own decisions about where the "playhead" can actually go. 
                      I just checked this and it looks like AVFoundation will only go to the nearest frame. Quicktime will go a value much closer to the specified value, but even it will not match exactly... this is may be dependent on the sample rate of the audio.... I'm not sure what the limitation is there.
                      @rodgy_fr
                      I assume when you say "But I have the same issue that explain by @jhoepffner." you mean about the end trigger bug, yes? Please confirm this. (I have fixed this bug for the next release.)
                      In the meantime, if you need a trigger when the movie gets to the end, use a Compartor actor. Set the 'compare' input to 'ge', and the 'value 2' input to 99.9\. Then you'll connect the 'position' output into 'value 1' and you'll get a trigger when the movie gets to the end.
                      Best Wishes,
                      Mark

                      Media Artist & Creator of Isadora
                      Macintosh SE-30, 32 Mb RAM, MacOS 7.6, Dual Floppy Drives

                      1 Reply Last reply Reply Quote 0
                      • Michel
                        Michel Izzy Guru last edited by

                        @mark

                        Ok I understand. Thank you.

                        Best Michel

                        Michel Weber | www.filmprojekt.ch | rMBP (2019) i9, 16gig, AMD 5500M 8 GB, OS X 10.15 | located in Winterthur Switzerland.

                        1 Reply Last reply Reply Quote 0
                        • rodgy_fr
                          rodgy_fr last edited by

                          @mark

                          Yes it is about the trigger bug. Thank you for your advice

                          MacBook Pro 15'' 2016 core i7 2,9Ghz - 16 Go Ram - Radeon Pro 460 4096 Mo
                          Hackintosh core i& 4Ghz - 32 Go Ram - Radeon Vega 64
                          MacBook Air 11'' 2014 - MacBook Pro retina 13'' 2014 - and old computers !

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post