Byron Roome:

No one has seen this before?  I even included a print screen :)

I realize I'm reopening an old thread but I never saw where a solution was found.  I just upgraded to MC 3.0 (and then 3.0.5) and (while not everytime) I have seen this pure virtual function call error show up several times.

I'd appreciate any assistance or insight as to where to look for this weirdness.  Everything works fine, just an annoying error.

 Not in front of my editing computer at the moment.

The only annoying error message I recall of his nature appears when I exit MC while my edit deck is still switched on (and connected).
I can imagine that even having a firewire connection to a camera (which is still on, when you close MC) would give a similar error message,

As far as I understand there are 2 ways of dealing with tis:

1. Exit MC while still keeping your edit deck/camera on and connected - and get the error message.
2. Remember to switch off your edit deck/camera before exiting MC - and not get the error message.

I tend to be a 50-50 man. Sometimes I remember to switch off/ sometimes I don't.

Regards,
Douglas

 I have noticed the same thing with my Canopus ADVC 300 unit , seems to be a firewire connection issue

added

and, this on an uncertified sys of course ...

Thanks.  I turned off my DSR-45 before exiting out of MC and did not get the error.  I turned it on, exited out, and the error returned.  It does seem to be tied to having a deck connected and powered on when you close MC.

I never used to turn off the deck when running AXP but if that's all it takes then I'm good with it.  The upgrade went very well and that was the only oddity I noticed.

dj