Control Surface Integration (CSI) Technical Feature Discussion - Page 82

MixMonkey · 06-26-2019, 05:18 PM

Quote:

Originally Posted by Geoff Waddington

Yes, if you don't have TrackSelection or FocusFX involved, you should be able to uncheck Synch Zones Across Surfaces on the C4.

Ah, I see. It's the TrackSelection that prevents this from working.

I was just trying to get the send splay on the MCU separate from the C4, so that if it was triggered (ToggleShouldMapSends) on the C4, it would splay on the C4 but not on the MCU (and vice versa)

Most of the time I'd be happy with sends on rotaries on the C4, keeping out of the way of channels on the MCU. But for FX rides to automation, you have to have faders, not least for the touch sensitivity.

If the MCU is going to splay the sends onto faders all the time or not at all, I'll probably go with all the time and forget about the C4 for sends.

The other thought I had (actually before the whole send thing was working) was to dedicate an XT to sends permanently and just let it follow the track selection. Had the same thought about VCA masters...

Like I said before, that's the trouble with CSI- too many darn possibilities

Geoff Waddington · 06-26-2019, 05:36 PM

Quote:

Originally Posted by MixMonkey

Ah, I see. It's the TrackSelection that prevents this from working.

I was just trying to get the send splay on the MCU separate from the C4, so that if it was triggered (ToggleShouldMapSends) on the C4, it would splay on the C4 but not on the MCU (and vice versa)

Most of the time I'd be happy with sends on rotaries on the C4, keeping out of the way of channels on the MCU. But for FX rides to automation, you have to have faders, not least for the touch sensitivity.

If the MCU is going to splay the sends onto faders all the time or not at all, I'll probably go with all the time and forget about the C4 for sends.

You should be able to uncheck Synch Zones Across Surfaces on the C4 and the MCU and using GoZone and GoSubZone instead of ToggleShouldMapSends, I think that should work.

ToggleShouldMapSends is a global thing like TrackSelection and FXFocus.

Quote:

Originally Posted by MixMonkey

The other thought I had (actually before the whole send thing was working) was to dedicate an XT to sends permanently and just let it follow the track selection. Had the same thought about VCA masters...

Like I said before, that's the trouble with CSI- too many darn possibilities

Well, now we're talkin' Pages, don't forget about them

MixMonkey · 06-26-2019, 05:43 PM

Quote:

Originally Posted by Geoff Waddington

You should be able to uncheck Synch Zones Across Surfaces on the C4 and the MCU and using GoZone and GoSubZone instead of ToggleShouldMapSends, I think that should work.

ToggleShouldMapSends is a global thing like TrackSelection and FXFocus.

Well, now we're talkin' Pages, don't forget about them

doh!

totally forgot about Pages. Page 1 = sends on C4, Page 2 = sends on MCU. Too easy

I think i'll stick that in in my back pocket and give the Zone/SubZone a try first. Important to get to grips with the whole Zone thing.

Geoff Waddington · 06-26-2019, 05:48 PM

Quote:

Originally Posted by MixMonkey

doh!

totally forgot about Pages. Page 1 = sends on C4, Page 2 = sends on MCU. Too easy

I think i'll stick that in in my back pocket and give the Zone/SubZone a try first. Important to get to grips with the whole Zone thing.

Cool !!

Thought about it a bit, ToggleShouldMapSends should constrain to the surface that sent it, unless Synch Zones is checked.
In other words, it's a bug, you should be able to use ToggleShouldMapSends to get the results you want once I fix it

MixMonkey · 06-26-2019, 05:56 PM

Quote:

Originally Posted by Geoff Waddington

Cool !!

Thought about it a bit, ToggleShouldMapSends should constrain to the surface that sent it, unless Synch Zones is checked.

Another words, it's a bug, you should be able to use ToggleShouldMapSends to get the results you want once I fix it

That'd be great

Maybe think about changing its name to ToggleWILLMapSends

