Hi, I have done a test of stability for the next project, 1080i50, and unfortunately the problem is the script mode occurred. The difference between the projects is that the one where the problem still did not show was originally based on MC4.

Sincerely, William

I just created an account to concur with editorofchoice and the others that YES, this is an issue with script view. It appears that fast scrolling with the scroll wheel definitely causes it, and the Avid guys here to help transition us to NC9 weren't aware of it, but now are. It happens to only me on any computer I use at the TV station I work at, but it did happen to one other guy today. I basically just use the Interplay window to get around it, as I edit much faster with the scroll wheel.

GP1138:

...and the Avid guys here to help transition us to NC9 weren't aware of it, but now are....

Whaaaa.... the original post was made in April and AVID's support personal doesn't know about this problem...?

I wonder if they know you also can't do a simple drag and drop of a video's audio clip to an activated audio track within a timeline with MC5... a drag and drop of a video clip will only default to the audio tracks A1 and A2 - only... some how I doubt.

Joe M:

GP1138:

...and the Avid guys here to help transition us to NC9 weren't aware of it, but now are....

Whaaaa.... the original post was made in April and AVID's support personal doesn't know about this problem...?

I find this extremely distressing. This issue was escalated and logged as a bug in June and July. Avid engineering requested and received bin files from users experiencing this issue to try to track down the cause of this problem. For Avid on-site support personnel to be completely unaware of this issue and it's history is disappointing, to say the least.

Like I said, really nice and helpful guys, but yeah, they didn't know anything about the bug. I get an "ASSERTION FAILED" crash that can't be recovered from, and the program has to be quit. I either save after every edit or I use the Interplay window. It varies, but sometimes it happens even when I first open a bin and scroll. SUPREMELY annoying. These are brand new machines, too, Dell T5500s.

I'd be curious to hear what you experience if you use Interplay Access instead of the Interplay window inside MC.

Just a suggestion:

Why not have the people who are having this issue post the type of mouse they are using and its driver version?

You can get the driver version by right-clicking on MyComputer, choosing Manage, choosing Device Manager, choosing Mice and other pointing devices and choosing the Driver tab.

For the heck of it, I'd also click on the Resources tab and jot down the Resource type (it should be something like IRQ 12).

Larry Rubin:

I'd be curious to hear what you experience if you use Interplay Access instead of the Interplay window inside MC.

Hi Larry,

why should he do that? I did not understand that there was an issue with IPWindow. It only happens in a bin ;)

cheers

-chris

BobbyMurcerFan:

Why not have the people who are having this issue post the type of mouse they are using and its driver version?

Good idea ;)

I do not have the issue, but I post my details here anyway so we can compare:

I use Wacom Tablett Sapphire CTE-630/Bwith driver and a Razorback Diamond Mouse. Drivers are HID-compliant mouse, Provider Microsoft and Version 5.1.2600.0. I just realized I did not install any additional software from Wacom or Razorback. Using XP Prof SP3. Keyboard, tablett and mouse are connected via KVM-Switch from Digitus. Keyboard is PS2 and Mice are USB.

All right, Version 5.1.2600 seems to be default to WinXP SP3. You will find this driver version for many different devices on the system. So the point is that here it is a standard windows installation without any additional drivers for the mouse or the wacom tablett.

I also saw that COM1 uses the same driver version, but the provider is avid ;)

This iswhat I get from System Information:

System Information report written at: 12/18/10 09:21:02
System Name: xxxxx
[Pointing Device]

Item    Value    
Hardware Type    HID-compliant mouse    
Number of Buttons    5    
Status    OK    
PNP Device ID    HID\VID_0B39&PID_CD02&MI_01&COL01\7&1F5FAD3D&0&0000    
Power Management Supported    No    
Double Click Threshold    6    
Handedness    Right Handed Operation    
Driver    c:\windows\system32\drivers\mouhid.sys (5.1.2600.0 (XPClient.010817-1148), 11,88 KB (12.160 bytes), 23.03.2005 17:39)

Also, SysInfo displays some sharing issues with IRQs, but I do not have any probs because of that...

Once again I do not have the scriptsync-issue. So maybe the information provided above can help others narrowing the search...

cheers

-chris

chris.... could you do me a favor...

Go to the Bin Settings - Current (in the Settings tab/windows)... change the "Double-click loads object in:"  drop down window to... "New Pop-up Monitor" (instead of Source or Record Monitor)...

Then, while in the Script bin make sure it is populated with at least 15 diffferent videos sources... click the right mouse in the Script bin for different video clips... this should open up a Pop-up preview window... do this numerous windows (at least 14-15 windows)...

....see if you get a error pop-up window after or before you get to about 15 or so Pop-up preview windows.

I have been dealing with the same issue.  The frustrating thing is we have two nearly identical machines and it only seems to happen on one.  Both are HP Z400, Win 7 64bit, Nitris DX, QT 7.6.6, recomended Nvidia drivers and Avid 5.  They both had 5.0.2 and I updated the machine that is crashing to 5.0.3 to see if that made a difference and it did not. I am always editing in  script bin view when it crashes.  Definitely seems like a bug that needs to get fixed.

I have to report that my system also crashed at script view (HDV 1080i/50 project) when I try play several takes from bin. I have MC 5.0.3.5, system info posted below.

This bug need to be fixed!!!

Runining AvidMediaComposer.exe has an administrator seems to have cured the problem for me.

Phillisp:

Runining AvidMediaComposer.exe has an administrator seems to have cured the problem for me.

As far as I remember, when you want to use MC not with an administrator account, you need to start MC after installation as an administrator. After that, you can use MC also with another useraccount. I think it is somewhere in the installation guide. Can anybody confirm?

If you experience the "script issue", which windows user do you use?

cheers

-chris

That is correct. Your OS user profile must be at the administrator level when installing Media Composer.