Hi there,
After several years of trouble free use I cant get AMC to start anymore. It seems to stop on Intiialzing Audio Plug ins, then comes up with the crash report screen.
I'm running Windows 10 Pro, 64 bit, on a i7 2600 running at 3.40GHz, 32 MB RAM, Avid MC 7.0.6
I havent made any changes to the system, only a Wndows update is the only thing thats changed.
I have uninstalled and reinstalled, I also deactivated and installed on my laptop and the same thing happened which makes me think this is a wnodws update issue
Any suggestions would be appreciated
Thank you
Rob
www.hdimages.tv
www.robscheeren.com
I'd do a system restore to a point before the window update and see if it comes good.
If it does then you know the cause.
Broadcast & Post Production Consultant / Trainer Avid Certified Instructor VET (Retired Early 2022)
Still offering training and support for: QC/QAR Training - Understanding Digital Media - Advanced Files * Compression - Avid Ingest - PSE fixing courses and more.
Mainly delivered remotely via zoom but onsite possible.
T 07581 201248 | E pat@vet-training.co.uk
What's the error message saying?
I've spent 3 days working with Microsoft on this. Since last week's patch, this verison of Media Composer is crashing at the Intializing Audio Plugins section. (I'm still on 7.0.4)
Rolling back resolves the issue, but - and here's the big part - Windows 10 cannot disable the patching/upgrade process. I have rolled back once a day for almost a week to continue working. I mean, you can disable the service, and even uninstall the Windows 10 Update assistant - but guess what? It will auto restart, install and execute the update assistant. Thank you Microsoft.
To roll back - go to "Windows Update settings" (you can hit the windos icon and just type this in).
Update History -> Recovery Options.
As I was typing this, Windows 10 Update Assistant just fired back up. Fortunately I was able to kill the process from the Task Manager before it updated.
It would be nice to understand what is causing the issue. The Microsoft Tech had me run Media Composer as Administrator, thinking maybe permissions might be an issue. No luck.
David
GoFetch Media, Inc.
David Rawlins: Windows 10 cannot disable the patching/upgrade process. I have rolled back once a day for almost a week to continue working. I mean, you can disable the service, and even uninstall the Windows 10 Update assistant - but guess what? It will auto restart, install and execute the update assistant.
Windows 10 cannot disable the patching/upgrade process. I have rolled back once a day for almost a week to continue working. I mean, you can disable the service, and even uninstall the Windows 10 Update assistant - but guess what? It will auto restart, install and execute the update assistant.
Thanks for the info. Horrible.
Good luck
Hi, all,
I've had the same problem with MC 7.0.7 starting on Sunday the 7th, after the Windows Update. Exactly the same crash point.
I spent most of yesterday with Avid Support to come up with a solution. Eventually, I decided to do a rollback. The update had installed a new version, 1709, build 16XXX. Prior to the upgrade the version was 1703, build 15XXX. MC 7.0.7 had been working perfectly under the 1703 build.
However, after the rollback, we could not get MC 7.0.7 to run; it crashed during init hardware.
Our final solution was to roll the MC version back to 7.0.5. Rather disappointing. But, at least I'm able to carry on with my work.
Best regards,Will
The error doesnt say anything, just comes up with an empty window and a Send to Avid option. I can save the log which I have done, but theres a lot of information there, nothing that really is clear to me.
Thanks for your reply Will, I have been back to the Avid download page for MC but cant see a 7.0.5 version, it goes from 7.0.6 which I have and doesnt work, back to 6.5.5... but no 7.0.5. I fyou know of a download link that would be great
So I just installed Version 6.5.5. and am still getting the crash at the same point. I guess I need to roll back the Windows update and was hoping Will might be able to shed some light on that process.
I looked at the programs and features to unsital the updates but not clear what to uninstall. There are multiple Microsoft Visual C++ updates and Windows Driver packages and also a Windows Essentials 2012 which all updated on the same day. Any assistance with how you rolled bacxk the update would be appreciated
Hey, Rob,
Yes, I see that. The versions from 6.5.5 to 7.0.6 have been deleted.
We installed 7.0.5 from a copy I have on my suite computer. As it turns out, it's not working as well as I originally thought when we got it running, yesterday. Every little change is met with an error message; "Exception: RGBAreader_UNKNOWN_COMPRESSION_TYPE". That was earlier.
Now, I get the same error message when trying to play the timeline.
I now remember when I had this version installed before, in 2016, I had problems changing settings, especially creating new export settings.That's probably why 7.0.5 has disappeared... too many bugs.
Cheers,Will
I wonder if anyone on v8 is having a problem...
I'd like to know what Avid's response is to this. We have paid for perpetual licences for these products, Surely they should be maintaing these products that are only a year or two old.
I have several projects in the system that I cant finish and my clients are looking at me like whats going on?
Hey, Rob, et al.,
Well, here's an interesting twist... I'm back to MC 7.0.7. It opens just fine, but it's giving the same error message as 7.0.5 did.
When the Avid Support Representative ended the service call, and closed the case, MC7.0.5 was opening successfully, but was giving an error message: Exception: RGBAReader_UNKNOWN_COMPRESSION_TYPE, as mentioned above in my previous post. At first, the error message would be presented immediately as the project completed loading in the timeline, and when a change was made to a setting. However, the problem escalated to the extent that the message was given with every operation on the timeline and in both Composer monitors. Some operations would be completed, others would not. Most importantly, the timeline would not playback.
Other issues were occurring in MC7.0.5, which I now recall, were the reasons I upgraded to 7.0.6 as soon as it was available. Among these issues were being unable to create new export settings, and Avid Background Services not working. In my case, some of the issues remained unsolved throughout any updates and patches of MC7.0.6. All issues were resolved when I installed MC 7.0.7. In fact, MC7.0.7 ran better under Windows 10 Pro, than any previous version of MC, SY, XPro, or XDV, ever ran on any of my computers. That is, until last Sunday evening, after the Windows Update.
We did a Windows rollback during my session with the Avid SR and we re-installed MC7. First we tried MC7.0.7 and it would crash, as before but at a different point, as described above. We tried installing MC7.0.5, which appeared to be a solution. But, it's not, as I say in this note, above.
With the error message and the other issues in 7.0.5, I uninstalled it, and re-installed MC7.0.7. As I said, it's now opening fine. Just the error message issue.
I'm going to have Avid re-open the case.
I'll keep you posted with any successes.Best regards,Will
The Windows 10 update that you rolled back will return. Then you won't be able to launch again until Avid identifies the issue and provides a resolution.
I'm in the same boat with clients and projects. Rolling back allows me to work again, but even powering down host last night, when it came back on it was immediately updating before I had windows control. All I could do was watch.
I had the same issues regarding Symphony V6.04 crashing at initializing audio under Windows 10 Pro, after a recent update just prior to Xmas.
The machine I experienced this on is my home system which was connected to both the internet and my local home network by a standard BT provided router. It is used solely for editing.
I initially solved the issue as others have by rolling back the update and carried on from there. However after powering the PC down, on reboot the update reinstalled and I was back where I started. Initially I believed the PC was re-downloading the dodgy update so I simply pulled the ethernet connection to test the theory out. I then rolled back the Windows 10 update and once again on reboot the update reinstalled itself. This was a problem!
My Solution (after 3 days of misery)
Firstly my disclaimer, I was trained in 2" and 1" VT machines and I am in no way a computer expert. I'm sure the following lacks elegance. However it is still working after multiple reboots.
1) I removed the ethernet connnection so as not to see the internet and then rolled the Windows 10 update back as before
2) I did a Google search on 'flush windows 10 update cache' and followed the instructions on one of the many search returns regarding how to deal with corrupted update downloads (my apologies I can't remember exactly which site I used)
3) I then changed the PC's default gateway to a random entry in Network connections. The PC now no longer see's the internet but on reconecting the ethernet cable it does still see my NAS and other PC's on my local network. This has stopped it re-downloading the dodgy Windows 10 update. It has also had the unfortunate side effect of blocking Windows Defender from updating automatically so the PC is becoming gradually less secure.
I believe it may be possible to manually update Windows Defender updates but I've yet to try. This solution is obviously only any use if you don't require the ability to browse the internet from your Avid. If anyone has a better solution I'd be delighted to hear it.
Paul
If you're on W10 Pro, you can disable automatic updates by starting the group policy editory and choosing the option to disable automatic updates. If you are on W10 Home, and you connect to the network via wifi, you can change your connection type to metered. This will also prevent automatic updates. You can search for how to do this online (there are many tutorials). If you're on W10 home and use a hardwired connection you can stop the updates by disabling the update service, but then you are incapable of getting any updates including seccurity patches, and when you turn it back on, it will first update Windows.
Dave S.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller