|
|
|
08-21-2018, 04:19 PM
|
#1841
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Quote:
Originally Posted by MixMonkey
Are they the messages you were expecting? ie do they match the .rst.
Have you tried just simply mapping one of the function buttons on the CMC-QC and seeing if you can use it to control an easy Reaper action like the metronome? (Reaper 40364) If it can do this it rules out a lot of possible issues.
|
Yep, just checked, the buttons work.
@Geoff, here you go:
Concerning the wrong folder name: my bad, corrected it!
CSI.ini
Code:
MidiInMonitor On
MidiOutMonitor On
VSTMonitor Off
Page GreenPage FollowTCP NoSynchPages UseTrackColoring 75 255 166
MidiSurface CMC-CH 1 Bankable 3 4 CMC-CH.rst CMC-CH.axt Console1
MidiSurface CMC-QC 1 NonBankable 30 30 CMC-QC.rst CMC-QC.axt CMC-QC
Page Send FollowTCP SynchPages UseTrackColoring 217 66 90
MidiSurface RedMix1 8 Bankable 0 0 ArtistMCU.rst ArtistMCUSend.axt MCU
MidiSurface RedControl 4 Bankable 2 2 ArtistMCU.rst ArtistMCUSend.axt MCU
MidiSurface RedMix2 8 Bankable 1 1 ArtistMCU.rst ArtistMCUSend.axt MCU
MidiSurface RedConsole1 1 NonBankable 7 6 Console1.rst Console1.axt Console1
Page Track FollowTCP SynchPages UseTrackColoring 89 134 255
MidiSurface BlueMix1 8 Bankable 0 0 ArtistMCU.rst ArtistMCU.axt MCU
MidiSurface BlueControl 4 Bankable 2 2 ArtistMCU.rst ArtistMCU.axt MCU
MidiSurface BlueMix2 8 Bankable 1 1 ArtistMCU.rst ArtistMCU.axt MCU
MidiSurface BlueConsole1 1 NonBankable 7 6 Console1.rst Console1.axt Console1
CMC-QC.rst
Code:
Channel
Rotary EncoderFB b0 10 7f b0 10 00
RotaryFeedback EncoderFB b0 30 7f b0 30 00
ChannelEnd
CMC-QC.axt
Code:
TrackOnSelection MapFXToWidgets
ReaComp.fxt
Code:
VST: ReaComp (Cockos)
Rotary1 Thresh
Rotary2 Gain
Rotary3 Attack
Rotary4 Release
Rotary5 Ratio
Rotary6 Bypass
Rotary7 Wet
Rotary8 GainReductionDB
And that's the MIDI input that I get in the ReaScript console output
(turned every knob once)
Code:
IN -> CMC-QC b0 10 01
IN -> CMC-QC b0 11 01
IN -> CMC-QC b0 12 01
IN -> CMC-QC b0 13 01
IN -> CMC-QC b0 14 01
IN -> CMC-QC b0 15 01
IN -> CMC-QC b0 16 01
IN -> CMC-QC b0 17 01
|
|
|
08-21-2018, 04:31 PM
|
#1842
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by _Stevie_
Yep, just checked, the buttons work.
@Geoff, here you go:
Concerning the wrong folder name: my bad, corrected it!
CSI.ini
Code:
MidiInMonitor On
MidiOutMonitor On
VSTMonitor Off
Page GreenPage FollowTCP NoSynchPages UseTrackColoring 75 255 166
MidiSurface CMC-CH 1 Bankable 3 4 CMC-CH.rst CMC-CH.axt Console1
MidiSurface CMC-QC 1 NonBankable 30 30 CMC-QC.rst CMC-QC.axt CMC-QC
Page Send FollowTCP SynchPages UseTrackColoring 217 66 90
MidiSurface RedMix1 8 Bankable 0 0 ArtistMCU.rst ArtistMCUSend.axt MCU
MidiSurface RedControl 4 Bankable 2 2 ArtistMCU.rst ArtistMCUSend.axt MCU
MidiSurface RedMix2 8 Bankable 1 1 ArtistMCU.rst ArtistMCUSend.axt MCU
MidiSurface RedConsole1 1 NonBankable 7 6 Console1.rst Console1.axt Console1
Page Track FollowTCP SynchPages UseTrackColoring 89 134 255
MidiSurface BlueMix1 8 Bankable 0 0 ArtistMCU.rst ArtistMCU.axt MCU
MidiSurface BlueControl 4 Bankable 2 2 ArtistMCU.rst ArtistMCU.axt MCU
MidiSurface BlueMix2 8 Bankable 1 1 ArtistMCU.rst ArtistMCU.axt MCU
MidiSurface BlueConsole1 1 NonBankable 7 6 Console1.rst Console1.axt Console1
CMC-QC.rst
Code:
Channel
Rotary EncoderFB b0 10 7f b0 10 00
RotaryFeedback EncoderFB b0 30 7f b0 30 00
ChannelEnd
CMC-QC.axt
Code:
TrackOnSelection MapFXToWidgets
ReaComp.fxt
Code:
VST: ReaComp (Cockos)
Rotary1 Thresh
Rotary2 Gain
Rotary3 Attack
Rotary4 Release
Rotary5 Ratio
Rotary6 Bypass
Rotary7 Wet
Rotary8 GainReductionDB
And that's the MIDI input that I get in the ReaScript console output
(turned every knob once)
Code:
IN -> CMC-QC b0 10 01
IN -> CMC-QC b0 11 01
IN -> CMC-QC b0 12 01
IN -> CMC-QC b0 13 01
IN -> CMC-QC b0 14 01
IN -> CMC-QC b0 15 01
IN -> CMC-QC b0 16 01
IN -> CMC-QC b0 17 01
|
You have the num channels set to 1 in the CSI.ini.
In order to auto generate the definitions, change this:
MidiSurface CMC-QC 1 NonBankable 30 30 CMC-QC.rst CMC-QC.axt CMC-QC
to this:
MidiSurface CMC-QC 8 NonBankable 30 30 CMC-QC.rst CMC-QC.axt CMC-QC
Let me know 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
|
|
|
08-21-2018, 04:39 PM
|
#1843
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Changed it (I think I also tried that previously). That's what happens:
|
|
|
08-21-2018, 04:58 PM
|
#1844
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by _Stevie_
Changed it (I think I also tried that previously).
|
Can't tell from the screen, that track is selected, right ?
What happens if you de-select it, then select it ?
__________________
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
|
|
|
08-22-2018, 01:05 AM
|
#1845
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Quote:
Originally Posted by Geoff Waddington
Can't tell from the screen, that track is selected, right ?
What happens if you de-select it, then select it ?
|
The track is selected twice actually. With the mouse and via the channel select buttons of the CMC-CH.
Re-selecting does nothing unfortunately
Last edited by _Stevie_; 08-22-2018 at 01:18 AM.
|
|
|
08-22-2018, 02:00 AM
|
#1846
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by _Stevie_
The track is selected twice actually. With the mouse and via the channel select buttons of the CMC-CH.
Re-selecting does nothing unfortunately
|
What happens if you remove the CMC-CH ?
__________________
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
|
|
|
08-22-2018, 02:31 AM
|
#1847
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Quote:
Originally Posted by Geoff Waddington
What happens if you remove the CMC-CH ?
|
Have to test, when I get back home on Sunday! But will do this ASAP!
|
|
|
08-24-2018, 01:26 AM
|
#1848
|
Human being with feelings
Join Date: Mar 2017
Location: France
Posts: 627
|
XTouchMini ?
Hi there!
Anyone done testing with Xtouch-mini form berhinger ? As I saw XTouch-one was on, maybe it woold be great to work on that one now. I'm kind of a noob but i'm willing to help
I did all the installations things mentioned here https://forum.cockos.com/showpost.ph...postcount=1724
With CSI, Imanaged to turn pans et widths and do transports in reaper with my XtouchMini and the feedback showed up too!
Installation was not that easy thow, I had to supress the control instance shutdown in reaper prefs shutdown reaper and disconnect the xtouchmini each time I tweaked something or it would stay sudenly dead.
Tried both normal midi mode and mcu, here is what midi in monitor showed
XTouchMini in MCU mode
- Fader
b0 00
- push rotaries when turned
b0 10
b0 11
b0 12
b0 13
b0 14
b0 15
b0 16
b0 17
- push rotaries when pushed
90 20
90 21
90 22
90 23
90 24
90 25
90 26
90 27
- push Buttons
first row
90 59
90 5a
90 28
90 29
90 2a
90 2b
90 2c
90 2d
Second row
90 57
90 58
90 5b
90 5c
90 56
90 5d
90 5e
90 5f
- Layers Buttons
Layer A 90 54
Layer B 90 55
XTouchMini in normal midi mode
Layer A
- Fader
ba 09
- push rotaries when turned
ba 01
ba 02
ba 03
ba 04
ba 05
ba 06
ba 07
ba 08
- push rotaries when pushed
9a 01
9a 02
9a 03
9a 04
9a 05
9a 06
9a 07
9a 08
When the buttons are realeased, it displays the same but with 8a instead of 9a
- push Buttons
first row
9a 08
9a 09
9a 0A
9a 0B
9a 0C
9a 0D
9a 0E
9a 0F
second row
9a 10
9a 11
9a 12
9a 13
9a 14
9a 15
9a 16
9a 17
Layer B
- Fader
BA 0A
- push rotaries when turned
BA 0B
BA 0C
BA 0D
BA 0E
BA 0F
BA 10
BA 11
BA 12
- push rotaries when pushed
9A 18
9A 19
9A 1A
9A 1B
9A 1C
9A 1D
9A 1E
9A 1F
Same as above, when the buttons are realeased, it displays the same but with 8a instead of 9a
- push Buttons
first row
9A 20
9A 21
9A 22
9A 23
9A 24
9A 25
9A 26
9A 27
second row
9A 28
9A 29
9A 2A
9A 2B
9A 2C
9A 2D
9A 2E
9A 2F
Not sure how to continue now... Hope it helps !
|
|
|
08-25-2018, 08:40 AM
|
#1849
|
Human being with feelings
Join Date: Jul 2011
Location: Northern Ireland
Posts: 903
|
Quote:
Originally Posted by Regisfofo
Hi there!
Anyone done testing with Xtouch-mini form berhinger ? As I saw XTouch-one was on, maybe it woold be great to work on that one now. I'm kind of a noob but i'm willing to help
I did all the installations things mentioned here https://forum.cockos.com/showpost.ph...postcount=1724
With CSI, Imanaged to turn pans et widths and do transports in reaper with my XtouchMini and the feedback showed up too!
Installation was not that easy thow, I had to supress the control instance shutdown in reaper prefs shutdown reaper and disconnect the xtouchmini each time I tweaked something or it would stay sudenly dead.
Tried both normal midi mode and mcu, here is what midi in monitor showed
XTouchMini in MCU mode
- Fader
b0 00
- push rotaries when turned
b0 10
b0 11
b0 12
b0 13
b0 14
b0 15
b0 16
b0 17
- push rotaries when pushed
90 20
90 21
90 22
90 23
90 24
90 25
90 26
90 27
- push Buttons
first row
90 59
90 5a
90 28
90 29
90 2a
90 2b
90 2c
90 2d
Second row
90 57
90 58
90 5b
90 5c
90 56
90 5d
90 5e
90 5f
- Layers Buttons
Layer A 90 54
Layer B 90 55
XTouchMini in normal midi mode
Layer A
- Fader
ba 09
- push rotaries when turned
ba 01
ba 02
ba 03
ba 04
ba 05
ba 06
ba 07
ba 08
- push rotaries when pushed
9a 01
9a 02
9a 03
9a 04
9a 05
9a 06
9a 07
9a 08
When the buttons are realeased, it displays the same but with 8a instead of 9a
- push Buttons
first row
9a 08
9a 09
9a 0A
9a 0B
9a 0C
9a 0D
9a 0E
9a 0F
second row
9a 10
9a 11
9a 12
9a 13
9a 14
9a 15
9a 16
9a 17
Layer B
- Fader
BA 0A
- push rotaries when turned
BA 0B
BA 0C
BA 0D
BA 0E
BA 0F
BA 10
BA 11
BA 12
- push rotaries when pushed
9A 18
9A 19
9A 1A
9A 1B
9A 1C
9A 1D
9A 1E
9A 1F
Same as above, when the buttons are realeased, it displays the same but with 8a instead of 9a
- push Buttons
first row
9A 20
9A 21
9A 22
9A 23
9A 24
9A 25
9A 26
9A 27
second row
9A 28
9A 29
9A 2A
9A 2B
9A 2C
9A 2D
9A 2E
9A 2F
Not sure how to continue now... Hope it helps !
|
Your best bet is to try and make a new .rst file for the XTouchMini and call it as such.
Basically you are assigning each midi value a name, the name is specific to the XTouchMini normally we go with as it says on the surface so if it's Marker then it's name is Marker and so on.
On the Mini you need to use the same convention as used on the Mackie C4.rst
It's just a matrix style rows and columns, just have a look in the CSI folder and you'll get the gist.
My only question (for Geoff) would be, should you label the Back, Foward, Loop, Stop, Play, Rec, buttons as those names or stick with the matrix label.
Also as far as Layers go, you need to assign names to both layers, A and B
I guess there are a few different logics you could use, ButtonAA (for layer A row A) AB (for layer A row B) and BA and BB (for layer B rows A and B) But that seems a little confusing, Maybe better to have AButtonA AbuttonB.
I think I'll leave it there and hope Geoff steps in to save me from myself.
|
|
|
08-26-2018, 07:09 AM
|
#1850
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Quote:
Originally Posted by Geoff Waddington
What happens if you remove the CMC-CH ?
|
Hey Geoff,
finally back in the studio. Nope, that didn't change anything.
|
|
|
08-26-2018, 09:02 AM
|
#1851
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Regisfofo
With CSI, Imanaged to turn pans et widths and do transports in reaper with my XtouchMini and the feedback showed up too!
|
Hi- Good work mapping out the X-Touch mini!
When you used it in MCU mode what did the fader control?
Quote:
Originally Posted by Regisfofo
Installation was not that easy thow, I had to supress the control instance shutdown in reaper prefs shutdown reaper and disconnect the xtouchmini each time I tweaked something or it would stay sudenly dead.
|
Are you using Win7? If so, then this is a known (and irritating) bug, well done for persevering!
Quote:
Originally Posted by Regisfofo
- push Buttons
first row
90 59
|
Was that all of the message? I would expect something like: 90 59 7f followed by 90 59 00 on release (in MCU mode) and the same for all the other controls.
This surface presents an interesting challenge for the syntax because it has 8 rotaries, two rows of buttons, but only one fader. As such it isn't really an 8 channel controller like an MCU nor a single channel device like a faderport or alpha track- hence my question about what the fader controlled in MCU mode.
|
|
|
08-27-2018, 02:33 AM
|
#1852
|
Human being with feelings
Join Date: Mar 2017
Location: France
Posts: 627
|
Thanks for your answers guys!
Quote:
Originally Posted by MixMonkey
When you used it in MCU mode what did the fader control?
|
In "normal" mcu mode, the XTouchMini controls master volume et the rotarys controls pan (and they set pan to middle when clicked).
So no means to change tracks volumes, bank up/down etc... Wich makes that mode pretty useless imho.
I think to use normal midi mode might be better, as it gives us almost twice the number of control other mcu.
Quote:
Originally Posted by MixMonkey
Are you using Win7? If so, then this is a known (and irritating) bug, well done for persevering!
|
I'm on win10 pro 64 bits.
Some times, restarting reaper is enough, but from time to time i have to disconnect the surface.
Quote:
Originally Posted by MixMonkey
Was that all of the message? I would expect something like: 90 59 7f followed by 90 59 00 on release (in MCU mode) and the same for all the other controls.
|
well, sorry I wasn't very clear. here is exactly what it shows for the first push-button : By default it's tuned on midi channel 11
9a 29 7f (when pushed)
8a 29 00 (when Released)
Isn't it strange that the first number change on same button?
I tried differents settings with the XTouchMini Software
Same button tuned to channel 10
99 20 7f
89 20 00
same button tuned to channel 2
91 20 7f
81 20 00
same button tuned to "cc" number "0" instead of "note", channel 2
b1 00 7f
b1 00 00
same button tuned to "cc" number "1",channel 2
b1 01 7f
b1 01 00
same button tuned to "cc" number "1", but midi channel 11
ba 01 7f
ba 01 00
same button tuned to "mcm" value "play", channel 11
f0 7f 7f
same button tuned to "mcm" value "stop", channel 11
f0 7f 7f (yes it's the same)
The two last digits are obviously max and min values,
The first one shows what kind of midi message
The second seems to follow the channel except with "mcm"
the thirds and forths, seems to be midi note's names or cc number.
I think, it would be simpler if we could stick with defaults settings
aka "notes" on channel 11 for buttons and CCs for fader and encoders, but I don't know if it is the best way to go.
Quote:
Originally Posted by Freex
Your best bet is to try and make a new .rst file for the XTouchMini and call it as such.
Basically you are assigning each midi value a name, the name is specific to the XTouchMini normally we go with as it says on the surface so if it's Marker then it's name is Marker and so on.
On the Mini you need to use the same convention as used on the Mackie C4.rst
It's just a matrix style rows and columns, just have a look in the CSI folder and you'll get the gist.
|
Ok, i'll look into that thanks!
Quote:
Originally Posted by Freex
My only question (for Geoff) would be, should you label the Back, Foward, Loop, Stop, Play, Rec, buttons as those names or stick with the matrix label.
Also as far as Layers go, you need to assign names to both layers, A and B
I guess there are a few different logics you could use, ButtonAA (for layer A row A) AB (for layer A row B) and BA and BB (for layer B rows A and B) But that seems a little confusing, Maybe better to have AButtonA AbuttonB.
I think I'll leave it there and hope Geoff steps in to save me from myself.
|
Don't know if it helps but in the berhinger software, they are named :
FD1 (the faders)
EN1 ... EN8 ,PUSH or TURN (the rotaries)
BT1 ... BT16 (the buttons)
I think to use originals labels may be misleading as there are two layers, and just a few controls are labelled anyway.
|
|
|
08-27-2018, 08:13 AM
|
#1853
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Regisfofo
I'm on win10 pro 64 bits.
|
OK, looks like this a bug affecting all Windows versions.
Quote:
Originally Posted by Regisfofo
In "normal" mcu mode, the XTouchMini controls master volume
|
I see, so you get to control 8 channels of pan etc, but no track volume It might be better to see if we can approach the X-Touch mini as if it were a single channel controller that could be 'banked' (in steps of one) across the tracks. That way you could use the fader to control track volume, the first rotary control pan, the second rotary control send and use the other rotaries and buttons for plugins, transport etc. Just thinking out loud here- this isn't something I've tried before.
Quote:
Originally Posted by Regisfofo
Isn't it strange that the first number change on same button?
|
Yes and no. It's actually sending a note on message when you press it and a note off message when you release it. Not sure it helps us much though, all the others I've seen so far have been note on at velocity 127 when pressed and note on at velocity 0 when released.
If you're up for it , we could try a little experiment to see if we could get the buttons working with CSI
Create a plain text file called: XTouchMini.rst and put this line in it:
Code:
ButtonA1U Press 9a 29 7f 9a 29 00
Put this file in the rst folder inside the CSI folder
Now create a plain text file called XTouchMini.axt and put this line in it:
Code:
ButtonA1U CycleTimeline
Put this file in the axt folder inside the CSI folder.
In the CSI prefs in Reaper create a new page called XTouchMini. Select the XTouchMini Page and in the surfaces box click add MIDI. In the dialog box enter the details for your XTouchMini- 1 channel, non bankable (for the time being), MIDI I/O and select the XTouchMini.rst and XTouchMini.axt in the little drop downs at the bottom of the box.
Click OK, then delete all the other Pages, leaving just your XTouchMini Page (you might want to back up the whole CSI folder before you do this)
Click OK and OK.
Now see if pushing upper button 1 (far LHS) toggles the cycle function in Reaper.
Last edited by MixMonkey; 08-28-2018 at 12:10 AM.
Reason: tyop
|
|
|
08-27-2018, 10:04 AM
|
#1854
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
I'm trying out the Faderport 16 here atm. That's going to be interesting.
I intend to try and use it with CSI as soon as the surface will actually get the automation data correctly. I can record automation with the faders, but the faders are not responding to the automation playback at all.
Some fun can be had with SYSEX'ing the display modes on the scribble strips. There are 10 modes.
And then there's all the fun button stuff. Most of it is easy to decipher from the midi monitor or well documented.
So far I'm liking this surface.
Geoff, I can see the data going to the Mackie Control Universal Device, but the faders aren't reacting to it. The control surface works fine with the stock MCU csurf(doing those few things well).
|
|
|
08-27-2018, 10:32 AM
|
#1855
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by airon
I can see the data going to the Mackie Control Universal Device, but the faders aren't reacting to it.
|
Mackie MCU and XT faders and pans responding to written moves here, but this was a recent fix. Do you have the latest version?
|
|
|
08-27-2018, 09:22 PM
|
#1856
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Quote:
Originally Posted by MixMonkey
Mackie MCU and XT faders and pans responding to written moves here, but this was a recent fix. Do you have the latest version?
|
That’s it then. Thanks.
|
|
|
08-28-2018, 12:22 AM
|
#1857
|
Human being with feelings
Join Date: Mar 2017
Location: France
Posts: 627
|
@MixMonkey Ok I'll do that when I come home this weekend.
|
|
|
08-28-2018, 08:59 AM
|
#1858
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by airon
That’s it then. Thanks.
|
I probably should have mentioned that you need to use the new .axt or at least the automation definitions from same. The definitions have changed to the standard Reaper actions.
|
|
|
08-28-2018, 01:32 PM
|
#1859
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Quote:
Originally Posted by Geoff Waddington
What happens if you remove the CMC-CH ?
|
Any idea what else I could do to make this work? Or will this need an update?
|
|
|
08-28-2018, 02:57 PM
|
#1860
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by _Stevie_
Any idea what else I could do to make this work? Or will this need an update?
|
Seems like you're doing everything fine, and the fact that the CMC-CH works great more or less proves that.
Do you have any other units to integrate ?
__________________
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
|
|
|
08-28-2018, 03:02 PM
|
#1861
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Yep, also got the CMC-AI.
So you think it's the CMC-QC that causes these problems?
|
|
|
08-28-2018, 03:06 PM
|
#1862
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by _Stevie_
Yep, also got the CMC-AI.
So you think it's the CMC-QC that causes these problems?
|
No idea, just trying to find a way to isolate the problem.
__________________
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
|
|
|
08-28-2018, 03:07 PM
|
#1863
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Quote:
Originally Posted by Geoff Waddington
No idea, just trying to find a way to isolate the problem.
|
You know what, I'm gonna try if the device works on my Mac. Just to see what happens... The CSI files should be working on my Mac as well, right?
|
|
|
08-28-2018, 04:17 PM
|
#1864
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by _Stevie_
You know what, I'm gonna try if the device works on my Mac. Just to see what happens... The CSI files should be working on my Mac as well, right?
|
Yes, they are exactly the same, just make sure to put everything in the right place as stated in the ReadMe.
__________________
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
|
|
|
08-29-2018, 01:45 AM
|
#1865
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by _Stevie_
The CSI files should be working on my Mac as well, right?
|
You might need to re-assign the MIDI ports- the numbers in the CSI.ini will probably be different.
|
|
|
08-29-2018, 02:48 AM
|
#1866
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by MixMonkey
You might need to re-assign the MIDI ports- the numbers in the CSI.ini will probably be different.
|
Oops, yes of course, my bad
__________________
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
|
|
|
08-29-2018, 10:33 AM
|
#1867
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Okay, got the device working, now on OSX and Windows. The encoder are functional when assigning them to Pan or the like. BUT, I can't control the VST plugin parameters, with neither of my devices. Either, I'm doing it wrong or something is broken.
|
|
|
08-29-2018, 10:53 AM
|
#1868
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Stevie, in the CMC-QC.rst, what's this?
Code:
RotaryFeedback EncoderFB b0 30 7f b0 30 00
Also, you don't have the Reacomp controls 'learnt' in the normal way do you?
|
|
|
08-29-2018, 10:59 AM
|
#1869
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Quote:
Originally Posted by MixMonkey
Stevie, in the CMC-QC.rst, what's this?
Code:
RotaryFeedback EncoderFB b0 30 7f b0 30 00
|
That's code from Geoff, but still undocumented. I think that way you can decouple the MIDI Feedback and assign it to a different CC (which is necessary for the CMC-QC).
Quote:
Also, you don't have the Reacomp controls 'learnt' in the normal way do you?
|
That's right. I will now check, if I can get VST parameters working on OSX. Maybe it's a Windows thing.
|
|
|
08-29-2018, 11:32 AM
|
#1870
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Nope, doesn't work either in OSX
|
|
|
08-29-2018, 11:55 AM
|
#1871
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Stevie, try deleting:
Code:
CompressorMeter GainReductionDB
from the ReaComp.fxt
|
|
|
08-29-2018, 12:30 PM
|
#1872
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Sorry, my bad. Delete:
Code:
Rotary8 GainReductionDB
from the ReaComp.fxt
|
|
|
08-29-2018, 12:44 PM
|
#1873
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Had one of those hunches...
Tried it out...
There is currently a bug whereby trailing spaces are not trimmed.
Make sure there are no spaces at the end of your fx name:
e.g. VST: ReaComp (Cockos)
Should apply to params as well.
__________________
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
|
|
|
08-29-2018, 12:54 PM
|
#1874
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Will try that, although, I just took over the provided ReaComp.fxt file.
|
|
|
08-29-2018, 01:11 PM
|
#1875
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
The MCU part for the Faderport16 is working well for volume on main faders. I'm trying out other stuff too, though in the long run I want to use the native stuff, i.e. the Studio One mode of the unit. It might hold more potential.
We've got a bunch of buttons on this unit that can change colour to indicate certain states and some that have just one colour because they're lit by one type of LED.
For example, the left column of buttons at the very left of the console, the manual lists those as
ARM led
Solo Clear led
Mute Clear led
Bypass rgb
Macro rgb
Link rgb
Shift led
Only in the cases of the rgb lights, do we have a special system for setting the colour of a button. Each button gets an id, which exeactly like the note numbers in the MCU stuff, and mostly matches up to that too.
The send button has the id 29 for example.
Thus just like in the MCU the SEND button is still 90 29 7f for PRESSED and 90 29 00 for RELEASED. The line
Code:
Send PressFB 90 29 7f 90 29 00
in an .RST file works fine.
Setting a 1-colour led on or off requires one of two commands.
Setting the colour of a button however requires three 3-byte midi sequences.
Red 91 id cc
Green 92 id cc
Blue 93 id cc
cc is the 7-bit colour value
This is useful stuff for the automation mode buttons for example.
Do we have session state feedback mechanisms yet ?
|
|
|
08-29-2018, 02:28 PM
|
#1876
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by airon
The MCU part for the Faderport16 is working well for volume on main faders. I'm trying out other stuff too, though in the long run I want to use the native stuff, i.e. the Studio One mode of the unit. It might hold more potential.
We've got a bunch of buttons on this unit that can change colour to indicate certain states and some that have just one colour because they're lit by one type of LED.
For example, the left column of buttons at the very left of the console, the manual lists those as
ARM led
Solo Clear led
Mute Clear led
Bypass rgb
Macro rgb
Link rgb
Shift led
Only in the cases of the rgb lights, do we have a special system for setting the colour of a button. Each button gets an id, which exeactly like the note numbers in the MCU stuff, and mostly matches up to that too.
The send button has the id 29 for example.
Thus just like in the MCU the SEND button is still 90 29 7f for PRESSED and 90 29 00 for RELEASED. The line
Code:
Send PressFB 90 29 7f 90 29 00
in an .RST file works fine.
Setting a 1-colour led on or off requires one of two commands.
Setting the colour of a button however requires three 3-byte midi sequences.
Red 91 id cc
Green 92 id cc
Blue 93 id cc
cc is the 7-bit colour value
This is useful stuff for the automation mode buttons for example.
Do we have session state feedback mechanisms yet ?
|
Right now automation works, but automation feedback doesn't because we are just using Reaper Actions, which are good for feedback on things like Metronome, or CyleTimeline, but don't work for multi-state items like automation.
Since cleaning up automation feedback was on the to-do list anyway, maybe let's work to exploit the colour features of the FP16 as we fix automation feedback -- have you thought about your dream solution using colours ?
[Edit]: Just downloaded the user manual -- which includes the midi spec -- thanks Presonus -- work to do in the display SysEx too, lots of fun to be had !!
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Last edited by Geoff Waddington; 08-29-2018 at 02:40 PM.
|
|
|
08-29-2018, 03:31 PM
|
#1877
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
I reckon we have two different states that we’d send feedback to hardware for.
Page choice, as send or fx edit would necessitate using a different page.
Reaper states. Automation modes, play status, solo status and so on.
Not sure we’d need more than a toggle.
Automation buttons require two colours, i.e. we need a freely definable number of commands.
Perhaps: ReaperState togglecommand-from-rst midimessageA midimessage-separator midimessageB
Example
autolatch latch 91 11 7f 92 11 50. 92 11 50 zz 91 11 20. 91 11 05. 91 11 05
That’s three midi 3-byte messages for each state of the Latch envelope mode. autolatch is the keyword to get that state, latch is what the .rst surface template defines as the toggle command coming from the control surface.
This would naturally go in to the .axt action template.
First shot at this. What do you think ?
|
|
|
08-29-2018, 04:28 PM
|
#1878
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Quote:
Originally Posted by MixMonkey
Sorry, my bad. Delete:
Code:
Rotary8 GainReductionDB
from the ReaComp.fxt
|
No luck, checked the fxt file for spaces at the end.
I actually deleted all lines and only kept: Rotary Tresh
Just to be sure!
I suspect there's something wrong with the fxt, maybe I'm missing something?
What's the easiest way to find out if fxt works on my system at all?
|
|
|
08-29-2018, 04:43 PM
|
#1879
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by _Stevie_
No luck, checked the fxt file for spaces at the end.
I actually deleted all lines and only kept: Rotary Tresh
Just to be sure!
I suspect there's something wrong with the fxt, maybe I'm missing something?
What's the easiest way to find out if fxt works on my system at all?
|
You mean Rotary 1 Thresh right ?
In which folder is ReaComp.fxt located ?
__________________
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
|
|
|
08-29-2018, 04:54 PM
|
#1880
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Quote:
Originally Posted by Geoff Waddington
You mean Rotary 1 Thresh right ?
In which folder is ReaComp.fxt located ?
|
It's indeed Rotary. I removed the Channel/ChannelEnd tags to single out another source of possible error.
So, only the first Rotary is configured (no additional encoders are automatically generated).
The fxt file is located in CMC-QC. Could the hyphen be the issue maybe?
|
|
|
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 09:38 PM.
|