Bc2000 (for the BCF2000 & BCR2000)

Hi all,

i read here (i guess it was on BCnScript documentation) that you can't 
use both .easypar and .tx with a button....i did it "by mistake", and i 
realized it works! maybe i lost some documentation update, and i'm the 
only one who didn't know it....however, it works (and i'm pretty happy 
about it!)
BTW, i did it on the push encoder buttons, so i don't know if it works 
for standard buttons (but i don't see any reason why it shouldn't 
work...)

Ciao,
Goyya

Hi Royce,

> with .tx you can have quite a few MIDI messages so you don't really 
need
yes of course - i just keep on using it because as far as i have 
understood the button/encoder gets feedback only on .easypar...so 
actually i'm using both (telling this because maybe it could be 
interesting for someone):

- my BCR&BCF are routed through Usine, and from Usine to Cubase 
trhough midiyoke
- each .easypar is assigned in Cubase remote control panel (and 
feedback from the host is a nice feature...), the .tx messages are 
assigned to Usine functions (to switch the midi channel on which 
Usine passes the .easypar messages to Cubase)
- in this way with the same button i can open insert 1,2,...,8 of a 
track (Cubase) and aat the same time route the BCR messages (enc33-
enc56) on channel 1,...,8 using just one program (Cubase it's not 
able to "sense" the active insert, so i had to make a set of 24 CCs 
for each insert, with the same CCs on different channels)

at the beginning i used 8 bcr programs, but i was tired of passing 
from one to the other....

Take care,
Francesco ^_^

Hi Francesco 

> > with .tx you can have quite a few MIDI messages so you don't really 
> need
> yes of course - i just keep on using it because as far as i have 
> understood the button/encoder gets feedback only on .easypar...so 
> actually i'm using both (telling this because maybe it could be 
> interesting for someone):

This well. A great use for doubling up tx with easypar

> 
> - my BCR&BCF are routed through Usine, and from Usine to Cubase 
> trhough midiyoke
> - each .easypar is assigned in Cubase remote control panel (and 
> feedback from the host is a nice feature...), the .tx messages are 
> assigned to Usine functions (to switch the midi channel on which 
> Usine passes the .easypar messages to Cubase)
> - in this way with the same button i can open insert 1,2,...,8 of a 
> track (Cubase) and aat the same time route the BCR messages (enc33-
> enc56) on channel 1,...,8 using just one program (Cubase it's not 
> able to "sense" the active insert, so i had to make a set of 24 CCs 
> for each insert, with the same CCs on different channels)
> 
> at the beginning i used 8 bcr programs, but i was tired of passing 
> from one to the other....

Very clever. I think I might steal this idea myself.

Royce