I guess that’s the price we pay for being able to ToggleScrollLink from within the surface Zone. As you say, it used to be in the Prefs
Having it dynamically available per surface is great.
The only clash here is that there is no SetScrollLink available but only ToggleScrollLink is avalilable.
I don't see how I would ever want to have one surface with ScrollLink ON-by-default, while having another same surface with ScrollLink OFF-by-default. Once they start running, user can enable/disable at will, that's fine.
One more case where I want to have the same surface data on several surfaces is for development reasons.
Well, you actually can't have one Surface with it on and one with it off, Scroll Link is at a Page level, therein lies the issue.
__________________
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
Having it dynamically available per surface is great.
The only clash here is that there is no SetScrollLink available but only ToggleScrollLink is available.
Right, the issue is whether SetScrollLink should even exist or if it should once again be an option on the Page config.
__________________
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
Well, you actually can't have one Surface with it on and one with it off, Scroll Link is at a Page level, therein lies the issue.
Is that a good thing or a bad thing?
Would it be more flexible if it was per surface?
Like, me and my friend are mixing together, in one control room, each on their own iPad, then, one could have ScrollLink ON while the other one could have it OFF, where one is flying over the whole mix while the other one is showing only drums, for example. Just thinking out loud here.
Thanks, it really is an issue because, outside of modifiers, TrackNavigationManager, where Scroll Link lives, is the only thing that is at a Page level, since Track banking applies to all Surfaces.
It's tricky to get just right, because there are no Widgets or Actions at a Page level.
This might be a dumb question, but would it make sense to eventually make it a surface-level action then just add ToggleScrollLink to the Broadcast/Receive list?
Is that a good thing or a bad thing?
Would it be more flexible if it was per surface?
Like, me and my friend are mixing together, in one control room, each on their own iPad, then, one could have ScrollLink ON while the other one could have it OFF, where one is flying over the whole mix while the other one is showing only drums, for example. Just thinking out loud here.
Might be a good idea, but there is a fundamental design issue that more or less precludes that -- an internal class named TrackNavigationManager exists at a Page level, for good reason, you generally want to aggregate all your surfaces into one large logical Surface.
TrackNavigationManager takes care of all the Surface offsets, banking, etc., and generally keeps things in synch when you have, say, an 8 Fader MCU, and two 8 Fader extenders that you want to behave like one single 24 Track Surface.
Six years ago, when this project started, the fashion was one of this type of emulation of large format consoles, Neve, SSL, API, etc.
Times have changed somewhat, we still want to support the aggregate concept, but a lot more use cases like yours are developing, we probably need to update TrackNavigationManager for the more modern times, just one more thing on the old plate, along with EuCon, Track colors, Broadcast/Receive of Banking Actions and ToggleEnableFocusedFXMapping, auto plugin Zone generation...
__________________
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
This might be a dumb question, but would it make sense to eventually make it a surface-level action then just add ToggleScrollLink to the Broadcast/Receive list?
Well, adding to the previous post, think of what would happen if you had an MCU and two extenders, and had Scroll Link on for only the middle one, and you selected a Track way down the list from where you are currently banked, things would look pretty strange
__________________
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
Well, adding to the previous post, think of what would happen if you had an MCU and two extenders, and had Scroll Link on for only the middle one, and you selected a Track way down the list from where you are currently banked, things would look pretty strange
I just configured ToggleScrollLink on both my X-Touch and the Extender. Can't think of a reason why they should be set different...
I just configured ToggleScrollLink on both my X-Touch and the Extender. Can't think of a reason why they should be set different...
Well, actually they can't be set different.
If, by configured, you mean you mapped ToggleScrollLink to a button on both Surfaces, you have just provided two points of control of the same thing.
__________________
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
Well, adding to the previous post, think of what would happen if you had an MCU and two extenders, and had Scroll Link on for only the middle one, and you selected a Track way down the list from where you are currently banked, things would look pretty strange
Totally makes sense.
Sounds like the best solution is the "copy the zone folders, but don't include "OnInitialization ToggleScrollLink" in one.
And just to add some more roux to this gumbo, ToggleSynchPageBanking suffers all of the same issues.
Wonder if it's easier to just put them both back in Page config as check boxes for purposes of initialization, and allow changing them on the fly with the Toggle Actions.
__________________
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
And just to add some more roux to this gumbo, ToggleSynchPageBanking suffers all of the same issues.
Wonder if it's easier to just put them both back in Page config as check boxes for purposes of initialization, and allow changing them on the fly with the Toggle Actions.
I'd still think we'd have the same issue if you shared a zone folder between two surfaces where the toggle actions would fire twice on a page-level action, but your approach would allow AtmanActive to set the correct default state and just keep it there, which I think is desirable and an improvement over current-state.
I'd still think we'd have the same issue if you shared a zone folder between two surfaces where the toggle actions would fire twice on a page-level action
Yes, but that would only be true if the Action were in OnInitialization, or if you pushed the buttons on both Surfaces simultaneously
__________________
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
Having it dynamically available per surface is great.
The only clash here is that there is no SetScrollLink available but only ToggleScrollLink is avalilable.
It isn't per surface though, it's global, akin to modifiers.
Wonder if it's easier to just put them both back in Page config as check boxes for purposes of initialization, and allow changing them on the fly with the Toggle Actions.
As long as we can still change it on the fly, then yes, do this
Wonder if it's easier to just put them both back in Page config as check boxes for purposes of initialization, and allow changing them on the fly with the Toggle Actions.
As long as we can still change it on the fly, then yes, do this
The only thing I don't like is it clutters the config panel, new users have enough to worry about without these arcane concepts.
Wonder if we can spit the difference.
Since we required a manual edit of a Zone file to accomplish this, could we leave it out of the config page and have it as a manual edit in CSI.ini ?
Code:
Page "HomePage" NoScrollLink UseSynchPageBanking
would be the default, and a savvy user could change them in CSI.ini directly.
Dunno, what do you think folks ?
__________________
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
One more thing, before I forget:
It would be useful to have "ena/disa" state per surface in the main config (CSI.ini), to be able to quickly choose active surfaces without having to completely remove (and configure again and again).
Same like how MIDI interfaces in Reaper can be configured but still be enabled or disabled.
One more thing, before I forget:
It would be useful to have "ena/disa" state per surface in the main config (CSI.ini), to be able to quickly choose active surfaces without having to completely remove (and configure again and again).
Same like how MIDI interfaces in Reaper can be configured but still be enabled or disabled.
Hmmm...
I presume you want this for testing/development ?
Would have to weigh it against the confusion factor of regular users who might be stumped as to why things weren't working.
This is the first request for this feature...
__________________
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
One more thing, before I forget:
It would be useful to have "ena/disa" state per surface in the main config (CSI.ini), to be able to quickly choose active surfaces without having to completely remove (and configure again and again).
Same like how MIDI interfaces in Reaper can be configured but still be enabled or disabled.
I'm not sure what your use-case is, but you could always create different "Pages" in CSI with different surfaces included/excluded.
Yes, testing, development, but also ad-hoc recording sessions:
Let's imagine I'm about to record a 5-member band, every musician in their own studio (or half way across the world), and each has their phone/ipad with TouchOSC and a dedicated surface. Now, while I'm setting this up I need to keep track of ports and IP addresses and program everything in CSI. Now, at the end of the recording session I want to turn all those surfaces off, but I don't want to completely delete them as I will have another recording session with same people a few weeks later.
Quote:
Originally Posted by Geoff Waddington
Would have to weigh it against the confusion factor of regular users who might be stumped as to why things weren't working.
Simple, just default the checkbox to ON on new entries.
By the way, can I comment/uncomment lines in CSI.ini with //? That would easily give me the same thing.
Also, does CSI support TCP OSC in addition to UDP?
But then, what I'm missing is last-used-page information in CSI.ini.
It is great to be able to change pages programmatically, but, in my humble opinion, CSI should be able to also remember which page I used last and default to that one when Reaper starts. Or, since this can be a nuisance for some use cases, have one more setting in CSI.ini (UI), a drop-down, where user can choose the default page. Factory default would, of course be DefaultPage="HomePage".
Or just a simple checkbox: "remember the last used page" ON/OFF.
Simple, just default the checkbox to ON on new entries.
Ux principles say every time you add an option you risk overloading the new user even more, it's always good to be as minimalist as possible.
Quote:
Originally Posted by AtmanActive
By the way, can I comment/uncomment lines in CSI.ini with //? That would easily give me the same thing.
You can't right now, but it's a great idea, will add it !
Quote:
Originally Posted by AtmanActive
Also, does CSI support TCP OSC in addition to UDP?
No, just UDP, TCP has the unfortunate effect of adding latency.
__________________
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
But then, what I'm missing is last-used-page information in CSI.ini.
That's because it's not in CSI.ini, it's in the Reaper project file
If you open a Reaper project file (.rpp) with a text editor and scroll to the very bottom, you will see CSI remembers the Page and Track Bank settings (if you save the project), so that the next time you collaborate with your worldwide team on a particular project, as in your example, you will open the project to the exact Page you were on when you last saved the project.
__________________
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
That's because it's not in CSI.ini, it's in the Reaper project file
If you open a Reaper project file (.rpp) with a text editor and scroll to the very bottom, you will see CSI remembers the Page and Track Bank settings (if you save the project), so that the next time you collaborate with your worldwide team on a particular project, as in your example, you will open the project to the exact Page you were on when you last saved the project.
Done! Added a note to the Pages section, as well as another to the TrackBank action. Much easier to maintain the Wiki now that it's up to date and includes information on each action.
...I didn't know where else to put this. Does it belong on the "Zones" page? Does it belong under the "Encoder" section of the "Message Generators" page? Does it belong the "Stepped Parameters" page?
Just decided to lump it into one. I realized that I took this information out when we transitioned from the V1 to V2 wiki. It was previously on the Encoders page.
If anyone has a better idea of where/how to organize this, please let me know. Thanks!
Done! Added a note to the Pages section, as well as another to the TrackBank action. Much easier to maintain the Wiki now that it's up to date and includes information on each action.
Yes, and thanks for making it so, as Picard would say
__________________
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
Last edited by Geoff Waddington; 08-11-2022 at 04:26 PM.
...I didn't know where else to put this. Does it belong on the "Zones" page? Does it belong under the "Encoder" section of the "Message Generators" page? Does it belong the "Stepped Parameters" page?
Just decided to lump it into one. I realized that I took this information out when we transitioned from the V1 to V2 wiki. It was previously on the Encoders page.
If anyone has a better idea of where/how to organize this, please let me know. Thanks!
My 2 cents:
Take that page and Stepped Parameters and add both of them to the Encoders section of the Message Generators page, Encoders is the last section already, so you would just be extending it -- a lot .
__________________
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
Reworked colors, so please check Windows, Mac, and OSC, to be sure everything is working.
Didn't get to incorporate theme default Track color yet, but if the color is 0, it becomes 64, 64, 64.
You can now put comments in CSI.ini, but be aware that if you have a section commented out and you use the config GUI, and save CSI.ini, the commented sections will be lost.
The CSI.ini Page line can now optionally include NoSynchPages and/or UseScrollLink to override the default behaviour.
Note these are optional, so existing CSI.ini files parse just fine.
Code:
Page "HomePage"
Code:
Page "HomePage" NoSynchPages
Code:
Page "HomePage" UseScrollLink
Code:
Page "HomePage" NoSynchPages UseScrollLink
Code:
Page "HomePage" UseScrollLink NoSynchPages
__________________
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
Take that page and Stepped Parameters and add both of them to the Encoders section of the Message Generators page, Encoders is the last section already, so you would just be extending it -- a lot .
I originally had it all Encoders, but stepped params also applies to buttons so that was always my concern with it being there.
How about we keep Stepped Params and Toggles as one page, just because I think that's important for visibility, then provide a link to the new Encoders section where I have the limited parameter ranges, deltas, and custom curves?
I originally had it all Encoders, but stepped params also applies to buttons so that was always my concern with it being there.
How about we keep Stepped Params and Toggles as one page, just because I think that's important for visibility, then provide a link to the new Encoders section where I have the limited parameter ranges, deltas, and custom curves?
Sure, sounds good.
__________________
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
Big thanks to Geoff Waddington, Funkybot and MixMonkey. Without your work this wouldn't be possible.
Looking very nice! I was hoping someone would pull my iPad mixer apart and make their own thing out of it!
Increasing the size of the buttons obviously aids usability, do you have any plans for the FX section? on another page perhaps? It does use a lot of space....
Incidentally, credit must also go to @puck, I used several of his ideas in the mixer.
Linear Mode
