Saludos. Al comprar mi Pro Tools con licencia perpetua se me activó automaticamente en el iLok Cloud. A mí me gustaría tenerlo en el iLok físico, porque en ocasiones trabajo en lugares donde no hay coenctividad.

¿Existe alguna manera de transferir mi licencia?

I'm trying desparetely to up rez a 14min sequence from DNxHD45 to DNxHD145 (or maybe 175) When I tried to transcode to 220, the copy looked good but wouldn't play properly on my computer; it stuttered and froze and skipped. I tried playing it with VLC Media Player, Quicktime, etc...no luck.

So I thought I would do a re-batch import and try it that way. For some reason, MC could only find 11 of 39 clips, even though all the clips came from drives on this system. When I looked into it further, the clips all had a "?" mark at the beginning of the files location tab. Does this mean I inadverently moved the files or something so that the program can't find them? How do I fix this?

My computer normally plays full HD video back with no problem so I'm confused about why it won't play back a hi-rez clip. I really need to get this program from DNxHD45 to something significantly better, sooner rather than later, so any light you could shed here would be deeply appreciated. Thanks!

I have a couple questions; here goes. I have a sequence made up of clips I imported at DNxHD 45 that I would like to export at a higher resolution, like DNxHD 175. None of the clips are AMA linked, all were imported from various folders on my computer in the normal fashion. What would the best way to up rez these clips be? I don't know whether I should transcode or batch import the clips. Do I need to delete the media first, or can I import without deleting? I will need the low rez media for future edits so I'm guessing I shouldn't delete the media. Also, what about the titles, still photos, other graphics. Will they up rez automatically or do I need to do it manually, and if so, how would I do that? Almost all the clips came from a Panasonic GH3 at 1080p 30p and they look pretty good, so I am hoping for a nice looking export for screening on a projector at a music conference. Would I gain any quality by going to DNxHD 220 or Jpeg 2K or some other format? And finally, I am paying someone to do a sound mix in Pro Tools, any suggestions on how to get the project and media from my computer to his? He lives in another city so it has to be moved to his machine. By the way, you Avid Moderators are doing a great job and I really appreciate all your help. Thanks!

Hello all,

I had assistants and editors complaining about dropped frames recently.  I ran benchmark utility and noticed massive drop in read speeds, from 105MB/s to 35MB/s, to what I would expect.  I then checked several computers and realised that this drop was universal on both the E4 and the Nexis Pros which were running 2018.6.0.8.  I then tested the ISIS 5000 which is running 4.7.11 and the read speeds are what I would come to expect.  I upgraded the E4 and NexPros to 2018.6.1.14 in the hope of fixing the issue.  It did not.  

                        netsh int tcp set global autotuning=disableThe read speeds went up from 35MB/s or 60MB/s up to 105MB/s.

This goes against all current avid literature but both EdPrep and ASDT flip the setting todisabled.  ASDT was run on all computers.  Problem solved... or maybe not.  I then realised that installing and 2018 Nexis Client Manager flips the setting back tonormal as does rebooting the computer.  So every time the computer restarts Nexis Client flips this setting tonormal.  The Nexis Client 7.6.1 (which I upgraded from) did not alter this setting.  What I don't know is did having the setting set to normal or disabled effect the WR numbers in 7.6.1 and in 2018.6.1.14?

Ourcurrent infrastructure has four Nexis Pros and E4 10GB linked into a Dell S4810 switch with a Force10 S50-01-GE-48T-V and a S25-01-GE-24T also 10GB'd into the Dell.  Then 1GB clients are plugged into theForce10s. I have had our Avid support guys try recreate the issue to no avail so the escalated it to Avid proper who are flummoxed, as am I.   
There is already a case created with Avid but I was wondering what others experience were?  And how your infrastructure is in comparison.  The Avid support seen no change in WR numbers when the setting was normal/disabled but that was a 1GB Dell N2024 connected directly to the Nexis.  Does anyone have a 10GB backbone > force 10 > 1GB client? 

Can you post even if your WR numbers do not change or change as expected or in my case change as unexpected depending on the global autotuning status.  Thank you.  

Best,Rory

Hi,

Since I have updated to 8.6.3 I have a problem when I'am opening my projet :

Exception: VolListElement::IsVolWriteable() Bad path terminator

I have the same if I try to import media or if I just quit the application.

Any ideas?

Thanks a lot.

Regards.

Emmanuel

I installed the Baselight for Avid trial yesterday.   I played around with the plug-in for a couple of hours and everything seemed to work fine.

