bishopuniverse

Silverhead, you are correct. This would take some effort. In my mind the coding would be minor compared to the planning and testing. We would need to break all conversions into three options: As Is: This is where the conversions match as is. (This sounds like your Phase 1) Simple: This is where there isn't a match but decisions can be made by the program. (This sounds like Phase 2) Complex: This is one that would require a person to decide what changes to make. This could be done with or without the program making suggestions. As the models are in JSON, it should be easy to create objects, modify them, then spit the JSON out for the right output. Except for UI and decision making, a lot of the code should be straightforward. However, as you can see by the document I attached, discovery is a big animal. Determining what models exist, how they map to other models, how branches work between models, when users need to be involved in decision making, etc. would be a much bigger piece. Then, testing these mappings on various devices would be a big animal. The plus side is that most anyone can do most of the work here, with just a little bit of direction. Coding would be possibly 25-30% of the total work. The thing I find most intriguing is that CustomForge has done the work of decoding a ton of tones for Rocksmith (Just under 6000). Tapping into that resource to pull tones for Pod Go and Helix seems like a huge win. You are correct, Silverhead: this will be a big undertaking. It would provide access to many tones and convert between models. The good news is anyone who is interested can contribute if they are willing to read JSON and/or spreadsheets and document them. if that sounds valuable to anyone, just reply. If not, no worries.

Thanks for all the support and great discussion here! (There's also more discussion on the CustomForge Discord channel, for anyone interested). Sorry for dropping this then dropping off the face of the earth. Life suddenly became overwhelming with lots of high demand events crammed into a small timeframe. That being said, things have slowed down. I would love to see this finalized, and I know at least one person had enough interest to ask for special access to the file. If there are coders, people willing to document (such as the Rocksmith tones format from the tools found in the CustomForge Discord), and people willing to try it out on their devices (Pod Go, Helix, etc), I'd be up for participating. I guess the easiest way to see how much traction this has is to just reply to this message with the role you would be willing to participate in. Let's see how that goes. :) We have the information to make this. If we can find the people and the time, we'd have one really badass tool that people like us would love.

I have been working on understanding the Pod Go files and the Helix files so I could determine how to convert between them. I have completed the first draft of the format document that explains the file formats and shows how we could convert between them. The document can be found here: For me, the next steps are: Verification of the information, by creating files and verifying against Helix (I only have the Pod Go). Creating a conversion document that shows how to convert for each item. Creating a converter. The convertor would simply "dumb down" a Helix file for Pod Go, and beef up a Pod Go file for Helix. Is this something anyone is interested in? It was a lot of fun, but a lot of work. I would like to know how much interest there is before I go further. (Side note: it looks like steps 4 and 5 could be using Rocksmith to create a presets from your favorite Rocksmith songs.) Thanks for your time. I would love to hear your thoughts.