Hi,

I am in the setup of a new site and want to use the ldap sync app to import useers from a new domain we set up.

However, it seems i cannot authenticate. It keeps giving the error of a faulty DN of paw.

However, if a test by commandline of third party test app, all seems to work.

Anyone know more about this? Is there a bug?

Thank you...

Hello, I am thinking to make a new pc build for Avid Media Composer.

I was looking to a system based on the i9 9900k platform, a solid z390 mobo with thunderbolt 3, 1tb of nvme storage and 32 gb of ddr4 3200mhz ram. I have a big doubt about the gpu side.

I really can't figure out if I have to take a quadro p4000 for example, I was undecided between the rtx 2080 and the new radeon 7 because of the 16 gb hbm memory, then I read about avid supporting only the pro gpu like quadro or amd radeon pro.

Does Media Composer support some kind of gpu acceleration for the consumer cards?If it doesn't and I get a quadro the difference in performace will be worth the extra money?

Thanks a lot

David

Could somebody with Mac and PC workstations do me a favor and test this? Make a timeline on a PC. Drop an Avid Titler on some filler. Type something out. Then open that same sequence on a Mac workstation and let me know if it works. 

I have a timeline with a bunch of Avid titler filters on it then went to a Mac workstation to do an output and none of them were working. 

Thanks in advance for your help. 

MC 2018.12.3 on both workstations.  

This is for people who run MC on custom built computers, I will NEVER buy a qualified system, please do not reccomend or warn me of doing this.

I've been building my own computers and running Media Composer for about a decade now.  I get flawless performance, but lately ive been considering upgrading to a prosumer cpu such as a 6900k, 6950x, possibly Ryzen 1800x, or wait for future Skylake-X.

My current setup is intel 4790k @4.4ghz  32gb ram, asus z97 gryphon motherboard, nvidia 980ti. And running Media Composer 8.8.1, windows 10 home.

When I do a mixdown it looks like im getting 68% avg across 8 threads.  What average are you all getting?  Id be interested to know about kabylake 7700k, skylake 6700k, 6900k, 6950x, AMD Ryzen,  and other current cpus.

Im wondering if I built a computer with a 6950x @4ghz would Media Composer utilize all 10 cores/20 threads?  If so, that would be a substantial performance upgrade over these mainstream gaming cpu's.

Also im going to start paying close attention to how Media Composer uses all my cores while performing different tasks. Mixing down, rendering, exporting, importing, transcoding, etc.

Due to the discontinuation of Sorenson Squeeze by Sorenson, Avid can no longer offer Sorenson Squeeze either for purchase or as part of a Media Composer | Subscription or Production Pack bundle.

Customers who have purchased Sorenson Squeeze can continue to use it while the license is valid.

Customers who have purchased the Production Pack can continue to use Sorenson Squeeze while the license is still valid. They will not receive any software updates to Squeeze, however, and cannot receive support from Avid on issues related to Squeeze.

Customers who have a Media Composer subscription that includes Sorenson Squeeze can continue to use it until January 31st, or the next time they renew their subscription in 2019, whichever comes first, at which time it will be disabled (will cease to run) and will be removed from their Avid Master Accounts.

For further questions, please refer to this FAQ

FAQ:

What’s happening to Sorenson Squeeze?

Due to the discontinuation of Sorenson Squeeze by Sorenson, Avid can no longer offer Sorenson Squeeze either for purchase or as part of a Media Composer | Subscription or Production Pack bundle.

Customers who have purchased Sorenson Squeeze can continue to use it while the license is valid.

Customers who have purchased the Production Pack can continue to use Sorenson Squeeze while the license is still valid. They will not receive any software updates to Squeeze, however, and no support from Avid will be available on issues relating to Sorenson Squeeze.

Customers who have a Media Composer subscription that includes Sorenson Squeeze can continue to use it until January 31, 2019, or the next time they renew their subscription in 2019, whichever comes first, at which time it will be disabled (will cease to run) and will be removed from their Avid Master Accounts.

Why is this happening?

Earlier this year, Sorenson Media announced that Squeeze was no longer part of their portfolio and ceased all licensing, development and support of that product line. Avid is therefore no longer able to sell or support the product.

Can I still get help with issues?

Customers who require support for Squeeze should refer to the Sorenson Media website. Avid cannot provide any support for issues related to Squeeze.

When will I stop being able to use Squeeze as part of my Media Composer subscription?

Sorenson Squeeze installers will be removed from accounts on January 31st. Starting January 1st, the next time a subscription license is reactivated – either as part of an annual renewal, a monthly payment, or a monthly “call home,” – Squeeze will stop running as part of a subscription license.