(or just ToggleMapSends

)

Geoff Waddington · 06-27-2019, 02:56 AM

Quote:

Originally Posted by MixMonkey

That'd be great

Maybe think about changing its name to ToggleWILLMapSends

(or just ToggleMapSends

)

Ooops, programming nomenclature bleeding through, ToggleMapSends it is

uksnowy · 06-27-2019, 03:07 AM

Quote:

Originally Posted by poetnprophet

Hey there, yes I think it would work. There are a few buttons on the Prox that aren't on the G2, but looks like majority are similar and I would assume have identical midi values (after all, they should both mimic the mcu the same).

I can post my zon and mst files later tonight for you to try.

That'll be awesome. Thank you.

I checked your website. I'm digging your groove man.. Nice.

Geoff Waddington · 06-27-2019, 09:25 AM

New build is up.

ToggleMapSends (was ToggleShouldMapSends) now respects ZoneLink settings.

Added TrackAutoMode and GlobalAutoMode -- see MCU.zon for deets.

Let me know if this cures the automation permalit blues

MixMonkey · 06-27-2019, 04:43 PM

All working as planned

Great job Geoff!

Auto lights behave exactly as expected. If your selection includes tracks with different modes, more than one light comes on. When you push an auto mode button, all the selected tracks switch to that mode, all the other mode lights go out and the selected mode light stays on.

ToggleMapSends now confines the send splay to the surface that triggered it (when Synch Zones Across Surfaces is unchecked), so I can now choose whether to splay the sends on the C4 rotaries or the MCU faders

PoetnProphet, here's the modified C4.zon: (slightly flashier, using the |1-8 style to make it shorter

)

Code:

Zone Home
OnFXFocus MapFocusedTrackFXToWidgets
/
SpotErase ToggleMapSends
SlotUp Reaper _fba48393e4ca48f88d11cba0e4671ab3
SlotDown Reaper _265b374bdcd740f7af4550cd986e4e9c
TrackL Reaper _S&M_WNONLY1
TrackR Reaper _S&M_WNONLY2
Split Reaper _S&M_WNCLS3
BankLeft TrackBank -24
BankRight TrackBank 24
ChannelLeft TrackBank -1
ChannelRight TrackBank 1
ZoneEnd
/
/
Zone Send|1-8
	DisplayUpperD|  TrackSendNameDisplay
	DisplayLowerD|  TrackSendVolumeDisplay
	RotaryPushD| TrackSendMute
	RotaryD|  TrackSendVolume
ZoneEnd

To get the sends on the faders, here's my MCU.zon. Cut and paste what you need.

Code:

Zone Home	
	IncludedZones
		Buttons
		Channel|1-8
	IncludedZonesEnd
ZoneEnd
/
/
Zone Send|1-8
	DisplayUpper|  TrackSendNameDisplay
	TrackTouch+DisplayUpper|  TrackSendVolumeDisplay
	Mute| TrackSendMute
	Fader|  TrackSendVolume
	TrackTouch+Fader|  TrackSendVolume
	FaderTouch|  TrackTouch
ZoneEnd
/
Zone Buttons
	Send ToggleMapSends
        ChannelLeft TrackBank -1
	ChannelRight TrackBank 1
	BankLeft TrackBank -8
	BankRight TrackBank 8
	Rewind Rewind
	FastForward FastForward
	Stop Stop
	Play Play
	Record Record
	F1 NextPage
	F7 PinSelectedTracks
	F8 UnpinSelectedTracks

	smpteBeats CycleTimeDisplayModes
	TimeDisplay TimeDisplay

	Read	TrackAutoMode 1
	Write	TrackAutoMode 3
	Trim	TrackAutoMode 0
	Touch	TrackAutoMode 2
	Latch	TrackAutoMode 4
	Group	Reaper 42023	

	Shift+Read	GlobalAutoMode 1	
	Shift+Write	GlobalAutoMode 3	
	Shift+Trim	GlobalAutoMode 0	
	Shift+Touch	GlobalAutoMode 2	
	Shift+Latch	GlobalAutoMode 4	
	Shift+Group	Reaper 42024	

	Save Reaper 40026
	Shift+Save Reaper 40022

	Undo Reaper 40029
	Shift+Undo Reaper 40030

	Shift Shift
	Option Option
	Control Control
	Alt Alt

	Marker Reaper 40172
	Shift+Marker Reaper 40157
	Option+Marker Reaper 40174

	Nudge Reaper 40173
	Cycle CycleTimeline
	Click Reaper 40364
	Solo Reaper 41818

	JogWheelRotaryCW Reaper 40647
	JogWheelRotaryCCW Reaper 40646

	MasterFader MasterTrackVolume
