Alesis VI Series Script for FL Studio: Drastically increases functionality

[@baarish216]

oh my god bro. i bought the VI25 back in 2020 as i started self learning production and it seemed like the best option for me cuz i wanted drum pads and full sized keys. but i realised later that most of its functions especially those switches are of no use with fl studio. just got greedy with the pads and keys and bought this. i googled for so long to find a way to make use of my keyboard's buttons, found nothing, and now months later i'm finding this video. no one ever talked about how to make use of those toggle switches with FL studio on the internet, and you finally did it. you're finally gonna make this keyboard a lot more useful for me than just writing melodies. i CANNOT thank you enough. i feel like i should be paying you for this. i genuinely don't know how to express my gratefulness. this is insane and exactly what i was searching for for more than an year. THANK YOU. THANK YOU. thank you. i CANNOT thank you enough. i needed this video. thank you man. 🙏

[@forgery810]

Thanks for the appreciation. I'm glad it is getting good use.

[@baarish216]

@@forgery810 it sure is, and big thanks to you for being the sole person on the internet that i could find that understood the functionality issues of the VI series with FL Studio and came up with this script. HUGE help.

[@esterix101]

@@baarish216 this is better than new akai mpc keys released for 2300 usd

[@esterix101]

Great video. I find interesting how this old ass midi keyboard is still better and have better pads and look more modern and futuristic than keyboards coming out now. This midi keyboard is total gem who need 16 pads instead wasting money on MPC and keys separately.

[@baycitybeat5593]

You guys use it w logic at all?? I wanna get into FL but haven't yet. Hoping is compatible with logic, far cheaper than komplete s series and is the only good alternative I've found. . . I have a mpk249 and it's been NOTHIN but trouble. I have a mikro and want to get this, samplr (kickstarter) OR just wait until I can get the kontrol s. . Any recommendations on combinations for mikro; any advice on a seemingly faulty mpk? It is not plug and play for me :( also have the m1 idk if anyone had issue w alesis. Great effin video man.

[@khersy]

first venture into trying out scripts for fl stuido, looks promising!

[@baycitybeat5593]

Subbed!

[@noelmguni2987]

Hi Brother, thank you for the script, very valuable! I'm currently having issues with the Pad Mode on AI25, I assigned Pad mode to switch number 2 but it seems the Pad per Channel mode is not working properly. There is no activity on the pads when I cycle between modes only standard works. It doesn't show the currently selected mode on the info bar. Please help

[@forgery810]

I thought it was an issue with how the switches are set on the layout but they look ok. Make sure your switches are set to Momentary rather than Toggle. Otherwise, I could not replicate the issue. Double check that your pads are set correctly as well, channel 1, 60-75. In FL Studio, go to View, Script Output. Push the Pad Mode Button and then another button that is working and post the output in a reply here which should help me figure out what is going on.

[@lowlifelens4780]

This is so sick! Any plans to make this work with FL 21?

[@forgery810]

Thanks. It actually already works with FL 21.

[@OliverWhispersASMR]

@@forgery810 My sustain pedal stops working as soon as I set the controller from generic controller to your script. Any ideas?

[@forgery810]

@@OliverWhispersASMR Probably a bug that I can fix. Are you using the latest version of the script (2.0)?

[@forgery810]

@@OliverWhispersASMR This bug is fixed in a new update, version 2.02. The sustain pedal midi channel must be switched to 2 in the layout. Thanks for letting me know and do so again if you encounter any other problems.

[@mr.snuggles1095]

Hey there, thanks for sharing this with us! I'd love to use it, however, as soon as I select the script, FL Studio does not seem to receive any input from the Alesis VI49. The last line in script output reads as following: " ModuleNotFoundError: No module named 'plugins' " Do you have any idea what could cause this? Any help will be appreciated a lot!

[@forgery810]

That error is likely related to running an older version of FL Studio. Try updating and let me know if that fixes the issue.

[@mstfbldrc]

