Jump to content

ZagatoZee

Member
  • Posts

    442
  • Joined

  • Last visited

  • Days Won

    2
  • Country

    Colombia
  • Donations

    0.00 USD 

Posts posted by ZagatoZee

  1.  

      - The Guitar Pro file format doesn't contain the real timing of notes and chords. So it is not sufficient by itself.

     

     

    Would the sync export data from Go-Play Along do the trick then?  I know it isn't "free" but is potentially a nice and "easy" option.

     

    The exports from there have an xml for sync, the gp file and audio file in one export folder. Happy to share a few if you'd like them for testing.

     

    As for the 5/7 string addition - NICE.

    If I can make a suggestion from a users point of view, could it be possible to have an option for the "extra" string be added above the low E, rather than changing the color of the high e?

     

    I often use the ER mode we hacked into Rocksmith, we change the color of the low E, as (for me at least) it is easier to transition between 4 and 5, or 6 and 7 strings, if the EADGBe are always the same colors - the only change being the low B etc being added when necessary.

     

    I know if using something akin to the RS file format, that isn't super simple, given the way they name strings - But, felt it worth asking about.

     

    Loving the way this is looking!

    • Like 1
  2.  

    Sure no problem! Do you want the whole list of every tuning I've got in there (even the really weird rare ones) or just the many variants more common low tunings like B standard, Drop A, Bb, A standard etc?

     

    If you want all of them, I can post screenshots of my tuning.database.json in its entirety or perhaps upload it to google drive so you can download and look through it. 

     

     

    Share the file and if/when we are able to make it so, we can just copy/paste it all.

  3. Personally I found it worth the time and effort, whenever I see a "custom tuning" label I immediately have to get rid of it and add the tuning in! Since I play a lot of weird tunings, it's made it a lot easier to browse them without constantly clicking on songs to see what tunings they're in.

     

    Though if you don't play a lot of low tuning songs it might not be worth it.

     

    One of the things some of us are working on, is a way to fix all those custom tuning definitions without modifying the psarc files, if you have a list of the settings you've accumulated to remove as many of them as possible, please share it with me and if/when we manage to work out how to fix them the way we'd like, I'll make sure as many as we have defined are included. 

    • Like 1
  4. The custom tuning label removal shared a while ago - was intended only for the tunings used in oDLC up to that time. It wasn't set for the Varied 5/6 string bass chart options, or all of the variable crazy thin stringed options.

  5.  

    I think we lost Steve - Manchot66 and  LaceyB here at The Classic Rock Coalition, and I don't know how many more with the awful covid-19 spreading around the world. I would love to hear from everyone. So say hi, here at The Classic Rock Coalition.

     

    I sincerely hope we haven't actually lost anyone from all of this global crap atm.

     

    Your post triggered a notice to the site admins, I just thought you might like to read this. It was posted in several reddit groups by "TraitorsG8", aka SeanMo, aka LaceyB on the 18th of April.

     

    unknown.png

     

     

    • Like 2
  6. Does the CGT know what the default values are for string colours?

     

    Asking since my strings are modified from the Proof of concept builds, and applying your changes via the toolkit, doesn't correct the issues the POC builds had, can I use CGT to revert those changes easily, or will I have to do that manually, then run your tool?

  7. Just tried with editing again, using v1.2 of the string change tool - tuning pegs still broken for me in regular and colorblind mode.

    Miss indicators are correct however!

     

    The gradient map is way too light too.

     

    This is seriously useable however. Great work!

    • Like 1
  8. What an hilariously back asswards way of doing things. 8 "identical" gradient files with 2 different names in multiple locations and a totally separate text based identifier for other elements....

    • Like 1
  9. @@ZagatoZee the miss icons are in \assets\gameplay\indicator so maybe you missed a file in there. Also in that folder there is a "gradient_map_additive" as well as a "note_gradient_map" so make sure you've changed both.

     

    That folder also does the "!" miss icon for riff repeater so see if that works correctly as well.

     

    Both of those have been modded.

  10. For some reason, with my modded files, I'm getting the single note "miss" or "hit" indicators as the "original" string colours, not my altered ones. Any pointers on which file I've forgotten to change that would likely be the cause of this?

     

    eg;

    Cn3QZIf.png

  11. What color did you choose for the seventh string?

    Black seems cool, but I'm not sure if it will be difficult to see.

     

    I used the Teal colour that is the default high B string in the stock colourblind mode.

  12. I'll have to try and fix the tuning pegs, I probably missed a row that needed changing or something in the tool. I'll do it tomorrow since its late here.

     

    Mod looks cool btw

     

    No rush man, the help you've given already is invaluable!

    • Like 1
  13. I used your string changer tool to create the string mods, but it seems to do some weird things by default to the tuning pegs.

     

    Here is a demo of my "Extended Range" mod - some minor tweaks needed still; 

  14. re custom tuning definitions;

     

    https://1drv.ms/f/s!AvYwHVKnDAP7lIpzdSGcSyRfv4OkxA

     

    2 files in that folder. One is the tuning definitions json, replacing the existing one in cache.psarc \ cache7.7z\manifests will sort out all but a few of the officially used tunings.

     

    There is also a text file contained within that has the text you should add to the end of the "maingame.csv" file (cache.psarc\cache4.7z\localization\) for it to display correctly.

    • Like 1
  15.  

    What colour would be good to have as the new colour tho?

     

    Maybe if all this cool stuff takes off we can add it to the toolkit or something so its more accessible.

     

     

    The 5/7th string is typically a B string, so something in a greenish tone would make some sense (since the high B is green) and be an acceptable contrast from the low E red. Atleast, that is where my head is at atm.

  16. Firekorn and I were spitballing a "practical use" for changing the colours - beyond helping out the colour blind and simple "because we can".

     

    So, suggestion for the non colour blind (FK has already been experimenting with this).

     

    Rename "color blind mode" in the menus (maingame.csv I hope) to "Extended range mode".

     

    We create a "new colour" for the lowest string on a 7 string guitar / 5 string bass - and move all the other note and string colours "up" a string. Idea being switching to this mode would make it much less of a mind F%$# to remember which string you should be playing.

     

    I realise this is tantamount to suggesting we "run a marathon, while still learning to crawl" - but I'm floating it publicly, so the idea is in more peoples heads!

×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy