Quantcast
Channel: Avid Media Composer - PC
Viewing all 7351 articles
Browse latest View live

HP Z400 vs Z820

$
0
0

I have been running Symphony 6.5 on a Z400 for about 10 years now and the machine and software have treated me well. But with my current project – perhaps my last doc (I’m 75) – at two hours and with lots of layered effects, the Z400 seemed rather slow, So, I reluctantly upgraded. After seeing an old Larry Rubin post re the Z820 being compatible with Symphony 6.5, I bought a Z820 from NewEgg for about $1200.

HP Z820 Workstation – 2x E5-2640 Six Core 2.5Ghz – memory 16GB DDR3 (running speed DDR3 1333)– 1TB SSD – NVIDIA K4000.

After installing WIN 7 PRO and setting Symphony up, the first problem was a Symphony message that the K4000 was NOT accepted. After trying unsuccessfully with various drivers, I realized that I had long ago downloaded a 6.5.5 upgrade of Symphony but never actually installed it. I installed it and in the C/AVID/UTILITES folder I found Nvidia’s 310.90 driver that was recommended in the MAY 1, 2013 Z820 configuration PDF (Joe Conforti). That did the trick; Symphony was now good to go. Or so I thought.

Then I did a test to compare the Z820 to the Z400. On the Z400, I highlighted a 20 second clip on my timeline where I had a Boris Unsharp Mask on the fourth video track and two other Boris effects beneath it, plus Color Correction on the base clip. I rendered the top effect. I took 9 minutes. I did the exact same thing on the Z820 and it took 18 minutes. This was very depressing. The Z820 has 16GB RAM, is running the software from a 1TB SSD C-Drive and accessing the media from two 4TB INTERNAL 7200 NAS Toshiba 7200 rpm drives where the MEDIA and EFFECTS are on separate drives. The Z400 has less RAM (12GB), an old 7200 HHD C-drive, and with media on two EXTERIOR 1TB 2.5 drives that are, yes, connected with the newer flat USB connectors on the drive end, but using old USB 2. The Z400 does not have USB 3.

So I again went through all the adjustments recommended in Joe Conforti’s PDF, along with other adjustments from the Symphony 6.5.5 PDF – including those regarding the K4000 graphics card – and ran the test again. Same results: the old Z400 was twice as fast. Concerning the Z820 BIOS, I was not able to find (at the HP site) the two Conforti recommended (1.14 and 2.08). But since his PDF was from 2013, I went with the BIOS already installed (J63 v03.94) and did F10 to make all the recommended adjustments.

I also opened the machine to see how many and where the MEM sticks are located. There are 4 sticks of 4GB each in the 1 and 8 slots of each of the six-core processors. The Conforti PDF recommends a Standard AVID memory configuration of 16GB (8 x 2GB) DDR3 1600 ECC memory (eight 2GB DIMMs). His optional recommendation, however, is for 16GB with 4 x 4GB DDR3 1600 ECC memory. My Z820 has this 4x4 configuration– and they are correctly installed at CPU0-DIMM1, CPU0-DIMM8 and CPU1-DIMM1, CPU1-DIMM8 – but the sticks are Dual Channel 128bit DDR3-SDRAM, not 1600. Is this the problem? But why such a drastic 2:1 difference on the test I ran?

I have another two weeks where I am able to return the Z820 to NewEgg – and I would like to keep it, as it is well made and very quiet – but at half the render speed of ny 10-year old Z400, I cannot keep it. And I need to continue on this project on mine. Does anyone have any ideas? Thanks.


ScriptSync Question

$
0
0

Any Script Sync Pros out there? We have separate audio and video files from filming. We need to sync those for editing and are doing so using a sequence file. SS won't allow sequence to connect with the script files because they're probably anticipating using clips. Any best practices for doing this? 

Thanks!

MEDIA COMPOSER 2020.6 AVAILABLE NOW - 23 JUNE 2020

$
0
0

Great news, Today, June 23, 2020 @ 12:00 noon ET, Avid has launched a June update to Media Composer v2020.6.

 

Location at Launch:  The Media Composer v2020.6 (Mac and PC) is available in MyAvid Master accounts, Avid Link, and on the Download Center.  

 

ReadMe: The ReadMe has been uploaded to the Media Composer 2020 Documentation page .

 