There are some problems! I use FL Studio 21 btw. Firstly, all the pad functionality is mapped to the keyboard. For example, if I'm in step editing mode, pad doesn't do anything but the corresponding key on the keyboard does work. And when I press the numbered buttons, their light stays turned on and I have to double click. How can I solve these? Thank you!

[@mstfbldrc]

OK, I solved it. Thank you for the incredible supplementary video, I just noticed it.

[@forgery810]

Ok Cool. Just so anyone reading has the same issues, this happens because the switches need to be set to momentary rather than switch. Uploading the included layout will solve this issue. Also, the pads are essentially keys so pressing the corresponding key will do the same thing as the pad. If you are in step edit mode, some of the keys will set steps. There is no way around this really. @@mstfbldrc

[@SscopezZ]

Hey man, I have a question. Please excuse my ignorance, but I'm not able to paste my vi25 layout into the python file you specified. What am I doing wrong here? 😂

[@forgery810]

Are you able to paste it anywhere? You should be able to open that file in a text editor or ide and paste it into the file, replacing what is there. If, for some reason, that isn't working, you can go to www.online-python.com/. Paste the data there and click the download file button. Rename it to the same name and delete/replace the original file on the folder.

[@SscopezZ]

@forgery810 thanks, I'll try that out this evening!

[@bastienrousset]

hello, first of all, thanks a lot for sharing this amazing script with us! I have an Alesis VI49, i found some issues when pressing some buttons: The record button : When i'm pressing it in my MIDI controller, it works, but at the moment i'm releasing the button, it stop recording. is it possible to fix that ? it would be perfect if a simple pression let the record button ON in Fl studio :)

[@forgery810]

So I think what you are describing is happening because you don't have the correct Alesis layout. A few of the buttons, shift, record, metronome etc need to be set to toggle but the default on the controller is momentary. This is so their leds are lit when they are active. (Although, if you use your mouse to toggle the settings, they led will not change to reflect it. Nothing I can do about that unfortunately). In the folder you downloaded, there are some layouts to upload for each keyboard. Try that and let me know either way if that solves the issue.

[@BigKilla99]

This script is a life saver! I've been using another script with far less features for years, this one has so much more functionality. The only problem I've encountered so far has been the mod wheel. I can't get it to scroll as shown in the video. The arrow keys work, but scrolling would be prefered. Any ideas what might be causing this problem?

[@forgery810]

The mod wheel should be set to channel 1 and CC 49, which I think is different than the default. If changing that doesn't solve the issue, in FL, click View and then Script Output. Use the mod wheel briefly and copy what appears there and post it here.

[@BigKilla99]

@@forgery810 I set it to CC 49 and it works in the channel rack now, but still not the browser. Could this be due to FL 21's changes to the browser?

[@BigKilla99]

Arrow keys work fine in the browser, however.

[@forgery810]

@@BigKilla99 The scroll wheel doesn't work in the browser. If I remember right, using mod wheel to scroll relies on knowing how many channels/tracks etc. there are. There was no way with the API to get that info about the browser, so I couldn't implement it. It would be nice, though.

[@BigKilla99]

@@forgery810 ok thanks. You're e legend 🙏

[@ItzNotKnight]

I cant get the hotkeys to work properly im not sure what it is, the only one I notice doing anything is the one that lets you tap the bpm, do you know if this is something im maybe doing wrong or has anyone run into this?

[@forgery810]

This should be fixed now. The layouts for the 25 and 49 were set to toggle rather than momentary. You will have to either get the new ones from github and reupload or fix it yourself on the Alesis editor. Thanks for letting me know. I can't test those layouts so it made for an unfortunate oversight. Please let me know if it works or not.

[@kdogus77]

This did not work with fl studio 20. Controller did show up in the list. But gave an error indicating missing files.

[@forgery810]

What version of FL are you on? It must be 20.7.1 or later. Beyond that, double check the installation notes to make sure you did everything it says there, most importantly, putting the data.py file in the same folder.

[@dusle9834]

