202181
Level 31 Chipist
damifortune
post #202181 ::
2024.11.30 10:47am
Jangler, agargara, Opilion, Lasertooth, nitrofurano, arceus413 and SRB2er liēkd this
Jangler, agargara, Opilion, Lasertooth, nitrofurano, arceus413 and SRB2er liēkd this
this format is so much more awkward than i thought it would be when i added it. out of all the formats in Oops! All New Formats, this one is by far the most problematic. i'll go over the issues - and i'd love to hear input from YOU! reading this! so we can figure out how this format should be defined going forward.
1) it's not multiplatform
BotB formats should be free and multiplatform (or at least able to be emulated well) for maximum accessibility - Buzz proper is Windows-only software and apparently not usable in WINE. going into this battle, i had found Buzztrax which claimed to be a Buzz-like for Linux. it was so focused on cloning Buzz's capabilities that i just thought it was cross-compatible with Buzz projects; however as nitrofurano reported apparently it isn't. it's just a separate thing. this strikes me as the biggest issue with the format.
because running this experimental major required me to answer questions quickly and make calls when necessary, i made the call to allow Buzztrax submissions as well to O!ANF, in the spirit of inclusivity. i posted about it here but to summarize, i think this would be a terrible fit for XHBs. Buzz users won't be able to interact with Buzztrax submissions, and vice versa, leaving voters beholden to somebody being around to upload renders. i don't want that; battles need to run in a consistent manner.
the best answer i can come up with to this problem is simply to disallow Buzztrax and have the format support Jeskola Buzz only. (splitting the format into two would just be turning one problem into two problems.) but this still sucks because that would make the Buzz format accessible only by Windows users and that goes against one of the main tenets of BotB format eligibility.
to summarize, i kind of fucked up with this one 😅 there's also the option of retiring this format or making it XHB-unhostable, but i'd feel bad about that one too; it's brand new! what do you all think?
2) third-party machines
as first mentioned by Lasertooth here, Buzz's individual modules, called "machines", can have their roster expanded significantly via "third-party machines", most of which can be donloaded from within Buzz or on their site. i allowed this because it's not unlike the VCV Rack format - which supports "the entirety of freely available modules in the VCV ecosystem".
however, this is still tricky in terms of voting on XHBs; machines may need to be donloaded by voters to play back the entry correctly. and, in the long term, machines might disappear from Buzz's catalogs, making an entry some degree of unplayable in the future. agargara proposed answering this by adding .zip to the filetype list - something i probably should've actually done for the major but slipped my mind. this future-proofs the entry by including the third-party machines alongside the submission, and makes voting easier so people don't have to go hunt down the machine(s) to play back the entry.
i think allowing .zip would be an OK answer to this particular conundrum, but should it be required to submit .zip if third-party machines are used? also i'm assuming there's going to be once again no cross-compatibility with Buzztrax... all the more reason i don't think Buzztrax will fit in this format going forward.
---
those are the issues that i'm aware of - are there more things that stand out to you? how do you feel about this stuff? i don't wanna be the one making final judgment calls here, i only did what i needed to in order to keep the major running smoothly. but now that its entry period is coming to a close, it's time to figure it out!
1) it's not multiplatform
BotB formats should be free and multiplatform (or at least able to be emulated well) for maximum accessibility - Buzz proper is Windows-only software and apparently not usable in WINE. going into this battle, i had found Buzztrax which claimed to be a Buzz-like for Linux. it was so focused on cloning Buzz's capabilities that i just thought it was cross-compatible with Buzz projects; however as nitrofurano reported apparently it isn't. it's just a separate thing. this strikes me as the biggest issue with the format.
because running this experimental major required me to answer questions quickly and make calls when necessary, i made the call to allow Buzztrax submissions as well to O!ANF, in the spirit of inclusivity. i posted about it here but to summarize, i think this would be a terrible fit for XHBs. Buzz users won't be able to interact with Buzztrax submissions, and vice versa, leaving voters beholden to somebody being around to upload renders. i don't want that; battles need to run in a consistent manner.
the best answer i can come up with to this problem is simply to disallow Buzztrax and have the format support Jeskola Buzz only. (splitting the format into two would just be turning one problem into two problems.) but this still sucks because that would make the Buzz format accessible only by Windows users and that goes against one of the main tenets of BotB format eligibility.
to summarize, i kind of fucked up with this one 😅 there's also the option of retiring this format or making it XHB-unhostable, but i'd feel bad about that one too; it's brand new! what do you all think?
2) third-party machines
as first mentioned by Lasertooth here, Buzz's individual modules, called "machines", can have their roster expanded significantly via "third-party machines", most of which can be donloaded from within Buzz or on their site. i allowed this because it's not unlike the VCV Rack format - which supports "the entirety of freely available modules in the VCV ecosystem".
however, this is still tricky in terms of voting on XHBs; machines may need to be donloaded by voters to play back the entry correctly. and, in the long term, machines might disappear from Buzz's catalogs, making an entry some degree of unplayable in the future. agargara proposed answering this by adding .zip to the filetype list - something i probably should've actually done for the major but slipped my mind. this future-proofs the entry by including the third-party machines alongside the submission, and makes voting easier so people don't have to go hunt down the machine(s) to play back the entry.
i think allowing .zip would be an OK answer to this particular conundrum, but should it be required to submit .zip if third-party machines are used? also i'm assuming there's going to be once again no cross-compatibility with Buzztrax... all the more reason i don't think Buzztrax will fit in this format going forward.
---
those are the issues that i'm aware of - are there more things that stand out to you? how do you feel about this stuff? i don't wanna be the one making final judgment calls here, i only did what i needed to in order to keep the major running smoothly. but now that its entry period is coming to a close, it's time to figure it out!