firekorn

No, it's not okay, our rules clearly states that.

Those are only a small portion of what I could screenshot that are problematic (there are also some issue that repeats everytime the same riff is played) because I don't think sending dozen of screenshot is helpful to showcase the different problem that can be seen by any user. It does make for what I would tend to qualify as a "bad experience" as a user of CDLC and what the standard aim to fix over time. Sure some of those things can be fixed very quickly, that's also the point of the report so that you are aware those issue exist as anyone can miss a spot here and there in the process. It is also why we don't delete content or that the initial report don't add the red flag anymore and many other changes we've made for that process recently. We also give as much time as ones wants to fix those, you just have to keep us informed. We do try to adapt the report system so that it doesn't feel as crushing but it also means charter have to make "better" content than they did before as most just weren't good in any kind of way. It's not easy, we know.

We've offered to help and you refuse to join the discord for some reason to get some help from others. All of the issue you are facing can be solved with help from more experienced people that are willing to help but you have to reach out a little to find that help. And yes, we play and look at the CDLC live because it sometimes more practical than simply loading it into the Builder. As for being "new", you've been at it since early 2019 and the info about managing FHP properly has been out before you started. But again, none of those are "minor" issues as far as we are concerned, it seriously hinder the playability of your CDLC and needs to be adressed.

@ gamestabs3 Let me know which of those screenshot do you think showcase minor issues and which are major so that we make sure we talk about the same things : Slides but FHP stays on the same fret, also impossible to tell if the player should play the C#5 again or play a D5 instead (8 fret partial barre) First finger but FHP says it should be played with the middle finger instead Note out of the FHP highlight Massive stretch that doesn't make sense I haven't shown all instances of those different issue in your latest CDLC (which was reported "notes outside of lane" as well as "bad finger position" amongst other things). Do you want me to continue to talk about the issue I can see in a single playthrough of your CDLC? While I do agree that some report may be nitpicking about some stuff. I also don't think your CDLC are being reported for "minor" issues. We are trying to help but you need to also do some work on your end for all of this to work.

@ GoatHerd The onus always was and will always be on the creator of the content itself. That said, the time pressure can be changed or even alleviated, we already do this on a case by case basis when requested in the report conversation but I'm all ears to how we could make things better. I also can't stress enough that nothing will go into oblivion, that's why I repeat constantly that deletion isn't a thing and that we have other solution that are far less radical currently in place. We are really making an effort to improve the process for all but that also means we needs individuals feedback about it to tailor the details over time. When it comes to people that requested fixes through comment, they have been largely ignored. We still see content being reported just now while the issue was talked about in comment back in 2014, sometimes with the charter promising a fix "soon". That clearly isn't working. The report system has been in place for many years already but was largely unused for a long time for different reasons. We are trying to change all that so that feedback left through comment aren't simply ignored and that report are more actively used to keep the database cleaner than it used to be. But those changes aren't painless or easy or fast but we are engaging with users to adjust the course as we are trying to change it all. As for requiring any user to have published chart to report, that's a bad idea in many ways. Report are also about broken link and bugged chart and this does not require any charting knowledge to report. This idea has too many downside and would require us to create too many loophole and it'll also create some problematic incentive for the community. CF has tons of chart because we've been letting anyone publish anything but it also created a reputation alongside it. It was perfectly fine early on but as tools have changed, knowledge have been gathered, there is a time where starting to have some minimum requirements become the next logical step to aim for a database of content that is more enjoyable for all. I don't think those standard are that extreme though maybe some of it could be altered. It's not an easy discussion but we are open to have it with whomever wants to offer their feedback about it. We do understand that there's a trade off and that it'll slow the publish rate of content but that's something we are okay with at the moment. As for having two different categories, it's a logistical nightmare, a dev nightmare and we just don't have the ressources for such idea. We are afterall doing it for free on our spare time and some solution are out of reach sadly. @ JamesPrestonUK It is a bug when a mod/admin look up old report, you can ignore those message as there's no risk of anything happening. I'm sorry for the trouble this kind of notification brings.

