Go Back   Cockos Incorporated Forums > REAPER Forums > MIDI Hardware, Control Surfaces, and OSC

Reply
 
Thread Tools Display Modes
Old 04-12-2020, 04:48 PM   #8241
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
Default

Quote:
Originally Posted by spkr4thdd View Post
I tried that one first. It appears to do nothing in this context? Having said that, would I have to define within the zon TrackTouch for that to work?
That's a shame. I was hoping it would work in a similar manner to:
Code:
TrackTouch+DisplayLower|     TrackVolumeDisplay
...where it switches the lower display to the fader gain from pan.

I think I'm trying to pretend TrackTouch is a modifier, when it just isn't
MixMonkey is offline   Reply With Quote
Old 04-12-2020, 09:09 PM   #8242
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

OSC Ports: Limitation

Hi Geoff, I have discovered a bit of a thorny issue with regards to OSC.

I am using Lemur for my iOS Controller app, and it is hardcoded to receive on port 8000. CSI works as expected. Until I add a second OSC device. It appears that CSI won't accept more than one outgoing stream on Port 8000 even though their IP destination is different.

I have confirmed that both devices work fine, and if I change the order in the CSI.ini file the second one always has no CSI OSC output stream.
tdc is offline   Reply With Quote
Old 04-13-2020, 12:01 AM   #8243
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

Is there a way to grab the Title of the Focused FX Plugin within the confines of the FocusedFX Navigator?

Also, found this today "TrackFolderDive" what is it and how should it be implemented?

Thanks, tdc
tdc is offline   Reply With Quote
Old 04-13-2020, 12:42 AM   #8244
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

OSC Tracking Muting oddity.

I am working through building a Selected Track Parameter page for Lemur, and have come across a weird behaviour with the Track Mute.

OST extract
Code:
Widget STN-TrackMute
	Control  /STN-TrackMute
	FB_Processor /STN-TrackMute
WidgetEnd

ZON Extract.
Code:
Zone "SelectedTrackNavigator|"
    SelectedTrackNavigator
    STN-TrackMute		TrackMute
ZoneEnd
Sending the message from Reaper to Lemur, the state of the Lemur button matches the Track Mute. But when I press the Lemur Mute, the Track acts like it is interpolating the incoming OSC values of on/off ( 0.0 and 1.0 ), and only toggles its stage on every 1.0 message. Its acting like the Action Message as a Toggle+ prefix.

I have confirmed that Reaper is receiving sequence 0.0 and 1.0 messages.

Also - just checked, Solo is performing the same

Any thoughts?

Last edited by tdc; 04-13-2020 at 12:51 AM.
tdc is offline   Reply With Quote
Old 04-13-2020, 01:22 AM   #8245
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

OSC TrackAutoMode Messages

It seems that CSI is only sending TrackAutoMode messages when the Mode is either Read [0] or TrimRead [1]

If a track is set to a mode other than those two, no message is sent.
tdc is offline   Reply With Quote
Old 04-13-2020, 01:55 AM   #8246
spkr4thdd
Human being with feelings
 
Join Date: Apr 2020
Location: Scotland
Posts: 155
Default

Quote:
Originally Posted by MixMonkey View Post
That's a shame. I was hoping it would work in a similar manner to:
Code:
TrackTouch+DisplayLower|     TrackVolumeDisplay
...where it switches the lower display to the fader gain from pan.

I think I'm trying to pretend TrackTouch is a modifier, when it just isn't
Yup, that’s what I’d hoped as well. It seems not.

Geoff, is their any way to send CC/ASCII messages and values on button presses?
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
spkr4thdd is offline   Reply With Quote
Old 04-13-2020, 02:00 AM   #8247
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

OSC TrackOutputMeter

It appears like the TrackOutputMeter action is a little odd too. Firstly the scaling seems low (Though I have a feeling that this is related to your preferences in Reaper). I thought that the OSC meter output was a tap from the visible meter settings in the MCP, but the OSC data is lower than that.

However, it sees like all three Actions use the same data, as they don't change values as you would expect for differing test signal.
TrackOutputMeter
TrackOutputMeterAverageLR
TrackOutputMeterMaxPeakLR


The other issue is a subtle one and is probably in the hands of Cockos, but the OSC VU stream fluctuates even on a steady test signal. I have posted a bug report about this a while ago, but here it is just in case this is something CSI can resolve?

I am designing a control surface based on OSC and am finding the VU values being sent out are behaving oddly. Despite being steady in Reaper ( tone generator set to a fixed value) the OSC Values for the given meter oscillate.

In this example, if I set the tone generator to 1kHz @ -18dB FS, Sine. the MCP shows a steady Meter at -18, but the OSC data being output fluctuates between two values. [0.6257 and 0.6461]

I have tried various update rates of meters in the OSC settings preferences pane, and different tone frequencies and waveform shapes. All result in this strange fluctuating OSC message.

Interesting the amount that the OSC messages fluctuate by remains constant regardless of the set value. Its always [0.0204].

Any thoughts? Am I being a goose?

