Timewarp Visualizer

Loading shaders

Getting the 12 scenes ready for your graphics card.

0:00.0 / 0:00.0 — BPM

Section change (music shifts)Big transitionCut on the bar

Track

No song loaded

The whole track is analyzed up front: five frequency bands, kick, snare and hat hits, the beat grid, and the points where the music changes.

Scenes

“ref” is where each look appears in the source video. Solo previews one scene; the switch removes it from the cut.

Direction

Shortest scene

Longest scene

Cut on

Transitions

Hit effects (light bars, flares, glitch)

Audio reactivity

Force a scene change when the music changes Match high-energy scenes to loud parts

Seed

Export

Size

Frame rate

Bitrate

Preview quality

Checking what this browser can write…

Render MP4 draws every frame offline, so nothing drops even at 4K. Use it for anything you post. Real-time recording plays the track once and captures what you see.

ⓘ Posting to X

What Timewarp writes. Render MP4 saves H.264 video with AAC-LC audio at 44.1 or 48 kHz, 192 kbps stereo. That's the format X recommends, and it plays everywhere else too.

Free X accounts can post videos up to 2 minutes 20 seconds and 512 MB. They play back at 720p.

X Premium raises that to 4 hours and 16 GB on the web, with 1080p playback and 4K uploads.

Song longer than 2:20? Post a clip: trim the finished MP4 in any video editor, or load a shorter edit of the song.

Bitrate. X re-encodes every upload, so 16 Mbps at 1080p is plenty. Higher settings only make a bigger file and a slower upload. Keep 40 or 80 Mbps for a master copy.

Render or record? For posting, use Render MP4. Real-time recordings can drop frames, and some browsers save them as WebM, which X won't accept.

X changes these limits from time to time. Current rules are on help.x.com.