ArrayArrayArrayArrayArrayArrayArrayArrayArrayArray BrainModular BrainModular Users Forum 2015-04-30T17:50:01+02:00 https://brainmodular.com/forums/app.php/feed/topic/4547 2015-04-30T17:50:01+02:00 2015-04-30T17:50:01+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=32586#p32586 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]> Statistics: Posted by 23fx23 — 30 Apr 2015, 17:50


]]>
2015-04-30T17:45:57+02:00 2015-04-30T17:45:57+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=32585#p32585 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]> Statistics: Posted by 23fx23 — 30 Apr 2015, 17:45


]]>
2015-04-30T15:50:55+02:00 2015-04-30T15:50:55+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=32584#p32584 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]>
Hard to do in the middle of a script, though.

Statistics: Posted by shawnb — 30 Apr 2015, 15:50


]]>
2015-04-30T07:21:07+02:00 2015-04-30T07:21:07+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=32581#p32581 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]> Statistics: Posted by 23fx23 — 30 Apr 2015, 07:21


]]>
2015-04-30T06:59:55+02:00 2015-04-30T06:59:55+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=32580#p32580 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]>
This now works in HH2.

Still get the erroneous 'Var not found' messages though. But the links are properly created in subpatches now.

Statistics: Posted by shawnb — 30 Apr 2015, 06:59


]]>
2014-09-13T19:26:51+02:00 2014-09-13T19:26:51+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=30450#p30450 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]>
The beauty of HH, though, is that there a many ways to do what you wanna do...

I found a way to automate using the #s, e.g.,
CREATE_LINK 17 2 13 0

After numerous attempts, I couldn't get IML to talk to modules within a subpatch. Sure looks like it should do that (I think this is another symptom of the same problem...). Rather than pull my hair out, I just created data inputs, negating the need to communicate directly to a module within the subpatch.

There's always an alternative approach to get the job done. I *really* love that about HH.

Statistics: Posted by shawnb — 13 Sep 2014, 19:26


]]>
2014-09-10T04:30:19+02:00 2014-09-10T04:30:19+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=30439#p30439 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]> The following demonstrates the issues with CREATE_LINK with subpatches.
I have similar issues elsewhere using IML with subpatches.
Shawn

The following code works great:
CREATE_MODULE GEORGE 4 200 200
CREATE_MODULE SUSAN 4 400 200
CREATE_LINK GEORGE 'OUT 1' SUSAN 'IN 1'

And reports the following in the console (the 'Var not found' messages are erroneous, because the link was formed correctly):
process msg CREATE_MODULE GEORGE 4 200 200
Create module TpgVolume_audio 261
SET_VAR String LAST_CREATED_MODULE_NAME = GEORGE
process msg CREATE_MODULE SUSAN 4 400 200
Create module TpgVolume_audio 261
SET_VAR String LAST_CREATED_MODULE_NAME = SUSAN
process msg CREATE_LINK GEORGE OUT 1 SUSAN IN 1
Var not found GEORGE
Var not found OUT 1
Var not found SUSAN
Var not found IN 1

But this does not (IN & OUT are terminals & LIFEPATCH.pat is a subpatch that works fine):
CREATE_MODULE GEORGE 6 200 200 lifepatch.pat
CREATE_MODULE SUSAN 6 400 200 lifepatch.pat
CREATE_LINK GEORGE OUT SUSAN IN

This is reported in the console:
process msg CREATE_MODULE GEORGE 6 200 200 LIFEPATCH.PAT
Create module TPgInput_DATA 20
Create module TPgOutput_Data 21
Create module TpgShape 334
Create module TpgPass_Event 157
Create module TpgEqual 49
Create module TpgEqual 49
Create module TpgOr 51
Create module TpgPlus1 291
Create module TPgInput_DATA 20
Create module TpgSelector_Color 342
Create module TpgColor_Chooser 223
Create module TpgSub_Patch 6
SET_VAR String LAST_CREATED_MODULE_NAME = GEORGE
process msg CREATE_MODULE SUSAN 6 400 200 LIFEPATCH.PAT
Create module TPgInput_DATA 20
Create module TPgOutput_Data 21
Create module TpgShape 334
Create module TpgPass_Event 157
Create module TpgEqual 49
Create module TpgEqual 49
Create module TpgOr 51
Create module TpgPlus1 291
Create module TPgInput_DATA 20
Create module TpgSelector_Color 342
Create module TpgColor_Chooser 223
Create module TpgSub_Patch 6
SET_VAR String LAST_CREATED_MODULE_NAME = SUSAN
process msg CREATE_LINK GEORGE OUT SUSAN IN
Var not found GEORGE
Can't create/delete link GEORGE OUT SUSAN IN

