[RWP] Success Running Reaper With Behringer BCF2000

[indigo]

You know, Scott, after reading the text that PDF2TXT put out after OCR, 
I realize that an OCR is not going to help much with these Behringer 
documents.
 From the ones I printed out as bit maps, that my wife looked at, 
Behringer has pictures of the front panel, with a few words of 
identification or instruction here and there on the page; near the 
control it refers to.
Without the pictures of the control in question; the info around all the 
controls, when it's converted to text;  just sstacks up in a vertical 
list, has lost its association with a control it belonged to, and makes 
no sense at all.
I'll try to get it human read, in the old fashioned way, take notes, 
then write it out in a tutorial

Thanks,
Indigo L
.


On 2/11/2012 2:59 PM, Scott Chesworth wrote:
> Hi Indigo,
>
> Just a thought, I wonder whether something like DocuScan Plus from
> Serotek might be able to OCR those Behringer PDF's? Last time I
> checked in, they were running a free 7 day trial.
>
> Scott
>
> On 2/11/12, indigo<33indigo at charter.net>  wrote:
>> Hi Scott,
>> I've set it up twice now, because last night I updated the Behringer USB
>> midi driver and managed to make the setup stop working.
>> Yes, it is a very strange configuration procedure from my screenreader.
>> I think decades of running winize, with no help from scripts, has taught
>> me to try every possible move to reach elusive buttons; especially using
>> the number padcursor.
>>
>> I've only done it in Window-Eyes, and I couldn't have got it done
>> without Wineyes's read previous and read next item; numpad insert plus 7
>> or 9; which exposed a little blank area just before the Midi Input and
>> Midi output buttons.
>> As sometimes occurs, Winize is speaking the buttons a few pixels off
>> their correct position, so no amount of clicking on those buttons gets
>> them to react.
>> My wife had no problem left clicking them from the physical mouse.
>>
>> In winize, when I left clicked from the number pad in that little
>> blankplace just before the spoken button, the list of choices for Midi
>> Input and Midi Output appear at the arrow keys.
>> I'll try looking at the same assignment procedure with Jaws 10 today, to
>> learn how to do it with Jaws.
>> I honestly don't know if N V D A can be made to provide enough
>> information to do the assignment, since it's review from the number pad
>> is very limited; but Sometimes N V D A surprises me by providing more
>> info than Window-Eyes at the tab and arrow keys, I hope so in this case.
>> By doing it twice now, I've simplified the procedure, and eliminated
>> some of the unnecessary moves.
>>
>> Except for easy writing and reading automation, so far, everything you
>> get from the BCF2000 you can do from ReaAccess, it's just quicker and
>> more impressive from a control surface.
>>
>> Now, the puzzle has become determining exactly what the control surface
>> buttons and their shift buttons are doing in Reaper.
>> To make it all even more fun, way too many of the Behringer PDF
>> documents are in bit map image.
>> Well, eventually I hope to get those read by my very busy wife, so I'll
>> somehow get it all sorted out.
>> Indigo L
>>
>> On 2/11/2012 1:58 PM, Scott Chesworth wrote:
>>> Awesome, even if the setup process is a little strange.
>>>
>>> Keep us posted on how you get on when you throw Tim's MDR into the mix
>>> man.
>>>
>>> Scott
>>>
>>> On 2/10/12, indigo<33indigo at charter.net>   wrote:
>>>> Yea, I think I got it!
>>>> I followed a combination of directions from a YouTube video, and the
>>>> directions I got from a Gear Heads forum.
>>>> In my Reaper 3.78, Windows XP 32 bit, and Window-Eyes 6.1, the BCF2000
>>>> must be disabled in Reaper's options/preferences/Midi Devices; just the
>>>> opposite of
>>>> the directions for running Sonar with the Mackie Display Reader, where
>>>> the BCF2000 must be enabled in Sonar's Midi Devices.
>>>> I set the BCR2000 in Mackie Mode Sonar, opened reaper, went to
>>>> options/preferences/midi devices, enabled and then disabled the BCF2000
>>>> settings; just to wake up the settings and make sure they took.
>>>> This time I got the apply button that should have been there before, but
>>>> wasn't.
>>>> I hit apply; then okay.
>>>> Then I went to Reaper's options/preferences/control surface; double
>>>> clicked on the Remove button at the number pad; to removed any previous
>>>> assignment, double clicked on add and selected Mackie Mode Universal
>>>> from the list of 8 modes the BCF2000 sends.
>>>> I went to the number pad and single left clicked on Mackie Mode
>>>> Universal, and got Mackie DEV 55; 1 of 1;  in that same edit boxwhere
>>>> Mackie Mode Universal was shown before.
>>>> Still at the number pad, I went to Midi Output, and this time the
>>>> current input and output settings were shown on a line above Midi Input
>>>> and on a line above Midi Output.
>>>> I single left clicked each of the setting that were displayed; and a
>>>> menu dropped at the arrow keys.
>>>> The BCF2000 shows 2 settings in Midi Input, BCF2000, and below that
>>>> BCF2000, with a 2 in parentheses.
>>>> I selected the top setting.
>>>> In Midi Output the BCF2000 shows 3 settings, BCF2000, below that BCF2000
>>>> (2) and below that BCF2000 (3).
>>>> I also chose the top setting for Midi output
>>>> Then I hit okay, closed and reopened Reaper, and the faders immediately
>>>> jumped to tracks 1 through 8, I pushed the right bank button and the
>>>> faders jumped to tracks 9 through 16, then 17 through 24, etcetera;
>>>> through the 32 track project.
>>>> Each time the faders jumped to a different bank of tracks they took a
>>>> different position, showing that Reaper is sending track level
>>>> information to the BCF2000, and the fader positions indicate the track's
>>>> level.
>>>> The transport buttons work as expected. The V Pots send pan for each
>>>> track..
>>>> In Reaper the top mute button sets a marker at the current position, and
>>>> holding the upper shift button while pressing the top button mutes the
>>>> track, not quite the same as in Sonar.
>>>> I'm sure there are many more settings to discover yet, with the
>>>> combinations of shift buttons and other buttons.
>>>> Best of all, ReaAccess seems totally unaffected, everything I tested in
>>>> ReaAccess still works as expected.
>>>> When I exit Reaper I no longer lose speech, as in my last experiment
>>>> It looks very  much like the BCF2000 adds to the access we already get
>>>> from ReaAccess, to do automations, and should be very useful during
>>>> mixdown.
>>>> I even got some speech from ReaAccess, announcing setting Marker 1 when
>>>> I pushed the top button.
>>>>
>>>> Now I'm wondering what those other BCF2000 settings in Midi Input and
>>>> Midi Output will do.
>>>> Next, I'll try connecting Tim Burgess's Mackie Display Reader between
>>>> the BCF2000 and Reaper, with virtual midi cables, and maybe I'll get
>>>> spoken feedback as to what each of the BCF2000's controls is doing.
>>>> Indigo L
>>>>
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at reaaccess.com
>>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>>>
>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at reaaccess.com
>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>>
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>