I'm caffeinated, so this is going to be unnecessarily long-winded...
There have been a few bug fixes lately, but most of my time has been spent on a new piece of functionality spurned into development by Lucas Boucher. Maybe you creative folks can come up with some amazing uses for it (like you usually do).
Lucas wanted to use his Wii guitar to record to a sequence and also live-update his hardware. Picture a group of guys sitting in driveway with their Rock Band equipment being backed up by 25,000 Christmas lights that are responding to their instruments. This is all that my meager imagination can come up with. Anyway, Lucas had the equipment and some code, he just needed the app to be able to handle it. So, as of 2.5, there will be a new plugin type, an "Input" plugin.
Unlike the Trigger plugin type that can trigger the execution of a sequence, an Input plugin will be used to create event data in real-time. The plugin will define an array of inputs it implements and then the user will dictate which channels each input goes to. In Lucas's case, he created a bunch of inputs representing the different controls on the Wii guitar. The user can also specify if the input data is to be written to the sequence, update the hardware, both, or neither. The input plugin starts up when the output plugins startup, so if the sequence is executing, the inputs will work.
An input doesn't have to be hardware. As long as there is a plugin providing inputs, the data can be anything -- hardware, audio, even time itself. So don't limit yourselves to just hardware.
So why tell you all of this? For one, so that the people who have had bug fixes go through know why they're not getting an update with them in it and, secondly, because 2.5 is enough of a change that it's not going to be a simple upgrade, hence "2.5" and not "2.2". When it is ready for use, it's going to have to be a separate installation and 2.1 will remain as-is. One of the changes going into it will allow it to play nicer with installation scripts as well, so Aurbo99's install will be better off.
Lucas has a video showing all of this working that he's going to post soon. If anyone else gets some use out of this functionality, he deserves the credit. Also, be on the lookout for the EFX-TEK EZ-8 which will also make use of this functionality. If you made it through this long-winded post, I apologize for its length and I thank you for your patience.
There have been a few bug fixes lately, but most of my time has been spent on a new piece of functionality spurned into development by Lucas Boucher. Maybe you creative folks can come up with some amazing uses for it (like you usually do).
Lucas wanted to use his Wii guitar to record to a sequence and also live-update his hardware. Picture a group of guys sitting in driveway with their Rock Band equipment being backed up by 25,000 Christmas lights that are responding to their instruments. This is all that my meager imagination can come up with. Anyway, Lucas had the equipment and some code, he just needed the app to be able to handle it. So, as of 2.5, there will be a new plugin type, an "Input" plugin.
Unlike the Trigger plugin type that can trigger the execution of a sequence, an Input plugin will be used to create event data in real-time. The plugin will define an array of inputs it implements and then the user will dictate which channels each input goes to. In Lucas's case, he created a bunch of inputs representing the different controls on the Wii guitar. The user can also specify if the input data is to be written to the sequence, update the hardware, both, or neither. The input plugin starts up when the output plugins startup, so if the sequence is executing, the inputs will work.
An input doesn't have to be hardware. As long as there is a plugin providing inputs, the data can be anything -- hardware, audio, even time itself. So don't limit yourselves to just hardware.
So why tell you all of this? For one, so that the people who have had bug fixes go through know why they're not getting an update with them in it and, secondly, because 2.5 is enough of a change that it's not going to be a simple upgrade, hence "2.5" and not "2.2". When it is ready for use, it's going to have to be a separate installation and 2.1 will remain as-is. One of the changes going into it will allow it to play nicer with installation scripts as well, so Aurbo99's install will be better off.
Lucas has a video showing all of this working that he's going to post soon. If anyone else gets some use out of this functionality, he deserves the credit. Also, be on the lookout for the EFX-TEK EZ-8 which will also make use of this functionality. If you made it through this long-winded post, I apologize for its length and I thank you for your patience.