ZoneEnd
/
/
Zone Channel|1-8
	TrackNavigator
	DisplayUpper| TrackNameDisplay
	DisplayLower| TrackPanDisplay
	TrackTouch+DisplayLower| TrackVolumeDisplay
	RotaryPush| TrackCycle PanWidthCycle 2
	PanWidthCycle+Rotary| TrackPan 0
	PanWidthCycle+Rotary| TrackPanWidth 1
	RecordArm|  TrackRecordArm
	Solo|  TrackSolo
	Mute| TrackMute
	Select|  TrackUniqueSelect
	Shift+Select|  TrackRangeSelect
	Control+Select|  TrackSelect
	Fader|  TrackVolume
	TrackTouch+Fader|  TrackVolume
	FaderTouch|  TrackTouch
ZoneEnd

Geoff Waddington · 06-27-2019, 05:11 PM

Quote:

Originally Posted by MixMonkey

All working as planned

Great job Geoff!

Auto lights behave exactly as expected. If your selection includes tracks with different modes, more than one light comes on. When you push an auto mode button, all the selected tracks switch to that mode, all the other mode lights go out and the selected mode light stays on.

ToggleMapSends now confines the send splay to the surface that triggered it (when Synch Zones Across Surfaces is unchecked), so I can now choose whether to splay the sends on the C4 rotaries or the MCU faders

Great, thanks for testing !!

MixMonkey · 06-27-2019, 06:37 PM

Quote:

Originally Posted by Geoff Waddington

Great, thanks for testing !!

No probs

It might be an idea to include:

Code:

Zone Send|1-8
	DisplayUpper|  TrackSendNameDisplay
	TrackTouch+DisplayUpper|  TrackSendVolumeDisplay
	Mute| TrackSendMute
	Fader|  TrackSendVolume
	TrackTouch+Fader|  TrackSendVolume
	FaderTouch|  TrackTouch

in the MCU.zon file. It has Send ToggleMapSends in Zone Buttons, but no send defs to go with.

Also that pesky space is still in:

Code:

TrackTouch+ DisplayLower|  TrackVolumeDisplay

I was thinking about the RadioButton lights thing and how it relates to purely CSI constructs.

I quite agree that the Reaper scenarios like automation modes are best handled case by case, taking into consideration the feedback from Reaper, but for CSI operations that are mutually exclusive (Pages, Zone/SubZone) could CSI not generate the feedback messages required, independent of Reaper?

Say I have a Zone/SubZone arrangment in an FX.zon file. In the Zone part I have:

Code:

SomeButton2 GoSubZone "SubZone-1" "VST3:SomeFX"

and in the SubZone I have:

Code:

SomeButton1 GoZone "VST3:SomeFX"

SomeButton1 and SomeButton2 are both FB_TwoState type buttons. When I press SomeButton1 I want CSI to send the light on message for SomeButton1 and the light off message for SomeButton2. These messages are already in the .mst file.

Ideally, in the Zone, i'd like to write something like:

Code:

 SomeButton2FB (SomeButton1FB) GoSubZone "SubZone-1" "VST3:SomeFX"

Meaning: SomeButton2 receives feedback directly from CSI and when pressed it is sent the light on message. On the same press SomeButton1 is sent its light off message.

