script - RPR_GetSetTrackState trashes fx info?
|
07-11-2010 01:17 AM
|
|
Human being with feelings
|
|
script - RPR_GetSetTrackState trashes fx info?
using RPR_GetSetTrackState appears to stomp on vst info
hi there,
i had a shot at a script to automatically add track icons to a project. i've got it working, but running a diff on the project before/after shows that a lot of stuff is disappearing.
i'm using python 3.1.
basic method:
* reading raw track data using RPR_GetSetTrackState
* modifying the track data
* writing back using RPR_GetSetTrackState
if i write a function that just reads and writes back the track data without editing or changing anything, it gets trashed pretty bad when the track data is large, even if i set a huge read buffer as the third param (verifying that the input buffer is large enough).
i've attached a script and a project that reproduces this. running the script will mangle the project (it gets 90% smaller!).
it only seems to affect VSTs with lots of embedded data (e.g. romplers/samplers). plugs like ReaEQ come across fine.
also, note that the reascript spec seems a bit wrong wrt the GetSetTrackState function.
|
|
Issue Details
|
Project
Deprecated REAPER issue tracker
Category Arcana
Status Unconfirmed
Priority 5 - Medium
Affected Version 3.63
Fixed Version (none)
Users able to reproduce bug
0
Users unable to reproduce bug
0
Assigned Users
(none)
Tags
(none)
|
|
07-12-2010 09:32 PM
|
|
Human being with feelings
|
|
|
|
All times are GMT -7. The time now is 02:00 AM.