<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18702">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Guys,</FONT></DIV>
<DIV><FONT size=2 face=Arial>I'm just trying to set up a nice track template.
Nothing fancy. At some point in the setup, I get to the stage where reaper
context menus seem to be off by one track. If I arrow to track 2, the
context menus are showing me input and output parameters for track 1. And,
if I change those, it affects track 1, not 2. If I up arrow to track 1,
the context key gets me the track menu, not the output stuff. It doesn't
start out that way, but it gets that way as a result of editing the
settings.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Is there something I might have done to cause
that? Or is it just being a bad boy once again.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>I'm running version 3.76 just to not deal with the
context menu hassle, and since there isn't really anything I need in the later
versions. Unless it be absence of this lovely feature. That would be
nice. </FONT><FONT size=2 face=Arial>Can I prevent this?</FONT></DIV>
<DIV><FONT size=2 face=Arial>Or, Should I just scrap 3.76, and move on to the
latest batch of bugs.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Somewhere in the back of my mind is the nagging
notion that, if they spent half as much time worrying about correct, reliable
operation as they do over color tinting and icon saturation, we'd have a better,
more usable product.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV></BODY></HTML>