I know this is a duplicate of t/12415?hilit=stanza (in completed request), but it came to my attention that the nightcore mod adds a cymbal crashes every fourth stanza. As a result, I would like to be able to see when cymbal crashes will. I think a small number over every 4th stanza in the timeline would solve this issue.

Isn't this already shown in the timeline? in the form of X:Y Stanza or something like that.

You can. Although technically it's the timing tab, and not compose tab. It still works. Take the stanza and divide by 4 or cheat and look at a multiplication table.

Having to continuously switch to the timing tab and then back to the compose tab to change hitsounds (to sync with nightcore) is a large annoyance, especially since you need to scan the stanza of every section in the song.

You could count the stanzas. Each 4/4 measure has 4 stanzas. So every long white tick should be a multiple of 4. If it's 5/4 then it's a multiple of 5. I'm not entirely sure what happens when the red line changes though. If the measure changes, the nightcore sounds would not appear synced with the music or do they reset per red line?

Anyways I don't know how it would be possible to sync it up with Nightcore anyways. I don't believe you can change the effect of a storyboard/skin based on mod used. Nightcore = doubletime, which means that each stanza will be playing 1.5x faster than it will during normal play. How would you even compensate for this? 4/1.5 = 2.66666..... So every 2.666666 ticks is a stanza in Nightcore and every measure lasts 10.666666..... ticks. It would be easier, observing the BPM *1.5, and then changing it to that in the editor. You can then bookmark every long white tick in the timeline. When you're happy, change the BPM back to normal.

You're misunderstanding the use of this, nightcore mod adds in a built in cymbol crash every stanza (those made it known to me in this map p/1849871). In that linked post, he adds 3 timing sections to reset the stanza to make sure the cymbal crashes in nightcore sync to the finish hitsounds used. (Nightcore mod, still has a stanza every 4 tall white ticks which still at the same location as standard speed)

Sure you can count them, but why do we want to deal with that inconvenience.

A stanza is 4 beats, i think you're misunderstanding the difference between beats and stanzas @TVO

Nevertheless, i dont see the reason to count the ammount of stanzas in compose? all you need to know is when a stanza starts, which would be, the long white tick.

Woops, now I got myself confused. What I am talking about is every 4 long white ticks (those kept saying those are stanzas)? Just try playing the song I linked above with nightcore mod. Play it once with all of the timing sections, and play it again with only the first timing section. You'll see what I mean (If you only have 1 timing section, you'll have a cymbal crash here 00:08:153 instead of 00:05:971).

yes, every long white tick is the start of a Stanza, so if the cymbal crash happens every 4 stanzas, then this feature request would make sense.

Edit: I got confused about the beat/measure thing, because it compresses the timeline in timing mode.

I guess. I just don't think that your idea will fix anything. Dividing a song every 4 measures with bookmarks doesn't take that much time and your idea doesn't even solve your issue. If every white line is numbered, you still have to could the white lines. The numbers are meaningless in this case. If you're not using the numbers to find a multiple of anything, then there is no point in having the numbers there.

The christmas collab I'm working on, I had to divide the parts by 4 measures each. It didn't take me very long to count 1,2,3,4 bookmark. 1,2,3,4 bookmark. It probably takes less than 30 seconds longer than the length of the song itself. It would take less time than it would to divide a stanza number by 4.

I think what you want is an indicator every fourth stanza, not every stanza. I'm not sure I agree to this as there are many more important things they could add to the design tab, and aimod. Only a handful of people would ever find this useful unless perhaps there was an option to skip every four measures through a map with a keypress. I would fully support this if that was included, because it would add more functionality to the base idea that takes a small amount of time to do.

This is going offtopic, but really I feel I must bring up the non user friendly interface of the design tab. Precisely making adjustments in design tab wastes so much time and outside of checking the .osb, there's no way to check set parameters for scaling, coordinates, start, end positions. Doing anything every x anything in the design tab takes much longer than what you're requesting unless you know the code well, and how to use it (but that has to be done outside of the design tab). Design mode needs an overhaul if we're considering things that unnecessarily waste people's time.