and in the SubZone:

Code:

 SomeButton1FB (SomeButton2FB) GoZone "VST3:SomeFX"

Meaning: When SomeButton1 is pressed it is sent the light on message by CSI and on the same press SomeButton2 is sent the light off message.

When FX.zon is deactivated, all SomeButton lights go off.

Hopefully it could be extended to things like:

Code:

SomeButton1FB (SomeButton2FB SomeButton3FB SomeButton4FB) GoZone "VST3:SomeFX"

Hairbrained?

Geoff Waddington · 06-27-2019, 07:07 PM

Quote:

Originally Posted by MixMonkey

No probs

It might be an idea to include:

Code:

Zone Send|1-8
	DisplayUpper|  TrackSendNameDisplay
	TrackTouch+DisplayUpper|  TrackSendVolumeDisplay
	Mute| TrackSendMute
	Fader|  TrackSendVolume
	TrackTouch+Fader|  TrackSendVolume
	FaderTouch|  TrackTouch

in the MCU.zon file. It has Send ToggleMapSends in Zone Buttons, but no send defs to go with.

Also that pesky space is still in:

Code:

TrackTouch+ DisplayLower|  TrackVolumeDisplay

Thanks, included your Sends Zone and fixed that silly space bug

Geoff Waddington · 06-27-2019, 07:09 PM

Quote:

Originally Posted by MixMonkey

No probs

I was thinking about the RadioButton lights thing and how it relates to purely CSI constructs.

I quite agree that the Reaper scenarios like automation modes are best handled case by case, taking into consideration the feedback from Reaper, but for CSI operations that are mutually exclusive (Pages, Zone/SubZone) could CSI not generate the feedback messages required, independent of Reaper?

Say I have a Zone/SubZone arrangment in an FX.zon file. In the Zone part I have:

Code:

SomeButton2 GoSubZone "SubZone-1" "VST3:SomeFX"

and in the SubZone I have:

Code:

SomeButton1 GoZone "VST3:SomeFX"

SomeButton1 and SomeButton2 are both FB_TwoState type buttons. When I press SomeButton1 I want CSI to send the light on message for SomeButton1 and the light off message for SomeButton2. These messages are already in the .mst file.

Ideally, in the Zone, i'd like to write something like:

Code:

 SomeButton2FB (SomeButton1FB) GoSubZone "SubZone-1" "VST3:SomeFX"

Meaning: SomeButton2 receives feedback directly from CSI and when pressed it is sent the light on message. On the same press SomeButton1 is sent its light off message.

and in the SubZone:

Code:

 SomeButton1FB (SomeButton2FB) GoZone "VST3:SomeFX"

Meaning: When SomeButton1 is pressed it is sent the light on message by CSI and on the same press SomeButton2 is sent the light off message.

When FX.zon is deactivated, all SomeButton lights go off.

Hopefully it could be extended to things like:

Code:

SomeButton1FB (SomeButton2FB SomeButton3FB SomeButton4FB) GoZone "VST3:SomeFX"

Hairbrained?

Hmm...

I envisioned Radio Buttons to be in the same Zone, however your cross-Zone use case looks good, more thinking to do...

poetnprophet · 06-27-2019, 07:21 PM

Quote:

Originally Posted by MixMonkey

PoetnProphet, here's the modified C4.zon: (slightly flashier, using the |1-8 style to make it shorter

)

Wow thank you, that is much neater!
Also can confirm that the automation modes are working great now. Really appreciate everyone's on this!

poetnprophet · 06-27-2019, 07:27 PM

Quote:

Originally Posted by uksnowy

That'll be awesome. Thank you.

I checked your website. I'm digging your groove man.. Nice.

Ah thanks I really appreciate that!

Ok, here is the MST and ZON files. It's got a few commented lines and there are several custom actions there but otherwise all working very well. FYI this is with Geoff's very latest and greatest as of today.

dave

