EeveeonE

Interesting. The issue appears to be due to the higher tunings, where there is numbers that are positive. The negatives won't run with them. If the negative is out numbered. 

You should use 220Hz as the A frequency to go an octave lower (12 half step).

Thanks. I don't know how frequency works. I know that it adjusts the tone. 

But I'm still having the same issue. The tuning keeps randomly going to 9 0 2 2 3 3

I'm trying to compile a CDLC which has an eight string arrangement with a strange tuning. 

The tuning from lowest to highest:

C#AEADG.

In EOF, this would be -15 -12 -10 -10 -9 -9. I know that the tool kit can't go above or below 10. My solution was to make the tuning -3 0 2 2 3 3 instead. 

When I import this arrangement with this tuning and lower the frequency to 330hz. I check the tuning after I compiled the CDLC, and instead of -3, it is 9. This is the incorrect tuning. Everything else is fine, it's just the C# note the toolkit doesn't like. 

I made a quick video to show what was happening:

https://streamable.com/sua2x

Edit: I give up. It seems things that should be simple are not because automatic is a thing. 

I decided to put the C tuning into a bass track instead. Then there's just a standard eight string tuning for rhythm. I'm hoping this will work. 

Use a different album artwork image.  256x256 jpeg would be best.

Figured it out. It was the album artwork. But it was because it had Japanese characters and some other strange characters in the name. I did download it from some sort of song wiki. Thanks for the help though. I'll be sure to keep this in mind if the issue happens again. 

@@SuperSonic, try with our latest beta release and make sure your AV have toolkit in whitelist

Neither of those fixed it. I still get the same error. 

I've installed all my Rocksmith CDLC creation on a new PC because my old one has crashed. And I just created my first CDLC on this PC with all the necessary software, and I get this error: 

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

I'm using EOF v1.8RC10 (r1337)

UltraStar Creator

Wwise 2014.1.6 build 5318

Rocksmith Custom Song Toolkit (v.2.8.0.0-3d133c61)

I have no clue what this error is trying to tell me. The first file name that it was looking for keeps changing on each generation. 

Does anyone know how to fix this? 

 

 

Not exact, but I bet the default plexi tone assigned to the lead path would mix in well enough.

 

Give it a playthrough and see how it sounds.  Remove the delay and reverb pedal though.  Fiddle with the gain as needed.

What gear would it be?

 

 

As soon as you start the game stay in the lead path and go straight into tone designer.  It will be loaded up already and you can copy the settings into the toolkit.

 

Oh, you mean the default? I see. I'll tab part of the song by ear and try it out. 

Not exact, but I bet the default plexi tone assigned to the lead path would mix in well enough.

 

Give it a playthrough and see how it sounds.  Remove the delay and reverb pedal though.  Fiddle with the gain as needed.

What gear would it be?

I'm very curious what this Rhythm guitar tone uses. Can anyone help me identify it? 

I downloaded the  6 'Omnific' CDLC you created.  The latest beta CFSM repairs all the 'Omnific' CDLC without throwing any errors.  If you are still experiencing problems in the game with any of these CDLC after repair then I would suggest checking the CDLC Sections/Phrases in EOF for proper placement.  Also check any chords that may not be named or placed correctly (EOF will throw errors for these).

 

Looks like you are using custom tuning in 'Avant-Garde'.  This can also cause in-game problems if you have not defined the custom tuning properly in the toolkit.  Additionally, I would suggest dropping the '-' dash from the sortable song title as this may also be the cause of in-game problems.  (The new beta of the toolkit will validate the song information fields.  Dashes are not permitted in the sortable fields.  You owe me $10 bucks if you ask why!)

 

Make sure you are using the latest version of EOF and the latest beta toolkit.

Huh. Okay. That's strange, on my end, only three Omnific CDLC's got Corrupted. I can't remember all of them, but there were some that were corrupted. Very strange. 

A couple of additional tips. 

 

Open your CDLC project files in EOF.  If EOF throws any warnings when you go to save the project again before you exit then you may have some more EOF debugging work to do.  EOF does a go job of catching issues, the problem is that most users tend to just ignore these warnings which is not usually a good idea.  If you assign multitones in EOF then resist the urge to change the multitone names in the toolkit (you will get a warning if try to do this).

 

Open up the CFSM 'remasterd_error.log' file (do a Windows search for the file if you don't know where to find it).  The log has a pretty good description of what the CDLC corruption is.  This may help you narrow down what you have to debug/fix in the EOF project before regenerating in the toolkit.

EOF throws a warning at me every time, up to two usually. And I never really bothered to get rid of them because most of my CDLC's have the same warnings in EOF. As for tones, I never change the name. I know that can cause issues. I'll see what I can do.

"How come some CDLC's are corrupt, and cannot be repaired?  What's the reasoning behind it?"

 

Two reasons:

 

1) CDLC was produced using old version of toolkit which did shitty job of validation of data entries.  New toolkit version does much better job of validating and checking project files for errors before CDLC is generated.

 

