I am pleased to announce that new Rocksmith Custom Song Toolkit.
 
All thanks to the developers involved in the project that made this feasible possibility in so little time.
 
DEVS:
* me;
* Snakez;
* Maveth;
* Raynebc;
* Dreddfoxx;
* Alex360 (L0fka);
* Shrubbery (otaznik);
* Cozy1;
* Zephyrix;
* Xavatar (PowerSlinky);
* Chlipouni;
* Cgeorge;
 
TESTERS (consoles):
* Acid6D94 (XBox 360);
* Redeyed (PS3);
* Kim666 (PS3);
 
And among others for PC/Mac.
 
DOWNLOAD:
http://www.rscustom.net/
 
NOW WITH A RELEASE FOR MONO (CAN BE USED ON MAC) !!!
 
ANY ISSUE? TRY TO DOWNLOAD THE LAST BUILD:
http://www.rscustom.net/builds
 
IF PROBLEM PERSISTS, OPEN AN ISSUE IN THE PROJECT ON GITHUB:
https://github.com/rscustom/rocksmith-custom-song-toolkit/issues
 
 
NEW VERSION INCLUDE:
 

NEW IN 2.6.0.0:* New auto-update feature (shows changes from your version and allow update with one click);* Added InlayCreator (new package type to customize your guitar) [all credits to Cozy1 and Baoulletes for this feature];* Added config screen that you can pre-define some fields in toolkit;* Added song preview volume box to make preview independant of song volume;* Added structured project import option;* Added package author (charter name) inside the package (can be setup on config screen, default value is "Custom Song Creator", but you can define your name if you want);* Added background worker with progress bar for most toolkit features (Generate package, unpacker, update appid, etc);* Added option to use acronym in file names when generate packages;* Fixed DLCConverter CLI issues;* Fixed packer for mod purposes;* SNG 2 XML general issues fixed;* Enhanced package validation;* Toolkit random hangs fixed;* Package random crashes fixed;* Fixed auto-tone load with ToneC and ToneD in some cases;* Fixed Import Template from package (tuning frequency and some minor issues);* Fixed some existent appIds and added new ones;* DDC updated to 2.2;* Fixed packer for larger than 100mb files;* Minor issue fixes.

 
Note: RS2014 CDLC support almost all new features like new techniques, custom tunings, Tuning Pitch (frequency), Mac platform, etc.
 
This new version of toolkit require lastest version of Editor-on-Fire (EoF) 1.8RC8(r1281) or above.
 
To play custom songs on PC and Mac platform is required a patch to bypass song signature that will be released in a tutorial in smithyanvil. (for consoles is not required).
 





 
==============================================
 
CHANGE LOG:

 

