[Rwp] Arming track, and track view issue resolved: You're not gonna believe this!

[Christopher-Mark Gilland]

Definitely not.  I have a very very clean area where I have the surface 
sitting.  Plus, I may be a major neat freak, but I am extremely extremely 
careful about that type thing.  I always have to tell band members ok, the 
guitar stand isn't a coatrack, the piano isn't a dresser, the recliner isn't 
a drawer.  Point being, I don't put things in a position where other stuff 
can fall on top of it unknowingly.

Chris.

----- Original Message ----- 
From: "onlineeagle via RWP" <rwp at bluegrasspals.com>
To: "Reapers Without Peepers" <rwp at bluegrasspals.com>
Cc: "onlineeagle" <onlineeagle at googlemail.com>
Sent: Thursday, February 18, 2016 5:24 AM
Subject: Re: [Rwp] Arming track,and track view issue resolved: You're not 
gonna believe this!


> ai assume this isn't your issue Chris, but I once had a similar problem. 
> Midi values were being sent to my DAW, and I was utterly confused, until I 
> eventually realised that there was a book that had fallen on to some of 
> the keys of my keyboard, thus triggering midi.
>
> Sent from my iPhone
>
>> On 18 Feb 2016, at 01:10, Scott Chesworth <scottchesworth at gmail.com> 
>> wrote:
>>
>> Yep, used a couple of surfaces here too with no issues, an MCU and an
>> Alphatrack. I find it kinda unlikely that a surface that has been
>> specifically implemented would be this buggy without anyone raising
>> hell by now, but hey, anything's possible with Reaper. Keep us posted
>> Chris if you work with the other Chris and end up solving it, it'd be
>> interesting to know what's up.
>>
>>> On 2/17/16, onlineeagle via RWP <rwp at bluegrasspals.com> wrote:
>>> 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.
>>>
>>> Sent from my iPhone
>>>
>>>> On 17 Feb 2016, at 02:40, Christopher-Mark Gilland 
>>>> <clgilland07 at gmail.com>
>>>> wrote:
>>>>
>>>> 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.
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at bluegrasspals.com
>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp