I have spent a month working on this too..so here is what I found.Some of this is basic but her goes. The BCF must be on first. Go to midi preferences, I also activated the Remote on Port 1 input and output. For me the auto mapping only worked on Lives devices like eq and automation work great. I manualy mapped the other stuff. In P-1 I left Encoder Group 1 alone as thatseems to control the Live Devices. I use Encoder Group 2 for Panning. Group 3 for Sends. I just bought Live 9 so I have to get this to work. My frustration has been to map the 16 push buttons. I know just how you feel. I posted on this forum earlier with no responses so it can drive you nuts. Now I am using a combination of Keyboard mapping and midi mapping. I too have scoured the Internet and slowly I am having success. Just about to power up jLive 9 to see if my BCF got better!! I am a newbie but wanted to give you a little support. Things have come along way since I was recording in London on Ampex Reel to Reels at Pye studios for CBS..1969!! all the bestRichard From: bc2000@yahoogroups.com [mailto:bc2000@yahoogroups.com] On Behalf Of patgoodfellow Sent: Saturday, May 18, 2013 7:00 PM To: bc2000@yahoogroups.com Subject: [bc2000] Re: BCR & Ableton set-up - what the deuce?! Hey Maan... did you see the post I just made... haha-ha. I'm on the verge of taking this down to the river and seeing how water-tight it is... auto-mapping has failed for me so far - only the first set of functions work, i.e Operators A & B Oscillators only - nothing more. I can see that even for someone like me, the midi learn function is fairly straightforward... but with auto-mapping not working, does that mean I need to go to every device I might wanna use, and set it up manually? Do you customize the BCR mappings for every Ableton project (and save that to where?)? Or do you...... gah.... I've run out of words.. Hasn't someone already done the hard work on this? lol So I can just grab and upload their template upload it it to the BCR (with a nice pdf of the actual mappings - coz that's vital imo),and control Ableton's Devices with no fuss? Agreed on Yahoo groups... feels like the format hasn't changed since 1999. --- In bc2000@yahoogroups.com <mailto:bc2000%40yahoogroups.com> , "mmruijgrok" <senang@...> wrote: > > I know it is possible though. I'm on a forum where someone else with alot more knowlegde is setting up the BCR now. Having said that it's not that much of a big deal to assign MIDI-learn to different rotaries by hand and when you have BCR-Manager it should even be easier. > > OP don't give up yet! > > BTW. I really hate it that thus Yahoo-group is the only dedicated source for info on the BCR and BCF. Yahoo feels disorganized browsing messages and to me (I only joined 2 months ago) the community seems dead. Such a shame... > > > --- In bc2000@yahoogroups.com <mailto:bc2000%40yahoogroups.com> , Joey Robinson <jsrobinson@> wrote: > > > > I never could get my BCF or BCR to work the way I wanted in Ableton. I'd > > really love for them to work in a sensible manner but when I found myself > > watching Python tutorials to try and fix a controller, I had a realization > > on how much time I was wasting with no easily accessible solution, and > > stopped programming to go back and actually make some music. > > > > The knob resolutions were always off, but moreover, it was just the simple > > stuff that seemed to hard to get working right. All I wanted my BCR to do > > was control send knobs on channels, automatically without having to MIDI > > map every single stupid knob. Similarly with my BCF, the faders never > > mapped after channels 1-8 no matter how many scripts I tried from the net. > > > > I gave up, and bought a mixing desk. This solves 90% of the problems I > > wanted the BCR/BCF for in the first place. It still doesn't address the DAW > > send knobs for when I use in the box effects, but everything else is a > > dream. > > >
Message
RE: [bc2000] Re: BCR & Ableton set-up - what the deuce?!
2013-05-19 by Richard Stephen Melhuish
Attachments
- No local attachments were found for this message.