2.5.0.0:* Packer/Unpacker Tab new layout;* New SNG Tab, that is the gui to sng2014 CLI;* New tool sng2014 CLI that allow pack/encrypt and decrypt/unpack sng, convert song xml to sng and sng to song xml;* DDC 2.1 update;* Packer/Unpacker now generate song xml if it doesn't exists;* DLC Converter now supports non custom packages;* DDC now supports non custom packages;* Changed keyboard shortcuts from Global to OnFocus;* Fixed game file packer like cache.psarc for mod purposes;* Allow DragDrop in DDC Tab file list;* Fixed absolute paths in Mac;* Fixed DD bars not appears in song preview;* Changed package and template default name replacing "_" to "-" in name spaces;* Fixed tuning frequency in toolkit is not the same in game;* Fixed DDC progress bar not update;* Fixed tuning pitch/frequency is not imported on Import template or DLC Converter;* AppId updated;* Fixed sng cleanups that cause arrangement don't start play after tuning in some cases;* New showlight algorithm that works better;* Fixed tuning auto selector in some cases;2.4.1.0:* Allow Update AppId for Mac packages;* Showlights are now generated by toolkit;* Fixed a lot of bugs in DLC Converter envolved XBox 360 and PS3 conversions;* Added sng2014 CLI to unpack/decrypt and encrypt/pack a SNG 2014 file;* Fixed error when Dynamic Difficulty level bars are not displayed in DDC generated files;* Added recent AppIds;* Added arguments to predefine platform and game version on packer CLI;* Fixed RS1 Packer/Unpacker and RS1 AppId Updater;* DDC Tab was improved;* Fixed "Index out of range" on any key is pressed in DLC Package Creator Tab;* Fixed issue when wem file was wrongly converted in some cases;* General small fixes. 2.4.0.1:* Added One Click Dynamic Difficulty Generator for custom song packages;* Added Import project template from Package (You generate a project from a package, edit values and regenerate song again without loss information);* Added Tuning Editor (now you can edit and add new tunings from GUI);* New tunings are now automatically imported to local database when add new arrangement or import packages;* Added option to use DDC Tab with Clean Process (overwrite original arrangament xml and don't generate DDC logs);* DDC updated to 2.0 with two new difficulty templates (thanks to Chlipouni);* Removed "Change output folder" from DDC Tab because the normal process doesn't overwrite original file, so this feature have no utility;* Fixed Mac > PC DLC conversion;* Added shortcut for most used actions in DLC Package Creator Tab:--- Ctrl + Shift + O = Open Package Template;--- Ctrl + Shift + S = Save Package Template;--- Ctrl + Shift + I = Import * Package Template;--- Ctrl + Shift + G = Generate Package (song);--- Ctrl + Shift + A = Add new Arrangement;--- Ctrl + Shift + T = Add new Tone;* Fixed some packer CLI issues. 2.3.1.0:* Fixed CAPO feature in CLDC;* Fixed Tuning Pitch (CentOffSet) for some tuning frequencies;* Added option to duplicate a tone;* Fixed DLC Converter when convert X360 packages from another platform;* A lot of fixes in DLC Converter (song year is 0, lost dynamic density, vocal and preview are lost, etc);* Recover RS2012 package generation support;* DDC updated to 1.9;* A lot fixes for DDC integration;* Added default name when generate package;* Added version field for user define version of the package;* Added validation for null tones to avoid problem with CDLC;* Added recently official DLC App Ids;* Fixed ParentPrevNote in song file (sng);* Set RS14 as default version in DLC Packer/Unpacker;* Defined Cherub Rock as default app id in DLC Converter;* A lot of fixes in showlights;* Added option to open folder where package was saved;* A lot of minor bug fixes. 2.3.0.0:* Package Creator only need one audio file to create packages for all platforms (RS1 and RS2014);* Tone import from profile (You can design your tone in Tone Design in game and import in Toolkit);* DDC update to v1.5 (thanks to chlipouni);* Added java check/explanation for PS3 package creation;* DLC Converter minor fixes;* Fixed AppId disappears when PC is not selected;* Fixed problem with pack/unpack RS2014 game files (for mod purporses);* Minor bug fixes. 2.2.2.1:* Fixed issue with load/create new and save tones;* Fixed bonus Arrangement displaying as normal arrangement;* Make the second arrangement of the same arrangement type as ALTERNATE arrangement ingame;* DDC Tab fixes and enhancements;* Fixed issue with load bass arrangement that have more than one tuning match in tuningdefinition repository;* Added fixes to solution to compile with mono in Mac;* Fixed default AppId is not setup when toolkit load;* Make US Holliday Pack (RS1) and Cherub Rock (RS14) as default AppId;* Fixed AppId not update on DLC Converter tab when target is PC/Mac. 2.2.2.0:* New DLC Converter CLI tool;* Fixed Audio Decode when Unpack songs in some environments;* Added option to convert ogg audio file between platforms like (WEM file);* RS1: Fixed error knob button not enable for editing and not load from package template;* DLC Converter: Fixed tmp folder not deleted after conversion;* DLC Converter: Fixed some arrangement identifications that cause crash on some conversions;* Fixed tone slot not enable for any arrangements;* Tone slot are now disabled when arrangement with auto tone setup is selected to prevent auto tone change to fail (user can enable slots again by check an option); 2.2.1.0:* Audio Converter Tab now can convert .WEM files between platforms (Desktop  Console);* DLC Converter now convert any platform with one click;* DLC Converter now convert multiples files at once;* DDC updated to 1.4 (thanks to chlipouni);* More Auto Tone Change Improvements and validations;* packer CLI: Fixed file paths;* Minor bug fixes. 2.2.0.2:* DDC Tab updated with new DDC 1.3 and new better interface that allow to apply DD in arrangements xmls or packages;* DLC Convert fix for Mac platform and many improvements;* PS3 package name fix (can't be space character due to encryption limitation);* Added validation to average tempo to avoid invalid value alert;* New Appids;* Sorted AppIds by name to easy artist identification;* Fixed tone edit when imported tone;* Auto tone change improvements;* Removed gameplay path for RS1 packages;* Fixed tuning issues for RS1 packages;* Many improvements and bug fixes. 2.2.0.0:* Full support for create RS2014 custom songs (all toolkit features included like packer/unpacker, packer CLI, AppId Update, tone import, etc);* New improved interface;* All platforms supported, including Mac (RS2014) and a improved PS3 support;* RS2014 only: New DLC Converter (allow user to convert from any platform to another with one click);* DDC integrated (Dynamic Difficulty Creator) [thanks to chlipouni];* Packer/Unpacker now compatible with any platform and game version include PS3;* So many improvements and bug fixes. 1.4.0.1:* Added option to encrypt files on 'pcdecrypt.exe' CLI.* Fixed Repack (APP_ID) problem (issues #59 #61);* Fixed problem with special/accented characters on save/load DLC template and Tones (XML) (issue #54);* Fixed HandShape ChordId field is wrong type (issue 66). 1.4.0.0:* Added 'SNG/Package 2 Tablature' (ASCI) converter [thanks to Thierry Steinberg];* Added 'Packer/Unpacker' CLI (Using 'packer.exe' users can pack/unpack a song in command line);* Added 'Build' CLI (Using 'packer.exe' users can build a song in command line from Rocksmith DLC template *.dlc.xml)[thanks to Adam Sloboda]* Added an option to recreate SNG on 'Packer/Unpacker' tab;* Added an option to specify PersistentID and MasterID on arrangement (this feature allow user to maintain scores after rebuild a song)[thanks to Adam Sloboda];* SongAppId list moved to a Xml file (now users can add new AppId);* Several fixes and minor improvements. 1.3.0.0:* Added fully support for PS3 custom songs (generate edat files);* Fix US holiday pack ID;* Fixed executable name;* Minor bug fixes. 1.2.0.1:* Added partial support for PS3 custom songs (generate PSAC files, but need other tool to encrypt to .edat and pack into .pkg file);* Fixed a problem where bass tones were not labeled as bass tones;* Added a few APP_ID's, and fixed the Rush ones;* Minor bug fixes. 1.1.5.2:* Fixed problem in Ogg Converter Wwise decode in some environments;* Removed validation that requires them to have a section near the END phrase at the end of the song;* Added validation to block special characters in tone name to avoid unpacking problems and others;* Added function to allow user reorder arrangements and tones (using keyboard keys: up, down, page up, page down, -, +);* Changed packing function to preserve package signature type and all license keys of package. 1.1.5.1:* Fixed error when pack a XBox 360 multi-song DLC (DLC Pack);* Fixed the OGG decode process when path have spaces;* Added support to import tones from XBox 360 DLC packages;* Added option to decode OGG when unpack songs;* Added button to restart application. 1.1.5.0:* Added function to convert Wwise/Rocksmith OGG format to OGG default readable by EoF and players. 1.1.4.4:* Fixed problem when XBox 360 packages are generated with double size. 1.1.4.3:* Fixed the volume value don't load from DLC saved data. 1.1.4.2:* Fixed "Tone Import" on packed song. 1.1.4.1:* Fixed "Packer/Unpacker" > "Update App Id" function. 1.1.4.0:* Packer/Unpacker now supports XBox360. 1.1.3.1:* Added song volume control;* PC and XBox 360 are now with same volume level;* Changed tab order (since it's no longer necessary to use the "SNG File Creator" and "Ogg Converter" tab). 1.1.3.0:* Fixed tone bug in XBox360 packages;* Enabled XBox360 tone;* Fixed MasterID for consoles;* Removed tone reference in vocal arrangement. 1.1.2.4:* Delete temp generated SNG files when generate packages;* Fix bass hopo technique and bass chord density. 1.1.2.3:* New APP ID;* Fixed problem when edit an arrangement and try load information from XML chart. 1.1.2.2:* Fixed tone not saving when loaded. 1.1.2.1:* Little fix to import data of arrangement XML chart;* Fixed Bass arrangement not selected when imported data from arrangement XML chart. 1.1.2.0:* Automatically populate some fields information from the arrangement XML chart. 1.1.1.6:* Allow multiple Bass arrangement in song. 1.1.1.5:* Fixed tone changes not saved when name don't changed. 1.1.1.4:* Fixed a bug when try to generate a package that has no vocals arrangement. 1.1.1.3:* Changed the arrangement list to not display tone name on vocals arrangement, they don't use;* Changed the add arrangement window to show only relevant options for arrangement type;* Fixed knob settings crash error if more than 9 knob settings like with (Bass) Boutique 800;* Changes Xlock to generate in same order of the official DLC file to make easy comparison;* Added validation in DLC name to remove invalid characters. 1.1.1.2:* Fixed song partition count that set up arrangement name count, eg.: "Combo 1", "Combo 2", now Bass always is "Bass" and not "Bass 3" anymore;* Fixed title ID to default Rocksmith title ID for XBox 360;* Removed dynamic information from imported tone;* Added validation in DLC name to remove invalid characters;* Fixed BinaryVersion (arrangement type) in XBlock file that is not anymore with fixed values. 1.1.1.1:* Fixed Packer/Unpacker display position. 1.1.1.0:* XBox 360 support (tones not work for XBox at this time);* Added fields to define song name sort and artist name sort;* Fixed problem with CueTextBox, now has greater compatibility in all environments;* Fixed problem when user cancel tone editing and it's saved anyway;* Fixed app id don't selected from saved app id in saved DLC data;* Fixed field tab index in Package Creator;* Fixed problem on Ziggy Pro Converter Tab width that don't display "browse" buttons;* Fixed width of the form to view all tabs correctly.

 

 

@Gibson  I am not going to be able to help you much if you are on a Mac.  Maybe look for other Mac users on CF and ask them for help or get a PC emulator for your Mac and run CGT.  At what point in game is RS shutting down?  After you load user profile and select a song to play or before?  Does shut down occur for all songs or just some?

@@Gibson, I had a report that someone fail to convert pc>mac, It's confirmed and I'll look into it.

@@Gibson, I had a report that someone fail to convert pc>mac, It's confirmed and I'll look into it.

Many thanks. You're more efficient than most governments I work with. Grateful for your help!

 

@@Gibson, I had a report that someone fail to convert pc>mac, It's confirmed and I'll look into it.

Many thanks. You're more efficient than most governments I work with. Grateful for your help!

 

If it's any help, we have asked other members to convert songs to the Mac platform (from their PC) and those have worked. Us converting p.psarc files to m.psarc files on our Mac have failed.

Sigh... I don't know what you did, but my previous tone error is back (latest version, 9312319f):

 

http://puu.sh/i4QGy/ed8971b15f.png

 

How it's set up in EoF:

 

http://puu.sh/i4QHP/d078312cdb.png

 

XML file before generating package:

 

http://puu.sh/i4QKp/bfee0e8f93.png

 

XML after trying to generate package:

http://puu.sh/i4QN1/e8e89524b5.png

 

The fix would probably be to change the name of "clean" and "distortion" in <tone time...> to reflect the names as defined in tonebase/tonea/toneb etc. After I did that manually, the package generated without errors.

Hello, 

 

I tried to convert Rocksmith 2012 CDLC to Rocksmith 2014 CDLC using the latest available toolkit. 

The song is U2 - One and is available at http://www.mediafire.com/download/6objb4rzc1d9a62/onebeta3.dat

 

I couldn't import tones because of json parse error, but I imported two arrangements and tried to generate a package. The settings and the result are on the picture:

https://drive.google.com/file/d/0B3uXlknE4eJrcUJJMVBnSkk3NmM/view?usp=sharing

 

Sorry for russian language, it's written "Index of out range" with references to files and rows.

I will appreciate any help with this.

Thanks.

@@comp, looks like another shovvlights bug.... aaaand It's fine to me(ru locale), I should force en locale to it, but but but

@comp @Alex360  I think there is a problem with that song.  Other RS1 CDLC are still converting ok.  I am investigating.

 

EDIT:  So the problem is that the Bass arrangement xml element is wrong in the RS1 CDLC file.  It is currently set to "Lead". 

 

Here's how to fix this CDLC song.  In the Creator GUI, press Import Package.  Select the song.  After the toolkit loads the RS1 song into the GUI.  Select (highlight) "Guitar -Rythm" and press Remove.

 

Now open up "Part REAL_BASS.xml" in the GR\Behaviors\Songs folder and manually edit it.  Change "Lead" to "Bass", save and close.  Then back in the Creator GUI manually adding the three arrangements back.  Press Add and select each XML file again from the GR\Behaviors\Songs folder.  Adjust the tones for each arrangement or leave as default.  Then press Generate.  Your song should work.

 

I will try to add an exception handler to the toolkit so that users are alerted of this condition and the need to manually edit.

 

I am nice guy, I will just automate these types of repairs in next release.

@@cozy1 Thank you very much for the help!

Indeed, I changed the xml element and the song was generated fine.

I have one assumption about the root of the problem. In Rocksmith 2012 this song contains 3 Lead arrangements (no bass), where the 3rd one has been converted to the Bass arrangement in the Toolkit. That's why the XML file contained Lead. 

Is there a way to make the Bonus Lead track out of it instead of the Bass arrangement?

@comp  Ah ... interesting and unusual.  May be able to fix by using Lead (Part 1), Lead (Part 2), Lead (Part 3).  You could confirm by manually editing the xml's arrangment and part elements and following the same procedure to manually generate the CDLC.  Let me know if it works.

 

EDIT: FYI original charter authored the song this way, probably in EOF.  Toolkit does not change the arrangement XML file names it only reads them.

@@cozy1 Thanks for the advice, I tried to change Lead/Rhytm/Bass strings in XML files to Lead (Part 1)/Lead (Part 2)/ Lead (Part 3) but I faced the same error during generation as I posted above. 

I think I stick to what I have now. It's more or less enough :)

@@Alex360 @@cozy1 still nothing on that tone naming issue that came back that @@SmellyOrc talked about here ?

@@firekorn I am unable to reproduce the error without having SmellyOrc project files.  Interesting SmellyOrc and I responded here after his initial post and now our responses are missing.

@@firekorn I am unable to reproduce the error without having SmellyOrc project files.  Interesting SmellyOrc and I responded here after his initial post and now our responses are missing.

 

I think the admin had to restore an old backup of the forum database, thats why those posts are missing

@@firekorn I am unable to reproduce the error without having SmellyOrc project files.  Interesting SmellyOrc and I responded here after his initial post and now our responses are missing.

 

I have uploaded a project here:https://www.dropbox.com/s/67b3zu5xs18vu6m/Amorphis%20-%20Day%20of%20Your%20Beliefs.rar?dl=0

 

This is my workflow:

 

1) Create tone change.

