• 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

    atem mini OSC : problems with continuous control and envelops with transition bar

    How To... ?
    blackmagic atem mini remote control
    2
    7
    1696
    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.
    • Bennnid
      Bennnid last edited by

      hi, 

      i have a strange behavior when switching the mixer with OSC with /atem/transition/bar,
      when I'm using a scaled midi controller and with envelops too...
      its as if it would reverse sometimes... though when moving slowly no problem (almost),
      scale seems to be 0.0   1.0 , I 'm afraid there's a big basic I'm missing with video mixer...

      I just need to crossfade 2 cams, no big deal...
      thanks a lot ! 

      MBP 2019- 16' (16,1) i9 2,3 GHz, 32 Gb /Radeon pro 5550M 8GBram/ OSX 10.15.3
      Equip.: kinect 360 1414/ Leapmotion / Myo Armband /Wiimotes/ Saitek Joysticks ( X, evo, throttle) /Ipad / enttec dmx usb pro

      jfg 3 Replies Last reply Reply Quote 0
      • jfg
        jfg @Bennnid last edited by

        @bennnid

        I think it has to do with the way ATEM Mini manages time. There is a conflict between the duration of the fade in/out in the Enveloppe actor and the setting of the time in the ATEM mini. I think the best way is to use the auto command (/atem/transition/auto) to start the transition. The duration must then be set on the ATEM. Unfortunately there is no OSC address for the duration of the transition.

        best

        Jean-François

        • Izzy 3.2.6
        - MacBook Pro M1 Max 16" 64GB RAM, Mac OS 15.3.2 Sequoia
        - Mac Pro 5.1 middle 2012 (3,33 GHz 6-Core Intel Xeon, 32GB RAM, Radeon RX 580 8 GB ),
        Mac OS 10.14.6 (Mojave)
        - Mac mini Pro M4, Mac OS 15.3.2 Sequoia

        • A range of deployable older Macs
          Located in Bremen, Germany
        1 Reply Last reply Reply Quote 1
        • jfg
          jfg @Bennnid last edited by

          @bennnid

          from the ATEMosc website:

          Auto and cut commands don’t seem to work, or look buggy, when combining atemOSC with MIDI control

          Problem

          A lot of MIDI controls send two signals when a button is pressed, one signal when you press down, and another when you release. If you connect the button the /atem/transition/auto or cut, atemOSC recieves both events and attempts to send the transition command to the switcher twice. This can cause buggy behavior or just not work at all.

          Solution

          Tune your MIDI software to send only one of the two signals, either ok button press (rising edge) or button release (falling edge). See #120 for instructions for OSCulator.

          • Izzy 3.2.6
          - MacBook Pro M1 Max 16" 64GB RAM, Mac OS 15.3.2 Sequoia
          - Mac Pro 5.1 middle 2012 (3,33 GHz 6-Core Intel Xeon, 32GB RAM, Radeon RX 580 8 GB ),
          Mac OS 10.14.6 (Mojave)
          - Mac mini Pro M4, Mac OS 15.3.2 Sequoia

          • A range of deployable older Macs
            Located in Bremen, Germany
          1 Reply Last reply Reply Quote 0
          • jfg
            jfg @Bennnid last edited by

            @bennnid

            I got a better result with this configuration (OSC multi transmit)

            • Izzy 3.2.6
            - MacBook Pro M1 Max 16" 64GB RAM, Mac OS 15.3.2 Sequoia
            - Mac Pro 5.1 middle 2012 (3,33 GHz 6-Core Intel Xeon, 32GB RAM, Radeon RX 580 8 GB ),
            Mac OS 10.14.6 (Mojave)
            - Mac mini Pro M4, Mac OS 15.3.2 Sequoia

            • A range of deployable older Macs
              Located in Bremen, Germany
            Bennnid 1 Reply Last reply Reply Quote 0
            • Bennnid
              Bennnid @jfg last edited by

              @jfg THAAAANKS !

              indeed it's too bad not to be able to give full osc control...
              the problem being that we can't use 1 button for transition A>B and another one to B>A so that, as you never know where the lever is it can lead to misbehavior...

              have you tried to get osc values and try making this lever more coherence gating your osc message when already in the commanded position? 

              thanks ' ps: I tried also osc transmit but doesn't seem completely stable like this...
              too bad those osc control on ATEM  have square weels!

              MBP 2019- 16' (16,1) i9 2,3 GHz, 32 Gb /Radeon pro 5550M 8GBram/ OSX 10.15.3
              Equip.: kinect 360 1414/ Leapmotion / Myo Armband /Wiimotes/ Saitek Joysticks ( X, evo, throttle) /Ipad / enttec dmx usb pro

              jfg 2 Replies Last reply Reply Quote 0
              • jfg
                jfg @Bennnid last edited by

                @bennnid said:

                have you tried to get osc values and try making this lever more coherence gating your osc message when already in the commanded position? 

                 I haven't but you can try with atem/preview and atem/programm. They give you the code of the corresponding entry (e.g. Colors bars=1000 or Camera 1= 1) for program and preview.

                best

                Jean-François

                • Izzy 3.2.6
                - MacBook Pro M1 Max 16" 64GB RAM, Mac OS 15.3.2 Sequoia
                - Mac Pro 5.1 middle 2012 (3,33 GHz 6-Core Intel Xeon, 32GB RAM, Radeon RX 580 8 GB ),
                Mac OS 10.14.6 (Mojave)
                - Mac mini Pro M4, Mac OS 15.3.2 Sequoia

                • A range of deployable older Macs
                  Located in Bremen, Germany
                1 Reply Last reply Reply Quote 0
                • jfg
                  jfg @Bennnid last edited by

                  @bennnid said:

                  the problem being that we can't use 1 button for transition A>B and another one to B>A so that, as you never know where the lever is it can lead to misbehavior...

                   a video mixer doesn't work in this way. It has a program and a preview level. Program is always online and you choose on the preview level what you want to have as next, then you choose with which effect (cut, fade, wipe,…) you will send it to the program. You cannot change the program directly so you cannot have a to B or B to A. It is always preview to program.

                  What I send you before is working but not always because some time (and it is a question of time between value and trigger)the last sent value is not 0 or 1 but 0,002 or 0,998.

                  so you have to add a trigger delay, then you can also use two segments in the Enveloppe generator:

                  To see the state of the lever you can use the OSC input /atem/transition/bar . it will show you the current value of the bar:

                  best

                  Jean-François

                  • Izzy 3.2.6
                  - MacBook Pro M1 Max 16" 64GB RAM, Mac OS 15.3.2 Sequoia
                  - Mac Pro 5.1 middle 2012 (3,33 GHz 6-Core Intel Xeon, 32GB RAM, Radeon RX 580 8 GB ),
                  Mac OS 10.14.6 (Mojave)
                  - Mac mini Pro M4, Mac OS 15.3.2 Sequoia

                  • A range of deployable older Macs
                    Located in Bremen, Germany
                  1 Reply Last reply Reply Quote 1
                  • First post
                    Last post