I am still in the process to install the harmonies on my PS3 which is truly a labor of love. However, my PS3 is showing signs of age and therefore I am in the process to build 2 back ups. One I have up an running successfully with the customs. My question is regarding the file structure where the harmonies live - each .dta file.

Can an expert answer the question: is the file structure the same so that I could potentially test copying and pasting my set of updated files with the updated harmonies dta files over? i.e. CCF0376 is Lego and CCF005B is Boston I know that is somewhat a loaded question as it could imply copying songs in general - which is not my intent. Seems the file structure without comparing side by side might be tied to how I purchased (packs vs songs, etc. ) and when...

If indeed attempting to copy and overwrite is a dumb approach and the only way to update the second and third PS3s for for harmonies is the manual labor of love...so be it. Then also back to first question, does anyone have a reference list such as CCF0376 is Lego and CCF005B is Boston? If not, maybe as I work on it this time around that could be by contribution back to the community. It would speed things up - any tips or tricks welcomed here.

Run it from whatever folder you want to get the upgrades from, and it'll combine all the upgrades.dta files into upgrades-master.dta, and move all the *_plus.mid files into the folder you ran it in for easy conversion. You still have to manually move the songs.dta files, though.

Samyaza reminded me that i never did get around to posting my perl script... so here we are!

it exists, it works (for me) and I use it often, but it comes with a bunch of caveats...

- tested on linux only... and it has dependencies on several other tools. i tried to make it path-agnostic, but i don't know how great it'll run from a windows machine.

- requires a PS3_DTA_LIST.csv file generated by letting the c3 tools crawl your ps3 to generate a list of songs+paths

- it worked for me, but might not work for you. i did a TON of testing before i let it loose on my PS3. in the end, i ended up using it to automatically apply all RBHP updates, and haven't found an issue yet. i started doing incremental updates with it almost 3 years ago, and i believe it was 2 years ago that i did my first mass update of all RBHP that existed at that time, and a final round a year or so back once the project was "done".

- it tries to be very cautious as it works, and makes backups of any existing file it modifies. the first time around it should create a .orig of your .dta files, intending to preserve a "golden master" if you ever need to get back. after that any updates will generate a foo.dta.timestamp version, so you can get back to a previous version... handy when something goes wrong.

of particular note - it has a --readonly option which is a VERY good idea to run the first time or two around. it'll connect to and read from your ps3 and all the other files, but does NO write operations... great way to make sure your config is good and there's no other problems.

- it also has several other features, some better tested than others. i actually use it to install all my customs these days. it relies on things being in the .rar format, but it's pretty smart. probably good to have other beta testers, i just keep not getting back around to updating that thread. eventually i hope to remove windows entirely from my customs installation and get it converting CON files to PS3, but it's not there yet...

c3ps3tool.pl is the only file you strictly need. edit the first chunk of it to make path updates where needed (or use the corresponding command line option). if you run into issues, add the --log outputfile option to have it do some more verbose logging to a separate file and I can try to help you sort out what went wrong.