Geoff Waddington · 06-28-2019, 05:13 AM

New build is up.

Calibrated FB_VUMeter for Console1, since that's all I have here

The clip lights come on as close to simultaneously on both the Console1 and Reaper as i can get them, that was the main focus.

The meter seems roughly accurate (within a dB or so) on the Console1.

Anyone else, please have a look at the calibration.

MixMonkey · 06-28-2019, 05:17 PM

Found a bit of a bug between showing/hiding tracks in a folder in the mixer and OnFXFocus MapFocusedTrackFXToWidgets.

If the tracks in a folder are hidden in the mixer, FX on tracks after the folder track (but not in the folder) won't map when focussed.

If you show the tracks in the folder (with that little clickable circle on the bottom left of the mixer channel) the FX behaviour returns to normal.

Regarding folders, it's a shame we've only got: Toggle show tracks in folders in mixer

If we had: Toggle show tracks in folders in mixer on selected track(s)

We'd be golden

Geoff Waddington · 06-28-2019, 05:55 PM

Quote:

Originally Posted by MixMonkey

Found a bit of a bug between showing/hiding tracks in a folder in the mixer and OnFXFocus MapFocusedTrackFXToWidgets.

If the tracks in a folder are hidden in the mixer, FX on tracks after the folder track (but not in the folder) won't map when focussed.

If you show the tracks in the folder (with that little clickable circle on the bottom left of the mixer channel) the FX behaviour returns to normal.

Thanks, will investigate.

Quote:

Originally Posted by MixMonkey

Regarding folders, it's a shame we've only got: Toggle show tracks in folders in mixer

If we had: Toggle show tracks in folders in mixer on selected track(s)

We'd be golden

Ok, let's talk Cadillac Folder solutions.

Wondering if this would be a good workflow.

Implement Folders as Zones, much like Sends, but instead of a fixed number like Sends, have a different Navigator, more like Track, where you could bank through the child Tracks.

So workflow is like this:

Select Folder Track.
Press Folder button (mapped to ToggleZone Folder)
Folder children map as per Folder Zone, probably including mapping bank controls.
Navigate Folder children.
Press Folder button to return to normal operation

Does that make sense use case/workflow wise ?

Now, as far as showing only Folder Tracks, should that be an Action that you can map a button to ?

Does Klinke support more than one nested level ?

Is there a Cadillac solution for nested Folders ?

Any and all thoughts appreciated folks !!

MixMonkey · 06-28-2019, 06:04 PM

Useful Observation: Buttons, lights and Actions (can't be 100%, but it seems to hold true for all the Actions I've tried)

In the Action list, any Action that has an entry in the Status column will send correct on/off feedback to a CSI surface Button (ie FB_TwoState). If there isn't an entry in the Status column, it won't and the the light will be on permanently.

So even if it has Toggle in the name, if there's no Status column entry, there'll be no feedback to the light.

Useless observation:

Reaper can do RadioButtons by itself when it wants to. I mapped the grid divisions to four FB_TwoState MCU Buttons (Actions 40781, 40780, 40779, 40778)

The Grid obviously can't be set to Bars and Quarter notes simultaneously, but the surprise was that it turns out one grid button light when another grid button is selected.

I guess this happens so that on screen icons for the same functions will light and extinguish appropriately.

MixMonkey · 06-28-2019, 06:13 PM

Quote:

Originally Posted by Geoff Waddington

Is there a Cadillac solution for nested Folders ?

Any and all thoughts appreciated folks !!

I'm a bit of an amateur folder user

so others are probably better equipped to offer suggestions.

All I would really want would be the Folder (on a selected track) to expand to the right, pushing all the other tracks further right. That way I could quickly change the track balance in the folder and then close it up again. So what you suggested sounds good to me

MixMonkey · 06-28-2019, 07:06 PM

Quick thought about send splay. It's working great btw, but I was wondering if it would be possible to blank the displays and zero the faders on channels that aren't being used in the splay on the surface.

