-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support FX renaming #240
Comments
Note that FX can also be renamed in the plug-in selection window, which makes the state chunk appear as follows;
Therefore, we can not rely on the first string - we could use the filename. Filename could obviously change too, but I think that's the least likely to change (and users should probably expect some issues if they start renaming essential components). The ideal solution is to compare plug-in IDs. This is where #122 would certainly help. |
If the user renames the plug-in in the plug-in selection window, then this will also break import since |
REAPER now allows the user to rename FX, which is going to mess up any calls to;
int TrackFX_GetByName(MediaTrack* track, const char* fxname, bool instantiate )
bool TrackFX_GetFXName(MediaTrack* track, int fx, char* bufOut, int bufOut_sz )
There is currently (at v6.74) no API function to get the original name rather than the user-specified name. It can however be derived by parsing the tracks state chunk using;
bool GetTrackStateChunk(MediaTrack* track, char* strNeedBig, int strNeedBig_sz, bool isundoOptional )
This will return something like;
Care needs to be taken with quote marks. In this case there were 5 EAR Object plugins (to understand quotes and escaping). They were named;
...with the final one having no custom name.
The text was updated successfully, but these errors were encountered: