|
|
|
06-24-2020, 06:35 AM
|
#9641
|
Human being with feelings
Join Date: Aug 2019
Location: UK
Posts: 65
|
I have a button labelled Master on my surface. It is an FB_twostate button. Here's how it's defined in my mst file:
Widget Master
Press 90 3a 7f
FB_TwoState 90 3a 7f 90 3a 00
WidgetEnd
In my zon file I have set it to GoZone "Master" on press and then to GoZone Home on the second press.
The Master zone controls everything on my master channel (obvs.).
It works well (result!), BUT....
When Master zome is not active, the LED is on but dull (good). Is there a way to make it glow bright when it's active? Note: The other buttons do this.
Thanks, gang!
Simon
Last edited by Pompeysie; 06-24-2020 at 06:42 AM.
|
|
|
06-24-2020, 07:07 AM
|
#9642
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
Quote:
Originally Posted by Geoff Waddington
OK, one more thing eliminated, I think you will find we are quite relentless, we WILL get to the bottom of this !
|
Ha ha, love that!
Seriously, my other questions are more pressing for me personally. (I have temp-fixed the jumping issue by using SelectedTrackNavigator instead -- works for now).
|
|
|
06-24-2020, 07:21 AM
|
#9643
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Pompeysie
I have a button labelled Master on my surface. It is an FB_twostate button. Here's how it's defined in my mst file:
Widget Master
Press 90 3a 7f
FB_TwoState 90 3a 7f 90 3a 00
WidgetEnd
In my zon file I have set it to GoZone "Master" on press and then to GoZone Home on the second press.
The Master zone controls everything on my master channel (obvs.).
It works well (result!), BUT....
When Master zome is not active, the LED is on but dull (good). Is there a way to make it glow bright when it's active? Note: The other buttons do this.
Thanks, gang!
Simon
|
That's actually a design request, and a good one at that !
It will be an extension of colour support syntax, maybe something like
Code:
Zone "aZone"
aWidget anAction { 0 1 }
ZoneEnd
to indicate which state should be lit.
__________________
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
|
|
|
06-24-2020, 07:22 AM
|
#9644
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by cemark
Ha ha, love that!
Seriously, my other questions are more pressing for me personally. (I have temp-fixed the jumping issue by using SelectedTrackNavigator instead -- works for now).
|
Cool, ask away with the other questions.
__________________
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
|
|
|
06-24-2020, 07:23 AM
|
#9645
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
Quote:
Originally Posted by Geoff Waddington
Cool, ask away with the other questions.
|
They are the ones in the separate thread
|
|
|
06-24-2020, 07:27 AM
|
#9646
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
Quote:
Originally Posted by cemark
They are the ones in the separate thread
|
Please, start at post #2, where it says "Update"
Last edited by cemark; 06-24-2020 at 07:28 AM.
Reason: wrong number
|
|
|
06-24-2020, 09:17 AM
|
#9647
|
Human being with feelings
Join Date: Aug 2019
Location: UK
Posts: 65
|
Quote:
Originally Posted by Geoff Waddington
That's actually a design request, and a good one at that !
It will be an extension of colour support syntax, maybe something like
Code:
Zone "aZone"
aWidget anAction { 0 1 }
ZoneEnd
to indicate which state should be lit.
|
On this Faderport V2 (yes, that!) there are a few other buttons that might benefit from something similar. Have a look at this image of the unit:
https://d1aeri3ty3izns.cloudfront.ne...00/preview.jpg
Below the rotary encoder,in the middle of the unit, you'll see buttons for Pan, Channel and Scroll.
THe idea is that you press the pan button (change from dull to bright light) and use the encoder to control track pan. Channel is not that useful but, again, it's meant to control a different function using the jog wheel, previous and next buttons (a press of this button dulls the Pan button LED and turns the Channel button bright). Scroll button does the same. You get the idea.
Is this possible?
|
|
|
06-25-2020, 12:52 PM
|
#9648
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
Aaallrightee then ...
Here follows an updated list of my remaining questions from the separate thread (which we now will let die):
1. The rotary. I got it produce very basic operation. My question is posed in this post: https://forum.cockos.com/showpost.ph...postcount=9628
I tried
Code:
Widget Rotary1
Encoder b0 10 7f [ < 41-7f > 01-3f ]
WidgetEnd
which as far as I understand should be correct, but the rotary is just dead with this definition.
Note also, that there's an error in the text copied from the manual. It says bit 0-6, but it should be bit 1-6.
2. The magical jump!
3. This question: https://forum.cockos.com/showpost.ph...postcount=9627
4. Solved
5. Solved
6. Question here: https://forum.cockos.com/showpost.ph...01&postcount=8
7. Question here: https://forum.cockos.com/showpost.ph...39&postcount=9
8. Solved
9. SOLVED! In this example Prev works but Next does not. How come?
Code:
Zone "VST: Thorus (UVI)"
FocusedFXNavigator
Shift+Rotary1 FXParam 0 "Speed"
Rotary1 FXParam 1 "Depth"
Next FXParam "7" "NumVoices" [ 0.0 0.16 0.33 0.50 0.66 0.83 1.0 ]
Prev FXParam "7" "NumVoices" [ 1.0 0.83 0.66 0.50 0.33 0.16 0.0 ]
Fader1 FXParam 8 "Mix"
ZoneEnd
Edit: In another zone, the same structure (but different values) both Next and Prev work perfectly.
Last edited by cemark; 06-25-2020 at 01:46 PM.
Reason: More info
|
|
|
06-25-2020, 05:37 PM
|
#9649
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by cemark
Aaallrightee then ...
Here follows an updated list of my remaining questions from the separate thread (which we now will let die):
1. The rotary. I got it produce very basic operation. My question is posed in this post: https://forum.cockos.com/showpost.ph...postcount=9628
I tried
Code:
Widget Rotary1
Encoder b0 10 7f [ < 41-7f > 01-3f ]
WidgetEnd
which as far as I understand should be correct, but the rotary is just dead with this definition.
Note also, that there's an error in the text copied from the manual. It says bit 0-6, but it should be bit 1-6.
|
Difficult to say without seeing the raw output from the control. Here's what I use for an MCU rotary:
Code:
Widget Rotary1
Encoder b0 10 7f [ > 01-0f < 41-4f ]
FB_Encoder b0 10 7f
WidgetEnd
For use with Pan, I have this in the Zone:
Code:
Rotary| TrackPan "0" [ (0.005,0.005,0.01,0.02,0.02,0.02,0.04,0.04,0.04,0.06,0.08,0.1,0.1,0.1,0.1) ]
I'll redefine my MCU as a one fader device and see if I get the same thing, bear with me.
Quote:
3. What am I supposed to map my rotary to, to get the standard mousewheel zoom to operate?
|
I don't believe you can do that, just as you can't map Reaper Actions that are MIDI CC/OSC only.
What you could do is create a different page where your rotary is defined as a pair of Press commands (one for CW, the other for CCW) This is how we get the MCU JogWheel to play ball, as you turn it sends a series of presses, presses that be mapped to useful Reaper Actions like 1011 and 1012.
Quote:
6. Why doesn't Next work here?
[Code]
Zone "VST3: FabFilter Pro-Q 3 (FabFilter)" "ProQ"
FocusedFXNavigator
Write FXParam 0 "Use band 1" // Doesn't work
Rotary1 FXParam 2 "Freq band 1"
Fader1 FXParam 3 "Gain band 1"
Shift+Rotary1 FXParam 7 "Q band 1"
Next GoZone "ProQ Band 2" // This doesn't work
ZoneEnd
|
Don't know why the GoZone doesn't work, looks ok. For "Use band 1" try:
Code:
Toggle+Write FXParam 0
It's best to avoid VST3 plugins if you can, they tend to just stop working with CSI.
Quote:
7. I'm trying to make a raw parameter file for FabFilter Saturn. But when the insert is finally done, only parameter 508 and up (through 1034) remains in the window. That is, parameters 0 through 507 are cut.
|
This sounds like a bug in the console output, too many parameters. I've attached a list for the VST2 version I had.
Quote:
9. In this example Prev works but Next does not. How come?
Code:
Zone "VST: Thorus (UVI)"
FocusedFXNavigator
Shift+Rotary1 FXParam 0 "Speed"
Rotary1 FXParam 1 "Depth"
Next FXParam "7" "NumVoices" [ 0.0 0.16 0.33 0.50 0.66 0.83 1.0 ]
Prev FXParam "7" "NumVoices" [ 1.0 0.83 0.66 0.50 0.33 0.16 0.0 ]
Fader1 FXParam 8 "Mix"
ZoneEnd
Edit: In another zone, the same structure (but different values) both Next and Prev work perfectly.
|
They can be finnicky about values, these work here:
Code:
RotaryPushC1 FXParam 7 [ 1.0 0.84 0.67 0.5 0.34 0.17 0.0 ]
RotaryPushC2 FXParam 7 [ 0.0 0.17 0.34 0.5 0.67 0.84 1.0 ]
Also remember that stepped parameters will only 'wrap around' when going from a larger value to a smaller one. So if Voices is set to '2' pressing RotaryC1 won't do anything, as CSI prevents the jump from '2' to '8'
Last edited by MixMonkey; 09-06-2020 at 11:44 AM.
|
|
|
06-25-2020, 11:22 PM
|
#9650
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
MixMonkey, thanks so much!
Comments:
1. I see you have 4 bits (01-0f), I have 6 bits (01 - 3f, and 41 - 7f). I have checked the raw output, and it seems I can get most (or all) values. The manual doesn't mention any skips.
I have tried both
Code:
Encoder b0 10 7f [ < 41-7f > 01-3f ] // This does not work
and your rumbers.
#3. Aha!
#6 Edit 2: SOLVED!
Edit: What is the issue with VST3? I have mostly VST3:s, and they all work fine with CSI.
#7 Thanks!
Last edited by cemark; 06-25-2020 at 11:46 PM.
Reason: More info
|
|
|
06-26-2020, 02:43 AM
|
#9651
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by cemark
I have tried both
Code:
Encoder b0 10 7f [ < 41-7f > 01-3f ] // This does not work
|
From the manual:
Session Navigator Encoder: B0, 3C
Try that and see what happens.
__________________
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
|
|
|
06-26-2020, 03:11 AM
|
#9652
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
The manual has some errors, unfortunately ...
I checked the output -- it's b0 10 ...
( I tried b0 3c just for the heck of it )
|
|
|
06-26-2020, 03:54 AM
|
#9653
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by cemark
Edit: What is the issue with VST3? I have mostly VST3:s, and they all work fine with CSI.
|
With VST3, at a certain point, for no apparent reason, the plugin will stop receiving input from the surface.
The return (FB) path continues to work, that is to say that turning a control on the screen is reflected on the surface.
It was never given much attention because everyone just used VST2 instead. See how you get on, the bug may not even exist anymore.
|
|
|
06-26-2020, 03:55 AM
|
#9654
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by cemark
The manual has some errors, unfortunately ...
I checked the output -- it's b0 10 ...
( I tried b0 3c just for the heck of it )
|
It's usually best to examine the raw surface output using a MIDI monitor, rather than take the documentation as gospel
|
|
|
06-26-2020, 04:00 AM
|
#9655
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by cemark
1. I see you have 4 bits (01-0f), I have 6 bits (01 - 3f, and 41 - 7f). I have checked the raw output, and it seems I can get most (or all) values. The manual doesn't mention any skips.
|
Make absolutely sure you get ALL the values or just include the ones that you have seen. My Mackie C4 behaves differently to the MCU, it only has 5 values:
Code:
Widget RotaryA1
Encoder b0 00 7f [ > 01 04 08 0C 0f < 41 44 48 4c 4f ]
FB_Encoder b0 00 7f
WidgetEnd
|
|
|
06-26-2020, 04:07 AM
|
#9656
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
Thanks, MixMonkey and Geoff!
Here's what I discovered regarding the rotary: With this simple definition
Code:
Widget Rotary1
Encoder b0 10 7f
WidgetEnd
I get basic operation. However, using CSI edit mode in Reaper, I see that for CW turns, I get values between 0 and 0.5, and for CCW turns, I get between 0 and -0.5.
Instead of hacking away with the hex code, is there some simpler way to extend it so I get the full range, i.e. 0-1.0 and 0-(-1.0)?
Also, I think I doscovered a bug. If I add this comment to the definition:
Code:
Widget Rotary1
Encoder b0 10 7f // Gives basic operation
WidgetEnd
The rotary dies.
|
|
|
06-26-2020, 04:13 AM
|
#9657
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
Quote:
Originally Posted by MixMonkey
Make absolutely sure you get ALL the values or just include the ones that you have seen. My Mackie C4 behaves differently to the MCU, it only has 5 values:
Code:
Widget RotaryA1
Encoder b0 00 7f [ > 01 04 08 0C 0f < 41 44 48 4c 4f ]
FB_Encoder b0 00 7f
WidgetEnd
|
Yes, but I'm unsure how to be sure :-) Well, I took the advise of FunkyBot and generated about 500 data points from the rotary. I pasted them into Excel, removed copies, and finally sorted them. It turned out that different runs gave me different values. And I could see almost all possible ones.
However, there are 6 bits, so there are 64 possibilities. It would be a nightmare to try to map this out.
That's why I would love it if there's a way to to extend the range somehow (I get from 0 through +- 0.5)
|
|
|
06-26-2020, 04:31 AM
|
#9658
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by cemark
Also, I think I doscovered a bug. If I add this comment to the definition:
Code:
Widget Rotary1
Encoder b0 10 7f // Gives basic operation
WidgetEnd
The rotary dies.
|
I think the // comment syntax only applies to .zon files, so yes, a bug. You should be able to comment out a whole line with a single / though.
|
|
|
06-26-2020, 04:35 AM
|
#9659
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by cemark
I have tried both
Code:
Encoder b0 10 7f [ < 41-7f > 01-3f ] // This does not work
|
It isn't something really stupid like putting the > term first is it? (and losing the comment)
Code:
Encoder b0 10 7f [ > 01-3f < 41-7f ]
|
|
|
06-26-2020, 04:38 AM
|
#9660
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
Quote:
Originally Posted by MixMonkey
I think the // comment syntax only applies to .zon files, so yes, a bug. You should be able to comment out a whole line with a single / though.
|
Yes, now I remember seing something about that on the wiki
|
|
|
06-26-2020, 04:40 AM
|
#9661
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
Quote:
Originally Posted by MixMonkey
It isn't something really stupid like putting the > term first is it? (and losing the comment)
Code:
Encoder b0 10 7f [ > 01-3f < 41-7f ]
|
Thanks for sticking with me! But no. I deleted the comment, and tried both orders.
|
|
|
06-26-2020, 04:50 AM
|
#9662
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by cemark
Thanks for sticking with me! But no. I deleted the comment, and tried both orders.
|
In that case my best guess would be CSI is choking on the wider range being generated, but that's one for Geoff.
|
|
|
06-26-2020, 11:07 AM
|
#9663
|
Human being with feelings
Join Date: Jun 2020
Location: Paris
Posts: 244
|
Hi,
I've purchased a Faderport V2 and installed the MCU Kinkle following the manual.
It works but I encounter the following issues :
If I click on a item, the fader still controls the previous track until I do an action on the current track (mute, solo,...)
I need to click an item to control the track I want. If I click on TCP or MCP it remains on the previous track.
Plus, on Play mode, the timeline does not move anymore, the screen stays where the start marker is.
Last edited by Jibeji; 06-26-2020 at 11:13 AM.
|
|
|
06-26-2020, 02:16 PM
|
#9664
|
Human being with feelings
Join Date: Jun 2020
Posts: 2
|
Control volume of all selected tracks
I'm trying to map my Volume knob on my Console 1 to control track volume on all selected tracks.
Is there a way to do that?
I tried with SelectedTrackNavigator in my zone, but it seems like it only works when one track is selected.
I also tried to make a template zone "Tracks|" with TrackNavigator and including it in my "Home" zone.
Zone "Tracks|"
TrackNavigator
Volume TrackVolume
ZoneEnd
But this doesn't work as it doesn't know which track to handle.
If I then use instead:
Zone "Tracks|"
TrackNavigator
Volume| TrackVolume
ZoneEnd
And I make a Volume1 widget (while also keeping my original Volume widget), responding to the same midi-message as my original Volume widget, it kind of works. Now I can adjust volume on all selected tracks. But only if Track1 is selected. If i deselect Track1, (but still have other tracks selected in reaper, Track1's volume is responding to my volume knob.
If i deselect everything, Track1's volume is responding to my volume knob (as i would expect).
I hope it makes sense.
Bottom line is that I want one knob to control volume of all selected tracks.
Does anybody know how to do this?
Thanks,
Anders
|
|
|
06-26-2020, 05:08 PM
|
#9665
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by andersskibsted
I'm trying to map my Volume knob on my Console 1 to control track volume on all selected tracks.
Is there a way to do that?
I tried with SelectedTrackNavigator in my zone, but it seems like it only works when one track is selected.
I also tried to make a template zone "Tracks|" with TrackNavigator and including it in my "Home" zone.
Zone "Tracks|"
TrackNavigator
Volume TrackVolume
ZoneEnd
But this doesn't work as it doesn't know which track to handle.
If I then use instead:
Zone "Tracks|"
TrackNavigator
Volume| TrackVolume
ZoneEnd
And I make a Volume1 widget (while also keeping my original Volume widget), responding to the same midi-message as my original Volume widget, it kind of works. Now I can adjust volume on all selected tracks. But only if Track1 is selected. If i deselect Track1, (but still have other tracks selected in reaper, Track1's volume is responding to my volume knob.
If i deselect everything, Track1's volume is responding to my volume knob (as i would expect).
I hope it makes sense.
Bottom line is that I want one knob to control volume of all selected tracks.
Does anybody know how to do this?
Thanks,
Anders
|
I might be misunderstood but are u trying control multiple track volumes at once ? Why not just go the group or vca route. Vca groups are one of the features in CSI. Check out the wiki
I could be way off base in what ur trying to do. So just throwing it out there . Keep checking back the guys on this forum are good. Theyll help u out
|
|
|
06-27-2020, 10:40 AM
|
#9666
|
Human being with feelings
Join Date: Jun 2020
Posts: 2
|
Quote:
Originally Posted by Cragster
I might be misunderstood but are u trying control multiple track volumes at once ? Why not just go the group or vca route. Vca groups are one of the features in CSI. Check out the wiki
I could be way off base in what ur trying to do. So just throwing it out there . Keep checking back the guys on this forum are good. Theyll help u out
|
I'm not sure that VCA's are the solution. They're new to me, so I'll read up on it.
But what I want to do, is kinda simple. I want my volume knob on my controller to control volume on all selected tracks. And of course changing when I select other tracks...
|
|
|
06-27-2020, 01:24 PM
|
#9667
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by andersskibsted
I'm not sure that VCA's are the solution. They're new to me, so I'll read up on it.
But what I want to do, is kinda simple. I want my volume knob on my controller to control volume on all selected tracks. And of course changing when I select other tracks...
|
I would also suggest investigating VCAs, and Folders too.
The tricky part of your seemingly simple task is it makes you ask this question:
"What value is displayed on the Console 1 led rings ?"
Uh-oh, is it the low value of the selected tracks, the high value, an average, hmmmm..
Also what happens when you adjust -- do they all suddenly jump to the same value -- the value on the Console 1 led rings ?
Pretty messy, usually VCAs and/or Folders are the way to go.
__________________
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
|
|
|
06-28-2020, 05:55 AM
|
#9668
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
I was doing kinda well, and then ...
Now, suddenly, no FXZones work. Focus remains on the selected channel regardless of which FX I open, close or switch between.
I have removed all newly created FXZone files from the directory. The only ones that remain are the three ones I created days ago and haven't touch since. They were all working fine.
I have re-started my computer, re-started my FPv2, tried to Reset all surfaces, but the problem remains.
I have also checked in Reaper Preferences that everything seems good.
What's going on???
Edit: Everything defined in the main .zon file works fine. It's just the mapping of FXZones that has stopped working. (And the main .zon file is also untouched)
Last edited by cemark; 06-28-2020 at 06:04 AM.
Reason: More info
|
|
|
06-28-2020, 06:50 AM
|
#9669
|
Human being with feelings
Join Date: Jun 2014
Location: Sweden
Posts: 329
|
Update (more info): So, I asked myself: What _has_ changed?
Well, I bought and installed a couple of plugs from Softube. This required accessing my iLok account.
I checked my new Transient Shaper in Reaper and it worked. I then proceeded to create an FXZone for it. This also worked well (with the FPv2).
Then, I tried to switch focus to some other plugin, end there you go --- poof! Nothing.
The CSI system now does not seem to acknowledge any focused FX windows. I get the impression there's a "dangling reference" somewhere. But what do I know?
Weird ...
Edit: I have now checked with CSI edit mode. There's nothing being sent to the surface regardless of which FX windows I switch between.
Last edited by cemark; 06-28-2020 at 07:35 AM.
Reason: More info
|
|
|
06-29-2020, 02:33 PM
|
#9670
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
I'm putting together a Lemur template on an ipad, replicating some of the functionality I already had and extending it to others.
Can someone tell me how I get the track name from CSI ?
With Reaper I had this:
OSC config:
TRACK_NAME s/track/seltrack/content In the Lemur template I placed a text object inside a frame called "track" and called that text object "seltrack".
That gave it the OSC target "/track/seltrack"
I then gave this object a one-line script.
setattribute(seltrack, 'content', OSC_ARGS);
So, I have an .OST and a .ZON file for CSI.
How do I get the track name to an OSC device ?
In the C4emu TouchOSC example(picked up the editor) it's just a "DisplayUpperA1" for example. Could be it be that simple ? Sure hope that works with Lemur.
Last edited by airon; 06-29-2020 at 02:40 PM.
|
|
|
06-30-2020, 02:51 AM
|
#9671
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by airon
I'm putting together a Lemur template on an ipad, replicating some of the functionality I already had and extending it to others.
Can someone tell me how I get the track name from CSI ?
With Reaper I had this:
OSC config:
TRACK_NAME s/track/seltrack/content In the Lemur template I placed a text object inside a frame called "track" and called that text object "seltrack".
That gave it the OSC target "/track/seltrack"
I then gave this object a one-line script.
setattribute(seltrack, 'content', OSC_ARGS);
So, I have an .OST and a .ZON file for CSI.
How do I get the track name to an OSC device ?
In the C4emu TouchOSC example(picked up the editor) it's just a "DisplayUpperA1" for example. Could be it be that simple ? Sure hope that works with Lemur.
|
With the TouchOSC editor you can name your OSC Widgets directly in TouchOSC so it's pretty easy to do:
Code:
Widget ShowFXWindows
Control /ShowFXWindows
FB_Processor /ShowFXWindows
WidgetEnd
So, yours would look something like:
Code:
Widget ShowFXWindows
Control s/track/seltrack/content
FB_Processor s/track/seltrack/content
WidgetEnd
Then just use a Zone file in a normal way:
Code:
Zone "aZone"
TrackNavigator
ShowFXWindows SetShowFXWindows
ZoneEnd
And, of course, you would use a TrackNameDisplay Action.
__________________
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
|
|
|
06-30-2020, 06:26 AM
|
#9672
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Quote:
Originally Posted by Geoff Waddington
With the TouchOSC editor you can name your OSC Widgets directly in TouchOSC so it's pretty easy to do:
Code:
Widget ShowFXWindows
Control /ShowFXWindows
FB_Processor /ShowFXWindows
WidgetEnd
So, yours would look something like:
Code:
Widget ShowFXWindows
Control s/track/seltrack/content
FB_Processor s/track/seltrack/content
WidgetEnd
Then just use a Zone file in a normal way:
Code:
Zone "aZone"
TrackNavigator
ShowFXWindows SetShowFXWindows
ZoneEnd
And, of course, you would use a TrackNameDisplay Action.
|
Thank you, that's what I need. Phase 1 . Hopefully I can expand in to my MFTs at some point, and fix my damn Faderport 16 MST. That thing is gold for send control once I can get it working.
|
|
|
06-30-2020, 01:32 PM
|
#9673
|
Human being with feelings
Join Date: Jul 2011
Location: Northern Ireland
Posts: 903
|
I've been out of the loop for a bit,(crazy work patterns due to Covid19) but I've been trying to keep up as best I can.
That said, do I recall something about only the last FX Slot in the chain showing on C4 (or as I'm currently messing on) C4emu.osc?
It only seems to be displaying the last FX slots in the chain for me, swap them around and everything changes but still only the slat in the chain.
Any advice?
|
|
|
06-30-2020, 01:32 PM
|
#9674
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
hello everyone, I have a couple of questions for the group here. This is using the XTouch Mini. Actually, 2 of them:
1. I have one of the XT mini's rotary sets using sends 1-8. I'd like to use the other for sends 9-16. Just changing the channel | numbers doesn't work. How would I write that code?
2. I would like to (also/maybe) use the rotaries for just one plugin parameter. I would have this plugin on every track, so I would like for it to be available and display feedback all the time and bank with the channels. I just can't wrap my head around how to set that up.
I'm not at my studio computer right now to post any of the code I have, I am just thinking out loud.
cheers!
|
|
|
06-30-2020, 02:00 PM
|
#9675
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by poetnprophet
hello everyone, I have a couple of questions for the group here. This is using the XTouch Mini. Actually, 2 of them:
1. I have one of the XT mini's rotary sets using sends 1-8. I'd like to use the other for sends 9-16. Just changing the channel | numbers doesn't work. How would I write that code?
|
You'd use the same .zon and just add the surface twice in the same Page un CSU. So CSI will see this in your .zon file:
SENDS|1-8
...and assign the first surface to sends 1-8, like you're currently seeing. Add that same surface again, using the same .zon file, to the same Page in CSI, and CSI will automatically use the second instance for sends 9-16.
|
|
|
06-30-2020, 02:12 PM
|
#9676
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Quote:
Originally Posted by Funkybot
You'd use the same .zon and just add the surface twice in the same Page un CSU. So CSI will see this in your .zon file:
SENDS|1-8
...and assign the first surface to sends 1-8, like you're currently seeing. Add that same surface again, using the same .zon file, to the same Page in CSI, and CSI will automatically use the second instance for sends 9-16.
|
Yes I have 2 zon files already. FYI they have to be named separately otherwise one will mirror the other. But I wasn't getting it to work with identical code OR changing 1-8 to 9-16 in another zon file.
|
|
|
06-30-2020, 06:00 PM
|
#9677
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by poetnprophet
Yes I have 2 zon files already. FYI they have to be named separately otherwise one will mirror the other. But I wasn't getting it to work with identical code OR changing 1-8 to 9-16 in another zon file.
|
I wouldn't expect the 9-16 approach to work. But I think duplicating 1-8 thing is supposed to. Unless there's some kind of conflict or logic with SelectedTrackNavigator to specifically prevent that.
|
|
|
07-02-2020, 09:08 AM
|
#9678
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Quote:
Originally Posted by Funkybot
I wouldn't expect the 9-16 approach to work. But I think duplicating 1-8 thing is supposed to. Unless there's some kind of conflict or logic with SelectedTrackNavigator to specifically prevent that.
|
I did the duplicate, it didn't work.
|
|
|
07-02-2020, 11:17 AM
|
#9679
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by poetnprophet
I did the duplicate, it didn't work.
|
Yeah, I saw that you mentioned it didn't work. I was just saying I expected that it would. Out of ideas. I've never had anywhere near 9 sends on a track so just never had to worry about it personally, but was answering based on how I think it should work (**in theory**).
Geoff's been a little low key, hopefully wrapping up some of the work he's been up and will have a new build and more frequent forum presence soon (once everything's all good post-cataract surgery of course - that's most important).
|
|
|
07-02-2020, 12:33 PM
|
#9680
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Understood. I see the idea, based on what happens with channels relative to multiple 8-fader surfaces. But Channels are also defined as "TrackNavigator" and not selected, so who knows what's going on behind all the code. yes 8 sends is a lot, but I have a few more I use for parallel processing.
Ok next question is: how would I setup an FX control/widget that is always active regardless of what track I've selected...AND doesn't need to be focused?
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 03:09 AM.
|