2) Give a descriptive name, like  "Acoustic", "Distortion" or "Lead", for example.

3) Save project in EoF.

4) Add XML file as arrangement

5) Toolkit loads the descriptive tone names

6) Add real tones to my tone list

7) Edit arrangement to change the tones to the ones that I have loaded.

8) Make everything else correct in toolkit

9) Save

10) Generate

11) ERROR

 

Note: it does not matter if I load the real tones (the ones that I'll use/try out) before or after I add the arrangement.

 

The problem is that the toolkit changes the XML file to reflect the changed tone names in the <tonebase> <tonea> etc fields, but not in the ones after that, the fields that specify the time of the tone changes:

 

http://puu.sh/i4QN1/e8e89524b5.png

 

So in the above case, the EoF tone names have been changed from Clean and Distortion to Clean_Reverb and endofhope, respectively. Done manually, by me. In the Edit arrangement box. The <tone time> stuff still uses the old tone names, and therefore returns an error. If I manually edit those tone names to Clean_Reverb and endofhope, the package generates just fine, and the song plays just fine as well.

 

If you need anything else, let me know.

 

PS: The project I've uploaded is a different project from the one described here.

@SmellyOrc  Thank you I will look at the project files.

 

"PS: The project I've uploaded is a different project from the one described here."  ???

@@SmellyOrc

 

I am able to produce a working CDLC from the project files that you provided with toolkit version 9312319f (screen shot of my setup after I clicked Generate).

I think the problem is with your workflow steps 6 and 7. 

6) Add real tones to my tone list  (DON'T use Add button.  Use Edit button and then Load Tone button to overwrite the existing incomplete/unpopulated EOF tone.)

7) Edit arrangement to change the tones to the ones that I have loaded.  (DON"T  edit the arrangement.  If you add tones properly using Edit the toolkit will automatically update the arrangements with new tone names.  Editing the arrangement only breaks the tones.)

 

See my step 3 below for more detail.

 

Here is my work process that produces working CDLC.  In the toolkit Creator GUI I did the following:

 

1.  In Arrangments groupbox ...

Add Lead (PART REAL_GUITAR_22_RS2.xml)
Add Rythum (PART REAL_GUITAR_RS2.xml)
Add Bass (PART REAL_BASS_RS2.xml)  Toolkit pops up Tuning Editor form warning you because the Bass EOF xml tuning element has:   You can correct this by clicking the red X (upper right corner) on Tuning Editor form popup to close it and then select the proper bass tuning in the Add Arragment form Tuning combobox, I used E standard.

Also my personal choice, I changed tuning on the guitar parts from D Standard to E Standard so that I wouldn't have to retune my guitar for testing.

2.  In Files groupbox ...

Add Album Artwork (folder1hj.dds).
Add Audio (guitar.ogg).

I did not find any custom tone files in the project folder so I added my own for Clean, Lead, Distortion, and Lead End.  

3.  In Tones groupbox ...

I added custom tones using the Edit Tone form and clicking Load Tone.  The tones I used were named Bass, Clean, Acoustic and End.  The toolkit successfully renamed the tones according to what was loaded.
You can also generate CDLC without adding tones and toolkit will use default tone values (which may not sound too good).

If you click Generate now toolkit will throw an error because Song Information, Year and Version fields are not filled in so fill these in first and then Generate.  The files described in the steps above are the only files I needed to generate a CDLC for this song.

The toolkit works as expected and produced working (confirmed by testing) CDLC from the project files you provided.

If you follow these steps you should be able to produce a working CDLC too.

I did find one bug in the Tone Editor which is unrelated to your original issue.  The Load Tone and Save Tone are not working as expected which has no effect on CDLC Generation.  I could not load tones from my archived tones2014.xml files and saved tones are not being named correctly for reuse.  I will fix this in a future release.

 

Please note that I did not use the "Amorphis_Day-of-Your-Beliefs_RS2014.dlc.xml" with Load Package because my system paths are different than yours.  Also using Load Package can also result in some errors.

 

Good luck.

Is the toolkit now overwriting arrangement XMLs to reflect tone edits?

 

Scenario is I had tones set up, Lead1 and Lead 2.  Everything working fine, tested in game.  I wanted to swap Lead1 and Lead2 around to try it out, and when I edited them in the toolkit it seems to have overwritten the XMLs permanently so that they now expect Lead2 first instead of Lead1.

 

At first I thought it was no biggie, I just reloaded the Toolkit save and started again, going to try to edit the tones in a different way.  But now every time I pull in an arrangement they expect Lead2 as the base tone not Lead1.

 

So is this the toolkit?

@PC Plum  If you edit tone name with toolkit then toolkit will change tone name in XML arrangement.  See above response to SmellyOrc, make sure to use Tones Edit and not the Tones Add button if you have multiple tones in one arrangement and you are simply wanting to make changes to existing tone names.  Toolkit does not change times when multiple tones are applied.  You can also use "Load Tones" in Edit Tones mode to select a different predefined tone and toolkit will handle name changes for you.   PM me if that doesn't answer it.

I worked out how to do it (get what I want), thanks for the reply.

 

I just wasn't sure what was going on, maybe I had did something wrong in EoF.  I've never known the toolkit to edit XML files before.

Hey guys, I've been away for a while and I was trying to catch up on this thread..... so many posts in a short period of time.

 

Anyway, I read the last posts talking about tone issues with the toolkit, but from what I gathered, you were just talking about changing tone names or the order of the tones....

 

Well, I've experienced an issue related with tones when removing DD (I don't know if the same happens when adding DD to a custom).