Attached is a graph of the messages.
tdc is offline   Reply With Quote
Old 04-13-2020, 02:16 AM   #8248
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by Funkybot View Post
But there was a slight regression: if I open a new Reaper Eucon works fine with the first project. But if I then open another project in Reaper, Eucon does not update to reflect the newest project. The faders/scribble strips will blank out, and not come back up for the new project. I have to run "Restart All Eucon Applications" to get it to pick back up.
Thanks, will check it out.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 02:18 AM   #8249
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by tdc View Post
Few fun things:

Found a better way to arbitrarily colour encoders now , I call it the NoGoZone method.(Colour format is for the MFT, but you could change the to your controllers method I suspect, or just leave the colour out and use this to create a blocking widget.

Code:
Press2 GoZone "NoGoZone" { 0 0 0 0 0 0 }  // NoGoZone Black
By not specifying a zone to go to with a GoZone Action, we can add a colour and also ensure it won't action anything. This is also good for creating Null widgets to either reset or cover prior assignments when switching zones or resolving the current issues with the naughty navigators.

- - - -

Here is a hack to take you from either a SelectedTrackNavigator or FocusedFXNavigator, and ensure the overlain temporary zone is pushed off the stack to gracefully return to Home. This is a temporary UX fix for Reaper's inconsistent reporting to CSI that a track has been left.

Key to this solution is to have all encoders / switches do something in each zone. Messy, and potentially laborious to add to your existing setup but straightforward when starting from scratch. In this example, I have a Rotary Encoder / Press Switch 13 assigned to the HPF Frequency of ReaEQ. When I select a track the MFTwister the FX window is floated and the Encoder turns Yellow and displays the parameter value of the HPF.

I am using the NoGoZone trick here to set the colour of the LED, whilst the standard widget to action assignment is mapping the HPF Param.
Code:
Press13         GoZone "NoGoZone" { 242 255 0 242 255 0 }  // Yellow
Rotary13        FXParam "0" 	"HPF Freq" // HPF Frequency
If I was to now select another track that had no FX instantiated, or perhaps another zone that had Encoder 13 not being used, this encoder's parameter and colour would still be displayed due to the naughty navigator bug. So, we add the following to our Home Zone, and other FX Zones. This will zero out the encoder parameter value, and also reset the colour to our chosen black on the home zone.

Code:
Rotary13 FXParam “999” // Zero Out Encoder Display
Press13	 GoZone "NoGoZone" { 0 0 0 0 0 0 } // NoGoZone Black
Lastly, on each FX Modal Zone we can have a button to return us to the Home Zone without needing to manually unselect or change tracks.

Code:
Press2  Reaper "_S&M_WNCLS5" // Hide All Floating FX for Selected Track
Press2. Reaper "40297"   // Unselect All Tracks  
Press2  GoZone "Home"
- - - -

I must caveat all this, as its a temporary hack that may cause issues, but it has been working all evening here and feels really clean when operating so I thought I would share.

[Edited to include "999" into FXParam.]
There ya' go !

REAL nice man
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 02:20 AM   #8250
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by tdc View Post
OSC Ports: Limitation

Hi Geoff, I have discovered a bit of a thorny issue with regards to OSC.

I am using Lemur for my iOS Controller app, and it is hardcoded to receive on port 8000. CSI works as expected. Until I add a second OSC device. It appears that CSI won't accept more than one outgoing stream on Port 8000 even though their IP destination is different.

I have confirmed that both devices work fine, and if I change the order in the CSI.ini file the second one always has no CSI OSC output stream.
Hmmm...

Haven't touched OSC in a while, but looked at my CSI.ini and the phone and tablet use different ports, maybe had to do that, will check into it, thanks.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 02:25 AM   #8251
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by tdc View Post
Is there a way to grab the Title of the Focused FX Plugin within the confines of the FocusedFX Navigator?
Not right now, use case ?

Quote:
Originally Posted by tdc View Post
Also, found this today "TrackFolderDive" what is it and how should it be implemented?
Oops, that was an old prototype idea that got dumped when we came up with the current folder implementation. Where did you see it ?
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 02:34 AM   #8252
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by tdc View Post
OSC Tracking Muting oddity.

I am working through building a Selected Track Parameter page for Lemur, and have come across a weird behaviour with the Track Mute.

OST extract
Code:
Widget STN-TrackMute
	Control  /STN-TrackMute
	FB_Processor /STN-TrackMute
WidgetEnd

ZON Extract.
Code:
Zone "SelectedTrackNavigator|"
    SelectedTrackNavigator
    STN-TrackMute		TrackMute
ZoneEnd
Sending the message from Reaper to Lemur, the state of the Lemur button matches the Track Mute. But when I press the Lemur Mute, the Track acts like it is interpolating the incoming OSC values of on/off ( 0.0 and 1.0 ), and only toggles its stage on every 1.0 message. Its acting like the Action Message as a Toggle+ prefix.

I have confirmed that Reaper is receiving sequence 0.0 and 1.0 messages.

Also - just checked, Solo is performing the same

Any thoughts?
By design.

We went through a whole phase of the design/coding, where some surfaces:
Sent a 1 only
Sent a 1 on press and a 0 on release
Held internal state (grrrr CSI doesn't like surfaces doing that -- let CSI take care of that) and sent a 1 on first press and a 0 on second press.

Having to deal with that led to leaving it up to the actions to decide how to handle Press.

The feedback processing is there to provide the surface with the current state, and indeed should be the ONLY source of current state. That way, if some one mouse clicks Mute, things stay in synch.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 02:35 AM   #8253
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by tdc View Post
OSC TrackAutoMode Messages

It seems that CSI is only sending TrackAutoMode messages when the Mode is either Read [0] or TrimRead [1]

If a track is set to a mode other than those two, no message is sent.
Wow, that seems strange, will investigate.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 02:43 AM   #8254
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by tdc View Post
OSC TrackOutputMeter
However, it sees like all three Actions use the same data, as they don't change values as you would expect for differing test signal.
TrackOutputMeter
TrackOutputMeterAverageLR
TrackOutputMeterMaxPeakLR
Are you using a stereo test signal with different values for L/R ?

Quote:
Originally Posted by tdc View Post
I am designing a control surface based on OSC
Cool !!

Quote:
Originally Posted by tdc View Post
[B]
In this example, if I set the tone generator to 1kHz @ -18dB FS, Sine. the MCP shows a steady Meter at -18, but the OSC data being output fluctuates between two values. [0.6257 and 0.6461]

I have tried various update rates of meters in the OSC settings preferences pane, and different tone frequencies and waveform shapes. All result in this strange fluctuating OSC message.

Interesting the amount that the OSC messages fluctuate by remains constant regardless of the set value. Its always [0.0204].

Any thoughts? Am I being a goose?

Attached is a graph of the messages.
Hmmm...

Well, for a quick solution for your surface design, I would just smooth the data, all the numbers you need to do the math, you presented above

As far as why, I have no idea
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 03:42 AM   #8255
WaveTrans
Human being with feelings
 
Join Date: Aug 2019
Location: Forest City
Posts: 336
Default

Quote:
Originally Posted by Mike@Ossarium View Post
I have made the test.

Shit ... when i hide the track before my track with the Fx i got the same problems like you. :-(
After unhideing the track everything will be back ok.

I think then i will switch to the FXMenu approach...
Thanks a lot.

At least this means it isn´t my surfaces or me

I guess Geoff has to sort this out.

Before I re-arrange all of my projects, I´ll have a go on the FXmenu alternative as well.

Thanks again for testing.
WaveTrans is offline   Reply With Quote
Old 04-13-2020, 05:00 AM   #8256
Mike@Ossarium
Human being with feelings
 
Mike@Ossarium's Avatar
 
Join Date: Nov 2012
Location: Munich, Germany
Posts: 111
Default

Quote:
Originally Posted by Mike@Ossarium View Post
Is there a way to do the FX in the master channel the same way like for the normal tracks with the FXMenu?
I already tried

Code:
SomeButton Reaper _SWS_TOGSELMASTER
but it won't work like when i am selecting the Master track with the mouse.

Ok - i figured out that

Code:
	SomeButton   Reaper	"40297"				// Track: Unselect all tracks
	SomeButton   Reaper	"_SWS_TOGSELMASTER"		// SWS: Toggle master track select
did a good job.
Question 1: Is it allowed to execute multiple actions for the same button?
Question 2: The LED for SomeButton don't reflect the actual status of the master channel. It's always on. Any ideas why?

Cheers,
Mike
__________________
Reaper Version: 6.18 with CSI 1.0 and SWS / Audio Interface: Behringer FCA1616 + ADA8000
Band: Ossarium / Last Project: http://ossarium.bandcamp.com/ (Recorded and Mixed with Reaper)

Last edited by Mike@Ossarium; 04-13-2020 at 05:25 AM.
Mike@Ossarium is offline   Reply With Quote
Old 04-13-2020, 05:10 AM   #8257
Mike@Ossarium
Human being with feelings
 
Mike@Ossarium's Avatar
 
Join Date: Nov 2012
Location: Munich, Germany
Posts: 111
Default

Is there a way to turn on/off a LED when i step in/out of a zone?

Quote:
Originally Posted by Geoff Waddington View Post
Not right now, but great idea !
Any news on that? Would be very helpfull in a lot of cases :-)

Cheers,
Mike
__________________
Reaper Version: 6.18 with CSI 1.0 and SWS / Audio Interface: Behringer FCA1616 + ADA8000
Band: Ossarium / Last Project: http://ossarium.bandcamp.com/ (Recorded and Mixed with Reaper)
Mike@Ossarium is offline   Reply With Quote
Old 04-13-2020, 06:44 AM   #8258
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

Quote:
Originally Posted by Mike@Ossarium View Post
Is there a way to turn on/off a LED when i step in/out of a zone?
Any news on that? Would be very helpfull in a lot of cases :-)
Hey Mike, I resolved this today with a bit of a boot-strapped method, but its working well at present.

Check out at the top of top of this page, a post called "Few fun things:" Here is my current Zone file for the FX ReaEQ. Its formatted for my MidiFighter Twister, but shows the additional entries for blanking out unused rotary encoders and also how I colour things.

VST__ReaEQ.zon.zip

Last edited by tdc; 04-13-2020 at 06:53 AM.
tdc is offline   Reply With Quote
Old 04-13-2020, 07:47 AM   #8259
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

Quote:
Originally Posted by Geoff Waddington View Post
Not right now, use case ?
UX clarification primarily. Having a tablet being a Super Channel is aided by having the name of the plugin and the instance number. Stops you having to check on the screen all the time.

Quote:
Originally Posted by Geoff Waddington View Post
Oops, that was an old prototype idea that got dumped when we came up with the current folder implementation. Where did you see it ?
It was in one of the ZON's in the examples, or maybe one of the other CSI groovers I have downloaded and stashed. Thanks for the clarification.

Edit: Its also on the Zone Wiki Page. (I wish I knew enough to offer to assist with the Wiki. Soon )
https://github.com/malcolmgroves/rea...changing-zones

Last edited by tdc; 04-13-2020 at 08:12 AM.
tdc is offline   Reply With Quote
Old 04-13-2020, 07:50 AM   #8260
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

Quote:
Originally Posted by Geoff Waddington View Post
By design.

We went through a whole phase of the design/coding, where some surfaces:
Sent a 1 only
Sent a 1 on press and a 0 on release
Held internal state (grrrr CSI doesn't like surfaces doing that -- let CSI take care of that) and sent a 1 on first press and a 0 on second press.
:-) I can imagine it was a long debate. Thanks for letting me know that this is indeed working fine, I can code around it.
tdc is offline   Reply With Quote
Old 04-13-2020, 07:52 AM   #8261
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

Quote:
Originally Posted by Geoff Waddington View Post
Are you using a stereo test signal with different values for L/R ?
Yes, set up a proper test chain to ensure the feedback here was accurate.

Quote:
Originally Posted by Geoff Waddington View Post
well, for a quick solution for your surface design, I would just smooth the data, all the numbers you need to do the math, you presented above

As far as why, I have no idea
:-) I had already built a simple LP smoother in Lemur to make the meter look calmer, until I discovered there is something odd with the OSC data itself. I have written to the Cockoteers a few times, so we shall see.

