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 }}
Repository navigation
The empty studio draws seven lanes against six faders, drifting apart #661
Open the app and look at the stack before loading a track. The mixer shows six stems; the waveform column beside it draws seven flat lines, at a different spacing, so a stem's name and the line for its waveform are on different rows by the third one and the last line has no fader at all.
Two causes, both only in this state
The placeholder lane is a hardcoded height: 48px in waves.css, while every mixer row is sized from --lane-h, which is 77px on an empty studio. The two columns run at different pitches from the first row.
There is one placeholder too many.renderPlaceholderTracks builds one per stem plus original, but the mixer hides its original row until a job is loaded: applyStemSelectionFilter is called with STEM_NAMES, and original is not in that set.
Why it survived
Loading a track has always been fine, and the existing lane-alignment.spec.mjs covers that case thoroughly. It is the state before a track exists that nothing was checking, which is also the first thing anyone sees.
Constraints for whoever fixes it
--lane-h is the row, and a row is a lane plus its 2px separator, so the lane is the variable less the separator. Anything that redraws a row should derive from that rather than carry its own number.
The count has to follow the mixer rather than be a second list, or the two drift again the next time the set of rows changes.
Activity