Well, it appears I spoke too soon.
After not having the problem for a day or so with only two monitors connected -- it came back again late today -- with only two monitors connected.
Looks like that theory has bit the dust.
And, regarding a DAE effect -- I can say that this is happening without any in the project.
I am glad I'm not losing work -- but I agree -- it is very annoying and it feels fundamentally wrong to have an application at this level closing in such an ungraceful manner.
If anyone else has a solution I'd appreciate hearing it.
Thanks.
--- In Avid-L2@yahoogroups.com, "Luca Gazzolo" <luca_gazzolo@...> wrote:
>
> If this is happening after running a DAE effect during the editing session it is "normal"... until someone at Avid decides that it is something that needs to be fixed. If it is happening when not using a DAE effect then it's something else.
>
>
> --- In Avid-L2@yahoogroups.com, Christopher Pitbladdo <avid@> wrote:
> >
> > I used to have exactly the same symptoms as you describe when I first
> > upgraded to V5 on an HP XW8600 PC. I'm not sure when the problem went
> > away... Maybe when I updated the OS to Win7, or when I updated MC to
> > 5.0.3.r7? I'm not sure.
> >
> > It was only ever an inconvenience for me, although I'm glad it's gone.
> >
> > *Christopher Pitbladdo
> > Creative Director
> >
> > DB Creative*
> > 496 Ferry Road
> > Edinburgh
> > EH5 2DL
> >
> > Tel: 0131 552 5530
> > Mob: 07590 570 683
> > Email: christopher@ <mailto:christopher@>
> > Web: www.dbcreative.tv <http://www.dbcreative.tv>
> >
> > Award-Winning Avid SD/HD Symphony Editing in Edinburgh
> >
> >
> > On 10/07/2011 09:15, blafarm wrote:
> > >
> > > Somewhere back around v.5 (on PC) -- I started not being able to
> > > cleanly close-out of MC without an error message.
> > >
> > > Using "File>Exit", MC grays-out and hangs until I click my mouse on
> > > the application. At which time, I am presented with an error message
> > > that reads: "Avid Editor has stopped working". The options are to
> > > check online for the problem (which is a dead-end) -- or close the
> > > program. I always select close the program -- and it will shutdown MC.
> > >
> > > I have updated several times to the newest versions of MC using the
> > > correct procedure -- and I keep expecting the problem to disappear --
> > > and yet it never does. Importantly, I've never lost any files or work
> > > -- but I am growing weary of not being able to exit cleanly -- and I
> > > am loathe to start a paid trouble ticket for this issue.
> > >
> > > I've searched high and low on the web for a solution. Anyone else have
> > > this problem -- or have a sense of what might be the cause -- or how
> > > to solve it?
> > >
> > > Thanks.
> > >
> > > The "Problem Details" associated with the error message are as follows:
> > >
> > > Problem signature:
> > > Problem Event Name: APPCRASH
> > > Application Name: AvidMediaComposer.exe
> > > Application Version: 5.5.2.18480
> > > Application Timestamp: 4dc2db8f
> > > Fault Module Name: ntdll.dll
> > > Fault Module Version: 6.1.7601.17514
> > > Fault Module Timestamp: 4ce7ba58
> > > Exception Code: c0000005
> > > Exception Offset: 0002dedb
> > > OS Version: 6.1.7601.2.1.0.256.48
> > > Locale ID: 1033
> > > Additional Information 1: d3dc
> > > Additional Information 2: d3dc4f779579ffa4068ec94c2025ee19
> > > Additional Information 3: 9531
> > > Additional Information 4: 953134fc15cbd1945b875e131d725182
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
If you want to donate to Red Cross quake relief, you can do so through your cell phone. Text redcross to 90999 to make a $10 donation. It will be on your next cell bill.
No comments:
Post a Comment