So, I uninstalled completely 2022.12 and rolled back to the 2022.9 build after
fortunately finding the download in the download center of my Avid account.
Unfortunately, that didn't help.
Looks like I'm screwed!
Chris.
--
You received this message because you are subscribed to the Google
Well, damn! So, you're getting very similar results to me. At least you can
open a new session. I can't even do that!
Chris.
> On Mar 14, 2023, at 11:06 PM, Martin (Punky) Sopart
> wrote:
>
> Hello all!
>
> I'm running the latest Pro Tools 2022.12 under Ventura 13.2.1.
> Pro Tools opens
Could not create a new document because Assertion in
"/Users/autobld/gitlabci/PT_COLOR/ProTools/App/Misc/UDashboardListView.cpp",
line 1189.
(Use the Copy button to copy this message to the clipboard.).
--
You received this message because you are subscribed to the Google Groups "Pro
Tools
So, I just ran ProTools after doing that upgrade from 2022.9 to 2022.3, and
now, though ProTools is working correctly, any darn time I go to the dash with
Command+N as soon as I go to the create tab in the dash, I get the following
error:
Could not create a new document because Assertion in
Hello all!
I'm running the latest Pro Tools 2022.12 under Ventura 13.2.1.
Pro Tools opens without any message or warning and I'm able to create new
sessions.
I'm further able to open decent existing sessions without any issue.
But when I try to open e.g. the current Pro Tools demo session or
Sorry, no informations regarding the synth...
On Mar 15, 2023, at 3:08 AM,
wrote:
Yup, I got the temporary installer. My friend sent it to me the other day for
Ventura. Looks like I was already on the most up to date version though,
although ProTools definitely needed updating.
That's now
Yup, I got the temporary installer. My friend sent it to me the other day for
Ventura. Looks like I was already on the most up to date version though,
although ProTools definitely needed updating.
That's now taken care of. Do you know anything about that virtual synth I
referenced?
Chris.
Hello Chris!
If Pro Tools is running, go to the system menus and check the Flo Tools version
in the Keyboard Maestro sub menu.
Current version still is 2022.4.
In addition you can find an installer for Ventura in the PTAccess Dropbox.
Best! / Martin
On Mar 15, 2023, at 2:55 AM,
wrote:
Wow, I need to get with the ball game! I was only on 22.9. Where do I go to see
if I'm on the most recent FloTools, and if I'm not, can I just install over the
top?
Also where do I find that new synth with over several hundred presets, or has
that not yet been quite released yet. I got an
Hello Chris!
Are you running Pro Tools 2022.12 or an older version?
Go to the status menus and quit the Keyboard Maestro engine.
After that, try again.
If the issue still exists, it's a new Pro Tools keyboard shortcut and not a Flo
Tools thing.
You could try to free up the shortcuts again by
Shawn,
In regards to guitar rig, I've heard of some people with VOCR that got it to
work, kind of sort of, but I sure never could get it to work that way.
Now that said, if you have a Native Instruments Komplete Kontrol midi
controller, then yes, it's completely accessible, but realize that
Hi Steve,
Man I sure appreciate the info. IK has some good stuff, so it sucks hard that
we can’t access it. Their loss I guess… I was also looking at amp hub, so
thanks for letting me know that it is useable. I’m guessing guitar rig is also
not accessible for VO users?
Thanks again Steve,
I beg to differ. I'm doing this inside of a plug-in window. Specifically, I'm
doing it inside of the waves epic reverb, and delays. However, it's doing this
inside of ProTools, regardless where I'm at. It doesn't matter the plug-in,
it's doing it regardless.
You are correct in saying that you
In what window is this happening to you? It works fine for me but I only ever
use VOCR in plug in windows. You shouldn't need it anywhere else, as far as I'm
aware. And that flow tools command shouldn't execute when in a plug in window
because it has no effect on that plug in and the tracks are
The command to move item by item after scanning a window with V O C R is
CTRL+Command+left and right arrows.
Unfortunately, this is seeming to get sent through to FloTools, and isn't being
interpreted by V O C R. So, I'm curious therefore how to go about fixing this.
Right now, it's switching
15 matches
Mail list logo
