I'm guessing that beyond nVidia drivers and QT, there are other drivers that could be causing the issue. For example, Wacom.

I'm also wondering if this has anything to do with Mojo or other Avid hardware connected to the box. I haven't had time to try the steps to reproducing this issue but I certainly will try (hopefully later today).

Am I correct that this only happens when the mouse scroll wheel is used to scroll?

Is there any relationship to the media appearing in the bin. For example, are you all using AMA files or HDV or ???. How about HD vs SD?

Steve,

Correct, only when mouse scroll wheel.  If you use the click/drag slider instead of the wheel, you're golden.

I've have the crash with older projects and when I test by starting a new projects; AMA or non AMA.  Some of my projects have HDV footage that has been captures; other are 100% footage that I've converted to DNxHD and imported.  But all HD--you've got me there. I do have a quick SD project to do this week, I'll do it in MC5 and see if I can produce the crash.

No Mojo or external devices, only the software.  I do have Looks installed for plug-ins, I can't say definitively whether or not it's crashed without it installed.  I'm running QT 7.6.6 & 190.38 for Nvidia, as I had matched all the versions to the MC matrix in troubleshooting this.

Thanks,

- wb

I'm wondering if it has something to how Windows caching the thumbnails? I was having problems with Windows crashing everytime it was was loading the thumbnails for AVCHD files. I had to install shark codes and update ffdshow and the crashing stopped in windows.

Like I said, I've been scrolling with the mousewheel in Scriptview with no crash; so that's why everyone is asking what else you have installed if you have all the Avid certified drivers. Trying to help....Salud!

Hi all,

my Mojo analog is not connected so this shouldn't be an issue. The crashes appear with Mojo connected or not. It makes no difference.

As my system has no MB Looks insalled (just a clean install of Win764 QT and MC5) this shouldn't be an issue either.

@halo

I had this crash recently with a DVCPro50 SD project. All AMA linked P2 footage.

Regards

lunalobo75:

Like I said, I've been scrolling with the mousewheel in Scriptview with no crash; so that's why everyone is asking what else you have installed if you have all the Avid certified drivers. Trying to help....Salud!

Looking for answers.  How about mice? Is there any connection between the crashes and USB mice vs standard wired mice?
I was using a USB mouse when I tried, unsuccessfully, to induce a crash.

Regards,
Douglas

Random Post:

Open an project, load a timeline the usual way.... then open a bin, switch the bin into "Script" view (right-most tab in a bin).  In "Script" view, use the scroll button on your mouse to scroll down to a clip you might use in your edit. Make sure your bin is populated enough that you need to navigate up / down in the bin.   Double-click the choosen clip to load into the source monitor.  Doodle some action on the clip (play, rewind, mark in, etc...) Then, open another bin, switch to "script" view.... using the scroll button on the mouse, scroll up / down to another clip, double-click on a clip, edit into timeline.. etc.

After three of these scroll-to-a-clip using mouse scroll button in "Script" mode, both my Dell 670 (approved config, see specs) and the HP8600 (Win7/FX3700 approved config) I am currently using  to cut a documentary at a broadcaster, all crash.

Avoiding scrolling with the mouse scroll button, is the ticket.  I've been using the slider to navigate up / down in the bins and I have not had any problem, even though the bin is in "Script" mode.  I've also changed the default background, in all the bins, to a nice soothing shade of yellow... Thanks to Larry R. 's  excellent suggestion.

FYI Random: After following your step-by-step procedure to the letter (including "doodling some action") - trying 6 different bins, many edits, lots of script view scrolling and random "doodling" - still no crash. 1080i project, many different types of media - AMA included. This on my hand-built i7/920 Vista 64 Ultimate system (see specs). Hope this adds another piece to the puzzle. I will not automatically see any replies to this as I've unsubscribed this thread. May all your crashes be recoverable. Good luck!

drbgaijin:

How about mice? Is there any connection between the crashes and USB mice vs standard wired mice?

Great idea - I use a USB Dell mouse - so USB should not be the problem :(

Interesting idea; I indeed don't think I've tried a PS/2 mouse.  Always wireless or usb corded.  I'll see if I can dig one out of my garage and do some testing :) .

- wb

editorofchoice:

drbgaijin:

How about mice? Is there any connection between the crashes and USB mice vs standard wired mice?

 

Great idea - I use a USB Dell mouse - so USB should not be the problem :(

Not necessarily. Mice have drivers too. e.g. with the Wacom problem (USB) it was the driver version that was the factor in whether the Wacom caused playback/stop problems or not.

But if we get into drivers for any/every piece of hardware that we have connected.... we will get hopelessly bogged down and probably not get anywhere anyway.

Regards,
Douglas

it could very well be a mouse problem. ive had mouse problems with other applications as well, but i dont know if it will pertain to media composer. Anyways, in after effects, it would always jitter, i mean literally the whole window, when accessing a menu would just randomly jitter and it would mess up the screen so i would have to reselect what i was about to click. it was very annoying, but i found out it was an old microsoft mouse driver problem causing this weird occurence. idk, maybe a mouse problem, i've had my share of those problems.

EOC:

Just for the hell of it, why don't you switch to a standard corded mouse and see if the problem persists.

I know this may be a simple question - but has anyone (who has the scriptview crash)  check the event viewer in Administrative tools, or check the crash report?

Larry Rubin:

EOC:

Just for the hell of it, why don't you switch to a standard corded mouse and see if the problem persists.

It is a standard corded mouse but I will try another one. But I don't think that it will use another driver in Win7. Becasue every mouse (unless you install a specific driver) uses the standard windows mouse driver.

But I'll give it a try.

Thanks and regards

Hello,

today I joined MXO2 mini and edited the whole day, used a script with the mouse wheel if the fall occurred. Pojekt 25iPAL. Note that earlier I was able to crash the system call within 2 minutes. Major changes in the system configuration was: remove the second graphics card Qvadro370 (she was involved did not work MXO2) MXO2 connection and install the appropriate drivers. Maybe this will help solve the problem. Tomorrow or Monday I'll try to HD otastovat pojektu in which 100% of the fall occurred.

William

Team P. S. Mistake I was able to produce certified stations DN HP8400 Nitris, Win7 on which I work, too.

Tried to reproduce with a bin with about a dozen clips in it. Scrolled exclusively with the mouse wheel in script mode, copied clips from the bin to the timeline, double-clicked in bin to move them to the source window and them cut them into the timeline and back to the bin to scroll with the mouse whell. Did this for about 15 minutes without a crash. I'll continue to try this every once in a while but for me, there does not seem to be a problem with the script view and MC 5.0.3.5.