MIDI not controlling FS (but is recognized) Topic is solved

[strikeforcezero]

I was running Freestyler 3.5.2 and everything was working with the MIDI controller
I Upgraded (fresh install) to 3.5.4 and now it doesn't seem to be reacting to the MIDI controller
It shows up in the setup screen and shows what buttons/notes are being pressed but doesn't actually perform the operations mapped to the keys/notes.

I've tried both the AKAI MPD18 and a KORG nanoKEY2 MIDI controllers.

Am I missing something, like a new setting that is affecting this?

Here's a screen shot of the MIDI control panel showing its picking up the input of the MIDI controller


Here's a screenshot of the new options menu

[Mattotone]

Try Page independent, otherwise you have to select the page first via another midi button..i think?

[strikeforcezero]

Thanks for the reply.

I think I already tried that, I'll have to give it another go.
Default is page 1. I think the korg only had one page anyway

[Kings]

The new version of FS appears to 'forget' the midi settings. Try entering them again the same way you did originally.

[strikeforcezero]

The screen shots are from a fresh install with no previous settings and me entering them for the first time on this version

[Spirit]

hi

i cant see which Velocity the button send so can you tell me which Velocity it sends if you press a button?

/spirit

[strikeforcezero]

I'll have to check again.

If my memory serves the korg was 60 something and stayed 60 until next key press. and the mkai was 0->127->0
I did notice the note would fluctuate depending on pressure until the pad was released.

I'll try taking a video of the mkai later

[Spirit]

hi i have taken a look at the Akai pdf..

and it seems the pads are touch sensitive. but as i see you need to enable "Full LEVEL" this will disable the touch sensitive and the pad will allways sens 127.

also take a look at Page 3 No.4 i think you need this...

But its realy importent you send a Velocity of 127. By default FS works like this you can Change this
But besure If you PRESS the button it should send 127 and if you Release the button it should send 0 (Flash button)

/spirit

[strikeforcezero]

It looks like the note/pad value is parsing the velocity instead of the note being pressed
It parses the correct velocity and note/pad being pressed if you "tap" the pad/note, with note being #48, velocity 127 (see second image)
but if you hold it down, FS reads the note as 127, velocity 0 (see 5th image)
or if you hold it down 1/3, its jumps around 20-30 (see 3rd image)
if you hold it down 2/3, it ranges from 70-90 (see 4th image)
when you release the pad/note, it reads note #48, velocity 0 (see image 1) just like it should.

Here's the screenshots I took while pressing the same Pad/Note #48
The MIDI Controller is in "Full Level" mode
http://imgur.com/a/cvHY9

[Kings]

FS only recognises a value of 127 from a midi key press. Touch (or velocity sensitive) will put out a value between 1 and 127 depending how hard you hit the key. The Korg nano has some install software that enables a value of 127 for any key press. Search this forum for a post I put up with the keywords Korg and nano.

[strikeforcezero]

FS only recognises a value of 127 from a midi key press. Touch (or velocity sensitive) will put out a value between 1 and 127 depending how hard you hit the key. The Korg nano has some install software that enables a value of 127 for any key press. Search this forum for a post I put up with the keywords Korg and nano.

I'm using a AKAI MPD18, the korg was for testing to see if it was the pad.
What you are referring to is what is called "Full Level" on the Akai.
The problem is version 3.5.4 FS is not working, while 3.5.2 FS is working normally.

[Spirit]

hi

can you download Midiox and monitor 1 Key press for me and meake a Screenshot...

/spirit

[strikeforcezero]

Note C / Pad #48 [Full Level]
4 taps
last 3 were held down for variable amount of time