I did it as in the video, but FL just ignores the clicks. No errors. Nothing. My fl version: 20.7.2. HEEEELP!!!

[@forgery810]

@@dusle9834 Make sure MIDIIN2 is NOT enabled under midi settings. Only the VI61 should be enabled. Also, did you upload the proper layout to the keyboard using the Alesis software? If you have followed all of the instructions on the github, it should work. If you are still having problems, with everything set up properly, go to View/Script Output, hit a few buttons on the VI, then copy and paste what shows up in a reply and I'll try to figure it out. It also might help to update to the latest FL version.

[@TheYoungSandwichfilm]

I skimmed through the code and I don't think that the option is there to set the behaviour of the transport buttons, knobs or wheels like you can with the buttons. I did find a workaround for this though which works great incase anyone else is wondering. In the action.py file, I commented everything out from line 42 down to the very end (open file in Visual Studio Code, highlight all of the text and do Ctrl K + Ctrl C). Then from line 72 down to line 83 uncomment the functions 'start', 'stop', 'setPosition', and 'record' (open file in Visual Studio Code, highlight all of the text and do Ctrl K + Ctrl U). Restart FL studio if it is already open and you should be able to use the play, stop, and record buttons and you can link parameters to your knobs :) Thanks again for this man! (I think my original comment got removed for some reason but I am commenting again because this is useful information)

[@forgery810]

Doing this will bring up a lot of errors and break functionality for certain options. It may still work but I think if you were to open View / Script Output, you would see errors which could cause unforeseen issues. I would just recommend creating a new layout with the Alesis editor and changing the knob/transport cc values. In fact, you can have two layouts, one with the Script layout and another with everything the same except the knobs and easily change between them as needed. There may be conflicts with certain cc values so you may need to experiment. Again, look at the script output for errors. If you want edit the code, I would try going to process.py and changing line 35 from "Switch.transport(event)" to "pass"(no quotes, same indentation, like like 23). I am not going to test this but it should work with less issues. This will catch any transport button presses and do nothing. You can do the same for the pitch wheel by changing line 41 to pass. If changing the cc values doesn't work let me know and I can update the script so different cc values are bypassed.

[@TheYoungSandwichfilm]

@@forgery810 Thanks man. I didn't notice any errors for the small amount of time that I was playing around with this but I'll check the Script Output to see if it's causing any errors. I'll also try what you suggested later on when I'm at my computer and let you know the results

[@TheYoungSandwichfilm]

@@forgery810 I just had a look at the output and yeah there was a bunch of errors whenever I tried to use the knobs or any of the buttons, even though I was able to link parameters to it. I tried what you suggested with adding the pass statement to each of the if statements that i wont be using and it worked perfectly, no errors at all in the output window! Thanks again man, and kudos to you for still replying to comments years after you wrote this script. You just earned a sub from me :)

[@deebaker4671]

Will this work with ver 20.8 for MAC\WIN ?

[@forgery810]

Yes it should. I've never tested it on Mac but it should be fine.

[@prodUYI]

