<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Interesting, I use two standard midi keyboard controlers, plus a BCF2000, and they all work fine, so it must just be something to do with the fadeport. But you can just plug any control surface or keyboard in and have it work with Reaper. This is one of the main reasons I moved from Protools to Reaper. You can use any control surface, and even control plugins with it, whereas with ProTools you had to spend thousands of pounds to get a control surface that allowed you to control plugins in ProTools.<br><br>Sent from my iPhone</div><div><br>On 17 Feb 2016, at 02:40, Christopher-Mark Gilland <<a href="mailto:clgilland07@gmail.com">clgilland07@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.23532">
<style></style>
<div><font size="2" face="Arial">Guys,</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">Mission accomplished. I now am up and
reaping! I'm a little frustrated though, but not because of another
problem. More, because of what caused! the problem.</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">So, here's the deal. Upon closer
investigation off list with another list member, we went through things over a
voice chat. this way, he could hear my speech and hear exactly what it was
doing. Sure enough, this was nothing at all I was doing wrong. There
really indeed was! something very very weird going on. Not only could I
not arm the track, but even worse, we had a few things going on here, and I'd
like to briefly outline those here, so that if someone else runs into this, they
won't spend 2 and a half days like I did trying to get things up and
working. LOL!</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">So first off, back before yesterday, when I first
started trying out Reaper last summer when I bought the thing, I think it was, I
started with using Rea Access. Now, for those of you newbies like Brandon,
or Beth, etc who never really had the chance to try Reaper with Rea Access, let
me say this. You all're at an advantage actually. You all are
starting with learning Osara, which is up to date, and what now is being
actively developed. Rea Access, as I understand it, is pretty much
dead. The problem is, if you're migrating over from Rea Access, then
you're gonna have a heck of a time with some things not working as you may
expect. I wish I had the money to get into the next Cavicast on Osara, but
I don't.</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">Anyway, so first off, I was trying to insert a new
track into my Reaper project with ctrl+T. It used to gbe with Rea Access,
this worked. It still works, but it's now a little different. Now,
this is bound to insert and name track, not just insert new track.</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">So, what was happening initially was, I was hitting
ctrl+T, then thinking like Rea Access, that it just popped a track into the
project. Bam! Done! Not quite though. I didn't realize
that after I hit ctrl+T, it doesn't actually seem to be adding the track until I
type a name for the track, then hit enter. This is awesome, as I can now
kill 2 birds with one stone. Before, I had to hit ctrl+T, then focus the
track, and then hit F2 to rename it, followed by the enter key to accept.
Now, I can do it all in one step. Go Osara!</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">The second issue was that damned Faderport control
surface was getting in the way. Yeah, I got it enabled, and yeah, I did
what Scott said by selecting the in and out ports, and by doing that, oh
sure. I got the thing working all right. I got it working almost
too! good! The thing is, the Faderport actually works as a midi device, in
and of itself. In other words, everything you do on the unit is translated
back and forth as midi event messages. I think in some DAWS, you actually
configure the thing as a HUI device, if that tells ya anything. My point
is, moral of the story, the stupid thing was sending midi events back and forth
in realtime and was really really confusing both Reaper, and even more so,
Osara. I have my suspitions what it actually was doing, but I can't
totally prove it, so I won't bore you with those details, as this already is
getting pretty long winded. Basically though, when I would try to up and
down arrow to move track by track, the Faderport was interfering.
Basically, it kept sending track volume messages back into Reaper. We
figured this out by looking in the menu bar under Edit. We then found
under undo, that it kept saying undo track volume change. Finally, the guy
helping me was like, huh? What the!</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">End of the story is, we unplugged the faderport,
and disabled it under control surfaces. We then restarted Reaper, and
guess what! Boom! Thinks started working totally as they
should. My up and down arrows now let me go track by track, as they
should, etc. So words to live by. The faderport is evil! I
can't speak for other surfaces, but I'm with Chris Bell on this. Seems
like, at least this! surface, almost gives more head ache than it's worth!
I'll use it in PT, but, never again in Reaper!</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">Chris.</font></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>RWP mailing list</span><br><span><a href="mailto:RWP@bluegrasspals.com">RWP@bluegrasspals.com</a></span><br><span><a href="http://bluegrasspals.com/mailman/listinfo/rwp">http://bluegrasspals.com/mailman/listinfo/rwp</a></span><br></div></blockquote></body></html>