• 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

    [FEATURE REQUESTS LOGGED] mapper functions improvements in V3

    Feature Requests
    izzymap mapping isadora 3
    2
    4
    1337
    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.
    • Fred
      Fred last edited by Woland

      I had a chance to do a little more work in V3 and noticed a few things that are still missing.

      Inside the composite mapper I cannot type pixel values for positioning slices in the output, only the input - needless to say with only one side able to do precise positioning it is not so hopeful.

      Also inside the composite mapper there is no magnet for rotation, nor any way to type in rotation, once you rotate a quad there is no way to actually position it precisely.

      Again, there is no way to give any precise control over scale, I cannot nudge the scale control with arrow keys to do small scale increments, nor can I enter any values for pixel positions so everything is very loose.

      The addition of the numeric control for the input slices is great, but without the corresponding output control and numeric control over rotation this feature is half implemented.


      Izzy 3.0.7b4 on Os Catalina - 16" macbook pro w/AMD Radeon Pro 5500M 8 GB GPU.

      http://www.fredrodrigues.net/
      https://github.com/fred-dev
      OSX 13.6.4 (22G513) 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

      1 Reply Last reply Reply Quote 1
      • Woland
        Woland Tech Staff last edited by

        @fred said:

        Inside the composite mapper I cannot type pixel values for positioning slices in the output, only the input...
        ... inside the composite mapper there is no magnet for rotation, nor any way to type in rotation, once you rotate a quad there is no way to actually position it precisely.
        ... there is no way to give any precise control over scale, I cannot nudge the scale control with arrow keys to do small scale increments, nor can I enter any values for pixel positions

        All now logged as feature requests ;)

        Best wishes,

        Woland

         

        TroikaTronix Technical Support
        New Support Ticket: https://support.troikatronix.com/support/tickets/new
        Support Policy: https://support.troikatronix.com/support/solutions/articles/13000064762
        Add-Ons: https://troikatronix.com/add-ons/ & https://troikatronix.com/add-ons/?u=woland
        Professional Services: https://support.troikatronix.com/support/solutions/articles/13000109444

        | Isadora Version: all of them | Mac Pro (Late 2013), macOS 10.14.6, 3.5GHz 6-core, 1TB SSD, 64GB RAM, Dual AMD FirePro D700s |

        Fred 1 Reply Last reply Reply Quote 0
        • Fred
          Fred @Woland last edited by

          @woland thanks, as a reference the numeric control from resolume gives good control over positions in and out, and values can also be copy pasted which is great. The mapper can be really useful for compositing, a specific example could be for sending images to a ledwall processor or artnet processor where there are precise positions for tiles and fixtures. these numeric inputs are the only way to conform to this, where say a full hd image will be split across a variety of led tile surfaces and or artnet fixtures in other software and hardware systems. As it is now in these fast setup windows if I use Isadora I need to make a template in Photoshop and eyeball the mapper output and hope it is close enough so I don't spill images over the wrong pixels and hence wrong surface. Actual full numeric control would allow this to be a fast and accurate process.

          http://www.fredrodrigues.net/
          https://github.com/fred-dev
          OSX 13.6.4 (22G513) 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

          Woland 1 Reply Last reply Reply Quote 1
          • Woland
            Woland Tech Staff @Fred last edited by

            @fred

            All excellent points. I can see how this would be a very valuable addition to IzzyMap. Thank you for taking the time to give us feedback :)

            TroikaTronix Technical Support
            New Support Ticket: https://support.troikatronix.com/support/tickets/new
            Support Policy: https://support.troikatronix.com/support/solutions/articles/13000064762
            Add-Ons: https://troikatronix.com/add-ons/ & https://troikatronix.com/add-ons/?u=woland
            Professional Services: https://support.troikatronix.com/support/solutions/articles/13000109444

            | Isadora Version: all of them | Mac Pro (Late 2013), macOS 10.14.6, 3.5GHz 6-core, 1TB SSD, 64GB RAM, Dual AMD FirePro D700s |

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