How to Obtain Media Composer 2020.6 Updates: 

 

  • The latest update to Media Composer 2020.6 is available as of  June 23.
  • Customers who have already installed the latest version of Media Composer 2020.5 will be notified of the availability of the upgrade via Avid Link. They may download and install the update from Avid Link or from a browser-based MyAvid Master Account when desired.
  • New customers who purchase Media Composer from today onward will receive the 2020.6 update in their Avid Master Account.

 

Reminder: This release of Media Composer 2020.6 requires an active Update & Support plan. Please ensure your customers’ plans and licenses are both up-to-date before installing this update.

 

What’s fixed in 2020.6:  The following have been fixed in this release.

  • Bug Number: MCCET-3290. You might have received “FatalAbort VDM Scheduling failed” and “MultiFrameCombiner” errors when trimming.
  • Bug Number: MCCET-3474. Marking an IN and OUT and then dragging an effect to the Timeline sometimes caused multiple additional add edits.
  • Bug Number: MCCET-3237.  (Windows) FrameFlex scaling might have appeared blurry on some images.
  • Bug Number: MCCET-3589.  (Media Composer Video Satellite) If the Timeline crossed midnight (00:00:00;00) playback would not start if the playhead was beyond halfway between 00:00:00;00 and the end of the sequence.
  • Bug Number: MCCET-3479. When working with Edit While Capture subclips, the cursor and position indicator did not follow smoothly when scrubbing with the mouse.
  • Bug Number: MCCET-3331. In some instances, linked MOV files failed when performing a background transcode.
  • Bug Number: MCCET-3596. Adding Key Code to a Subclip did not work properly.
  • Bug Number: MCCET-3635. AAF exports were much slower than in previous releases.
  • Bug Number: MCCET-3597. You might have lost renders when working between two systems and using the Sapphire Plugin.
  • Bug Number: MCCET-3577. In some instances, changes in the Timeline and audio were not correct after performing a batch re-import or relink of the audio.
  • Bug Number: MCCET-3542. You might have received a “No such track” error after performing a mixdown for a sequence with a Timecode Burn-in effect.
  • Bug Number: MCCET-3614. (macOS) (List Tool) When choosing to save an EDL “To several files” the save destination was not remembered.
  • Bug Number: MCCET-3443 . When working with Paint Effect, video on a lower track appears when you first drag the paint object.
  • Bug Number: MCCET-3481. If you zoomed in on a Paint Effect object in a sequence and then scrubbed the Timeline and moved the object, the image displayed was incorrect.
  • Bug Number: MCCET-3472. You might have received a “Fails Playout QC Process due to repeating idr_pic_ids” error when exporting 4K / UHD XAVC Class 300 media
  • Bug Number: MCDEV-12926. (macOS) If you have upgraded to macOS 10.15.4, there is a known issue with local attached RAID storage. The system will hang when running Media Composer or copying large files. This does not happen with earlier versions of the OS. You can read details about this issue in this blog.
  • Bug Number: MCDEV-12988. (macOS) The AMA Drastic plug-in is not supported with Media Composer v2020.4
  • Bug Number: MCDEV-12964. For a faster performance of export audio/video sequences to .mov in 2020.4, please render the sequence prior to export, or disable the GPU fx (in the Render Settings - Current menu)
  • Bug Number: MCDEV-12735. Maestro graphics do not appear correctly in the Timeline if your system uses the Radeon video card.
  • Bug Number: DEFI-1808. (Media Composer | Distributed Processing) Two clips or sequences will always be created when performing a consolidate or transcode with Media Composer | Distributed Processing.
  • Bug Number: MCDEV-11481. Promoting a title from the Title Tool application to Avid Titler+ cannot be performed if it includes a motion adapter.

In anyone using Titler+ successfully? Or is it me?

$
0
0

I've experienced nothing but frustration trying to learn and use Titler+.   I've shared my frustration about the lack of Titler+ documentation in another post:

http://community.avid.com/forums/p/197433/887822.aspx#887822

Last week, I learned how to use BCC's Primatte studio in a few hours.  I figured if I can learn to use a tool as sophisticated as Primatte studio then I'm not a total idiot and I should be able to make a basic title in Titler+.  After all, I've been using the old Title Tool and Marquee for years.  So this weekend, I decided to give Titler+ one more try...without the benefit of any documentation.   After many frustratiing hours, I have come to the conclusion that Titler+ is essentially unusable.   If it does indeed work--which I am seriously beginning to doubt--it certainly cannot be made to work without any documentation.

