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

tdc · 04-03-2020, 07:13 PM

Quote:

Originally Posted by Geoff Waddington

Is that an ATC SCM25A I see ? -- drools

:-)

You have keen eyes Geoff!

Geoff Waddington · 04-04-2020, 09:45 AM

Quote:

Originally Posted by tdc

:-)

You have keen eyes Geoff!

Haha, have wanted to audition a set for years now

How do you like them, do they have that big ATC sound ?

On another note, upon seeing your setup. I usually don't recommend specific products, but I recently picked up a Novation Launchpad mini mk3, with full RGB support, it is the perfect addition to go with the iPad, iPhone, 2 Mixes, Transport, and Console 1, might even have to call it the icing on the cake.

It takes over all the MCU (or Artist Control) right panel chores, highly recommended, and of course fully supported in CSI.

Fully customized MacGyver layouts available

The ability to control the on/off RGB colours alone is worth the price of admission.

1/2" labels on the laser printer come out close enough for rock and roll to add even more context info

Also note the colours are much nicer than they shoot

WaveTrans · 04-04-2020, 02:43 PM

Hi!

Got a functioning Icon Platform X+ to expand my Icon Nano now.

Works fine so far, just a couple of questions came up during use.

- The Fader motors of the X+ make littel sounds as if they were making micro movements or switching on/off rapidly kind of jittering (trackmode andFX mode).
Stops copletely, when I turn off Reaper/leave the programm or toggle sends

Is this normal (console) behaviour?
May this damage the motors?

- In most of my existing projects, FX focus is failing when I switch through chains of plugins; meaning display info of plugins which are not selected or just the track info is displayed, and FX.zones are not toggled.

Thought it is bridged Plugins or hidden tracks, but when I use the same plugin combinations in my test project everything works fine there.
Also, if I copy a track from the project into my test project, everything works as it should.
Duplicating and erasing the original track does not help it.

Edit: On a second look, the tracks in the test project show the same behaviour.

Any idea what´s causing this?
What I can do about it?

It´s a bit wierd that I can use CSI/surfaces only in new projects...

Thanks!

Geoff Waddington · 04-04-2020, 02:43 PM

New builds are up.

Also need the new EuCon.zon file.

Hopefully fixed the unwanted Touch linking, but unfortunately not the weird Pan/Width/PanL/PanR behaviour.

Transport time display is operational -- and synchs with Reaper settings -- that fixes another bug as well where Reaper and the surface time displays got out of synch.

Geoff Waddington · 04-04-2020, 02:47 PM

Quote:

Originally Posted by WaveTrans

Hi!

Got a functioning Icon Platform X+ to expand my Icon Nano now.

Works fine so far, just a couple of questions came up during use.

- The Fader motors of the X+ make littel sounds as if they were making micro movements or switching on/off rapidly kind of jittering.
Stops copletely, when I turn off Reaper/leave the programm.

Is this normal (console) behaviour?
May this damage the motors?

Sounds like the telltale signs of the dreaded double mapping, the faders are being sent conflicting values in rapid succession.

Please post your .zon file contents and we'll have a look.

WaveTrans · 04-04-2020, 03:12 PM

Quote:

Originally Posted by Geoff Waddington

Sounds like the telltale signs of the dreaded double mapping, the faders are being sent conflicting values in rapid succession.

Please post your .zon file contents and we'll have a look.

Thanks, here are the surface zones.
Since this "jittering" appears in FX mode, are the FX.zones also required?

What shall I do about it?
Put "no Action" for all unused controls in the respective .zone?

Icon Nano zone

Code:

Zone "Home"
	OnTrackSelection MapSelectedTrackSendsToWidgets
	OnFXFocus MapFocusedFXToWidgets 
	IncludedZones
		"Buttons|"
		"Channel|1-1"
		"MasterChannel|"
		"JogWheelHack|"
	IncludedZonesEnd
ZoneEnd

Zone "Buttons|"
	Track 		Reaper 	"40917"  		// Master MonoStereo
	Send 		ToggleMapSelectedTrackSends
	Send 		Reaper 	"40293"  		// Send Menu
	Pan 		Reaper 	"_S&M_SELFXNEXT" // Next FX
	Plugin		ToggleMapFocusedFX   
	Plugin		Reaper 	"_S&M_TOGLFXCHAIN"  // Fx menu
    EQ 			Reaper 	"_S&M_TOGLFXCHAIN"  // Fx menu  
    Instrument	Reaper 	"40293"  		// Send Menu 
		
	Play 		Play
	Stop 		Stop
	Record 		Record
	Rewind 		Rewind
	FastForward	FastForward

