Jump to content

Axe Edit III disturbs mouse, can you repro...?


Panu Pentikäinen

Recommended Posts

Has anybody else seen this? If you have Fractal Audio Axe Edit III running while using Cakewalk, it somehow disturbs mouse double-clicks and resizing events: more than half of the double-clicks are not registered in Cakewalk and if resizing for example track height, it may jump suddenly to unexpected height. As soon as Axe Edit III is closed, mouse works perfectly again.

I do not see this behavior in other programs like Firefox, Adobe Audition, Adobe Premiere, After Effects or Microsoft Word while Axe Edit III is open.

Can anyone repro this?

My mouse is Logitech M185.

EDIT:  My Axe FX 3 MK II is connected via USB to PC but for audio I use AES/EBU. USB is for the firmware updates only.
EDIT2: When starting Axe Edit III, mouse works OK while user presets and cabinets are read. Problem arises when Axe Edit III has completed all initializations and is ready for use.
EDIT3: I tried other free USB 2.0 and 3.0 slots for the Axe FX III MK II USB cable. No effect.
EDIT4: Video track height: same issue but Cakewalk fixes height immediately after the glitch unlike when resizing track height.
EDIT5: Issue is in the busses, too.
EDIT6: I think this issue is in the system level: when resizing windows of many other programs, they may too blink momentarily to wrong height but window size jumps back to mouse location when the next mouse location is read.  I suspect  Axe FX III's USB driver is the cause for this problem.
EDIT7: Changed title.

Edited by Panu Pentikäinen
Link to comment
Share on other sites

47 minutes ago, Matthew Simon Fletcher said:

That's very perculiar - I haven't got Axe Edit III but regularly use Axe Edit II/Calkewalk and haven't seen that behaviour.

Interesting... What is your mouse model?

Maybe there's something wrong in the Logitech drivers in my setup although all other programs work just fine. Also the older Axe Edit for AxeFX II did not have this issue.

  • Like 1
Link to comment
Share on other sites

Thats weird. Is there a component from axeedit running in Cakewalks process space via a plugin or something?
Otherwise mouse handling from another app shouldn't affect messages sent to Cakewalk. Its possible that its a mouse driver issue also.
You could run Spy and have it watch mouse messages sent to the Fractal app and see if there is any activity there (There shouldn't) while operating the mouse in Cakewalk.

Link to comment
Share on other sites

19 hours ago, Noel Borthwick said:

You could run Spy and have it watch mouse messages sent to the Fractal app and see if there is any activity there (There shouldn't) while operating the mouse in Cakewalk.

I tested Spy last night but for some reason I was not able to log messages.
Might need some help as I've used that tool last time a decade ago..

Link to comment
Share on other sites

1 hour ago, Panu Pentikäinen said:

I tested Spy last night but for some reason I was not able to log messages.
Might need some help as I've used that tool last time a decade ago..

There's actually a 64 bit version of Spy++ in the same folder as the 32 bit version. Visual Studio opens the 32 bit one by default (via Tools -> Spy++).

Since CbB is a 64 bit application, you need to run the 64 bit version of Spy++. On my PC it's here:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\Tools\spyxx_amd64.exe 

Give that a go and you should be able to view messages.

  • Thanks 1
Link to comment
Share on other sites

Spy++

No messages going to Axe Edit while mouse is inside Cakewalk.exe.
Here is a snippet from mouse movement log while I was resizing track height. Line 000678: mouse xpos and yPos values are corrupted. This causes the track height resizing problem but it does not tell where the bug is (somewhere in Kernel?) . @Ben Staton & @Noel Borthwick, have you any idea..?

Note to followers, just in case... This bug is not in Cakewalk but it makes using Cakewalk challenging.

 

Quote

<000670> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:300 yPos:92

<000671> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:300 yPos:92
<000672> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:300 yPos:87
<000673> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:300 yPos:83
<000674> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:300 yPos:80
<000675> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:300 yPos:80
<000676> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:300 yPos:78
<000677> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:300 yPos:76
<000678> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:1587 yPos:-201
<000679> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:300 yPos:74
<000680> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:299 yPos:73
<000681> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:299 yPos:72
<000682> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:299 yPos:71
<000683> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:299 yPos:70
<000684> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:299 yPos:70
<000685> 0000000000011C84 P WM_MOUSEMOVE fwKeys:MK_LBUTTON xPos:299 yPos:69

 

 

Edited by Panu Pentikäinen
Link to comment
Share on other sites

Wow thats a bizarre issue. It could be hardware or driver related. I have no idea how invalid mouse messages could be sent otherwise. Are you running a multi monitor setup as well?
I see in your video that you have two monitors. Are they identical resolutions and have you set one up in windows to be higher than the other? Also to troubleshoot see what happens if you tile the axe fx on the same monitor as CbB, or flip cakewalk to the right monitor.
 

Link to comment
Share on other sites

Dual monitor setup with NVIDIA GeForce 1070.

Mouse works perfectly whenever Axe Edit III program is not running - problem starts after Axe Edit III has completed initialization on startup and is ready to use. And mouse behavior is healed as soon as I close the program or turn off power from Axe FX II MK 2. 

I tried to switch AxeFX and mouse to different USB ports - no effect. Also two different mouses (Logitech and Microsoft) tested - no effect.

Next I will test if problem persist with Remote Desktop Connection and old PS/2 mouse.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...