@ GoatHerd Can you point us toward cases of BS reports? We do reserve the right to action users that abuse report but that's not something we've seen as necessary so far given what we've seen. If we missed something there, feel free to tell us. I'm not sure what prevent you from making your content available on CF or what kind of penalties you think are too high currently but if you were to expose the problem clearly, I'm sure we could work out solutions to make as many users happy as possible.

@ GoatHerd Point to me example of what you are referring to and talk to us about it when you see it and we can sort it out together. That said, anonymous reporting aren't all that frequent at this point and admin and mod are always aware of the user that made the report so we can act if it is ever needed. I'll repeat again that deletion isn't a thing, we've put in places alternative options and deletion only really happens for broken link at this point. I'd be curious what you feel would be more appropriate penalties too. We are open to alter how we work and handle things but users also need to reach to us if they feel things aren't working so we can work on a solution.

@ fripponomic I'll reiterate what I've said on the report discussion itself : A comment back from 2016 already mentioned the issue. It also has been something that has been mentioned in the earliest set of rules for content to be properly named both in game and on the ignition record. It won't result in deletion of the content. This would take you literally a minute to fix but you instead chose to go for another round of discussion around the topic. You know the options we offer, we can discuss this calmly or you can keep on complaining about report. The choice is yours. @ Sniper Reload3d What you say is already what we do. Content isn't deleted for that but that doesn't mean the report is wrong and there was rule back in 2014 that people already had to uphold and we will keep on enforcing the rules of the time the chart was made. I don't know how else to say any of that. Our process and rules have changed already.

The dev have put a hard limit in the recognition system below C1 so the B0 on bass will never detect properly without tricking the system to go around that limit. Which is why CDLC with tuning below C need to use the "low bass tuning fix" which is a trick that has been found to bypass that limit but it doesn't fix the inherent problem the detection system has that low which is the whole reason the dev decided to put that limitation in place. There are still plenty of CDLC that don't include that fix though which makes tuning and detection entirely impossible for the low notes and those can be reported. But all of this has nothing to do with the bass hardware/strings. This is just how the software is designed.

We have permanently suspended Lil Ramen Noodle's account for repeatedly scamming people who commissioned charts from him. While we don't know the full extent of the problem, we know this was a frequent occurrence. We have issued temporary bans and restrictions over time, which have helped motivate some refunds and completion of work. Ultimately this policy stopped being effective, and we apologize for not suspending his account earlier. Additionally, we have permanently suspended 65 days for monetizing charts behind a "Ko-Fi". Our rules are clear and stipulate that CDLC linked to on CustomsForge should not be locked behind a paywall. His ban is also effective immediately. Using a new Ignition feature, all charts belonging to Lil Ramen Noodle and 65 days have been moved to our Abandoned user. This user's purpose is to store charts for users who have requested that, or for instances like this when accounts have received administrative action. It's possible for any user to request ownership of an abandoned chart, just contact a staff member. Charts are given out on a first come, first serve basis. Taking ownership makes you liable for issues with the chart and requires you to update it to match our 2025 charting standards. We are grateful to all users who have taken the time to report these issues with Lil Ramen Noodle. While investigating and actioning users is a time-consuming process, we do our best to ensure a safe environment for all our users.

I'm not sure which CDLC @ ErikOfEngland are reffering to but I find no chart that have been deleted for such reason in any of the report. He did report a CDLC that was in Eb std but with a missing capo resulting in a very problematic out of tune situation but that was resolved and the CDLC is still perfectly available on our database. It was a valable report and the charter fixed the CDLC. We are aware of the frustrations the report can cause but we are indeed changing things in how we handle the process behind the report as well as how it is displayed through Ignition. Deletion of CDLC is not the norm after a report and there is always a grace period to give both mod and charter time to take actions before anything automatic happens. I know the charting standards set at the beginning of 2025 have caused a lot of pushback for many different reasons and that there is an uptick in reports (not all being warranted) following that change but we are available to talk over the situation calmly to find the best compromise possible. I especially hope we can resolve both @ fripponomic and @ Lukkeren situations as nicely as possible to avoid any potential loss for the community.