Thanks Geoff.
tdc is offline   Reply With Quote
Old 04-13-2020, 09:18 AM   #8262
Mike@Ossarium
Human being with feelings
 
Mike@Ossarium's Avatar
 
Join Date: Nov 2012
Location: Munich, Germany
Posts: 111
Default

Quote:
Originally Posted by tdc View Post
Hey Mike, I resolved this today with a bit of a boot-strapped method, but its working well at present.

Check out at the top of top of this page, a post called "Few fun things:" Here is my current Zone file for the FX ReaEQ. Its formatted for my MidiFighter Twister, but shows the additional entries for blanking out unused rotary encoders and also how I colour things.

Attachment 40106
Hey Tony,

thanks for the zon file.
Could you explain what happened between the {} ?

I want to turn of and off the follwign LED when entering or leavon a zone.

Code:
Widget ZoomLedOn
	FB_TwoState 90 64 7f 90 64 7f
WidgetEnd

Widget ZoomLedOff
	FB_TwoState 90 64 00 90 64 00
WidgetEnd
There two widgets are fake!! Inly for understanding.
__________________
Reaper Version: 6.18 with CSI 1.0 and SWS / Audio Interface: Behringer FCA1616 + ADA8000
Band: Ossarium / Last Project: http://ossarium.bandcamp.com/ (Recorded and Mixed with Reaper)
Mike@Ossarium is offline   Reply With Quote
Old 04-13-2020, 09:24 AM   #8263
Mike@Ossarium
Human being with feelings
 