Really great script but somehow my mod wheel is mapped with the function to redo and undo(displays: unknown event(#00009001)) and my first knob selects the channels anybody has an idea on how to fix it?

[@forgery810]

What version of the keyboard are you using? Most likely those functions are mapped incorrectly. Did you upload the layout provided in the github repo?

[@hankhomaomes2830]

Hey bro please let me know why when using your script is recording double midi notes , for eg : when i try to record midi like say FPC so if i hit my pad or key quickly it's not onl;y recording the actual hit note but also a duplicate of it [sustained / long pressed note) how to fix it ... i thought it was from the editor but no it's the script for VI25 cause I rechecked using the M audio 25 script which is already there hence midi recording is fine as it is suppose to be. please help ... also please make a video on how to customize your script like you have set switches from 3-7 empty or idk what it does , so what if i want to add somethings on there like tempo tapper .

[@forgery810]

Thanks for letting me know. I fixed the issue but I want to make sure it didn't mess anything else up in the process before I post it. I'll test it out more tomorrow and let you know when I upload the new version to github. Do switches 3-7 not do anything or your VI25? I'd like to do more videos but I'm limited on time between various projects and having to go to my actual job sometimes.

[@forgery810]

I just updated the script to fix the issues and it is on Github for download. Thanks again for letting me know.

[@hankhomaomes2830]

@@forgery810 TYSM for replying ... I really love your work... and willbe waiting for more contents from you... yeah the switches 3-7 do not do anything for me on my VI25.

[@hankhomaomes2830]

@@forgery810 You are awesome .... I'm gonna download it rightaway and check it out... will surely reply back ... I also have an idea for your next content which I m sure you'll be able to script better it's regarding the FL's performance mode I did fiddle around to set it accordingly and it works almost perfectly ... anyway will get back after testing the new script from you TYSM once again.

[@forgery810]

Thanks man. Let me know how it works. If you feel like it, look up the troubleshooting section of the instructions and follow the directions there to create an issue on github so I can try to see what's up with those buttons. If you do, make sure you hit the buttons and copy what the script output shows when you do. I'm going create a new layout for the VI25 soon so it can access the random trig/random notes functions along with some of the other new stuff. So check back for that, as I think the random notes functionality is super useful. I never use performance mode actually but I may check it out.

[@baarish216]

hey, i did everything you said and installed everything and its all working. all the buttons and modes are working as you showed but my pads are not working according to the selected mode. for example when i'm in step mode, i can toggle the steps using my KEYBED, not my pads. the pads just play the selected channel in the standard way even though i'm in step mode. its taking my keybed input as the pads in step mode. any idea why?

[@forgery810]

Did you upload the vi25 layout? If you did and it still doesn't work, it is possible that layout is incorrect, as I was not able to test it. Since the keys work, all you should have to do is change the pad layout to the same note numbers as the corresponding key. If I remember correctly, pad 1 should be 60, pad 2 is 61,etc. So it should be easy to just use the Alesis layout editor to set it up. Let me know if the layout I uploaded is wrong and I can fix it.

[@baarish216]

@@forgery810 yes, i uploaded the layout too and everything else works perfectly. all the switches, buttons, knobs everything is perfect, its just the pads only work in the standard mode like i described. i'll surely try changing the pad inputs in the alesis editor, that actually sounds like it could solve the issue. thanks!

[@forgery810]

Looking it over, those were incorrect and have been fixed in the repository. Thanks for letting me know.

[@forgery810]

Also, I suggest creating another layout that accesses the random note, random pattern generator, etc. as I found those really useful and changed my workflow. You can look at the layout file in the folder to find what CC numbers to set the buttons to. Just make sure you include the shift button and set it to toggle and the others to momentary.

[@baarish216]

@@forgery810 just downloaded the updated version and its perfect now. pads, knobs, switches, everything works perfectly, thank you so much man!! i owe you. and i'll check out the other suggestion too, thank you so much.

[@mert2434]

Is it possible that its not working on the newest fl patch? ive been using it since 1-2 years but all of sudden it stopped working. havent been active on fl for 4 months prolly. Tried to re-do it and it didnt work out :/ anyone has info or can maybe help? xoxo

[@forgery810]

I just checked it on the FL Studio 2024, the latest update and it is still working for me. Make sure everything is set up correct as per the installation instructions. Then go to View, then View Script Output and reply with what shows up there.

[@mert2434]

@@forgery810 thanks for the fast Feedback, I will try it tomorrow and Share it W you. Much love out to you I really appreciate it

[@metiisalihu5675]

Why this dont work for mac 🥺

[@forgery810]

To my knowledge, it should work for Mac, although I cannot test it. Read the troubleshooting info in the readme file at Github and follow the instructions there for help figuring it out.

[@metiisalihu5675]

@@forgery810 where to get fl 20.7…

[@forgery810]

You have to update to 20.9 at www.image-line.com