Music & Tech II Blog

After looking around at both in-browser games and on steam, I ended up deciding to use Brawlhalla as my game engine for this project. It's one of many Super Smash Brothers clones available, but this one is free to download and had good reviews regarding its ability to work with a variety of controllers, as I was unsure how plugging in my roommate's off-brand X-Box controller would work.  It went incredibly smoothly, and after turning off the in-game music I opened up the project file in ChucK, started the virtual machine, and was able to get the sounds running simultaneously with the gameplay. My familiarity and skill with Super Smash Bros. is unfortunately quite limited (I never completed the tutorial levels) but I was able to jump into the game with ease and begin getting a feel for how the controls worked. However, I have some small concerns about my more experienced friends as they are very used to Super Smash Bros. controls and, at least for the button inputs, they are qui...

 This weekend once again was less productive than I'd hoped, as I never was able to set aside a large block of time to contribute at once to this project. However, the benefit of many smaller intervals was that I had to plug in the controller and get ChucK set up about once a day for the past week, and was able to consistantly get it working every time. This includes both the default example code and other modified files that are saved directly to my device. That being said, I'm concerned with my ability to complete the larger initial scope of this project, as I'm finding I'm much more rusty on code than I used to be, and so progress is much slower than I'd hoped. I've also begun mapping ideas for how I would like the sounds to be generated. The base fm and noise files appear to only generate sounds from a specific number of inputs, the A, B, X, and Y buttons, and simply modifies what those noises look like based on what triggers or axis are in motion or use. Fo...

This weekend was frustratingly less productive than I had planned and hoped, due to a combination of personal and technical issues. While last week I was able to hook up the controller and get it to produce sounds, this week I was running into a repeated error with the device recognizing the dac, independent of which controller or keyboard was plugged in.  As these are from existing ChucK examples and they were working previously, I know that in theory the format of these files should be correct, however I'm still unsure what the cause of this error is. ChucK has also continued to experience repeated crashes, which may have been what caused this error, though I haven't been able to find any floating ChucK files or programs after that fact. I may not be looking in the right place for those.  I also ran into issues with downloading Wekinator and getting access to the program. There has been a lot of tutorial watching and site reading and I have still made very little progress on...

This past week I did some initial testing of ChucK using the example files provided by the program, and verified the outputs of the off-brand X-Box controller could be read by ChucK. I first tested the device's ability to generate midi sounds from the keyboard inputs, to ensure that the audio on the device was functioning. I was unable to get sound to play through headphones during the sessions, so tested subsequently without additional audio devices. I first used the command line to "--probe" ChucK to see the list of devices, and verified that the off-brand X-Box controller I'd plugged in via USB cable was registering in the system. I used the basic joystick controller example to begin reading output from the controller. Unexpected, though in hind sight very predictable, was that while the controller buttons had a single "on" or "off" state, the joysticks and triggers had a very rapidly changing range of values. These were initially read from the ...