/Nano ChannelL/R and BankL/R buttons are hardwired to simulate 8 Channels
/	ChannelLeft TrackBank "-1" 
/	ChannelRight 	TrackBank "1" 
/	BankLeft 	TrackBank "-8"
/	BankRight 	TrackBank "8"
	
/red buttons "automation, incl. LastTouchedParam (call FocusedFXParam)"
	Flip GoZone "LastTouchedParam" // automate last touche FX param; for instr see zone below
	Read 		TrackAutoMode 	"1"
	Write 		TrackAutoMode 	"3"
	Trim 		TrackAutoMode 	"0"
	GlobalView 	Reaper "_S&M_DISARMALLENVS" //Disarm all Envelopes
	Touch 		TrackAutoMode 	"2"
	Latch 		TrackAutoMode 	"4"
    LatchPrev 	TrackAutoMode 	"5"		
	
/Green buttons "CSIEdit, Mixer, Wiring, St. FX insert" 
	TrackLearn Reaper "_CSIEditMode"
	Items Reaper "24900" 		// Insert ReaEQ
	Takes Reaper "24901" 		// Insert ReaComp
	Create Reaper "24902" 		// Insert ReaVerb
	Project Reaper "42031"		 // toggle Wiring diagram
	Mixer Reaper "40078" 		// Toggle Mixer
	TrackFX Reaper "_BR_TOGGLE_PLAY_MOUSE_SOLO_TRACK" //play from mouse cursor solo track
	Master Reaper "_BR_PLAY_STOP_MOUSECURSOR" // play from mouse cursor

/Blue buttons "Misc"
	nameValue GoZone "Home"
	Marker 		Reaper "40157" 
	Nudge 		Reaper "41228" //  nudge dialog
	RecordMode 	Reaper "_BR_CYCLE_RECORD_MODES"
	smpteBeats 	CycleTimeDisplayModes
	/ blue 6 CC58 Replace    
	Click 		Reaper "40364"
	UnSoloAll 	Reaper "40340"

/purple buttons "Save, Undo, Redo, Modifiers"
	Save 		Reaper "40026"
	Undo 		Reaper "40029"
	Redo 		Reaper "40030"	 // Mcu Cancel
	/Enter Reaper ??
	Shift 		Shift
	Option 		Option
	Control 	Control
	Alt 		Alt

/yellow buttons  "project nav.; track/env min/max"
	F1 		Reaper 	"40042" 	 // Go to start of project
	F2 		Reaper 	"40043" 	 // Go to end of project
	F3 		Reaper 	"40182" 	 // Select all
	F4 		Reaper 	"40289" 	 // unselect all
	F5 Reaper "_RS0864070d129fe58581acadd27a177b6c942943e6" //Maximize envelopes of selected Track
	F6 Reaper "_RSaeb8288b2019d5651b11138904e570e27a58c2db" //Minimize all tracks Env
	F7 Reaper "40110" // Minimize all tracks height
	F8 Reaper "_WOL_FZOOMSELENVTIMESEL" //SWS/wol: Full zoom selected envelope in time selection

ZoneEnd

Zone "JogWheelHack|"
/		JogWheelRotaryCW  Reaper "40647"      //Move cursor right to grid division
/		JogWheelRotaryCCW Reaper "40646"      //Move cursor left to grid division


/ scroll view left Reaper "40140"
	JogWheelRotaryCW 	Reaper "40647"
	JogWheelRotaryCW2 	Reaper "40647"
	JogWheelRotaryCW3 	Reaper "40647"
	JogWheelRotaryCW4 	Reaper "40647"
	JogWheelRotaryCW5 	Reaper "40647"
	JogWheelRotaryCW6 	Reaper "40647"
	JogWheelRotaryCW7 	Reaper "40647"

/scroll view right Reaper "40141"
	JogWheelRotaryCCW 	Reaper "40646"
	JogWheelRotaryCCW2 	Reaper "40646"
	JogWheelRotaryCCW3 	Reaper "40646"
	JogWheelRotaryCCW4 	Reaper "40646"
	JogWheelRotaryCCW5 	Reaper "40646"
	JogWheelRotaryCCW6 	Reaper "40646"
	JogWheelRotaryCCW7 	Reaper "40646"
	
/Zoom
	Zoom+Up 		Reaper "40111"
	Zoom+Down 		Reaper "40112"
	Zoom+Right 		Reaper "1012"
	Zoom+Left 		Reaper "1011"