So now that the week is over, a bit of some trivia and info on the Blue Stones song. It is a 2 man band, one drummer and one guitarist/singer so the bass is technically made up to mimic part of his signal split to fill in that role live. Lead and rhythm has only very few different spot as there isn't major split in the recording as it is meant for a single guitarist anyway. As for the guitar parts, the intro uses what is called "hybrid picking" by using the pick for the low string and finger picking for the high strings (since holding a pick leaves 3 fingers free). An important part to play this is also to hold the whole chord shape. It's the usual barre chord as played for the rest of the song so no big surprise past the first playthrough. They've also just released a new album last week called Metro which is worth a listen.

Software Alternative IN PROGRESS 1. Charter (alternative to EOF) The Charter is an alternative tool to EOF. Most concept behind chart creation are shared accross both tool as they both have the same end goal of making content for RS. II.Getting Started That is where the fun begins ! You know which songs you wanna play in your favorite music game ? You have an audio file to work with ? You better do cause you will need it directly ! After Starting the Charter, create a new project (File => New project) and you will need to indicate which audio file you wanna use. https://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKhttps://imgur.com/Iws8BfKThen you can select where the work folder will be, either the folder where the audio file is or inside a designated work folder that can be configured. 1. The basic for a good project I will start to get into some technical stuff about music theory in there so be warned ! I’ll try to keep it as basic as i can but we are dealing with musical element here, so there’s no way to cut through some of that vocabulary. a. Set the beatmap to the correct tempo all along the song First the beatmap is what define the tempo, the beat of the song, you can see it in any music game as the white bar that lay horizontally on the highway, some are stronger because they are the first beat of a measure, other are lighter because they are the other beat inside the measure. It is the fundation of a music, it is the metronome that assure you that everything is correctly set in time all along the music. It’s also an important visual cue once in game. It allow players to see how close are note from each other. I can’t stress enough how much this is vital but it is also a part that requires the charter (the one creating the chart for the game) to have atleast a small cue about what the hell a beat is, a measure and how music revolves around it. Many things can make this step a nightmare for a lot of user : How well was recorded the song in the first place How many variation of tempo are in the song Lack of elements that clearly mark the tempo (kick, snare are usually the most obvious cue) I’ve made a long piece about how i do this myself over CustomsForge forum and other users have shared different ways of getting this done properly, there’s no easy and perfect way so i’ll just lay some link for all of you to take a good look at it and try what you prefer : http://customsforge.com/index.php/topic/5099-how-to-sync-your-beat-map/ http://customsforge.com/index.php/topic/856-tutorial-for-proper-gp-tab-sync-sectionphrase-authoring-and-more/ http://customsforge.com/index.php/topic/2393-how-to-get-beat-map/ http://customsforge.com/index.php/topic/5136-using-beat-markers-to-sync-in-eof/ b. Have enough « silence » at the beginning of the song The silence at the beginning vary a lot from song to song, if it is slow or fast, have an intro with or without guitar or bass but one rule is to follow here to have the best Rocksmith experience and is ODLC standard : The first beat should be at the 10 seconds mark! Since the beat map is common to all instrument that will ensure that everything doesn't start too early in game so that the player will have enough time to get ready. But why 10 seconds? Because Rocksmith need some time to load all the element needed for the song to play correctly and rest assured, you won't see the full 10 seconds of it! In fact you will rarely see more than 4/5 seconds of silence before the beat map appear. One important detail here is that even if the beat map start at 10 seconds, there won't be any note at that point in time. There has to be at least 1 full empty measure (usually 4 beat but for more detail, i suggest to read about time signature and their signification) that will mostly be used for count in event. The charter has a function made to get it right in a simple step : This function do two things at once : - Add the 10s of silence needed for RS - Add as many empty bar as the user indicate to have a count-in In case 1, you don't need any extra bar so you'll input 0. In case 2, you'll add 2 bars and in the specific example, 1 will be enough. My screenshot above fits the 1st case so I'll add 2 bars (written with version 0.19.16)

That seems like an error in regards to the audio file in the original psarc. Not much else to work from with those error.

FHP (Fret Hand Position or anchor) do show which finger to use for individual note, it is the whole purpose of that system to begin with and defining those properly will heavily reduce the cases where FHP somewhat fail to give that information.