Premiere Pro CC Cursor Offset

[roarfilm]

Hi all,

Strange issue that has just started this morning. The cursor in Premiere Pro seems to be slightly offset, above and to the left.

For example if I want to add a cross-fade to the end of a clip I drag the transition from the effects panel and hover over the end of a clip in the sequence. However instead of being able to drop it in position I get a cursor with a cross next to it indicating I can't put the transition there. If I then move the cursor above the clip and slightly to the left I can drop the transition on the clip no problem at all. It's as if Premiere Pro isn't quite sure where the cursor really is. Strangely though normal selection of clips and general clicking around the interface is fine, it's only when dragging or hovering on something that this issue appears.

It is also confined to Premiere Pro as no other applications on Mac OS X are exhibiting this behaviour.

I've already checked that I've got the latest updates installed and tried a reboot but the issue persists.

Any suggestions on how to fix it? Thanks

[gregb6937055]

Hello,

I too am struggling with this issue. Did you find a solution?

Thanks.

[gregb6937055 · Accepted solution]

After pulling out the bulk of my hair I have, as often is the way, found a simple cause and effect of the problem;

I calmly disconnected my second display (it might have unplugged mid flight as it flung toward the wall), and reduced the workspace to a 1 screen set up - and voila; no misplacement of the cursor.

Plugging in the second display after giving the program this chance to pull itself together, everything is back to normal. Except my hair.

Hope that helps you in some way!

[sambojo]

I too have been struggling with this problem.  If I tried to drop a video clip from the project window to the new comp button it wouldn’t work unless I was about 1/4" up and slightly left.  Also when moving a clip in the timeline it would try to drop it on the clip track below it.  This was a total pain.  I solved mine the same way sorta.  In my System Preferences - Displays panel (I'm on a mac) I clicked on the mirror displays and then unselected it.  It appears to be a graphics thing and any change will reset it.   Not sure why it is happening.  Seems to be working now though.

[ananggadipa]

Yes check and uncheck mirror display fix it. thank you.

My problem was the cursor icon do not change/reflect on selected tool.

Everytime I found weird solution to adobe's bug:

[Raulsm]

It worked, I had to re-start Premiere I plugged the second monitor and all back to normal.

[ElementEditor]

Same problem here (see video)

Premiere Pro Cursor Offset Drag Snap Bottom - Sendvid

Absolutely annoying!

Even if the Display Mirror Check/Uncheck thing works... I need to do it every time I restart the computer and Premiere.

[Riff Raff Photography]

Good stuff. This was driving me mental, I tried unplugging my second display like suggested by gregb6937055 however, although it seems to have helped others, it didn't resolve my issue. But your suggestion did, so thanks to you both for your solutions!

[dkort6]

I am having the same issue. Based on your solution, I simply resized my current workspace from stretching across both displays to fitting on a single one. I tried, and my cursor problem was fixed. I stretched it back out across both displays and it was still working properly.

I have to repeat the steps of sizing it down and back out every time I completely close and open Premiere; it's fine when switching projects.

[mdr525]

Thank you for that workaround.  I thought it was my Wacom that was screwing it up.  After restarting and it not fixing the problem, I resized the workspace window and it fixed immediately.  I believe I had part of the workspace between my first and second screen. 

[EENewton]

I tried the "Mirror Display" solution and it didn't help, but when I looked carefully at my Premiere window I noticed it was very slightly edged toward my second display.  Shrinking it slightly and bringing it wholly into the first window fixed it.  Thanks!

[oluwatosina6343574]

Thank you, you have just saved my full head of hair

[youngo]

Thanks, this worked, though I had to reboot before plugging the second monitor back in.

[Ronno]

Thanks for 'discovering' this fix. Was totally frustrating - very happy I found this.

[michellec69855599]

The dual monitor mirror/un-mirror fix doesn't always work for me, but changing the Premiere workspace settings (Windows -> Workspace) to 'All Panels' and then back to my pre-set has worked for me more often than not.

[eclecticscribe]

This issue was driving me to man tears - thank you. Disconnecting the second monitor put me back on track.

[Gus Evangelista CBN]

I've isolated the problem to this file : WorkspaceConfig.xml

Located here:

Macintosh HD>Users>(computername)>Documents>Adobe>PremierePro>10.0(CC2015)>Profile-(computername)>Layouts

THE FIX:

Close PPro

Delete (or re-name) the file WorkspaceConfig.xml

launch PremierePro

PPro will make a fresh WorkspaceConfig.xml from scratch. Your saved workspaces should remain intact. It happens to us once in a while, probably every 2-3 months.

Hope this helps!

[eclecticscribe]

Thank you. Worked, and it is much more simple and less time consuming the unplugging monitors then rebooting - especially since this appears to solve the problem for a long time before it rears its ugly head again.

[harriettm14466082]

Sweet baby jesus thank you so much.  It is VERY annoying when it happens. deleting the WorkspaceConfig.xml worked like a charm.

[gbmcinephoto]

Oh my! Thanks for this simple fix!

What a maddening and annoying bug!

[toddp74137589]

Maybe even simpler as I think mentioned above, is the panel was ever so slightly stretching over into the second monitor space causing erratic behavior. By making sure the window is only on one monitor should fix it.

[Gus Evangelista CBN]

It appears deleting the WorkspaceConfig.xml also fixes Mercury Transmit problems to a 2nd or 3rd monitor.

[AnimoMotion]

Worked for me too, Dual display, did this and worked perfectly!

Cheers!

Dave

[metalvinny]

This is still an issue in CC 2017 and this solution still works! THANK YOU!

[ian_son_of_john]

Hey thanks so much! This was driving me nuts and was instantly fixed by your suggestion.