Re: Ramp message

Administrator

Hi Ricardo,

I would recommend using j.send or j.remote instead. If you check the inner workings of standard modules such as degrade~.model you’ll see that we no longer have inlets connected directly to j.model. In this model it still works to pass messages to the leftmost inlet, thanks to j.in~ that forwards them to j.model, but you could also use j.send as illustrated here.

Re: Ramp message

Administrator

Hi Ricardo,

At some point the code for the j.parameter @scheduler attribute was updated so that it is no longer needed (or even correct) to write “Max” with a capital M. If I change “Max” for “max” in the glue model, and then reload the patch, it works fine afterwards.

As for the forum, when you are posting to the forum rather than the mailing list, it always takes a while for it to show up. The best way to check if the mail made it to the list, is to check the proper list archive here:

Apart from that, may I suggest that you restructure your repository so that it an be distributed as a Max package? All that is needed is probably to create a folder named “patchers” and move all of your model patchers inside of it. This is the “modern” way to distribute 3rd party extensions to max, rather than having to add them to the File preferences.

Re: Ramp message

1) At some point the code for the j.parameter @scheduler attribute was updated so that it is no longer needed (or even correct) to write “Max” with a capital M. If I change “Max” for “max” in the glue model, and then reload the patch, it works fine afterwards.

Ah, ok, I see. Is there any overview over the changes made in each iteration of Jamoma 0.6, to see exactly what has been changed? I have been using the j.parameterCreate, to generate all attributes in all my modules. So this has automatically set the scheduler to "Max".

2)As for the forum, when you are posting to the forum rather than the mailing list, it always takes a while for it to show up. The best way to check if the mail made it to the list, is to check the proper list archive here:

Ok, thanks. Did not know that. I'm a child of the fast era, if it does not happen instantly, then it is broke. Sorry for this.

3)Apart from that, may I suggest that you restructure your repository so that it an be distributed as a Max package? All that is needed is probably to create a folder named “patchers” and move all of your model patchers inside of it. This is the “modern” way to distribute 3rd party extensions to max, rather than having to add them to the File preferences

Yes, I saw your issue on github, I'll fix this soon. Just did not think of it.
Thanks for the help Trond

Re: Ramp message

Administrator

Hi,

> 1) /At some point the code for the j.parameter @scheduler attribute was
> updated so that it is no longer needed (or even correct) to write “Max” with
> a capital M. If I change “Max” for “max” in the glue model, and then reload
> the patch, it works fine afterwards./
>
> Ah, ok, I see. Is there any overview over the changes made in each iteration
> of Jamoma 0.6, to see exactly what has been changed? I have been using the
> j.parameterCreate, to generate all attributes in all my modules. So this has
> automatically set the scheduler to “Max".

OK, I’ll make an issue for updating j.parameterCreate, it should also be renamed j.parameter_create.

I’m afraid that we don’t always manage to keep a proper log of changes. As long as 1.0 is still in beta, there might be changes happening. After the initial release we need to get better at logging changes. For the time being your best shot is to monitor the devel list every now and then to keep track of discussions.

> 2)/As for the forum, when you are posting to the forum rather than the
> mailing list, it always takes a while for it to show up. The best way to
> check if the mail made it to the list, is to check the proper list archive
> here:/
>
> Ok, thanks. Did not know that. I'm a child of the fast era, if it does not
> happen instantly, then it is broke. Sorry for this.

Yes, the Nabble site is a kind of hack forum solution. It’s just subscribing to the mailing list and displays mails. When someone posts to Nabble, the post is sent as a mail to the mailing list. We’ve been considering moving the mailing lists to Google groups, but I’m not sure if we’ve made a final decision on this yet.

> 3)/Apart from that, may I suggest that you restructure your repository so
> that it an be distributed as a Max package? All that is needed is probably
> to create a folder named “patchers” and move all of your model patchers
> inside of it. This is the “modern” way to distribute 3rd party extensions to
> max, rather than having to add them to the File preferences/
>
> Yes, I saw your issue on github, I'll fix this soon. Just did not think of
> it.
> Thanks for the help Trond

Hi,
> 1) /At some point the code for the j.parameter @scheduler attribute was
> updated so that it is no longer needed (or even correct) to write “Max” with
> a capital M. If I change “Max” for “max” in the glue model, and then reload
> the patch, it works fine afterwards./
>
> Ah, ok, I see. Is there any overview over the changes made in each iteration
> of Jamoma 0.6, to see exactly what has been changed? I have been using the
> j.parameterCreate, to generate all attributes in all my modules. So this has
> automatically set the scheduler to “Max".

OK, I’ll make an issue for updating j.parameterCreate, it should also be renamed j.parameter_create.

I’m afraid that we don’t always manage to keep a proper log of changes. As long as 1.0 is still in beta, there might be changes happening. After the initial release we need to get better at logging changes. For the time being your best shot is to monitor the devel list every now and then to keep track of discussions.
> 2)/As for the forum, when you are posting to the forum rather than the
> mailing list, it always takes a while for it to show up. The best way to
> check if the mail made it to the list, is to check the proper list archive
> here:/
>
> Ok, thanks. Did not know that. I'm a child of the fast era, if it does not
> happen instantly, then it is broke. Sorry for this.

Yes, the Nabble site is a kind of hack forum solution. It’s just subscribing to the mailing list and displays mails. When someone posts to Nabble, the post is sent as a mail to the mailing list. We’ve been considering moving the mailing lists to Google groups, but I’m not sure if we’ve made a final decision on this yet.
> 3)/Apart from that, may I suggest that you restructure your repository so
> that it an be distributed as a Max package? All that is needed is probably
> to create a folder named “patchers” and move all of your model patchers
> inside of it. This is the “modern” way to distribute 3rd party extensions to
> max, rather than having to add them to the File preferences/
>
> Yes, I saw your issue on github, I'll fix this soon. Just did not think of
> it.
> Thanks for the help Trond

Re: Ramp message

At some point the code for the j.parameter @scheduler attribute wasupdated so that it is no longer needed (or even correct) to write “Max” witha capital M. If I change “Max” for “max” in the glue model, and then reloadthe patch, it works fine afterwards./

Just as a side note, I believe (but that shoud be checked...) that ‘max' is set as the default ramp/drive for integers and decimals.. and so, not giving any value to this attribute is generally the best option (unless you actually want to prevent ramps to happen)