ZoneEnd

Zone "Channel|"
	TrackNavigator
	DisplayUpper| TrackPanDisplay
	DisplayLower| TrackNameDisplay 
	TrackTouch+DisplayUpper| TrackVolumeDisplay
	Rotary| TrackPan "0" 
	RotaryPush| GoZone "PanWidth|" 
	RecordArm| TrackRecordArm
	Solo| TrackSolo
	Mute| TrackMute
	Select| TrackUniqueSelect
	Fader| TrackVolume
	FaderTouch| TrackTouch
	VUMeter| TrackOutputMeter
ZoneEnd

Zone "MasterChannel|"
	MasterTrackNavigator 
	MasterFader TrackVolume
	VUMeterMaster TrackOutputMeter
	Rotary2 TrackPan "0"
ZoneEnd

Zone "Pan|1-1" // "Pan|1-1"
	TrackNavigator //SelectedTrackNavigator
	Rotary| TrackPan "0" //ursp Rotary|
	DisplayUpper| TrackPanDisplay
	RotaryPush| GoZone "PanWidth|1-1"
	Shift+RotaryPush| Reaper "_XENAKIOS_PANTRACKSCENTER" // Pan center sel Track
ZoneEnd

Zone "PanWidth|1-1" 
	TrackNavigator //SelectedTrackNavigator
	Rotary| TrackPanWidth "1"
	DisplayUpper| TrackPanWidthDisplay
	RotaryPush| GoZone 	"Pan|1-1" //ursp RotaryPush|
	Shift+RotaryPush| Reaper "_RSdba7d179fe17818a8fb63f5011e7fb07d27d95a8" //Sel Track width to 100%
ZoneEnd

/Zone "Send|1-8"
/	SelectedTrackNavigator
/	DisplayLower| TrackSendNameDisplay
/	TrackTouch+DisplayUpper| TrackSendVolumeDisplay
/	Mute| TrackSendMute
/	Fader| TrackSendVolume
/	TrackTouch+Fader| TrackSendVolume
/	FaderTouch| TrackTouch
/	Rotary| TrackSendVolume  //send lev. via rotaries, deact. /faders
/	Rotary| TrackSendPan
/	RotaryPush| NoAction
/ZoneEnd

/Zone "FXMenu|1-4"
/	FocusedFXTrackNavigator
/	DisplayUpper| FXNameDisplay|
/	DisplayLower| NoAction
/	RotaryPush| GoFXSlot| 
/ZoneEnd

Zone "LastTouchedParam"
/ Select Track, 
/ "Last touch" Param in FX
/ Press "LastTouchedParam" button
/ Set track to write mode
/ Press Play to ride automation - Stop when finished
/ Envelopes remain armed; disarm before riding a different FXParam
/ Hit GoZone "Home" (Blue1) to leave 
    Fader1 FocusedFXParam
    FaderTouch1 TrackTouch
	DisplayUpper1 FocusedFXParamNameDisplay
	DisplayLower1 FocusedFXParamValueDisplay
	GlobalView Reaper "_S&M_DISARMALLENVS" 
ZoneEnd

Icon X+ zone

Code:

Zone Home
	OnTrackSelection MapSelectedTrackSendsToWidgets
	OnFXFocus MapFocusedFXToWidgets
	/OnTrackSelection MapSelectedTrackSendsToWidgets
	IncludedZones
		"Channel|1-8"
	IncludedZonesEnd
ZoneEnd

Zone "Channel|"
	TrackNavigator
	DisplayUpper|  		TrackNameDisplay
	DisplayLower|  		TrackPanDisplay
	TrackTouch+DisplayLower| TrackVolumeDisplay
	RotaryPush| 		GoZone PanWidth|
	Rotary|			 TrackPan "0"
	RecordArm|  		TrackRecordArm
	Solo|  			TrackSolo
	Mute| 			TrackMute
	Select|  		TrackUniqueSelect
/	Shift+Select|  		TrackRangeSelect
/	Control+Select|  	TrackSelect
/	Shift+Control+Select|	TogglePin
/	Option+Select|		TrackFolderDive
	Fader|  		TrackVolume
	TrackTouch+Fader|  	TrackVolume
	FaderTouch|  		TrackTouch
ZoneEnd

Zone "Pan|1-8"
	TrackNavigator
	Rotary| 	TrackPan "0"
	RotaryPush|	GoZone "PanWidth|"
ZoneEnd

Zone "PanWidth|1-8"
	TrackNavigator
	Rotary| 	TrackPanWidth "1"
	RotaryPush| 	GoZone "Pan|"