Mike@Ossarium's Avatar
 
Join Date: Nov 2012
Location: Munich, Germany
Posts: 111
Default

Hi Tony,

could you also explain why "Press2." have a dot? Is it a different widget?
Or some hidden feature :-)

Code:
Press2  Reaper "_S&M_WNCLS5" // Hide All Floating FX for Selected Track
Press2. Reaper "40297"   // Unselect All Tracks  
Press2  GoZone "Home"
I also wasn't aware that it is allowed to call multiple actions for the same button :-)
__________________
Reaper Version: 6.18 with CSI 1.0 and SWS / Audio Interface: Behringer FCA1616 + ADA8000
Band: Ossarium / Last Project: http://ossarium.bandcamp.com/ (Recorded and Mixed with Reaper)
Mike@Ossarium is offline   Reply With Quote
Old 04-13-2020, 10:17 AM   #8264
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
Default

Hi Geoff, not a high priority at all but it would be amazing if CSI could be made to communicate with the displays of the Novation RemoteZero SL. The MK 1 device had two glorious displays. If I could make that a plugin box with FXParam names that'd be insanely great for me. It's such a legacy device though (and not sure if there's enough available info in how it's spec'd out) that I'd understand if it's just not possible.

Found the manual here:

https://resource.novationmusic.com/s...english106.pdf

I'd kill for a modern take on it with better encoders and faders but with the customizable displays.
Funkybot is offline   Reply With Quote
Old 04-13-2020, 10:23 AM   #8265
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

Strange MIDI output in CSI Console

Hi Geoff,

Just saw this pouring out of the CSI Console, and wondered what it was and whether it was due to my cavalier approach to the recent hacking. Interestingly I can't see these messages in my Midi monitors going to the MidiFighter Twister.

Code:
OUT -> MFTwister b4  0f  ffffff81 
OUT -> MFTwister b0  01  ffffff81 
OUT -> MFTwister b0  02  ffffff81 
OUT -> MFTwister b0  0a  ffffff81 
OUT -> MFTwister b0  0c  fffffffb 
OUT -> MFTwister b0  0d  ffffff81 
OUT -> MFTwister b0  0e  ffffff81 
OUT -> MFTwister b4  00  ffffff81 
OUT -> MFTwister b4  01  ffffff81 
OUT -> MFTwister b4  02  ffffff81 
OUT -> MFTwister b4  03  ffffff81 
OUT -> MFTwister b4  04  ffffff81 
OUT -> MFTwister b4  05  ffffff81 
OUT -> MFTwister b4  06  ffffff81 
OUT -> MFTwister b4  07  ffffff81 
OUT -> MFTwister b4  08  ffffff81 
OUT -> MFTwister b4  09  ffffff81 
OUT -> MFTwister b4  0a  ffffff81 
OUT -> MFTwister b4  0b  ffffff81 
OUT -> MFTwister b4  0c  ffffff81 
OUT -> MFTwister b4  0d  ffffff81 
OUT -> MFTwister b4  0e  ffffff81 
OUT -> MFTwister b4  0f  ffffff81
tdc is offline   Reply With Quote
Old 04-13-2020, 10:47 AM   #8266
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

Quote:
Originally Posted by Mike@Ossarium View Post
Hey Tony,

thanks for the zon file.
Could you explain what happened between the {} ?
Hi Mike,

The 6 numbers inside the { } brackets are the way we change the LED's on the Midi Fighter Twister. Unless you have one of these that code isn't going to do anything, but you would simply add in your controllers Colour message I suspect.

The main point of the file was that we could blank out areas of the controller to make up for the Focus and Track Selected Navigators not being reliable disposing of an overlain Zone (such as FX).
tdc is offline   Reply With Quote
Old 04-13-2020, 10:52 AM   #8267
tdc
Human being with feelings
 
Join Date: Oct 2019
Location: Sydney
Posts: 471
Default

Quote:
Originally Posted by Mike@Ossarium View Post
Hi Tony,

could you also explain why "Press2." have a dot? Is it a different widget?
Or some hidden feature :-)
I would put that down to it being 3am here :-) Sloppy of me, sorry.

Quote:
Originally Posted by Mike@Ossarium View Post
I also wasn't aware that it is allowed to call multiple actions for the same button :-)
This however is completely fine! And is very powerful.

Here is a button on one of my controllers that is performing a GoZone home with some cleanup.

Quote:
Press1 Reaper "_S&M_WNCLS5" { 0 255 0 0 255 0 } // Close all float FX for Selected Track // Colour Green
Press1 Reaper "40297" // Unselect All Tracks // Green
Press1 Reaper "_S&M_WNMAIN" // Set Focus to Main Window.
Press1 GoZone "Home"
tdc is offline   Reply With Quote
Old 04-13-2020, 01:32 PM   #8268
spkr4thdd
Human being with feelings
 
Join Date: Apr 2020
Location: Scotland
Posts: 155
Default Display line parameters...

Hopefully this will be something quick and easy for people to answer...

What are the parameters available to call for the upper and lower MCU channel displays?

I understand this (and it works) in the default Channel| template:
Code:
	DisplayUpper|  			TrackNameDisplay
	DisplayLower| 			TrackPanDisplay
	TrackTouch+DisplayLower| 	TrackVolumeDisplay
	...
	FaderTouch|  			TrackTouch
But I've no idea how to get that same thing happening in a non template zone? i.e. a selected channel specific zone, not a 1-8 zone.


And I've kind of got it in FXZone files...
Code:
	DisplayUpper1		FXParamNameDisplay "0" "HPF"
	DisplayLower1		FXParamValueDisplay 0
