Timofey Kazantsev
Timofey Kazantsev
OK, finally, I've launched Reaper inside and connected to it via VNC. So, there is no real limitation in making test stand based on Docker. Also, I've thought about test...
One more *pro* to the «test-stand» approach: now I'm refactoring the „send“ branch for disconnecting it from the SWS API. And, suddenly, native `RPR_GetTrackSendInfo_Value(track.id, category, sendidx, 'P_SRCTRACK')` returns the pointer...
It seems, that idea is not so scary: GUI apps can be run in CI environment with `xvfb` package as GUI (X) server, and `jack -d dummy` as sound server....
Hi! The matter is FX functions (for track or take fx) are generated at the import time. Fixed their generation by the [commit](https://github.com/Levitanus/reapy-boost/commit/5d69bbe3ce9f129e96f1e2a66dd5fc3bc44fa8d8). Also, You can use my fork (`pip...
well, never faced this before... Maybe this is some sort of firewall... But on such many systems.... Can't imagine what is wrong Maybe a problem is the Reaper is already...
> In the `Note` object : *`Note.beat` to get the absolute beat of a note (not relative to its current measure) *`Note.measure` to get the measure in which the note...
I feel, if You split this PR into the couple (one with import mesia, one with MIDI) — @RomeoDespres will be able to include something after #81 is merged. Anyway,...
Romeo, how about theese?)))
Thanks, Just it was really connected to the 0.6.0 release, so I was maybe surprised more than should by the 0.7.0 🤐
You're probably right :)