So, If a track only has 3 sends, when it splays on the (8 channel) surface, could channels 4 to 8 be blanked for the duration of the splay. It would make the display much easier to read and having unused send faders go to zero makes it instantly clear which sends are in use, rather than having them side by side with active tracks.

A similar thing happens in FX Zone/SubZone switching. When you switch into the subzone, any unused widgets in the SubZone retain their Zone Settings- because they're unused they don't get overwritten with new data.

The problem doesn't occur when switching back to the main Zone, because the surface seems to receive a complete reset before the zone is loaded. That does produce a bit of a delay, but you know exactly where you are with it.

Could we have some kind of 'null' parameter so that unused controls don't have to be inactive but at the same time can overwrite the Zone?

The displays are easy to blank with spaces. It does make for make for a bit more work when using SubZones, but switching speed wise it will be much faster than blanking the whole surface each time. You'd only be nulling widgets that aren't in use in the Zone you're switching to, rather than the whole surface.

Geoff Waddington · 06-29-2019, 03:07 AM

Quote:

Originally Posted by MixMonkey

Quick thought about send splay. It's working great btw, but I was wondering if it would be possible to blank the displays and zero the faders on channels that aren't being used in the splay on the surface.

So, If a track only has 3 sends, when it splays on the (8 channel) surface, could channels 4 to 8 be blanked for the duration of the splay. It would make the display much easier to read and having unused send faders go to zero makes it instantly clear which sends are in use, rather than having them side by side with active tracks.

Yup, that's fair, thou hast assigned a certain number of slots for Sends display (e.g. 1-4, 1-8, etc.) and thou shalt get them

Quote:

Originally Posted by MixMonkey

A similar thing happens in FX Zone/SubZone switching. When you switch into the subzone, any unused widgets in the SubZone retain their Zone Settings- because they're unused they don't get overwritten with new data.

The problem doesn't occur when switching back to the main Zone, because the surface seems to receive a complete reset before the zone is loaded. That does produce a bit of a delay, but you know exactly where you are with it.

Could we have some kind of 'null' parameter so that unused controls don't have to be inactive but at the same time can overwrite the Zone?

That's already there -- NoAction is what you need to prevent "bleed through":

Code:

Zone aZone
        someButtonThatITookOverWhilstInThisZone Reaper 1234
        someButtonThatHasAnActionOnTheUnderlyingZoneThatIWantToHide NoAction
ZoneEnd

MixMonkey · 06-29-2019, 05:46 AM

Quote:

Originally Posted by Geoff Waddington

That's already there -- NoAction is what you need to prevent "bleed through":

Code:

Zone aZone
        someButtonThatITookOverWhilstInThisZone Reaper 1234
        someButtonThatHasAnActionOnTheUnderlyingZoneThatIWantToHide NoAction
ZoneEnd

Splendid!

Can I use it like this?

Code:

DisplayUpperC7		FXParamNameDisplay	""	"       "
DisplayLowerC7		FXParamNameDisplay	""	"       "	
RotaryC7		FXParam			"NoAction"		
Toggle+RotaryPushC7	FXParam			"NoAction"

Geoff Waddington · 06-29-2019, 06:30 AM

Quote:

Originally Posted by MixMonkey

Splendid!

Can I use it like this?

Code:

DisplayUpperC7		FXParamNameDisplay	""	"       "
DisplayLowerC7		FXParamNameDisplay	""	"       "	
RotaryC7		FXParam			"NoAction"		
Toggle+RotaryPushC7	FXParam			"NoAction"

Not quite:

Code:

DisplayUpperC7		NoAction
DisplayLowerC7		NoAction	
RotaryC7		NoAction		
Toggle+RotaryPushC7	NoAction

It's always Widget followed by Action, possibly followed by Parameter(s).

poetnprophet · 06-29-2019, 08:42 AM

Quote:

Originally Posted by MixMonkey

Regarding folders, it's a shame we've only got: Toggle show tracks in folders in mixer

