Both MMB and LMB interactions have the issue, and sometimes the only way to get the par val to not continue changing with cursor movements is to alt+tab over to another program. When modulating a parameter with the value ladder the cursor position continues to modulate the value after mouse button is released. I usually ignore it, but at the moment I have a lot of parameters to fine tune in small increments over large ranges and it’s driving me crazy, (trying to find sweet spots in a complex system… I guess this is why someone - teflonjf maybe - made those speed/jog sliders a few years ago.) I have been experiencing very similar bugs for a while across several 2020 builds and different PCs. It’s almost always fixed by taking the TD window in question out of, and back into focus. TLDR: Honestly this is not nearly as much of a nuisance as the previous version of this bug, and it’s probably related to having (at least for me) too many TD windows open and TD “missing” the ‘mouseUp’ message coming from the mouse. Clicking on the Windows desktop (often just with LMB, sometimes you actually have to click with MMB) and then clicking back into TD will often fix it.ĭespite that, occasionally at the tv studio this would not fix it and I had to restart that TD process, but I can’t say why until I have access to test on that computer again (not through AnyDesk) That’s always happened for as long as I’ve used TD… But recently sometimes after that, if the immediate next action is to attempt to use MMB (or even your mac friendly “holding down LMB” method :–) the value ladder will not pop up - almost as if the window is not in focus, or maybe TD is not expecting two “mouseDown” triggers in a row from the mouse. ![]() I’ve gotten very used to giving the mouse a little wiggle after every window move just to see if it’s free and if not, a couple clicks later it will let go. I regularly have a couple TD processes running, sometimes with multiple perform / network editor windows open (I know I know bad practice - sue me) and occasionally I beleive TD “misses” the “mouseUp” trigger when I’m done dragging and thus the perform (or sometimes network editor) window will continue following the mouse cursor even when the mouse button is released. The only real clue I have is that it seems to coincide with whenever a perform window gets stuck to my cursor after attempting to drag said window by it’s titlebar. I had it happen semi-regularly on a media server that I have running at a TV studio, but they’re on hiatus right now so I can’t try it out there. ![]() I can move this to a thread in the bug forum if need be, just wasn’t sure till now if it was a bug or a No, whatever the issue is now, it’s much harder to pin down / re-create than before. And Actually I just now tried using it over a remote desktop software (AnyDesk, not TeamViewer) and it unfortunately does not negate the “value ladder aggressively accelerates” limitation that has always been present when working over most remote desktop solutions (as mentioned here TeamViewer & Middle Mouse Slider broken) I am using Windows 10 LTSC Version 1809 Build 17763.1131Īnd this happens on both local or remote usage. builds (aka bug is not present in 2019.20700, but is preset in 2020.20020) ![]() So I went back and tested the last five versions, and it shows up in all the 2020. As soon as I click somewhere in the network grid, the cursor returns to normal. It still always shows the cursor outside of TD, or even in the Palette, but not the network editor or parameter panel. ![]() I have found that the ONLY time the cursor disappears when I release MMB is when I release while the cursor is over the border of the parameter pane (when the cursor switches to double-headed sideways arrows) I MMB Click and start dragging, but certain elements start highlighting or changing the cursor when I pass over them.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |