![]() ![]() ![]() Warrior is just an easy start due to the extra 1 Stamina. I personally found the huntress most difficult to play, Warrior and Rogue were equally easy - Mage wasn't too bad either. I am as well curious about similar software for MIDI manipulation, preferably released Open Source.Īnother idea would be to solve this with a nice Max4Live device.I think it's more dependant on what items you have than class after a few playthroughs - before getting a new phone I had unlocked the huntress (by using a Rogue) and gained books on the three characters except the huntress. ![]() If you find a way to code this all into one script or even solve the message manipulation without AppleScript, just using a combination of MidiPipe’s other modules, please leave a comment, I would love to here! Also MidiPipe is a rather dated piece of software and is not in active development anymore. I even sometimes use it for live finger drumming. So far it doesn’t seem all this introduces latency that delays the drum hits noticeably. In MidiPipe set the two “Midi Out” modules to the port your Volca is connected to. In your DAW you now have to send the output of the MIDI track you use for triggering the Volca to “Midi Pipe Input1”. set channel to (( item 1 of message ) mod 16 ) # 144 is Note-On on channel 1 set first_byte to ( channel + 144 ) set note_no to ( item cnt of note_list ) set note_val to ( item 3 of message ) #display dialog "CC to note -> ch:" & channel + 1 & ¬ " note_no:" & note_no & " CC_no:" & CC_no & " cnt:" & cnt set ( item 1 of message ) to first_byte set ( item 2 of message ) to note_no set ( item 3 of message ) to note_val # we found the CC_no and translated to note, nothing else to do exit repeat end if set cnt to ( cnt + 1 ) end repeat return message end runmeĭownload my MidiPipe config file and if you not already have, MidiPipe. # translate note to CC # comment out for debugging from AppleScript editor #runme( set cnt to 1 repeat with CC_no in CC_list #display dialog (item 2 of message) if (( item 1 of message ) ≥ 176 and ( item 2 of message ) is ( CC_no as integer )) then # returns 0 for channel 1, 1 for channel 2, etc. The second AppleScript Trigger translates the MIDI CC messages back to Note messages and sets their velocity correspondingly:Īnother Alist, here we should see a MIDI CC message followed by a MIDI Note for each drum triggered:Īnd finally everything is sent out to the same MIDI port as above: MIDI CC messages are sent to Midi Out port as well as passed through to the next module: The first AppleScript Trigger translates the Note messages to MIDI CC messages (full code is below pics): The AList modules are for debugging, they show how the MIDI messages look like at the current point in the pipe: We only want to manipulate MIDI Note and Control Change messages. ![]() The settings of the modules in detail, obviously this is the input: You can see that I use two AppleScript Triggers and also two MIDI outs: The right half of MidiPipe’s window shows the modules the messages are flowing through. I couldn’t find a way to code this all into one AppleScript so my solution looks like this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |