GetTheLedOut

@@albatross213 I can at least confirm that notes and slides up to the 24th work just fine in-game. I came across this in testing a forthcoming custom, and according to PC Plum, you can also find evidence of this in his Pink Floyd - Echoes (Pompei) custom. This means I'll need to go back and fix my Layla custom :D Perhaps it is time to update the warnings related to this? Was/is this a problem in RS1?

http://customsforge.com/topic/901-how-to-use-custom-dlcs-in-rs2014/

Sounds like that's exactly what it is. What are the specs of your processor, RAM, graphics card? Are you running any other applications while playing Rocksmith?

If you're describing what I think you are, there was an update a while ago that fixed this. You may want to update to the latest version of the Toolkit. If had to with the Rocksmith showing a slightly different tuning frequency that what was shown in the Toolkit. If I've misinterpreted your problem, then please do clarify it for me :D

As far as Rocksmith is concerned, there's not really a good way to distinguish between pinch harmonics and the "harp harmonics" that you're describing. The best way that I know of would be to chart it as a normal pinch harmonic and and then perhaps describe the technique in the "author notes" section when you add it to the database. Hopefully Rocksmith's note recognition gets it right, but if it doesn't, you can use the "ignore" status on the harmonics so that they don't count against in the scoring. They'll still be displayed on the note highway, just not scored. Alternatively, you could chart the fretted note along with a tapped note an octave higher, designating the tapped note with an "ignore." The problem with this is that it would cause the in-game camera to zoom way out in order to view both notes. It might then be difficult to read/play. You'd also have use the "ignore" status on the tapped notes, since you're not really tapping there - just touching the string. Maybe try this method first, and after some testing, see if you prefer the first method. In which case, you can just delete the octave tapping notes. If anyone else knows a better way, then please do chime in.

@@raynebc Might it be worthwhile to have EoF warn users upon saving if there are linknext slides which carry over into another section? See above.

There are a couple of problems with stuff like that... Some charters, like myself, create CDLC in nearly an hour, so the updates would be pointless, in that instance. Another problem would be those who start working on a CDLC, and update the 'progress bar', may not even finish the CDLC. So if someone else was going to make it and checked the progress bar, saw that it was like 50%, that someone else would just move on to another project, assuming that the CDLC would be made. In all reality, it doesn't take very long to make a CDLC. IMO, If someone said that they were going to work on a certain song one day, I would expect it to be done on that day. Cheers. The time it takes to make a CDLC depends on your method and how much attention you pay to small details. I can't recall the last time I made a CDLC in less than an hour. Creating your own arrangements, transcribing by ear, or simply fixing mistakes can take much longer. Even if you have a perfect GP file (which almost never happens), there's a fair bit of fiddling in EoF required in order to optimize things for Rocksmith. That could be slides, bends, tone changes, note sustains, arpeggios, hand shapes, sections, etc. If it only takes you an hour or less, there's a good chance you're just importing the tab and then skipping right to the Toolkit steps. That being said, the "progress bar" suggestion could be mildly useful, but it would never be an indicator of when a CDLC would be finished. People work in their spare time and obviously don't make any money creating CDLCs. Just because a song is "in progress" doesn't necessarily mean it will ever get finished. IMO it would be more important to have a better way to update and/or clean up the request section. There's so many songs in there that are being requested, while there are finished versions already in the database. Also, there's no way (at least that I know of) for the list to be updated when someone finishes a requested song.

Thanks! Now that I know this, I can just author the sections to work around it.

I've recently been having trouble with linknext slides when using the DDC tool. Some slides will display as if there is no linknext status applied, and I can't figure out why. They display as normal when DDC is not used. Here are the .xml files, one with DD, and the other without - https://www.dropbox.com/sh/t08lre7iq6m1ev4/AACBt9J7phuxX5O6oc8JdzDBa?dl=0 The slides that are not working properly are on the G string, sliding from the 7th to the 9th fret - like this: "7/9---" The slides occur at the following timestamps: ~8.5 seconds, ~12.5 s, ~16,9 s, 21 secs. One or two of them (sorry, I forget which ones) do not display correctly, while the others do. Also, the first phrase doesn't seem to be leveling properly, but I could be wrong. Is it ok that the first section is 5 measures long (because of the lead in measure) and yet I've used a phrase length of 4? All the other sections are either 4 or 2 measures in length.

This is what I was thinking too. Though we've struck out a few times so far :D If you used the DDC creation tool, you may also want to try creating the song without DD to see if the DDC tool is causing the problem - in which case @@Chlipouni would want to know.

Are there actually sections added, or just phrases? It needs to be a section in order to be selected by riff repeater. When a section is added to the first beat, it will display with a red line over the beat, but I can't tell from this picture because the green "seek" line is covering it. Regarding the play counter, I think it may not count a playthrough if there are no sections, but I could be wrong.

Well, you would only have to re-import the arrangement xml, assuming I'm correct. The rest the rest of the fields can be left alone after loading your template

My guess would be that you need to remove and re-import the arrangements in the Toolkit. The toolkit might use a cached version of the arrangements, though I'm not 100% sure on that. Or you may be using the wrong .xml (i.e. if PART_REAL_GUITAR_22 is your lead arrangement, make sure you set it that way in the Toolkit). If you're using DD, you'll also need to regenerate DD with the DDC tool. EoF only saves/updates the original PART_REAL_GUITAR etc. xml files, not the ones that DDC creates. There is no data being stored within the .wav, .ogg or .wem, since those are just audio files. No need to delete them and recreate them, really. This almost goes without saying, but make sure you've saved the project in EoF after you've made the new changes. :D

99% of the time it's a case of not following the tutorial correctly. Most likely the .dll is in the wrong folder or there are multiple instances of the .dll in your root folder (with names that end in (1) or (2)). There's 100's of topics for this problem, all with the same solutions...

Since the 4-14-2016 hotfix, I've noticed that using the CTRL+Z undo function while the waveform graph is in view causes the waveform graph to disappear. Almost as if the "undo" is also being applied to the waveform itself. It's happened in a couple of individual projects, so it should be quite easy to replicate. If not, just let me know and I'll provide a project for you to test with.

@@avdocatwork As far as I know, he wrote most of the music - at the very least. He definitely doesn't get the appreciation that he deserves. Those two songs have been out since the days of Smithy's Anvil, so a lot of people had them even before CustomsForge was founded. The fact that they're classic rock staples coupled with the fact that I've made a few updates certainly padded the numbers :D

Hey gang! So this is where all the heavy hitters hang out? *takes off shoes and puts feet up* :)

Yes, you can. Have you checked the tutorials section? There's a tutorial there that shows you how to do this.

By root folder I'm guessing you mean the Rocksmith2014 folder that you go into under SteamApps > common > Rocksmith2014? If so, I did do that. That didn't change anything. The video didn't really explain much about the root folder to begin with. Yes, it's the one subfolder back from the /dlc folder - it contains the game's .exe file. In that case, make sure that the file name of the .dll does not end with a "(1)" or "(2)" - it does, just delete that from the filename. This will happen if you've added the .dll multiple times, and is one of known causes of your problem. If you've done things correctly, you should see a small black cmd prompt window open up when you launch Rocksmith. You'll also want to read the rest of that tutorial if you haven't already.

Without seeing the tab I can't say for sure, but chances are, it's in B Standard for a reason. Any notes that are below a low E (or simply below the pitch of your open E string in your desired tuning) would need to be transposed an octave up or left out completely. It usually requires a fair amount of musical acumen along with a working knowledge of EoF. If you're not comfortable doing this on your own, then it may not be worth it to you to go through all of the steps. If it's something you'd be willing to try, here's a broad overview of the steps: 1) unpacking the CDLC with the Toolkit 2) changing the notes and tuning (either in Guitar Pro or directly in EoF), then saving 3) re-adding the arrangement(s) to the Toolkit, with the new tuning 4) re-generating the .psarc

It sounds like you don't have the .dll file in the correct folder. It needs to be in the root folder, as per the tutorial: http://customsforge.com/topic/901-how-to-use-custom-dlcs-in-rs2014/

I think it has something to do with steam not "being aware" that you've purchased that Iron Maiden DLC. I've seen this pop up in other threads in this sub-forum, but I forget the answer. You may want to look back on some of the old threads that something like "CDLC won't work" in the title - there is a lot of them though! Perhaps you can try downloading the Iron Maiden DLC again on your new PC?

Have you you tried converting the ID's of the CDLCs to the Iron Maiden song that you've purchased? You can use the Toolkit to do this. If they have not been converted to an official DLC that you own, then they will not show up in your song list.

"We're Gonna Groove" is now released. Also, I've updated the very bottom of the OP with a special announcement of sorts.

Ahhh ninja'd by @@raynebc :D