You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
BR_TrackAtMouseCursor() doesn't support the new pinned tracks in TCP #1935
changed the title [-]mouse_tr = r.BR_TrackAtMouseCursor() doesn't work anymore with Reaper[/-][+]BR_TrackAtMouseCursor() doesn't support the new pinned tracks in TCP[/+]on Apr 4, 2025
The best workarround would simply for the function to now use reaper native API GetThingFromPoint if the function is available (reaper API function check)
Activity
[-]mouse_tr = r.BR_TrackAtMouseCursor() doesn't work anymore with Reaper[/-][+]BR_TrackAtMouseCursor() doesn't support the new pinned tracks in TCP[/+]X-Raym commentedon Aug 24, 2025
Confirmed 😮
Moyf commentedon Nov 14, 2025
Some clues: The height of the pinned tracks appears to add an additional offset to the cursor position.
#1987 (comment)
acendan commentedon Jan 30, 2026
+1 and easy to repro. Big workflow blocker for some folks using my scripts.
2026-01-29.09-33-47_hb.mp4
Infrabass commentedon Feb 10, 2026
+1, both functions "BR_TrackAtMouseCursor" and "BR_GetMouseCursorContext_Track" are affected by this.
andrummer commentedon Apr 11, 2026
Just faced an issue, and found out that offset is gone when non pinned tracks are at minimal height :))
Might be there is a possible workaround on script side?
used _BR_CONT_PLAY_MOUSE_SOLO_TRACK
https://github.com/user-attachments/assets/bb78c46e-1c78-4682-99e5-923b98d0b282
X-Raym commentedon Jun 23, 2026
The best workarround would simply for the function to now use reaper native API GetThingFromPoint if the function is available (reaper API function check)