-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
action to send midi data to selected track #386
Comments
From maria...@mariannerobinson.com on October 11, 2011 21:51:37 Sysex for instance. I've seen this mentioned a few times. Conceptually picture a grid. |
From lewis.sc...@gmail.com on October 18, 2011 09:40:56 as i was attempting to illustrate in my original post, one would want to send notes/cc data to control settings on external hardware.- |
From a...@amcms.org on October 18, 2011 13:40:12 +1 - I'd really like this functionality to. Basically I'd like to send a midi note message to a midi output. This way I could control presets on RME's TotalMix. |
From jeffos...@gmail.com on October 19, 2011 11:15:15 hey guys, this is doable but a making custom JS effects would be straight forward (and there sould be some VST in the wild that propose such features.. for ex: ReaControlMIDI can send custom SysEx messages - on playback start though) |
From lewis.sc...@gmail.com on October 19, 2011 11:41:04 yes, definitely, but js/vst wouldn't be able to be used in custom action chains/assigned to hotkeys... |
From jeffos...@gmail.com on November 02, 2011 13:36:51 ok, I added the flowing stuff in r617 (will be available in the next SWS version): Added media file slot actions: there's no GUI for media file slots but you can define them just by running the "Play media file in selected tracks" action: a file browser is displayed if no file is defined for this slot. Media file slots are saved in the S&M.ini file in the section [MediaFiles]. I think this reply this reply to this FR: you can define your own .mid file slots. It is a bit more opened as it will also work with audio files (wav, wavpack, etc..) Status: Started |
From lewis.sc...@gmail.com on November 02, 2011 13:45:36 ooohahah wow, this is even better than i had originally planned, jeffos...i think you mighta just made a bunch of people very happy. might be a while before i can test this but i'll get back to you. and yes, i think it's safe to say this FR has been serviced, x100. |
From musicbynumbers@gmail.com on November 04, 2011 13:51:07 Errr.. how do you STOP the file playing guys? ;) I just added a pink noise sample to slot 1 for quick k-metering setting up but was hoping there would be a "stop" action too! ;) lol Was going to create a "cycle action" for it. |
From jeffos...@gmail.com on November 08, 2011 09:25:00 A GUI will be soon available for medial file slots (i.e. new item "Media files" in the top right dropdown box of the Resources view) Status: Done |
From jeffos...@gmail.com on November 10, 2011 14:15:05 hey Matt!? can you delete your 3 last comments about find/replace, I copied them: will paste & reply them in a more appropritate issue.. Thanks! |
From musicbynumbers@gmail.com on November 10, 2011 19:28:53 ok :) sorry! |
From lewis.sc...@gmail.com on September 24, 2011 04:34:10
i have been dying for actions that could send MIDI notes or midi CC messages into a selected track.
NOTE: timing is not an issue for this purpose, as the messages are conditional/control oriented in purpose.
use:
by sending to a track that contains a hardware midi output or a vst, you could build macros that not only control Reaper but also midi controlled equipment...setting up conditions and optimizing workflow. this type of integration would be extremely powerful.
if this is inclear, please allow me to clarify or give some examples of use...
instead of having thousands of midi actions (all note ons, note offs, cc messages and values) i'm picturing a reaconsole type of scenario where the user must input what messages he would like sent and call them accordingly...
best wishes
nym
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=386
The text was updated successfully, but these errors were encountered: