View Single Post
Old 07-31-2017, 12:14 PM   #15
lb0
Human being with feelings
 
Join Date: Apr 2014
Posts: 3,111
Default

Ok - at first - it appears the SetTrackStateChunk may not suffer the same limitations as the GetTrackStateChunk.

So I'm going to try out using the GetTrackChunk from the top of this thread (which works fine and brilliantly ) alongside the standard reaper.SetTrackStateChunk which seems to write back overly large chunks ok (in my quick limited tests).

If this is the case - then all should be good for my purposes

However - it should probably be mentioned (as I have) - that the SetTrackChunk function above using the SNM API calls can do strange things to GUIDs


EDIT - UPDATE:

Yep the native reaper.SetTrackStateChunk handles the large >4Mb chunk strings fine. (phew!)

So I would say go with the GetTrackChunk function provided at the top of this thread to replace reapers function - but stick with reaper's native settrackstatechunk function if you plan to do any reordering/removal of plugin data to avoid messing with the FXIDs.
__________________
Projects - Reascripts - Lua:
LBX Stripper | LBX Chaos Engine | LBX Floating FX Positioner | LBX SRD Smart Knobs
Donate via Paypal

Last edited by lb0; 07-31-2017 at 02:29 PM.
lb0 is offline   Reply With Quote