Statistics: Posted by shawnb — 10 Sep 2014, 04:30


]]>
2014-09-09T21:43:35+02:00 2014-09-09T21:43:35+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=30435#p30435 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]>
Feels like it's not working for subpatches. Still no luck.

Statistics: Posted by shawnb — 09 Sep 2014, 21:43


]]>
2014-09-09T10:01:49+02:00 2014-09-09T10:01:49+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=30427#p30427 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]> The module type is set by the parameter id , then the module is renamed with the modulename.

so
CREATE_MODULE vol 4 100 100 // creates an audio volume module ( because of it's ID 4) , then rename this module vol

so
CREATE_MODULE xyz 4 100 100 // creates an audio volume module and will rename it xyz

Statistics: Posted by nay-seven — 09 Sep 2014, 10:01


]]>
2014-09-07T01:39:15+02:00 2014-09-07T01:39:15+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=30419#p30419 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]>
I'm learning IML... Sorta...

If I create a module from a subpatch, e.g.:
CREATE_MODULE xyz 6 100 100 mypatch.pat

it works great, though the module's caption says it is "mypatch"
Any attempt to use xyz, e.g.,
CREATE_LINK xyz OUT somethingelse IN

and I get a "Var Not Found XYZ"

Question 1: Should I be able to use xyz as a modulename in CREATE_LINK?

Question 2: Where is the module name visible? Everywhere I look I cannot see xyz, I see "MYPATCH" - the subpatch's filename?

If I use the #s, e.g.,
CREATE_LINK 17 2 13 0
everything works great....

Curious, but if I use a:
CREATE_LINK 17 OUT 13 IN (using the terminal's names, not indexes)
everything works great, however, it ALSO tells me
Var Not Found OUT
Var Not Found IN
even though it worked.

Probably noob questions...

Shawn

4/30/15 edit: This was a bug & it was fixed in HH2.

Statistics: Posted by shawnb — 07 Sep 2014, 01:39


]]>
BrainModular BrainModular Users Forum 2015-04-30T17:50:01+02:00 https://brainmodular.com/forums/app.php/feed/topic/4547 2015-04-30T17:50:01+02:00 2015-04-30T17:50:01+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=32586#p32586 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]> Statistics: Posted by 23fx23 — 30 Apr 2015, 17:50


]]>
2015-04-30T17:45:57+02:00 2015-04-30T17:45:57+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=32585#p32585 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]> Statistics: Posted by 23fx23 — 30 Apr 2015, 17:45


]]>
2015-04-30T15:50:55+02:00 2015-04-30T15:50:55+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=32584#p32584 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]>
Hard to do in the middle of a script, though.

Statistics: Posted by shawnb — 30 Apr 2015, 15:50


]]>
2015-04-30T07:21:07+02:00 2015-04-30T07:21:07+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=32581#p32581 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]> Statistics: Posted by 23fx23 — 30 Apr 2015, 07:21


]]>
2015-04-30T06:59:55+02:00 2015-04-30T06:59:55+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=32580#p32580 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]>
This now works in HH2.

Still get the erroneous 'Var not found' messages though. But the links are properly created in subpatches now.

Statistics: Posted by shawnb — 30 Apr 2015, 06:59


]]>
2014-09-13T19:26:51+02:00 2014-09-13T19:26:51+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=30450#p30450 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]>
The beauty of HH, though, is that there a many ways to do what you wanna do...

I found a way to automate using the #s, e.g.,
CREATE_LINK 17 2 13 0

After numerous attempts, I couldn't get IML to talk to modules within a subpatch. Sure looks like it should do that (I think this is another symptom of the same problem...). Rather than pull my hair out, I just created data inputs, negating the need to communicate directly to a module within the subpatch.

There's always an alternative approach to get the job done. I *really* love that about HH.

Statistics: Posted by shawnb — 13 Sep 2014, 19:26


]]>
2014-09-10T04:30:19+02:00 2014-09-10T04:30:19+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=30439#p30439 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]> The following demonstrates the issues with CREATE_LINK with subpatches.
I have similar issues elsewhere using IML with subpatches.
Shawn

The following code works great:
CREATE_MODULE GEORGE 4 200 200
CREATE_MODULE SUSAN 4 400 200
CREATE_LINK GEORGE 'OUT 1' SUSAN 'IN 1'