2) CDLC author/charter did a crappy job of producing the CDLC in the first place.  There is a lot of garbage out there that people post without doing a good job of debugging and testing.

 

Hope that clears it up for you.

Oh, so like tones being stuck and all that?

That's strange, because some of my CDLC actually was corrupted and I made it all with the same version of the toolkit. To my disappointment, CDLC I made by the artist 'The Omnific', only half were repaired, the other half were corrupted, and the only one that used a five string bass on Rhythm was a song called 'Pharaoh' I don't know why it got corrupted. 

Thanks guys. I got v2.7.1. And thanks for the explanation 'Lovroman' I was really interested to know what happened behind the scenes. 

But I've got another question. How come some CDLC's are corrupt, and cannot be repaired?

What's the reasoning behind it?

Sorry if this is in the wrong place, but it isn't made very clear where you ask questions about anything on these forums. 

My question is, how does CFSM (CustomsForge Song Manager) fix the 100% mastery bug? 

I'm really curious how it works, because I'm wondering if it's possible to prevent the 100% mastery bug when creating a CDLC.

I used this software a while ago to attempt to fix the 100% bug, but I didn't back up my CDLC because I was never told the corrupt CDLC would be deleted. So I lost 90% of downloaded Corrupted CDLC. 

I downloaded it again today. And I downloaded the latest release (1.2.6.9). Here are the list of issues and I will try and explain what happened.

1. The selection system. I was in the duplicates menu, and I struggled to tick the boxes of duplicate CDLC's I had. It doesn't always register a mouse click for some strange reason.

2. The duplicates menu is not very helpful. I was looking through duplicate DLC and because I made a backup a while ago and Steam deleted most of my newer CDLC, I had to use an old backup. And the duplicates I had looked very similar. There were some with different version numbers, and some had the same name with a very hard to spot detail like an extra dot or dash. My issue with this menu is it doesn't display the date modified which it would help to have because I know which version is

recent. I have over 1600 CDLC, there were over 150 duplicates. (I'm not sure if this is a bug, but it won't pick up CDLC with a number in brackets, so masterofpuppets.psarc  masterofpuppets.psarc (1) and that's happened, it doesn't affect it in game from what I can see, but bothers me a little)

3. After fixing most of my CDLC, the corrupt CDLC's were archived luckily. But my issue is there isn't an easy way to access the corrupt files. I would like something on that menu that would allow you to open the folder containing corrupt CDLC's.

