cozy1

Guess that is why I had added that comment to the code. Any suggestions for the code revision?

1) I will adjust the toolkit Quick add file path validation so that '.' periods are acceptable characters. 2) The toolkit no long makes any changes/corrections to the EOF arrangement's default/alternate/bonus representative like it did in the past. It is up to the user to specify arrangement representative in EOF. Which explains the difference you are seeing between old CDLC and new CDLC. @@firekorn assisted with promoting and testing the change. Maybe he can shed some light on what you are seeing. 3) WWISEROOT Environmental Variable is set during Wwise installation. The toolkit will use whatever is specified by WWISEROOT if it is present, unless you specify a custom Wwise path in toolkit>General Config. The General Config custom Wise path supersedes the WWISEROOT Environmental Variable. What is the full custom path to your Wwise installation? Could be the same validation issues as in #1.

@@scrummer Nothing sinister is lurking in the toolkit if you downloaded it from the official site here. Typically AV's throw false positives with auto updaters because they act like a trojan would. You can whitelist the exe's contained in the zip archive to avoid false positives in the future.

@QOTSANINSOADKORN Plz pm your EOF project files.

Looks like we don't have to step back anything. Just use the '-' dash instead of the '~' tilde. An acceptable alternative for that band according to Wikipedia. I can automate the toolkit update/replacement process in the next build. https://en.wikipedia.org/wiki/L%27Arc-en-Ciel

"unless you're willing to decide to allow the character." I think you misunderstand. I am not the one that decided not to allow the character. We are just follow the standards that we have been able to glean from ODLC. There are significantly fewer issues with CDLC since EOF and toolkit data validation was implemented. While your particular request may not cause a problem, I would hate to go back to from where we have come.

@@theSG Autosave will work like you want in the next build. YW

"does't automatically saves template if you import cdlc" I mean that the part where "folder and files including the new template" What is the purpose of saving a template when you have not changed any song information? Just use 'Import Package' again. Templates are saved whenever you change song information and exit the toolkit (if you have autosave enabled), or press 'Generate', (if you have autosave enabled), or press 'Save Template'. "I still don't understand why now you need to have additionally same files without friendly names in the same folder." If you decide to repack the artifacts using the Packer/Unpacker tab menu then you will need the .wem files. Feel free to manually delete the files if they are bothersome.

User Comments and Developer Answers (C&A) C: Discovered that the new toolkit removes the tilde ~ from L'Arc~en~Ciel, breaking the artist sort for songs I've been making since 2014. A: You have asked this question before and it was answered in depth here. The toolkit and EOF use validation checks that are in-line with ODLC standards to provide for CDLC consistency, quality, and playablity. If your goal is to produce non-conforming CDLC then consider using an unsupported legacy pre 2.8 version of the toolkit. C: There's definitely something wrong with the template file. A: Old template files are not compatible with new version of the toolkit. You can regenerate the template file using the newest build of the toolkit. Here's how: >CDLC Creator>Import Package (select the old psarc)>Save Template. This creates a new EOF project file folder and files including the new template. C: It seems to require you to have wwise installed even though I provided necessary and wem files A: I'll make code modification in next build so that if both wem files are present then the toolkit will not check for a valid Wwise installation C: does't automatically saves template if you import cdlc A: Make sure you have 'Autosave Templates' check in 'General Config'. The template is auto saved when you select 'Generate'. Alternatively you can manually save a template as you make changes at any time by selecting 'Save Template'. C: wem files extracted twice (with .wem and ) A: It is nearly impossible to tell which wem files is which from the standard .wem file naming. The toolkit provides user friendly names to the wem files so you can tell the audio apart. C: extracted ogg files ending with *fixed (not sure if toolkit actually fixes anything since I imported song generated with latest toolkit) A: Wem audio ogg file format is proprietary and it can not be played on a non-Audiokinetic music player. The toolkit (fixed) the ogg audio for you so that it can be played on any audio player.

So which version of .Net do you have installed? Plz post screenshot of the error.

