[quote user="camoscato"] [quote user="Ryan Schoonmaker"]I hope AVID gets this straightened out, but I'm not going to hold my breath.[/quote] I wouldn't, either. Avid can't make Apple undo the decision to eliminate support for 32-bit apps in Catalina and later versions of the Mac OS, and Avid can't make Apple bring

[quote user="Pat Horridge"] Unfortunatley QT 10 is a scaled back version of QT you need the older QT version to get the full functionality and if your OS won't support that you can't get it. [/quote] Thanks, yea I'm on Big Sur and I believe anything past Catalina does not support QT7. I hope AVID gets this straightened out, but

[quote user="Avarice"] I had the same thing... Brand new custom PC, fresh install of WIN 10 and no importing of .mov or .m4a. Saw your posts and read the doc. There is a small bit which refers to falling back to QuickTime if UME doesn't work... -->>>SOLUTION FOR ME: Install QuickTime Player 7.7.9, reboot and everything imports

Hmmmmm I definitely don't fit under all of the categories in that document of what can and can't be done. Of course I haven't tried them all, but I can export MP4, and can Link to any files I've tried...whereas that doc says no exporting mp4 or Linking to certain codecs of MOV and MP4. I also find it odd that there is no error message

I find it cumbersome. I don't mind waiting, I mind extra steps. Importing is a one step process... 1. Point browser to file, click OK...wait. AMA is more steps, unless I'm doing it wrong 1. Point browser to file, click OK 2. Right Click AMA file in bin, click transcode. 3. Set Transcode options, click OK...wait. Also, if you don't have the

When I go to direct import a .MOV file from my GFX guy, I get nothing at all. No error message, no hanging progress bar...just nothing. I can import .wav files, but the same thing happens with .m4a files...just nothing at all. Obviously the workaround is to AMA them, but I would rather not AMA and then transcode everything I ingest. Is this a known

[quote user="MikeyB"] [quote user="Ryan Schoonmaker"]Any idea why this works?[/quote] It's due to a new Workspace behaviour in 2021.6 that doesn't always - behave - as it should. If you look in your Interface settings, there's an item "When moving to a Workspace load:" and its choices are "Last known state"

[quote user="Pat Horridge"] And that still happens after creating fresh new user settings? [/quote] Unfortunately, yes.

[quote user="MikeyB"] What about if you hold the Alt key as you recall the workspace? [/quote] This did the trick! Nice workaround! Any idea why this works?

Hi - I have the same error (and others) Basically I have a custom Color Correction workspace. When I load that workspace, the CC tool is completely gone. The only way to get it to come back it to revert the workspace to the default. Also, I have to do this every single time. So, I will revert the workspace to default, save it as the "color correction