Modify cues

Hello,

I try to find a solution to modify “cues” via a midi controller and the " MidiController " node.

The difficulty is that the values coming from the controller give up automatically the original values from the cues. I’ve tried with " framedelay " and “S+H” nodes without results…

By using the " MidiControllerOut " node and the " dosend" pin the values are sent to the controller and it works well, but they are not updated in the " MidiController " node.

What’s wrong?

Any help would be much appreciated!

Friendly, qwas

Here is a little example of the patch

modifyCues.v4p (14.5 kB)

Since I am never to lazy to help… what you want to do with the ‘Cues’ from your MIDI controller? Merge them, add them or replace them?

You get a spread of MIDI values, and than you select a cue number. What do you want to select? Looking at the patch, you receive 32 values from the MIDI controller, and than you want to decide what 8 slices you want to send as output to the MIDI controller? Is this correct?

Hello West,

Thanks for you answer !

what you want to do with the ‘Cues’ from your MIDI controller? Merge them, add them or replace them?

I want to create the ‘Cue list’ with the MIDI controller and the outgoing values from the ‘Cue list’ have to update the MIDI controller values too.

You get a spread of MIDI values, and than you select a cue number. What do you want to select? Looking at the patch, you receive 32 values from the MIDI controller, and than you want to decide what 8 slices you want to send as output to the MIDI controller? Is this correct?

Yes exactly !

I finally found a easy solution to update the incoming values from the controller with the S+H and OR nodes and for updating the ‘Cue list’ using a ‘FrameDelay’ node.

It work fine but now when I open the patch with the ‘Cue list’ pin connected to the ‘FrameDelay’ pin the values are erased…

How can I do to keep save the ‘Cue list’ values without disconnect these pin’s before save and closing the patch ?

Here is a patch

modifyCues_midi.v4p (31.7 kB)

And without MIDI…

modifyCues_no_midi.v4p (28.6 kB)

hi qwas_blus, hi west

may i ask you on your very first patch sended in this thread HOW you hide connecions and restore their viewing ? ;-)

@ Karistouf, long time no chat, hope you are doing great :)

in Herr Inspector, you have these white, grey or dark gray boxes in front of the pin value - name. Just click on these to toggle them to get them hidden or shown again.

White = Hidden
Grey = Hidden, but link able.
Dark Grey = Shown and link able.

This is a great way to retrieve your hidden pins on some nodes.
Texture type pin on DX9Teture (EX9.Texture) for example, I always hate it when I can’t select a mode with Alpha.

On a personal note, hiding nodes is evil, because you can’t change anything or check values without using Herr Inspector (but that is just personal).

@ qwas_blus, I will check it tonight, no vvvv here.

hi west ! going fine. at home finally with the little family. i m not dropping down the idea to make you come in france ;-)

thanks for the explanation
i m of your opinion about hiddens, BUT there is quite some figures some clean of patch is needed…

by the way, just trying with an IO box doesnt give me any result … you know me to be a very slowww boy, could you just tell me how you proceed to make disappear the connection betxeen 2 IOboxes ?

@West

You are right about ’ hiding nodes is evil ’ but I work almost the time with the Inspektor opened…

@Karistouf

Actualy I’m not loosing the connection but the values of the IOboxe. Save the IOboxe with connected FrameDelay node, closes the patch, open it again: The values of the IOboxe are lost…

?

hum… what about OnOpen getting values saved in a subpatch ? ( a copy of framedelay output) with a switch ?

@ Karistouf, I really need to visit some day soon :)

For the IO box, if you look at Herr Inspector, there are 3 section (and this goes for most nodes). The sections are separated by a grey horizontal line.

The First part, that begins with Descriptive name, are the (dunno the vvvv word) but call it settings. These cannot be changed by the pins (can be changed with Setpatch (vvvv) and other nodes).
So, there is nothing to hide or show here.

The Middle Part, (begins with Slice offset) these are the INPUT pins, these can set to white grey, dark grey.

The Last part (begins with X Output Value), these are your output pins. For Example, ID has he white box in front of it. If I want to use the ID in my patch, I can make it Grey, a pin appears, and I can use the ID.

Hope it is a bit clear now.

@ qwas_blus

Your problem can be easy fixed with a simple ‘on open’ and ‘switch’ combo. This is always used to give frame-delay loops a default value.

modifyCues_no_midi-3.v4p (28.4 kB)

And here is a patch that does the same, without a feedback loop.

modifyCues_no_midi-4.v4p (17.2 kB)

hi west ! you will you will… next project i will not do it alone, better to work in team…
about hidden: this for the pins. ok, got it.
i was not clear in my asking.
in its FIRST posted patch qwas blus has an IO box conneted to the other, without connection being seen. that i would like to know to do properly: hidden connections, not pins.
je sais, its surely a peace of cake, BUT ;-)

@West
Thank you , I had also tried with OnOpen but not in the good place…

@Karistouf
Thank you to! ( et je ne suis même pas sûr de pouvoir mieux m’exprimer en français! :p )

my pleasure !
basé ou ?

Bienne, Berne in Switzerland, and you?

france, near Vernon, between Rouen and Paris ;-)