This is it guys. The lutebot in a new and shiny version. What was originally a little project for a handful of alpha roleplayers has been heavily reworked to match the incredible release mordhau and its community just went through. I hope to be able to update and support it to bring the best out of mordhau's lute (and possible future instruments) for years to come using this new solid codebase and set of features.
See this new thread as a rework as well. Please read carefully through the guides below, they have been written by painstackingly collecting feedback from the new release users.
Join the bards guild discord server here to get troubbleshooting help, midis and more !
Check out this live midi input showcase, one of the novelties brought by the 2.0 :
The lutebot is a third party software that can read midi files (.mid) and mimic their content to the best of its ability using the lute in game. It uses console commands to communicate with the game.
Is it safe ?
The lutebot is born from a cooperation with the devs. They created the console commands for the lute specifically for this usage and fully endorse it. Furthermore, the code is entirely public on github (check the download section).
I have heard from moderators that some people have been trying to blame the lutebot after getting banned for third party software usage (actual cheats). Rest assured that the lutebot won't get you banned.
How does it works ?
The lutebot is built on the C# midi library by sanford that you can get here. This library plays midi files for the lutebot, which then intercept midi events when thrown by the library and turn them into console commands.
The lutebot's interface is made using winform, a somewhat outdated yet time saving tool for simple window interfaces.
If you like the lutebot and wish to support it, you can help me by donating to my patreon
Reworking the lutebot and adding live midi input was only the beginning, I have more features planned for the future (more on that on my patreon page !). But this is a time consuming project, your support will let me put more time into it.
Download and unzip the lutebot folder. As long as its content is intact, it will work regardless of where you put it.
Quick Setup
Start the lutebot by double clicking on LuteBot.exe. Click on options then on keybinding to open the keybinding menu.
From here, check the message displayed below the list of keybinds. It should look like this :
If it does, please Ignore the following section.
If this is not the message you're seeing, you need to manually set the path to mordhau's configuration file. Please do so by clicking on Mordhau Config then Mordhau Configuration Files then Set DefaultInput.ini Location. Then, select the file named DefaultInput.ini in your game folder. Its default location is : C:\Program Files (x86)\Steam\steamapps\common\Mordhau\Mordhau\Config\DefaultInput.ini
If you selected the right file, the message below should look like the picture above.
Now that the lutebot knows where your mordhau settings are located, you may use the automatic configuration that will set the console both in game and in the lutebot to PageDown for you.
To do so, please click on Mordhau Config then on Automatic Configuration then on Set up.
Then press Apply to close the keybind window.
The lutebot's OpenConsole keybind should be set to Next, and the next time the game starts, pressing PageDown should open the console. Take a moment to check if this is your case.
How to operate
To play a midi file (.mid) on the lutebot, click on Load Midi File in the main window and select a file. If you selected a proper midi file, it's title should appear one the window, and the buttons Stop and Play Should be now accessible. Click on the play button and you should start hearing music.
To play this midi file using the in game lute, go in settings and turn off sound effects here :
Then go in game, have a lute equipped in your hands, and press + on the numpad (the default shortcut to play) to start playing.
Warnings :
Do not use the play button to play in game, always use the shortcut.
Do not attempt to open the console yourself, let the lutebot manage the console.
Do not try to jump or crouch while playing.
The lutebot should now be ready to operate. Consult the detailed guide for more, or the troubleshooting section if you're still encountering issues.
This is the main window of the lutebot that will always show while it is running. It is designed to look like a regular music player, displaying the elapsed and total time in the current song, a scrollbar that you can move around, a play/pause button and a stop button.
Clicking on the central button will let you manually load one midi file into the player.
The previous and next buttons will let you navigate in the playlist. They are only accessible if a playlist is currently active and it contains at least two tracks.
The Options button in the top left corner will let you access the settings and the keybind menu. The Window button next to it let you use the optional features of the lutebot described below. The focus button in the window menu will put all of the lutebot's windows back to the foreground, useful when having multiple windows open. Alternatively, clicking on the main window does the same.
Configuring the LuteBot
Settings
The following settings affect which parts of the lutebot's interface will be open when starting the lutebot :
Show Playlist Menu on Startup
Show Soundboard Menu on Startup
Show Track Selection Menu on Startup
Show Online Sync Menu on Startup (unfinished)
Show Live Midi Input Menu on Startup
Sound effects : lets you switch between playing in game or playing using midi sounds (useful to try different instruments and tracks settings beforehand).
Automatic Console System : lets you change the way the lutebot interacts with the console.
Old : The big console will open once when you start playing, and close when you pause. This console mode prevents you from moving entirely when playing, and is slower (meaning that the note cooldown needs to be set much higher for it to work, 50 is recommended for this setting)
New : Opens the small console for each command. The small console closes automatically upon inputting one command, which allows the lutebot to input commands at a much faster rate. This is the recommended setting. Warning this setting won't work if the console key you're using for the lutebot can input characters (like Tilde). PageDown is recommended for this setting.
Off : the lutebot will not try to interact with the console at all. You have to manually open the big console before pressing play. Just like the old setting, it is slow and require a high note cooldown.
Note Conversion Mode : Turns on and off the note transposition feature. Due to the lute's limitations in game, the lutebot has a transposition system applied to notes outside of the lute's range. Turning it off and enabling sound effects lets you use the lutebot as a regular midi player. Useful to listen to original tracks before attempting tweaks.
Lowest Note ID : The lowest note id mordhau's lute supports. This setting should not be modified, please keep it to 0 at all times.
Note Count : The number of notes mordhau's lute supports. If mordhau's lute gets updated and receive more notes, you can set this setting so that the lutebot will take these changes into account.
Note Cooldown : This setting changes the cooldown in ms applied after a note has been played. 50 is recommended when using old or off console modes, while 30 or lower is recommended for the new console system.
You can check for updates in the bottom right corner of the settings window.
Keybinds
To change one of the lutebot's keyboard shortcuts, simply click on one of the keybind list's items and press the desired key to set the shortcut.
Do not forget to apply or your change won't be saved.
Here is a detail of all the keybinds and their functionnalities :
Play : Start/pause the current song. Next : Load the next song in the current playlist.Previous : Load the previous song in the current playlist. Ready : Currently unused (related to online sync).OpenConsole : Is used by the lutebot to open the console for you.
*LiveMidiListen : Toggle listening to your selected midi input device.
As explained in the Getting Started section, the keybind menu is also capable of setting your console key properly for you. Please refer to this section for more details.
Features
Each of the main features have their own window, so that you can customize the lutebot's interface to your liking.
Playlist
The playlist window lets you create a list of midi files that will be played one after the other. You can also skip to the previous or next song in the playlist using the buttons on the main window, or use the convenient keyboard shortcuts (/ and * on the numpad by default) to go from one song to the other without even leaving the game.
You can use the Add to Playlist button to add a midi file to the playlist.
You may also save the playlist as an xml file for later use using the Save Playlist button, and load a previously saved playlist using the Load Playlist button. Note that when you open the playlist window, it will automatically open the last playlist you saved.
Warning: Do not attempt to load a soundboard xml file as a playlist.
Soundboard
The soundboard lets you create up to 9 song shortcut. Pressing the associated key will instantly start playing the associated song. Consider using this feature to avoid alt-tabbing to switch between songs. To modify a shortcut's keybind or song, simply right click on one of the 9 buttons.
Just like the playlist, the soundboard can be saved as an xml file, and loaded later. Opening the soundboard window will automatically load the last soundboard you saved.
Track Filtering
The track filtering window lets you remove some complexity out of a midi file to make it sound better on the lute. Some midi files may contain a lot of instruments playing at the same time, which is undesired for mordhau's lute limitations.
You can tweak the content of a midi file simply by ticking boxes off to remove either instruments, or tracks. Tracks are a series of commands in midi files that may or may not contain notes, removing some might not have any effects depending on how the current midi was made.
When you think the tweak you applied suits your needs, simply press Save Song Profile to save your changes. As opposed to the soundboard and the playlist, you cannot choose where you save song profiles. They will be automatically stored in a folder and retrieved if they exists when a song is loaded (manually or using a playlist or soundboard).
Live Midi Input
The live midi input window is the most important feature of this new version. It allows you to take full control of the lute using either a midi input device plugged to your computer, or your keyboard directly.
Check the drop down menu to see the list of available devices. Keyboard Mode will always show up in the list on top, any midi input device directly plugged into your computer will show under it.
Once you selected the device you wish to use, click on the listening button. Your inputs will only be taken into consideration when this button is green. You may also use the . (or del) key on your numpad to toggle it while in game.
Selecting Keyboard mode will allow you to simulate a midi input device using your computer keyboard. You can bind individual notes to each of the piano keys below by clicking on one then pressing the desired key. Pressing those keybinds while in the game and with listening enabled will play the corresponding notes.
You may use the - 1 Octave and +1 Octave buttons to change the note range the lutebot is focusing on. Pressing a key on your midi device that plays a note outside of the displayed range will automatically transpose that note to the range. Alternatively, checking the box below will causes notes outside of this range to be simply ignored.
Before reading this section, please read carefully through the quick start up guide first. Make sure you're operating the lutebot properly.
The lutebot immediately spam the chat and open the team selection menu when I press play
This typically happens when your console key isn't set properly. Check that the lutebot's OpenConsole bind in the keybinding menu is properly set to the key you use to open the console in game. To rebind the console key in game, please check the quick start up guide. Alternatively, you can consult the official discord (by typing !c console in any channel of the official discord) to know how to bind it manually.
Command not recognised appears in the console when playing
This can happen for multiple reasons, please refer to the two sections below for more information.
A character appears before every command, causing the command not recognised error
This happens because the key you have set your console to can input characters (like tilde writing ~). You need to use a key that cannot input characters, like PageDown.
The i is missing, equpmencommand is being written in the console, causing the command not recognised error
Check the keyboard windows is currently set to. Make sure it is set to qwerty (EN should appear on the taskbar), or azerty (FRA on the taskbar).
Any other keyboard type is officially untested thus support cannot be guaranteed.
The lutebot start spamming the chat and opening the team selection menu in the middle of a song
This can happen for various reasons. Make sure that you don't jump, crouch or sprint while playing the lutebot.
If this happens with the big console (console mode off or old) then you need to set the note cooldown higher than it is. 50 ms is recommended.
Awesome work, the 2.0 note conversion is what I am most happy with, it is able to play both my fixed and non-fixed octaves files from 1.2 with no issues.
Here is my collection of MIDI files I created from scores I found online: FloridaMan's Collection
All songs are done on 20 note cooldown and default for the rest.
Come join The Bards Guild discord for more files, discussion and help: Link
Can someone PLEASE help me? I just got online today and suddenly my lutebot "Open Console - Next" button isn't working.
My .ini file is still edited correctly, considering I literally haven't changed it from a few days ago. Yet for some reason it stopped working, even with the 2.0 update.
You're the best @ÐMontyleGueux for investing your time into this project!
And thank you to @Fohshizle and @FloridaMan and all the others for sharing their MIDI collection.
Can't wait to see concerts being played in Mordhau :D
When I tried to alter the settings of 2.0 Norton said Lutebot 2.0 has been disconnected from the internet, and when I try to open lutebot again, nothing happens, even when I run as an admin. If anyone finds a fix, would be greatly appreciated
@TheEvergreen said:
When I tried to alter the settings of 2.0 Norton said Lutebot 2.0 has been disconnected from the internet, and when I try to open lutebot again, nothing happens, even when I run as an admin. If anyone finds a fix, would be greatly appreciated
Huh, this is strange. So I went through with the setup completely as instructed, console key is pagedown and Lutebot was run as an admin, but it seems to just not paste commands into console, regardless of which automatic console setting I use.
What's even stranger is that the program works when using the live midi input function, but not with just regular midi files. No clue what's going on.
@FloridaMan said:
Awesome work, the 2.0 note conversion is what I am most happy with, it is able to play both my fixed and non-fixed octaves files from 1.2 with no issues.
Here is my collection of MIDI files I created from scores I found online: FloridaMan's Collection
All songs are done on 20 note cooldown and default for the rest.
Come join The Bards Guild discord for more files, discussion and help: Link
@ParalyzedTortoise said:
Huh, this is strange. So I went through with the setup completely as instructed, console key is pagedown and Lutebot was run as an admin, but it seems to just not paste commands into console, regardless of which automatic console setting I use.
What's even stranger is that the program works when using the live midi input function, but not with just regular midi files. No clue what's going on.
Very excited to see the release of Lutebot 2.0 and the potential possibilities with live MIDI input capabilities available now! I just bought myself an Alesis V25 on the spot specifically because of this news and I regret nothing. It will make the greatest game controller ever.
I have established the Bards Guild to support lute players in their endeavors to bring music to the battlefield by setting an expected standard of performance for the bard class and thus validating our presence on the battlefront. By literally banding together and setting some communal guidelines for lute players we are positively changing the overall perception towards bards, and proving that while the lute may not provide a direct buff to the players around it, there is still a strong if less tangible benefit to having a skilled bard on your team. The guild is a growing community for sharing MIDIs and information on how to edit MIDI files to work with LuteBot, and I am hoping will grow into some live jam sessions with the new LuteBot 2.0 features!
I am also building the Bards Guild MIDI Library as a web based database, and have already been working with @Fohshizle and @Seshn to include their collections in the library! I will have to talk with this @FloridaMan as well!
My feedback after playing with the new 2.0 version of LuteBot for a while tonight...
It seems slightly slower than 1.2, some of my faster MIDIs will drop more notes now when using the same settings.
Most of the songs I have that used to sound great with non-fixed octaves settings in 1.2 now sound bad in 2.0. :-(
Most of the fixed octave songs I have still sound great but slightly... different than before.
When I set the Note Conversion Mode from 2.0 to Off, it behaves for me as if the Sound effects option were checked even when it is not, and does not play in game at all.
I will probably continue to use version 1.2 for a while until I can figure out how to edit some of my favorite tracks to play as well on version 2.0, until my new MIDI keyboard arrives next week. :-) Are you able to expound a bit upon how the note conversion has changed between 1.2 and 2.0 to help me with updating my MIDI files?
Yeah I am getting some weird notes here and there, would be nice if the bot allows us to use some of the older note conversions. 2.0 is probably more flexible and can make more midi files sound closer to the original, but some of the files I made in 1.2 is getting wonky and there doesnt seem to be a way to fix it.
- 4
28 May
ÐMontyleGueuxThe Lutebot 2.0 Thread
This is it guys. The lutebot in a new and shiny version. What was originally a little project for a handful of alpha roleplayers has been heavily reworked to match the incredible release mordhau and its community just went through. I hope to be able to update and support it to bring the best out of mordhau's lute (and possible future instruments) for years to come using this new solid codebase and set of features.
See this new thread as a rework as well. Please read carefully through the guides below, they have been written by painstackingly collecting feedback from the new release users.
Join the bards guild discord server here to get troubbleshooting help, midis and more !
Check out this live midi input showcase, one of the novelties brought by the 2.0 :
Index
About
What's the lutebot ?
The lutebot is a third party software that can read midi files (.mid) and mimic their content to the best of its ability using the lute in game. It uses console commands to communicate with the game.
Is it safe ?
The lutebot is born from a cooperation with the devs. They created the console commands for the lute specifically for this usage and fully endorse it. Furthermore, the code is entirely public on github (check the download section).
I have heard from moderators that some people have been trying to blame the lutebot after getting banned for third party software usage (actual cheats). Rest assured that the lutebot won't get you banned.
How does it works ?
The lutebot is built on the C# midi library by sanford that you can get here. This library plays midi files for the lutebot, which then intercept midi events when thrown by the library and turn them into console commands.
The lutebot's interface is made using winform, a somewhat outdated yet time saving tool for simple window interfaces.
Donate
If you like the lutebot and wish to support it, you can help me by donating to my patreon
Reworking the lutebot and adding live midi input was only the beginning, I have more features planned for the future (more on that on my patreon page !). But this is a time consuming project, your support will let me put more time into it.
Download
You can get the latest lutebot version here
Or get access to the code directly on GitHub
Older versions :
Getting Started
Installation
Download and unzip the lutebot folder. As long as its content is intact, it will work regardless of where you put it.
Quick Setup
Start the lutebot by double clicking on LuteBot.exe. Click on options then on keybinding to open the keybinding menu.
From here, check the message displayed below the list of keybinds. It should look like this :
If it does, please Ignore the following section.
If this is not the message you're seeing, you need to manually set the path to mordhau's configuration file. Please do so by clicking on Mordhau Config then Mordhau Configuration Files then Set DefaultInput.ini Location. Then, select the file named DefaultInput.ini in your game folder. Its default location is :
C:\Program Files (x86)\Steam\steamapps\common\Mordhau\Mordhau\Config\DefaultInput.ini
If you selected the right file, the message below should look like the picture above.
Now that the lutebot knows where your mordhau settings are located, you may use the automatic configuration that will set the console both in game and in the lutebot to PageDown for you.
To do so, please click on Mordhau Config then on Automatic Configuration then on Set up.
Then press Apply to close the keybind window.
The lutebot's OpenConsole keybind should be set to Next, and the next time the game starts, pressing PageDown should open the console. Take a moment to check if this is your case.
How to operate
To play a midi file (.mid) on the lutebot, click on Load Midi File in the main window and select a file. If you selected a proper midi file, it's title should appear one the window, and the buttons Stop and Play Should be now accessible. Click on the play button and you should start hearing music.
To play this midi file using the in game lute, go in settings and turn off sound effects here :
Then go in game, have a lute equipped in your hands, and press + on the numpad (the default shortcut to play) to start playing.
Warnings :
The lutebot should now be ready to operate. Consult the detailed guide for more, or the troubleshooting section if you're still encountering issues.
Detailed Guide
Main Window
This is the main window of the lutebot that will always show while it is running. It is designed to look like a regular music player, displaying the elapsed and total time in the current song, a scrollbar that you can move around, a play/pause button and a stop button.
Clicking on the central button will let you manually load one midi file into the player.
The previous and next buttons will let you navigate in the playlist. They are only accessible if a playlist is currently active and it contains at least two tracks.
The Options button in the top left corner will let you access the settings and the keybind menu. The Window button next to it let you use the optional features of the lutebot described below. The focus button in the window menu will put all of the lutebot's windows back to the foreground, useful when having multiple windows open. Alternatively, clicking on the main window does the same.
Configuring the LuteBot
Settings
The following settings affect which parts of the lutebot's interface will be open when starting the lutebot :
Sound effects : lets you switch between playing in game or playing using midi sounds (useful to try different instruments and tracks settings beforehand).
Automatic Console System : lets you change the way the lutebot interacts with the console.
Note Conversion Mode : Turns on and off the note transposition feature. Due to the lute's limitations in game, the lutebot has a transposition system applied to notes outside of the lute's range. Turning it off and enabling sound effects lets you use the lutebot as a regular midi player. Useful to listen to original tracks before attempting tweaks.
Lowest Note ID : The lowest note id mordhau's lute supports. This setting should not be modified, please keep it to 0 at all times.
Note Count : The number of notes mordhau's lute supports. If mordhau's lute gets updated and receive more notes, you can set this setting so that the lutebot will take these changes into account.
Note Cooldown : This setting changes the cooldown in ms applied after a note has been played. 50 is recommended when using old or off console modes, while 30 or lower is recommended for the new console system.
You can check for updates in the bottom right corner of the settings window.
Keybinds
To change one of the lutebot's keyboard shortcuts, simply click on one of the keybind list's items and press the desired key to set the shortcut.
Do not forget to apply or your change won't be saved.
Here is a detail of all the keybinds and their functionnalities :
Next : Load the next song in the current playlist.Previous : Load the previous song in the current playlist.
Ready : Currently unused (related to online sync).OpenConsole : Is used by the lutebot to open the console for you.
*LiveMidiListen : Toggle listening to your selected midi input device.
As explained in the Getting Started section, the keybind menu is also capable of setting your console key properly for you. Please refer to this section for more details.
Features
Each of the main features have their own window, so that you can customize the lutebot's interface to your liking.
Playlist
The playlist window lets you create a list of midi files that will be played one after the other. You can also skip to the previous or next song in the playlist using the buttons on the main window, or use the convenient keyboard shortcuts (/ and * on the numpad by default) to go from one song to the other without even leaving the game.
You can use the Add to Playlist button to add a midi file to the playlist.
You may also save the playlist as an xml file for later use using the Save Playlist button, and load a previously saved playlist using the Load Playlist button. Note that when you open the playlist window, it will automatically open the last playlist you saved.
Warning: Do not attempt to load a soundboard xml file as a playlist.
Soundboard
The soundboard lets you create up to 9 song shortcut. Pressing the associated key will instantly start playing the associated song. Consider using this feature to avoid alt-tabbing to switch between songs. To modify a shortcut's keybind or song, simply right click on one of the 9 buttons.
Just like the playlist, the soundboard can be saved as an xml file, and loaded later. Opening the soundboard window will automatically load the last soundboard you saved.
Track Filtering
The track filtering window lets you remove some complexity out of a midi file to make it sound better on the lute. Some midi files may contain a lot of instruments playing at the same time, which is undesired for mordhau's lute limitations.
You can tweak the content of a midi file simply by ticking boxes off to remove either instruments, or tracks. Tracks are a series of commands in midi files that may or may not contain notes, removing some might not have any effects depending on how the current midi was made.
When you think the tweak you applied suits your needs, simply press Save Song Profile to save your changes. As opposed to the soundboard and the playlist, you cannot choose where you save song profiles. They will be automatically stored in a folder and retrieved if they exists when a song is loaded (manually or using a playlist or soundboard).
Live Midi Input
The live midi input window is the most important feature of this new version. It allows you to take full control of the lute using either a midi input device plugged to your computer, or your keyboard directly.
Check the drop down menu to see the list of available devices. Keyboard Mode will always show up in the list on top, any midi input device directly plugged into your computer will show under it.
Once you selected the device you wish to use, click on the listening button. Your inputs will only be taken into consideration when this button is green. You may also use the . (or del) key on your numpad to toggle it while in game.
Selecting Keyboard mode will allow you to simulate a midi input device using your computer keyboard. You can bind individual notes to each of the piano keys below by clicking on one then pressing the desired key. Pressing those keybinds while in the game and with listening enabled will play the corresponding notes.
You may use the - 1 Octave and +1 Octave buttons to change the note range the lutebot is focusing on. Pressing a key on your midi device that plays a note outside of the displayed range will automatically transpose that note to the range. Alternatively, checking the box below will causes notes outside of this range to be simply ignored.
Troubleshooting
Before reading this section, please read carefully through the quick start up guide first. Make sure you're operating the lutebot properly.
The lutebot immediately spam the chat and open the team selection menu when I press play
This typically happens when your console key isn't set properly. Check that the lutebot's OpenConsole bind in the keybinding menu is properly set to the key you use to open the console in game. To rebind the console key in game, please check the quick start up guide. Alternatively, you can consult the official discord (by typing !c console in any channel of the official discord) to know how to bind it manually.
Command not recognised appears in the console when playing
This can happen for multiple reasons, please refer to the two sections below for more information.
A character appears before every command, causing the command not recognised error
This happens because the key you have set your console to can input characters (like tilde writing ~). You need to use a key that cannot input characters, like PageDown.
The i is missing, equpmencommand is being written in the console, causing the command not recognised error
Check the keyboard windows is currently set to. Make sure it is set to qwerty (EN should appear on the taskbar), or azerty (FRA on the taskbar).
Any other keyboard type is officially untested thus support cannot be guaranteed.
The lutebot start spamming the chat and opening the team selection menu in the middle of a song
This can happen for various reasons. Make sure that you don't jump, crouch or sprint while playing the lutebot.
If this happens with the big console (console mode off or old) then you need to set the note cooldown higher than it is. 50 ms is recommended.
Midi Files
I will post here the various midi files that people have edited to work with the lutebot.
Thanks to @Fohshizle for his work, you can get his midi files (here)[https://drive.google.com/file/d/1RUTe3ZMlpDY8QTNVTorZbKCa4oSqHh88/view?usp=sharing]
Also try FloridaMan's Collection
Special Thanks
Marox :
For making the lutebot possible in the first place.
Milosh_Obilic :
For putting together the tutorial videos as well as the various showcases. Stay tuned for his modding work once the sdk drops!
My testers, JasonBourne, PlouPlou, Iodine, Madcow :
For helping me figure out what I lacked in music knowledge, and reporting various bugs since the first version.
28 May
MonsteriThis topic has been pinned.
28 May
McMercyA little warning to the aspiring lutebot roleplayer
You are bloodlust fuel
but very cool monty
28 May
MadMartiganYESSS!!!! At last I can use my midi keyboard!
Monty soit béni jusqu'à la 75ème génération.
28 May
goddamnminilambNice, excited to try this out.
28 May
FNFreedomtell me you can hook me up with that bandit radio midi, cant find any good ones!
- 2
28 May
RecHELP!
I downloaded 1.2 and it worked perfectly, but for some reason when I downloaded 2.0 it was unable to unzip it. Any suggestions?
Edit: Nvm, extracted it with a different app and it worked, not sure what went wrong
- 2
29 May
FloridaManAwesome work, the 2.0 note conversion is what I am most happy with, it is able to play both my fixed and non-fixed octaves files from 1.2 with no issues.
Here is my collection of MIDI files I created from scores I found online:
FloridaMan's Collection
All songs are done on 20 note cooldown and default for the rest.
Come join The Bards Guild discord for more files, discussion and help:
Link
29 May
MrKrinklezCan someone PLEASE help me? I just got online today and suddenly my lutebot "Open Console - Next" button isn't working.
My .ini file is still edited correctly, considering I literally haven't changed it from a few days ago. Yet for some reason it stopped working, even with the 2.0 update.
ConsoleKey=None
-ConsoleKeys=PageDown
+ConsoleKeys=PageDown
+ConsoleKeys=Caret
+ConsoleKeys=#
But my PageDown just opens the console and doesn't start the program. Please help.
29 May
OmnivalYou're the best @ÐMontyleGueux for investing your time into this project!
And thank you to @Fohshizle and @FloridaMan and all the others for sharing their MIDI collection.
Can't wait to see concerts being played in Mordhau :D
29 May
TheEvergreenWhen I tried to alter the settings of 2.0 Norton said Lutebot 2.0 has been disconnected from the internet, and when I try to open lutebot again, nothing happens, even when I run as an admin. If anyone finds a fix, would be greatly appreciated
29 May
VampireDuckTry whitelisting the Lutebot in Norton?
29 May
ParalyzedTortoiseHuh, this is strange. So I went through with the setup completely as instructed, console key is pagedown and Lutebot was run as an admin, but it seems to just not paste commands into console, regardless of which automatic console setting I use.
What's even stranger is that the program works when using the live midi input function, but not with just regular midi files. No clue what's going on.
29 May
ÐMontyleGueuxThanks, I added it to the post
29 May
ÐMontyleGueuxYou probably have the sound effects on.
29 May
SeshnHey there!
Thanks for all the great work. Loving LuteBot 2.0.
I'd like to provide a link a link to my midi collection. I have edited many of the files myself and I update it frequently.
My Reddit post
https://www.reddit.com/r/Mordhau/comments/bt1rpm/sharing_my_entire_midi_collection_with_the/
A direct link to the google drive
https://drive.google.com/drive/folders/1XmrbhZ9J06RKPseOqFcxVwyqhGjsaUR-
30 May
Bardlord LutemasterVery excited to see the release of Lutebot 2.0 and the potential possibilities with live MIDI input capabilities available now! I just bought myself an Alesis V25 on the spot specifically because of this news and I regret nothing. It will make the greatest game controller ever.
I have established the Bards Guild to support lute players in their endeavors to bring music to the battlefield by setting an expected standard of performance for the bard class and thus validating our presence on the battlefront. By literally banding together and setting some communal guidelines for lute players we are positively changing the overall perception towards bards, and proving that while the lute may not provide a direct buff to the players around it, there is still a strong if less tangible benefit to having a skilled bard on your team. The guild is a growing community for sharing MIDIs and information on how to edit MIDI files to work with LuteBot, and I am hoping will grow into some live jam sessions with the new LuteBot 2.0 features!
I am also building the Bards Guild MIDI Library as a web based database, and have already been working with @Fohshizle and @Seshn to include their collections in the library! I will have to talk with this @FloridaMan as well!
https://steamcommunity.com/sharedfiles/filedetails/?id=1750155302
30 May
Bardlord LutemasterMy feedback after playing with the new 2.0 version of LuteBot for a while tonight...
I will probably continue to use version 1.2 for a while until I can figure out how to edit some of my favorite tracks to play as well on version 2.0, until my new MIDI keyboard arrives next week. :-) Are you able to expound a bit upon how the note conversion has changed between 1.2 and 2.0 to help me with updating my MIDI files?
30 May
FloridaManYeah I am getting some weird notes here and there, would be nice if the bot allows us to use some of the older note conversions. 2.0 is probably more flexible and can make more midi files sound closer to the original, but some of the files I made in 1.2 is getting wonky and there doesnt seem to be a way to fix it.
30 May
DaddySidiousKGThe lutebot download link doesn't work, it sends me to a white blank page. Don't know why this is happening.