I'm getting much closer to an actual work CDLC thanks to the help I received previously, but I've hit another snag.

 

When trying to import tones I get the following error:

 

Can't Import Tone(s).

Invalid Package

 

My tones are stored in the C:\Steam\userdata\ [hidden user ID] \221680\remote directory.

 

I'm running the toolkit as admin.

 

I reloaded RS and the tones are still present and working.

 

Any ideas?

Do a Windows Explorer file name search for "*_prfldb" or "localprofiles.json".  These files are in the directory you want to choose if your are trying to import tones from your user profile (game save). 

 

Make sure you are selecting the proper file type in the toolkit 'Select CDLC Song Package or Tone File or your Profile' popup.  It should be 'Rocksmith 2014 Game Save Profile (*_prfldb) and then select the *_prfldb file you found with Windows Explorer. 

 

There are several other ways to import tones in the toolkit, just make sure you are selecting the correct method to match the type of file you are importing from.

I have the correct directory ( I have steam installed directly on C:\ not in C:\program files). The _prfldb files and localprofiles.json are located there.

 

The file name is 1D28A8133E4E42D18123EEA99527601C_PRFLDB

 

There are two other _prfldb files as there are multiple profiles on my copy of RS2014, but that should be the correct one judging by the date the file was modified.

 

It's when I try to import the _prfldb in the toolkit that I get the error.

 

-----------

Also,  I'll be away for a few days so if you post something and I don't get back to you that's why.

I'm back from my trip, and see there hasn't been any word on this yet.

 

I've given it another try, but still no luck.

 

This is the last step before testing, so I'm eager to get it done. If anyone has suggestions or has had a similar problem please let me know.

 

Thanks.

@@Nullstate, share the profile, since I think It's not common issue or you mis something? should work just fine tho ._.

If I understood what it is you're asking for, then you can find it here

 

https://www.dropbox.com/s/j96j5xxdbg07htu/Profile.rar?dl=0

 

If you meant something else, or there's something wrong, let me know.

 

I also tried logging into RS2014 as a different user, and recreating the tones. That didn't work either.

 

Thanks for the help.

So that _prfldb that you sent link to has three tones in it that the toolkit can use ImglygL, ImglygR, and imglM2. 

 

1) In the toolkit Creator under Tones groupbox click on Import button.  Change 'File of type:' to Rocksmith 2014 Game Save Profile (*_prldb)  and select the 1D28A813*_PRFLDB file.  Click Open.

 

2)  Select the tuning you want to use from the Tone List.  (I picked ImglygL (-30.38069))  Click Continue.  You will get message that Tone(s) imported: 1  (you can pick any or all of your custom tones to import)

 

3) In toolkit Creator in Tones groupbox click on 'Default'  then click 'Del' button

 

4) In the Arrangements groupbox click on the arrangement that you want to change the tone of and click Edit button

 

5) In the Edit Arrangements popup box in the Tone Selector groupbox change the tone to your tone, ie ImglgL  (Choose Base and Tone A etc to match your tone) Click ok.

 

6) Generate

 

Keep trying, toolkit works as expected.

That's what I've been doing, or rather trying to do. When I try to import is when I get the error.

 

Good to know that some can get it working though. Which should mean that the prfldb isn't the probelm. Thanks for that.

 

I just tried importing those tones tones in a new (blank) project under the creator. Still getting the error.

 

I'm going to try removing an reinstalling the toolkit again. Wish me luck, I suspect I'll need it.

Okay, I just reinstall the toolkit, again. Version 2.6.0.0 gave me that same error as before, but for some reason this time 2.6.1.0 worked when run as admin (which is what I'd been doing). I'd tried that same process three times without success.

 

Weird. At least it is working now, but I do wish I know why it hadn't worked up until now

 

Thank you guys for all the help. Hopefully I can get this custom ready for beta testing now.

Moral of story ... ALWAYS use the latest beta build.  Looking for bugs in old release version is ... (fill in the blank).

Actually I had tried both previously, and reinstalled both. Not sure where I screwed up, but at least it works now.