4. My four issue is to do with the entire program itself. I repaired CDLC and I archived my corrupt CDLC. The menu went blank, and then I closed it. Because I had done what I needed to do until something else came up. Then I tried to open it up because there was CDLC I was unsure if it was mine or another users, as I attempt to make better/fixed versions of CDLC (Also, unrelated, there's quite a few CDLC's out there that don't use Cherub Rock as the DLC tree thing). So I tried to open the CFSM software again, and I got an error 'Master Collection.Count = 0  The program will now shut down' And as a result, it didn't properly shut down. I found my countless attempts of reopening the software completely useless, as the CFSM process was still running in the background, so I had to close it via Task Manager. 

5. Every time I load CFSM, it asks me to set it up again? But the program launches normally alongside the setup?

I hope this helps you. I might use this more often. Here are things I would like to see in CFSM or outside depending on if it's suitable:

- I would like to see a tutorial on how to repair the CDLC mastery bug manually, or how to prevent it. And also how to repair corrupt CDLC's (If possible). 

- More customisability and accessibility (Being able to change colours, font, text size, etc.)

- An option to back up your dlc folder somewhere on your storage device (If possible, make it a scheduled thing, so every week, or day, depending on what it's set to, it will back up updated CDLC files)

Latest build can be found below 1.2.9.1 the beta 

http://ignition.customsforge.com/cfsm

be sure to uninstall the old one and not install over the top of the old

 

EDIT

 

 

 

 

Click on the repairs tab and select the ones in the image above, then click run selected options.

I have not used the 5 instrument fix as that was not in their the last time i ran it (cool addition) as the new remastered will only support 5 instruments including vocals (lyrics) so as some charters included both DD and NON DD arrangements and lyrics in their customs this will break rocksmith and cause it to crash due to having up to 7 arrangements lead x2 bass x2 and rhythm x2 then the lyrics . It appears we now have the option to remove a given path for ourselves without having to unpack them. I would opt to remove the NDD ones myself as we can now turn off DD in the game.

Hope this helps.

Thanks. I will reinstall it now. And I will make a backup this time. 

That's strange. I tested it yesterday and didn't get 100% mastery bug, tested it today and I got the bug again? Where is the fix for this?

@@SuperSonic note that CDLC without any chord won't have the 100% bug so you just got lucky on this one...

 

I'm no expert on CFSM and before doing anything to your CDLC, i would suggest to make a copy somewhere safe just in case. And if you encounter issue, please post something in the appropriate section or it might never get fixed if we don't even know the bug is there.

 

For the toolkit is strongly suggest you to upgrade to the latest beta to avoid any bug with the remastered version of the bug.

Chords? When I tested a previous version of my CDLC, it has the 100% mastery bug. Then I added two tones in editor on fire, as opposed to editing it in Rocksmith Custom Song Toolkit, and it fixed the issue for the CDLC I created. 

And I will not upgrade to the beta. The last time I did that, it decided to cause a whole lot of issues like being unable to locate Wwise, and then a whole lot of issues with generating CDLC's and saving packages. It's a broken mess to be honest. 

Sorry if I posted this in the wrong section. I don't know what section this post would go under?

@@SuperSonic http://customsforge.com/topic/33365-rocksmith-remastered-discussion-part-2/

 

The last update of that post was on the 8th of november and it was displayed during at least a month in the red banner up there that the 100% bug was fixable.

 

In fact you probably dl the latest beta of the toolkit which fixed your issue in the last CDLC you created.

 

The bug was purely on the Toolkit end.

I don't understand? I'm kinda scared to use CFSM again because it deleted a lot of CDLC I had when I tried to remove the 100% mastery bug, about over 400 CDLC's were deleted.

And my Rocksmith Custom Song Toolkit version is 2.7.0.0.6d0cdeda. 

There was a fix that was created, and not updated as an actual part of the game. Here is the link to the files needed to fix the bug. http://customsforge.com/topic/33138-rocksmith-remastered-cdlc-fix/?p=231225

I already have this. It doesn't fix the 100% mastery bug. 

I've been making CDLC for the past few months since the release of Rocksmith 2014 Remastered, and I've been sat here for months trying to figure out what could be causing the 100% mastery bug, and I came to the conclusion a few months ago you couldn't fix it. It just stayed like that, and if you were lucky the CDLC would not master 100%.

Here I am today, taking a break from tabbing and I decided to create a CDLC. And damn. This was strange to me. My Bonus Lead arrangement for this CDLC had no 100% mastery bug. I was trying to think what was different about it to all the other CDLC I've created. But why specifically did my Bonus Lead arrangement not have 100% mastery whilst the others did? 

I thought the only difference had to be the tones.

I went into EOF, fixed some notes I wasn't happy with when testing, and I decided to add two tones, one for default, and one to allow me to save the notes because for some reason EOF doesn't like one tone, you have to have two on each track to save each of them.

I generated the CDLC after adding generating DD for each arrangement, launched up the game, plugged in my guitar, played the CDLC I added the two tones on, and I played a bit of the song then skipped to the end because I was curious. There it was. No more 100% mastery. Awesome. I wasn't sure if there was an official fix for this, because I used the CFSM, but it deleted most of the CDLC's I played that had the 100% mastery bug. Which sucked, I didn't want any CDLC to be removed, just fixed.

So how long has this possible mastery bug fix been around? I assumed because it wasn't displayed above that it wasn't fixed?

I'm really confused?

That issue is caused by the lack of section inside the CDLC, you would need to edit the CDLC inside EOF to correct this.

Oh, right, okay, thanks. 

To briefly say what this is. It's basically where the camera isn't focused on the fret board. It's not zoomed out like it is in Joe Satriani's Satch Boogie. I can't see anything beyond a certain fret, and I'm not sure how to fix it. 

And when I installed the Customs Forge Song Manager, which I'm never using again by the way, it deleted half my CDLC's because they were apparently 'Corrupt' when all of them I have played since installing the Remastered update. And surprisingly, I found out some of the CDLC that was deleted had no issues at out. Where some did, and it's the issue I'm having here.

I'm going to link a screenshot of the issue. http://images.akamai.steamusercontent.com/ugc/107354018519765970/E85BE96560FB342E721B14467CD8BD4D910851EE/

I'm guessing it has something to do with finger positions and or dynamic difficulty. I might take it a step further and recreate all the CDLC's I've played that have this issue as of currently. 

At the bottom of your post when your mouse is on your post a report button with a yellow triangle appears I think thats the best way to handle those.  Not sure if its the same on smartphones.

I did do that, but I wasn't sure if the report system was abused or not, so I posted here to make sure this issue was resolved. Which it is, thanks! 

Sorry, I wasn't sure where to put this, but I accidentally submitted my CDLC "Crush 40 - Fuel Me" at least 8 times. I need all but one deleted please. 

Thanks in advance.