Open Levitanus opened 1 year ago
Considering Nudge I'm wondering in exact numbers for NudgeUnits
.
Here is original API documentation:
nudgeunit: 0=ms, 1=seconds, 2=grid, 3=256th notes, ..., 15=whole notes, 16=measures.beats (1.15 = 1 measure + 1.5 beats), 17=samples, 18=frames, 19=pixels, 20=item lengths, 21=item selections
But, when I continued a sequence from 256th to 2th — I've finished on the literal 10
, but not on the 14
as I would expect from docs.
I've never used nudge feature, so, here my expertise is out)
Well, not as straight, as I desired...
get_set_project_info_string_set
constantly returns false in any language. OK.get_set_project_info_string_get
fails in test with category TrackGroupName(x)
. But it works in my working instance of Reaper, when built from my extension.I feel, that AudioAccessor
commit is OK. But, for the case, I put it here: not as straight, as typing arguments in right order.
Here are functions I'm not sure in. Which are better to discuss.