So... first off, yes. I can! confirm that the issue Matthew Diemert is
having with the plugin parameters resetting when playing is not just
him.
I, too am noticing this odd behavior in PT 11. Again, I can confirm
just
as
Matt said, that this isn't occuring in any build of PT 10. It's only
happening in version 11.X.
Just out of a hunch, I tried something, and what do you know, it
worked.
What I did... let's just take his example with the 7 band E Q. I would
instantiate the plugin on... let's just say, insert A, for the sake of
simplisity. Now, without choosing a plugin, I go down to the high
pass
filter, and set the parameter to in. This way it's enabled. Then I go
down
to each band and set my configuration tweaks. Now, I hit space bar.
It
plays fine. I stop with space bar, then, I hit space bar again to
play.
As
soon as I do, the parameters get set back to default values, therefore
killing the tweaks I did.
So here's what I did to get around this. And, by the way, though it's
not
very practical necessarily, I'll definitely grant you that, it does!
consistently seem to be working for the time being. If you go into the
plugin's settings menu, regardless which plugin you're using, the E Q
was
only an example... the possibilities are literally endless, drop open
that
settings menu, and go to save preset. Now, save the preset with a
name.
Don't! and I repeat, don't! change the default directory where it's
trying
to save the preset to. If you do, you risk PT not being able later to
find
it. You want it showing up in your librarian menu, so keep that set as
is.
Go ahead though and name the preset, then hit save.
OK, now, if the parameters get reset, go back to the librarian menu,
and
pick your custom made saved preset. Once you do, it'll snap to, and
lock
on. By that, I mean, it'll stay put. Those parameters won't reset on
ya.
Again, I totally totally get that this is really not a very good
workflow.
I agree whole heartedly, but hey! It does! work. It might be a sloppy
way
a doing it, but for the time being, it looks like this is the sollution
work
around, so I hope that helps you guys, as far as that goes.
Now, on to my! problem. So, I have a theory what may be going on, and
I'm
gonna be testing my theory out here in a bit, but I'm noticing that
when
I
hit command+option+num pad plus or minus whilst no audio is selected,
the
nudge value doesn't seem to want to be changing like it used to. Yes.
Link
timeline in selection, and link track in edit selection or whatever
it's
called are both checked. There was one more option there in the
options
menu that needs to be checked, but I don't recall what it says. I know
it
when I see it, but I'm not at my mac right now to look. I will!
however
say
that I do! remember it being checked though, no question.
This is making doing my command+shift+num pad plus and minus very
difficult,
as I'm moving a bit too far each way. So, I'm trying to adjust that a
bit
and make the nudge slope if you will for lack of better term a bit
less...
Actually... quite a bit! less. It's not happening though. I'm getting
no
result at all. Yes. All the tracks which I need to manipulate are
definitely selected. I made double dawg sure of this, so that's not
the
problem, I don't think. By the way, this is happenning both in V 10,
and!
in V 11. I admit that I've not tried manually going into the edit
window
and changing it through the nudge value control. For all intents and
purpose, that would be more tedious for the project I'm trying to do.
That
said, I can try it, if you all would like me to, and report back. What
my
theory is though is, earlier back, about a week ago, when I first got
PT
11,
I was working on a session which I was cross mixing between V 10 and V
11.
Mainly as I have some plugs in V 10 that are also in 11, but 11 has
some
stuff not in 10. So I started recording in 10, then moved to 11 to
instantiate the things I needed from it. Anyhow, I went into the
counter
cluster in the edit window and set it to bars/beats. So now, I opened
a
new
session. I then immediately did my command+shift+I to import an audio
file.
I browsed for the karaoke track I wanna sing on top of. When I went
back
and looked later on, I remembered that the counter cluster was on
bars/beats. Obviously, this isn't gonna really work with a karaoke
track.
So, I set it back to mins/secs. What I'm wonderring is, being I did
that
*after!* key word, importing the audio, could that! be what is making
my
nudge value not work, and kind a screw up? Did I maybe confuse
ProTools
a
bit by doing it that way? Should I first have set it back to
mins/secs?
Then? started importing, or recording from scratch? That's the only
thing I
can think which may! potentially be causing this, as I've literally
done
nothing whatsoever aside from that differently since it was working.
So, yeah... any ideas?
Chris.
--
You received this message because you are subscribed to the Google
Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to [email protected].
For more options, visit https://groups.google.com/d/optout.
