brmj.page at gmail.com
Mon Dec 16 08:06:22 PST 2013
Thanks for the pointers. I'll keep a lookout for details that might help
narrow down the issue.
On 16 December 2013 16:50, Don Estabrook <don.estabrook at gmail.com> wrote:
> Sorry for the late reply.
> On Fri 2013-12-13 15:51:57 -0800, John Page wrote:
> > one thing that bugs me is that sometimes ardour stops responding to the
> > keypresses that should act on the region below the mouse, for example
> > or 'delete'.
> This may not be relevant at all, but I see the same/similar thing
> fairly often, and my GUI setup is usually pretty simple - editor and
> mixer on one display -- not to say there still couldn't be something
> going on with focus on widgets, logs, etc, as Joern suggested -- but
> for me, I discovered that if I un-select everything (Edit > Select >
> Deselect All; something I do so often now that I've bound it to a key)
> and then (re)select the region(s) I want to affect, the 's' or
> whatever works every time. In most cases I'm not aware that I had
> anything else selected before that -- well, most times I'm not really
> sure, but in a few cases I actually looked carefully for selected
> regions and didn't see any. But I suppose _something_ could've been
> selected - a mark or automation point, for example.
> - Don
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ardour-Users