eptheca Posted April 8, 2015 Report Share Posted April 8, 2015 is it a way to have the SEQ V4 send note off (80) in stead of note on (90) with 0 velocity? I have a synth that doesn't care about velocity, and therefor triggers twice on each note Quote Link to comment Share on other sites More sharing options...
Elektruck Posted April 9, 2015 Report Share Posted April 9, 2015 (edited) I think I suffer from the same issue. I have a WTPA2 8-bit sampler wich I can play manually, or by midi. Manually works great but I can't get tight loops of e.g. 4 bars. Midi from ableton works also great, I can record really tight 4 bar loops, and by playing the loop an octave higher it doubles speed, great machine. But if I play it from my SeqV4 I can record music (it starts recording on CC#3) but when I play the sample with notes it only triggers the sample to play, but it doesn't stop at the end of the note. It does stop at the end of the notes comming from Ableton. I didn't understand yesterday but as I read your/this thread now I think this is the issue. I also would like note-offs, so any help or comments appreciated! Edited April 9, 2015 by Elektruck Quote Link to comment Share on other sites More sharing options...
TK. Posted April 11, 2015 Report Share Posted April 11, 2015 I added this request to the wish list, but the implementation won't be so easy because there are many implications in the firmware for sending NoteOn with velocity 0 to turn off the note. Changes at many places will be required, especially in the MIDI scheduler, sequencer core, live and recording function, MIDI router, etc... (just thinking loudly): it might be easier to add a "modification" option directly in the MIOS32 kernel, but SW wise it would be a dirty patch which should normally be prevented to avoid unexpected side effects in later developments. However, did you already request a firmware fix from the manufacturers of these synths? Because they don't work according to the MIDI specification. I guess that some other devices can't control these synths correctly as well. In addition, Note Off events will disturb the "running status" feature, hence you will notice some additional latency if MBSEQ would switch between Note On/Off. Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
eptheca Posted April 11, 2015 Author Report Share Posted April 11, 2015 OK. Thanks TK. Forget about it, it sounds like too much work, and if Note On, Velocity = 0 is the standard, we'll stick to that. For my synths, they are custom / home made stuff. I will try to change the firmware in them in stead. Quote Link to comment Share on other sites More sharing options...
kpete Posted April 12, 2015 Report Share Posted April 12, 2015 From the first post I was wondering if you were using one of those synths that would send a Midi All Notes Off message for the last note rather than just a note off message. Your last post answered that question eptheca. Quote Link to comment Share on other sites More sharing options...
Elektruck Posted April 13, 2015 Report Share Posted April 13, 2015 I agree with eptheca, I'll stick to the midi standard and ask the WTPA2 forum for a solution. Cheers, Roel Quote Link to comment Share on other sites More sharing options...
Elektruck Posted April 14, 2015 Report Share Posted April 14, 2015 After studing the WTPA2 manual again I found this sentence: "WTPA is fully capable of handling and generating running status messages (and interpreting NOTE ON messages with a velocity of 0 correctly as NOTE OFFs)." So my problem needs a different solution, any idea? Cheers, Roel Quote Link to comment Share on other sites More sharing options...
ilmenator Posted April 14, 2015 Report Share Posted April 14, 2015 Roel, are you sure you are running the same firmware the manual refers to? (I don't have one of these units myself, but differences between manual and actual firmware versions are a common source of confusion). Quote Link to comment Share on other sites More sharing options...
TK. Posted April 14, 2015 Report Share Posted April 14, 2015 Especially if this feature (which should be commonly supported by all MIDI devices) is explicitly mentioned in the user manual it could be related to a problem in earlier firmware versions... ;-) Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.