I just got an old 2010 5,1 mac pro for free. Thinking about upgrading to dual x5690 cpus (theyre $70 each on ebay by reputable sellers) and maxing out the ram to 128gb (it may be 96gb usable). Anyone doing this? What are your results? Anyone running MC 2019 on it?
thx
ps: I did a search for x5690 and didn't get much.
This is my most basic feature request ever.
Having 1 shortcut key to mute a clip (my U key) and making another shortcut key to unmute (shift U) seems a little redundent.
Can it just be the same shortcut key to mute and unmute?
just a suggestion. thank you
Hi all,
I'm looking for some advice with an ingest issue we've all of a sudden begun to see across several of our ingests.
On ingesting FS7 rushes (1920x1080 25p XAVCi) we're starting to encounter the below error message:
Exception: FATAL_ERROR, msg:Assertion failed: NULL != actualEntryref, file:s:\coresw\src\msm\amamapper.cpp, line:1620
I've taken over ingesting from our edit assistants to check if theres an issue somewhere to no avail.
In terms of ingesting I've removed the data track from the AMA (unlink>modify>remove data track>relink) and ingested which seems happiest. I've also tried AMA'ing to rushes, cutting AMA into a sequence then deleting the data track, by transcoding a sequence which seems the most prone to falling over.
Any advice would be great for this one. I've tried the ingest on z440, z4 and a z840 and all come up with the same issue. Our facility run MC 18.12.6 but i've run the patch release up to 12.10 and experienced the same issue.
We haven't updated any machines this year so it isn't a new build causing this but I have rebuilt one of z4's to see if a new workstation helps. We ingest to ISIS/Nexis and store rushes on a seperate nearline storage, but have done so for many years.
I hope this info helps!
Ben
For this project I have many rushes (long clips) spread over 4 local drives.
Now that the main editing stage is finished (using less than 10% of the original material), I would like to consolidate on 2 of these drives.
Using sequence consolidate, I can only select one target drive, and it will then move everything needed from all other drives to that target, including renders which are already one of the drives I wish to keep, right ?
Consolidating clips instead of the sequence will move 90% unnecessary data, which is obviously not the goal.
Is there a way to be more granular and prevent sequence consolidate from moving things that are already on either of the 2 drives I wish to keep ?
I teach an MC class at Northeastern University and one of my students installed MC First so they could work at home, they realized that it's a bit different from the version we use in school so they uninstalled and tried to install the free 30 day trial of Ultimate, however it says that it can't install Ultimate because First was already installed on the system, even though it's currently uninstalled. Is there a way to get them on the trial or can you not do that once you've installed First?
*note* this on a Windows computer
- G
Hello Avid Community,
I am currently having a strange (intermittent) issue with Media Composer 2019.12 – on a Mac OS 10.14.6 (Mojave) install.
I have gone through many different stages of uninstalling all things AVID (Media Composer, Pro Tools, Interplay, and Nexis) and re installing it. I have done a complete erased one of the client machines and started from scratch (a complete OS reinstall - harddrive was erased). It worked on one computer but not reliably on the next.
Basically – We hit play and it takes about 4-6 seconds for playback to start (Both is source and record window). This only happens on an M-Audio, Display audio, Pro Tools Hardware. IF I change the audio output to Internal (in the OS level) – everything works fine - Playback responds fine. Yesterday I was pressing the HW/SW button and the video would play back first – I would see the Metering of audio – but the actual audio feed would still only start 4 seconds after.
Here are the Computer Specs:
macOS Mojave 10.14.6
Mac Pro (Late 2013)
Processor : 3.5 GHz 6-Core Intel Xeon E5
Memory : 32 GB 1866 MHz DDR3
Graphics : AMD FirePro D500 3 GB
Installed AVID Software:
Media Composer 2019.12.0.53599
Pro Tools Ultimate 2019.12
Avid Nexis Client Manager 2019.2.2
Hi there,
I've recently added a focusrite solo interface and can't for the life of me work out how to configure it to work with Media Composer. When I look at the punch in tool I only have options for windows mixer and host 1394 as input options, same in the audio project settings. The only thing I can think of is changing the peripheral in the hardware tab but don't want to do that unless I know its going to work.
Does anyone have any experiance using the focusrite (or any similar) interface to record VO's direct into Avid?
Thanks in advance and apologies if I'm being dumb!
Cheers,
Ian
I have recently updated MC (after uninstalling everything and restarting), then installed new version and every project I open has this error message: Error Initialising bin Indexer Unable to set root path: /
Is this a drive permissions issue? It doesn't affect my other computer at all (running the same version of the software).
Running El Capitan and was on 8.5, but tried installing 2018.9 and 8.9 and both have same message, so it seems as though it's the Mac blocking something rather than MC?
Any suggestions welcome!
Hi,
I need to move several clips from right to left, like a "film roll" that is being played and can't find how to do it. How do I connect the clips together so there's no black hole in between them? Is the the 3D warp that I should use? (
Thanks for helping out!
/Elisabet
I worry that NAB Show may be cancelled this year This is a great opportunity for companies around the globe to show their new products and releases. Hope things get better and Nab will happen so far.
cj
On MC 2019.9 windows 10. I have a setting in my workspaces for my editing. WHen I switch to be able to do color correction, then swtich back, my edit setting doesn't fully revery and I get small floating bins now full screen. Have I not saved my setting correctly? (although it works fine at other times) or do I need to adjust the color correction to match better to what I go back to?
thanks in advnace for the help
Brian
I've just installed the 2019.12 MC on Windows 10 version, and I'm well on my way to getting familiar. There is one thing I can't figure out . How can I get the Audio Mixer pane to open up in the left hand monitor rather than it's default right hand monitor position.
I've tried moving it and saving, or moving and making new worplace settings, but with no luck.
Any/all info helps
Thanks
Philippe
Hi,
I'm wondering if there is a way to have the subclips refresh theselves with the modifications I've made to the masters using Frame Flex?
For context, the DIT made a mistake unsqueezing our anamophic footage, so I am compensating in Frame Flex but we have subclips made from the original dailies. So rather than replacing each clip and reapplying the effects etc... I'm wondering if there is a way to refresh those subclips? Like some little hack...
m
https://www.avid.com/press-room/2019/09/avid-delivers-video-editing-workflows
Uhm this is kind of a big deal.
And supposedly, Pro Apps (including Quicktime X?) will support DNx natively.
getting some 360 footage sometime soon...I know nothing. I'll probably be just cutting bits together but iv'e seen various mentions of mocha 360 (ive used mocha for tracking in the past...but not much). Watched a few youtubes on using the plugin in a 360 project....looking for some thoughts/experiences/warnings....
thanks all
cheers
Gregg
Dont do it peeps...... Dont upgrade until we say you can upgrade. I suggest you all subscribe to the below Knowledge Base article so when we updated it with news, you are notifed. Tools menu on the right side of the article
http://avid.force.com/…/Compatibility/macOS-Catalina-support
JUST SAY NO!!!!!!!!
Marianna
After NewBlue discontinued the free (full) version of New Blue Titler on Avid MC recently, we purchased and upgraded our software to the New Blue Titler Pro 7 Ultimate.
However, since installing it, it has constantly crashed the entire Avid application - mostly while saving.
In spite of contacting support, there seems to be no resolution to this from either Avid or New Blue Titler.
From what we’ve seen, the problems have been there throughout various versions over the years, and plagued various users.
If we uninstall and stop using the software, what alternatives do we have besides Marquee?
Voltaire
macOS High Sierra (ver. 10.13.6)
iMac (Retina 5K, 27-inch, Late 2014)
Processor 4 GHzz Intel Core i7
Memory 32 GB 1600 MHz DDR3
Graphics AMD Radeon R9 M295X 4096 MB
I am new to the subscription based Avid Media Composer Ultimate plan. I had a couple of questions about Avid Link and Avid Background Services and was hoping the gurus could help.
Avid Link and Avid Background Services are automatically installed when I download Avid Media Composer (V. 2018 -12.3 - Windows 10).
1. Are they needed to run Media Composer and does uninstalling them affect MC?
2. Does Avid Link (not signed in but running) use a lot of resources along with Avid Background Services (If you have it turned off in Avid)?
The last release of the year has now launched. Updates to Media Composer 2019.12 are available from Avid Link, MyAvid and the Avid Download Center (login and password required).
Status of Support Plan: The ability to launch this Media Composer 2019.12 software is dependent on the status of a customer’s Upgrade and Support Plan on the date this software version is released. Media Composer 2019.12 has been released today, December 23, 2019.
IMPORTANT: macOS Support: Media Composer v2019.12 does NOT currently support macOS v10.15 (Catalina) – we expect a Q1 release in 2020 to support Catalina.
*** (macOS) IMPORTANT: If you are installing the editing application and you have a previous version of the editor on your system, manually uninstall the editing application before you try and install v2019.12. If you do not manually uninstall, you might receive a “CATWrapperConfig.cpp” error message when opening your project. If you do experience this issue, you can manually remove the file here:
Applications/Avid\ Media\ Composer/SupportingFiles/CodecToolkit_Config/dfm/dnxpacked.lua
What’s Changed in 2019.12: The following has changed in Media Composer v2019.12.
1. Show Bin in Sidebar
2. Inspector Tool Update
3. OpenEXR Export Support
4. Avid Titler+ Updates
5. Media Composer and Distributed Processor Worker on the Same System
6. Media Composer | Enterprise Settings Update
7. Updated ACES Support
What’s Fixed in 2019.12: Below is the list of items fixed….
- Bug Number: MCCET-3285. With connected IO hardware such as AJA or Blackmagic, you could not downscale monitor output on an HD client monitor.
- Bug Number: MCDEV-11345. When tools were tabbed with the Composer Window, the video displayed on top of the tools.
- Bug Number: MCCET-3374. Bin sifting was not retained after closing and opening the bin.
- Bug Number: MCDEV-12014. Sometimes when the Audio Mixer was layered over another tool or bin, and the Timeline or Composer had focus, hovering the mouse over the Audio Mixer made the Audio Mixer the active window.
- Bug Number: MCDEV-12015. Minimizing Media Composer on dual monitors with auto hide sometimes resulted in losing Menus, Workspace Bar, and background host panel.
- Bug Number: MCCET-3210. The Source Record monitor would go black, and menus stopped working if you were working with the Source Browser and the Windows taskbar was set to auto-hide.
- Bug Number: MCDEV-12099. Thumbnails for subclips were recaching every time you opened a bin in Frame View, slowing performance.
- Bug Number: MCDEV-12347. With large projects on shared storage, updating the project after changing a bin name was slow.
- Bug Number: MCCET-3257. (macOS). When waveforms were enabled, clicking in the Timeline might have resulted in a crash and Breakpad error.
- Bug Number: MCCET-3345. (macOS) In some instances, after performing a lasso and trim, the Source monitor would display black.
- Bug Number: MCCET-3171. (macOS v10.12.6). Media Composer was not populating the second screen on a dual monitor setup.
- Bug Number: MCCET-3305. You might have received a “Cannot find bin x in Project x” when performing a Find Bin.
- Bug Number: MCCET-3108. The text to identify locked bins was not displayed in bold.
- Bug Number: MCCET-3299. Using JKL did not work properly when playing a clip with a Timewarp effect.
- Bug Number: MCCET-3355. Imported tga files were only one frame in duration.
- Bug Number: MCCET-3304. Newly created bins that were empty did not save size nor position when working with shared storage.
- Bug Number: MCCET-3206. In some instances, clip frames would rebuild on the entire sequence.
- Bug Number: MCCET-3388. You could not resize an effect +/- 10 steps using the keyboard shortcuts.
- Bug Number: MCCET-3369. French, Swedish, German, and Danish letters in Bin Script View comment field didn’t display properly.
- Bug Number: MCCET-3333. Sequential Targa (.tga) files could not be imported correctly.
- Bug Number: MCCET-3337. When right-clicking on linked clips in a bin, the Relink to Files option might have been grayed out.
- Bug Number: MCCET-3404. (NRCS Tool) When browsing iNews database, the cursor continued showing a spinning wheel even after the result had been returned.
- Bug Number: MCCET-3292. A Transition did not play correctly in full quality if the first clip was an imported still image with XDCAM HD or AVC Long GOP.
- Bug Number: MCCET-3399. The position info did not display even if you selected Settings > Grid > Display > Show Position Info.
- Bug Number: MCCET-3372. Media Composer became unresponsive when you tried to perform a transfer to a Transfer service that was not available.
- Bug Number: MCCET-3342. If Waveforms were enabled, the Timeline responsiveness lagged when dragging or trimming.
- Bug Number: MCCET-2817. Trimming a clip with an AudioSuite Time compression/expansion effect might have affected subsequent renders.
- Bug Number: MCCET-3251. In some instances, Media Composer vaporized when extracting a segment.
- Bug Number: MCCET-3330 (Avid Artist DNxIO, Avid Artist DNxIQ). In some instances, 720p25 projects were incorrectly converted to 1080i50.
- Bug Number: MCCET-3250. (macOS) In some instances, when editing keyframes and then entering Trim mode, the Source Record monitor would appear black.
- Bug Number: MCCET-3230. Timecode Burn-in added pulldown frame info when added to V5 or V6 track.
- Bug Number: MCCET-3306. In some instances, if the Effects Editor was open, Color Correction was not always added correctly, and the wrong clip was modified.
ReadMe: The ReadMe for this release is attached.
How to obtain the Media Composer 2019.12 Update:
1. Customers who have an active support and upgrade plan will be notified of the availability of the 2019.12 via Avid Link and it will be available via Link, MyAvid and the Download Center.
2. New perpetual and subscription Licenses purchased on or after Monday December 23, 2019 will also receive 2019.12.
Have agreat holiday!
Marianna