[espher]

So I’ve been mulling over trying to throw RBHP on GitHub or a similar repository. It’s obviously not code or plaintext, for the most part, but the prospect of built-in versioning and other contributors being able to throw things up there and/or submit fixes and stuff appeals to me. Might make it easier for me to manage things like submissions, bug reports, etc, etc.

 

I could still periodically pull down a copy of everything on there and upload it as a new ‘release’, but would there be any benefit for anyone else here to me going that route?

 

May also be useful if I ever go ahead and start developing that web-based packager… ” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif”>

[MFX]

It would benefit me. I’ve been looking into new ways to manipulate metadata to offer more sorting flexibility, and being able to shim some post-processing in would be nice.

[FujiSkunk]

Sounds like a good idea. People could pull the latest snapshot whenever they want. Speaking personally, it would give me incentive to learn a new versioning control system, assuming you use something other than Subversion.

 

I agree that something like this would benefit from a packager. Otherwise you’ll have to rely on contributors to add their updates to all the right combinations of files, which could prove a bit of a challenge.

[espher]

Alright. I’ll have to look some options over. I’ve never really done any repository stuff before (my version control at home/work has always been “copy folder to external storage/network share, rename to include timestamp”, but I’m not really a developer, so…) and this isn’t exactly a coding project.

 

Might try to do it up this coming weekend. I am 200% open to suggestions.

 

I do think it would be much better to do it this way since other people can just add their crap instead of e-mailing or PMing me and me completely forgetting about it because I am unreliable like that. ” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif”>

[Whizzer]

I’m very much in favor of this.

 

Before the final harmonies upgrade, I’ve found some errors here and there, but haven’t yet checked all the files. I will probably start over with the new final release, slowly checking every single file, adding a couple every week.

 

Thanks for all the hard work!

[espher]

Yeah, I had been playing through RB4 and updating RBHP tracks on my end (and compiling feedback) but had put that on hold waiting for updates. I’m likely going to pick it up again since there’s an update coming in April and a) I don’t want to wait that long before I do anything and the stuff they fixed will be stuff I need to fix, probably. ” src=”/wp-content/uploads/invision_emoticons/default_SA_cheeky.001.gif”>

 

So a repository may be good to avoid duplication of effort.

[espher]

Alright, I had to fight with the desktop client yesterday, but I did get a repository in place which has the latest public release:

 

https://github.com/rbhp-espher/rbhp

 

I went ahead and made a new branch to account for any changes since then (which I have not yet uploaded) or for any submissions other people want to make:

 

https://github.com/rbhp-espher/rbhp/tree/2016-1st-quarter-update

 

I legitimately have no clue what I am doing but I’ll see if I can add any of you who are interested in making submissions and we’ll go from there. I also have to do things like clean up the upgrades.dta RBHP-specific metadata in songs. Many still list me as the author or have the rbhp_version as 1/0. I will be tweaking those and the versions in the repository as of creation of the master branch (so, from the end of last year) will be v1.

[FujiSkunk]

I volunteer!

[Whizzer]

Yeah, I had been playing through RB4 and updating RBHP tracks on my end (and compiling feedback) but had put that on hold waiting for updates. I’m likely going to pick it up again since there’s an update coming in April and a) I don’t want to wait that long before I do anything and the stuff they fixed will be stuff I need to fix, probably. ” src=”/wp-content/uploads/invision_emoticons/default_SA_cheeky.001.gif” />

 

So a repository may be good to avoid duplication of effort.

Update for RB4, or planned RB:HP update?

 

Either way, sign me up. I’m willing to check midi and .dta files.

[espher]

It’s an update for RB:HP on my end, though I’m compiling things I noticed into a bug list that I will provide (maybe on the community bug tracker thing or through some other means).

 

I’ve run through about a quarter to a fifth of the list so far, iirc, and it’s mostly minor cosmetic stuff, though I do know from reports there are some ‘bigger fish’, so to speak.

[espher]

I spent the better part of this weekend fighting with Github for Desktop, and gave up yesterday evening, so I’ll be trying with something else to see if I can get this working. I certainly haven’t given up on the idea. ” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif”>

[Linos Melendi]

So I tried submitting 2 keys upgrades with a pull request. No idea if I did it right, never used github before.

[espher]

I think you did it right. At least, you did if I did, lol.

[Sideshow]

I’ve gathered up several official dlc songs that need fixes to the pro drums. Going to try this github way of submitting songs when I have some done. If any other contributors out there is working on Pro Drum fixes let me know so we don’t duplicate our work.

[Sideshow]

I submitted the following pro drum fixes:

 

Avenged Sevenfold “Bat Country”

Bon Jovi “You Give Love a Bad Name”

Deep Purple “Spacetruckin”

Deftones “Cherry Waves”

Deftones “Hole in the Earth”

Freezepop “ScienceGeniusGirl”

Foo Fighters “Breakout”

Green Day “EmeniusSleepus”

Green Day “Homecoming”

Iron Maiden “The Clairvoyant”

Kansas “Icarus”

The Cars “I’m In Touch With Your World”

 

More to come.

[Author]

Posts