[Rwp] Arming track, and track view issue resolved: You're not gonna believe this!
Christopher-Mark Gilland
clgilland07 at gmail.com
Tue Feb 16 21:40:10 EST 2016
Guys,
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.
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!
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.
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.
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!
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!
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!
Chris.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bluegrasspals.com/pipermail/rwp/attachments/20160216/89b21bbb/attachment.html>
More information about the RWP
mailing list