I'm curious if anyone on these forums is using Titler+ successfully on a regular basis or if I'm lacking some basic function in my brain that just doesn't get it where Titler+ is concerned?

Changing Source & Record window colour bar

$
0
0

Hello,

The option to change the colour of the Source & Record windows seems to be missing.

Usually I would do this via the Interface settings but the option is no longer there (it is usually directly under the highlight colour section).

I am using version 8.5.5

Can anyone please help?

 

Kind Regards

Adam

1.66 Mask different from FX and Format Project

$
0
0

This is so frustrating. I have a 16:9 project with a Raster Dimension of 1920x1080.

If I add on a video track the effect Film--> 1.66 Mask I get a mask that cuts from top and bottom.

But if instead I use from the Format tab--> Mask Margins--> the Mask margins preset --> 1.66:1 , I will get a left and right cut.

Check screenshots.

Why is this different?

 

AMA_MAPPER_ERROR_CANT_GET_MAPPER

$
0
0

Hello. I came to archive a completed project which was largely kept a linked files. However when I open the project noe some of the linked clips (DNxHD wrapped in quicktime MOV wrapper exported from After Effects) wont display in MC; instead I see the error message "AMA_MAPPER_ERROR_CANT_GET_MAPPER" in the source and record monitors.

I dont understand why most of the clips are re-linked and play fine and these few display the error above, yet they are all the same codec.

I have tried re-linking, but they are not actually offline. (and I can play outside MC in VLC player)

I must be some king of AMA plug-in issue, but they are Avid codec files.

I have rolled MC back to 2020.4 just incase it was to do with the change in QT plug-in, but still no go.

has anyone had the same experience or can anyone suggest a solution to the issue.

Thanks

Having an issue motion tracking the titler +

$
0
0

Hi all,

 

When i try to motion track a title created with the Titler + effect and turn on the tracking option in the effect editor, the tracker automatically de-selects itsself...

 

Hopefully this video clarifies what i mean: https://youtu.be/kHBHKt6LCOY

 

Does anyone have any ideas? 


Do NOT install Windows 10 Build 2004

$
0
0

Windows 10 build 2004 is causing a lot of issues for a lot of people, not just for MC users. At this point I would advise NOT installing build 2004. If you have already installed it, and have a restore point, downgrade using the restore point. If you've installed it within the  past 10 days, you can roll back the installation to the previous version. If it's been over 10 days, or you did a clean install of build 2004, then you're out of luck. The only option in this case is to do a clean install of Windows 10 build 1909 and then reinstall all of your applications.

If it's been less than 10 days, you can downgrade Windows 10 to a previous version. See the following Microsoft article:

https://support.microsoft.com/en-us/help/12415/windows-10-recovery-options

and choose Remove an installed Windows update.

 

Windows 10 build 2004, possible to stop for more than 35 days?

$
0
0

-and, is anyone running build 2004, and have problems?

Boxx Threadripper qualified system

$
0
0

Has anyone been able to test out the Boxx Threadripper qualified system?

I'd love to hear how it is working and also how many threads are used when transcoding.

Is there a limit to how many threads Media composer uses while transcoding?

I have a lot of UHD media (Canon C300) that I have to chew through on a daily basis.

 

MC Resolve Roundtrip Issues

$
0
0

We're following the workflow outlined by Kevin P McAuliffe for roundtripping footage. It's a little dated with Resolve 12, but the workflow has worked perfect for us until now. We're hitting a snag importing the finished AAF file into MC. The error message is:

"Exception: CM_LABEL_NOT_UNIQUE, tt:2, lnum:2".

Then a similar error: "Exception: CM_OFFSET_OUT_OF_RANGE, offset:9206. range:165

We're working with MC 2020.6 and Resolve 16.2.5

Structured Exception Error Frequent

$
0
0

I recently updated to 2020.6 and I'm getting the following error:

Exception: Structured Exception, ExceptionCode:3221225477, ExceptionString:ACCESS_VIOLATION ...

