|
|
|
02-04-2019, 05:18 PM
|
#2441
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by jamesd256
When I set up the midi device in BC Man and detect B-Controls, it complains about a midi loop.
|
Are you connected via USB or MIDI? I'm connected via USB using mode U-4. It is worth checking out page 25 of the BC Manager manual for advice on BCR setup. Pretty much everything I know about the BCR2000 came from that manual
Check the MIDI Devices Setup in Options/MIDI Devices. Only enable one MIDI In and One MIDI Out and disable MIDI Thru.
After you've solved the feedback problem and got BC Manager working correctly, it's a good idea to update the firmware. DL here: https://www.musictribe.com/Categorie...tive=Downloads
|
|
|
02-04-2019, 06:05 PM
|
#2442
|
Human being with feelings
Join Date: Apr 2018
Posts: 211
|
Multiple Surface With CSI
Is it possible to have multiple Instance of CSI in reaper.
CAuse I have a FaderPort 8 and a BCR2000 And I can't figure out how to add them both.
If I add Bcr and then the FP8 after, the FP8 does not respong.
If I add another instance of CSI with 1 surface in each, it does not work, they seems to conflict.
tks
Seby
|
|
|
02-04-2019, 06:33 PM
|
#2443
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by SebyMusic
Is it possible to have multiple Instance of CSI in reaper
|
No, but no need. Add them individually as MIDI surfaces in the CSI prefs.
But it's worth bearing in mind that at the moment they are probably mapped to the same functions (fader, pan. etc)
You need to think about how you're going to integrate the BCR2000 with the FP8. Maybe use the FP8 for fader, pans, mutes, solos etc and the BCR for plugins, for instance.
When you've worked that out, you can map the surfaces accordingly.
|
|
|
02-04-2019, 06:51 PM
|
#2444
|
Human being with feelings
Join Date: Apr 2018
Posts: 211
|
Quote:
Originally Posted by MixMonkey
No, but no need. Add them individually as MIDI surfaces in the CSI prefs.
But it's worth bearing in mind that at the moment they are probably mapped to the same functions (fader, pan. etc)
You need to think about how you're going to integrate the BCR2000 with the FP8. Maybe use the FP8 for fader, pans, mutes, solos etc and the BCR for plugins, for instance.
When you've worked that out, you can map the surfaces accordingly.
|
Like I sais, when I ADD a second controller in the same instance, it's not working, the 2nd controller does not respond or output anything.
|
|
|
02-04-2019, 07:07 PM
|
#2445
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Windows or Mac?
|
|
|
02-04-2019, 08:05 PM
|
#2446
|
Human being with feelings
Join Date: Apr 2018
Posts: 211
|
Quote:
Originally Posted by MixMonkey
Windows or Mac?
|
Windows
|
|
|
02-04-2019, 08:07 PM
|
#2447
|
Human being with feelings
Join Date: Apr 2018
Posts: 211
|
HHHHHHHHEEEEEEELLLLLLPPPPPPPP!!!!!
Oh my god, I don't know what's going on and what I have done...
I have installed the version 5.966 (pre2) and since then I have sooooooooo much problem with CSI, nothing is working and I don't know what to do. My FP8 is unusable now. Even if I re-installed the "normal" version, I still have those problems..
tks
Seby
|
|
|
02-05-2019, 05:21 AM
|
#2448
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by SebyMusic
Oh my god, I don't know what's going on and what I have done...
I have installed the version 5.966 (pre2) and since then I have sooooooooo much problem with CSI, nothing is working and I don't know what to do. My FP8 is unusable now. Even if I re-installed the "normal" version, I still have those problems..
tks
Seby
|
Restore from your backup?
|
|
|
02-05-2019, 05:42 AM
|
#2449
|
Human being with feelings
Join Date: Apr 2018
Posts: 211
|
Quote:
Originally Posted by MixMonkey
Restore from your backup?
|
Not sure to follow you, what backup? Is there a backup of the software somewhere?.
I don't even know where is the problem.
tks
Seby
|
|
|
02-05-2019, 07:47 AM
|
#2450
|
Human being with feelings
Join Date: Apr 2018
Posts: 211
|
Here'smy problem with my Reaper and CSI and FP8
|
|
|
02-05-2019, 08:10 AM
|
#2451
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by SebyMusic
|
I'd turn the CSI MIDI Monitor off first, those data streams are probably MCU display information. The Monitor produces a response lag which can lead you to believe that things are not working properly.
Beyond that, I'd completely uninstall Reaper and CSI and start again.
|
|
|
02-05-2019, 09:03 AM
|
#2452
|
Human being with feelings
Join Date: Apr 2018
Posts: 211
|
Possible to have an answer on that please Geoff? Tks
Quote:
Originally Posted by SebyMusic
Hi, can you please confirm me that it is possible with CSI or not please.
tks
Seby
On my BCR2000 how can I assign Encoders on different Sends?
Now, this one is working....
RotaryG1 TrackSendVolume
But this is what I want
RotaryG1 TrackSendVolume1
RotaryG2 TrackSendVolume2
RotaryG3 TrackSendVolume3
RotaryG4 TrackSendVolume4
etc...
tks
Seby
|
Tks for taking the time.
Seby
|
|
|
02-05-2019, 12:56 PM
|
#2453
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
BREAKING CHANGE COMING
Affects RST files only !!
.rst files will now all be renamed to .mst for Midi Surface Template.
The rst folder will be renamed to mst.
The CSI.ini entries must be changed from .rst to .mst
That's been planned for a while.
Now for the big one:
It's getting harder to add features because the parser is very simplistic, and I want to keep it that way.
The major impediment is the handy Channel/ChannelEnd notation.
If we remove that we can also remove SingleChannel and MasterChannel, they're all just single channel layouts.
So now Channel/ChannelEnd will simply mean any kind of channel.
The distinction will be in the role:
Fader1 Fader e0...
Fader2 Fader e1...
...
Fader8 Fader e7...
Fader9 MasterFader e8...
In fact, I believe things will be much more readable, because you will see each channel explicitly laid out in the .mst file.
There will be no need for a num channels entry in CSI.ini, the .mst file says it all.
Once set up, it's probably the least edited file in CSI.
OK, scream away... ducking
__________________
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-05-2019 at 01:10 PM.
|
|
|
02-05-2019, 03:25 PM
|
#2454
|
Human being with feelings
Join Date: Apr 2018
Posts: 211
|
Quote:
Originally Posted by Geoff Waddington
BREAKING CHANGE COMING
Affects RST files only !!
.rst files will now all be renamed to .mst for Midi Surface Template.
The rst folder will be renamed to mst.
The CSI.ini entries must be changed from .rst to .mst
That's been planned for a while.
Now for the big one:
It's getting harder to add features because the parser is very simplistic, and I want to keep it that way.
The major impediment is the handy Channel/ChannelEnd notation.
If we remove that we can also remove SingleChannel and MasterChannel, they're all just single channel layouts.
So now Channel/ChannelEnd will simply mean any kind of channel.
The distinction will be in the role:
Fader1 Fader e0...
Fader2 Fader e1...
...
Fader8 Fader e7...
Fader9 MasterFader e8...
In fact, I believe things will be much more readable, because you will see each channel explicitly laid out in the .mst file.
There will be no need for a num channels entry in CSI.ini, the .mst file says it all.
Once set up, it's probably the least edited file in CSI.
OK, scream away... ducking
|
Nice to hear Geoff, will it help for the sends question I sked earlier up here?
tks
Seby
|
|
|
02-05-2019, 03:30 PM
|
#2455
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
Quote:
Originally Posted by SebyMusic
Nice to hear Geoff, will it help for the sends question I sked earlier up here?
tks
Seby
|
Not immediately, but it is a necessary step to get there from here.
Your feature request will be possible when Zones and Overlays are added.
__________________
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-05-2019, 06:12 PM
|
#2456
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Geoff Waddington
OK, scream away... ducking
|
No probs here, bring it on
Will there be a Master Fader definition?(it sort of looks like it in your example)
How are things looking on the XYZ Overlay/Zone navigation thing?
A couple of questions came up whilst doing the BCR2000 map:
i) Is there a way of accessing TrackPan and TrackPanWidth on their own, without using the Rotary TrackCycle RotaryPush "TrackPan 0" "TrackPanWidth 1" construction? (I wanted to use the RotaryPush for TrackUniqueSelect, whilst using the Rotary for Pan)
ii) I only seem to be able to make TrackVolume work with the 14Bit e0 pitchbend controller (Fader14BitFB -60.0 12.0 e0 7f 7f e0 00 00) I can't make it work with Fader7BitFB and a b0 controller (the BCR2000 only seems to send 7Bit pitchbend data, so I was just going to use Fader7BitFB instead)
Neither of these are a big deal, just curious
BTW my master fader returned!- no idea what was going on there, but now it seems to be pinned to fader 9 without being pinned by me (if that makes sense) So that's OK
Also RotaryPush1 on the MCU doesn't flip between Pan and Width, it banks 1 right?? Can't find any reason for this. Every other RotaryPush behaves as expected.
|
|
|
02-05-2019, 06:35 PM
|
#2457
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
Quote:
Originally Posted by MixMonkey
No probs here, bring it on
Will there be a Master Fader definition?(it sort of looks like it in your example)
|
That was earlier today
There will be a MasterFader definition but it will be in the Overlay/Zone files.
The channel definitions will be in the Overlay/Zone files too.
The .mst file will be vastly simplified.
I will hack the .axt for now, it's basically going to be changing this:
Fader TrackVolume
to this:
Fader1 TrackVolume
Fader2 TrackVolume
Fader3 TrackVolume
Fader4 TrackVolume
...
etc.
Quote:
Originally Posted by MixMonkey
How are things looking on the XYZ Overlay/Zone navigation thing?
|
Coming along as this redesign indicates
Quote:
Originally Posted by MixMonkey
A couple of questions came up whilst doing the BCR2000 map:
i) Is there a way of accessing TrackPan and TrackPanWidth on their own, without using the Rotary TrackCycle RotaryPush "TrackPan 0" "TrackPanWidth 1" construction? (I wanted to use the RotaryPush for TrackUniqueSelect, whilst using the Rotary for Pan)
|
Does this not work for you ?
Rotary TrackPan 0
Quote:
Originally Posted by MixMonkey
ii) I only seem to be able to make TrackVolume work with the 14Bit e0 pitchbend controller (Fader14BitFB -60.0 12.0 e0 7f 7f e0 00 00) I can't make it work with Fader7BitFB and a b0 controller (the BCR2000 only seems to send 7Bit pitchbend data, so I was just going to use Fader7BitFB instead)
Neither of these are a big deal, just curious
|
Hmmm.. works here with the Console1 a la:
Fader Fader7BitFB b0 07 7f b0 07 00
Quote:
Originally Posted by MixMonkey
BTW my master fader returned!- no idea what was going on there, but now it seems to be pinned to fader 9 without being pinned by me (if that makes sense) So that's OK
|
Cool.
Quote:
Originally Posted by MixMonkey
Also RotaryPush1 on the MCU doesn't flip between Pan and Width, it banks 1 right?? Can't find any reason for this. Every other RotaryPush behaves as expected.
|
Turn on Midi in mon see what's up.
If that looks good sounds like a mapping issue.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
02-05-2019, 07:21 PM
|
#2458
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Geoff Waddington
Does this not work for you ?
Rotary TrackPan 0
|
Ah, forgot the 0 Will TrackPanWidth 1 also work?
Quote:
Hmmm.. works here with the Console1 a la:
Fader Fader7BitFB b0 07 7f b0 07 00
|
OK, will give it another go.
New developments are sounding exciting!
|
|
|
02-06-2019, 06:10 AM
|
#2459
|
Human being with feelings
Join Date: Apr 2018
Posts: 211
|
Quote:
Originally Posted by Geoff Waddington
Not immediately, but it is a necessary step to get there from here.
Your feature request will be possible when Zones and Overlays are added.
|
Hi Geoff, do you have an idea of when "approx" the new version will be out?
tks again for your great work sir.
Seby
|
|
|
02-06-2019, 06:20 AM
|
#2460
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
Quote:
Originally Posted by MixMonkey
Ah, forgot the 0 Will TrackPanWidth 1 also work?
|
Yup.
Quote:
Originally Posted by MixMonkey
New developments are sounding exciting!
|
Well...
A bit topsy turvy, and will require interim changes to .axt until we get Overlays/Zones working.
.mst files will have no notion of channels or anything else, they are simply a mapping from Midi message(s) to widget type and name.
Here is an excerpt from an .mst file:
Code:
BankLeft Press 90 2E 7f
BankRight Press 90 2F 7f
ChannelLeft Press 90 30 7f
ChannelRight Press 90 31 7f
Rewind PressFB 90 5b 7f 90 5b 00
FastForward PressFB 90 5c 7f 90 5c 00
Stop PressFB 90 5d 7f 90 5d 00
Play PressFB 90 5e 7f 90 5e 00
Record PressFB 90 5f 7f 90 5f 00
DisplayUpper1 MCUDisplayUpper 0
DisplayUpper2 MCUDisplayUpper 1
DisplayUpper3 MCUDisplayUpper 2
DisplayUpper4 MCUDisplayUpper 3
DisplayUpper5 MCUDisplayUpper 4
DisplayUpper6 MCUDisplayUpper 5
DisplayUpper7 MCUDisplayUpper 6
DisplayUpper8 MCUDisplayUpper 7
Fader1 Fader14BitFB e0 7f 7f e0 00 00
Fader2 Fader14BitFB e1 7f 7f e1 00 00
Fader3 Fader14BitFB e2 7f 7f e2 00 00
Fader4 Fader14BitFB e3 7f 7f e3 00 00
Fader5 Fader14BitFB e4 7f 7f e4 00 00
Fader6 Fader14BitFB e5 7f 7f e5 00 00
Fader7 Fader14BitFB e6 7f 7f e6 00 00
Fader8 Fader14BitFB e7 7f 7f e7 00 00
FaderTouch1 PressRelease 90 68 7f 90 68 00
FaderTouch2 PressRelease 90 69 7f 90 69 00
FaderTouch3 PressRelease 90 6a 7f 90 6a 00
FaderTouch4 PressRelease 90 6b 7f 90 6b 00
FaderTouch5 PressRelease 90 6c 7f 90 6c 00
FaderTouch6 PressRelease 90 6d 7f 90 6d 00
FaderTouch7 PressRelease 90 6e 7f 90 6e 00
FaderTouch8 PressRelease 90 6f 7f 90 6f 00
RotaryPush1 Press 90 20 7f
RotaryPush2 Press 90 21 7f
RotaryPush3 Press 90 22 7f
RotaryPush4 Press 90 23 7f
RotaryPush5 Press 90 24 7f
RotaryPush6 Press 90 25 7f
RotaryPush7 Press 90 26 7f
RotaryPush8 Press 90 27 7f
Rotary1 EncoderFB b0 10 7f b0 10 00
Rotary2 EncoderFB b0 11 7f b0 11 00
Rotary3 EncoderFB b0 12 7f b0 12 00
Rotary4 EncoderFB b0 13 7f b0 13 00
Rotary5 EncoderFB b0 14 7f b0 14 00
Rotary6 EncoderFB b0 15 7f b0 15 00
Rotary7 EncoderFB b0 16 7f b0 16 00
Rotary8 EncoderFB b0 17 7f b0 17 00
RecordArm1 PressFB 90 00 7f 90 00 00
RecordArm2 PressFB 90 01 7f 90 01 00
RecordArm3 PressFB 90 02 7f 90 02 00
RecordArm4 PressFB 90 03 7f 90 03 00
RecordArm5 PressFB 90 04 7f 90 04 00
RecordArm6 PressFB 90 05 7f 90 05 00
RecordArm7 PressFB 90 06 7f 90 06 00
RecordArm8 PressFB 90 07 7f 90 07 00
Solo1 PressFB 90 08 7f 90 08 00
Solo2 PressFB 90 09 7f 90 09 00
Solo3 PressFB 90 0a 7f 90 0a 00
Solo4 PressFB 90 0b 7f 90 0b 00
Solo5 PressFB 90 0c 7f 90 0c 00
Solo6 PressFB 90 0d 7f 90 0d 00
Solo7 PressFB 90 0e 7f 90 0e 00
Solo8 PressFB 90 0f 7f 90 0f 00
Mute1 PressFB 90 10 7f 90 10 00
Mute2 PressFB 90 11 7f 90 11 00
Mute3 PressFB 90 12 7f 90 12 00
Mute4 PressFB 90 13 7f 90 13 00
Mute5 PressFB 90 14 7f 90 14 00
Mute6 PressFB 90 15 7f 90 15 00
Mute7 PressFB 90 16 7f 90 16 00
Mute8 PressFB 90 17 7f 90 17 00
Select1 PressFB 90 18 7f 90 18 00
Select2 PressFB 90 19 7f 90 19 00
Select3 PressFB 90 1a 7f 90 1a 00
Select4 PressFB 90 1b 7f 90 1b 00
Select5 PressFB 90 1c 7f 90 1c 00
Select6 PressFB 90 1d 7f 90 1d 00
Select7 PressFB 90 1e 7f 90 1e 00
Select8 PressFB 90 1f 7f 90 1f 00
Notice how DisplayUpper now requires a trailing parameter for channel number.
Similarly, C4 will require row column style a la:
Code:
DisplayUpperA1 C4DisplayUpper 0 0
DisplayLowerA1 C4DisplayLower 0 0
RotaryPushA1 Press 90 20 7f
RotaryA1 EncoderFB b0 00 7f b0 00 00
DisplayUpperB1 C4DisplayUpper 1 0
DisplayLowerB1 C4DisplayLower 1 0
RotaryPushB1 Press 90 28 7f
RotaryB1 EncoderFB b0 08 7f b0 08 00
DisplayUpperC1 C4DisplayUpper 2 0
DisplayLowerC1 C4DisplayLower 2 0
RotaryPushC1 Press 90 30 7f
RotaryC1 EncoderFB b0 10 7f b0 10 00
DisplayUpperD1 C4DisplayUpper 3 0
DisplayLowerD1 C4DisplayLower 3 0
RotaryPushD1 Press 90 38 7f
RotaryD1 EncoderFB b0 18 7f b0 18 00
DisplayUpperA2 C4DisplayUpper 0 1
DisplayLowerA2 C4DisplayLower 0 1
RotaryPushA2 Press 90 21 7f
RotaryA2 EncoderFB b0 01 7f b0 01 00
There will be a new pair for .axt -- BankableChannel/BankableChannelEnd a la:
Code:
BankableChannel
DisplayUpper1 TrackTouchControlled TrackNameDisplay TrackVolumeDisplay
Fader1 TrackVolume
FaderTouch1 TrackTouch
Rotary1 TrackCycle RotaryPush "TrackPan 0" "TrackPanWidth 1"
Select1 TrackUniqueSelect
Shift+Select1 TrackRangeSelect
Control+Select1 TrackSelect
RecordArm1 TrackRecordArm
Mute1 TrackMute
Solo1 TrackSolo
BankableChannelEnd
BankableChannel
DisplayUpper2 TrackTouchControlled TrackNameDisplay TrackVolumeDisplay
Fader2 TrackVolume
FaderTouch2 TrackTouch
Rotary2 TrackCycle RotaryPush "TrackPan 0" "TrackPanWidth 1"
Select2 TrackUniqueSelect
Shift+Select2 TrackRangeSelect
Control+Select2 TrackSelect
RecordArm2 TrackRecordArm
Mute2 TrackMute
Solo2 TrackSolo
BankableChannelEnd
The BankableChannel syntax will be replaced by Zone definitions later.
The overall syntax is a lot cleaner, what do you think ?
__________________
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-06-2019 at 06:25 AM.
|
|
|
02-06-2019, 06:23 AM
|
#2461
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
Quote:
Originally Posted by SebyMusic
Hi Geoff, do you have an idea of when "approx" the new version will be out?
tks again for your great work sir.
Seby
|
Probably have an interim version within a week or so, and it will include:
GoPage PageName
and configurable refresh rate for the XTouch-like units:
Play PressFB 90 5e 7f 90 5e 00 0.5
As described above the .rst(now .mst) and .axt files will be changing.
__________________
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-06-2019, 07:36 AM
|
#2462
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Geoff Waddington
The overall syntax is a lot cleaner, what do you think ?
|
Though it's a lot longer, I think it will be easier to understand.
In the current format, when you look at the contents of the Channel...ChannelEnd construct in the .rst, you don't really get a sense of how many controls are being represented.
Also, if i'm right in interpreting it this way, you would now have individual access to any Widget (or group of Widgets) on the surface.
Conceivably you could decide to have 7 channels on your 8 channel surface dedicated to regular channel duties and bankable, and the 8th channel dedicated to Send for the currently selected channel.
Or am I jumping the gun here
Last edited by MixMonkey; 02-07-2019 at 07:02 AM.
Reason: Type the words, don't just think them....
|
|
|
02-06-2019, 09:46 AM
|
#2463
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
Quote:
Originally Posted by MixMonkey
Though it's a lot longer, I think it will be easier to understand.
In the current format, when you look at the contents of the Channel...ChannelEnd construct in the .rst, you don't really get a sense of how many controls are being represented.
|
Agreed.
Quote:
Originally Posted by MixMonkey
Also, if i'm right in interpreting it this way, you would now have individual access to any Widget (or group of Widgets) on the surface.
|
Yup.
Quote:
Originally Posted by MixMonkey
Conceivably you could decide to have 7 channels on your 8 channel surface dedicated to regular channel duties and bankable, and the 8th channel dedicated to Send for the currently channel.
Or am I jumping the gun here
|
Not jumping the gun at all, you could even have an Overlay/Zone setup where the odd channels were bankable representing tracks and the even channels were Send 1 for each of those tracks -- just a made up example, not sure it's useful in any way, but it shows the flexibility of moving those definitions out of the surface definition file
__________________
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-06-2019, 03:10 PM
|
#2464
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
hey everyone, this all sounds interesting and looking forward to what's coming next.
But, my concern over this new format for the MST is that, for someone who has say 16 channels to define (on ONE surface)...it's a LOT of extra work to setup. What happens when I add additional 8-channel extender in the near future? One can't simply copy/paste because several lines have to have updated channels, if I'm understanding this correctly.
With that said, has there been any thought into the UI so that a user could enter his info and the MST is created accordingly? I understand something like that is much further down the road, I'm mostly thinking about myself and how many more mistakes I can make with this new format :|
Don't get me wrong, I definitely see how this opens up more possibilities and I welcome anything that is progress
|
|
|
02-06-2019, 04:35 PM
|
#2465
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
Quote:
Originally Posted by poetnprophet
hey everyone, this all sounds interesting and looking forward to what's coming next.
But, my concern over this new format for the MST is that, for someone who has say 16 channels to define (on ONE surface)...it's a LOT of extra work to setup. What happens when I add additional 8-channel extender in the near future? One can't simply copy/paste because several lines have to have updated channels, if I'm understanding this correctly.
With that said, has there been any thought into the UI so that a user could enter his info and the MST is created accordingly? I understand something like that is much further down the road, I'm mostly thinking about myself and how many more mistakes I can make with this new format :|
Don't get me wrong, I definitely see how this opens up more possibilities and I welcome anything that is progress
|
Your point is well taken and I did think about this quite a bit.
I believe the new format, although more verbose, is more easily understood because it's more linear.
You can usually re-use things from the channel definitions for things like extenders, that's how I did it here when setting up the Artist Mixes and Control.
Also the new format is very simplistic and, once set up, should be very stable.
There will need to be only one file that everyone can use for each surface, so a single definition, although tedious and error prone to complete, can serve the whole community.
The vast majority of the customization will be in the easier-to-read files -- .axt, .fxt, 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-06-2019, 04:59 PM
|
#2466
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Quote:
Originally Posted by Geoff Waddington
There will need to be only one file that everyone can use for each surface, so a single definition, although tedious and error prone to complete, can serve the whole community.
The vast majority of the customization will be in the easier-to-read files -- .axt, .fxt, etc.
|
appreciate you, Geoff! This part is really cool, and does kinda negate some of my worries.
cheers dude!
dave
|
|
|
02-07-2019, 01:43 AM
|
#2467
|
Human being with feelings
Join Date: Nov 2014
Posts: 798
|
Quote:
Originally Posted by Geoff Waddington
There will need to be only one file that everyone can use for each surface, so a single definition, although tedious and error prone to complete, can serve the whole community.
|
I like this
|
|
|
02-07-2019, 05:49 PM
|
#2468
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
New build is up: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
BREAKING CHANGE !!!
It's a biggy, you will need all new files including CSI.ini, as well as all .mst and .axt files.
You can use the supplied ones as a starting point.
New features --
In the .mst, you can now specify a forced refresh interval:
Play PressFB 90 5e 7f 90 5e 00 0.5
The 0.5 is the number of seconds between forced refreshes -- aka the refresh interval.
In the .axt, you can now go to a named page:
SomeButton GoPage PageName
__________________
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-07-2019, 07:31 PM
|
#2469
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Oh boy, can't wait to try it.
Is that refresh modifier required, or can it be blank? I'm still not quite sure what it does actually.
Anxious to try this out so I might delve into it tonight
|
|
|
02-07-2019, 07:34 PM
|
#2470
|
Human being with feelings
Join Date: Jan 2019
Location: VT, USA
Posts: 11
|
Quote:
Originally Posted by Geoff Waddington
SomeButton GoPage PageName
|
Would there happen to be a current list of all the available CSI actions (as opposed to Reaper actions) for using in the .axt file(s)? Or are they all used in the existing files (and I should just compile my own list from those)? Thx.
|
|
|
02-08-2019, 04:06 AM
|
#2471
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
Quote:
Originally Posted by poetnprophet
Is that refresh modifier required, or can it be blank? I'm still not quite sure what it does actually.
|
It's optional -- for X Touch Compact and any other units that require refreshes.
Say you set it to 0.5.
That means that the widget will get it's value refreshed every 0.5 seconds, whether the value has changed or not.
__________________
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-08-2019, 04:12 AM
|
#2472
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
Quote:
Originally Posted by 40Hurts
Would there happen to be a current list of all the available CSI actions (as opposed to Reaper actions) for using in the .axt file(s)? Or are they all used in the existing files (and I should just compile my own list from those)? Thx.
|
Yeah, they're mostly in the .axt files, but they are in such a state of flux right now, they haven't been documented -- after all it's a pre alpha -- yeah I know poor excuse
__________________
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-08-2019, 06:07 AM
|
#2473
|
Human being with feelings
Join Date: Dec 2015
Location: Folkestone
Posts: 196
|
Quote:
Originally Posted by MixMonkey
Are you connected via USB or MIDI? I'm connected via USB using mode U-4. It is worth checking out page 25 of the BC Manager manual for advice on BCR setup. Pretty much everything I know about the BCR2000 came from that manual
Check the MIDI Devices Setup in Options/MIDI Devices. Only enable one MIDI In and One MIDI Out and disable MIDI Thru.
After you've solved the feedback problem and got BC Manager working correctly, it's a good idea to update the firmware. DL here: https://www.musictribe.com/Categorie...tive=Downloads
|
The BCR I'm using is a rescue job - doesn't work in USB mode. Has been working correctly in MIDI mode since I got it.
After attempting the syx dump as part of this exercise, I tried it via MIDI through 3 devices (Midisport 4x4, Roland UM-G1, and BCF2000), and it seems it's not working as before.
No midi activity lights on any of these interfaces now responds to knob turning, and BC Man doesn't detect the BCR any more at all.
I've tried factory reset (holding down button 1 during power up). I've also tried sending the syx for the 1.10 firmware via Midi-OX. The Midisport light flashes on in sync with the BCR input light, but the BCR doesn't go into sys-ex receive dance, and comes back on with 1.07, so the unit is receiving midi signals, but doesn't handle the syx as a firmware update.
Right now it seems it's toast
|
|
|
02-08-2019, 06:35 AM
|
#2474
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
Forgot to mention this trick from a while back that should (I haven't tested it) work, because you can have one button do a list of things (in this case just 2 things):
TrackButton GoPage Track
TrackButton Reaper 40454 // Screenset: Load window set #01
SendButton GoPage Sends
SendButton Reaper 40455 // Screenset: Load window set #02
EQButton GoPage EQ
EQButton Reaper 40456 // Screenset: Load window set #03
Can someone try this and see if it actually works ?
__________________
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-08-2019, 07:34 AM
|
#2475
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by jamesd256
The BCR I'm using is a rescue job - doesn't work in USB mode. Has been working correctly in MIDI mode since I got it.
After attempting the syx dump as part of this exercise, I tried it via MIDI through 3 devices (Midisport 4x4, Roland UM-G1, and BCF2000), and it seems it's not working as before.
No midi activity lights on any of these interfaces now responds to knob turning, and BC Man doesn't detect the BCR any more at all.
I've tried factory reset (holding down button 1 during power up). I've also tried sending the syx for the 1.10 firmware via Midi-OX. The Midisport light flashes on in sync with the BCR input light, but the BCR doesn't go into sys-ex receive dance, and comes back on with 1.07, so the unit is receiving midi signals, but doesn't handle the syx as a firmware update.
Right now it seems it's toast
|
Sorry to hear that
Regarding the MIDI mode the BCR is in, make sure you set it to S4 (just a thought, if it's toast, it's toast) S4 will get rid of the feedback loop.
|
|
|
02-08-2019, 09:05 AM
|
#2476
|
Human being with feelings
Join Date: Dec 2015
Location: Folkestone
Posts: 196
|
Quote:
Originally Posted by MixMonkey
Sorry to hear that
Regarding the MIDI mode the BCR is in, make sure you set it to S4 (just a thought, if it's toast, it's toast) S4 will get rid of the feedback loop.
|
Ok, after following your lead on operating modes, took the time to read the manual.
Good news, it's sending midi again. I guess the failed sysex operation knocked it out of s4 mode, or whatever mode it was in.
Hoping the USB issue was just down the modes, I went through all the modes and tried connecting USB, and always get device not recognised/malfunctioned.
Will try to do the dump again with BC Manager and report back
Thanks MixMonkey for your work on CSI and support with my BCR
Edit: No errors from BC Man during the dump this time. Looks like P1 has your settings as far as I can tell, but Reaper still not responding as expected.
I can think of 2 things - my CSI needs updating, or I should update the firmware to 1.10
Edit: fw updated successfully. Still no effect turning the push encoders in reaper (CSI setup the same, midi in showing what looks like valid logging data). Sadly fw update didn't bring USB connection back to life
Last edited by jamesd256; 02-08-2019 at 09:35 AM.
|
|
|
02-08-2019, 09:23 AM
|
#2477
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by jamesd256
Hoping the USB issue was just down the modes, I went through all the modes and tried connecting USB, and always get device not recognised/malfunctioned.
|
There have been reports of failing/malfunctioning USB connections on the BCR2000, so you might end up on MIDI. It's a bit slower to send data when setting ip but doesn't seem to make any difference in actual use.
|
|
|
02-08-2019, 11:14 AM
|
#2478
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
I swear I have done this half dozen times, but I could not get the new csi to be recognized last night.
Same install process, yes? .dll in plugins, CSI folder in Reaper resources?
|
|
|
02-08-2019, 11:36 AM
|
#2479
|
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,785
|
Quote:
Originally Posted by MixMonkey
There have been reports of failing/malfunctioning USB connections on the BCR2000
|
I dumped one or that reason
-Michael
|
|
|
02-08-2019, 11:45 AM
|
#2480
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,252
|
Quote:
Originally Posted by poetnprophet
I swear I have done this half dozen times, but I could not get the new csi to be recognized last night.
Same install process, yes? .dll in plugins, CSI folder in Reaper resources?
|
You used the new CSI.ini and the new .axt files 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
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 03:36 AM.
|