Resolume sends odd control signals to TouchOSC

[zerbix]

Hi All,

First of all,thank you very much for having this lovely artistic community put together!

Currently I`m assembling a TouchOSC-Resolume template.
Its partly going to be an exact copy of the active clip transport controls.

I have assigned note values for all the buttons,an osc for the playhead and midi cc for the rest of the faders.Sending these messages are seamless,however,I have experienced a very odd occurrence with received updated values.

For example,after I assigned the 1/5 CC. value for the BPM/Timeline/Smpte selector,several cue select and cue trigger buttons lit up on resolume,and it seems to go crazy ,as if instead of the 1/5CC parameter,a whole range of commands would rage through it.

I have separated the whole range into 0-42,43-85,86-127,created a multi toggle with exclusive mode on,and assigned the first two ranges for the first two buttons(I dont need smpte).

I thought,assigning a range of CC values is the problem,so I filtered out the exact values for the BPM and Timeline,yet the craziness persisted,regardless that nothing else was assigned to 1/5 CC.

Then,I changed the midi channel to 2,which sorted this problem.It was odd though.I couldnt find an answer to how the hell was resolume able to be "controlled" that manner when all the CC and note values were different and I made sure I havent left any osc commands on those buttons accidentally.

The second oddity is that if I select a clip to preview-although mostly most of the parameters are updated(faders,buttons,toggles)-frequently I have to double click on the desired clip to get TouchOSC updated.Sometimes a single click is enough.

The third oddity is,that I have created six push buttons for cue point select,and a six button multi toggle(exclusive mode) for cue point trigger.

These are all have different notes assigned to them.When I click(or double click) on a loaded clip to preview,the 6th cue point select button is lit,also the 3rd of the cue point trigger button..

They are all on different midi channels with different note values,yet something is making them lit up.If I touch cue point select 6,then 5 lit up,if I touch 5,then 4 lit up,and it all descends until 1 is lit,and If I press it,it goes off.

Now,the icing on the cake is with the cue point trigger multitoggle(exclusive mode).As If I click on 2 that changes the play direction(assigned to a totally different channel and note value),and if I press cue point trigger 1,that somehow,turns off the active play direction button,it becomes unlit.

It would be excellent to have the ability to monitor OSC and midi messages transmitted by resolume.I have already googled this and downloaded OSC monitor and that other one(the german dude wrote it),but they seem to only monitor the traffic received from the Ipad with TouchOSC.

Sorry If I wasnt entirely clear.

Setup:
Win7 32bit
Reso Arena 4.1.11.1.1.1.1.1.111111111 demo
quad core 2,4Ghz
4 gig ram
Ati Powercolor 6870(3 screens on mini-dp>VGAs)
Wireless USB dongle appr. 8cm away from the Ipad

[Sadler]

You seem to know enough to work this out yourself. However, you didn't mention if you were using a comp midi map or an app midi map. I think you want the app midi map if you are controlling the active clip. This raises the question as to why use midi at all when all you need is an OSC map. OSC is the future, embrace it

[zerbix]

Thanks for your reply,however ,you just earned yourself the most unhelpful/unsupportive comment award ...

If I wouldnt feel that I seriously cant solve this problem,I would 
 not  have registered and wrote a detailed explanation of where I got stuck.
I thought on a professional forum serious questions are being taken seriously.

I am fully aware of the differences between app/comp mapping,including layer/desk focus thank you.
There is a very valid reason to why OSC is not being implemented in my template,I wouldnt dive into the explanation as its irrelevant to the topic but briefly its about limited feedback options to TouchOsc(a 0 osc parameter value  lit no buttons or leds=confusion of whats on and whats not if you want to perform away from the main screen with ipad only,and you are not intended to create 8 separate pages for 8layers[even then it would be hard task to figure out which button or toggle is on if you have 6 options and none being lit,in the middle of a complicated performance with several object mapped layers visualised by several projectors)

So future or not,Im not a max msp or pd programmer yet to freely jazz a patch together for my needs,therefore I came here to kindly ask the following questions only hoping for some relevant advice or comments:

-How can I monitor osc and midi messages sent from resolume to a target device(i have tried changing ips,redirecting ip then monitoring osc as received,changing port values o the sending port in oscmonitor and that german dudes osc app to no avail)
-Why(and how) does a certain assigned parameter value "trigger" several functions at the same time ,regardless that the triggered functions are on a completely different note value or cc value or even channel or not even mapped!(As if there would be a "circuit shorting" and those triggered parameters blink and change abruptly as the very assigned control parameters values are being changed)

-Why did i feel as if only the osc control would be native to resolume and the midi is somehow  "translated" within the application.
Let me explain this a bit better.I have assigned the cue point select osc parameter to a multipush  containing six buttons.The values were 0-5 as provided in resolume.
When the template became active,without any particular reason,button 6 were lit.At this moment I had no cue points selected at all.When I pressed button nr6,nr 5 lit up,when i pressed 5 then 4,and this went on in descending order until I pressed 2,then button 1got lit,followed by pushing button1which resulted in the button being unlit.

Then changing the osc to midi note for each button would solve the problem...but only resulting in the exact very situation explained above.

Im terribly sorry if It sounds like a ridiculous unintelligible request but im seriously trying and working hard to create a template to achieve a screen free controlling option and felt quite disappointed when a senior member gave me a reality check instead of answering any of my questions.

With due respect,

Peter Farago

[Joris]

Hi Peter

I think you are not receiving a helpful reply because you are providing a lot of information, too much actually. Quite often it's hard to help someone because they post too little info. But in your case, it's hard to define what you are actually having trouble with. There are so many factors involved, it becomes hard to see the forest through the trees, so to speak.

Perhaps you could narrow it down to a few specific steps, preferably staring from a fresh comp and eliminating any factors that do not influence the problem at hand.

Example:
1. Make a new comp.
2. Clear all the App midi mappings.
3. Connect an Akai APC40.
4. Assign note shortcuts to the Cue Points in App mapping, deck focus.
5. The notes now trigger the Cue Point one down from the one that should be triggered.

This way we can easily recreate your problem, and hopefully fix it.

If you are having multiple issues, it's best to make separate threads for them, each one clearly describing the problem like above.

You can also always contact us directly at mail@resolume.com