|
|
|
02-15-2020, 04:03 PM
|
#6601
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by MixMonkey
Thanks for the confirmation
Now I think I've got my head around it a bit more, a couple of questions if you've got the time.
Do you intend to use this channel switching ability with CSI? or is there a better way of moving track to track in Reaper with just a single, fixed channel definition on the X-Touch One?
I ask because there are a number of these single fader devices available and it would be good to have a common game plan for them if possible (probably a wild hope )
|
You can also set the Behringer up in MCU Std or MCU User modes and it'll revert to (I believe) just two fader:. Fader5 (no idea why they didn't chose Fader1) and MasterFader. I guess the idea in that mode is that you'd select the channel in the DAW and the X-Touch would follow the active selection (basically: SelectedTrackNavigator in CSI).
I didn't spend a ton of time with that mode, but it's nice having that option. Both methods could work equally well with CSI. The nice thing with the Mackie DAW modes is everything works out of the box with the typical MCU.zon and .mst files. Then you just tweak from there. The downside is you may not want to work in banks of 8 on a one-fader surface, and that's where navigating via a Selected Track Navigator may make more sense.
At this point, I'm still customizing the surface, so I haven't fully explored both options to figure out which I prefer, but the nice thing with CSI is how flexible it is so I'm not sure we need any one standard. I think that one ICON single-fader surface uses the 9-virtual-fader approach, whereas I'm not sure wha the FaderPort does. I tend to think, the best approach may vary from vendor to vendor, unit to unit, user to user, so no need in trying to setup a standard approach. If I setup a 9-fader .zon and others want to use it, they can, and if someone wants to setup a 1-fader .zon for the same surface and users want to use it, they can.
Anyway, just my random, meandering thoughts. Definitely plan on eventually trying both ways.
|
|
|
02-15-2020, 04:03 PM
|
#6602
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
New build is up.
Please check banking thoroughly, it just received a major rewrite.
If everything checks out, the code is ready for beta, now we just have to do the docs and then lean on all you good folks to supply as many .mst/.ost/.zon files as we can to start the beta off right !!
__________________
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
|
|
|
02-15-2020, 04:37 PM
|
#6603
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Funkybot
You can also set the Behringer up in MCU Std or MCU User modes and it'll revert to (I believe) just two fader:. Fader5 (no idea why they didn't chose Fader1) and MasterFader. I guess the idea in that mode is that you'd select the channel in the DAW and the X-Touch would follow the active selection (basically: SelectedTrackNavigator in CSI).
I didn't spend a ton of time with that mode, but it's nice having that option. Both methods could work equally well with CSI. The nice thing with the Mackie DAW modes is everything works out of the box with the typical MCU.zon and .mst files. Then you just tweak from there. The downside is you may not want to work in banks of 8 on a one-fader surface, and that's where navigating via a Selected Track Navigator may make more sense.
At this point, I'm still customizing the surface, so I haven't fully explored both options to figure out which I prefer, but the nice thing with CSI is how flexible it is so I'm not sure we need any one standard. I think that one ICON single-fader surface uses the 9-virtual-fader approach, whereas I'm not sure wha the FaderPort does. I tend to think, the best approach may vary from vendor to vendor, unit to unit, user to user, so no need in trying to setup a standard approach. If I setup a 9-fader .zon and others want to use it, they can, and if someone wants to setup a 1-fader .zon for the same surface and users want to use it, they can.
Anyway, just my random, meandering thoughts. Definitely plan on eventually trying both ways.
|
Thanks for the insight, I can see some experimentation is in order!
|
|
|
02-15-2020, 04:39 PM
|
#6604
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
New build is up.
Please check banking thoroughly, it just received a major rewrite.
If everything checks out, the code is ready for beta, now we just have to do the docs and then lean on all you good folks to supply as many .mst/.ost/.zon files as we can to start the beta off right !!
|
Working fine here Pounded on it with a 157 track session moving in banks of 8 and single channel- all good. Anything I should try?
|
|
|
02-15-2020, 05:10 PM
|
#6605
|
Human being with feelings
Join Date: Jan 2020
Posts: 36
|
X-Touch One - Success
@MixMonkey, @Funkybot, and of course Geoff, Thanks for all the help. I have the XTO doing everything I wanted and have 3 function buttons I can assign to other actions once I have a chance to actually mix something with the surface.
I'm using the Cubase overlay, and only had to reassign 2 widgets in the mst to make sure all MIDI addresses were right for that particular mode. My customizations are pretty basic, for instance I'm using the scrub button for Save just because it's in a handy place.
This is very cool, so thank you again. I could not have done this without the support of the community and especially you guys.
|
|
|
02-15-2020, 05:59 PM
|
#6606
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MixMonkey
Working fine here Pounded on it with a 157 track session moving in banks of 8 and single channel- all good. Anything I should try?
|
Cool, no that's enough, was tested here too, so all looks good.
OK everyone, this will be the beta code base.
Please report any bugs as you find them.
We will also be adding a few things like stepped values and Learn Mode (and others) during the beta phase.
However what exists right now should stay stable -- famous last words
__________________
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
|
|
|
02-15-2020, 06:38 PM
|
#6607
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
Cool, no that's enough, was tested here too, so all looks good.
OK everyone, this will be the beta code base.
Please report any bugs as you find them.
We will also be adding a few things like stepped values and Learn Mode (and others) during the beta phase.
However what exists right now should stay stable -- famous last words
|
Congratulations Geoff!! Beta land here we come
|
|
|
02-15-2020, 06:52 PM
|
#6608
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
This isn't really a bug, but it's had me going round in circles for an hour or so..
This works:
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpperD| FXNameDisplay |
DisplayLowerD| NoAction
RotaryD| NoAction
RotaryPushD| GoFXSlot |
ZoneEnd
This doesn't:
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpperD| FXNameDisplay|
DisplayLowerD| NoAction
RotaryD| NoAction
RotaryPushD| GoFXSlot|
ZoneEnd
|
|
|
02-15-2020, 07:12 PM
|
#6609
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MixMonkey
This isn't really a bug, but it's had me going round in circles for an hour or so..
This works:
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpperD| FXNameDisplay |
DisplayLowerD| NoAction
RotaryD| NoAction
RotaryPushD| GoFXSlot |
ZoneEnd
This doesn't:
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpperD| FXNameDisplay|
DisplayLowerD| NoAction
RotaryD| NoAction
RotaryPushD| GoFXSlot|
ZoneEnd
|
Yeah, it's subtle.
Think of it this way:
Similar Widgets often have tags to differentiate them -- Fader1, Fader2, etc.
Actions are never tagged, but often take parameters, FXNameDisplay 5, FXNameDisplay 6, etc.
__________________
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
|
|
|
02-15-2020, 07:20 PM
|
#6610
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
Yeah, it's subtle.
Think of it this way:
Similar Widgets often have tags to differentiate them -- Fader1, Fader2, etc.
Actions are never tagged, but often take parameters, FXNameDisplay 5, FXNameDisplay 6, etc.
|
Ah, ok, got it
I don't suppose there's a way I can double assign RotaryPushD(1-8) in that example?
|
|
|
02-15-2020, 07:42 PM
|
#6611
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MixMonkey
Ah, ok, got it
I don't suppose there's a way I can double assign RotaryPushD(1-8) in that example?
|
double assign ?
__________________
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
|
|
|
02-15-2020, 08:01 PM
|
#6612
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Geoff, as you move to beta, is "EncoderPlain" sticking around? I'm using that for my MCU Pan Encoder because the standard Encoder resolution is still brutally fine. EncoderPlain has a much better level of responsiveness, but I think encoder acceleration is still on the list for the beta. Just don't know if that widget type is going away...
|
|
|
02-15-2020, 08:36 PM
|
#6613
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Just found what I think is a bug:
1. Using FocusedFXMode, put two instances of the same plugin on the same track
2. Focus instance #1 and move some CSI knobs mapped to the plugin
Result: everything works as expected
3. Focus instance #2 of the plugin and move some CSI knobs
Result: nothing's moving, that's weird...
4. Focus back on instance #1
Result: ah...there we go. When I was moving knobs in Step 3, it was controlling instance #1, not instance #2 (even though #2 was focused).
Expected Result: the focused instance should always be the one controlled even if I have two instances on the same track.
|
|
|
02-15-2020, 10:58 PM
|
#6614
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Funkybot
Just found what I think is a bug:
1. Using FocusedFXMode, put two instances of the same plugin on the same track
2. Focus instance #1 and move some CSI knobs mapped to the plugin
Result: everything works as expected
3. Focus instance #2 of the plugin and move some CSI knobs
Result: nothing's moving, that's weird...
4. Focus back on instance #1
Result: ah...there we go. When I was moving knobs in Step 3, it was controlling instance #1, not instance #2 (even though #2 was focused).
Expected Result: the focused instance should always be the one controlled even if I have two instances on the same track.
|
i am having some issues with plugins .i havnt done anything but update to new build so idk if its a bug.it seems to be with the rotarypushes.some dont work and others dont toggle .all was fine with the plugins before update. all the problems seem to be with rotary pushes with toggle included.anyone else having rotarypush plugin issues ?
|
|
|
02-15-2020, 11:09 PM
|
#6615
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Cragster
i am having some issues with plugins .i havnt done anything but update to new build so idk if its a bug.it seems to be with the rotarypushes.some dont work and others dont toggle .all was fine with the plugins before update. all the problems seem to be with rotary pushes with toggle included.anyone else having rotarypush plugin issues ?
|
Can you post an example fx.zon? So the issue is Toggle+RotaryPush on an FxParameter? I can check it out tomorrow.
|
|
|
02-15-2020, 11:33 PM
|
#6616
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Funkybot
Can you post an example fx.zon? So the issue is Toggle+RotaryPush on an FxParameter? I can check it out tomorrow.
|
Yes it was working yesterday.all faders and rotarys work but the pushes either dont work or dont toggle. I dont remember making any changes or anything. Im all closed up for the night so ill post zone tmr. Thanks for your reply
|
|
|
02-16-2020, 04:03 AM
|
#6617
|
Human being with feelings
Join Date: Jan 2020
Posts: 25
|
Quote:
Originally Posted by Geoff Waddington
Yes, set the Tascam to Mackie Mode and use MCU in CSI.
|
Hi Geoff, I have played around modifying the MCU mst and zon for my FW1884, and most of the controllers ( faders, buttons + jogwheel) control REAPER as expected but the Rotaries (1-8) DON'T seem to adjust the pan of the tracks at all.
When moving Rotary1 I can see REAPER showing the status (near the menu bar) ...
Code:
"[Adjust track pan (via surface)]"
and the Reascript console showing a sequence below
Code:
In -> MCU -> Rotary1 0.498016
In -> MCU -> Rotary1 0.501984
In -> MCU -> Rotary1 0.501984
....
but REAPER pan control does NOT change at all.
I guess I must have done something incorrectly with the.zon file but can't quite to figure out what.
Below are the extract of mst and zon ...
Code:
Widget Rotary1
Encoder b0 10 7f
FB_Encoder b0 10 7f
WidgetEnd
Widget Rotary2
Encoder b0 11 7f
FB_Encoder b0 11 7f
WidgetEnd
Widget Rotary3
Encoder b0 12 7f
FB_Encoder b0 12 7f
WidgetEnd
Widget Rotary4
Encoder b0 13 7f
FB_Encoder b0 13 7f
WidgetEnd
Widget Rotary5
Encoder b0 14 7f
FB_Encoder b0 14 7f
WidgetEnd
Widget Rotary6
Encoder b0 15 7f
FB_Encoder b0 15 7f
WidgetEnd
Widget Rotary7
Encoder b0 16 7f
FB_Encoder b0 16 7f
WidgetEnd
Widget Rotary8
Encoder b0 17 7f
FB_Encoder b0 17 7f
WidgetEnd
Code:
Zone Home
OnTrackSelection MapSelectedTrackSendsToWidgets
IncludedZones
"Buttons|"
"Channel|1-8"
"MasterChannel|"
IncludedZonesEnd
ZoneEnd
Zone "Buttons|"
Send ToggleMapSelectedTrackSends
Track ToggleMapSelectedTrackFXMenu
Pan ToggleMapSelectedTrackFX
ChannelLeft TrackBank "-1"
ChannelRight TrackBank "1"
BankLeft TrackBank "-8"
BankRight TrackBank "8"
Rewind Rewind
FastForward FastForward
Stop Stop
Play Play
Record Record
F1 NextPage
smpteBeats CycleTimeDisplayModes
TimeDisplay TimeDisplay
Read TrackAutoMode "1"
Write TrackAutoMode "3"
Trim TrackAutoMode "0"
Touch TrackAutoMode "2"
Latch TrackAutoMode "4"
Group Reaper "42023"
Shift+Read GlobalAutoMode "1"
Shift+Write GlobalAutoMode "3"
Shift+Trim GlobalAutoMode "0"
Shift+Touch GlobalAutoMode "2"
Shift+Latch GlobalAutoMode "4"
Shift+Group Reaper "42024"
Save Reaper "40026"
Shift+Save Reaper "40022"
Undo Reaper "40029"
Shift+Undo Reaper "40030"
Shift Shift
Option Option
Control Control
Alt Alt
Marker Reaper "40172"
Shift+Marker Reaper "40157"
Option+Marker Reaper "40174"
Nudge Reaper "40173"
Cycle CycleTimeline
Click Reaper "40364"
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
FaderTouch| TrackTouch
ZoneEnd
Zone "MasterChannel|"
MasterTrackNavigator
MasterFader TrackVolume
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
TrackTouch+Fader| TrackSendVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "FXMenu|1-4"
SelectedTrackNavigator
DisplayUpper| FXNameDisplay |
RotaryPush| GoFXSlot |
ZoneEnd
|
|
|
02-16-2020, 06:08 AM
|
#6618
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Funkybot
Geoff, as you move to beta, is "EncoderPlain" sticking around? I'm using that for my MCU Pan Encoder because the standard Encoder resolution is still brutally fine. EncoderPlain has a much better level of responsiveness, but I think encoder acceleration is still on the list for the beta. Just don't know if that widget type is going away...
|
Yeah, acceleration is in the list, that will take care of those issues.
__________________
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
|
|
|
02-16-2020, 06:09 AM
|
#6619
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Funkybot
Just found what I think is a bug:
1. Using FocusedFXMode, put two instances of the same plugin on the same track
2. Focus instance #1 and move some CSI knobs mapped to the plugin
Result: everything works as expected
3. Focus instance #2 of the plugin and move some CSI knobs
Result: nothing's moving, that's weird...
4. Focus back on instance #1
Result: ah...there we go. When I was moving knobs in Step 3, it was controlling instance #1, not instance #2 (even though #2 was focused).
Expected Result: the focused instance should always be the one controlled even if I have two instances on the same track.
|
Thanks, FocusedFX remains a work in progress
__________________
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
|
|
|
02-16-2020, 06:48 AM
|
#6620
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
double assign ?
|
Sorry, that was a bit obscure of me.
What I'd like to do is something like this:
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpperD| FXNameDisplay |
DisplayLowerD| NoAction
RotaryD| NoAction
RotaryPushD| GoFXSlot |
RotaryPushD1 Reaper "_S&M_FLOATFX1"
RotaryPushD2 Reaper "_S&M_FLOATFX2"
RotaryPushD3 Reaper "_S&M_FLOATFX3"
RotaryPushD4 Reaper "_S&M_FLOATFX4"
RotaryPushD5 Reaper "_S&M_FLOATFX5"
RotaryPushD6 Reaper "_S&M_FLOATFX6"
RotaryPushD7 Reaper "_S&M_FLOATFX7"
RotaryPushD8 Reaper "_S&M_FLOATFX8"
ZoneEnd
So that when I pick an FX slot from the menu, the corresponding FX window opens and the controls map to the surface.
|
|
|
02-16-2020, 07:24 AM
|
#6621
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MixMonkey
Sorry, that was a bit obscure of me.
What I'd like to do is something like this:
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpperD| FXNameDisplay |
DisplayLowerD| NoAction
RotaryD| NoAction
RotaryPushD| GoFXSlot |
RotaryPushD1 Reaper "_S&M_FLOATFX1"
RotaryPushD2 Reaper "_S&M_FLOATFX2"
RotaryPushD3 Reaper "_S&M_FLOATFX3"
RotaryPushD4 Reaper "_S&M_FLOATFX4"
RotaryPushD5 Reaper "_S&M_FLOATFX5"
RotaryPushD6 Reaper "_S&M_FLOATFX6"
RotaryPushD7 Reaper "_S&M_FLOATFX7"
RotaryPushD8 Reaper "_S&M_FLOATFX8"
ZoneEnd
So that when I pick an FX slot from the menu, the corresponding FX window opens and the controls map to the surface.
|
This is one of those rare times where you DO want to tag the Action, contrary to my answer to you earlier, not positive this will work, but it should:
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpperD| FXNameDisplay |
DisplayLowerD| NoAction
RotaryD| NoAction
RotaryPushD| GoFXSlot |
RotaryPushD| Reaper "_S&M_FLOATFX|"
ZoneEnd
__________________
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; 02-16-2020 at 07:36 AM.
|
|
|
02-16-2020, 07:28 AM
|
#6622
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
This is one of those rare times where you DO want to tag the Action, contrary to my answer to you earlier, not positive this will work, but it should:
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpperD| FXNameDisplay |
DisplayLowerD| NoAction
RotaryD| NoAction
RotaryPushD| GoFXSlot |
RotaryPushD1 Reaper "_S&M_FLOATFX|"
ZoneEnd
|
Thanks Will try it later, as have to go out now. Would be great if it works, there's a whole bunch of SWS Actions like this
|
|
|
02-16-2020, 09:20 AM
|
#6623
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by concaocao
Hi Geoff, I have played around modifying the MCU mst and zon for my FW1884, and most of the controllers ( faders, buttons + jogwheel) control REAPER as expected but the Rotaries (1-8) DON'T seem to adjust the pan of the tracks at all.
When moving Rotary1 I can see REAPER showing the status (near the menu bar) ...
Code:
"[Adjust track pan (via surface)]"
and the Reascript console showing a sequence below
Code:
In -> MCU -> Rotary1 0.498016
In -> MCU -> Rotary1 0.501984
In -> MCU -> Rotary1 0.501984
....
but REAPER pan control does NOT change at all.
|
concaocao, nothing sticks out as incorrect but pan is working here and the relevant parts of our .zon files look the same. Are you sure it's not the super-fine encoder resolution of the pan knob that you're running into? On my surface, I need to really twist and twist and twist to get pan to move using the standard encoder widgets. I get MUCH better resolution currently when I use the EncoderPlain widget for the pans. I'm not saying this will solve your issue, but it may be worth a shot.
Try replacing the "Encoder" portion of the widgets in the .mst with "EncoderPlain" (keep the FB_Encoder the same). Like this:
Code:
Widget Rotary1
EncoderPlain b0 10 7f
FB_Encoder b0 10 7f
WidgetEnd
Does that fix it?
|
|
|
02-16-2020, 09:37 AM
|
#6624
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Fun fact/warning about the X-Touch One: MCU Std and MCU User modes only use a single fader for tracks...BUT, the MIDI address of that fader stays the same as the last channel you selected in the other MCU Modes. It's not hardwired.
So for example:
Let's say you're were last in MCU Cubase mode, controlling [virtual] Fader5 with a MIDI address beginning e4. Then tomorrow you decide to go into MCU Std mode. MCU Std mode will be stuck on Fader5 because it was the last fader selected in one of the MCU DAW modes. To get MCU Std mode to work on Fader1, you'd have to go into one of the DAW modes, select the first fader, then go back to MCU Std mode.
dberman, I think this is a bit part of why we couldn't get the MCU Std or MCU User mode working in the past. Bizarre that Behringer didn't just hardwire the track fader to Fader1 in MCU Std and MCU User modes.
|
|
|
02-16-2020, 10:06 AM
|
#6625
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Question for the group: If I setup the X-Touch One for "Selected Channel" only, how do I setup RotaryPush1 to alternate between Pan and PanWidth? I can't for the life of me figure this out for the Selected channel only.
Here's what I've got...
Code:
Zone Home
OnTrackSelection MapSelectedTrackSendsToWidgets
IncludedZones
"SelectedChannel|"
IncludedZonesEnd
ZoneEnd
Zone "SelectedChannel|"
SelectedTrackNavigator
Read TrackAutoMode 1
Write TrackAutoMode 3
Trim TrackAutoMode 0
Touch TrackAutoMode 2
Latch TrackAutoMode 4
BankLeft TrackBank "-8" //not sure what action to replace this with
BankRight TrackBank "8" //ditto
ChannelLeft Reaper 40286 //Select previous track
ChannelRight Reaper 40285 //Select next track
DisplayUpper1 TrackNameDisplay
DisplayLower1 TrackPanDisplay
TrackTouch+DisplayLower1 TrackVolumeDisplay
Solo1 TrackSolo
Mute1 TrackMute
RecordArm1 TrackRecordArm
Select1 TrackUniqueSelect
Fader1 TrackVolume
FaderTouch1 TrackTouch
VUMeter1 TrackOutputMeter
Rotary1 TrackPan "0"
RotaryPush1 GoZone PanWidth|
ZoneEnd
Zone "Pan|"
SelectedTrackNavigator
Rotary1 TrackPan "0"
DisplayUpper1 TrackNameDisplay
DisplayLower1 TrackPanDisplay
RotaryPush1 GoZone PanWidth|
ZoneEnd
Zone "PanWidth|"
SelectedTrackNavigator
Rotary1 TrackPanWidth "1"
DisplayUpper1 TrackNameDisplay
DisplayLower1 TrackPanWidthDisplay
RotaryPush1 GoZone Pan|
ZoneEnd
It just gets stuck on pan no matter what I try (tried different navigators, etc.). Hoping someone can help. I'm experimenting with the one-fader approach just to see what I like better.
EDIT
Edited my edit. Spoke to soon.
Last edited by Funkybot; 02-16-2020 at 12:03 PM.
|
|
|
02-16-2020, 10:14 AM
|
#6626
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Funkybot
Can you post an example fx.zon? So the issue is Toggle+RotaryPush on an FxParameter? I can check it out tomorrow.
|
Code:
Zone "VST3: TDR Kotelnikov (Tokyo Dawn Labs)" "TDRComp"
SelectedTrackNavigator
DisplayUpper1 FXParamNameDisplay 0 "Tresh"
DisplayLower1 FXParamValueDisplay 0
Fader1 FXParam 0
DisplayUpper2 FXParamNameDisplay 1 "PeaCre"
DisplayLower2 FXParamValueDisplay 1
Fader2 FXParam 1
DisplayUpper3 FXParamNameDisplay 2 "Knee"
DisplayLower3 FXParamValueDisplay 2
Fader3 FXParam 2
DisplayUpper4 FXParamNameDisplay 3 "Ratio"
DisplayLower4 FXParamValueDisplay 3
Fader4 FXParam 3
DisplayUpper5 FXParamNameDisplay 4 "Attk"
DisplayLower5 FXParamValueDisplay 4
Fader5 FXParam 4
DisplayUpper6 FXParamNameDisplay 5 "RePeak"
DisplayLower6 FXParamValueDisplay 5
Fader6 FXParam 5
DisplayUpper7 FXParamNameDisplay 6 "ReRMS"
DisplayLower7 FXParamValueDisplay 6
Fader7 FXParam 6
DisplayUpper8 FXParamNameDisplay 7 "MakUp"
DisplayLower8 FXParamValueDisplay 7
Fader8 FXParam 7
Rotary1 NoAction
Rotary2 NoAction
Rotary3 NoAction
Rotary4 NoAction
Rotary5 NoAction
Rotary6 NoAction
Rotary7 NoAction
Rotary8 NoAction
RotaryPush1 NoAction
RotaryPush2 NoAction
RotaryPush3 NoAction
RotaryPush4 NoAction
RotaryPush5 NoAction
RotaryPush6 NoAction
RotaryPush7 NoAction
RotaryPush8 NoAction
Shift+DisplayUpper1 FXParamNameDisplay 8 "DryMx"
Shift+DisplayLower1 FXParamValueDisplay 8
Shift+Fader1 FXParam 8
Shift+DisplayUpper2 FXParamNameDisplay 9 "DryWet"
Shift+DisplayLower2 FXParamValueDisplay 9
Shift+Fader2 FXParam 9
Shift+DisplayUpper3 FXParamNameDisplay 10 "MxMode"
Shift+DisplayLower3 FXParamValueDisplay 10
Toggle+Shift+RotaryPush3 FXParam 10
Shift+DisplayUpper4 FXParamNameDisplay 11 "Gain"
Shift+DisplayLower4 FXParamValueDisplay 11
Shift+Fader4 FXParam 11
Shift+DisplayUpper5 FXParamNameDisplay 12 "Freq"
Shift+DisplayLower5 FXParamValueDisplay 12
Toggle+Shift+RotaryPush5 FXParam 12
Shift+DisplayUpper6 FXParamNameDisplay 13 "Slope"
Shift+DisplayLower6 FXParamValueDisplay 13
Toggle+Shift+RotaryPush6 FXParam 13
Shift+DisplayUpper7 FXParamNameDisplay 14 "Diff"
Shift+DisplayLower7 FXParamValueDisplay 14
Toggle+Shift+RotaryPush7 FXParam 14
Shift+DisplayUpper8 FXParamNameDisplay 15 "Delta"
Shift+DisplayLower8 FXParamValueDisplay 15
Toggle+Shift+RotaryPush8 FXParam 15
Shift+Fader3 NoAction
Shift+Fader5 NoAction
Shift+Fader6 NoAction
Shift+Fader7 NoAction
Shift+Fader8 NoAction
Shift+Rotary1 NoAction
Shift+Rotary2 NoAction
Shift+Rotary3 NoAction
Shift+Rotary4 NoAction
Shift+Rotary5 NoAction
Shift+Rotary6 NoAction
Shift+Rotary7 NoAction
Shift+Rotary8 NoAction
Shift+RotaryPush1 NoAction
Shift+RotaryPush2 NoAction
Shift+RotaryPush4 NoAction
Option+DisplayUpper1 FXParamNameDisplay 16 "Bypass"
Option+DisplayLower1 FXParamValueDisplay 16
Toggle+Option+RotaryPush1 FXParam 16
Option+DisplayUpper2 FXParamNameDisplay 17 "Scale"
Option+DisplayLower2 FXParamValueDisplay 17
Toggle+Option+RotaryPush2 FXParam 17
Option+DisplayUpper3 FXParamNameDisplay 18 "Mode"
Option+DisplayLower3 FXParamValueDisplay 18
Option+Rotary3 FXParam 18
Option+DisplayUpper4 NoAction
Option+DisplayLower4 NoAction
Option+DisplayUpper5 NoAction
Option+DisplayLower5 NoAction
Option+DisplayUpper6 NoAction
Option+DisplayLower6 NoAction
Option+DisplayUpper7 NoAction
Option+DisplayLower7 NoAction
Option+DisplayUpper8 NoAction
Option+DisplayLower8 NoAction
Option+Fader1 NoAction
Option+Fader2 NoAction
Option+Fader3 NoAction
Option+Fader4 NoAction
Option+Fader5 NoAction
Option+Fader6 NoAction
Option+Fader7 NoAction
Option+Fader8 NoAction
Option+Rotary1 NoAction
Option+Rotary2 NoAction
Option+Rotary4 NoAction
Option+Rotary5 NoAction
Option+Rotary6 NoAction
Option+Rotary7 NoAction
Option+Rotary8 NoAction
Option+RotaryPush3 NoAction
Option+RotaryPush4 NoAction
Option+RotaryPush5 NoAction
Option+RotaryPush6 NoAction
Option+RotaryPush7 NoAction
Option+RotaryPush8 NoAction
ZoneEnd
i dont know i think it maybe something i did.some parameters work some dont .today nothing is working in the first plugin i posted(TDR Comp)
Code:
Zone "VST: ReaComp (Cockos)" "ReaComp"
SelectedTrackNavigator
DisplayUpper1 FXParamNameDisplay 0 "Tresh"
DisplayLower1 FXParamValueDisplay 0
Rotary1 FXParam 0
DisplayUpper2 FXParamNameDisplay 4 "PreComp"
DisplayLower2 FXParamValueDisplay 4
Rotary2 FXParam 4
DisplayUpper3 FXParamNameDisplay 2 "Attk"
DisplayLower3 FXParamValueDisplay 2
Rotary3 FXParam 2
DisplayUpper4 FXParamNameDisplay 3 "Rel"
DisplayLower4 FXParamValueDisplay 3
Rotary4 FXParam 3
DisplayUpper5 FXParamNameDisplay 1 "Ratio"
DisplayLower5 FXParamValueDisplay 1
Rotary5 FXParam 1
DisplayUpper6 FXParamNameDisplay 14 "Knee"
DisplayLower6 FXParamValueDisplay 14
Rotary6 FXParam 14
DisplayUpper7 FXParamNameDisplay 6 "LoPass"
DisplayLower7 FXParamValueDisplay 6
Rotary7 FXParam 6
DisplayUpper8 FXParamNameDisplay 7 "HiPass"
DisplayLower8 FXParamValueDisplay 7
Rotary8 FXParam 7
Fader1 NoAction
Fader2 NoAction
Fader3 NoAction
Fader4 NoAction
Fader5 NoAction
Fader6 NoAction
Fader7 NoAction
Fader8 NoAction
RotaryPush1 NoAction
RotaryPush2 NoAction
RotaryPush3 NoAction
RotaryPush4 NoAction
RotaryPush5 NoAction
RotaryPush6 NoAction
RotaryPush7 NoAction
RotaryPush8 NoAction
Shift+Fader1 NoAction
Shift+Fader2 NoAction
Shift+Fader3 NoAction
Shift+Fader4 NoAction
Shift+Fader5 NoAction
Shift+Fader6 NoAction
Shift+Fader7 NoAction
Shift+Fader8 NoAction
Shift+DisplayUpper1 FXParamNameDisplay 13 "RMS"
Shift+DisplayLower1 FXParamValueDisplay 13
Shift+Rotary1 FXParam 13
Shift+DisplayUpper2 FXParamNameDisplay 11 "Wet"
Shift+DisplayLower2 FXParamValueDisplay 11
Shift+Rotary2 FXParam 11
Shift+DisplayUpper3 FXParamNameDisplay 10 "Dry"
Shift+DisplayLower3 FXParamValueDisplay 10
Shift+Rotary3 FXParam 10
Shift+Rotary4 NoAction
Shift+Rotary5 NoAction
Shift+Rotary6 NoAction
Shift+Rotary7 NoAction
Shift+Rotary8 NoAction
Shift+RotaryPush1 NoAction
Shift+RotaryPush2 NoAction
Shift+RotaryPush3 NoAction
Shift+DisplayUpper4 FXParamNameDisplay 16 "AutRel"
Shift+DisplayLower4 FXParamValueDisplay 16
Toggle+Shift+RotaryPush4 FXParam 16
Shift+DisplayUpper5 FXParamNameDisplay 17 "ClAtk"
Shift+DisplayLower5 FXParamValueDisplay 17
Toggle+Shift+RotaryPush5 FXParam 17
Shift+DisplayUpper6 FXParamNameDisplay 12 "PreFil"
Shift+DisplayLower6 FXParamValueDisplay 12
Toggle+Shift+RotaryPush6 FXParam 12
Shift+DisplayUpper7 FXParamNameDisplay 15 "AuMkUp"
Shift+DisplayLower7 FXParamValueDisplay 15
Toggle+Shift+RotaryPush7 FXParam 15
Shift+DisplayUpper8 FXParamNameDisplay 18 "LimOut"
Shift+DisplayLower8 FXParamValueDisplay 18
Toggle+Shift+RotaryPush8 FXParam 18
ZoneEnd
in the Reacomp evrything seems to work but the rotary pushes. they will work but will not toggle.so once i rotarypush once it doesnt work again after that.i just recently added all the noactions but im sure i tested evrything after i did that. it all workrd fine at one time thats all i know.maybe you can see something that im not seeing.i switched to anearlier build and it was same so its gotta be me.once i have time i will try some even earlier builds to be sure.since there has been a few updates in this last week. thanks all for your help
|
|
|
02-16-2020, 10:32 AM
|
#6627
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Cragster
i dont know i think it maybe something i did.some parameters work some dont .today nothing is working in the first plugin i posted(TDR Comp)
in the Reacomp evrything seems to work but the rotary pushes. they will work but will not toggle.so once i rotarypush once it doesnt work again after that.i just recently added all the noactions but im sure i tested evrything after i did that. it all workrd fine at one time thats all i know.maybe you can see something that im not seeing.i switched to anearlier build and it was same so its gotta be me.once i have time i will try some even earlier builds to be sure.since there has been a few updates in this last week. thanks all for your help
|
A few questions.
1A. For TDR Comp are you 100% sure you're not loading the VST2 version and that's why things aren't working? I've done that. "Plugin isn't working - whoops, it's the wrong plugin format."
1B. If you are loading the VST3 of the comp and it's still not working, did you happen to rename the plugin in Reaper? I renamed my TDR plugins in Reaper, but this will of course break the fx.zon files, which need a 100% on the plugin name.
Now...Rotary push...no clue.
Now, while I don't know why it's not working, this is the process I'd follow to troubleshoot:
1. backup your fx.zon file (call it reacomp.bak or something)
2. Create a new ReaComp.zon file
3. Assign a single Toggle+RotaryPush1 (no Shift yet) to a single toggle ReaComp parameter only (save this and restart Reaper of course)
4. Test that one paramater. Does it work? If yes, then...
5. Introduce Shift. Does Shift+Toggle+RotaryPush1 work? Nothing else in the zone, yet, still doing 1 parameter at a time. If yes, that means it can work, then it's a question of "why isn't this working in my original .zon."
If it's not working, then the questions become:
1. Is the syntax correct? If yes, then...
2. Is there a conflict with something else in my fx.zon? Maybe one of the NoActions is preventing messages from getting through.
3. Maybe there's a bug that got introduced? Especially if it worked in a prior build.
|
|
|
02-16-2020, 03:40 PM
|
#6628
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Funkybot
A few questions.
1A. For TDR Comp are you 100% sure you're not loading the VST2 version and that's why things aren't working? I've done that. "Plugin isn't working - whoops, it's the wrong plugin format."
1B. If you are loading the VST3 of the comp and it's still not working, did you happen to rename the plugin in Reaper? I renamed my TDR plugins in Reaper, but this will of course break the fx.zon files, which need a 100% on the plugin name.
Now...Rotary push...no clue.
Now, while I don't know why it's not working, this is the process I'd follow to troubleshoot:
1. backup your fx.zon file (call it reacomp.bak or something)
2. Create a new ReaComp.zon file
3. Assign a single Toggle+RotaryPush1 (no Shift yet) to a single toggle ReaComp parameter only (save this and restart Reaper of course)
4. Test that one paramater. Does it work? If yes, then...
5. Introduce Shift. Does Shift+Toggle+RotaryPush1 work? Nothing else in the zone, yet, still doing 1 parameter at a time. If yes, that means it can work, then it's a question of "why isn't this working in my original .zon."
If it's not working, then the questions become:
1. Is the syntax correct? If yes, then...
2. Is there a conflict with something else in my fx.zon? Maybe one of the NoActions is preventing messages from getting through.
3. Maybe there's a bug that got introduced? Especially if it worked in a prior build.
|
hey thanks man.i just sat down to try to find out whats going on .i will go through your checklist.and its definitly the VST3.whats weird is it works wen i use the mouse on reaper screen in TDR.ie...i have threshold mapped to fader1 when i move fader1 nothing happens but when i move the threshold on screen with the mouse it works..the fader on my surface moves and the values change on the display.try to move the fader itself and nothing ???
|
|
|
02-16-2020, 03:40 PM
|
#6629
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Is the "Press" modifier not working?
I was trying to assign the toggling of the mix window to a widget that had press and release defined in the widget. This was causing the mix window to only stay open as long as I held the button down. Expected.
Code:
Widget Option
Press 90 47 7f 90 47 00
FB_TwoState 90 47 7f 90 47 00
WidgetEnd
So to resolve the issue, I attempted to modify the zone to say:
Code:
Press+Option Reaper 40078 //open mixer
This wasn't having the desired effect though. The mixer window only stayed open as long as I held the button down even after adding the press modifier.
What did work was changing the .mst to say:
Code:
Widget Option
Press 90 47 7f
FB_TwoState 90 47 7f 90 47 00
WidgetEnd
...which, at least according to the Wiki, is less than ideal if your surface transmits release.
|
|
|
02-16-2020, 03:58 PM
|
#6630
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
idk this TDR plugin is not working at all .i feel like im missing something very obvious.but the fact that evrything works wen i move parameters with my mouse but not wen i move parameters on the surface has got me baffled
|
|
|
02-16-2020, 04:08 PM
|
#6631
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Funkybot
Is the "Press" modifier not working?
I was trying to assign the toggling of the mix window to a widget that had press and release defined in the widget. This was causing the mix window to only stay open as long as I held the button down. Expected.
Code:
Widget Option
Press 90 47 7f 90 47 00
FB_TwoState 90 47 7f 90 47 00
WidgetEnd
So to resolve the issue, I attempted to modify the zone to say:
Code:
Press+Option Reaper 40078 //open mixer
This wasn't having the desired effect though. The mixer window only stayed open as long as I held the button down even after adding the press modifier.
What did work was changing the .mst to say:
Code:
Widget Option
Press 90 47 7f
FB_TwoState 90 47 7f 90 47 00
WidgetEnd
...which, at least according to the Wiki, is less than ideal if your surface transmits release.
|
Yeah, the Press option has been removed.
It is up to the individual Action to either ignore or process release messages.
There was a bug in Reaper Action, now fixed in latest build.
__________________
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
|
|
|
02-16-2020, 04:09 PM
|
#6632
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
New build is up
Fixed bug in Reaper Action -- it now ignores release messages.
__________________
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
|
|
|
02-16-2020, 04:30 PM
|
#6633
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Cragster
idk this TDR plugin is not working at all .i feel like im missing something very obvious.but the fact that evrything works wen i move parameters with my mouse but not wen i move parameters on the surface has got me baffled
|
That's definitely weird. Do you have the VST2 installed? Did you try mapping that to see if that works? Grasping at straws here...
|
|
|
02-16-2020, 04:37 PM
|
#6634
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Funkybot
That's definitely weird. Do you have the VST2 installed? Did you try mapping that to see if that works? Grasping at straws here...
|
no the TDR gave me the option on install for vst2 or vst3 .i only installed the vst3.i dont get it it was all just working the other day. The TDR worked breifly last night .just the rotary pushes didnt work now it doesnt work at all. i like move the parameters with the mouse and i watch it all move on my surface but wen i move it on the surface nothing . im like going crazy here lol.i had this setup dam near prerfect.and the rotary pushes on the reacomp no longer toggle. and they toggled the other day. sry man im starting to lose my cool so bare with me. i need to rant !!!
|
|
|
02-16-2020, 04:37 PM
|
#6635
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Geoff Waddington
New build is up
Fixed bug in Reaper Action -- it now ignores release messages.
|
Much better, thanks!
|
|
|
02-16-2020, 04:58 PM
|
#6636
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Funkybot
It just gets stuck on pan no matter what I try (tried different navigators, etc.). Hoping someone can help. I'm experimenting with the one-fader approach just to see what I like better.
|
Did you get it to work in the '8 fader' mode?
|
|
|
02-16-2020, 05:03 PM
|
#6637
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
@Funkybot
I can't vouch for the SelectedTrackNavigator, but I got rid of the separate Pan Zone and changed PanWidth to:
Code:
Zone "PanWidth|1-8"
TrackNavigator
Rotary| TrackPanWidth 1
DisplayLower| TrackPanWidthDisplay
TrackTouch+DisplayLower| TrackVolumeDisplay
RotaryPush| GoZone Home
ZoneEnd
|
|
|
02-16-2020, 05:14 PM
|
#6638
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Cragster
no the TDR gave me the option on install for vst2 or vst3 .i only installed the vst3.i dont get it it was all just working the other day. The TDR worked breifly last night .just the rotary pushes didnt work now it doesnt work at all. i like move the parameters with the mouse and i watch it all move on my surface but wen i move it on the surface nothing . im like going crazy here lol.i had this setup dam near prerfect.and the rotary pushes on the reacomp no longer toggle. and they toggled the other day. sry man im starting to lose my cool so bare with me. i need to rant !!!
|
In my experience VST3 is best avoided
I've had several occasions where the mapping from the surface has just stopped working. The return path, however, remains fine.
Try it again with VST2. Check that the parameter numbers have not changed (if you're using the ones I posted, they're from the VST2 plugin)
|
|
|
02-16-2020, 06:05 PM
|
#6639
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by MixMonkey
In my experience VST3 is best avoided
I've had several occasions where the mapping from the surface has just stopped working. The return path, however, remains fine.
Try it again with VST2. Check that the parameter numbers have not changed (if you're using the ones I posted, they're from the VST2 plugin)
|
oh man thank you mixmonkey !! and funkybot too !! i switched to the VST2 and its working now. Man i take this stuff way too hard haha. i was literally bout to throw this surface out the window haha. allthough im still having the toggle problem. nothing is toggling and it was before. did something change in a build the way toggle is supposed to be mapped ? right now i use...ie... Toggle+Shift+RotaryPush1. it toggled before so i know this used to be right. thanks for all the help !!
|
|
|
02-16-2020, 06:33 PM
|
#6640
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Geoff, I'm getting something really weird with SelectedTrackNavigator. The last/highest track in the project doesn't work.
1. Start with an empty project.
2. Create a single track. Move a fader press a button. Nothing.
3. Add a second track. Try to change something on it. Nothing. Now, select track 1. Now everything works. Select track 2 again. Nothing.
4. Add a third track. Select track 1. Works. Select track 2. Now it works. Select track 3. Nothing.
And so on...
5. Load a project...use SelectedTrackNavigator to move around and change some stuff...everything works until...
6. Select the last track in the project...nothing works on that track.
When I say nothing works, I mean the fader goes to minimum, the display blanks out, any selected track buttons stop working.
|
|
|
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 08:21 AM.
|