ZoneEnd

Zone "Send|1-8"
	SelectedTrackNavigator
	DisplayUpper|  			TrackSendNameDisplay
	TrackTouch+DisplayUpper|  	TrackSendVolumeDisplay
	Mute| 				TrackSendMute
	Fader|  			TrackSendVolume
	FaderTouch|  			TrackTouch
	Rotary| TrackSendPan
    RotaryPush| NoAction
ZoneEnd

Zone "FXMenu|1-4"
    FocusedFXTrackNavigator
	/SelectedTrackNavigator
	DisplayUpper|  	FXNameDisplay |
	RotaryPush| 	GoFXSlot |
/ZoneEnd

Thanks!

Geoff Waddington · 04-04-2020, 03:43 PM

Quote:

Originally Posted by WaveTrans

Thanks, here are the surface zones.
Since this "jittering" appears in FX mode, are the FX.zones also required?

The only possible thing I spotted was in the "LastTouchedParam" Zone where Fader1 is used, of course that would require that Zone being active...

Please post an FX Zone that you know misbehaves, we'll have a look.

Geoff Waddington · 04-04-2020, 07:04 PM

New build is up.

Added CycleTrackAutoMode, you can rearrange the order if you like, just make sure the last number is larger than the first number or it won't cycle:

Code:

	RecordArm|  		TrackUniqueSelect
	RecordArm|  		CycleTrackAutoMode [ 0 1 3 2 4 ]

tdc · 04-04-2020, 08:34 PM

Quote:

Originally Posted by Geoff Waddington

Haha, have wanted to audition a set for years now

How do you like them, do they have that big ATC sound ?

I have been lucky enough to have been mixing on ATC's for about 25yrs, some of that time was the 100's and 20's then mainly the 50's. When I left the corporate studio world and set up on my own, I tried the KM-120's, which I thought were amazing for the size and money, then looked and listened to the O300's. I was very impressed with them also - had the ATC imaging. I have a colleague who was an ATC chap for years, but decided on a full 5.1 K&M system. He loves them, and I do agree that they are amazing for the $$.

But, in the end, after delivering a few full film mixes, I knew that I needed to have my reference ATC sound. The 25's fitted my needs and budget perfectly. (who needs to upgrade that car anyway).

Quote:

Originally Posted by Geoff Waddington

On another note, upon seeing your setup. I usually don't recommend specific products, but I recently picked up a Novation Launchpad mini mk3, with full RGB support, it is the perfect addition to go with the iPad, iPhone, 2 Mixes, Transport, and Console 1, might even have to call it the icing on the cake.

:-) I hear you! The Mini Mk3 looks great, certainly for the size! I have an Ableton Push 2 that is awaiting some CSI attention. I use it a lot for product demos and live performance. There are some great third party plugins for it to enable OSC and more complex display control, so am eager to see how I can augment the CSI and Reaper system with it.

On a tangent, You should take a break from your programming and do some instructional videos of your setup. I think many folks would benefit from what you have going on there. In fact, Mr FunkyBot, you should also consider this as it sounds like you have a mature and refined implementation of CSI being used for your day to day work.

tdc · 04-05-2020, 12:56 AM

Quote:

Originally Posted by Geoff Waddington

Hopefully fixed the unwanted Touch linking, but unfortunately not the weird Pan/Width/PanL/PanR behaviour.

Grabbed the new builds.

Time Display on Transport updated with Reaper time display. Well done! At present, it appears that it will only work if the Primary is set to Measures.Beats, and the secondary is Minutes:Seconds. Any other configuration renders the displays blank. (I will typically use Primary at Hours:Minutes:Seconds:Frames, and Secondary to None.)

Touch Linking has been fixed between Pan and Volume. :-) Both parameters still suffer from the previously discussed issue when in Touch. But I assume you know that.

CycleTrackAutoMode Automation Mode Switching via surface channel Rec Button. That was a very fast fix Geoff! This now works as expected - and is amazingly empowering.

The whole CSI implementation is really feeling solid I have to say. Its been running for days through dozens of reboots and reconfigurations all without a crash or unexpected behaviour. :-)

WaveTrans · 04-05-2020, 02:55 AM

Quote:

Originally Posted by Geoff Waddington

The only possible thing I spotted was in the "LastTouchedParam" Zone where Fader1 is used, of course that would require that Zone being active...

Please post an FX Zone that you know misbehaves, we'll have a look.

Thanks for checking my zonfiles.

I removed all FX.zones from the .zon folders to find a rogue one by re-adding them one after another.

however, I found that the jitteringsound occurs even without any FX.zones.

Tested frequency 15-30-60Hz, different settings of "Volume Fader Ranges", new set up with Reaper MCU and MCUXT.
No change.

Jittersound is gone, however, if the faders are at -inf or +12dB
Occurs briefly if faders are set to 0.0

To refine the term jittering:
faders do not visibly vibrate.
It´s the sound of the fader motors permanently trying to adjust to values which do not fit their stepping.

tdc · 04-05-2020, 05:10 AM

Quote:

Originally Posted by WaveTrans

It´s the sound of the fader motors permanently trying to adjust to values which do not fit their stepping.

Hey Wavetrans, well done for finding the culprit, so annoying these little sounds whilst mixing. Its for this reason I always have two layouts on my consoles, usually on the same button with a Shift Key modifier for the second one. A 1:1 layout with all channels shown, and then a completely blank layout - for silence when I am in the critical listening phase.

Geoff Waddington · 04-05-2020, 06:48 AM

Quote:

Originally Posted by tdc

I have been lucky enough to have been mixing on ATC's for about 25yrs, some of that time was the 100's and 20's then mainly the 50's. When I left the corporate studio world and set up on my own, I tried the KM-120's, which I thought were amazing for the size and money, then looked and listened to the O300's. I was very impressed with them also - had the ATC imaging. I have a colleague who was an ATC chap for years, but decided on a full 5.1 K&M system. He loves them, and I do agree that they are amazing for the $$.

But, in the end, after delivering a few full film mixes, I knew that I needed to have my reference ATC sound. The 25's fitted my needs and budget perfectly. (who needs to upgrade that car anyway).

I came up a little earlier

Now by today's standards these monitors pretty much suck, but back in the day I liked JBL 4350's, 4311's, disliked everything in between, hated Westlakes, and there was one place that had urei 813s mounted horizontally driven by a pair of Studer power amps in bridge -- actually sounded very good in that room

Back then is was Studer A80s and Neves everywhere.

When I did the home studio thing, I really wanted to go for the ATCs, maybe someday, but for now the KH 310s with a KH 810 are more than OK

Quote:

Originally Posted by tdc

On a tangent, You should take a break from your programming and do some instructional videos of your setup. I think many folks would benefit from what you have going on there. In fact, Mr FunkyBot, you should also consider this as it sounds like you have a mature and refined implementation of CSI being used for your day to day work.

@MixMonkey, @poetnprophet and others have some pretty interesting setups too.

Definitely planning a video soon.

Geoff Waddington · 04-05-2020, 06:54 AM

Quote:

Originally Posted by tdc

Grabbed the new builds.

Time Display on Transport updated with Reaper time display. Well done! At present, it appears that it will only work if the Primary is set to Measures.Beats, and the secondary is Minutes:Seconds. Any other configuration renders the displays blank. (I will typically use Primary at Hours:Minutes:Seconds:Frames, and Secondary to None.)

Yeah, the right click menus and the internal time modes seem independent.

If you assign this action to a button, you get something better:

Code:

Zone "Buttons|"
        someButton 	CycleTimeDisplayModes
ZoneEnd

Quote:

Originally Posted by tdc

Touch Linking has been fixed between Pan and Volume. :-) Both parameters still suffer from the previously discussed issue when in Touch. But I assume you know that.

Good stuff, yes aware the other automation problem still exists.

Quote:

Originally Posted by tdc

CycleTrackAutoMode Automation Mode Switching via surface channel Rec Button. That was a very fast fix Geoff! This now works as expected - and is amazingly empowering.

Yeah, turns out it was pretty low hanging fruit

Quote:

Originally Posted by tdc

The whole CSI implementation is really feeling solid I have to say. Its been running for days through dozens of reboots and reconfigurations all without a crash or unexpected behaviour. :-)

Glad to hear it, thanks for testing !!

tdc · 04-05-2020, 07:29 AM

Quote:

Originally Posted by Geoff Waddington

If you assign this action to a button, you get something better:

Code:

Zone "Buttons|"
        someButton 	CycleTimeDisplayModes
ZoneEnd

Ah perfect - works a treat!

Quote:

Originally Posted by Geoff Waddington

Yeah, turns out it was pretty low hanging fruit

Fruit is very healthy.

In regards to the Automation Mode switching on each channel - is there a way I can adjust the .zon file to send a CHAR string to the TrackNameDisplay field that shows the automation mode just selected for a second or so then return to the Track Name? Similar behaviour that you have for the dB values for Pan and Volume touching.

