• gentleclockdivider

    @seb-harmonik.ar said:

    @gentleclockdivider in order to have an attack time of 1000 ms, you need to do:
    [1 1000 0(
    meaning 'from the time this message was sent (no delay = 3rd arg), ramp to 1 over 1000 milliseconds'.
    then, if you want to send a message for the decay and for the decay to be scheduled after that attack you would send this at the same time:
    [0 500 1000(
    meaning "from 1000 milliseconds after this message is sent (3rd arg, which will be when the attack stage ends), go to 0 in 500 ms"
    putting those together (and sending them at the same time) would be:
    [1 1000 0, 0 500 1000(

    You mean opening with an opening square bracket and closing with an opening bracket ?
    Sorry but I hav never ever seen something that closes a message-list with an open bracket
    I guess that must be some knd of typo since the console doesn't understand it , forgive me when wrong
    Using [ ] doesn't work either

    posted in technical issues read more
  • gentleclockdivider

    @ddw_music
    To wait before attack stage is excuted , iow delay time
    Wait for 1000 ms when triggerd , then go to level 1 instantly (0ms°)

    posted in technical issues read more
  • gentleclockdivider

    @ddw_music said:

    @gentleclockdivider said:

    So when I have two separate messages 1 0 1000 , and 0 0 1000 , both messages will wait for 1000 ms and have the exact same behaviour as when clicking the toggles ( see screenshot )

    Do you want the envelope segments to run at the same time?

    No. You want one after the other.

    Therefore the two times should not be the same.

    Making them both 1000 means it will of course not work.

    Putting two messages into one message is afaik separated by a comma , this just does not work

    It absolutely does work. Here, there's one message box with two messages in it, and you clearly see two envelope segments being drawn.

    pd-envelope.png

    hjh
    Now change that delay time time for the attack stage to 1000 , it won't work anymore
    1.jpg

    posted in technical issues read more
  • gentleclockdivider

    @ddw_music said:

    You misinterpreted "delay time" as the delay after the previous segment. In fact, it's a delay time after the moment of receipt.

    NO I didn't
    See part my first message
    I created two packs the first left pack triggered by yellow toggle goes to level 1 in 500 ms and no delay time

    posted in technical issues read more
  • gentleclockdivider

    @timothyschoen
    I am aware of that and I have used it before for making a drum synth , altough prefer the cyclone curve~object
    2.jpg
    Still I want to figure this vline~stuff out

    posted in technical issues read more
  • gentleclockdivider

    1.jpg
    If I put the nr's 1 0 1000 into a pack f f f and bang it , the vline will be executed 1000 ms after it has received it's trigger .
    Same as when put in a message 1 0 1000
    So when I have two separate messages 1 0 1000 , and 0 0 1000 , both messages will wait for 1000 ms and have the exact same behaviour as when clicking the toggles ( see screenshot )
    Putting two messages into one message is afaik separated by a comma , this just does not work

    posted in technical issues read more
  • gentleclockdivider

    @ddw_music said:

    @gentleclockdivider said:

    The issue is when I want to bring these two messages into a single one , which uses a comma sign "," ' to separate the two series of arguments
    So 1 500 0; 0 600 0 but the message doesn't work becasue of the zero delay time in the first part of the message ( attack stage )

    The message box should be 1 500, 0 600 500.

    You misinterpreted "delay time" as the delay after the previous segment. In fact, it's a delay time after the moment of receipt.

    If you want the "0 600" segment to execute immediately after the 500 ms segment, this is 500 ms after the message arrives at the inlet -- so you have to restate the 500.

    You could argue that this not the way you would like it to be done, but this is what's documented and it does work.

    hjh
    1.jpg
    If I put the nr's 1 0 1000 into a pack f f f and bang it , the vline will be executed 1000 ms after it has received it's trigger .
    Same as when put in a message 1 0 1000
    So when I have two separate messages 1 0 1000 , and 0 0 1000 , both messages will wait for 1000 ms and have the exact same behaviour as when clicking the toggles ( see screenshot )
    Putting two messages into one message is afaik separated by a comma , this just does not work

    posted in technical issues read more
  • gentleclockdivider

    The vline ~makes absolutely no sense to me
    I understand the concept just fine but when putting multiple stages in a message it's just behaves not as expected
    Concept is simple , target level , times it takes to reach that level and optional delay
    SO
    I created two packs the first left pack triggered by yellow toggle goes to level 1 in 500 ms and no delay time (console = print A)
    The vline~ as expeced stays at that level , blue toggle will bring the Vline~down to level 0 in 600ms with no delay (console print B )
    The console shows two separate messages .
    The issue is when I want to bring these two messages into a single one , which uses a comma sign "," ' to separate the two series of arguments
    So 1 500 0; 0 600 0 but the message doesn't work becasue of the zero delay time in the first part of the message ( attack stage )
    Why is that ?
    I put the two pack messages into a single message separated by a comma it should work no ?
    1.jpg

    posted in technical issues read more
  • gentleclockdivider

    I'm on win 10
    It seemed to be a one time issue.
    Doesn't happen anymore

    posted in technical issues read more
  • gentleclockdivider

    Not perse an issue
    A select module nr of outputs is defined by the nr of arguments , it's a pity we can't change the argument of select modules as long as it respects the nr of outputs
    Screenshot shows 4 single select modules , when unpacking a list we can change the argument of each select module individually
    When the select module has 1> argument we can't do that anymore
    1.jpg

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!