Gain Reduction Meter



  • Right click on the module browser and it shows a list of each module‘s parameter.



  • @christoph-hart Adding the module browser to a workspace causes an instant close for me - has done for ages.



  • @d-healey said in Gain Reduction Meter:

    @christoph-hart Adding the module browser to a workspace causes an instant close for me - has done for ages.

    It's working smoothly here.... (Current version)

    0_1526450426330_W.jpg



  • @remarkablex Aha perhaps it's only on Linux then...



  • @christoph-hart What's the math behind startTimer(30) ?



  • 30 milliseconds.



  • @Christoph-Hart said in Gain Reduction Meter:

    The getCurrentLevel() functions return the output level. For the gain reduction, use the dedicated parameters:

    Dynamics.getAttribute(Dynamics.CompressorReduction);
    
    HiseSnippet 1237.3oc2XssaaaCFlxNZX1cIXcnCX2MgfcgKVWfc5oALLjC1wEYKNIHJMa8pBZIZa1HQpQQ4Uug9fr8lr6xCPuXOJ4MX6mTRVzwZY1cco.UHAvj+m93O+zGo8wBtGINlKPV0NcRDAY8Q1tSXxQsGgoLz9cPVqY2CGKIBmzo1cRDNNl3irrp9D0DV0VAoetbqcwAXlGoXJD5LN0ib.MjJKlMZ6umFDzE6SNkFZ38C1deONqMOfm.3opcSTD16b7PxgXkaUrQV164SkbgqDKIwHqU1k6OwcD+mYo9eFMl1OfnFzB4BIJc5t7.eEhUeF0dDMv+370cLBR5wEcgpocg6X2i5SmNeQ23i0FbJhvreXU45fWq2P3YY.uURg2ssc8DzHYgEE1tk89LXiZ.F1BLgUpunJedE61bvClbiP74jtBXvzHZ7nlMumyCa17teyp0WsNrQDKcFiENclvvgTuXmu0QyL1XHQt2fADOYi0yss9UC5DhehmjxYPT40DhqMOLhyfAMVepGYwNa7RHt8XCoLxFdBBzMULEwQ8egprp.jaDSj5IaiCB5C7jFCRX5D13t0+050TYYLjkbHpJ+NRof1OQRZLcVEhD5V3T.oReM3uwEX.hsCwi1mDD2kKTz9tXOXitw3bmmFsBWmgCRHJa0eE7uFrRrHEtMtutCmCVGN6PtjbTFpq+p4rLXPYlTMUAOH.RXIVSqz+bXMXIg8Ih6A8Z.o49AzqY4uevhwe8R2fMbjy1mQkGEQxFWvvaUBCGkwPTb8L.BtJ0L80xX5tATeh.Q8Uz7oMajF+l5MnmteGrDmmJHqPkhHBIUsfr5PFC5QouDUytCI9bIOR6aFwDR+BU3WBxFV8g5MQ8gMgODR88CHGyioZGlhoMu.TOibo+hFm+9uod9isBMUNe1Eg3WZtJhSFLfpJgsi+tnPteFb0TPDgggcA8q1n40F.EJteR.VNqrkhzlYPAOS8AkF.Cf8DSs7kPKqYoZYktSufv811GSkdiJGuUJAuv98+23M6jgUsSE+J.6J1c+wa3iA9jTrT2NWGSCDigydJsjrWNkongol9zQf12HntW0.nTBRpl7A0rmPBH3Xi22d11E5myUhK2pv3UKzEu9fu6BCsW0l7TSu9KMR6UQxWrsoj8b3QeUChnj0alkRWxY1leUmYXtBYhhdvYoIQkjt4MXUcVlQ0EiYTBw7DdhjxF1CCmnoDJNLIzEt1jGA3kLFbNkRVphRaMcbS0XEDbILe8f+BdxL1RM1JyXqbilj+0RIb2x1ENNTeM.Mi6S0ic9A7XhySHLhP8Z70bEw+7s+UDOxSBU+TAlEGwimIwtjP5ofpdr4jOMFt3C4mLYb5m1brnTSWtUWXMVZLtXYhPqOsSHOgIuts5ETDXVYZC+KQQXk2A2a8suV++8ilptXv8eQSsVNFcogQAfh4XR.bygryi5PFfSBjSm0Dj83LdzHNi5YR.Ng.uZNbHQXB8RWOWU14NaWhdyA.IDK5kdUf2jVQqEuUbcaWelcJbcTuX579wMJp9dzMJVBnbSbFxMQMBwdB9y8R+lCJt7GpmAV2L8ObPM6dpwNsx+5BpdCbcc5y87TM6uB5NkGwlKcD2eoi3AKcDOboi3QKcDOdoi3qulHTm8rShjGl9pGB82N1j7RC
    

    @Christoph-Hart I'm using this script for GR meters, and they intermittently stop working. The only way to recover is remove the plug and load again. Would something be interrupting the timer? What's the proper way to debug this?



  • Hmm, weird, once the timers are started, it should run.

    There is one mechanism that stops all timers if the interface is closed (because if you have more than 30 instances of a plugin open the overhead of going through all timers will make the UI very unresponsive). This is the only thing that might cause the timers to stop working.

    Which setup are you testing?



  • @Christoph-Hart I'm using scriptnode built October 23.
    It will happen (sometimes) after putting a second instance of the plugin FX in a single session and (most often) when activating a plugin FX after making it inactive first.
    also noticing a loud pop when bypassing in PT and cubase.



  • @Christoph-Hart Did you ever get a chance to investigate? Let me know if there's anything else I can do to help troubleshoot.



  • @dustbro Did you find an resolution or workaround to this issue?
    Just stumbled across a similar thing ☺
    Cheers



  • @LeeC I haven't.



  • @Christoph-Hart said in Gain Reduction Meter:

    Hmm, weird, once the timers are started, it should run.

    @Christoph-Hart I have to dig this one up from the grave. I have 2 different virtual instruments using this code for GR meters and both are experiencing intermittent behavior.
    The interesting thing is whatever causes this to happen seems to be "system wide". By that I mean: If I load instrument A and the meter isn't working, loading an instance of instrument B will also experience a non working meter.
    Sometimes changing the GUI scale in the custom settings floating tile can knock it back into action, but most of the time I have to close/reopen my session to get meters working again.

    These are using a slider with filmstrip.
    I also tried using a panel instead of a slider. When the malfunction occurred, the meter flickered (what appeared to be the amount of images in the strip) and then disappeared.

    Does any of this ring a bell for you?


Log in to reply
 

27
Online

741
Users

2.9k
Topics

24.7k
Posts