Replies: 3 comments 3 replies
-
Interesting!
Kind of ;-). @dtinth @hoffie and a few others worked on a JSON-RPC API. You can test it with the nightly or next release I mentioned in your other issue |
Beta Was this translation helpful? Give feedback.
-
That also sounds interesting! I found the json-rpc interface on the latest nightly you linked. Is there some documentation for that API? |
Beta Was this translation helpful? Give feedback.
-
Been awhile, but I've been revisiting the issue of "unnamed" audio files from Jamulus recordings. I just wanted to point out to anyone who stumbles across this, that the script I linked above can be used to convert audio file names after the recording is finished. Just convert the .rpp to yaml, pass the yaml to your favorite language, iterate through the tracks and rename your files. Also wanted to say thanks for the json-rpc interface! That will be very helpful for a project I'm currently working on. |
Beta Was this translation helpful? Give feedback.
-
I'm posting this with the intention of helping others like me who searched exhaustively for a way to programmatically access data related to Jamulus recordings. I'm not sure of the best place to post this, so apologies if I picked the wrong one. I'm happy to move/repost or whatever the moderators prefer.
I've been doing a lot of automation scripting of Jamulus server on Linux. One thing that's been missing for me is a manifest of each recording session in a well-supported format. The Reaper .rpp file has all the data, and it's structured in a sane way, but there's no easy way to programmatically access the data (at least none that I've found). Maybe someday Jamulus will export this data as xml, yaml, or json?
Meanwhile, I created a shell script to convert the .rpp data to yaml. From yaml, one can easily convert to json, xml, whatever, using your favorite libraries.
https://gist.github.com/ginjo/de9cf9397b28908c68a8947be219f237
Beta Was this translation helpful? Give feedback.
All reactions