WaveTrans · 04-05-2020, 11:49 AM

Quote:

Originally Posted by tdc

Hey Wavetrans, well done for finding the culprit, so annoying these little sounds whilst mixing. Its for this reason I always have two layouts on my consoles, usually on the same button with a Shift Key modifier for the second one. A 1:1 layout with all channels shown, and then a completely blank layout - for silence when I am in the critical listening phase.

I see. Shouldn´t worry about it then.

Thanks for the tip.

Found some other issue while I was testing.

It never get´s boring

Funkybot · 04-05-2020, 01:07 PM

Quote:

Originally Posted by Geoff Waddington

New build is up.

Added CycleTrackAutoMode, you can rearrange the order if you like, just make sure the last number is larger than the first number or it won't cycle:

Code:

	RecordArm|  		TrackUniqueSelect
	RecordArm|  		CycleTrackAutoMode [ 0 1 3 2 4 ]

How about this as the default Eucon behavior? Kind of a best of both worlds.

Code:

	RecordArm|  		TrackRecordArm
	Shift+RecordArm|  	TrackUniqueSelect
	Shift+RecordArm|	CycleTrackAutoMode [ 0 1 3 2 4 ]

New action works great BTW!

Funkybot · 04-05-2020, 01:15 PM

Two new pages up:

https://github.com/malcolmgroves/rea...eTrackAutoMode

https://github.com/malcolmgroves/rea.../TrackAutoMode

WaveTrans · 04-05-2020, 01:19 PM

