I ve read this proposition somewhere but i can t find it… sorry but Yeah export midi file without external plugin, directly from renoise pleaaaaaaaase… please please please … pleaaaaaaase
Like that i can load it in my sampler directly, that would improve my workflow for preparing live acts so muuuuch
It s so hell to compose melodies on hardware sequencers…
I’m guessing you already knew that and you still want it “inside” renoise, but I fail to see why. Probably took longer to post with “rolling eyes smilies” than to figure out the above two tools.
i am working on hardware… and i am composing on renoise
with thoses tools i have to save my file, open with the plug then export
if it s inside i am making a melody, i would clik on export directly on my hardware memory (g: at home ) like that i can test and modify really fast
i m working on quite old hardware that s why they don t have computer interface to improve composition, as renoise is the best sequencer ever, i like to use it nearly as fast as if it was a part of my hardware.
… ok that might interest just me maybe
anyway i just ask and i promise i won t use rolleyes anymore
i Tried this plugin but it doesnt export to midi corectly according to instrument, i tried to setup every instrument by its chanell and program number but half of the song converts only to piano (program 1)…
I have been trying to use both .NET and the XRNS-SF tools to create MIDI files with little success. the .NET tool seems to make empty MIDI files … and the XRNS-SF file says that it has run the script successfully but then no MIDI file shows up.
Here is the XRNS file I’m trying to convert. I’m using 1.9.1 BTW.
I’m not sure what I’m doing wrong but I can’t get this file to convert to MIDI. I’ve tried specifying different target folders with no luck. I haven’t had problems converting other XRNS files, but with this one I run the XRNS2MIDI and nothing happens. It’s very frustrating.
I’ve found the cause of this error. It’s a windows limitation… the maximum length of path including filename can’t exceed 260 chars in non unicode applications, which happens in your case. Instrument 03 has a very long name for the instrument and sample name, which would result in an extraction path similar like this on a standard windows system:
c:\Dokumente und Einstellungen\Username\Lokale Einstellungen\Temp\xrns2midi_36eca5744992b2bb01b53611ec33c2dd_Track01\SampleData\Instrument03 (UWT01 49 Bathtub - Bath Tub Filling Slowly, Underwater)\SampleData\Instrument03 (UWT01 49 Bathtub - Bath Tub Filling Slowly, Underwater)\Sample00 (UWT01 49 Bathtub - Bath Tub Filling Slowly, Underwater).flac
That’s way over 300 chars and the unzipping process fails because of this. You can manually overide this by creating manually a new temp folder eg. “C:\Temp”, then open xrns2midi.php in the scripts subfolder from the frontend, go to line 58 and change it from: