|
Post by djlastnight on Aug 20, 2018 15:00:01 GMT
Is it possible to set up the profile so that it has multiple notes line up with the same input from the game's perspective? The game has hardcoded drum lanes, depending on the used profile (4,5 or 7). You can bind multiple midi signals to the same game function. For example <GREEN>49,9,0</GREEN> <GREEN>52,9,0</GREEN> <GREEN>55,9,0</GREEN> <GREEN>57,9,0</GREEN>
is a valid midi profile. To achieve this with PsMidiProfiler, you should create a custom profile. The game doesn't register most of my hits using the generated profile, despite all my hits being recognized by tool from this thread. It can find one hit every once in a while, but most of the time hits are ignored. Make sure you midi link the generated profile, not another one. If the problem persists, try to create new profile with "Detect Note off" option unchecked. It is not a bad idea to post your current midi profile. Thanks, dj
|
|
|
Post by reina on Oct 5, 2018 2:21:36 GMT
Hey, I got my MIDI keyboard working almost properly. It detects all the keys properly in your program with no problems at all, but once I press a key in-game, that key stays held down.
|
|
|
Post by djlastnight on Oct 31, 2018 19:30:28 GMT
Hey, I got my MIDI keyboard working almost properly. It detects all the keys properly in your program with no problems at all, but once I press a key in-game, that key stays held down. Sorry for the late reply. Can you try to edit your profile manually and set the cutoff values to 0 (if different). Ex: <GREEN>49,9,0</GREEN> - where 0 is the cutoff value.
|
|
|
Post by schmoo on Dec 4, 2018 17:14:05 GMT
Hey, I got my MIDI keyboard working almost properly. It detects all the keys properly in your program with no problems at all, but once I press a key in-game, that key stays held down. Sorry for the late reply. Can you try to edit your profile manually and set the cutoff values to 0 (if different). Ex: <GREEN>49,9,0</GREEN> - where 0 is the cutoff value. I've been having an issue with double hits with one of my cymbals, and in the profiler I can see the 2nd hit is of really low frequency. The sensitivity settings on my kit are of no help, so I took this latest post to mean I could add a custom cutoff value to any drum/cymbal. So I set it to 20, but then whenever it's hit under that value, it'll detect the hit in game, and then completely disable the cymbal until any other drum/cymbal is hit. Am I misinterpreting how the cutoff value is supposed to work or is this a bug? Im using v1.27. If this is not fixable within phase shift, is there any other software that could parse the midi before it gets to phase shift? Also a seperate issue, but I'm having real trouble trying to setup a double bass drum profile. I use a Roland HD-1 btw. So here's me playing open hihat twice, then hitting the left pedal and holding while i then hit the hihat again twice (now closed) [15:52:758] - ControlChange | 4 | Channel: 9 | Velocity: 0
[15:52:759] - NoteOn | 46 | Channel: 9 | Velocity: 40
[15:52:860] - NoteOff | 46 | Channel: 9 | Velocity: 64
[15:53:410] - ControlChange | 4 | Channel: 9 | Velocity: 0
[15:53:411] - NoteOn | 46 | Channel: 9 | Velocity: 31
[15:53:511] - NoteOff | 46 | Channel: 9 | Velocity: 64
[15:54:638] - ControlChange | 4 | Channel: 9 | Velocity: 81
[15:54:640] - NoteOn | 44 | Channel: 9 | Velocity: 124
[15:54:651] - ControlChange | 4 | Channel: 9 | Velocity: 127
[15:54:741] - NoteOff | 44 | Channel: 9 | Velocity: 64
[15:56:739] - ControlChange | 4 | Channel: 9 | Velocity: 127
[15:56:739] - NoteOn | 42 | Channel: 9 | Velocity: 61
[15:56:840] - NoteOff | 42 | Channel: 9 | Velocity: 64
[15:57:350] - ControlChange | 4 | Channel: 9 | Velocity: 127
[15:57:350] - NoteOn | 42 | Channel: 9 | Velocity: 59
[15:57:450] - NoteOff | 42 | Channel: 9 | Velocity: 64 So I setup my profile like this: <YELLOW>42,9,0</YELLOW>
<YELLOW>46,9,0</YELLOW>
<BASS>36,9,0</BASS>
<BASS>44,9,0</BASS> But then when I try to use it in game, if i hit the hithat with the left pedal down (what would be a closed hit), it triggers Yellow and Bass. Is it something to do with the ControlChange event? Is that what CC is? Any idea how to fix the issue? Final question, is there any way to get the steam beta? If I donated now would I get access? Is there a specific amount I'd need to donate? Edit : Seems like you had to of donated before or be a notable member? Please let me know if this isn't correct Thanks
|
|
|
Post by schmoo on Dec 10, 2018 17:11:33 GMT
I sort of solved the double bass issue, so I'll post it incase anyone else has a similar issue. The problem lies in the CC#4 (ControlChange ID 4) event as suspected, but afaik this event does not alter any other MIDI events, so it's up to whatever is reading it to interpret it. Phase shift is doing something weird and there is no way to prevent it. The solution is to stop the CC#4 event from reaching phase shift. To do this I used LoopBe1, which sets up a virtual MIDI input and output. Whatever I send to the output will come in through the input which I can choose on phase shift. Then a simple Pure Data (specifically Purr Data, an extended version with necessary functions) script to parse the midi input from the drumkit and send to the LoopBe1 output. The script looks like this: This takes in the drumkit midi input, splits in into it's different components, rebuilds it, then sends to the midi output. But as you can see, the 3rd node of midiparse is not connected to midiformat, as this is the controller message node. So no CC event will make it to the output. You set the in/out devices in Edit > Preferences I could also use Pure Data to solve the cymbal issue too, although it's become increasingly obvious the cymbal is in need of a repair as it's very loose. I would still be interested to know if the cutoff setting is bugged or I'm misinterpreting it, and also if the CC#4 event is bugged and if there is a way to disable it within phase shift.
|
|
|
Post by djlastnight on Dec 24, 2018 3:06:35 GMT
schmoo, sorry for the late reply, again! The thing that you misunderstood is how the CC#4 midi profile works. It needs ONLY ONE yellow note. The pedal position determines the hi-hat state. It is reported as ControlChange 4 (CC#4) midi event in range [0-127] and the game uses this data as follows: CC#4 [0-80] + yellow = open CC#4 [81-120] + yellow = sizzle CC#4 [121-126] + yellow = closed CC#4 127 = pedal (closed) The problem... You are currently using CC#4 profile, but your drum brain sends different note for a given hi-hat state. The solutions: A) Switch to real drums profile, which uses 4 yellow (c,o,p,s) notes. CC#4 events are completely ignored here. OR B) Keep using CC4 profile, but change your drum brain settings. It must send CC4 for the pedal position and a single yellow note. --- Also make sure your drum brain note off value (currently 64) is the same as your profile cutoff value (last changed to 0). This applies to each profile note. I would recommend value of 0. Hope this helps, dj
|
|
depaula
Chihuahua
I WANT TO DRUM!
Posts: 9
|
Post by depaula on Jan 26, 2019 12:24:22 GMT
Hey guys is there any way for you guys to help me out setting up my drums on phase shift? i've surfed through your forum in search of an answer and although i've found many interesting tips and programs i still haven't found a solution. I own an Alesis Dm8 and it works fine with third party vst's on my computer. Phase Shift recognizes my drums and everything (although the signal in midi link is always red) but whenever i hit the drums no notes come out. even when calibrating i can't get the drums to play the notes.. any advice on what might be happening? or maybe should i share some files with anyone? (ps. I used PsmidiProfiler to create my profile and i did it with no problems, all the other included programs tho gave me problems like button_data, etc..) Thanks for your time! Not sure if this is related but this is what happens whenever i open Midi_data.exe www.facebook.com/photo.php?fbid=2172575766124174&set=p.2172575766124174&type=3&theater
|
|
|
Post by jt4567 on Jul 2, 2019 0:09:19 GMT
it does not recognize my alesis nitro eveytime i try to use the app it says no midi devices found im using the ps3 midi adapter
|
|
|
Post by djlastnight on Jul 10, 2019 3:37:23 GMT
Hey guys is there any way for you guys to help me out setting up my drums on phase shift? i've surfed through your forum in search of an answer and although i've found many interesting tips and programs i still haven't found a solution. I own an Alesis Dm8 and it works fine with third party vst's on my computer. Phase Shift recognizes my drums and everything (although the signal in midi link is always red) but whenever i hit the drums no notes come out. even when calibrating i can't get the drums to play the notes.. any advice on what might be happening? or maybe should i share some files with anyone? (ps. I used PsmidiProfiler to create my profile and i did it with no problems, all the other included programs tho gave me problems like button_data, etc..) Thanks for your time! Not sure if this is related but this is what happens whenever i open Midi_data.exe www.facebook.com/photo.php?fbid=2172575766124174&set=p.2172575766124174&type=3&theaterI hope you fix your problem already. Sorry, I saw it just now. it does not recognize my alesis nitro eveytime i try to use the app it says no midi devices found im using the ps3 midi adapter Strange. Can you confirm that other apps detects midi device(s). Maybe you have some driver issues?
|
|
|
Post by sithy on Aug 27, 2019 11:41:22 GMT
L'application PS MIDI Profiler créera des profils MIDI pour votre instrument. C'est facile a utiliser. Tout ce que vous avez à faire est: -choisissez votre midi dans l'appareil- choisissez votre type d'instrument -détectez toutes les notes une par une -cliquez sur le bouton générer -copier et collez le nouveau profil dans midi_profiles.ini J'espère qu'il vous plaira. La version actuelle est toujours en version bêta, alors n'hésitez pas à poster vos suggestions et vos rapports de bugs.
|
|
|
Post by sithy on Aug 27, 2019 11:43:02 GMT
Bonjour, j'ai un problème avec l'application MIDIProfiler. J'exécute toutes les étapes jusqu'à ce qu'il soit nécessaire de générer le profil MIDI. Je reçois le message "La création de profil Midi a échoué. Toutes les notes n'ont pas été définies" que dois-je faire?
Merci
|
|
|
Post by sithy on Aug 27, 2019 11:44:42 GMT
L'application PS MIDI Profiler créera des profils MIDI pour votre instrument. C'est facile a utiliser. Tout ce que vous avez à faire est: -choisissez votre midi dans l'appareil- choisissez votre type d'instrument -détectez toutes les notes une par une -cliquez sur le bouton générer -copier et collez le nouveau profil dans midi_profiles.ini J'espère qu'il vous plaira. La version actuelle est toujours en version bêta, alors n'hésitez pas à poster vos suggestions et vos rapports de bugs.
|
|
|
Post by sithy on Aug 27, 2019 11:44:56 GMT
Hello, I have a problem with the MIDIProfiler application I execute all the steps until when it is necessary to generate the MIDI profile I receive a message "Midi profilecreation failed-not all notes were set" what should I do ? thank you
|
|
erxer
Chihuahua
Posts: 12
|
Post by erxer on Aug 27, 2019 15:38:53 GMT
Hello, I have a problem with the MIDIProfiler application I execute all the steps until when it is necessary to generate the MIDI profile I receive a message "Midi profilecreation failed-not all notes were set" what should I do ? thank you The midi profiler requires all of the notes to be set. When you (for example) don't map the bass pedal, it will give you that error. If you don't have enough drums on your drum kit then select a different style of drums to map to.
|
|
|
Post by underachiever on Dec 17, 2020 22:34:19 GMT
I have the following error: midi device could not be started! MIDI_ERROR_NOMEM
But the program can detect the name of my module (alesis nitro). And I've been able to create profile with the program in the past.
|
|