@@Aiddy0 Ok moved your question correct place. So if you want to install .Net 4.0 you are going to have to unstall the newer versions of .Net first. But I'm not sure you need to do that. Have a look here: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed and let me know what is installed. You can get the correct version of .Net from here if you want to try yourself: https://www.microsoft.com/en-us/download/confirmation.aspx?id=17718

@@Aiddy0 You posted your question in the toolkit thread. Are you asking about the toolkit or CFSM?

@apocmeow Do you know how to use Photoshop? You can make the inlay yourself. Here's the instructions and Photoshop template. Plz share you inlay template if you are sucessful.

@@NDAUBER "Is there a way to modify an already created song or does it have to be created from step one?" You can normalize the volume of existing CDLC using Audiosmith per the above directions. You can also use the toolkit, or CFSM to modify the volume of existing CDLC for your personal use. Just do one of the following: - CFSM>SongManager (select a CDLC)>Edit Song Information (right click)>Song Volume (change it)>Save - Toolkit>CDLC Creator>Import Package>Song vol. (change it)>Generate You may want to pass along your findings to the original CDLC charter so they can modify the volume according to what you have found.

The old updater, 2.8.0 will not work with the new version of the toolkit 2.9.2. You have to manually update and then the auto updater should work.

@ghr1227 Thanks for the input. "I did not manually customize the environment variables so whatever windows put in there from moving the users folder and sub folders to E:\ is entirely produced by windows during that process" Correct. But when you did this you programmatically modified the registry value (Environmental Variables) that points to a new 'My Documents'. I suspect this customization may be the cause of the issue. You would have to restore the default settings for 'My Documents' to know for sure. The new exception at least tells me I'm in looking in the right place. EDIT: New build released. Will catch and detail the error.

The original Quick Add did not allow users to specify the order of the Arrangements (a user requested feature). I suspect the issue has to do with your customization of 'Environmental Variables'. I will see what I can do to improve the feature. In the toolkit 'General Config' what do you have the 'Default Project Folder' set to? You can try specifying your custom project folder path if it is not already set and see if that helps. EDIT: Just released new build. Let me know if issue persists.

How are you setting 'e:\'? With 'Environmental Variables'? For now you can remove the setting you have for 'e:\' and see if that works. (Also try simplifying that path name to the 'The Searchers'. Maybe put your project in the root directory and see if that works). 'Quick Add' uses tree view on the system paths. Maybe it doesn't like you custom setting. I will have to investigate.

Can you post a screen shot of the Quick Add with the Multiselect XML Arrangements and Arrange Order GUI before the error occurs? What is the path to your EOF project files? System.IO.DirectoryNotFoundException: Did not find the rootNode text: e:\ Does it exist?

@Starchyld "Faulting application name: CustomsForgeSongManager.exe, version: 1.5.3.1" This is all I needed to know. You are two builds behind. :( As the song goes 'Nothing else matters'. 1) Delete the 'My Documents>CFSM' folder and subfolders. 2) Download, install and run the newest build of CFSM as Administrator. 3) If your AV or Defender throws an error then disable them and start over.

What OS and AV have you? Make sure you are using the latest build of CFSM. Delete the >My Documents>CFSM folder and subfolders. Screen shots of error would be helpful.

@Starchyld Any idea why Defender is quarantining these two files? file: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\CustomsForge Song Manager\CustomsForge Song Manager - Latest Build.lnkstartup: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\CustomsForge Song Manager\CustomsForge Song Manager - Latest Build.lnk - Click on the arrow on the right side that says “Actions” then click “Restore”All they are is freak'n shortcuts. Just goes to show how fluky Defender is being. I am currently searching for workarounds. Thanks for explaining the file restore process to users.

@Wolfranium There currently is not a method to change Artist in bulk. It sounds like you already know about, CFSM>Song Manager>Select>Mouse Right Click>Edit Song Information> which can be used to edit CDLC Song Information one at a time. I am working on CFSM 2nd Edition which would permit such bulk changes of song information. I don't have an expected release date.

@@Jan Universe This has worked for others having problems. You may want to give it a try. Make sure you have all folders closed when you run the updater. If it fails then something is locked or not closed (you will have to unlock and close manually before running updater again). Also make sure your Local Settings>Temp folder is empty before starting.

@@Jan Universe That's interesting, but have you tried the latest build?