What about an alternative software solution?

Avid will not be replacing Squeeze with an alternative software option.

Questions, let me know

Marianna

Is it possible to add a color correction made on the timeline back to the source clip, thereby negating the need to add it to every instance of that clip on the timeline?

Thanks

Hi,

I have this strange problem on our Media Composer logged into Interplay environment:

Whenever an export to file is initiated, it suddenly stops without any error popup or anything. The progress bar just disappears.

I can also see the export file growing in size on the target folder, but the minute that the export progress bar disappears, the export file will also disappear.

I tried restarting the Interplay server but to no avail.

Any suggestions and comments are highly appreciated. Thanks!

Hi All,

We are trying to install a bus service to cloudux 2019.2. The service was cerated in App Creator Tool in VS Code with cloudux-starter-kit-service@2.0.2. After uploading the feature pack to the server we execute commands

avidctl feature-pack import service.zip

and

avidctl feature install --feature avid-releases/service --name service --version=1

The second command fails with

Error: render error in "service/templates/deployment.yaml": template: service/templates/deployment.yaml:19:28: executing "service/templates/deployment.yaml" at <include (print $.Tem...>: error calling include: template: service/templates/config.yaml:13:13: executing "service/templates/config.yaml" at <.Values. service .env>: can't evaluate field env in type interface {}

exit status 1

Do you know where can be the problem? Installing other a UI App with the same commands is working, the problem is only with bus services.

Thanks and Best Regards

BTW. The App Creator Tool stopped working with the newest version of VS Code on macOS and windows also.

Working with consolidated sequences, and one of the files are offline, how do you go about reconnecting the offline media once you find the original source? I have a consolidated sequence, for which the "Avid MediaFiles" have been lost, so all clips are offline. I have the original media, but the file names in the consolidated sequence BIN now have “.new01 , .new02", and so on at the end of the clip names plus the timing is different since its just small segments of the original files. This gives an error when I try to batch import since they no longer match.

How can I batch import my original footage, to replace missing Avid MediaFiles from a consolidated sequence?

Thanks for the help.

Good news! Media Composer 2018.12.5 is now available. This is a patch release, and is only available through the Download Center. You will not see it in your My Avid account or on Avid Link.

The Windows version of Media Composer v2018.12.5 is a patch release. You must have v2018.12.3 already installed. Then use the 2018.12.5 patch to update to this release.

Fixed in Media Composer v2018.12.5

The following has been fixed:

➤ Bug Number: MCCET-2999. You might have received an Exception error when deleting an asset from a bin.

Fixed in Media Composer v2018.12.4

The following have been fixed:

➤ Bug Number: MCDEV-10783. You might have received errors when trying to log into the MediaCentral Cloud UX server.

➤ Bug Number: MCCET-2822. In some instances, the .mxf extension was not appended using Send to Export, therefore “Auto Launch” could not open mxf files.

➤ Bug Number: MCCET-2927. Intermittently, saving bins resulted in Exception errors.

➤ Bug Number: MCCET-2902. In some instances, a video mixdown included the effects from an upper nested layer.

➤ Bug Number: MCCET-2897. After importing, certain WAV files may have had an incorrect start time.

Fixed in Media Composer v2018.12.4

2

➤ Bug Number: MCCET-2748. If a sequence with media from a P2 card was loaded into the Source or Record monitor, relinking to add an extra clip would take too long.

➤ Bug Number: MCCET-2867. In some instances, rendering some effects on linked H264 media resulted in mixed up frames.

➤ Bug Number: MCCET-2862. (Windows 10) The Audio Tool was not updating when scrubbing with CAPS lock enabled.

➤ Bug Number: MCCET-2937. In some instances, if you captured with a single track that was not A1, the capture would abort immediately.

➤ Bug Number: MCDEV-10869. Clicking the yellow bin lock icon maximized bins that were minimized.

➤ Bug Number: MCCET-2967. (Avid Artist DNxIO and DNxIQ) Audio meter levels were not displayed in the Audio tool when recording.

➤ Bug Number: MCCET-2952. The Audio Punch-In Tool did not remember the last bin selected.

➤ Bug Number: MCCET-2914. In some instances, when exporting JPG, if you changed the name of the export, the file may have been unusable.

➤ Bug Number: MCCET-2942. You could not perform an insert edit export of DNxHR HQX media.

➤ Bug Number: MCCET-2946. (Interplay) In some instances, Media Composer would crash during check-in of sequence.

➤ Bug Number: MCCET-2910. Importing a non-shared user profile created a duplicate and prevented the application from closing.

➤ Bug Number: MCCET-2913. The Property Merge window would inadvertently appear when checking in a clip for first time into Interplay.

➤ Bug Number: MCCET-2901. Media Composer would hang when playing back an Avid Titler+ title in the effect editor.

➤ Bug Number: MCCET-2729. You might not have received the correct find results when searching group clips in PhraseFind.

➤ Bug Number: MCCET-2931. After upgrading from Media Composer v2018.12.1 to v2018.12.2 or v2018.12.3, batch re-import of Matte Key clips was not working.

Fixed in Media Composer v2018.12.4

3

➤ Bug Number: MCCET-2878. The UHD video output is converted to HD when consolidating HD media in a UHD project.

➤ Bug Number: MCCET-2859. Switching camera angles in Multicam stopped playback if the group contained mixed frame rates.

➤ Bug Number: MCCET-2857. If you were working on a system using Chinese locale, you might have experienced consolidate and transcode audio issues.

➤ Bug Number: MCCET-2957. Insert Edit Export failed if only video tracks were selected.

➤ Bug Number: MCCET-2966. You might have been unable to import an EDL.

➤ Bug Number: MCCET-2915. The metadata might have been incorrect after importing an ALE.

➤ Bug Number: MCCET-2841. Saved presets did not always retain the last keyframe.

➤ Bug Number: MCCET-2805. The Raster Dimension column in a bin was incorrect for thin raster media.

➤ Bug Number: MCCET-2925. In some cases, after performing a render operation, the green dot remained in the Timeline on PNG clips including a Matte Key effect.

➤ Bug Number: MCCET-2930. You might have seen performance issues when editing a long AVC Long GOP 25 clip.

➤ Bug Number: MCCET-2973. Changes to Audio Reference Level settings changes were not properly reflected when you switched between Normal and Narrow Mixer View.

➤ Bug Number: MCCET-2960. (Mac v10.14.x) When linking to media on a shared network drive, the UNC path in the Drive column might have had the network user name in the path.

➤ Bug Number: MCCET-2732. When consolidating AVC Long GOP subclips created new master clips that were too long. A new check box has been added to the Consolidate/Transcode dialog

boxes. Select the “Re-encode AVC Long GOP media to ensure shortest subclip durations” option when you consolidating AVC Long GOP subclips.

➤ Bug Number: MCCET-2923. (Mac) You might have received “not authorized” errors when trying to use PhraseFind or ScriptSync.

➤ Bug Number: MCCET-2947. You might have received errors when trying to set target the Dynamic Relink settings in an SD 25i PAL project.

Fixed in Media Composer v2018.12.4

4

➤ Bug Number: MCCET-2936. If Dynamic Relink was enabled, imported DaVinci Resolve AAF media was offline.

Hello,

I have a very strange error that appeared after installing MC 2018.12.2.

The error is that you can not transcode video clips that have been AMA linked on a different computer than the one where you want to transcode. On the other PC, this error is shown as on bottom.

Interestingly, the case concerns only clips, which in our case come from cameras like GoPro or DJI OSMO.

All clips that come from Sony PMW-300 cameras and are recorded as XDCAM 422 50Mb do not show the problem described above.

Additionally:

- The duration of the clip is double on clips linked with GoPro and DJI OSMO

- When an error occurs, it is NOT POSSIBLE to transcode on the first PC (AMA Linked on the one where the clips have been), AMA LINK needs to be re-enabled

- When I want to view the clip on the second PC, which is there, the MEDIA OFFLINE in the PRV window has an image but no sound

Procedure:

- clips from the card are copied to the network share

- network share is visible on PC through Symbolic Links (aka Symlinks)

- after copying the clips are AMA Link in Composer

- clips are described and sorted

- Then on the second PC the same project and the same bins are opened (BINs are previously closed on the first PC) and

- the transcoded option of selected clips, which are AMA Linked on the Avid ISIS 5500 workspace, is run

and then an error occurs.

Specification:

1. Both PCs are HP Z440 Win 7, Intel (R) Processor Xeon (R) CPU E5-1660 v3, 32 GB RAM, NVIDIA Quadro K2200

2. Both PCs are Media Composer 2018.12.2

3. Avid ISIS 5500 Workspace

4. Network - Intel (R) PRO / 1000 PT Dual Port Server Adapter

5. The format of the project is HD 1080i50

6. The codec of the project is XDCAM 422 OPAtom

7. Source codec AVC Long-GOP High (HD1080p)

8. Automated AMA Plugin - Avid Generic

Information from the console:

18.12.2.51455

* Can not consolidate master clip with offline media.

Error on DirectQtDrawing: QPaintEvent was ignored for BARTEK TEST, rects: 2 (org: 0, 1 size: 1435, 20) (org: 1, 26 size: 1415, 547), due to suspension update events for this window.

Error on DirectQtDrawing: QPaintEvent was ignored for * EXPORT CONTROL, rects: 2 (org: 0, 1 size: 118, 20) (org: 1, 26 size: 117, 283), due to suspension update events for this window.

DIDWriter :: DoSDKHWEncodeForCapture - SDK HW encode disabled

Exception:

@ Wed May 15 15:01:52 2019

I am asking for help, because in previous versions of Media Composer, for example 2018.11, this problem did not occur.

I just installed Media Composer 2018.5.  It seems to be working fine, except for the fact that when I exit/quit the application, it crashes.  I don't seem to lose any work, but I did not have this issue with the previous version.  I did an uninstall before I installed this version.  I am also working in a brand new project, so I am not sure why I am experiencing this issue.  I am also using a new user profile.  MacOS High Sierra Version 10.13.4  

Hi All,

I'm seeing massive performance hits while running MC 2018.12.5 on all my Macs running 10.13.6. Models vary from 2010 Mac Pros with 16-20GB Ram, ATI 5770 Radeons, to 2013 Trashcans with 32GB ram etc. Even my iMac Pros are noticing it.

I'm getting a lot of pinwheeling just opening bins or opening AMA footage. Under 2018.12.3 I had no issues.

I'm also noticing that some of the AMAs from 2018.12.3 seem to be broken after the upgrade with network usernames included in the source path for AMA linked files from a NAS.

Hi,

Working in a Nexis environment, we have new Imac with Mojave so we have to install Media Composer 2018.12.3 but the effects that have been applied to a sequence in a 2018.8 (High Sierra) are not recognized if you open the same sequence in 12.3. all appear like Titles.

Any ideas?

Thank you.

Dalidá Burgos

Hi team,

Updated one of our test machines today to the new 2018.12.2 release hoping that scriptsync would be fixed, but we're still havning issues.

The client is an iMac Pro running Mac OS Mojave 10.14.3 and Avid Media Composer Ultimate 2018.12.2.

When attempting to scriptsync, the client get's the error:

Error syncing "SCRIPT NAME"

This machine has not been authorized.

Continue?

Yes/No

Link to the error message screengrab: https://i.imgur.com/6hhA8lA.png

If the user clicks either Yes or No, nothing happens. 

Thanks

Derek

Getting a PGLUE IMPOLITE PORT NUMBER error when exporting. Haven't had this issue before with previous version of Avid. Running current version. Exporting 4k project. Footage was AMA. Have transcoded and run all sorts of ways to export including running mono channel of audio (based on issue in version 6). Any work arounds? Waiting for support call with Avid and needing this exported hours ago for client deadline.

Thanks!

Michael

Hi

Anybody know if this still works in MC 2018.12.x

I used to make use of this function all the time to get picture on HDMI mons that couldnt dispaly 1080p 25. You used to be able to toggle to psf and an attahced AJA Io woudl display picture as 1080i 50, taking its signal from MC.

Seems like now it just doesnt work at all.

Thoughts

Did behavior when playing a clip while in the motion effect editor change? I thought it used to stop playback when it reached the end of the clip. Currently in 2018.12.3 it just keeps playing in the timeline which is super annoying. I don't remember being annoyed by this behavior before so feel like it must have changed in the last few months.

Play loop seems to work so i'll just use that for now (or forever if this is the intended behavior).

So I'm finally taking the plunge and going to monthly subscrition because I will be editing some 4K projects. Can I keep my version 7.04 dongle license and just deactivate it and install the new subscription version? So I could atsome point go back to it.

Another option I might try would be to move the dongle V7.04 to another computer and put the new license on the other?

Thanks Greg

We just upgraded all of our systems to W10 along with MC 2018.11 and we're randomly encountering weird UI issues. Wondering if others have seen this and found a solution.

Our systems are dual monitor, and without warning various regions of the UI will become unclickable with the mouse. The keyboard will still work and other regions of the UI will still work.

For example: the project window will be all the way on the left of the left monitor. Can double click to open a bin. The bin will open in the center region of the left monitor and nothing in the bin and the bin itself cannot be clicked on. Avid isn't locked up because I can still click on menus and I can still open other bins from the project window. If the bin opens elsewhere, say on the right monitor then it is clickable. But, when a bin has opened in the region of the interface that is unclickable we have no way of interacting with that bin. If the bin is half way in the unclickable region I can usually grab the bin and move it and then the whole bin is clickable. Close Avid and re-open fixes it for a while.

Have tried clean uninstall and re-install of the video drivers, have deleted the MCState file, but nothing seems to be a permanent fix. Anyone encounter this?