Jump to content

iminashi

Developer
  • Posts

    411
  • Joined

  • Last visited

  • Days Won

    3
  • Country

    Finland
  • Donations

    0.00 USD 

Everything posted by iminashi

  1. Section names need come from the list of the names defined in the game. Phrase names can be defined freely.
  2. On my machine it works. I tried importing this https://ignition4.customsforge.com/cdlc/87192 and with the ww2ogg.exe replaced with the 0.24 version the import succeeds.
  3. That should be fixable by updating the ww2ogg in the Toolkit's files to a newer version: https://github.com/hcs64/ww2ogg/releases
  4. Shift+F edits the fret hand position at the cursor is location (I've also written a bit about it in the beginning of my guide). As for that bug, I've never heard of such a thing happening.
  5. I thought that EOF could handle that slide case properly, but apparently not. A way to get rid of the warning is to add an "ignore" tech note on the 7th fret note. For the fingering issue you'll need to manually correct the hand positions and chord fingerings.
  6. Looks like CFSM does not like it if the tone key and name are different. As for why it would need them to match, I don't know.
  7. Are you using Windows 7?
  8. The XML Combiner is for combining different songs together so that you play them one after another. I haven't tried combining arrangements from different customs of the same song myself, but I suppose one way to do it would be to import both PSARCs separately into DLC Builder, then open them in EOF and copy the notes from one into the other.
  9. I've been using RipX DeepRemix for a while now and it is really useful for someone with bananas in their ears like myself. I find it that it makes figuring out bass parts a lot easier, and the piano keyboard at the side is super useful for determining the pitches of notes. I've tried spleeter exactly once, with a J-Pop song I've got in the works and its separated bass sounds like muffled low notes whereas in RipX it sounds like the actual bass. It also displays chord guesses when the guitar layer is selected and automatically figures out the tempo/measures.
  10. I don't know if that's possible, but it would require some modding in addition that this tool doesn't do.
  11. The audio files are in songs.psarc for whatever reason.
  12. Java is needed to run the PS3 encrypt/decrypt tool included with the Toolkit. I've never used it so I don't know if it needs a specific version.
  13. DLC Builder only supports Wwise versions 2019 or 2021. For CDLC creation there's no need to get the GUI version of Wwise to work, just the CLI is needed. I don't see a Linux version on that site. Also, the macOS port is actually just the Windows version running on Wine.
  14. @ someotherbruce I made a Linux build of DLC Builder. Could you give it a try? I was able to build a working CDLC on my Mint VM. There may be issues with the automatic Wwise conversion. If the Wwise console path is left empty, it will try to find it from "~/.wine/drive_c/Program Files (x86)/Audiokinetic". I cheated a bit and just copied the Wwise installation from my Windows machine and then installed the vc redist files from the prerequisites folder from the archive from https://ignition4.customsforge.com/cfsm/wwise and that was enough to get it working.
  15. Creating a Linux version of DLC Builder is possible, since most of it is cross-platform. The automatic Wwise conversion would need a new implementation via Wine though. I haven't provided a Linux version since I assumed that practically no-one would use it (though I think practically no-one uses the mac version either ) .
  16. I've uploaded a new version, which is probably the last one since the program I've been working on, DLC Builder (an alternative to the Toolkit's CDLC Creator tab) contains most of DDC Improver's functionality.
  17. It's probably got something to do with the equalizer settings. With just an amp with max bass and no mid/treble gives a red color.
  18. @firekorn I can't see your attachments, but that sounds like the bug that should be fixed in the next version. Give this build a try and see if it fixes it.
  19. Invisible notes are caused by an incorrect linknext status on the previous note on the same string. Looking at the XML, there are two such notes in the lead arrangement at 37.672 and 113.451.
  20. @@nick_beat One should install the .NET version that matches the Windows version. DDC Improver itself should work the same on 32-bit and 64-bit Windows, though I've only tested it on 64-bit Windows 10.
  21. File -> Preferences -> Import/Export Check "Save separate Rocksmith 2 files".
  22. Additionally, the XML file in the project files (PART REAL_GUITAR) is for Rocksmith 1, not Rocksmith 2014.
  23. The exception originates in GetWwisePath, so it seems to be finding more than one 32-bit WwiseCLI.exe in the Wwise path.
  24. Based on the error message, did you check the obvious thing: that the file ICSharpCode.SharpZipLib.dll is in the Toolkit directory and not being blocked by Windows or some anti-virus software?
  25. v3.0 has been released. The place where the program configuration and logs are stored has been changed, so your settings will be reset to defaults when updating from v2.2. You may also delete the logs directory from the program folder when updating. The most prominent new feature is "Quick Remove DD", which I added since using the DDC tab in the Toolkit to remove DD always felt cumbersome to me. As an example, removing DD from all three arrangements from the AC/DC Powerage Full Album custom: With the Toolkit's DDC tab: ~1 min 45 sec With "Quick Remove DD": ~1 sec
×
×
  • 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