Operator feedback in the scheduler event domain

Options
13»

Comments

  • colB
    colB Member Posts: 1,122 Guru

    You had removed the ..SR default link to parent SR here:

    image.png

    And edited this one changing it from ..SR to SR (I explained that this would break it in an earlier post)

    Not sure what was going on in the strange macro here, but I replaced it with a multiply, because that's all the macro was doing anyway:

    image.png
    guiclock2 fixed.ens
  • gentleclockdivider
    gentleclockdivider Member Posts: 356 Advisor
    edited 12:19AM
    https://community.native-instruments.com/discussion/comment/233366#Comment_233366

    Noppes , the point was that I WANTED to change the masterclock name .
    I know it's just a mulitplier and I know that it works when the masterclock is called SR .

    The point was that once the masterclock was renamed , the mulitplier didn't mulitply the feedback anymore ,even when it was in a new macro that fell within the scope of the newly renamed masterclock .


    Here is it again , do NOT change the name of the masterclock called "this"

    The macro called 'Hello" is working correctly since the scope state is : connected , and it works perfeclty as a gain mulitplier but once it's used for routing operator 1 back to itself it doesn't anymore

    If you looked at the giff that I uploaded it's all documented , but I will do it again

    I a nutshell , I renamed the master clock to a new name called "this", and made sure that both operators fall within the scope of that new name .

    You said that for implicit feedback , it needs to fall within the same scope so I created a new macro that falls within the same scope , that macro is called "hello "
    The first 10 seconds of the giff show an operator mulitplied by this macro ( gain mulitiplier ) straight ot the ouptut , result is a working osciloscope
    Conslusion : the macro works
    The last part of the giff shows operator goimg into operator 1 , and fed back to itself , this time the macro is used a gain mulitplier for operator feedback but it doesn't works
    Hope it's all clear
    Please have a look at the giff

    Why is that ?

    https://i.imgur.com/H5OheIl.gif


    guiclock2.ens
  • colB
    colB Member Posts: 1,122 Guru
    edited 12:48AM

    It's because you created a new clock and gave it a new name.

    I keep telling you what to do, and why, and you keep insisting on doing it differently, but the stuff that doesn't work is the stuff you are doing differently. And yet you persist.

    The answer to this particular question is on the first page of this thread.

  • colB
    colB Member Posts: 1,122 Guru

    You cannot 'rename' the 'master clock' (whatever that is?)

    You can 'override' the sample rate clock bundle 'SR'. You override it by packing some other clock, sample rate and reset into a bundle and calling that SR. Within the scope of your new distribution bundle SR, anything that refers to the sample rate clock will use yours instead… including implicit feedback…

    Don't use implicit feedback, it's bad coding style.

    If you create a clock bundle, and pipe it through a bundle distributer called 'this', then all you have is a distribution bundle called 'this' with a clock in it.

Back To Top

Categories