Soundshaper doesn t read MIDI files

[Phoenix cat]

I try with TOOLS>MIDI TO SEQ and select a .mid file and I got this message "Failed to execute mf2t.exe". And I cant find documentation about what is posible with mid files. What is happening? what is possible with CDP, with a midi file?

[j_p_higgins]

There is some info on this in this thread here: https://unstablesound.net/cdpforum/index.php?topic=203.0
Seems it has been having some issues and is being considered for removal.

mf2t doesn't seem to have documentation on the CDP website that I can find but it is an adaption of this software: https://github.com/reinierdevalk/mf2t-t2mf

Its intended use in CDP seems to be to take a midi file and use it to generate a sequence file (see: https://www.composersdesktop.com/docs/html/filestxt.htm#SEQUENCEFILES ). I don't know of any other cdp processes that accept a midi file as input but there might be some I am unaware of!

[simonk]

Apart from the (currently) problematic use in Soundshaper

I believe midi files can be used for input to Tabula Vigilans (tv) or ProcessPack
More info here:
https://www.composersdesktop.com/pdf/tvinfopgnew.pdf

https://www.composersdesktop.com/interfaces.html

[Phoenix cat]

thanks, I will look into that links

[Robert Fraser]

I try with TOOLS>MIDI TO SEQ and select a .mid file and I got this message "Failed to execute mf2t.exe".

.

Thanks for reporting this. I'll look into it.

[Robert Fraser]

I try with TOOLS>MIDI TO SEQ and select a .mid file and I got this message "Failed to execute mf2t.exe".

Hi Phoenix,
I think this will be a Windows message because it couldn't find mft2t.exe. Soundshaper currently looks for mf2t in a subfolder of Soundshaper called BIN (although I've changed that for the next release to _cdprogs, because it's also in there along with all the other software). The .txt output of mf2t is put in the same folder as the .mid file itself, as is the converted .seq file. So it might make sense to copy the .mid file first to the Sequencer subfolder of your user folder (i.e. TXT\Sequencer) so that it's easy to load the .seq file.

Before running Sequencer (i.e. CDP EXTEND SEQUENCE2) you should take a look at the .seq file (which is a text file) as it has a header defining a number of input sounds: e.g. 60 60 60 will need three separate input files. You can load or copy these to different rows in Soundshaper. (Even if they sound the same, they'll have different names, so CDP won't object.) Also, the Sequencer program can take a while to run, so be patient. As an alternative, it could be worth getting your MIDI file to 'play' a free sampler program.