Re: [Qtractor-devel] Playhead click moving

[Rui N. C. <rn...@rn...>]

On 12/21/2015 12:22 PM, Philip Yassin wrote:
> Hi everyone!
>
> It's cold out there and the new Qtractor 0.7.2 is fresh out :) life is
> peachy
>
> I have my empty session in front of me, and something strikes me.
> When I click in the timeline (I have two tracks, and nothing in it)
> nothing happens.

> That must be one of the reasons why the new users that I saw approaching
> it (not that many but still quite a few) found it "user hostile" (my
> daughter texted me that /this very morning///, adding that "the
> interface is even worse than cubase's" das my girl :) I think this is
> excessive to say the least) sometimes, it does nothing when you expect
> it to do something.

tell your doughter to make (or text if she likes) some festure 
requests--even better, nurture her to get into the open-source community 
and rant away for her self! ;)


> Clicking in the timeline on an empty zone of a track could position the
> playhead at that location. Heck, even (optionally) in a non-empty zone,
> when selecting a clip, I can see how some ppl would use it like that. I
> think I would.
> At the very least, clicking in the empty zone below the track could do
> that, instead of doing nothing.
>

it's been o long departure from early days, but did you ever thought 
that shift-click would do exactly what you/she want?


> I humbly thing it would go a long way towards peace, harmony and
> downright happiness :)
>
> Maybe with the mid... Hey, the middle button /does/ something! It
> positions the two markers... Wow... All across the timeline window...
> Countless moons and I didn't know that... Damned, that kinda ruins my
> previous rambling, well, at least half of it. Now, Qtractor does
> something. And let me tell you, it is a /very/ nice feeling, moving the
> markers around with a single click. Oh, and it doesn't mess with an
> existing loop markers, too, nice. Id love to move the playhead as well
> that way, instead of this "middle click, forward key (or is the playhead
> ahead in that case backwards)" foggy business, and come to think of it,
> I would not mind if that would only move the transcient, invisible "last
> play position" and not the left & right markers. So that basically would
> just move the playhead. Can't that be an option? I might add to my case
> that this is the standard behaviour in the timelines of most of the
> software I saw. I have Kdenlive opened now, and that is what it does,
> only with the left mouse button. Doing like the elders say is often a
> (the) good path :)

middle-click behavior can be optionally reversed... indeed, that was 
once a long time ago a request from danboid, for which i made it so. i 
don't always indulge on dan's requests (you can put that 
most-interesting-man-meme here:) but... just think on tempo ramps and 
what not :D

>
> Second: Is there a technical reason why the "spacebar" play (and the
> moving between markers) is disabled while a plugin interface is opened?
> I know it can be solved with a control surface. Aaah, yes, I know.
> That's because one can have a need for his space key /inside/ the plugin
> interface to enter letters, like to name a preset. Hm. Feel free to
> ignore me :/
>

spacebar is a hard-coded keyboard shortcut (cf. Help/Shortcuts...) and 
as such it only works when the main window is in focus. that said, when 
any other window gets on top, like some plugins GUI's do, qtractor is 
blind-folded re. keyboard shortcuts. and yes, MIDI controller shortcuts 
don't suffer from this GUI window focus state-of-things. :)

> I guess I just wanted to say hi ;) and thanks again for Qtractor. Hey,
> why can't we see the list of presets of SynthV1 (which is really a mean
> polyphonic beast but I already said that) in the track's right-click
> "preset" menu like in other well-groomed plugins? ;)
>

there are synthv1 presets and there are, otoh. qtractor named presets, 
which includes system wide lv2 presets btw. the later are the ones you 
have access from the generic plugin/properties... dialog. the former are 
specific to the plugin in question. that said, you can certainly map 
ones into the others. i guess that will be straightforward once you 
realize the difference.

hth.
cheers
-- 
rncbc aka. Rui Nuno Capela