ffalsum: a music catalogue with a persistent player.

The saved opening uses an oversized black serif wordmark on a warm off-white background. Small monospaced labels, a numbered vertical rail and fine dividing lines organise the surrounding information. The contrast between expressive type and precise controls gives the catalogue a recognisable character without making every element equally loud. A long player bar sits along the bottom of the composition.

The player is part of the opening rather than a tool hidden several steps inside the catalogue. Its track name, transport controls, time and waveform make the listening state visible. This matters because the visitor is exploring audio, not simply comparing cover images. The design gives the main activity a stable place while the rest of the page introduces the producer's world.

The catalogue counts are project-scope information, not evidence of agency sales. Likewise, commercial wording visible in an archived concept screen does not mean HeadPills operates a real checkout for the producer. The distinction keeps the case useful: it can demonstrate a detailed music interface while being clear about ownership and the experimental status of the work.

Project records describe audio living in a persistent shell outside the page router. In practical terms, moving between the site's sections does not require rebuilding the player. The same track and playback position can continue while the visitor examines another part of the catalogue or a licence explanation. That continuity is the interaction problem this part of the concept addresses.

This is more precise than promising that the music never stops. Playback can still be affected by the visitor, the browser, a reload, a connection problem or leaving the site. The recorded design concerns navigation inside the experience. A clear case should describe that boundary rather than turn one architectural choice into an absolute guarantee about every possible listening situation.

For a comparable music website, we would define which transitions preserve playback and which actions intentionally change the track. Choosing a filter, opening an information section and selecting a new song are different events. If all three reset audio in the same way, the interface makes exploration harder. If none communicates its effect, a listener can also lose track of what is currently playing.

The project record describes an offline pass over each track to measure its beat grid. Elements intended to land on musical beats read that prepared grid rather than relying on an unrelated repeating timer. The distinction is meaningful: a generic pulse can continue at the same pace while the recording's structure changes or a different track is selected.

This does not mean every movement needs to react to audio. Navigation, reading and playback controls still need a stable hierarchy. The useful question is which visual events become clearer or more expressive when they follow the music. In a comparable brief, we would identify those moments before adding motion, instead of making all controls move simply because beat information is available.

A prepared grid also creates content-management requirements. A newly added track needs the corresponding data if it is expected to participate in the same behaviour. The interface needs a sensible presentation when that data is absent. These are implementation considerations for a similar project, not a claim that every music format or arbitrary uploaded recording has already been tested in this concept.

The recorded catalogue includes BPM and pack filters, with name or collaborator search described in the project material. These are different routes into the same collection. A listener who knows a title can search directly; someone exploring a musical pace can narrow by BPM; someone interested in a release can use the pack structure. The interface should not require all three kinds of knowledge at once.

The saved catalogue screen also presents the current track through a character-map visual. That expressive layer gives the project its own appearance, while the textual metadata keeps the material identifiable. The map is not a substitute for a readable title or a usable row. A music catalogue benefits from both an evocative presentation and an ordinary way to find something again.

For a commissioned version, we would agree the metadata before styling filters. Titles, collaborators, tempo and pack membership need consistent fields rather than information hidden inside free-form descriptions. The client also needs a defined process for correcting an entry or adding a release. A filter system is only as useful as the catalogue information it receives.

According to the project record, interface sounds were cut from the producer's own beats. This connects small feedback sounds with the larger audio identity. It avoids treating the player, page transitions and controls as unrelated layers. The case attributes the source music to the producer and the interaction treatment to the studio, rather than claiming authorship of the underlying recordings.

Sound also needs restraint. A visitor may be concentrating on a track, and feedback should not obscure what they came to hear. The saved opening includes a sound control, making sound an explicit part of the interface. For a similar commission, we would agree which actions produce feedback, how it relates to playback volume and how the experience remains understandable when those effects are disabled.

The recorded scope includes a licence page. Its role within this concept is to provide a place for explanations relevant to the catalogue. A website layout cannot itself establish permission to use a recording, and this case does not grant such permission. The producer's ownership and the studio's role remain separate from the design of an information page.

For a real commercial implementation, the owner would supply the approved offer, usage terms and purchase process. The web team would then connect those materials to the appropriate track or pack and make the next step clear. That is a separate scope decision from building a persistent player. An attractive catalogue should not be described as a complete music business merely because it includes a pricing or licence-related screen.

ffalsum demonstrates a persistent player, structured discovery, musical motion and a distinctive typographic direction around a real catalogue. It remains an explicitly labelled studio concept with no agency music sales claimed. For a comparable project, the useful starting material is the catalogue, ownership information and the intended listening journey; those decisions determine the interface more directly than a generic template for a music homepage.