ArrayArrayArrayArrayArray BrainModular BrainModular Users Forum 2019-12-27T16:41:26+02:00 https://brainmodular.org/forums/app.php/feed/topic/6590 2019-12-27T16:41:26+02:00 2019-12-27T16:41:26+02:00 https://brainmodular.org/forums/viewtopic.php?t=6590&p=41994#p41994 <![CDATA[Re: motorize in HH4]]>
Hello

You need to have a look on your "MIDI Device Out", right-click to display the settings and check "motorized device".

Sylvain
I owe you a cold one brotha. That was 95% of the problem. I recall setting it at one point, but didn't recheck later after I refreshed devices and possibly imported an old one. Devices seem a little different than they were in HH2, not just improvement-wise. I'm pretty sure I used to be able to have several versions of the same device, with different filter sets/modules but now it seems like there can only be one for a specific device id. Not sure, but it seems so. Anyway thanks again Sylvain!

Statistics: Posted by parityflux — 27 Dec 2019, 15:41


]]>
2019-12-24T00:30:05+02:00 2019-12-24T00:30:05+02:00 https://brainmodular.org/forums/viewtopic.php?t=6590&p=41993#p41993 <![CDATA[Re: motorize in HH4]]>
Screen Shot 2019-12-23 at 23.25.11.png
Hello

You need to have a look on your "MIDI Device Out", right-click to display the settings and check "motorized device".

Sylvain

Statistics: Posted by SylvainT — 23 Dec 2019, 23:30


]]>
2019-12-23T21:40:21+02:00 2019-12-23T21:40:21+02:00 https://brainmodular.org/forums/viewtopic.php?t=6590&p=41992#p41992 <![CDATA[Re: motorize in HH4]]> -j

Statistics: Posted by parityflux — 23 Dec 2019, 20:40


]]>
2019-12-23T21:12:12+02:00 2019-12-23T21:12:12+02:00 https://brainmodular.org/forums/viewtopic.php?t=6590&p=41991#p41991 <![CDATA[Re: motorize in HH4]]>
019-12-23 220715.jpg
if so, might be a bug 🤔

Statistics: Posted by x.iso — 23 Dec 2019, 20:12


]]>
2019-12-23T19:24:32+02:00 2019-12-23T19:24:32+02:00 https://brainmodular.org/forums/viewtopic.php?t=6590&p=41990#p41990 <![CDATA[motorize in HH4]]>
I have to use a workaround with using a MIDI bus to flow control data back to the output of the device. The device in my case is a LIVID CNTRL-R. It's a pretty straightforward implementation. If you send it a controller message and value, it will light up a button in a color depending on value. If I use a full 127, the assigned button lights up green. Dead simple.

I got to a certain permutation where I can toggle a button in Usine using the controller, and the Usine button and the controller button both light up. That's fine. If I click the button in Usine, however, the controller does not light up. I've checked all of the relevant pipes and no midi data comes out when a learned button is clicked. I have tested a barebones implementation on a new workspace and spent hours on it.

I had this working beautifully in HH2. Now I'm just banging my head and questioning reality.

Also, I seem to remember a setting where when loading a workspace, Usine would transmit all of the motorized controls so the controller would have an initial ready-state matching Usine's. Where is that setting?

Statistics: Posted by parityflux — 23 Dec 2019, 18:24


]]>
BrainModular BrainModular Users Forum 2019-12-27T16:41:26+02:00 https://brainmodular.org/forums/app.php/feed/topic/6590 2019-12-27T16:41:26+02:00 2019-12-27T16:41:26+02:00 https://brainmodular.org/forums/viewtopic.php?t=6590&p=41994#p41994 <![CDATA[Re: motorize in HH4]]>
Hello

You need to have a look on your "MIDI Device Out", right-click to display the settings and check "motorized device".

Sylvain
I owe you a cold one brotha. That was 95% of the problem. I recall setting it at one point, but didn't recheck later after I refreshed devices and possibly imported an old one. Devices seem a little different than they were in HH2, not just improvement-wise. I'm pretty sure I used to be able to have several versions of the same device, with different filter sets/modules but now it seems like there can only be one for a specific device id. Not sure, but it seems so. Anyway thanks again Sylvain!

Statistics: Posted by parityflux — 27 Dec 2019, 15:41


]]>
2019-12-24T00:30:05+02:00 2019-12-24T00:30:05+02:00 https://brainmodular.org/forums/viewtopic.php?t=6590&p=41993#p41993 <![CDATA[Re: motorize in HH4]]>
Screen Shot 2019-12-23 at 23.25.11.png
Hello

You need to have a look on your "MIDI Device Out", right-click to display the settings and check "motorized device".

Sylvain

Statistics: Posted by SylvainT — 23 Dec 2019, 23:30


]]>
2019-12-23T21:40:21+02:00 2019-12-23T21:40:21+02:00 https://brainmodular.org/forums/viewtopic.php?t=6590&p=41992#p41992 <![CDATA[Re: motorize in HH4]]> -j

Statistics: Posted by parityflux — 23 Dec 2019, 20:40


]]>
2019-12-23T21:12:12+02:00 2019-12-23T21:12:12+02:00 https://brainmodular.org/forums/viewtopic.php?t=6590&p=41991#p41991 <![CDATA[Re: motorize in HH4]]>
019-12-23 220715.jpg
if so, might be a bug 🤔

Statistics: Posted by x.iso — 23 Dec 2019, 20:12


]]>
2019-12-23T19:24:32+02:00 2019-12-23T19:24:32+02:00 https://brainmodular.org/forums/viewtopic.php?t=6590&p=41990#p41990 <![CDATA[motorize in HH4]]>
I have to use a workaround with using a MIDI bus to flow control data back to the output of the device. The device in my case is a LIVID CNTRL-R. It's a pretty straightforward implementation. If you send it a controller message and value, it will light up a button in a color depending on value. If I use a full 127, the assigned button lights up green. Dead simple.

I got to a certain permutation where I can toggle a button in Usine using the controller, and the Usine button and the controller button both light up. That's fine. If I click the button in Usine, however, the controller does not light up. I've checked all of the relevant pipes and no midi data comes out when a learned button is clicked. I have tested a barebones implementation on a new workspace and spent hours on it.

I had this working beautifully in HH2. Now I'm just banging my head and questioning reality.

Also, I seem to remember a setting where when loading a workspace, Usine would transmit all of the motorized controls so the controller would have an initial ready-state matching Usine's. Where is that setting?

Statistics: Posted by parityflux — 23 Dec 2019, 18:24


]]>