View Single Post
Old 02-29-2024, 11:28 AM  
cfillion
Human being with feelings
 
cfillion's Avatar
 
Join Date: May 2015
Location: Québec, Canada
Posts: 4,979
Default

@schwa Could the track's "make lanes big/small" state be exposed in the API? The source of the slowdown is SWS repetitively parsing the track's chunk to read the first value of FIXEDLANES in an attempt to mirror how REAPER computes the maximum spacer size for that track: BR_Util.cpp:2264-2321.

Even better would be for the effective TCP spacer size to be directly accessible, so we don't have to chase future changes in REAPER... (But that wouldn't completely help because parts of SWS still need to be able to predict spacer size for a given (non-current) track height.)

Last edited by cfillion; 02-29-2024 at 11:50 AM.
cfillion is offline   Reply With Quote