AJ Kerezy
Description:
Allow users to define the filenames of recordings created in Loopy Pro, instead of relying solely on automatically generated names. Users should be able to type a custom name before recording, and/or define reusable filename templates (with wildcards) that Loopy applies automatically when rendering or recording to disk.
Problem:
Currently, recordings made in Loopy Pro (for example, recording the main output, buses, or stems) are saved with automatically generated filenames. While this works technically, it has several practical drawbacks:
  • Hard to identify later:
    Generic or timestamp-based names make it difficult to know what a file contains (“Recording 2025-11-20 23-08”, “Project Render 3”, etc.), especially when quickly browsing in the Files app, DAWs, or other software.
  • Poor organization across sessions:
    When exporting multiple takes or songs from different projects, all recordings end up with similar-looking names. It becomes harder to know which recording belongs to which song, section, or show.
  • Inefficient in professional workflows:
    Users who archive recordings, send them to collaborators, or import them into DAWs often need to rename files manually to reflect:
- Song title or project name
- Section (Intro, Verse, Chorus, etc.)
- Take number
- Date or venue
  • Risk of confusion and mistakes:
    Manual renaming outside Loopy (in Files or on a computer) is error-prone and time-consuming, and it breaks the nice directness of a live performance workflow.
In short, the app decides the filenames, but users—especially those working professionally—need more control to keep their recordings organized and meaningful.
Proposed Solution:
Add flexible, user-controlled filename options for recordings:
  1. Simple per-recording name field
- In the “Record / Render” panel, provide a text field such as:
- “File name:” (default pre-filled with the current auto-generated name).
- Before starting a recording, users can:
- Edit this name manually (“SongName_Verse_Take01”).
- Loopy then saves the resulting file with that exact name (plus extension).
  1. Filename templates with wildcards
- Allow users to define reusable filename templates that can automatically include:
- Project name (
{project}
)
- Date and time (
{date}
,
{time}
)
- Section or group name (
{section}
,
{playgroup}
if available)
- Output or bus name (
{output}
,
{bus}
)
- Take number (
{take}
)
- Example templates:
-
{project}_{section}_{take}
-
{date}-{project}-{output}
- Provide a small “Wildcards” helper list or popup so users can see which tokens are available and insert them quickly.
  1. Per-project and global defaults
- Global default template in Settings (applies to all new projects).
- Per-project override so each project can have its own naming pattern:
- e.g. “BandName_{date}_{section}_{take}` for a live show project.
- Option to quickly reset to the default template.
  1. Auto-increment take numbering
- When a template includes
{take}
, Loopy should:
- Automatically increment the take number when recording repeatedly with the same base name/template.
- Ensure unique filenames and avoid overwrites, e.g.:
-
SongA_Verse_01.aif
-
SongA_Verse_02.aif
, etc.
  1. Compatibility and safety
- Ensure generated filenames avoid problematic characters for common file systems and cloud services.
- If a user types disallowed characters, Loopy could:
- Show a small warning, or
- Auto-sanitize them (e.g. replace with
_
).