|
|
|
06-21-2021, 03:36 PM
|
#14001
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by spkr4thdd
Hope it worked for you? The '73' is the value on the X-Touch... I've got the MCU manual somewhere if you haven't got a note of the Solo LED in the time code section for that?
|
Working fine here! Flashing away rudely!
|
|
|
06-21-2021, 03:38 PM
|
#14002
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
OK, I took the plunge tonight and swapped over to the 1.1 Beta. A couple of minor teething issues while I get used to the new navigators, but mostly going really well.
I only seem to have one or two things I can't sort at the moment; not sure if they're bugs, or me not thinking straight...
1. TrackFXMenuSlotNavigator
In navigator zone I can't configure selecting/activating the FX using RotaryPush|, I have to use Select| with both a 'TrackUniqueSelect' and a 'GoCurrentFXSlot' Is that the only way to do it?
2. TrackFXMenuSlotNavigator
Using the graphic shared a day or two ago, I see the mapping action is 'MapTrackFXMenusSlotToWidgets' and that maps the FX in the current slots to the 8 channels and the lower displays.
What's the corresponding unmapping action? I've tried 'UnmapTrackFXMenusSlotFromWidgets' but no joy?
And the only other thing which is a little frustrating is the lights on the buttons, which I think has already been raised?
I can set a NoFeedback property in their default state and that works great, but I like them to light up when I press Shift or another modifier so that I can see what buttons are linked to it. But... once they light up with Shift pressed, they won't sunlight when it's released.
Now the main controller's pretty much done, it's time to revisit the FX zones... do the GoSubZone commands work as per the old included GoZones? And do SubZones need to be in separate files, or can they stay in the parent zone file?
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
06-21-2021, 03:40 PM
|
#14003
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
Quote:
Originally Posted by MixMonkey
Working fine here! Flashing away rudely!
|
Great news! Nice to finally pay back a little for all the help you've given since I started this journey, even if it's only a tiny bit!
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
06-21-2021, 04:44 PM
|
#14004
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by spkr4thdd
Great news! Nice to finally pay back a little for all the help you've given since I started this journey, even if it's only a tiny bit!
|
Thanks and you're welcome!
Quote:
In navigator zone I can't configure selecting/activating the FX using RotaryPush|, I have to use Select| with both a 'TrackUniqueSelect' and a 'GoCurrentFXSlot' Is that the only way to do it?
|
You can use RotaryPush and I can understand why you would want to- it's like the FX Menu, but you will still need TrackUniqueSelect paired up with GoCurrentFXSlot. I don't why it has to be the selected track, but it does. Try just putting in:
Code:
RotaryPush| GoCurrentFXSlot
...the FX it maps is the one on the selected track, regardless of which Rotary you push. It would make more sense if it didn't do this as TrackFXMenuSlotNavigator isn't supposed to be a SelectedTrackNavigator
|
|
|
06-21-2021, 04:58 PM
|
#14005
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by spkr4thdd
Now the main controller's pretty much done, it's time to revisit the FX zones... do the GoSubZone commands work as per the old included GoZones? And do SubZones need to be in separate files, or can they stay in the parent zone file?
|
I've just finished an example FX for the build that has 1 SubZone. You can probably figure it all out from that:
Code:
Zone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)" "VOSEQ"
SelectedTrackNavigator
SubZones
"VST: TDR VOS SlickEQ (Tokyo Dawn Labs)-2"
SubZonesEnd
BankLeft GoSubZone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)-2"
BankRight GoSubZone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)-2"
DisplayUpper1 FXParamNameDisplay 10 "HPF"
DisplayLower1 FXParamValueDisplay 10
Rotary1 FXParam 10 [ (0.0025,0.003,0.004,0.006,0.008,0.01,0.015,0.02,0.025,0.03,0.06,0.08,0.1,0.2,0.4,0.6) ]
RotaryPush1 NoAction
DisplayUpper2 FXParamNameDisplay 1 "LF"
DisplayLower2 FXParamValueDisplay 1
Rotary2 FXParam 1 [ (0.0025,0.003,0.004,0.006,0.008,0.01,0.015,0.02,0.025,0.03,0.06,0.08,0.1,0.2,0.4,0.6) ]
RotaryPush2 FXParam 2 [ 0.0 1.0 ]
DisplayUpper3 FXParamNameDisplay 0 "Gain"
DisplayLower3 FXParamValueDisplay 0
Rotary3 FXParam 0 [ (0.0025,0.003,0.004,0.006,0.008,0.01,0.015,0.02,0.025,0.03,0.06,0.08,0.1,0.2,0.4,0.6) ]
RotaryPush3 FXParam 16 [ 0.0 1.0 ]
DisplayUpper4 FXParamNameDisplay 4 "MF"
DisplayLower4 FXParamValueDisplay 4
Rotary4 FXParam 4 [ (0.0025,0.003,0.004,0.006,0.008,0.01,0.015,0.02,0.025,0.03,0.06,0.08,0.1,0.2,0.4,0.6) ]
RotaryPush4 NoAction
DisplayUpper5 FXParamNameDisplay 3 "Gain"
DisplayLower5 FXParamValueDisplay 3
Rotary5 FXParam 3 [ (0.0025,0.003,0.004,0.006,0.008,0.01,0.015,0.02,0.025,0.03,0.06,0.08,0.1,0.2,0.4,0.6) ]
RotaryPush5 FXParam 17 [ 0.0 1.0 ]
DisplayUpper6 FXParamNameDisplay 6 "HF"
DisplayLower6 FXParamValueDisplay 6
Rotary6 FXParam 6 [ (0.0025,0.003,0.004,0.006,0.008,0.01,0.015,0.02,0.025,0.03,0.06,0.08,0.1,0.2,0.4,0.6) ]
RotaryPush6 FXParam 7 [ 0.0 1.0 ]
DisplayUpper7 FXParamNameDisplay 5 "Gain"
DisplayLower7 FXParamValueDisplay 5
Rotary7 FXParam 5 [ (0.0025,0.003,0.004,0.006,0.008,0.01,0.015,0.02,0.025,0.03,0.06,0.08,0.1,0.2,0.4,0.6) ]
RotaryPush7 FXParam 18 [ 0.0 1.0 ]
DisplayUpper8 FXParamNameDisplay 13 "Output"
DisplayLower8 FXParamValueDisplay 13
Rotary8 FXParam 13 [ (0.0025,0.003,0.004,0.006,0.008,0.01,0.015,0.02,0.025,0.03,0.06,0.08,0.1,0.2,0.4,0.6) ]
RotaryPush8 FXParam 19 [ 0.0 1.0 ]
ZoneEnd
Code:
Zone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)-2"
BankLeft GoSubZone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)"
BankRight GoSubZone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)"
DisplayUpper1 FXParamNameDisplay 8 "Model"
DisplayLower1 FXParamValueDisplay 8
Rotary1 FXParam 8 [ (4,4,3,2,1) 0.0 0.33 0.67 1.0 ]
RotaryPush1 FXParam 8 [ 0.0 0.33 0.67 1.0 ]
DisplayUpper2 FXParamNameDisplay 9 "Sat"
DisplayLower2 FXParamValueDisplay 9
Rotary2 FXParam 9 [ (4,4,3,2,1) 0.0 1.0 ]
RotaryPush2 FXParam 9 [ 0.0 1.0 ]
DisplayUpper3 FXParamNameDisplay 12 "Drive"
DisplayLower3 FXParamValueDisplay 12
Rotary3 FXParam 12 [ (0.0025,0.003,0.004,0.006,0.008,0.01,0.015,0.02,0.025,0.03,0.06,0.08,0.1,0.2,0.4,0.6) ]
RotaryPush3 NoAction
DisplayUpper4 FXParamNameDisplay 11 "Stage"
DisplayLower4 FXParamValueDisplay 11
Rotary4 FXParam 11 [ (4,4,3,2,1) 0.0 0.25 0.50 0.75 1.0 ]
RotaryPush4 FXParam 11 [ 0.0 0.25 0.50 0.75 1.0 ]
DisplayUpper5 FXParamNameDisplay 15 "Mode"
DisplayLower5 FXParamValueDisplay 15
Rotary5 FXParam 15 [ (4,4,3,2,1) 0.0 0.20 0.40 0.60 0.80 1.0 ]
RotaryPush5 FXParam 15 [ 0.0 0.20 0.40 0.60 0.80 1.0 ]
DisplayUpper6 FXParamNameDisplay 20 "Latncy"
DisplayLower6 FXParamValueDisplay 20
Rotary6 FXParam 20 [ (4,4,3,2,1) 0.0 0.50 1.0 ]
RotaryPush6 FXParam 20 [ 0.0 0.50 1.0 ]
DisplayUpper7 NoAction
DisplayLower7 NoAction
Rotary7 NoAction
RotaryPush7 NoAction
DisplayUpper8 NoAction
DisplayLower8 NoAction
Rotary8 NoAction
RotaryPush8 NoAction
ZoneEnd
EDIT: These are separate files, in case that wasn't obvious
Last edited by MixMonkey; 06-22-2021 at 05:56 PM.
Reason: Removed Navigator from SubZone, corrected FX parameter.
|
|
|
06-21-2021, 05:27 PM
|
#14006
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by MixMonkey
You can use RotaryPush and I can understand why you would want to- it's like the FX Menu, but you will still need TrackUniqueSelect paired up with GoCurrentFXSlot. I don't why it has to be the selected track, but it does. Try just putting in:
Code:
RotaryPush| GoCurrentFXSlot
...the FX it maps is the one on the selected track, regardless of which Rotary you push. It would make more sense if it didn't do this as TrackFXMenuSlotNavigator isn't supposed to be a SelectedTrackNavigator
|
I haven't followed the TrackFXMenusSlotNavigator closely as I haven't had a need for that one yet, but has this been raised to Geoff? I too wouldn't expect that a "TrackUniqueSelect" is required to make GoCurrentFXSlot. As you point out, it's not a SelectedTrackNaviagator, so I'd think CSI would understand the track # context.
If you've got a second surface on a SelectedTrackNavigator, you may not want to have to change the selection. Example: I've got my drum bus selected to control the level on my X-Touch One, but I want to edit the drum reverb on a different track on another surface.
Probably not a huge deal, but I totally get how that would trip someone up while crafting a zone file.
|
|
|
06-21-2021, 05:34 PM
|
#14007
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Funkybot
I haven't followed the TrackFXMenusSlotNavigator closely as I haven't had a need for that one yet, but has this been raised to Geoff?
|
Haven't mentioned it to Geoff, but there's been so much new stuff recently, I'm still catching up trying out possible workflows
|
|
|
06-21-2021, 05:35 PM
|
#14008
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by MixMonkey
I've just finished an example FX for the build that has 1 SubZone. You can probably figure it all out from that:
...
EDIT: These are separate files, in case that wasn't obvious
|
That second zone works? Not doubting you but, reason I ask: the navigator in the second file. I had to remove that for my .zon files to work with TDR's Limiter 6.
Here's what those files look like. First zone (includes navigator and subzones)
Code:
Zone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)" "Limiter6 GE"
SelectedTrackNavigator
SubZones
"VST: TDR Limiter 6 GE (Tokyo Dawn Labs)-1"
"VST: TDR Limiter 6 GE (Tokyo Dawn Labs)-2"
SubZonesEnd
/
MainDisplay1 FXNameDisplay
MainDisplay2 TrackNameDisplay
/
BankB GoZone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)"
BankBDisplay FixedTextDisplay "Compressor"
BankC GoZone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)-1"
BankCDisplay FixedTextDisplay "Peak Limiter"
BankD GoZone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)-2"
BankDDisplay FixedTextDisplay "HF Lim+Clip"
/
...
File 2 (no navigator, no sub zones necessary)
Code:
Zone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)-1" "Peak Lim"
/
MainDisplay1 FXNameDisplay
MainDisplay2 TrackNameDisplay
/
BankB GoZone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)"
BankBDisplay FixedTextDisplay "Compressor"
BankC GoZone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)-1"
BankCDisplay FixedTextDisplay "Peak Limiter"
BankD GoZone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)-2"
BankDDisplay FixedTextDisplay "HF Lim+Clip"
/
...
File 3 (no navigator, no sub zones necessary)
Code:
Zone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)-2" "HF Lim+Clip"
/
MainDisplay1 FXNameDisplay
MainDisplay2 TrackNameDisplay
/
BankB GoZone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)"
BankBDisplay FixedTextDisplay "Compressor"
BankC GoZone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)-1"
BankCDisplay FixedTextDisplay "Peak Limiter"
BankD GoZone "VST: TDR Limiter 6 GE (Tokyo Dawn Labs)-2"
BankDDisplay FixedTextDisplay "HF Lim+Clip"
/
...
|
|
|
06-21-2021, 05:37 PM
|
#14009
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Funkybot
That second zone works? Not doubting you but, reason I ask: the navigator in the second file.
|
Yeah, works fine but if that Navigator isn't needed I'll get rid.
EDIT: Works with, works without. Less is always better, so it's out
|
|
|
06-21-2021, 05:40 PM
|
#14010
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by MixMonkey
Yeah, works fine but if that Navigator isn't needed I'll get rid.
|
I only brought it up because I couldn't get the sub-zones working here until I removed it, so I was surprised it worked for you. Unless I was doing something wrong and now I'm just spreading fake news.
|
|
|
06-21-2021, 05:41 PM
|
#14011
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by MixMonkey
Haven't mentioned it to Geoff, but there's been so much new stuff recently, I'm still catching up trying out possible workflows
|
Yeah, currently both GoFXSlot and GoCurrentFXSlot use MapSelectedTrackFXMenuSlotToWidgets.
Call it a bug or simply unfinished
We should really check Navigators here and use whatever strategy makes sense
__________________
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-21-2021, 05:42 PM
|
#14012
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by MixMonkey
Yeah, works fine but if that Navigator isn't needed I'll get rid.
EDIT: Works with, works without. Less is always better, so it's out
|
Yeah, by definition SubZones don't have Navigators -- they get their context from the parent Zone.
__________________
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-21-2021, 05:49 PM
|
#14013
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
Yeah, currently both GoFXSlot and GoCurrentFXSlot use MapSelectedTrackFXMenuSlotToWidgets.
Call it a bug or simply unfinished
We should really check Navigators here and use whatever strategy makes sense
|
Regarding @spkr4thdd's point about using GoCurrentFXSlot, if you don't pair it with a TrackUniqueSelect when using the TrackFXMenuSlotNavigator and you then select a different track, you run into the cross mapping/display problems again.
The expectation is that the FX that will map will be the one from the channel that you pressed the Rotary on, regardless whether that track is selected or not.
|
|
|
06-21-2021, 05:59 PM
|
#14014
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by MixMonkey
The expectation is that the FX that will map will be the one from the channel that you pressed the Rotary on, regardless whether that track is selected or not.
|
Yup, that's what I meant by checking Navigators.
If CSI finds a SelectedTrack Navigator, it should use that, but if it finds another Navigator -- e.g. Track, it should base it's navigation on that, providing the outcome you are expecting
__________________
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-21-2021, 06:07 PM
|
#14015
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
Yup, that's what I meant by checking Navigators.
If CSI finds a SelectedTrack Navigator, it should use that, but if it finds another Navigator -- e.g. Track, it should base it's navigation on that, providing the outcome you are expecting
|
Well, that would be ideal if it isn't too much hassle to code
|
|
|
06-21-2021, 06:36 PM
|
#14016
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Thing is, I think you'll need another FXSlotBank, one that doesn't map the FX as it's used.
I didn't realise this until I started making the MCU Zones for the build. I figured it would be a good idea to assume that someone only had an MCU, no extra surfaces.
In that scenario, you can't actually bank through the FX Slots because as soon as you press FXMenuSlotBank, it maps the next slot's FX the MCU. When I have the C4 active, I can see the FXMenu slots on the MCU, because there are no MCU compatible fx.zon files in the MCU FXZones folder but there are in the C4 FXZones folder and they don't map until I GoCurrentFXSlot.
With the MCU on it's own, all the fx.zon files are available, so they map with the banking.
Hope that made sense
You know, it might be better just to ditch the TrackFXMenuSlotNavigator
|
|
|
06-21-2021, 06:57 PM
|
#14017
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
I'm not getting it. What's being mapped automatically?
In my head, it should work like this. You've got an 8-channel surface, you want to use TrackFXMenuSlot...
1. You engage the FXMenuSlot - MapTrackFXMenusSlotToWidgets
2. That action loads the TrackFXMenuSlot zone, FX Slot 1 spills across the displays, etc.
3. You'd likely use the TrackFXSlotBank 1 or -1 actions in tandem with your bank buttons in this zone to move through the slots
4. You activate the plugin map by assigning GoCurrentFXSlot [EDIT: see my thoughts on that below] to a rotary push widget (would use the same .zon files and mapping as the SelectedTrackFXMenu)
5. You de-activate the mapped fx by GoZone Home, if you're in FXSlot zone and just want to get out you can GoZone home or just use the UnMap action
So something like this...
Code:
Zone "Button"
Global GoZone "Home"
Plugin MapTrackFXMenusSlotToWidgets
Cancel UnmapTrackFXMenusSlotFromWidgets
BankLeft TrackBank -1
BankRight TrackBank 1
ZoneEnd
Zone "TrackFXMenuSlot"
TrackFXMenuSlotNavigator
DisplayUpper TrackNameDisplay
DisplayLower FXNameDisplay
RotaryPush| GoCurrentFXSlot
BankLeft FXMenuSlotBank -1
BankRight FXMenuSlotBank 1
ZoneEnd
...in fact, maybe it just needs a GoFXSlot like SelectedTrackFXMenu. I'm honestly not clear on the difference between GoFXSlot and GoCurrentFXSlot. But basically, for that workflow to work, it should function like GoFXSlot. You see the slot, you select it with RotaryPush, it activates the plugin.zon.
Last edited by Funkybot; 06-21-2021 at 07:03 PM.
|
|
|
06-22-2021, 03:02 AM
|
#14018
|
Human being with feelings
Join Date: May 2021
Posts: 102
|
Geoff, would it be too much of a hassle to create a Solo (ignore routing) option? I would like to have that for Alt+Solo (the one on the channels). I could make a custom action I guess (or maybe not because it doesn't seem to be in the actions menu), but then it would depend on having that channel selected.
I like to use that from time to time when soloing up individual channels if I want to listen to them without ambience effects.
If it's a hassle, just disregard it, but if it's possible, it would be a nice option to have for me.
|
|
|
06-22-2021, 05:33 AM
|
#14019
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Funkybot
I'm not getting it. What's being mapped automatically?
|
The plugin maps to the widgets when you use FXSlotBank. You don't simply navigate up and down the FX chain and then GoCurrentFXSlot when you arrive at the correct plugin.
Quote:
In my head, it should work like this.
|
Yes, I agree, it should
|
|
|
06-22-2021, 06:14 AM
|
#14020
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by ivanmihaljevic
Geoff, would it be too much of a hassle to create a Solo (ignore routing) option? I would like to have that for Alt+Solo (the one on the channels). I could make a custom action I guess (or maybe not because it doesn't seem to be in the actions menu), but then it would depend on having that channel selected.
I like to use that from time to time when soloing up individual channels if I want to listen to them without ambience effects.
If it's a hassle, just disregard it, but if it's possible, it would be a nice option to have for me.
|
Just build a custom solo action incorporating:
Code:
SWS: Mute all sends from selected track(s) _SWS_MUTESENDS
SWS: Unmute all sends from selected track(s) _SWS_UNMUTESENDS
|
|
|
06-22-2021, 06:41 AM
|
#14021
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by MixMonkey
The plugin maps to the widgets when you use FXSlotBank. You don't simply navigate up and down the FX chain and then GoCurrentFXSlot when you arrive at the correct plugin.
Yes, I agree, it should
|
Maybe just part of it being incomplete as Geoff said. Hopefully not a crazy big change to get it over the line.
|
|
|
06-22-2021, 08:56 AM
|
#14022
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by MixMonkey
Thing is, I think you'll need another FXSlotBank, one that doesn't map the FX as it's used.
I didn't realise this until I started making the MCU Zones for the build. I figured it would be a good idea to assume that someone only had an MCU, no extra surfaces.
In that scenario, you can't actually bank through the FX Slots because as soon as you press FXMenuSlotBank, it maps the next slot's FX the MCU. When I have the C4 active, I can see the FXMenu slots on the MCU, because there are no MCU compatible fx.zon files in the MCU FXZones folder but there are in the C4 FXZones folder and they don't map until I GoCurrentFXSlot.
With the MCU on it's own, all the fx.zon files are available, so they map with the banking.
Hope that made sense
You know, it might be better just to ditch the TrackFXMenuSlotNavigator
|
This is exactly the problem I was having. I couldnt figure it out I thought I had it set up wrong.
Thanks for clarifying this
|
|
|
06-22-2021, 09:23 AM
|
#14023
|
Human being with feelings
Join Date: May 2021
Posts: 102
|
Quote:
Originally Posted by MixMonkey
Just build a custom solo action incorporating:
Code:
SWS: Mute all sends from selected track(s) _SWS_MUTESENDS
SWS: Unmute all sends from selected track(s) _SWS_UNMUTESENDS
|
I know I can do that, but then I need to select the track too. It's obviously not a huge deal, but having control of the actual Solo (ignoring routing) per channel would be a far more elegant solution than any custom actions I could cook up.
|
|
|
06-22-2021, 09:27 AM
|
#14024
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by ivanmihaljevic
I know I can do that, but then I need to select the track too.
|
So add TrackUniqueSelect into your Alt+Solo| Actions.
|
|
|
06-22-2021, 09:46 AM
|
#14025
|
Human being with feelings
Join Date: May 2021
Posts: 102
|
Quote:
Originally Posted by MixMonkey
So add TrackUniqueSelect into your Alt+Solo| Actions.
|
Hehe, I knew you'd say that
As I said - it's not a huge deal and I can live without it. There are several disadvantages to a custom action, even if I do the TrackUniqueSelect.
For example, if I have a couple tracks soloed up with this custom action and then hit the ClearAllSolo action, the sends will stay disabled on those tracks.
Again, not a huge deal, but if it wouldn't be too much of a hassle, it would be a lot more elegant to have a dedicated action for Solo (ignore routing).
|
|
|
06-22-2021, 11:06 AM
|
#14026
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
OK, not really much further with my issues on 1.1 from last night...
I have the encoder assignments in my Buttons.zon configured like this:
Code:
Zone "Buttons"
/ ENCODER ASSIGN
Track GoZone "SelectedChannel"
Pan GoZone "PanWidth"
EQ NoAction
Send MapTrackSendsSlotToWidgets
Shift+Send MapTrackReceivesSlotToWidgets
Plugin MapTrackFXMenusSlotToWidgets
Inst NoAction
...
The corresponding TrackSendSlot and TrackFXMenuSlot are:
Code:
Zone "TrackSendSlot"
TrackSendSlotNavigator
Send UnmapTrackSendsSlotFromWidgets
DisplayUpper| TrackNameDisplay
DisplayLower| TrackSendNameDisplay
FaderTouch+DisplayLower| TrackSendVolumeDisplay
Mute| TrackSendMute
Rotary| TrackSendPan
Fader| TrackSendVolume
ChannelLeft SendSlotBank -1
ChannelRight SendSlotBank 1
ZoneEnd
This works as expected; click 'Send' and it maps send slot 1 across the tracks, scrolls through them with the ChannelLeft/Right button, banks through the channels with BankLeft/Right, and returns to my Home.zon by pressing 'Send' again.
Code:
Zone "TrackFXMenuSlot"
TrackFXMenuSlotNavigator
Plugin UnmapTrackFXMenusSlotFromWidgets
DisplayUpper| TrackNameDisplay
DisplayLower| FXMenuNameDisplay
RotaryPush| TrackUniqueSelect
RotaryPush| GoFXSlot
RotaryPush| Reaper "_S&M_FLOATFXEL"
Shift+RotaryPush| Reaper "_S&M_FXBYP|" //Bypass FX Slot
Option+RotaryPush| Reaper "_S&M_FXOFF|" //Offline FX slot
ChannelLeft FXMenuSlotBank -1
ChannelRight FXMenuSlotBank 1
ZoneEnd
This seems to work... Click 'Plugin' from the Home.zon and it maps the 1st FX Slot across the channels, ChannelLeft/Right scroll through the slots, BankLeft/Right bank through the channels and RotaryPush| now opens the FX.zon if it exists. But...
- Pressing Plugin again does not close this view or unmap the FX.
- If I click on an FX slot (and that FX is then mapped to the widgets) and subsequently return to the FXMenuSlot view, when I scroll through the slots, it shows the mapped FX rather than the slot view any time I return to whatever number of slot it opened from?
The more I think about it, the more difference there is behind the concept of mapping the send slots and controlling them, and mapping the FX slots then activating/controlling/closing FX and resetting the map.
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
06-22-2021, 12:03 PM
|
#14027
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by spkr4thdd
The more I think about it, the more difference there is behind the concept of mapping the send slots and controlling them, and mapping the FX slots then activating/controlling/closing FX and resetting the map.
|
Quite so TrackFXMenuSlot needs further development. It only kind of half works at the moment.
What do you think?, is it a concept worth pursuing or one that is redundant because we have the SelectedTrackFXMenu?
What it really offers is the ability to see and select the FX across many tracks, whereas the SelectedTrackFXMenu shows you many FX from one track.
|
|
|
06-22-2021, 12:17 PM
|
#14028
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by MixMonkey
Quite so TrackFXMenuSlot needs further development. It only kind of half works at the moment.
What do you think?, is it a concept worth pursuing or one that is redundant because we have the SelectedTrackFXMenu?
What it really offers is the ability to see and select the FX across many tracks, whereas the SelectedTrackFXMenu shows you many FX from one track.
|
While I'm not using it my current setup, I like the idea of having the option for both. I'm not sure what the effort would be to improve current-state but if not huge, I'd say it's worth pursuing. Currently it sounds like it was based on Send/Receive Slot and just needs a little more of that traditional FX Menu approach to mapping.
|
|
|
06-22-2021, 12:22 PM
|
#14029
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
Quote:
Originally Posted by MixMonkey
Quite so TrackFXMenuSlot needs further development. It only kind of half works at the moment.
What do you think?, is it a concept worth pursuing or one that is redundant because we have the SelectedTrackFXMenu?
What it really offers is the ability to see and select the FX across many tracks, whereas the SelectedTrackFXMenu shows you many FX from one track.
|
It's certainly worth pursuing, but not at the expense of anything else Geoff might be working on.
It's more of a nice to have I think as the SelectedTrackFXMenu works really well and, whereas the Sends slots makes sense as it stands, I'm less likely to want to affect change across a range of tracks on FX at the same time, if that makes sense?
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
06-22-2021, 12:31 PM
|
#14030
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by spkr4thdd
I'm less likely to want to affect change across a range of tracks on FX at the same time, if that makes sense?
|
I agree it's use case argument isn't as strong as sends (and maybe receives), but I could see myself using it in certain scenarios.
If all your EQs, say, are in the same slot, they're only one push away. You don't have to enter/exit a menu every time.
The fact we're having this discussion tells me we're getting rather feature rich now
|
|
|
06-22-2021, 12:46 PM
|
#14031
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
Quote:
Originally Posted by MixMonkey
I've just finished an example FX for the build that has 1 SubZone. You can probably figure it all out from that:
Code:
Zone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)" "VOSEQ"
SelectedTrackNavigator
SubZones
"VST: TDR VOS SlickEQ (Tokyo Dawn Labs)-2"
SubZonesEnd
BankLeft GoSubZone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)-2"
BankRight GoSubZone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)-2"
DisplayUpper1 FXParamNameDisplay 10 "HPF"
DisplayLower1 FXParamValueDisplay 10
Rotary1 FXParam 10 [ (0.0025,0.003,0.004,0.006,0.008,0.01,0.015,0.02,0.025,0.03,0.06,0.08,0.1,0.2,0.4,0.6) ]
RotaryPush1 NoAction
...ZoneEnd
Code:
Zone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)-2"
BankLeft GoSubZone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)"
BankRight GoSubZone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)"
DisplayUpper1 FXParamNameDisplay 8 "Model"
DisplayLower1 FXParamValueDisplay 8
Rotary1 FXParam 8 [ (4,4,3,2,1) 0.0 0.33 0.67 1.0 ]
RotaryPush1 FXParam 8 [ 0.0 0.33 0.67 1.0 ]
...ZoneEnd
EDIT: These are separate files, in case that wasn't obvious
|
Looks simple enough; apparently not so simple in practice...
I've set up the following 3 zones for the D16 Repeater plugin:
Code:
Zone "VST: Repeater (D16 Group Audio Software)" "RptrV"
SelectedTrackNavigator
SubZones // Use for multipage FX
"VST: Repeater (D16 Group Audio Software)-2"
"VST: Repeater (D16 Group Audio Software)-3"
SubZonesEnd
ChannelLeft GoZone "VST: Repeater (D16 Group Audio Software)-3"
ChannelRight GoZone "VST: Repeater (D16 Group Audio Software)-2"
DisplayUpper1 FixedTextDisplay "D16"
DisplayLower1 FixedTextDisplay "Rptr 1"
Rotary1 NoAction
Toggle+RotaryPush1 FXParam 25 [ 0.0 1.0 ] // Use for Bypass
Code:
Zone "VST: Repeater (D16 Group Audio Software)-2"
ChannelLeft GoZone "VST: Repeater (D16 Group Audio Software)"
ChannelRight GoZone "VST: Repeater (D16 Group Audio Software)-3"
DisplayUpper1 FixedTextDisplay "D16"
DisplayLower1 FixedTextDisplay "Rptr 2"
Rotary1 NoAction
Toggle+RotaryPush1 FXParam 25 [ 0.0 1.0 ] // Use for Bypass
Code:
Zone "VST: Repeater (D16 Group Audio Software)-3"
ChannelLeft GoZone "VST: Repeater (D16 Group Audio Software)-2"
ChannelRight GoZone "VST: Repeater (D16 Group Audio Software)"
DisplayUpper1 FixedTextDisplay "D16"
DisplayLower1 FixedTextDisplay "Rptr 3"
Rotary1 NoAction
Toggle+RotaryPush1 FXParam 25 [ 0.0 1.0 ] // Use for Bypass
I've tried with FunkyBot's version of fixed buttons for SubZones (F1=Zone1 etc) and pared it down to 2 zones to just move back and forth rather than have to cycle through... but every time I get to the 3rd click (either way, or even back and firth) it crashes Reaper.
Code:
Thread 0 Crashed:: reaper Dispatch queue: com.apple.main-thread
0 reaper_csurf_integrator.dylib 0x0000000118bdd656 Zone::RequestUpdate(std::__1::vector<Widget*, std::__1::allocator<Widget*> >&) + 102
1 reaper_csurf_integrator.dylib 0x0000000118b7e019 ControlSurface::RequestUpdate() + 217
2 reaper_csurf_integrator.dylib 0x0000000118b4ae1c Page::Run() + 236
3 reaper_csurf_integrator.dylib 0x0000000118b19f9c Manager::Run() + 92
4 reaper_csurf_integrator.dylib 0x0000000118b19f36 CSurfIntegrator::Run() + 38
5 com.cockos.reaper 0x000000010c722ab3 CSurf_Run() + 755
6 com.cockos.reaper 0x000000010c484576 runMiscTimers() + 5686
7 com.cockos.reaper 0x000000010c4828d1 Main_OnTimer(HWND__*, unsigned long) + 2609
8 com.cockos.reaper 0x000000010cace86d MainProc(HWND__*, unsigned int, unsigned long, long) + 2493
9 com.cockos.reaper 0x000000010c937aa6 SwellDialogDefaultWindowProc(HWND__*, unsigned int, unsigned long, long) + 438
10 com.apple.Foundation 0x00007fff3687ade9 __NSFireTimer + 83
11 com.apple.CoreFoundation 0x00007fff346f1484 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
12 com.apple.CoreFoundation 0x00007fff346f1104 __CFRunLoopDoTimer + 1108
13 com.apple.CoreFoundation 0x00007fff346f0bfa __CFRunLoopDoTimers + 346
14 com.apple.CoreFoundation 0x00007fff346e839b __CFRunLoopRun + 2427
15 com.apple.CoreFoundation 0x00007fff346e7787 CFRunLoopRunSpecific + 487
16 com.apple.HIToolbox 0x00007fff339c7d96 RunCurrentEventLoopInMode + 286
17 com.apple.HIToolbox 0x00007fff339c7b06 ReceiveNextEventCommon + 613
18 com.apple.HIToolbox 0x00007fff339c7884 _BlockUntilNextEventMatchingListInModeWithFilter + 64
19 com.apple.AppKit 0x00007fff31c74a3b _DPSNextEvent + 2085
20 com.apple.AppKit 0x00007fff3240ae34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
21 com.apple.AppKit 0x00007fff31c6984d -[NSApplication run] + 764
22 com.apple.AppKit 0x00007fff31c38a3a NSApplicationMain + 804
23 com.cockos.reaper 0x000000010c3afb74 start + 52
I'm going to try with the SlickEQ, as I know that was one of the agreed example FX, and we'll see what happens.
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
06-22-2021, 12:47 PM
|
#14032
|
Human being with feelings
Join Date: Mar 2019
Posts: 18
|
Hey all - @Funkybot and KDubb were super kind and helpful with me as I try to integrate this X-Touch Universal - but I'm hitting a wall and about to just sell the thing and use the mouse. The below post has my Zone and mst files. I've tried clean CSI installs - - tried a portable install of Reaper on the same machine, updated the firmware on the XTouch Universal to 1.21. This is just a bare clean CSI 1.0 install as linked to in Geoff's sig - not even the beta.
https://forum.cockos.com/showpost.ph...8&postcount=58
And a vid of my symptoms - -
https://youtu.be/gFsFzZBE9eQ
Thank you again in advance if anyone sees anything or has a couple files I can hopefully drop in and get these channels to lock to the reaper position - I don't even need all the FX stuff, yet
|
|
|
06-22-2021, 12:55 PM
|
#14033
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by spkr4thdd
I'm going to try with the SlickEQ, as I know that was one of the agreed example FX, and we'll see what happens.
|
It may very well be that it falls over with more than one SubZone. If my VOS EQ example holds up, contrive a second SubZone for it and see if it crashes.
|
|
|
06-22-2021, 01:12 PM
|
#14034
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by John_M
Thank you again in advance if anyone sees anything or has a couple files I can hopefully drop in and get these channels to lock to the reaper position - I don't even need all the FX stuff, yet
|
See if these work any better.
Last edited by MixMonkey; 08-07-2021 at 10:20 AM.
|
|
|
06-22-2021, 01:29 PM
|
#14035
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by spkr4thdd
I'm going to try with the SlickEQ, as I know that was one of the agreed example FX, and we'll see what happens.
|
Look familiar?:
Code:
Process: REAPER [9911]
Path: /Applications/REAPER.app/Contents/MacOS/REAPER
Identifier: com.cockos.reaper
Version: 6.29.0 12c62f6/x86_64-clang (6.29.0 12c62f6/x86_64-clang)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: REAPER [9911]
User ID: 501
Date/Time: 2021-06-22 21:23:01.645 +0100
OS Version: Mac OS X 10.15.7 (19H1217)
Report Version: 12
Anonymous UUID: 08924FD0-E74F-EE5A-E65A-7D0D9B7097EC
Sleep/Wake UUID: B7B177CB-3DD0-4D5F-AE7E-FA9C3C95E235
Time Awake Since Boot: 12000 seconds
Time Since Wake: 5400 seconds
System Integrity Protection: enabled
Crashed Thread: 0 reaper Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000071f2190000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [9911]
VM Regions Near 0x71f2190000:
__LINKEDIT 0000000119eae000-0000000119f27000 [ 484K] r--/rwx SM=COW /Library/Audio/Plug-Ins/VST/Sonnox/Oxford Dynamics Native.vst/Contents/MacOS/Oxford Dynamics
-->
MALLOC_NANO 0000600000000000-0000600008000000 [128.0M] rw-/rwx SM=PRV
Thread 0 Crashed:: reaper Dispatch queue: com.apple.main-thread
0 reaper_csurf_integrator.dylib 0x0000000112fa9656 Zone::RequestUpdate(std::__1::vector<Widget*, std::__1::allocator<Widget*> >&) + 102
1 reaper_csurf_integrator.dylib 0x0000000112f4a019 ControlSurface::RequestUpdate() + 217
2 reaper_csurf_integrator.dylib 0x0000000112f16e1c Page::Run() + 236
3 reaper_csurf_integrator.dylib 0x0000000112ee5f9c Manager::Run() + 92
4 reaper_csurf_integrator.dylib 0x0000000112ee5f36 CSurfIntegrator::Run() + 38
5 com.cockos.reaper 0x000000010d0c7651 CSurf_Run() + 193
6 com.cockos.reaper 0x000000010ce50f80 runMiscTimers() + 2512
7 com.cockos.reaper 0x000000010ceb8639 Main_OnTimer(HWND__*, unsigned long) + 329
8 com.cockos.reaper 0x000000010d3e8a4a MainProc(HWND__*, unsigned int, unsigned long, long) + 4730
9 com.cockos.reaper 0x000000010d27fb26 SwellDialogDefaultWindowProc(HWND__*, unsigned int, unsigned long, long) + 438
10 com.apple.Foundation 0x00007fff38b37d5a __NSFireTimer + 67
11 com.apple.CoreFoundation 0x00007fff36436e38 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
12 com.apple.CoreFoundation 0x00007fff3643699e __CFRunLoopDoTimer + 872
13 com.apple.CoreFoundation 0x00007fff36436489 __CFRunLoopDoTimers + 322
14 com.apple.CoreFoundation 0x00007fff3641b0ed __CFRunLoopRun + 1885
15 com.apple.CoreFoundation 0x00007fff3641a333 CFRunLoopRunSpecific + 466
16 com.apple.HIToolbox 0x00007fff35035abd RunCurrentEventLoopInMode + 292
17 com.apple.HIToolbox 0x00007fff350357d5 ReceiveNextEventCommon + 584
18 com.apple.HIToolbox 0x00007fff35035579 _BlockUntilNextEventMatchingListInModeWithFilter + 64
19 com.apple.AppKit 0x00007fff3367c039 _DPSNextEvent + 883
20 com.apple.AppKit 0x00007fff3367a880 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
21 com.apple.AppKit 0x00007fff3366c58e -[NSApplication run] + 658
22 com.apple.AppKit 0x00007fff3363e396 NSApplicationMain + 777
23 com.cockos.reaper 0x000000010ce0b134 start + 52
,,,I added one more SubZone to my Oxford Dynamics set and as soon as I hit that third button..crash.
|
|
|
06-22-2021, 01:34 PM
|
#14036
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
Quote:
Originally Posted by MixMonkey
It may very well be that it falls over with more than one SubZone. If my VOS EQ example holds up, contrive a second SubZone for it and see if it crashes.
|
Yeah, that works perfectly fine.
BTW, I think RotaryPush7 should be Param 18, not Param 7
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
06-22-2021, 01:36 PM
|
#14037
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by spkr4thdd
BTW, I think RotaryPush7 should be Param 18, not Param 7
|
Quite right, my bad
|
|
|
06-22-2021, 01:40 PM
|
#14038
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by MixMonkey
,,,I added one more SubZone to my Oxford Dynamics set and as soon as I hit that third button..crash.
|
Maybe try a...
plugin.zon
plugin-1.zon
plugin-2.zon
...naming convention? I've got 3 total zones (main zone +2 sub zones) making up my Limter6 files and can switch between the 3 without crashing. I noticed you guys were starting at -2 where I was using -1.
Geoff's examples all followed that convention so I just copied his approach.
Sample attached.
Last edited by Funkybot; 09-28-2022 at 11:55 AM.
|
|
|
06-22-2021, 02:01 PM
|
#14039
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Funkybot
Maybe try a...
plugin.zon
plugin-1.zon
plugin-2.zon
...naming convention?
|
Same result, alas.
|
|
|
06-22-2021, 02:02 PM
|
#14040
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
Quote:
Originally Posted by Funkybot
Maybe try a...
plugin.zon
plugin-1.zon
plugin-2.zon
...naming convention? I've got 3 total zones (main zone +2 sub zones) making up my Limter6 files and can switch between the 3 without crashing. I noticed you guys were starting at -2 where I was using -1.
Geoff's examples all followed that convention so I just copied his approach.
Sample attached.
|
Yeah, that's what I've got... no dice.
I've also noticed that when activating/focussing on any FX using RotaryPush and then returning to the home view it has carried over the rotary push into the home zone while in the FXMenu zone and changed the MCUTrackPan type to width (which I now remember is why I was trying to use my 'PanWidth' zone in the first place as discussed on the other thread).
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
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 12:28 AM.
|