This wasn't an issue before the update from a 2019 version. It is only happening when working with effects, mainly when manipulating Matte Key positions of PIP positioning. Maybe it would happen more with others, but this is when it's mainly popping up and it's frequent. Happening in UHD 29.97 & 1080 29.97 projects.

Any ideas on solutions? I already tried restarting, reinstalling Avid, disabling devices like my BM monitor mini, disabling OpenGL acceleration inside Avid, wiping the MCState files. I'm out of idea. This is crashing at least twice an hour when working with effects, but rebooting clears it up for a little bit and the error doesn't linger on a particular spot on the timeline. After I reboot and revisit the same effect on the same clip it works fine, but then 30 mins later, I'll apply a PIP and change the position or scale and it crashes again.

Specs:
Dell Worstation (approved)
Media Composer 2020.6
Windows 10 Pro (10.0.18362)
Dual - 8core Xeons
64GB Ram
AMD FirePro Card on recommended driver (A little old but I disabled OpenGL previews to see if that was related and the error still occurs)
Blackmagic 4k mini monitor (disabled in device manager to test and the probelm still occurs w/out this being enabled)
Using only local, internal SATA storage

AAF from Avid can't be imported into ProTools

$
0
0

I would like some help to work out this problem please. I've been working on a documentary and have exported a sound-only  AAF at picture lock which will not import into Pro Tools? The error message says it cannot be imported via Import Session Data?  What does this mean? There were a few clips that were originally in a different frame rate - could it be that this is the issue? What's the best way to fix this? Thank you

Have Media Composer licensed the ProRes encoder from Apple?

$
0
0

How official is the ProRes export on a windows PC?  I remember reading a long time ago that a lot of softwares reverese  engineer the ProRes codec to mimic Apples code.  

In the past content being delivered has failed using these reverse-engineered codecs so exporting on OSX was the option used for an Apple ProRes delivery. 

I noticed MediaInfo on the file exported from a PC using the ProRes codec will not say "Writing Library: Apple QuickTime" in the way it will after being exported on OSX but that may be not related to this topic. 

 

 


cannot access the ama media stream plugin to play this clip

$
0
0

Hi everyone...

 

Im working on a complex project with a lot of photos and I have found this strange bug(?):

 

When I link a picture using Source browser in MC 2020.6 and then I open the project on different computer with MC 2019.12 the linked pictures are offline (even if the files are on the same address e.g. D:\WORK\XX\), cannot be relinked to different files (the option is gray) and moreover THE WHOLE sequence is unplayable error "cannot access the ama media stream plugin to play this clip" appears when you hit play. 

 

The only solution I have is to locate the files on timeline and mute them (and replace them later by files linked in 2019.12). I hope this workaround might help some of you guys. If anyone has some insight it would be nice.

 

Thanks, take care.

MC 2019.6 New Interface Design - please roll back!

$
0
0

Hello Avid,
to keep things short:

I want my old, stable and proven user interface back! What you done in 2019.6 is a real garbage, especially to connect project view and bin view together.

With no reason you destroy the "muscle-memory" of every professional editor with longterm experience.

So bring up a switch, where the editor can choose which interface design he like to prefer.

 

The way of success to beat competitors products is not to copy and paste their bad peculiarities.

 

Regards

Bob.

 

 

 

 

PNG import to Avid Pan and Zoom looks terrible

$
0
0

I've created titles in Photoshop w/o backgound, saved as PNG, but can't get them to import properly with the Pan & Zoom effect. They just look garbled and illegible. I'm not sure, but I think there not importing with Alpha channel. Is it possible to use Pan & Zoom with PNGs?

Color control panels for Avid

$
0
0

Hi all, I am really after a simple color control panel I can use for quick colour work in Avid instead of steping out to Davinci. I have fould the tangent Ripple but it looks like Avid is not supporting it. What else is there, surly Avid would be able to set up compatibility with Tangent Ripple so we can use Avid as a one stop shop? Anyone know what is happening here and if Avid is looking into it? 

Sharpen subject/blur background

$
0
0

We have a shot we're trying to touch up. We have BCC tools and Mocha. The subject is slightly out of focus. We'll be using BCC Magic Sharp/Mocha to fix the soft focus but wanted to REALLY soften the back, give it a little more depth of field so the the soft/sharpened subject doesn't feel so out of focus.

Any thoughts of combining/masking some elements to create this. 

Thanks!

 

Viewing all 7351 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>