• Isadora
  • Get it
  • Forum
  • Help
  • ADD-ONS
  • Newsletter
  • Impressum
  • Dsgvo
  • Impressum
Forum
    • Categories
    • Recent
    • Popular
    • Tags
    • Register
    • Login

    From 2 values, delay one of them...

    How To... ?
    3
    12
    2.5k
    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.
    • camilozkC
      camilozk
      last edited by

      Thanks Reinhard!

      i5 M520 @ 2.40GHz / 4Gb Ram / Win 7 - izzy 2.2.2
      i7 7700HQ @ 2.8GHz / 16Gb Ram / Win 10 - izzy 2.6.1 // GeForce GTX 1060

      1 Reply Last reply Reply Quote 0
      • camilozkC
        camilozk
        last edited by

        lets see. I have a new complication: I attach an izzy file for the example.

        In the example, when "limit scale value" receives a value under 99, the bypass in "auto-fade" is on. When "limit scale value" receives a value over 100, after 2 seconds the bypass in "auto-fade" goes off.
        so far so good.
        now, there are some tricky situations in which the values change in the middle of a change of state in the bypass, which reverts this behaviour. And this, in my patch, happens very often. How could I prevent this???

        4f598b-untitled.izz

        i5 M520 @ 2.40GHz / 4Gb Ram / Win 7 - izzy 2.2.2
        i7 7700HQ @ 2.8GHz / 16Gb Ram / Win 10 - izzy 2.6.1 // GeForce GTX 1060

        1 Reply Last reply Reply Quote 0
        • R
          Reinhard
          last edited by

          Dear,

          sorry, I don't get it. You want a value between 99 and 100 to switch something. If you set an inside-range-actor to min 99 and max 100 it will tell you exactly that. Your downscaling with a limit-scale-value-actor and feeding this into an inside-range-actor set to min 0 and max 0 does not make any sense. Try this - if the value is other than 99-100 you get a 0, if it's in you get a 1.
          best r

          c0741e-camilozk.izz

          mbp 16", 2021, m1pro, 16gb, 12.6 / 6core trashcan, 11.2 / youngest Izzy

          1 Reply Last reply Reply Quote 0
          • camilozkC
            camilozk
            last edited by

            I understand reinhard, but this is not my problem anymore. I took away limit-scale-value-actor to try to explain my new problem in the new example attached.

            case 1
            -If I send an "enter" (from now on called "on"), the macro turns on
            -If I send an "exit" (from now on called "off"), after 2 seconds the macro turns off
            case 2
            -I send an "on", the macro turns on
            -I send an "off", after 2 seconds the macro will turn off
            -before this 2 seconds pass, I send an "on"
            In case 2, I would expect to have the macro "on", since the last signal I sent was "on", but because there was an "off" already on the way, that arrives after the 2nd "on", the final macro state is "off".
            how can I prevent this?

            59381b-untitled.izz

            i5 M520 @ 2.40GHz / 4Gb Ram / Win 7 - izzy 2.2.2
            i7 7700HQ @ 2.8GHz / 16Gb Ram / Win 10 - izzy 2.6.1 // GeForce GTX 1060

            1 Reply Last reply Reply Quote 0
            • R
              Reinhard
              last edited by

              Hi,

              use a gate!
              best r

              1ae766-camilozk.izz

              mbp 16", 2021, m1pro, 16gb, 12.6 / 6core trashcan, 11.2 / youngest Izzy

              1 Reply Last reply Reply Quote 0
              • camilozkC
                camilozk
                last edited by

                yes!

                I knew gate was the way, but the implementation was my problem.
                thank you very much!

                i5 M520 @ 2.40GHz / 4Gb Ram / Win 7 - izzy 2.2.2
                i7 7700HQ @ 2.8GHz / 16Gb Ram / Win 10 - izzy 2.6.1 // GeForce GTX 1060

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

                  @camilozk

                  Attached a solution with a gate actor, as soon an on trigger gets sent the gate closes until a off trigger gets sent again.

                  Best Michel
                  f2dfc3-untitled.izz

                  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
                  • R
                    Reinhard
                    last edited by

                    same but more clever - that makes the difference between user and guru...

                    mbp 16", 2021, m1pro, 16gb, 12.6 / 6core trashcan, 11.2 / youngest Izzy

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

                      @Reinhard

                      Thank you for the compliment.

                      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
                      • camilozkC
                        camilozk
                        last edited by

                        thanks!

                        i5 M520 @ 2.40GHz / 4Gb Ram / Win 7 - izzy 2.2.2
                        i7 7700HQ @ 2.8GHz / 16Gb Ram / Win 10 - izzy 2.6.1 // GeForce GTX 1060

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