Would I e.g. be able to do something that I currently would need to use a Midi CC message and send it via MidiToReaControlPath to trigger a script that is assigned to that CC ? Maybe I now could do a "defer" script that polls a gmem location and the JSFX will set seam.
I don't understand the question, but the answer is almost certainly yes.
The way video processors deal with tracks/items/etc might be causing you some problems. You might need to review the help text about how to enumerate/navigate the list of video inputs, but here's a quick explanation:
You can't get the name of a track unless it has a video processor on it at the track level.
Input 0 is the first input available to the processor. This could be the previous FX in the chain, or if a track FX, it could be the previous track, or an item on the track (or a take FX on the item on the track, etc).
If you want to get the output of the previous track that contains a video item/processor/etc, you should query input_track(0). If you want the second track that contains one of those, use input_track(1).
There are other functions to navigate the inputs.
Remember, any item/track that doesn't have any video processors/video files is effectively ignored (except when using input_track_exact() etc).
You can load whatever movie you want in replace of the .MOV file to test.
Track 1 "describe what is seen" has a processor which takes the first input (wherever it is), draws it, then draws the text that it gets from it over it.
At the start of the project, it reads from "item that is red", which is a MIDI item that has a video processor on it that generates red.
Then in the empty space between 2 and 3 seconds, there's no video processor on an item or the track, so instead it displays "green track", which has a video processor at the track level.
When it gets to the second item, which is a .MOV, it displays that, and uses the take name (since that take was renamed). Then between 4.5 and 5 seconds it goes back to green..
And the third item is just the same as the second item, only it has the filename of the .MOV in it (I didn't bother renaming that one). There's no way to actually get the filename, it just uses the take names.
I don't understand the question, but the answer is almost certainly yes.
The goal is to use the Reaper API by something that happens in the realm of the track FX chains (e.g. Midi messages). This is one of the main discussion issues in the many "Reaper Live usage" threads running in theses forums. Doing a single (timed) Reaper script maybe would be a cleaner solution than sending Midi CC messages to the Reaper Control Path and firing a bunch of Reaper Scripts with these.
I'll do a test once this update makes it into the released version (Or do you want me to test this right now ? Is there a documentation on this ? )
The way video processors deal with tracks/items/etc might be causing you some problems. You might need to review the help text about how to enumerate/navigate the list of video inputs, but here's a quick explanation:
You can't get the name of a track unless it has a video processor on it at the track level.
Input 0 is the first input available to the processor. This could be the previous FX in the chain, or if a track FX, it could be the previous track, or an item on the track (or a take FX on the item on the track, etc).
If you want to get the output of the previous track that contains a video item/processor/etc, you should query input_track(0). If you want the second track that contains one of those, use input_track(1).
There are other functions to navigate the inputs.
Remember, any item/track that doesn't have any video processors/video files is effectively ignored (except when using input_track_exact() etc).
You can load whatever movie you want in replace of the .MOV file to test.
Track 1 "describe what is seen" has a processor which takes the first input (wherever it is), draws it, then draws the text that it gets from it over it.
At the start of the project, it reads from "item that is red", which is a MIDI item that has a video processor on it that generates red.
Then in the empty space between 2 and 3 seconds, there's no video processor on an item or the track, so instead it displays "green track", which has a video processor at the track level.
When it gets to the second item, which is a .MOV, it displays that, and uses the take name (since that take was renamed). Then between 4.5 and 5 seconds it goes back to green..
And the third item is just the same as the second item, only it has the filename of the .MOV in it (I didn't bother renaming that one). There's no way to actually get the filename, it just uses the take names.