(Although I have to admit I bastardised someone esle's file (Thanks Mike!) so have no idea what the specific bits of those commands do...).

But I really don't know what I can call/how I call it for those displays?

How do I just write some plain ol' text in a specific DisplayUpper or DisplayLower?
How do I tell CSI to post the value of a specific channel's volume or pan to a specific display (NOT the one related to the channel itself)?I've tried syntax like:

Code:
DisplayLower2    TrackVolumeDisplay4
But that fails gloriously...

Any help would definitely save my sanity!

I know there's also a way with the MCU displays for it to 'flash' a message across the combined displays for a specific time before showing the individual displays, like "FX Menu Mode" or "Channel View". Is there any way to do that? (I'll get to the Name/Display' digits later )
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
spkr4thdd is offline   Reply With Quote
Old 04-13-2020, 02:29 PM   #8269
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by Funkybot View Post
Hi Geoff, not a high priority at all but it would be amazing if CSI could be made to communicate with the displays of the Novation RemoteZero SL. The MK 1 device had two glorious displays. If I could make that a plugin box with FXParam names that'd be insanely great for me. It's such a legacy device though (and not sure if there's enough available info in how it's spec'd out) that I'd understand if it's just not possible.

Found the manual here:

https://resource.novationmusic.com/s...english106.pdf

I'd kill for a modern take on it with better encoders and faders but with the customizable displays.
Has a VERY cursory glance, didn't see an obvious way, that doesn't mean it's impossible...
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 02:33 PM   #8270
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by tdc View Post
Strange MIDI output in CSI Console

Hi Geoff,

Just saw this pouring out of the CSI Console, and wondered what it was and whether it was due to my cavalier approach to the recent hacking. Interestingly I can't see these messages in my Midi monitors going to the MidiFighter Twister.

Code:
OUT -> MFTwister b4  0f  ffffff81 
OUT -> MFTwister b0  01  ffffff81 
OUT -> MFTwister b0  02  ffffff81 
OUT -> MFTwister b0  0a  ffffff81 
OUT -> MFTwister b0  0c  fffffffb 
OUT -> MFTwister b0  0d  ffffff81 
OUT -> MFTwister b0  0e  ffffff81 
OUT -> MFTwister b4  00  ffffff81 
OUT -> MFTwister b4  01  ffffff81 
OUT -> MFTwister b4  02  ffffff81 
OUT -> MFTwister b4  03  ffffff81 
OUT -> MFTwister b4  04  ffffff81 
OUT -> MFTwister b4  05  ffffff81 
OUT -> MFTwister b4  06  ffffff81 
OUT -> MFTwister b4  07  ffffff81 
OUT -> MFTwister b4  08  ffffff81 
OUT -> MFTwister b4  09  ffffff81 
OUT -> MFTwister b4  0a  ffffff81 
OUT -> MFTwister b4  0b  ffffff81 
OUT -> MFTwister b4  0c  ffffff81 
OUT -> MFTwister b4  0d  ffffff81 
OUT -> MFTwister b4  0e  ffffff81 
OUT -> MFTwister b4  0f  ffffff81
Can you please check which Widgets those are (b0 01, b4 01, etc.) and which actions they are mapped to at the time of the capture?

I'll look at adding all that info to the output so that it's easier to diagnose.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 02:34 PM   #8271
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by tdc View Post
Hi Mike,

The 6 numbers inside the { } brackets are the way we change the LED's on the Midi Fighter Twister. Unless you have one of these that code isn't going to do anything, but you would simply add in your controllers Colour message I suspect.

The main point of the file was that we could blank out areas of the controller to make up for the Focus and Track Selected Navigators not being reliable disposing of an overlain Zone (such as FX).
Actually those numbers are RGB and any Widget that supports RGB should work.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 02:41 PM   #8272
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by spkr4thdd View Post
Hopefully this will be something quick and easy for people to answer...

What are the parameters available to call for the upper and lower MCU channel displays?

I understand this (and it works) in the default Channel| template:
Code:
	DisplayUpper|  			TrackNameDisplay
	DisplayLower| 			TrackPanDisplay
	TrackTouch+DisplayLower| 	TrackVolumeDisplay
	...
	FaderTouch|  			TrackTouch
But I've no idea how to get that same thing happening in a non template zone? i.e. a selected channel specific zone, not a 1-8 zone.


And I've kind of got it in FXZone files...
Code:
	DisplayUpper1		FXParamNameDisplay "0" "HPF"
	DisplayLower1		FXParamValueDisplay 0
(Although I have to admit I bastardised someone esle's file (Thanks Mike!) so have no idea what the specific bits of those commands do...).

But I really don't know what I can call/how I call it for those displays?

How do I just write some plain ol' text in a specific DisplayUpper or DisplayLower?
How do I tell CSI to post the value of a specific channel's volume or pan to a specific display (NOT the one related to the channel itself)?I've tried syntax like:

Code:
DisplayLower2    TrackVolumeDisplay4
But that fails gloriously...

Any help would definitely save my sanity!
TrackVolumeDisplay4 isn't a thing

TrackVolumeDisplay is.

But which Track ?

That's where navigators come in, you are going to need one:

https://github.com/malcolmgroves/rea...iki/Navigators
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 02:47 PM   #8273
Mike@Ossarium
Human being with feelings
 
Mike@Ossarium's Avatar
 
Join Date: Nov 2012
Location: Munich, Germany
Posts: 111
Default

Quote:
Originally Posted by Mike@Ossarium View Post
Hi.
I have the following in my zon file:

Code:
Click Reaper "40364" // Options: Toggle metronome
Hold+Click Reaper "40363" // Options: Show metronome/pre-roll settings
Everytime i press click (short) the metronome settings window show up and sometimes dissapear after 1 second. When i remove the Hold+Click part everything works fine.

Can somebody check this behavior?

Cheers,
Mike

I've checked again and this Hold behavior is driving me crazy.

I have definde the following widget:
Code:
Widget Click
	Press 90 59 7f
	FB_TwoState 90 59 7f 90 59 00
WidgetEnd
and in my zon file is:
Code:
Click 		Reaper	"40364"		// Options: Toggle metronome
Hold+Click	Reaper 	"40363"		// Options: Show metronome/pre-roll settings
The behavior is arbitrary. Some times the metronome settings window appear and stays and sometimes it disappears at short button presses.
When i hold the button longer sometimes everythins is ok and sometimes nothing happends.....

When i remove the Hold action the standard button action performes as ecpected.

Is there any way i can debug that?

MidiOx shows the correct behavior.

Cheers,
Mike
__________________
Reaper Version: 6.18 with CSI 1.0 and SWS / Audio Interface: Behringer FCA1616 + ADA8000
Band: Ossarium / Last Project: http://ossarium.bandcamp.com/ (Recorded and Mixed with Reaper)
Mike@Ossarium is offline   Reply With Quote
Old 04-13-2020, 02:49 PM   #8274
spkr4thdd
Human being with feelings
 
Join Date: Apr 2020
Location: Scotland
Posts: 155
Default

Quote:
Originally Posted by Mike@Ossarium View Post
Hey Tony,

thanks for the zon file.
Could you explain what happened between the {} ?

I want to turn of and off the follwign LED when entering or leavon a zone.

Code:
Widget ZoomLedOn
	FB_TwoState 90 64 7f 90 64 7f
WidgetEnd

Widget ZoomLedOff
	FB_TwoState 90 64 00 90 64 00
WidgetEnd
There two widgets are fake!! Inly for understanding.
Mike, I'm working on CSI for the X-Touch as well and this is driving me crazy.

For some buttons, if I define the widget in any zone, the LED lights up and stays lit. (Up, Down, Left, Right buttons). This also appears to toggle anything related to the widget as 'On' by default, which is really annoying.

For some, even if I define the widget it simply refuses to light up when pressed or at any point. (Zoom, Scrub, Bank/Channel left/right).

And then, with the Shift button, if I press it then anything which has a 'Shift+" modifier attached to it lights up as long as Shift is pressed... (actually that's quite helpful at times).

I'm desperately trying to work out how to 'force' a widget's state to off, but as Geoff mentioned many posts ago this appears tied to there being a 'state' related to the action in Reaper (and I'm damned if I'm creating a custom action for every button!)

If I find some golden chalice I'll let you know, but I'm not holding out much hope.
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
spkr4thdd is offline   Reply With Quote
Old 04-13-2020, 02:57 PM   #8275
spkr4thdd
Human being with feelings
 
Join Date: Apr 2020
Location: Scotland
Posts: 155
Default

Quote:
Originally Posted by Mike@Ossarium View Post
I've checked again and this Hold behavior is driving me crazy.

I have definde the following widget:
Code:
Widget Click
	Press 90 59 7f
	FB_TwoState 90 59 7f 90 59 00
WidgetEnd
and in my zon file is:
Code:
Click 		Reaper	"40364"		// Options: Toggle metronome
Hold+Click	Reaper 	"40363"		// Options: Show metronome/pre-roll settings
Mike, I have Click set up the same as you in my mst.

In my zon file I was using Click to toggle metronome like you, and Shift+Click to show metronome settings. I've just added your second zon line to my zon file and it works fine...

Tap the 'Click' button, metronome toggles on/off.
Press and hold the 'Click button, the metronome settings appear. They don't toggle though so it has to be closed by mouse click.
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
spkr4thdd is offline   Reply With Quote
Old 04-13-2020, 03:01 PM   #8276
Mike@Ossarium
Human being with feelings
 
Mike@Ossarium's Avatar
 
Join Date: Nov 2012
Location: Munich, Germany
Posts: 111
Default

Quote:
Originally Posted by spkr4thdd View Post
Mike, I have Click set up the same as you in my mst.

In my zon file I was using Click to toggle metronome like you, and Shift+Click to show metronome settings. I've just added your second zon line to my zon file and it works fine...

Tap the 'Click' button, metronome toggles on/off.
Press and hold the 'Click button, the metronome settings appear. They don't toggle though so it has to be closed by mouse click.
Thanks for testing.
This is really strange. :-(

I am not the only one who has this problem, but i am glad that its ok on your side.
__________________
Reaper Version: 6.18 with CSI 1.0 and SWS / Audio Interface: Behringer FCA1616 + ADA8000
Band: Ossarium / Last Project: http://ossarium.bandcamp.com/ (Recorded and Mixed with Reaper)
Mike@Ossarium is offline   Reply With Quote
Old 04-13-2020, 03:02 PM   #8277
Cragster
Human being with feelings
 
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
Default

Quote:
Originally Posted by spkr4thdd View Post
Hopefully this will be something quick and easy for people to answer...

What are the parameters available to call for the upper and lower MCU channel displays?

I understand this (and it works) in the default Channel| template:
Code:
	DisplayUpper|  			TrackNameDisplay
	DisplayLower| 			TrackPanDisplay
	TrackTouch+DisplayLower| 	TrackVolumeDisplay
	...
	FaderTouch|  			TrackTouch
But I've no idea how to get that same thing happening in a non template zone? i.e. a selected channel specific zone, not a 1-8 zone.


And I've kind of got it in FXZone files...
Code:
	DisplayUpper1		FXParamNameDisplay "0" "HPF"
	DisplayLower1		FXParamValueDisplay 0
(Although I have to admit I bastardised someone esle's file (Thanks Mike!) so have no idea what the specific bits of those commands do...).

But I really don't know what I can call/how I call it for those displays?

How do I just write some plain ol' text in a specific DisplayUpper or DisplayLower?
How do I tell CSI to post the value of a specific channel's volume or pan to a specific display (NOT the one related to the channel itself)?I've tried syntax like:

Code:
DisplayLower2    TrackVolumeDisplay4
But that fails gloriously...

Any help would definitely save my sanity!

I know there's also a way with the MCU displays for it to 'flash' a message across the combined displays for a specific time before showing the individual displays, like "FX Menu Mode" or "Channel View". Is there any way to do that? (I'll get to the Name/Display' digits later )
I dont know if this will work . But in an fx zone FXParamNameDisplay takes control of the display. You can type anything you want in there. I use it all the time with a dummy param number. So if i have an open track display in my fx zone ill put DisplayUpperwhatevertracknumber FXParamNameDisplay 1(dummy param number) and then wgat i want in the display wrapped in quotes. I use it for say "shift" on the upper and "mode" on the lower. Just a trick because my modifier buttons dont stay lit and it keeps me from being lost. Maybe it will work in a regular zone ?? Worth a try
Cragster is offline   Reply With Quote
Old 04-13-2020, 03:04 PM   #8278
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
Default

Quote:
Originally Posted by Mike@Ossarium View Post
I've checked again and this Hold behavior is driving me crazy.

I have definde the following widget:
Code:
Widget Click
	Press 90 59 7f
	FB_TwoState 90 59 7f 90 59 00
WidgetEnd
and in my zon file is:
Code:
Click 		Reaper	"40364"		// Options: Toggle metronome
Hold+Click	Reaper 	"40363"		// Options: Show metronome/pre-roll settings
The behavior is arbitrary. Some times the metronome settings window appear and stays and sometimes it disappears at short button presses.
When i hold the button longer sometimes everythins is ok and sometimes nothing happends.....

When i remove the Hold action the standard button action performes as ecpected.

Is there any way i can debug that?

MidiOx shows the correct behavior.

Cheers,
Mike
If you think about it, one important thing Hold needs is a release message.

That way, if you just tap it, the Hold action doesn't occur.

It's waiting, ready to go, but it's hopes are dashed when it receives that release message before it has a chance to trigger the Action.

Then it just resets the timer and waits again patiently

You need something like this:

Code:
Widget Click
	Press 90 59 7f 90 59 00
	FB_TwoState 90 59 7f 90 59 00
WidgetEnd
AND the widget actually has to generate the release - use input monitor to be sure.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 04-13-2020, 03:05 PM   #8279
Mike@Ossarium
Human being with feelings
 
Mike@Ossarium's Avatar
 
Join Date: Nov 2012
Location: Munich, Germany
Posts: 111
Default

Quote:
Originally Posted by spkr4thdd View Post
Mike, I'm working on CSI for the X-Touch as well and this is driving me crazy.

For some buttons, if I define the widget in any zone, the LED lights up and stays lit. (Up, Down, Left, Right buttons). This also appears to toggle anything related to the widget as 'On' by default, which is really annoying.

For some, even if I define the widget it simply refuses to light up when pressed or at any point. (Zoom, Scrub, Bank/Channel left/right).

And then, with the Shift button, if I press it then anything which has a 'Shift+" modifier attached to it lights up as long as Shift is pressed... (actually that's quite helpful at times).

I'm desperately trying to work out how to 'force' a widget's state to off, but as Geoff mentioned many posts ago this appears tied to there being a 'state' related to the action in Reaper (and I'm damned if I'm creating a custom action for every button!)

If I find some golden chalice I'll let you know, but I'm not holding out much hope.
Hi Grae,

you can't force a state of a widget. It strongly linked to the state of reaper.

For the zoom button for example there is nothing you can link to so its off all the time. Thatswhy i ask for the possibllity to turn on/off an LED when a
Zone is entered or leaved.

If you like to discuss some things related to the X-touch you can write me an email if youi like.

Cheers, Mike
__________________
Reaper Version: 6.18 with CSI 1.0 and SWS / Audio Interface: Behringer FCA1616 + ADA8000
Band: Ossarium / Last Project: http://ossarium.bandcamp.com/ (Recorded and Mixed with Reaper)
Mike@Ossarium is offline   Reply With Quote
Old 04-13-2020, 03:09 PM   #8280
spkr4thdd
Human being with feelings
 
Join Date: Apr 2020
Location: Scotland
Posts: 155
Default

Quote:
Originally Posted by Geoff Waddington View Post
TrackVolumeDisplay4 isn't a thing

TrackVolumeDisplay is.

But which Track ?

That's where navigators come in, you are going to need one:

https://github.com/malcolmgroves/rea...iki/Navigators
Geoff, thanks for the quick response. I got there with the volume/pan display in the lower display.

How can a 'force' text in to a display? For example if I want it to read "Volume" or "FX Slot 1"?

Code:
DisplayUpper1     "Volume"
doesn't work...

Can you enter text to be shown on the display rather than a parameter passed by Reaper?
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
spkr4thdd is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 04:05 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.