Welcome to %s forums

BrainModular Users Forum

Login Register

Bug with Has Changed?

General Discussion about whatever fits..
Post Reply
whitelobster
Member
Posts: 19
Contact:

Unread post by whitelobster » 19 Aug 2018, 00:55

Hello

I am working on a patch and am running into a very strange behavior with the HAS CHANGED module

The XY pad in the attached patch sends jerky midi for reasons that I do not understand, moving from right to left and up to down within hollyhock produces a smooth stream of values from 0-127 -----however the second I attempt to create midi output from this stream of values, the string of values is distorted and the transition form 0-127 occurs oddly only in the middle of the xy pad, ie it behaves as if the XY pad has been compressed to a quarter of it's size and spits out jerky values

I believe this is caused by the HAS CHANGED module that is triggering the creation of the midi cc messages

you can see this jerkiness in action in the patch- I have created a red knob that shows the output midi signal next to the white knobs that show the same signal before it is sent out as midi- you can see that the white knobs run smooth along the entire length of the XY pad- but the red knob is very jerky and only activated in the center

I am using hollyhock 3.0.168-1

here is my patch

http://www.sensomusic.org/forums/upload ... -STRIP.wkp


Can someone please tell me what I am doing wrong or how I can implement this such that I get a smooth midi output across the entire 0-127 range while using the xy pad?

Thank you so much!

23fx23
Member
Posts: 2545
Contact:

Unread post by 23fx23 » 19 Aug 2018, 02:19

in the patch i only see a white knob, wich input is connected to a midi create out? (but im on 166..maybe i have to update)..

that won't fix your issue, but thats not a correct way of wiring, blue midi pins/wires create midi flows type signals, a knob expect float or integer flows type signals .
midi is internally 4bytes, like a float but those 4bytes are arranged in a conpletelly different way (0 is channel, 2 is msg, 2 is code1, 3 is code 2)
so if man try to 'interpret' that as a float number that doesn't make much sense.

whitelobster
Member
Posts: 19
Contact:

Unread post by whitelobster » 19 Aug 2018, 03:45

Hello
I believe we are talking about the same knob maybe the color changed in that version

I know that is improper wiring mixing colors like this- is there something else I can change to get the numbers flowing properly/smoothly to midi?

Thank you so much!

23fx23
Member
Posts: 2545
Contact:

Unread post by 23fx23 » 19 Aug 2018, 04:58

if want to display the actual 'value' that is sent out of the midi (wich is code2 here) one possibkle way is connect a midi filter out of your midi create, and link your knob to the code2 output of the midifilter. normally you should see see the same 'smooth' thing as input.

whitelobster
Member
Posts: 19
Contact:

Unread post by whitelobster » 19 Aug 2018, 05:14

I don’t actually care about accurately displaying the midi, this was only an attempt to visualize the jerky output of the midi itself—-if you try the patch you will find that the actual midi being sent out is jerky, not just the knob, this makes no sense to me though looking at the patch because everything except for the test display knob at the end of the chain seems to be wired properly from what I can tell——any ideas?

23fx23
Member
Posts: 2545
Contact:

Unread post by 23fx23 » 19 Aug 2018, 05:30

i ll re check tomorrow. thinks it can be problematic in some cases if too much midi messages are sent at same time in the same processed bloc. not in from of main computer now but normally there is an 'unpack' midi on input/output or midi config i don't remember that force send them one after the other, might worth a try

whitelobster
Member
Posts: 19
Contact:

Unread post by whitelobster » 19 Aug 2018, 05:55

Thank you so much, this is really making no sense to me now-

the modules generating midi cc 81 and 83 map properly

the modules generating cc 82 and 85 send the jerky distorted/imporperly scaled midi data

what is even more confusing- if I take the output going into the cc83 module and route it to the cc82 module it still sends out jerky midi even though it is coming from the exact same source

I've tried limiting excessive midi messages using hysteresis? Still doesn't seem to make a difference

User avatar
nay-seven
Site Admin
Posts: 5684
Location: rennes France
Contact:

Unread post by nay-seven » 19 Aug 2018, 09:32

Hello, here a modified patch (with labels)
don't have jerky data, i'have add a MIDI monophonic module, you'll test it ON/OFF
i've add some Oscilloscopes to monitor the flux
also change the speed fader precision, the visible one was x.x, when the sub-patch one was integer

Download

PS: next time, please, try to create a post in the Patching forum ;-)

whitelobster
Member
Posts: 19
Contact:

Unread post by whitelobster » 20 Aug 2018, 03:57

Hi thank you so much for this. I would like to integrate this back into my own design of the patch as the piece I uploaded was just a piece of a larger patch- what changes were required to make it work properly? Is it just the monophonic midi? Was polyphony the problem?

Thank you so much! Will post in the proper spot next time!

Post Reply

Who is online

Users browsing this forum: No registered users and 64 guests