This has been brought up before, but the original thread didn't focus on this.
~Chances are, you've seen a "Barcode Beatmap" before. These are beatmaps that use Inherited Sections to insert a different slidertick into the middle of a slider. For Example: Jumper /http://osu.ppy.sh/s/21130/ Heck, even I have one. However, after looking at the process, I think that it should be much, much easier.
~My Suggestion is that we implement a different method to interact with the slider ticks. A more convenient way. We should be able to double click a slidertick and apply a hitsound (whistle/clap/finish).
~You might be thinking: "No, why would I want to apply a regular hitsound to the slidertick, it would sound terrible." I would agree with this statement. I suggest though, that we would be able to set different files for each slidertick hitsound similar to how we normally insert custom hitsounds.
~Chances are, you've seen a "Barcode Beatmap" before. These are beatmaps that use Inherited Sections to insert a different slidertick into the middle of a slider. For Example: Jumper /http://osu.ppy.sh/s/21130/ Heck, even I have one. However, after looking at the process, I think that it should be much, much easier.
~My Suggestion is that we implement a different method to interact with the slider ticks. A more convenient way. We should be able to double click a slidertick and apply a hitsound (whistle/clap/finish).
~You might be thinking: "No, why would I want to apply a regular hitsound to the slidertick, it would sound terrible." I would agree with this statement. I suggest though, that we would be able to set different files for each slidertick hitsound similar to how we normally insert custom hitsounds.
normal-slidertick-whistleIf this was implemented, it would make adding custom hitsounds to the sliderticks a much easier process. It would also allow mappers to make more complex slidertick patterns than we have now (since you could represent multiple background instruments on a slider at the same time).