Unfortunately I didn't take any screenshots when the issue occurred, since it was just a few times, but given the "line of posts", here's the situation (I'll take screenshots on the next custom that this happens).....

 

1st I should describe the method I use to remove DD from a custom.

I import the package in the toolkit. Once the toolkit is finished and I have the custom imported, I add the letters "NDD" to the end of the title of the song, go to the DDC tab, select the .xmls inside the "arr" folder created by the toolkit when imported the package, Ramp-up model "ddc_dd_remover", Config File "ddc_default", Phrase length "40" and I click the check box "Overwrite original files" (that way I don't have to add the NDD arrangements and remove the DD ones on the "Creator" tab) and click "Remove DD".

This is what I've always done and it always worked perfectly.

I don't know which build of the toolkit started to do what I'm going to describe next, but it must be one of the latest builds, since this only happened recently, in the last month, maybe 2.

 

So, I do everything I described above but when I click the "Generate" button to create the _p.psarc file, I receive an error and all the times I read something related to the tones. Every time this happened, the behavior is always the same and I was "lucky" to discover why I was getting the error after removing DD, since that never happened before and this only happens on customs that have tone changes.

For some reason, DDC changes the names of the tones on the lines that have the tone time code in the .xml(s)

When I look above, where it's set ToneA, ToneB, etc., the names are correct, but DDC changes the names after that, on the lines with the time codes.

Since this happened 4 or 5 times so far, the only thing I find in "common" is that DDC replaces the names on the lines with the time codes for the "Tone type" name of the tone.

For example, a tone called "tone_dist", where the tone type is "Distortion", the unpacked xml has all the names correct, after removing DD with DDC, the name that shows on the line with the time code is "Distortion", instead of "tone_dist".

 

To demonstrate (this is just an example I manually edited to reflect what I described)....

This:

  <tonebase>IKYRH_lead</tonebase>
  <tonea>IKYRH_lead</tonea>
  <toneb>IKYRH_delay</toneb>
  <tones count="2">
    <tone time="375.924" id="0" name="IKYRH_delay" />
    <tone time="388.624" id="0" name="IKYRH_lead" />

 

 

 

After removing DD show this:

  <tonebase>IKYRH_lead</tonebase>
  <tonea>IKYRH_lead</tonea>
  <toneb>IKYRH_delay</toneb>
  <tones count="2">
    <tone time="375.924" id="0" name="delay" />
    <tone time="388.624" id="0" name="distortion" />

 

 

 

Every time this happened, I just replaced the incorrect names on the tone time line(s), clicked "Generate" in the toolkit and the _p.psarc is generated without any error.

 

Just thought you guys should know this is happening and I don't know if this is related with the toolkit or DDC.

 

As soon as I have another custom that this happens, I'll take screenshots and make a more detailed post.

 

Thanks again for everything, as always. :)

@@Kaijin maybe @Chlipouni can give us some input on this.

 

As long as you are not using "Add" Arrangements or "Add" Tones then the toolkit will not change the tones names the way you are showing above.  If you can confirm you are not using "Add" buttons in toolkit Creator GUI then it could be how DDC handles tones or something else.  I will be glad to investigate after we hear from Chlipouni.

@@Kaijin maybe @Chlipouni can give us some input on this.

 

As long as you are not using "Add" Arrangements or "Add" Tones then the toolkit will not change the tones names the way you are showing above.  If you can confirm you are not using "Add" buttons in toolkit Creator GUI then it could be how DDC handles tones or something else.  I will be glad to investigate after we hear from Chlipouni.

 

Yes @@cozy1, I don't add anything, neither arrangements or tones, I leave everything as it is when the toolkit imports the .psarc file, the only "modification" is adding NDD to the title of the song and removing DD from the .xml(s).

When I pack my own customs, where I have to add tones and arrangements, the last 3 I did all had tone changes and I didn't experienced none of what's described in the posts above.

Since I never add DD to my customs, I only use DDC to remove DD, that's why I only can confirm the issue when removing DD, I have no idea if the same issue might happen when adding DD to a custom using the method I described to remove it.

 

I wasn't sure about what could be the cause, but after reading your post I'm leaning towards something related with DDC, instead of the toolkit.

 

Since I usually remove DD from customs every week (because of the songs selected for the championship that have DD), I'm pretty sure that this will happen again and when it does, I'll take screenshots and make a detailed post with step by step.

 

Btw, I forgot to mention on the previous post, the error window I get when the issue happens is almost the same as the one posted by @@SmellyOrc on post nº 381.... I can't be sure of the entire text, but the 1st 5 lines are the same or very similar.

 

Thanks.

Hi Kaijin,

 

  DDC never updates the tones setting in the XML files.

 

  To remove DD, you can also use my new BPR tool with these few following steps :

  - Unpack the CDLC ([File][unpack])

  - For each track having DD, simply use [File][save]

  - Pack the CDLC ([File][Pack])

 

Thanks

Ok back to that tone issue :

 

i load my saved package to update my work quickly :

http://i.imgur.com/IBl21K8.png

Everything seems good then i just click generate and i have this error :

http://i.imgur.com/IMFst4y.png

 

The tone definition is like that after the generation :

http://i.imgur.com/n9lfdjF.png

The 3 first name are those in the toolkit and the other are those i put into EOF because i don't always remember and don't want to type the whole tone name.

Either the name are changed all the way or not at all but right now i have to manually edit every single .xml before being able to generate anything if i don't put the same tone name between EOF and the toolkit which i never did before and worked great since that v2.6.1.0-fe59ccde beta version...