Re: Moving From ProTools to Linux? Good or bad?
- From: dawhead <google@xxxxxxxxxxxxx>
- Date: Sat, 3 Jan 2009 23:41:33 -0800 (PST)
On Jan 4, 1:31 am, Mike Rivers <mriv...@xxxxxxxxxxx> wrote:
dawhead wrote:
I tried to save a "view" but Ctrl-F1 (Save View 1) gets
me a System Monitor window.
your personal preferences are set up to "steal" Ctrl-F1.
No, SOMEBODY ELSE'S personal preferences are set up that way. I haven't
changed
anything like that since I installed the system from the distribution disk.
I wasn't seeking to imply that *you* set them up that way. I meant
"your personal preferences" to distinguish them from "general system
preferences". you are attempting to use a multi-user system which
carefully differentiates between the two.
you can
change those preferences or change the bindings that ardour uses.
Sure I can, but in order to get what I see from the pull-down menu, I
have to change them.
And I didn't even know they were there. I'll go look.
Nope, nothing in the Ardour menus that offers me a preference like that.
Windows -> Key Bindings
Maybe you're taking
about the System Monitor preferences? Nope, not there either. Maybe
there's a configuration
file that needs to be edited, stuck in the bowels of Linux.
On my system (Fedora 9): Main Menu -> System -> Preferences ->
Personal -> Keyboard Shortcuts
And what kind of logic employs the use of the same keystrokes to both
save a view and to
jump to that view. I assume that the "view" I'm talking about here has
to do with zoom level
and what you see on the screen (hopefully which screens are displayed).
the same kind of logic used by any hardware system that differentiates
between a short press and a long press. short press: switch to
requested view. long press: save requested view. "save views" are
editor-specific at present - they have no effect on which windows are
visible, window placement or layering. they might, particularly if
someone files a feature request to that effect, and even more likely
if they sponsor the issue. saved views are a relatively new feature
and like so any others, undocumented at this time.
To me, and probably every other person who has ever used another DAW,
what makes sense is:
Snap to grid
Magnetic snap
No snap
well i'm sorry, our choice of words here was determined by SAE who
felt that the current choices were best, based on their experience
with thousands of students and many other DAWs. so now who am i
supposed to pay attention to? so many users believe their perspective
is correct, but they often don't see the flow of many different
conflicting perspectives that arrives at the developers doorstep ...
there's also the little detail of he who pays the piper picks the
tune, and right now, SAE is paying the piper.
And not to start making this a forum for bug reports, but when moving a
region in the Magnetic snap
mode works on some edges,
its not clear from your report that you understand what magnetic snap
does. regular snap means that when you move objects around they are
only ever positioned on the current grid points - they jump from one
to the next. magnetic snap allows you to freely move them but they
"stick" briefly as they cross the grid points. if you'd like to file a
bug report in the bug tracker, i'd be happy to look into the behaviour
you describe. you need to include information about which grid setting
you were using.
Stuffit doesn't say that because its not true.
like that is frustrating
enough to make me want to just give up before I give it a fair evaluation.
"Hey, Dummy!
You have to start JACK before anything will work. Quit and do that first."
I suppose that as long as you can edit without hearing audio, Ardour
doesn't
care whether JACK is running or not, so I guess you got me there.
that is not what i meant at all. what i meant, and what i have said
several times already, is that Ardour is perfectly capable of starting
the JACK server all by itself if JACK has already been configured
correctly with (e.g.) qjackctl OR if you use Ardour's "Audio Setup"
dialog to configure it correctly. if it is misconfigured (which
happens a lot when people use consumer audio interfaces), then it
won't start correctly. but you still haven't described what actually
happens ("I forget what happened then") in a way that allows me to
comment on what is happening (or not happening) on your system.
.
- Follow-Ups:
- Re: Moving From ProTools to Linux? Good or bad?
- From: Mike Rivers
- Re: Moving From ProTools to Linux? Good or bad?
- References:
- Re: Moving From ProTools to Linux? Good or bad?
- From: Mike Rivers
- Re: Moving From ProTools to Linux? Good or bad?
- From: Scott Dorsey
- Re: Moving From ProTools to Linux? Good or bad?
- From: Mike Rivers
- Re: Moving From ProTools to Linux? Good or bad?
- From: philicorda
- Re: Moving From ProTools to Linux? Good or bad?
- From: Mike Rivers
- Re: Moving From ProTools to Linux? Good or bad?
- From: Mike Rivers
- Re: Moving From ProTools to Linux? Good or bad?
- From: dawhead
- Re: Moving From ProTools to Linux? Good or bad?
- From: Mike Rivers
- Re: Moving From ProTools to Linux? Good or bad?
- Prev by Date: Re: An Alternative to ProTools - sick and tired of it.
- Next by Date: Re: An Alternative to ProTools - sick and tired of it.
- Previous by thread: Re: Moving From ProTools to Linux? Good or bad?
- Next by thread: Re: Moving From ProTools to Linux? Good or bad?
- Index(es):
Relevant Pages
|