You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
I don't know much about music composition, but from what I understand, the fact that every section in an FNF song chart is exactly four beats/16 steps long means that certain types of songs don't quite work properly in terms of camera panning.
The proposal in #65 may make this possible. It makes the note data not tied to sections at all; instead, the thing that controls the camera is a set of song events, which are customizable.
I believe part of implementing #65 while still making the chart usable involves allowing for the automation of a setting the camera every four beats. A change here would involve a visual indication of where and when "sections" of the music chart end and changing where these automated camera switches happen.
Please correct me if I'm wrong here.
The text was updated successfully, but these errors were encountered:
I don't know much about music composition, but from what I understand, the fact that every section in an FNF song chart is exactly four beats/16 steps long means that certain types of songs don't quite work properly in terms of camera panning.
The proposal in #65 may make this possible. It makes the note data not tied to sections at all; instead, the thing that controls the camera is a set of song events, which are customizable.
I believe part of implementing #65 while still making the chart usable involves allowing for the automation of a setting the camera every four beats. A change here would involve a visual indication of where and when "sections" of the music chart end and changing where these automated camera switches happen.
Please correct me if I'm wrong here.
The text was updated successfully, but these errors were encountered: