Have a look at it. Currently there are four scripts. A fifth one is in the works. The functions file has zip/unzip wrappers around info-zip which does the job. There might be other code you can use as well. The xrns2midi script written by Bantai has some inspriring stuff. All of the aforementioned is PHP.
I guess that means I’ve become a healthy fluffy teddybear
I’ve decided to go with the XRNS-PHP frontend, and it made for a really fast and easy way to develop the tuning app. Thanks to everybody involved with streamlining Renoise XRNx development !!
The alpha version 0.1 can be downloaded from this location (XRNS frontend with my script added): http://oscillity.net/microtuner/xrns-php%200.1.zip
It successfully translated all *.tun files I threw at it, but if you fare otherwise, please tell me. Version number is 0.1, so there is room for improvements and bug fixes.
Edit: Download Scala, and the Scale Archive if you need tuning files (there’s also a guide as to how to export *.tun files on their website) . Lots of plugins support the format as well, so a quick search on your harddrive might reveal some additional tunings
That was part of the reason, the reason for the real hanging is that the xrni folder in the temp folder wasn’t cleaned up after it failed to find the flac files, so when doing the second attempt the script hung in spite of what extension was set. Only after manually deleting the xrni folder from the temp folder and renaming the .flac extension to .ogg the script worked.
I am back, and have continued to develop the micro-tuning script.
Here is a question for Taktik, or anybody who know more than I do about the .xrni format:
Version 3 of the Renoise instrument format has a tag associated with each sample. How is this implemented in the software? Should I ignore it, and simply look for any sample whose filename match the tag, ending with either “.flac”, “.ogg” or “.wav” (which is how I’ve implemented it right now) ?
BTW: I would like to join the developer group on sourceforge. My account name is danoise, user name Bjorn Nesby
The way it’s now is correct. The filenames in the document are the original samples filenames, which are currently only used for undo/redo: If they are invalid (no longer present) Renoise will backup the sampledata before applying a destructive sample action, else the sample is simply reloaded again.