Oh man. I am now running MC 4.0.2 with the new Sept 29 released Intuos 4 driver (612-3). Same problem. Anyone have any luck?

There was such promise. A new MC and a new Wacom driver.... Two new releases and two fingers pointing at each other

What about that mark-in fix noted earlier - does that work for you?

Maybe Windows 7 is our next hope. The mark in/mark out function didn't correct anything for me.  I haven't run into this issue on OSX though. Avid/Final Cut seem to work perfectly with the Intuos4 on a Mac.

I'm another frustrated intuos 4 tablet user. The Mark in/out thing works for me. But that can only get you so far. It's pretty dissapointing. I'm running Vista and windows 7 with the same issues.

The tablet works perfectly everywhere else.

Man-o-man I hope this gets resolved soon. $500 bucks wasted on a tablet isn't my idea of a good time.

EDIT* Well something worked, but it seems it was only temporary. Mark in/out doesn't seem to work anymore.

Bah!

Great... my old Wacom tablet pen died and I just installed a new Wacom Intuous4... it is awesome for Corel Painter, fwiw... complaining to Wacom...

I have tested the same setup on my MAC pro running OSX 10.5.8 and intuos drivers 6.1.1 and everything runs fine. So it's clearly just a windows based issue.

I also tried all the different suggestions on this thread and nothing has worked so far.

The issue is most likely caused by Avid and Wacom using different versions of the same library code, or by them creating core program components with the same name.  If that's the case, unless one company or the other is prepared to change their methodology, it may never be fixed.  The fact that it doesn't happen with OSX is consistent with this assumption.

I briefly also used a Wacom tablet with MC, ran into the same problem, and abandoned the tablet on that system.  The one thing that I did find was that the effect appeared to vary with tablet placement.  If I got the problem, moving the tablet physically often corrected it.

Now that feels too much like black magic to me.  I tried searching for electromagnetic interference, dodgy cables, all the usual suspects, but was never able to come up with a satisfactory solution.

It's now a permanent part of my AE workstation, where it does work.

I decided to try this in Vista 32 with 4.02 today and had some success. Occasionally I'll still get the problem, but mostly it works.I was using drivers released by wacom a few days ago (6.12-4)

Are people with the problem running 32bit or 64bit OS? Perhaps it's a 64bit issue?

I seem to have fixed the issue for myself. I am running windows 7 64bit, but it should also apply to those using Vista, not sure about XP.

First thing I did was open up the group policy editor.

Quick way to do this, in the start menu search bar type cmd

In the window type gpedit

Then go Computer configuration>administrative templates>windows components>Tablet PC

Within that window I pretty well disabled (and by disabled, it sort of means enable, it will make sense when you look at it) everything I could. I don’t know for sure, but it seems to me that the windows tablet support side of things, is double dipping with wacoms drivers.

Second thing I did was go into the control panel and disable all of the pen flicks etc that I don't use anyway. Here is a list of what I turned off/changed in the settings. 

control panel> Pen and Touch

In pen options I disabled Press and Hold and I turned off start tablet PC input Panel

So far I have been running my intuos 4 tablet without much of a hitch. I say "much" as it has still come up with the same problems on the rare occasion, but mostly it’s about 95% working.

I guess the down side is if you normally utilise pen flicks etc. I don’t so there are no loss to me.

Hopefully this will work for others. I’m sure I didn’t need to disable everything in the groups policy’s but I figured I had nothing to lose by trying.

I just got my official response from wacom

"We are very sorry. We are aware of the problem. The issue comes from avid's
side and we cannot change their software. (Our tablet driver has no special
treatment for Avid). So far we have no sollution for this issue. But avid is
not listed in our software atlas."

Haha, oh well. I guess this issue isn't going to be resolved any time soon.

One day [:'(]

The solution for this annoying Intuos4 problem:

From the

Avid Knowledge Base

Why can't I stop playback of my media when my Wacom tablet is connected?

Some Wacom tablet drivers (version 6.1.0-6, for example) cause playback issues with Media Composer, Newscutter, or Symphony.

To rectify this:

1. Close the editor application
2. Create an emplty text file named "wintab32.dll"(you can Right Click on your Desktop and select "New Text File," then replace the default name with "wintab32.dll")
3. Make sure the .txt extension is removed
4. Place it in the same directory as the Media Composer executable [(install drive):\Program Files\Avid\(Editor Application)]
5. Re-launch the editor application
6. 
   

http://avid.custkb.com/avid/com.instranet.InstraServlet?Command=com.instranet.CmdDocVote&Redirect=/avid/app/selfservice/search.jsp&DocId=290089&UEL_DocVote_DocId=290089&UEL_DocVote_Rating=5&UEL_DocVote_VotedDocExtIds=&Module=selfservice

Really great tip! I wish I would have known that  few months ago. I wound up installing an old driver for my Intuos3. Good to know there

Fantastic,that works for me too. Happy days.

Any tech heads know what this fix is actually doing? Not that I care that much, just happy to be able to make use of tech new tablet. Thanks.

Dynamic Link Library files (DLLs) are files that contain code that is dynamically loaded as the main program needs it.  The order in which they're searched for is the local launch directory, then several Windows directories.  So by creating a null file called wintab32.dll, Avid will find the local file of that name, attempt to load it, fail, and not try again.

That file presumably contains support for functions that Avid never directly uses, but is none the less included in Avid's software library code.  It could also be automatically linked in by the compiler regardless of need.  Either way it's apparently totally unnecessary for Avid to function.

I can't believe it!

Someone finally found a solution that works for this annoying problem ! Excellent.

Uhm, Mr. Avid, Mr. Wacom - hire this man!