If we had: Toggle show tracks in folders in mixer on selected track(s)

We'd be golden

There is also the action: Mixer: Show/hide children of selected tracks.
But there's also still the bugs where the fx don't map properly when any mixer tracks are hidden, collapsed, or pinned.

Geoff Waddington · 06-29-2019, 09:02 AM

Quote:

Originally Posted by poetnprophet

But there's also still the bugs where the fx don't map properly when any mixer tracks are hidden, collapsed, or pinned.

Yeah, gonna tackle that as part of Folder design/implementation.

poetnprophet · 06-29-2019, 10:09 AM

Quote:

Originally Posted by Geoff Waddington

New build is up.

Calibrated FB_VUMeter for Console1, since that's all I have here

The clip lights come on as close to simultaneously on both the Console1 and Reaper as i can get them, that was the main focus.

The meter seems roughly accurate (within a dB or so) on the Console1.

Anyone else, please have a look at the calibration.

Hi Geoff, sorry to report that the meter is still low here. I made a short video showing the difference, the first part is CSI I downloaded 6/6/19, 2nd part is the new build from yesterday.

https://youtu.be/pDIqxLzhv7M

Geoff Waddington · 06-29-2019, 10:25 AM

Quote:

Originally Posted by poetnprophet

Hi Geoff, sorry to report that the meter is still low here. I made a short video showing the difference, the first part is CSI I downloaded 6/6/19, 2nd part is the new build from yesterday.

https://youtu.be/pDIqxLzhv7M

OK please post the relevant part of your .mst file -- the part where the meters are defined.

Also can you estimate a dB value required for the correction ?

poetnprophet · 06-29-2019, 10:36 AM

Quote:

Originally Posted by poetnprophet

Ah thanks I really appreciate that!

Ok, here is the MST and ZON files. It's got a few commented lines and there are several custom actions there but otherwise all working very well. FYI this is with Geoff's very latest and greatest as of today.

dave

I already forgot that there was a firmware update for the ProX, it really changed a lot, lots of new functions and totally new layout. I'm not sure if this will apply to yours or not, but now we have SEND and EQ buttons as well as a layer button, which the G2 has. I [think] I've got everything remapped accordingly, here is that mst file.

poetnprophet · 06-29-2019, 10:39 AM

Quote:

Originally Posted by Geoff Waddington

OK please post the relevant part of your .mst file -- the part where the meters are defined.

Also can you estimate a dB value required for the correction ?

Ha, just saw this and posted my MST on an unrelated reply. here are the meter statements:

Widget VUMeter1
FB_MCUVUMeter 0
WidgetEnd

Widget VUMeter2
FB_MCUVUMeter 1
WidgetEnd

Widget VUMeter3
FB_MCUVUMeter 2
WidgetEnd

Widget VUMeter4
FB_MCUVUMeter 3
WidgetEnd

Widget VUMeter5
FB_MCUVUMeter 4
WidgetEnd

Widget VUMeter6
FB_MCUVUMeter 5
WidgetEnd

Widget VUMeter7
FB_MCUVUMeter 6
WidgetEnd

Widget VUMeter8
FB_MCUVUMeter 7
WidgetEnd

I would estimate 6db.

Geoff Waddington · 06-29-2019, 10:47 AM

Quote:

Originally Posted by poetnprophet

Ha, just saw this and posted my MST on an unrelated reply. here are the meter statements:

Widget VUMeter1
FB_MCUVUMeter 0
WidgetEnd

Widget VUMeter2
FB_MCUVUMeter 1
WidgetEnd

I would estimate 6db.

Cool, the calibration was done for FB_VUMeter.

I will try a 6DB increase for FB_MCUVUMeter.

How about others using FB_MCUVUMeter, is it off on your surface by the same approx 6 dB ?

poetnprophet · 06-29-2019, 11:40 AM

whoops, i didn't notice that difference, should I have just used the other line instead of the MCU line?

