• Isadora
  • Get it
  • Forum
  • Help
  • ADD-ONS
  • Newsletter
  • Impressum
  • Dsgvo
  • Impressum
Forum

Navigation

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

    [LOGGED] Timecode + Markers

    Feature Requests
    8
    13
    3167
    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.
    • DusX
      DusX Tech Staff last edited by

      I think to be considered we will need to see if there is a standard for these things.

      Definitely could be useful.

      Troikatronix Technical Support

      • New Support Ticket Link: https://support.troikatronix.com/support/tickets/new
      • Isadora Add-ons: https://troikatronix.com/add-ons/
      • My Add-ons: https://troikatronix.com/add-ons/?u=dusx

      Running: Win 10 64bit, i7-8750H, M.2 PCIe SSD's, 16gb DDR4-2666, nVidia GTX 1070 | located in Ontario Canada.

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

        A quick word with my friends at Adobe suggests that markers are embedded in the XMP info in the file header, and are a 'standard'. I'll have a play with opening that example file in FCP and Resolve and see if those programs read the markers. Meanwhile here's a page about the XMP: http://www.adobe.com/devnet/xmp.html

        Intel NUC8i7HVK Hades Canyon VR Gaming NUC, i7-8809G w/ Radeon RX Vega M GH 4GB Graphics, 32GB RAM, 2 x NVMe SSD
        Gigabyte Aero 15 OLED XD. Intel Core i7-11800H, NVidia RTX3070, 32GB RAM 2 x NVMe SSD
        Homebrewed X99 Desktop, i7 5930, GeForce GTX980, 64GB RAM, Win10x64
        www.natalieinsideout.com

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

          Using EXIFtool:

          XMP info easily extracted and the markers are clearly read and show as follows:

          Tracks Track Name               : Markers

          Tracks Frame Rate               : f25

          Tracks Markers Start Time       : 45, 75, 100

          Tracks Markers Name             : blue, yellow, light

          Tracks Markers Type             : Comment, Comment, Comment

          Tracks Markers Cue Point Params Key: marker_guid, marker_guid, marker_guid

          Tracks Markers Cue Point Params Value: 42f744a8-1685-6a80-6548-729f00000024, 564c4da8-962e-ce3c-0701-cd0100000024, cd90ac2d-d593-35dd-049c-671400000024

          Tracks Markers Guid             : cd90ac2d-d593-35dd-049c-671400000024

          So the position of the markers is shown as the frame number, and the position (in hh.mm.ss.ff)  is calculated from the frame rate. (The markers are at 00:00:01:20, 00:00:03:00 and 00:00:04:00)

          Full XMP info from the file is here

          So you can see all the info contained in the file header.

          And here's what the XMP looks like if I export it from Premiere as FCP compatible XML. Again, the markers are clearly defined as part of the XML.

          Would Isadora have to be reading the XMP info anyhow, just in order to know the other video parameters like frame rate, frame size, duration, etc? In which case would this be straighforwards? Since Isadora would just looking for a couple more lines of XMP data.

          Anyhow, I've planted this seed, given it a bit of water and compost, and hope it falls on fertile ground :-)

          Intel NUC8i7HVK Hades Canyon VR Gaming NUC, i7-8809G w/ Radeon RX Vega M GH 4GB Graphics, 32GB RAM, 2 x NVMe SSD
          Gigabyte Aero 15 OLED XD. Intel Core i7-11800H, NVidia RTX3070, 32GB RAM 2 x NVMe SSD
          Homebrewed X99 Desktop, i7 5930, GeForce GTX980, 64GB RAM, Win10x64
          www.natalieinsideout.com

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

            I would love this.

            Recently I've been having to do video in QLab for a few people who've insisted on it. Generally I'm not a fan of it's video side but one neat feature is how it interprets 'markers' embedded in footage. A good example is being able to start a video, loop a section, then play the end. Obviously this is possible in Issy but it's nice to be able to just add the 'markers' in premier if you're lazy like me!

            2014 MBP Mojave 10.14.6 OS with 16GB, 2.5Ghz i7 quad core, Intel Iris Pro 1536 & Geforce GT 750m 2GB - Izzy 3.0.8
            Gigabyte Brix Windows 10 with 32GB, i7-6700 quad core, 4GB GeForce GTX 950 - Izzy 3.0.8
            Based in Manchester, UK.

            mark_m 1 Reply Last reply Reply Quote 1
            • mark_m
              mark_m @Kathmandale last edited by

              I just wanted to bump this up, and to say that I hope that Timecode for Video in the Movie Player - as announced at the 2016 Werkstatt Keynote speech - is still on the road map.
              Just been making a piece where I had to make a lot of use of percentage to time calculations, and Timecode would have been a huge time saver.
              Just asking. As well as the markers ;-)

              Intel NUC8i7HVK Hades Canyon VR Gaming NUC, i7-8809G w/ Radeon RX Vega M GH 4GB Graphics, 32GB RAM, 2 x NVMe SSD
              Gigabyte Aero 15 OLED XD. Intel Core i7-11800H, NVidia RTX3070, 32GB RAM 2 x NVMe SSD
              Homebrewed X99 Desktop, i7 5930, GeForce GTX980, 64GB RAM, Win10x64
              www.natalieinsideout.com

              Fred 1 Reply Last reply Reply Quote 2
              • Fred
                Fred @mark_m last edited by

                @mark_m +1 for me also for timecode and markers

                http://www.fredrodrigues.net/
                https://github.com/fred-dev
                OSX 10.15.15 MBP 2019 16" 2.3 GHz 8-Core i9, Radeon Pro 5500M 8 GB, 32g RAM
                Windows 10 7700K, GTX 1080ti, 32g RAM, 2tb raided SSD
                Windows 10 Threadripper 3960x 64g ram, 1tb NVME, rtx 2080ti + rtx2070 super

                mark_m 1 Reply Last reply Reply Quote 1
                • mark_m
                  mark_m @Fred last edited by

                  Just bumping this feature request up for attention, seeing as how it's been recently requested by someone else :-)

                  Intel NUC8i7HVK Hades Canyon VR Gaming NUC, i7-8809G w/ Radeon RX Vega M GH 4GB Graphics, 32GB RAM, 2 x NVMe SSD
                  Gigabyte Aero 15 OLED XD. Intel Core i7-11800H, NVidia RTX3070, 32GB RAM 2 x NVMe SSD
                  Homebrewed X99 Desktop, i7 5930, GeForce GTX980, 64GB RAM, Win10x64
                  www.natalieinsideout.com

                  mark_m 1 Reply Last reply Reply Quote 1
                  • barneybroomer
                    barneybroomer Beta Gold last edited by

                    Once upon a time.....when QuickTime was still the bomb, you could embed text, midi, multichannel audio and timecode to a single QuickTime movie. From QuickTime 5 this was ditched and up until now there has never been a file format that was that close to all-in-one format that could be made with a broad range of editors. You could edit audio and video and midi in Protools or another DAW, and export the whole thing to one QT file. In the QT player you could add different audio outputs and midi out to a external midi I/O or patch internal. Did many show like that always rock solid. I discussed the last 15 years with Mark several time this approach, but due to constant change in Quicktime it was not possible this way anymore.

                    Zap, many years later I had to do a large showontrol setup for a show in Rotterdam, but was not able to use timecode, since all tracks that were played there were coming from a DJ setup and give him the freedom to mix it like they always do, so also change in pitch. So in that time we used DVJ's and I added in the bottom of the video several stripes with optical markers for pyro, laser, lights and commands for boats. So the markers were setup up as a binary coded stripe and you could add numbers for playlists and everything. The video was played out by the DVJ's, and we got rid of the info stripe at the bottom before we ended out to all projectors. The software in that time (I'm talking about 13 years ago) was also Isadora and I used it to decode the optical markers. I did not use colors but used "placement" tabs,  black for zero's and white for ones and sended out the corresponding midi triggers to all equipment. Was a hell of a job back then and can't remember what actors I used to measure the optical triggers, there was a reason why I used black and white instead of colours. Any how, the whole setup of the show including the setup of all triggers was done in Final Cut Pro. 

                    So when you use timecode, this works great with a non-pitched video, but when using a bunch of starts and stops, variable pitch, optical markers are a great tool. in Isadora you could make a tool that generates a optical marker with a certain midi pitch in to make the setup proces quicker instead of hanging 6 A4 on your wall to doublecheck if that one optical marker is the right one hahaha

                    Mac Mini M1 2020 / OSX 11.7
                    MacBook Pro 2,3 Ghz Intel 8 core I9 / OSX 10.15.7
                    MacBook Pro 2,2 Ghz Intel 8 core I7 / OSX 10.15.7

                    and a Motorola DynaTAC 8000X ;)

                    1 Reply Last reply Reply Quote 1
                    • mark_m
                      mark_m @mark_m last edited by

                      @mark_m

                      Just bumping up this request for old times' sake! Gets quite a few +1s, shouldn't be hard to program (all the data's in the XMP). Easier than IzzyCast, I'll bet :-)

                      Intel NUC8i7HVK Hades Canyon VR Gaming NUC, i7-8809G w/ Radeon RX Vega M GH 4GB Graphics, 32GB RAM, 2 x NVMe SSD
                      Gigabyte Aero 15 OLED XD. Intel Core i7-11800H, NVidia RTX3070, 32GB RAM 2 x NVMe SSD
                      Homebrewed X99 Desktop, i7 5930, GeForce GTX980, 64GB RAM, Win10x64
                      www.natalieinsideout.com

                      Notdoc 1 Reply Last reply Reply Quote 4
                      • Notdoc
                        Notdoc @mark_m last edited by

                        @mark_m

                        strongly agree...

                        Catalina on Macbook Pro 15in 2018, 2.8 GHz 6-core Intel Core i7, with 16GB 2400MHz DDR4, Graphics: Radeon Pro 560X 4 GB Intel UHD Graphics 630 1536 MB

                        transitioning to:

                        Ventura on Macbook Pro 14-in M1 Max 2022

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