Code: Select all

 TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT               
 00020364   1  --     90    30    7F    1  C  3 Note On               
 0002038C   1  --     80    30    00    1  C  3 Note Off              
 000203EE   1  --     90    30    7F    1  C  3 Note On               
 00020420   1  --     80    30    00    1  C  3 Note Off              
 00020540   1  --     90    30    7F    1  C  3 Note On               
 0002056B   1  --     80    30    00    1  C  3 Note Off              
 000205D7   1  --     90    30    7F    1  C  3 Note On               
 0002060F   1  --     80    30    00    1  C  3 Note Off              
 000207BC   1  --     90    30    7F    1  C  3 Note On               
 0002080C   1  --     D0    40    --    1  ---  Channel Aft           
 00020820   1  --     D0    3E    --    1  ---  Channel Aft           
 00020834   1  --     D0    41    --    1  ---  Channel Aft           
 00020848   1  --     D0    44    --    1  ---  Channel Aft           
 0002085D   1  --     D0    46    --    1  ---  Channel Aft           
 00020899   1  --     D0    45    --    1  ---  Channel Aft           
 000208AD   1  --     D0    44    --    1  ---  Channel Aft           
 000208EA   1  --     D0    42    --    1  ---  Channel Aft           
 000208FE   1  --     D0    31    --    1  ---  Channel Aft           
 0002090E   1  --     D0    00    --    1  ---  Channel Aft           
 0002090E   1  --     80    30    00    1  C  3 Note Off              
 00020A08   1  --     90    30    7F    1  C  3 Note On               
 00020A55   1  --     D0    44    --    1  ---  Channel Aft           
 00020A69   1  --     D0    42    --    1  ---  Channel Aft           
 00020ACE   1  --     D0    3E    --    1  ---  Channel Aft           
 00020AE2   1  --     D0    2C    --    1  ---  Channel Aft           
 00020AF5   1  --     D0    00    --    1  ---  Channel Aft           
 00020AF5   1  --     80    30    00    1  C  3 Note Off              
 00020BDC   1  --     90    30    7F    1  C  3 Note On               
 00020C32   1  --     D0    4D    --    1  ---  Channel Aft           
 00020C3A   1  --     D0    48    --    1  ---  Channel Aft           
 00020C4E   1  --     D0    49    --    1  ---  Channel Aft           
 00020C61   1  --     D0    4C    --    1  ---  Channel Aft           
 00020C75   1  --     D0    4F    --    1  ---  Channel Aft           
 00020C89   1  --     D0    52    --    1  ---  Channel Aft           
 00020C9D   1  --     D0    53    --    1  ---  Channel Aft           
 00020CB5   1  --     D0    54    --    1  ---  Channel Aft           
 00020CC6   1  --     D0    55    --    1  ---  Channel Aft           
 00020CDA   1  --     D0    58    --    1  ---  Channel Aft           
 00020D02   1  --     D0    59    --    1  ---  Channel Aft           
 00020D2B   1  --     D0    58    --    1  ---  Channel Aft           
 00020D3F   1  --     D0    52    --    1  ---  Channel Aft           
 00020D53   1  --     D0    48    --    1  ---  Channel Aft           
 00020D67   1  --     D0    23    --    1  ---  Channel Aft           
 00020D70   1  --     D0    00    --    1  ---  Channel Aft           
 00020D70   1  --     80    30    00    1  C  3 Note Off              

[Spirit]

AA-HHHH i think your issue is because your controller send on differnt Channels and Event types..


Freestyler only supports B0 to BF (Control Change, CC# , channel 1 to 16)

/spirit

[strikeforcezero]

Well then why did it work on the previous version and not this one?
Both controllers did..

[Spirit]

Hummm thats a Good one i realy dont have a clue...

you can add a Bug report for the Devolper..

On the top of this webpage you have the Link "Submit a Bug report" add a Report and the devolper can try to get it working again..

/spirit

[strikeforcezero]

Alright I Submitted a bug report
http://www.freestylersupport.com/bugs/view.php?id=1065

[strikeforcezero]

Update:

I used the Software for the controller to set the ranges freestyler supports. Disabled after touch. It looked like all was perfect in the freestyler world. Values were showing up correctly in the 3 boxes.

But after I exited the setup window it still wasn't controlling the program

I'm stumped and think this has to be a bug since no other controller is working..

[Eddiie]

Add me to the list.

This is a bug.

Any chance of getting this fixed? I cannot log in to the bug base.

[Spirit]

i think its realy strange as my Midi controll BCF2000 and my own made midi controller "MIDIBOX" works Great!!!! no issues at all.

as i also see your controller send Noteon/Noteoff command and theres a Separte function you can Enable and Disable if your controller uses Noteon/Noteoff
can be found between the Midi setup from Freestyler.

/spirit

[oozaoru]

I also have the same problem, it recognize the midi note command but just dont accept it

[Uriahdemon]

Same here but only when I updated to V3.5.5, V3.5.4 was fine. I submitted a bug report and was asked to try 3.5.6 but that is the same. I would like to roll back to V3.5.4 but cannot see anywhere to download and install it from. Anyone any ideas please...??