Geoff Waddington · 06-29-2019, 12:05 PM

Quote:

Originally Posted by poetnprophet

whoops, i didn't notice that difference, should I have just used the other line instead of the MCU line?

Nope, we just have to calibrate FB_MCUVUMeter.

You've got the right one, trust me, if you use FB_VUMeter, your meters would likely be pegged most of the time

Geoff Waddington · 06-29-2019, 12:54 PM

New build is up.

@poetnprophet, as well as others using FB_MCUVUMeter, please check your calibration with this build and let me know which way to tune from here, it was low to start.

poetnprophet · 06-29-2019, 04:21 PM

Quote:

Originally Posted by Geoff Waddington

New build is up.

@poetnprophet, as well as others using FB_MCUVUMeter, please check your calibration with this build and let me know which way to tune from here, it was low to start.

very close now Geoff! 2db higher and it would be about perfect, although I'm using the AVG meter statement, not the peak. Not sure how much that will make a difference.

thank you thank you!

Geoff Waddington · 06-29-2019, 04:59 PM

Quote:

Originally Posted by poetnprophet

very close now Geoff! 2db higher and it would be about perfect, although I'm using the AVG meter statement, not the peak. Not sure how much that will make a difference.

thank you thank you!

Cool, let's leave it there for now.

Hopefully you and a few other folks will play with it for a bit (Peak vs Avg, etc.), let me know, we'll then do a final calibration.

airon · 06-30-2019, 01:19 AM

Lots to dig through. I‘ll give the new build a shot today after work. Lots of new stuff to try out.

Geoff, how about keeping a little spreadsheet of all the code words for the MST and the Zone files ? Or is that already available ?

Geoff Waddington · 06-30-2019, 03:58 AM

Quote:

Originally Posted by airon

Lots to dig through. I‘ll give the new build a shot today after work. Lots of new stuff to try out.

Geoff, how about keeping a little spreadsheet of all the code words for the MST and the Zone files ? Or is that already available ?

Yup, there is a very primitive start in the included "How It Works" pdf, would love to get your questions/feedback as an aid on how best to expand/improve those docs

MixMonkey · 06-30-2019, 05:30 AM

Quote:

Originally Posted by Geoff Waddington

Not quite:

Code:

DisplayUpperC7		NoAction
DisplayLowerC7		NoAction	
RotaryC7		NoAction		
Toggle+RotaryPushC7	NoAction

It's always Widget followed by Action, possibly followed by Parameter(s).

NoAction working well here

Doesn't blank the displays but does block parameter 'carry over' from Zone to SubZone (and back again)

I'm blanking displays like this:

Code:

	DisplayUpperA5	FXParamNameDisplay	"       "
	DisplayLowerA5	FXParamNameDisplay	"       "
              RotaryA5	NoAction	
   Toggle+RotaryPushA5	NoAction

Is it really necessary to have that big, whole surface reset when returning from SubZone to Zone?

Moving from Zone to SubZone is very snappy, but there's a pause when returning as the surface resets before the Zone parameters load.

Geoff Waddington · 06-30-2019, 05:59 AM

Quote:

Originally Posted by MixMonkey

NoAction working well here

Doesn't blank the displays but does block parameter 'carry over' from Zone to SubZone (and back again)

I'm blanking displays like this:

Code:

	DisplayUpperA5	FXParamNameDisplay	"       "
	DisplayLowerA5	FXParamNameDisplay	"       "
              RotaryA5	NoAction	
   Toggle+RotaryPushA5	NoAction

Cool.

Quote:

Originally Posted by MixMonkey

Is it really necessary to have that big, whole surface reset when returning from SubZone to Zone?

Moving from Zone to SubZone is very snappy, but there's a pause when returning as the surface resets before the Zone parameters load.

Are you running real Midi or USB ?

How much of a pause ?

Is it less snappy than banking ?

I see no lag at all here but I'm running the Avid Artist series in Mackie/Midi emulation mode.