And reports the following in the console (the 'Var not found' messages are erroneous, because the link was formed correctly):
process msg CREATE_MODULE GEORGE 4 200 200
Create module TpgVolume_audio 261
SET_VAR String LAST_CREATED_MODULE_NAME = GEORGE
process msg CREATE_MODULE SUSAN 4 400 200
Create module TpgVolume_audio 261
SET_VAR String LAST_CREATED_MODULE_NAME = SUSAN
process msg CREATE_LINK GEORGE OUT 1 SUSAN IN 1
Var not found GEORGE
Var not found OUT 1
Var not found SUSAN
Var not found IN 1

But this does not (IN & OUT are terminals & LIFEPATCH.pat is a subpatch that works fine):
CREATE_MODULE GEORGE 6 200 200 lifepatch.pat
CREATE_MODULE SUSAN 6 400 200 lifepatch.pat
CREATE_LINK GEORGE OUT SUSAN IN

This is reported in the console:
process msg CREATE_MODULE GEORGE 6 200 200 LIFEPATCH.PAT
Create module TPgInput_DATA 20
Create module TPgOutput_Data 21
Create module TpgShape 334
Create module TpgPass_Event 157
Create module TpgEqual 49
Create module TpgEqual 49
Create module TpgOr 51
Create module TpgPlus1 291
Create module TPgInput_DATA 20
Create module TpgSelector_Color 342
Create module TpgColor_Chooser 223
Create module TpgSub_Patch 6
SET_VAR String LAST_CREATED_MODULE_NAME = GEORGE
process msg CREATE_MODULE SUSAN 6 400 200 LIFEPATCH.PAT
Create module TPgInput_DATA 20
Create module TPgOutput_Data 21
Create module TpgShape 334
Create module TpgPass_Event 157
Create module TpgEqual 49
Create module TpgEqual 49
Create module TpgOr 51
Create module TpgPlus1 291
Create module TPgInput_DATA 20
Create module TpgSelector_Color 342
Create module TpgColor_Chooser 223
Create module TpgSub_Patch 6
SET_VAR String LAST_CREATED_MODULE_NAME = SUSAN
process msg CREATE_LINK GEORGE OUT SUSAN IN
Var not found GEORGE
Can't create/delete link GEORGE OUT SUSAN IN

Statistics: Posted by shawnb — 10 Sep 2014, 04:30


]]>
2014-09-09T21:43:35+02:00 2014-09-09T21:43:35+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=30435#p30435 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]>
Feels like it's not working for subpatches. Still no luck.

Statistics: Posted by shawnb — 09 Sep 2014, 21:43


]]>
2014-09-09T10:01:49+02:00 2014-09-09T10:01:49+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=30427#p30427 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]> The module type is set by the parameter id , then the module is renamed with the modulename.

so
CREATE_MODULE vol 4 100 100 // creates an audio volume module ( because of it's ID 4) , then rename this module vol

so
CREATE_MODULE xyz 4 100 100 // creates an audio volume module and will rename it xyz

Statistics: Posted by nay-seven — 09 Sep 2014, 10:01


]]>
2014-09-07T01:39:15+02:00 2014-09-07T01:39:15+02:00 https://brainmodular.com/forums/viewtopic.php?t=4547&p=30419#p30419 <![CDATA[CREATE_LINK confusing behavior... A couple of questions!]]>
I'm learning IML... Sorta...

If I create a module from a subpatch, e.g.:
CREATE_MODULE xyz 6 100 100 mypatch.pat

it works great, though the module's caption says it is "mypatch"
Any attempt to use xyz, e.g.,
CREATE_LINK xyz OUT somethingelse IN

and I get a "Var Not Found XYZ"

Question 1: Should I be able to use xyz as a modulename in CREATE_LINK?

Question 2: Where is the module name visible? Everywhere I look I cannot see xyz, I see "MYPATCH" - the subpatch's filename?

If I use the #s, e.g.,
CREATE_LINK 17 2 13 0
everything works great....

Curious, but if I use a:
CREATE_LINK 17 OUT 13 IN (using the terminal's names, not indexes)
everything works great, however, it ALSO tells me
Var Not Found OUT
Var Not Found IN
even though it worked.

Probably noob questions...

Shawn

4/30/15 edit: This was a bug & it was fixed in HH2.

Statistics: Posted by shawnb — 07 Sep 2014, 01:39


]]>