FAQ
Frequently Asked Questions
Practical guidance on how SampLab Pro operates in the browser, including technical limits, conversion mechanics, and realistic expectations for every tool.
Audio to MIDI
How accurate is the Audio to MIDI converter?
The converter uses Basic Pitch to estimate note pitches and timings. It performs best on isolated monophonic melodies or clear single-instrument recordings, while dense polyphonic arrangements often result in misidentified or extraneous notes. Output notes are estimates that should be audited and refined in a sequencer.
What audio file sizes and lengths are supported?
You can process audio files up to 50MB in size with durations ranging from 1 second to 10 minutes. Audio decoding depends entirely on your browser, so supported file formats match your browser's built-in audio codec capabilities.
Are audio files uploaded to remote servers for transcription?
No upload is needed for this transcription: decoding and note detection run in your browser. If you choose to save the result to your private library, the exported result is uploaded. AI tasks have a separate upload workflow.
Analysis & Filtering
Is the Frequency Band Splitter an AI stem separator?
No. The Frequency Band Splitter applies standard frequency filtering rather than source separation. It isolates frequency bands such as lows, mids, and highs, but cannot extract individual vocal or instrument stems from a mixed track.
Can I rely on automated BPM, key, and chord detections?
BPM, musical key, and chord predictions are algorithmic estimates paired with uncalibrated confidence scores. Complex harmonic content, tempo drift, or unusual tunings can skew results, so you should always verify the figures by ear.
Why does a particular audio file fail to open or decode?
SampLab Pro relies on your browser's native Web Audio decoder. If your browser lacks support for a specific audio codec or container, the file cannot be decoded locally.
MIDI & Notation
What sound engine powers the MIDI to WAV tool?
MIDI playback and audio rendering use three lightweight oscillator voices rather than realistic soundfonts or sampled instruments. Continuous controllers (CC) and pitch-bend messages are not supported.
What restrictions exist for rendering MIDI files?
The tool accepts MIDI files up to 50MB, handles renders up to 10 minutes in length, and caps processing at 20,000 notes per file to prevent browser memory exhaustion.
Are generated lead sheets ready for publication or engraving?
No. Lead sheets provide draft notation rendered in C with accidentals for basic structural reference. They are designed for quick chord and melodic review, not publishing-grade sheet music engraving.
Service & Independence
Which tools are free, and which use credits?
The browser audio and MIDI tools run on your device and do not use credits. AI lyrics, AI songs and stem separation use credits from a monthly membership or a credit pack.
Where does data processing occur across the site?
The original audio and MIDI tools process files locally in your browser. Saving a result or starting an AI task uploads the selected content for that action. Task results remain private; saving to the library is a separate action.