Mark with precision
Scrub to a frame, set a label, choose a cue category, and add notes for your editor or sound designer.
PIXELOKAY · CREATOR AUDIO TOOLS NEW STUDIO
Turn audio moments into a precise, editable sound-effects cue sheet. Find transients, mark by ear, sync timestamps to your video edit, and export markers ready for your workflow.
YOUR SOUND-DESIGN WORKSPACE
Listen · Mark · Refine · Deliver
Cues marked
0Confirmed cuesDetected events
0Review suggestionsSource duration
—Audio / video timelineProject format
30 fpsNon-drop-frame timecode04 / PREVIEW & TIMELINE
Import a file or try the example to see a waveform.
No media loaded. Waveform availability varies by codec. Manual cue marking remains available for playable media.
05 / CUE EDITOR
06 / CUE SHEET
Add a cue to begin building your cue sheet.
| Video time | Cue label | Category | Source time | |
|---|---|---|---|---|
| No cues yet. Press M while listening to mark a moment. | ||||
07 / IMPORT & RETIME
Append a PixelOkay CSV or Audacity label file without losing existing cues. You can undo the entire import.
Batch shifts operate on source timestamps; video start offset is a separate project setting. Invalid shifts leave all cues unchanged.
08 / EXPORT
Exports are made from confirmed cues, not unreviewed suggestions. The original media is not included in project files.
CSV includes source time, video offset and non-drop-frame timecode. Audacity labels use source time. SRT markers are designed as editor reference captions, not finished subtitles.
FOR SOUND DESIGNERS, VIDEO EDITORS & CREATORS
Scrub to a frame, set a label, choose a cue category, and add notes for your editor or sound designer.
Detect energy transients and accept only useful candidate times. Automatic analysis never pretends to understand the sound.
Export a CSV cue sheet, timecoded text report, Audacity label track, SRT reference markers, or an editable project.
No. The local detector looks for increases in audio energy, such as a hit or sudden transition. It does not identify sound classes. You review and label each event; specific sound recognition would require a separate trained model.
Yes. You can import supported video files, play and scrub them, and mark sound cues on the video's timeline. Some video containers cannot be decoded by the browser's Web Audio API for waveform analysis; manual mapping still works if the video is playable.
No. All selected media, waveform processing, cue edits and downloads are processed in your browser tab. Project JSON contains labels and timing but not the source media.
No. Timecode uses integer frame rates (24, 25, 30, 50 or 60 fps) and non-drop-frame counting. If your editing project uses drop-frame timecode, convert the markers in your editor or use the exact decimal timestamps in CSV.
Yes. Download the project JSON to preserve cues and settings. When reopening, the media is not bundled: reattach your audio or video if you need playback. Verify that it is the matching source.
PIXELOKAY CREATOR STUDIO
Analyzing local audio…
Load playable audio/video or the generated example, place and label cues manually, then review waveform energy-rise candidates as timing suggestions. Shift cues in batches and export a cue sheet rather than a rendered or mixed video.
Authored example: Mark an audible door close by listening to the clip, then compare its timestamp with a nearby energy-rise suggestion. Keep the cue name manual and check the offset before exporting.
Limits and privacy: Transient detection finds energy changes; it does not identify sounds or use AI. The tool does not mix media or render video. Playback accepts source media up to four hours, while waveform analysis is limited to thirty minutes. Project JSON excludes media, so reattach originals; timecode is integer non-drop-frame.