Dear Avid,
With the release of Mediacentral production 2018.9 and Media composer 2018.10 I'd like to request if the
Avid Editor Compatibility with Interplay Releases (time to update the name to Mediacentral?) document
http://resources.avid.com/SupportFiles/Attachments/Interplay_Editor_Compatibility.pdf
can be updated to include the latest versions.
(The current main reason for this is to confirm MC 2018.10 requires MCP 2018.6 or 2018.9 client components.)
If the mediamanager of a Nexis system locks a Bin because it have archived material then the other Nexis clients who want to use clips from that Bin will get the annoying 'Do you want to save as.." every few minutes.
How do I stop this ? I simply do not want them to change or write to that locked Bin.
Hi there. I can't seem to activate my Avid. It keeps saying, "Response is out of order with previous responses."
Any help would be appreciated.
So --- who is going to be in LA Next Tuesday 11/6/18?
I am and woud love to meet many of you.
ping me if you are interested in a get together.
Marianna
Getting a lot of multitrack files that are stems. (Split versions of edits)
Be very useful to be able to apply a 'split silence' effect that would put filler (or better add edits with clip volume set to silence) - as per ProTools.
This way I could see where there might be relevant audio to monitor, rather than having to use waveforms and soloing.
Hi,
Unsure if this is the correct place to post this but we have an Avid Nitris DX that failed a test after making a horrendous noise. The Test from the DX tester says "DMA failed to set". I was wondering if anyone could shed some light on what this means, please.
Many Thanks
My licences got lost in translation and expired one month early: last year I renewed on 10/11/2017, that is 10-november-2017 with the italian date format, they came across as the US date format october-11-2017. I want to publicly thank Lara Nugnes at Avid Roma, who catched and fixed this very fast as soon as I rang up to ask for renewal and told her that my licenses went down one month in advance, I would have never thought of such a tricky date format mismatch myself. This is what I call great after sale service!
Getting the following error when I have two sequences loaded in source and record sides. If I turn off dupe detection then everything continues to work fine. If I don't turn off dupe detection then this comes up with every action attempted.
Hello eveyone,
(please excuse my english, I'm french....)
I'm a (long time and experienced) Pro Tools user, mixer and sound editor, and have a question about AAF exports in MC2018.
I'm starting a new project (feature film) and for the first time in my quite long career am experiencing some kind of bug.
The AAFs I've received don't contain the volumes set by the editor. Clip gains do export correctly but volumes won't.
The editor's assistant in charge of the exports tells me there's no particular option to check in order for volumes to be exported.
I've sent the AAF to 2 different "colleagues" with different versions of Pro Tools and the result was the same.
I'm suspecting some bug in MC 2018 or, maybe, some new option the assitant isn't aware of...
Any idea?
Also, in case I don't find the answer, is there an option (as in Pro Tools) to quickly and automaticaly convert volumes to clip gains?
Thanks for any help.
Mat
Hi there,
we're having some huge problems with Media Composer 2018.8.
We have around 20 edit suites and are upgrading our whole facility from 8.4.5 to 2018.8. This takes quite a while. Unfortunately a lot of bins created in 8.4.5 raise an error in 2018.8 after you changed something inside the bin and then closing / saving it. The error is:
Assertion failed: iter != sWindowList.end ()
File s:\ppg\mediacomposer\media_composer\mcwindowsmenuutils.cpp, Line:141
The bins do not save and we cannot close them. Any suggestions here? We cannot migrate huge projects by creating a new project in 2018.8 and duplicate every content to a new bin. We need to work simultaneously on 2018.8 and 8.4.5.
Beste wishes
mult1
Hi all,
In many ways, it could be said that I don't deserve help from you guys… 🙃🙂
I have an aging Windows 7 (Home) computer is that I built a bunch of years ago for ProTools use, and it still runs well. I have no means to replace it, and I am attempting to move into the world of Media Composer, starting with First.
I know… I know… almost nothing I am trying to run it on his supported, but I am wondering if there may be back door ways to get this to work that some of you may know about.
It mostly installs fine, with the exception of about five plug-ins, and it begins to open fine, but after seemingly all is loaded, and it appears that the main editing screen is about to complete, the whole program just shuts right down, without any error notices.
So, my first step was to upgrade my memory, which was cheap, and I bought used memory modules of the same kind, so I am up to 12 GB. It still crashes upon opening.
The next step would be to consider updating the Windows 7 Home to Professional, but any installers I have found for that seem to expect a clean install, which means wiping my entire computer and starting from scratch, which would be a big old pain in the rear, considering all of the software I have loaded on this thing. Is there such a beast as a basic updater, rather than a completereinstall of, maybe windows 10?
I see on eBay there are many people selling licenses for Windows 10 for dirt cheap, which I presume will mean a complete reinstall? I have also heard a lot of people say stay away from Windows 10.
So, any thoughts about all this would certainly be appreciated.
It will also not be helpful to tell me that I shouldn't expect a new piece of software to run on an older computer. Not all of us can afford to be upgrading our computers on a regular basis, but I would hate to think that that would prevent someone from using a piece of software. Something tells me I am likely hallucinating, though… :-)
Thoughts or suggestions?
🙂🙃🎶🎹
I have a student verison of MC 8.4 and need to download a trial version of interplay pulse to make sure it works with the post house we are working with. Does anyone know where I can find that? Am I better off subscribing to the newest version of AVID which apparently comes with interplay?
Thanks!
Hello, I've just updated my Mac to MacOS Mojave 10.14.1 with Media Composer 2018.10.
Unfortunately now my Media Composer app crashes at startup; I searched around the forum but I wasn't able to find a solution to my problem. Does anyone have encountered a similar issue? If yes how did you solve it?
I use a Macbook Pro with Touch Bar 2017. These are my specs:
MacBook Pro (15-inch, 2017)
Processor: 2.9 GHz Intel Core i7
Memory: 16 GB 2133 MHz LPDDR3
Graphi1: Intel HD Graphics 630 1536 MB
Graphic2: Radeon Pro 560 4GB
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px 'Helvetica Neue'; color: #000000; color: rgba(0, 0, 0, 0.85)}
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px 'Helvetica Neue'; color: #000000; color: rgba(0, 0, 0, 0.85)}
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px 'Helvetica Neue'; color: #000000; color: rgba(0, 0, 0, 0.85)}
I also attached to the message my system report if someone need it.
I'm running MC 8.9 on a Mac OS 10.12.6. Every time I try to add a dissolve I get a message that the source drive in unavailable. When I go into Media Creation settings, all drives have been filtered out and there's no way to change that. Nothing is checked off in the Drive filtering box. All the drives have Read and Write permissions. I tried creating a new project and new user and that didn't change anything either. Any other possible fixes out there?
Thanks in advance!
I need to capture HDV tapes using a Sony FX1 camera. It's been a while since I've had to capture from tape and I've forgotton how to do it. What are the camera output settings and what are the input settings on Avid?
AAF from Media Composer to Pro Tools should be a seamless process but it is far from it. There are a bunch of caveats that must be adhered to to avoid crashes or to make sure that all the information is carried over correctly.
1. AAF export hangs when you have Multicam clips in the timeline.
This is a straight up bug that needs to be addressed. Workaround is to comit multicam edits.
2. Muted clips are carried over in the AAF but the media for the clips is not.
Seems like an oversight, please give an option to 'include muted media'. Workaround involves making a duplicate sequence and unmuting everything and then exporting media to a folder then exporting a linked AAF from the muted sequence.
3. Stereo clips do not include muted status.
Another bug. Only mono tracks retain the muted status inside protools. All ther tracks become unmuted again. Workaround is to zero the volume on all muted stereo clips.
Anyone else experience these issues or know if they have been addressed in a later version?
Running Windows 8.1 with Avid MC 7.0.4. Plenty of RAM for background transcoding (about 24 gb). Got a bit of a mess and I'm hoping someone has encountered this. Today I tried to transcode some DSLR media using the Background Transcoding feature. It's great and I've never had an issue with it. Let me repeat, I've never had an issue with Background Transcoding before today.
But today, the Background Queue was full of old completed jobs, but not the current job I had just started. Confused, I clicked the button in the top right hand corner of the background queue window and selected "clear inactive jobs". Now there is nothing running in the window. So I re-tried the transcode job again. Still no status in the background queue window. Then I hear my hard drives running and figured out that it was transcoding anyway but not showing me what it was up to. After checking the media tool I saw ".01" and ".02" versions of these files unnessesarily filling up my drives. Now, I can't seem to stop this transcoding job. I would just like to cancel all of it and try again but I can't clear the job.
Any ideas? Is there a way to reset the "Background Queue" permanently so it quits old jobs? Some sort of preference file I need to delete/rebuild? I don't want any more media floating around in the media tool than is necessary. I'd rather not reinstall Avid, but I'm almost ready to do that.
2018.9 and 2018.10 both exhibit this bug (I haven't checked anything prior to 2018.9). When I open the Dynamic Relink Settings Window and try to check the "Enable Dynamic Relink" checkbox I'll see the detailed settings appear briefly and then the box unchecks itself and the settings hide themselves again. Please look into this.
Join Avid and Key Code Media on November 6 (7:30 pm PT) for an exclusive special guest panel, Q&A session, and Media Composer technology preview on Facebook Live. Send us your post production questions —tag #AskAvid— and get the answers during the live broadcast.
Hey everyone,
Anybody run across this error recently? VDM3BobVideoOut::Setup:Unexpected state
Shows up in the source window as I'm logging clips, usually when shuttling video. Effectively freezes MC and sometimes causes it to crash. It's annoying as all get-out, and the only way to avoid the error is to restart avid with my Blackmagic Device disabled. Of course, that makes it sort of hard to work with any efficiency... Seems to run normally without my BM hardware connected.
I've experienced this running MC2018.10 and 2018.8, but not prior to those versions. I ran 2018.3 for months without this issue. I have reason to believe that this has something to do with my Blackmagic Mini Monitor and newer versions of MC, but as far as I know I'm running the Avid recommended BM drivers (most current 10.11.4, and previously I ran 2018.8 with BM 10.11.2 and experienced the same problem). Now running on a clean install of Windows 10 Pro with dual GTX1070 cards and a newer GeForce driver.
Got any ideas what this could be caused by?
EDIT:
I got one more error just now, one I hadn't seen yet:
"Exception: Fatal Open I/O Error - Callback consistency check failure"
Just wanted to add that.