This morning, I booted up my computer and got the dreaded "Unable to Start..." message.  Windows 7 attempted to "fix" the startup problem.  After a long wait it was unable to repair the problem and shut down my system.   I held my breath, pushed the start button again...and windows started.   But when I went into MC, the Baselight plug-in was gone.  It is also gone in my system's program files, so Windows must have done a system restore to the point before I installed the Baselight plug-in.

I want to try out Baselight, but the Unable to Start message makes me nervous.   According to Baselight's specs, it should run on Win 7.   I'm running MC 2018.4.     Before I try to re-installed, I'm wondering if anyone else experienced this problem?

Small bug.  When exporting using the new  Avid media processor / AMA dialogue the exported filename retains the suffix from the last selected export.

e.g. last export was .WAV ,  XDCAM export has filename   xxxx.WAV.MFX

Everytime I try to enter full screen playback both monitors go white and Media Composer goes unresponsive. Have to end task and re-launch. Full screen playback used to work with version 7.0.4 and an earlier version of 8 (I believe 8.4 but I'm not sure).

Has anyone else run into this issue and found a workaround?

Have tried:

-NVidia drivers 340.84 / 353.82 (Windows 10 only, failed to load) / 385.08

-NVidia control panel solution as listed in thread http://community.avid.com/forums/t/183957.aspx

-Enabling Windows Desktop Composition http://avid.force.com/pkb/articles/en_US/How_To/Enable-Desktop-Composition-in-Windows

-Switching the playback monitor between the main (Displayport connection) and the 2nd (DVI connection)

System:

HP Z840

Windows 7 SP1

Quadro K4200

Media Compser 8.10

Dual monitor 1920x1200 (1-DVI, 1-Display port)

Is there a way to quickly sort clips in a bin into the order in which they appear in a sequence?

Media Composer 2018.8 released 8/13/18

Avid is pleased to announce the release of Media Composer 2018.8.   

Location: This release is available from Avid Master Accounts, Application Manager, and the Avid Download Center (login and password required).  Note:  The Download Center goes live at 12:00 pm ET and the remaining components will follow shortly after.

Operating System Updates: The following lists the qualified Operating Systems. Depending upon your hardware the qualified Operating Systems are:

• Windows v7 64-bit SP1(Professional) and Windows v8.1 (Professional and Enterprise), Windows v10 64-bit (Professional, Creators, and Enterprise).

• Macintosh  10.11.6, 10.12.6, 10.13.6 (new Mac OS version approved) 

New MacBooks and iMac’s: The new 2018 MacBook Pros and iMac’s do NOT currently work with MC 2018.7.  Engineering has already made a fix to address this problem in Media Composer 2018.8 and with this version, you can now launch Media Composer on the new  2018 Mac’s.   However, this is a “use at own risk” scenario as Avid has just received our 2018 Mac’s and have started qualification testing but not finished yet.  Once they have been qualified, you will be notified.

Manual approval of loading Kernel Extensions (KEXTs): With the release of Mac OS v10.13.x (High Sierra), Apple requires manual approval of loading Kernel Extensions (KEXTs). (For example Avid Nitris DX, BlackMagic, and AJA IO devices install Kernel Extensions.) At installation time, you should get a dialog saying that the KEXT was not loaded. You must go the “Security & Privacy” system preference and manually approve the KEXT. Keep the Security & Privacy pane open after you install the I/O device drivers so that you will see the notice that the driver has been blocked and press the “allow” button within 30 minutes of installing or the driver will be permanently blocked.

Avid DX Driver Separate Installer:  The Avid DX Driver is not automatically installed when you install the editing application. If you need to install the Avid DX Driver to work with your Avid IO device, you can install it separately.  The installer is located:

• (Mac) /Applications/Utilities/Avid Utilities

• (Windows) Program Files\Avid\Utilities\DXDrivers

Note:  For Windows systems, there is a Win7 driver and a Win10 driver in the Utilities folder. The Win7 driver works for both Windows 7 and Windows 8 systems.

Installers:   Previously, a separate installer was required for Media Composer | First. With this release, you have a single installer for Media Composer and Media Composer | First. Note: The option to run as Media Composer | First is now include in the Avid Media Composer Activation window.

AppMan 2018.8:  There is a new AppMan 2018.8.  This version supports a single installer for Media Composer and Media Composer | First. and resolves the following:

- Bug Number: AMPT-7739. Activating a Sibelius license deactivated the Media Composer dongle.

What’s New:  The following are new features in 2018.8

- Avid Generic Plug-In:  Avid continues working to remove dependencies on QuickTime libraries.
- Launching Media Composer | First:  There is a single installer for Media Composer and Media Composer | First
- Enhanced Correlation Tracker: You can select additional export options from Export to File.
- Exporting to XDCAM Change:  When exporting XDCAM OP1a, you select XDCAM through the Avid Media Processor.
- Exporting AVC-I OP1a: This release expands our support for exporting AVCI-OP1a.
- Avid Artist DNxIP Device: This release supports the Avid Artist | DNxIP device.
- Setting Automatic HDR Conversions for SDR Media:  The editing application allows you to map the white point of SDR (Standard Dynamic Range) media for REC2020 (HLG) and REC2020 (PQ) projects.
- 3D LUTS for HDR to 709 Conversions: We have added 3 LUTs that allows you to preserve high luminance values when converting to Rec.709.

What’s Fixed: The following have been fixed:

- Bug Number: MCCET-2582. You might have received an “Avid editor stopped working” error when performing a send to playback with XDCAM media to Airspeed.
- Bug Number: MCCET-2324. In some instances, the results of Color Correction Auto Contrast on some low contrast clips was not accurate.
- Bug Number: MCCET-2563. Capturing AVC LongG media using the Capture tool created DNxHD 145 media.
- Bug Number: MCCET-2578. You might have received a “Exception: BeginWriting failed” error when exporting as Windows Media.
- Bug Number: MCCET-2565. You might have received an “Assertion failed” error when trying to link or import WAV files.
- Bug Number: MCCET-2572. You might have received a CORE_SEGMENT_NOT_FOUND error when enabling (video) Dupe Detection with “Show Effect Contents” enabled in the Timeline settings.
- Bug Number: MCCET-2561. When performing a File > Open Bin on a read only workspace, the bin did not display with a RED locked icon.
- Bug Number: MCCET-2513. (Mac) You might have received an “Exception: std::exception” error when transcoding spanned AVCHD clips.
- Bug Number: MCCET-2566. In some instances, you could not import .m2t (HDV) files.
- Bug Number: MCCET-2112. You might have received an “Assertion failed” error when linking to AVC Long GOP with the Avid Generic Plug-in.
- Bug Number: MCCET-2567. When in Segment mode, dragging clips in the Timeline might not redraw properly if the Audio Mixer tool was open.
- Bug Number: MCCET-2034. Linking to Panasonic GH5 media using the Avid Generic plug-in might have displayed incorrect duration and timecode.
- Bug Number: MCCET-2441. In some instances, the editing application would show 100% CPU usage and would lock or hang when linking to specific MP4 files.
- Bug Number: MCCET-2544. Markers did not always transfer between two systems when the same Script was opened on both systems.
- Bug Number: MCCET-2543. The image might have appeared flipped when you relinked to an exported Tiff file.
- Bug Number: MCCET-2507. You might have received an incorrect Disk full error message when transcoding multiple spanned AVCHD clips.
- Bug Number: MCCET-2551. (Audio Mixer) In some instances, while stopping play to add volume effect to a clip, the fader slider would jump back. This did not happen if you were in Narrow Mixer mode.
- Bug Number: MCCET-2276. The editing application was slow to respond when changing audio mixer levels.
- Bug Number: MCCET-2500. Markers added in the Timeline did not always appear in the Marker Window.
- Bug Number: MCCET-2494. In some instances, the editing application might have crashed to a BreakPad window if you played back using the spacebar after adding markers from the keyboard.
- Bug Number: MCCET-2532. In some instances, performing a Find did not find all clips and sequences, in all bins in the project.
- Bug Number: MCCET-2489. 1080 50p (50 timebase) media in a 50i project was shifted by one frame.
- Bug Number: MCCET-2028. In some instances, linked XAVC S media using the Avid Generic Plugin did not display Timecode in the Start column.
- Bug Number: MCCET-2341. The List Tool change log was not correct. Comparing the same sequence with itself showed changes.
- Bug Number: MCCET-2524. In some instances, the position indicator (blue bar) was not in sync with sound and picture when using 3rd party I/O devices.

“What’s New” Guide and “ReadMe” Documentation:  As is normal practice, these documents have been uploaded to the Knowledge Base.  For the list of limitations, please refer to these documents.

How customers will obtain the August Media Composer 2018.8 Update:  The latest update to Media Composer and Media Composer | First will be made available on Monday, August 13, 2018 @ 12:00 noon ET.

1.  Customers who have already installed the latest version of Media Composer will be notified of the availability of the upgrade via the Application Manager. The Apps tab also provides a link to download and install the update when desired. 

2.  New customers who purchase Media Composer will receive the update in their Avid Master Account.

3.  Customers on current Update plans can download the Media Composer update either from their MyAvid Master Account or the Avid Download Center (login and password required.) 

4.  Customers NOT on a current Upgrade & Support contract must purchase either a new Media Composer Subscription Crossgrade or a new Perpetual license to receive this update. 

Reminder: This release of Media Composer requires an active Upgrade plan. Please remind customers of this before suggesting they install this update. 

ENJOY!!!!!!!!!!!!!!

In my move up from my trusty Xpress Pro to MC 8.9 I'm obviously experiencing some new stuff. My current confusion is this; I've digitised some footage with V1 and A1-2 and this shows up as such in the bin details. But, when the clips are added to the source monitor the audio is shown as A1 only with 2 speaker icons.My timeline addsa new audio channel also with 2 speaker icons. Default pan toggling does not make a difference. Any ideas? Can't seem to find anything about this in the help.

Just today I got this error and I now can't really do anything in Avid Media Composer without this error coming up. Anyone know the issue?

And if I click continue on this error, I get this message

Would love some help. I'm running MC 18.2 and my specs are below

Thanks in advance

Is there an option in Media Composer to continue playback when you hit the fast-forward and rewind buttons? I'd like for my sequence to keep playing when jumping to the next (or previous) cut instead of having to hit fast-worward, then spacebar again to keep the sequence playing.

Hi, I just installed Pro Tools First

When I open it, it goes through the loading up process, initializing, etc.

As soon as it gets to the "Initializing Audio Engine" part, all the sound on my computer turns off

I rebooted, restarted, tried again, same thing

Any idea how I can fix this issue?

Had it happen a couple of times last week, but a restart of MC fixed it, but today across both suites that 2018.7 is installed, we cannot save a title at all. Have rebooted too.

Open Title tool, create title, goto save, pop up dialog shows, type name, click save, it goes back to title tool and nothing is saved in the bin.
Same for save and save as.

Is there a title tool config to reset anywhere?

I am trying to deactivate ScriptSync from a dongle and get the message 

failed deactivation. 0 deactivation ok. no record of this device was found

when I click "deactivate".

What should I do?

Hello

I'm being a Pro Tools user for quite a while (12.5)

I've downloaded and installed MCF but it won't launch.

AMPI subsystem error... Sys_FileLocMacOS.cpp line 147

Working on a Mac Pro Retina 2015, EL Capitan 10.11.6

I've tried the usual things, like repairing permissions etc...

Any help would be gladly appreciated,

thank you !

I'm a certified Avid Pro Tools user (Operator: Music), and wanted to give MC|F a try, as a possible replacement to Adobe Premier. Unfortunately, the program quits unexpectedly at launch when initializing AMPIPluginDSM.avx.

Removing AMPIPluginDSM.avx from the MC|F package allows the program to run, but with "limited audio capability."

Other than stock plugins, I use several from FabFilter, plus RX6 Advanced (all of which are up to date). Pro Tools 2018.4 runs with no problems (I use it daily).

Can someone point to some specific troubleshooting steps?

Thanks!

While it's relatively slow this month, I'm trying to refresh the OS and software on my 3 Mac Avid network, connected to Nexis Pro storage. All Macs (trash can, iMac and laptop) are on approved Mac hardware list.

After a fresh install of MacOS 10.13.6 and Media Composer 2018.8, Avid Background Services is not running consistently between different user profiles. I create Administrator (with admin rights) and Editor (standard, no admin rights) profiles on all machines, and make my freelancers use the Editor account. I am able to successfully start Avid Background Services on the Administrator account (green icon), it will not start on the Editor acocunt (red icon). I've installed this configuration on 2 of my 3 machines now (laptop and iMac) and this issue presents itself on both machines. 

I've tried creating a new editor profile with admin rights, and this newly created profile still does not start Background Services. Only logging into the original Administrator profile allows for successful background transcodes, renders, etc.

I'm upgrading from v8.5, where Background Services was also unreliable. I was hoping Background Services would be more stable with this release. When it works, I find it very useful for our workflows, especially transcoding media to our Nexis in the background, allowing us to organize our bins and even work on other projects while it transcodes media in the background. I don't see that many posts about it in the forums, does it generally work well for everyone else? Anyone have any tricks up their sleeves to get Background Services turn green when it goes red? Or does no one bother because it doesn't work for them? Asking for a friend... :)

Inky

I do not try using it often, but whenever I do, it is on long duration (1-hour plus) masterclips, from two pro cameras... and it never works for me. (V8.8.4 Win) I’m usually too busy syncing to troubleshoot and I just rely on eye-match or ear-match if Time Codes are faulty. Are there any forum editors here that can report long clip success (or failure) using Waveform grouping? If so,  which camera formats, duration, etc.? Thanks.