Well, sorry, it´s me again
(with a re-defined question previously asked in post #7883)

During testing I observed that in all of my projects some tracks
suffered from
- a severe lack of either focusing FX/Plugins at all, or
- failing to recognize plugins (with zones)
- or showing them in mixed up order (i.e. not in the order of the FX menu)

After fiddling about for quite a while, I found that hidden tracks are the culprit.

If I delete/unhide all hidden tracks from a project,
FX-focus works just fine.
If there is one hidden track, all tracks beyond this track show faulty FX focus.

Is this some known issue?
What can I do about it apart from deleting/unhiding (numerous) hidden tracks?

Any ideas, please?

Geoff Waddington · 04-05-2020, 01:34 PM

Quote:

Originally Posted by tdc

In regards to the Automation Mode switching on each channel - is there a way I can adjust the .zon file to send a CHAR string to the TrackNameDisplay field that shows the automation mode just selected for a second or so then return to the Track Name? Similar behaviour that you have for the dB values for Pan and Volume touching.

Great idea !

Added in new build below.

Geoff Waddington · 04-05-2020, 01:36 PM

Quote:

Originally Posted by Funkybot

How about this as the default Eucon behavior? Kind of a best of both worlds.

Code:

	RecordArm|  		TrackRecordArm
	Shift+RecordArm|  	TrackUniqueSelect
	Shift+RecordArm|	CycleTrackAutoMode [ 0 1 3 2 4 ]

Yup, the EuCon .zon file needs lots of work, it's mostly experimental right now

Geoff Waddington · 04-05-2020, 01:37 PM

Quote:

Originally Posted by WaveTrans

Well, sorry, it´s me again
(with a re-defined question previously asked in post #7883)

During testing I observed that in all of my projects some tracks
suffered from
- a severe lack of either focusing FX/Plugins at all, or
- failing to recognize plugins (with zones)
- or showing them in mixed up order (i.e. not in the order of the FX menu)

After fiddling about for quite a while, I found that hidden tracks are the culprit.

If I delete/unhide all hidden tracks from a project,
FX-focus works just fine.
If there is one hidden track, all tracks beyond this track show faulty FX focus.

Is this some known issue?
What can I do about it apart from deleting/unhiding (numerous) hidden tracks?

Any ideas, please?

Sounds like a bug in the code, not taking hidden tracks into account, will investigate.

Geoff Waddington · 04-05-2020, 01:40 PM

New build is up.

Extends the CycleTrackAutoMode capabilities.

If you give it a display Widget, it will display the mode for a second or so:

Code:

	RecordArm|  		TrackRecordArm
	Shift+RecordArm|  	TrackUniqueSelect
	Shift+RecordArm|	CycleTrackAutoMode Display| [ 0 1 3 2 4 ]

Funkybot · 04-05-2020, 02:21 PM

Quote:

Originally Posted by Geoff Waddington

New build is up.

Extends the CycleTrackAutoMode capabilities.

If you give it a display Widget, it will display the mode for a second or so:

Code:

	RecordArm|  		TrackRecordArm
	Shift+RecordArm|  	TrackUniqueSelect
	Shift+RecordArm|	CycleTrackAutoMode Display| [ 0 1 3 2 4 ]

So like?

Code:

	Shift+RecordArm|	CycleTrackAutoMode DisplayUpper [ 0 1 3 2 4 ]

or

Code:

	Shift+RecordArm|	CycleTrackAutoMode DisplayUpper| [ 0 1 3 2 4 ]

Geoff Waddington · 04-05-2020, 03:05 PM

Quote:

Originally Posted by Funkybot

So like?

Code:

	Shift+RecordArm|	CycleTrackAutoMode DisplayUpper| [ 0 1 3 2 4 ]

Yes, don't forget the "|"s get replaced by numbers so there will be:

RecordArm1 -> DisplayUpper1
RecordArm2 -> DisplayUpper2
RecordArm3 -> DisplayUpper3
RecordArm4 -> DisplayUpper4
etc.

MalcolmG · 04-05-2020, 03:34 PM

Quote:

Originally Posted by Geoff Waddington

Ok, now remind me what, other than the GUI, is left to do to get to version 1.0 ?

Only thing holding me up is the bug invoking custom actions from a Fader14bit (unless you've fixed that in the last couple of builds)

https://forums.cockos.com/showpost.p...postcount=5050

Funkybot · 04-05-2020, 03:44 PM

Quote:

Originally Posted by Geoff Waddington

Yes, don't forget the "|"

Thought that was a distinct possibility. That was the "or" option. Got it!

tdc · 04-05-2020, 03:48 PM

Quote:

Originally Posted by Geoff Waddington

New build is up.

Extends the CycleTrackAutoMode capabilities.

If you give it a display Widget, it will display the mode for a second or so:

Wow that was quick! Works here as expected :-)

For V2.0 would be worth investigating whether CSI could control the LED on the Rec Button to mirror Track automation writing state (Write, Touch or Latch).

Thanks Geoff.

Geoff Waddington · 04-05-2020, 04:03 PM

Quote:

Originally Posted by MalcolmG

Only thing holding me up is the bug invoking custom actions from a Fader14bit (unless you've fixed that in the last couple of builds)

https://forums.cockos.com/showpost.p...postcount=5050

Took another look at that post.

Even though the first run reports 16384 resolution, take a close look at all the val numbers.

They are all divisible exactly by 128, so it looks like they are indeed 7 bit values, even though they are stated in 14 bit terms.

tdc · 04-05-2020, 04:04 PM

Quote:

Originally Posted by Funkybot

Two new pages up:
https://github.com/malcolmgroves/rea...eTrackAutoMode
https://github.com/malcolmgroves/rea.../TrackAutoMode

Great stuff!

Geoff Waddington · 04-05-2020, 05:00 PM

Quote:

Originally Posted by tdc

Note on EuCon Panning Controls

Seems great, just one oddity or is just a feature I don't understand :-)

Here on the S3, in Stereo Balance Mode, works as expected. Pan, Width control their respective Reaper parameters, and I can see the there are PanLeft and PanRight as well. These control those parameters (but of course if the Track is set to Stereo Balance Mode, these don't have any effect on the audio, but they do update the Pan Pots in the Track Panning block.

When I switch the Track to Dual Pan, the S3 has a small bug in that the knobs labelled Pan and Width now control the PanLeft and PanRight parameters, and the PanLeft and PanRight knobs control their respective parameters.

Did some further investigation.

This happens even if CSI is configured for just Pan/Width.

So it would appear to be a Reaper thing, unless I'm missing something here, which is entirely possible

tdc · 04-05-2020, 06:08 PM

Quote:

Originally Posted by Geoff Waddington

Did some further investigation.
This happens even if CSI is configured for just Pan/Width.

So it would appear to be a Reaper thing, unless I'm missing something here, which is entirely possible

I have a feel you are right on. Might be time alert the Cockos wizards to this less than intuitive behaviour.

Created a Feature Request: https://forum.cockos.com/showthread....63#post2267163

MalcolmG · 04-05-2020, 06:14 PM

Quote:

Originally Posted by Geoff Waddington

Took another look at that post.

Even though the first run reports 16384 resolution, take a close look at all the val numbers.

They are all divisible exactly by 128, so it looks like they are indeed 7 bit values, even though they are stated in 14 bit terms.

I can probably live with that (lack of precision). It's when I drive it from CSI instead that the val is always coming out as 63, regardless of the position on the fader.

Am I missing something? Even if I go back and define it as a Fader7Bit, the val is always 63 through CSI, but works directly through Reaper.

tdc · 04-05-2020, 08:02 PM

Just for completeness, I thought I would post that I realised that Latch Preview was being missed, but simply calling Mode 5 selects this.

Code:

	RecordArm|  		TrackUniqueSelect
	RecordArm|  		CycleTrackAutoMode Display| [ 0 1 3 2 4 5 ]

Funkybot · 04-05-2020, 08:20 PM

Quote:

Originally Posted by tdc

Just for completeness, I thought I would post that I realised that Latch Preview was being missed, but simply calling Mode 5 selects this.

Code:

	RecordArm|  		TrackUniqueSelect
	RecordArm|  		CycleTrackAutoMode Display| [ 0 1 3 2 4 5 ]

Adding to the Wiki now. Thanks!

Funkybot · 04-05-2020, 08:33 PM

New page up just to formally document commenting in CSI .mst and .zon files.

https://github.com/malcolmgroves/rea...iling-Comments

mschnell · 04-05-2020, 10:17 PM

Thanks for any decent documentation !
-Michael

tdc · 04-06-2020, 08:01 AM

I am starting to add additional surfaces now and have been playing with the Midi Fighter Twister, and am a little confused as to the correct method for specifying an Encoder.

I am observing two issues.

1. It appears that there is some acceleration on the encoder, but it appears to be opposite. When I turn the knob fast, the response in ReaEQ is slower, and when I turn the knob slow the response in ReaEQ is faster :-)

2. If I set the .mst to be a non-plain variant, I am getting some odd jittery behaviour, where the parameters in Reaper follow as expected and then suddenly jump to full scale.

Code:

Widget Rotary6
	Encoder b0 05 3f
	FB_Encoder b0 05 41
WidgetEnd

In a Midi Monitoring app I can see that the MFT is only putting out two values as expected, but in the CSI console I can see all sorts of values.

Here is the Example of Midi Data input

Code:

00:58:28.376	From Midi Fighter Twister	Control	1	B0 05 3F
00:58:28.380	From Midi Fighter Twister	Control	1	B0 05 3F
00:58:28.601	From Midi Fighter Twister	Control	1	B0 05 3F
00:58:28.723	From Midi Fighter Twister	Control	1	B0 05 41
00:58:28.888	From Midi Fighter Twister	Control	1	B0 05 3F
00:58:28.959	From Midi Fighter Twister	Control	1	B0 05 41

And the code as seen in CSI Console (Note I have trimmed many of the repeats to reduce the size)

Code:

IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 -0.009921
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.004960
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.002976
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.002976
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 0.125000
IN <- MFTwister Rotary6 0.187500
IN <- MFTwister Rotary6 0.125000
IN <- MFTwister Rotary6 0.125000
IN <- MFTwister Rotary6 0.125000
IN <- MFTwister Rotary6 -0.004960
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.001984
IN <- MFTwister Rotary6 -0.002976
IN <- MFTwister Rotary6 0.125000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 0.625000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 -0.009921
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 0.625000
IN <- MFTwister Rotary6 -0.019841
IN <- MFTwister Rotary6 1.250000
IN <- MFTwister Rotary6 -0.004960

tdc · 04-06-2020, 08:36 AM

Just read through the Wiki again to see if I could find any reference to some mapping functions, I found the Stepped section which is close, but no cigar. Perhaps I have missed it somewhere, but thought I would add this here as an idea in case not.

It would be helpful to be able to set a range of values that the incoming message generator's values would be mapped to. A perfect case is a 7bit pot controlling a HPF. I will never (99% of the time) need to set this HPF above 500hz, so I would love to map the 0-127 range to 20-500hz. I suspect that at the .zon file level Hertz is not relevant, so it would be set in terms of (0.0 - 1.0) and it would be up to the programmer of the zon file to calculate the rate they wish.

Whilst an encoder would be able to get you more finer control, it still allows you to travel the entire distance of parameter values. I find that physical interfaces are vastly more creative and calming when the range is restricted. (Lexicon 960L I am talking to you!)

Funkybot · 04-06-2020, 08:47 AM

tdc, have you seen the EncoderPlainReverse section of the Wiki?

https://github.com/malcolmgroves/rea...erplainreverse

If you're knobs are setup as Encoders in the MFTwister Utility, you probably want to try out this Widget type in CSI.

That won't help with narrowing down parameter ranges, which isn't yet possible unless you want to use stepped parameters. At which point, just combine that widget type with the stepped parameters in your fx.zon.