vo.odgn.net

What is VO Pads?

VO Pads is a browser-based video player built around a pad grid, designed for triggering and sequencing video clips like a sampler rather than watching a single timeline. It is currently labelled Beta. You load clips onto pads, then fire them with mouse clicks, keyboard keys, or a MIDI controller, with per-clip control over start point, duration, playback speed, and volume.

H3 What it is actually for The page frames it as a performance and composition tool: "Pad Based Control" for triggering, and "Edit Playback" for trimming and mixing. That combination suits people who want to improvise with video the way they would with audio — VJ sets, live visuals, remix-style edits, or assembling a sequence from short loops. The listed demo material (a De La Soul track, a Rebecca Sugar song, a Blade Runner monologue) shows the intended flavour: sampling and recontextualising existing footage.

H3 Practical constraints worth knowing

• Sources: YouTube videos and local mp4 files. Pads open a selector where you add a file or paste a YouTube URL.
• Install: none — it runs in the browser. Sharing is a single URL that reproduces your project as configured.
• Browser: any HTML5-capable browser, with Chrome recommended. On iOS or iPadOS, only one video can play at a time, which limits layering and simultaneous pad triggers.
• Audio: volume is adjustable per clip, but the page makes no claim about audio routing or mixing beyond that.

H3 Who it fits A useful test: if your idea of editing is "press a pad and something happens now," it fits. If you need frame-accurate multicam editing, colour work, or long-form narrative cutting, a conventional editor will serve you better. Similarly, if your audience is on iPads, plan around the single-video limit — either design for one clip at a time or point them to a desktop.

Next step: open the demo, tap a pad, and paste a YouTube URL to see how quickly you can build a two- or three-pad sequence. If triggering feels natural, the workflow will; if you keep wanting a timeline, it won't.

For context on the sampling culture it draws from, Who Sampled documents track-to-source relationships, and Koala Sampler is cited on the page as a key inspiration for the pad interaction model.

How do you set up a VO Pads project for a live performance or VJ set?

A VO Pads project for live use is essentially a grid of video pads you trigger on cue, with each pad holding one clip and its own start point, duration, speed and volume. You build the set in the browser, then share or open it as a single URL so the performance rig is just a browser window.

Building the set

1. Open VO Pads and tap a pad to open its selector. Add a local mp4 file or paste a YouTube URL.
2. Repeat across the pads you plan to use, keeping one clip per pad.
3. For each pad, set the start point and duration so the clip fires on the beat or on your cue rather than from its beginning.
4. Adjust playback speed and volume per pad so clips sit at a consistent level in the mix.
5. Decide how you will trigger: clicking pads, keyboard keys, or a MIDI controller. Assignment is part of the pad-based control setup, so map the pads you will actually hit under pressure.
6. Share the project URL and open that same link on the performance machine. The recipient sees your layout and settings as you configured them.

Practical checks before you go live

• Test on the exact browser you will perform with. Chrome is recommended for the best experience.
• On iOS or iPadOS, only one video plays at a time, so layered or overlapping clips are not an option there. For a VJ set that stacks visuals, use a desktop browser.
• Confirm every source resolves: YouTube clips depend on a live connection and the video remaining available, while local mp4 files depend on those files being present on the performance machine.
• Preload or trigger each pad once during soundcheck so you know how quickly it starts and how it sounds at your set volume.

Whose observations these are

The page itself notes the iOS/iPadOS single-video limitation and the Chrome recommendation; those are the project's own statements, not a reviewer's. My practical read: treat the one-video limit as a hard constraint on your creative plan rather than a minor caveat, because it rules out the crossfading and overlay style many VJ sets rely on. If layering matters, plan a desktop-only set; if you are performing from a tablet, design around hard cuts and single-clip triggering.

A concrete scenario

Say you are playing a 30-minute set and want a different visual per track section. Use one bank of pads for intro clips, another for drops, and a third for spoken-word or film samples. Set each pad's duration to match the section length so a clip ends cleanly instead of running into the next cue, and keep volume matched so switching visuals does not change perceived loudness. If you use a MIDI controller, map the pads you use most to physical buttons and leave the rest for mouse or touch.

Decision criterion

Choose VO Pads when your set is cue-driven and clip-based: you want to fire discrete videos at chosen moments with tight control over start, length, speed and level. Choose something else if you need simultaneous multi-video compositing on a tablet, or if your visuals must run without any dependency on YouTube availability.

For inspiration on the pad-and-sample workflow this kind of tool borrows from, the project points to Koala Sampler, and for tracking down where a track's samples came from, WhoSampled is the reference it credits.

How do you trigger video clips with a MIDI controller or keyboard in VO Pads?

In VO Pads, you trigger a video clip by assigning it to a pad, then firing that pad from your MIDI controller or computer keyboard. The pad grid is the performance surface: each pad holds a clip, and hitting it starts playback instantly. MIDI and keyboard input are simply alternative ways of striking those pads, so anything you can play with a mouse or trackpad can also be played from hardware.

Setting up a trigger

1. Click or tap a pad to open its selector.
2. Add a clip — either a local mp4 file or a YouTube URL.
3. Repeat for as many pads as you need, building your layout.
4. Play the pads with mouse, keyboard, or MIDI controller.

What each input method is good for

• MIDI controller — the natural choice for live performance. Pads and keys give you physical, low-latency triggering and let you play with both hands instead of hunting for a cursor. If your controller has velocity or aftertouch, the practical benefit here is mainly tactile feedback and reliable repeated hits rather than expressive variation, since VO Pads is triggering clips rather than synthesizing sound.
• Computer keyboard — the quickest route for testing a sequence or performing without extra gear. Useful when you're building a project on a laptop and want to audition timing before committing to a controller mapping.
• Mouse/trackpad — fine for editing and arranging, less so for performance, because aiming at a pad adds a beat of hesitation.

Timing and shaping each clip

Triggering is only half the job. VO Pads also lets you set a clip's start point and duration, adjust playback speed, and tune volume per clip. That means you can, for example, fire a short vocal stab from one pad, a slowed-down atmospheric loop from another, and a full clip from a third, all from the same controller. Getting the start and duration right is what makes pad triggering feel musical rather than chaotic — a clip that begins a fraction late will sound sloppy no matter how good your controller is.

Sharing what you build

A finished project can be shared as a single URL, so a collaborator or audience member opens the link and plays the same layout you set up, with no install. This is where the pad approach pays off for teaching or remote collaboration: you can hand someone the exact trigger map instead of describing it.

Practical constraints to plan around

• VO Pads runs in the browser; the project recommends Chrome for the best experience, though any HTML5-capable browser should work.
• On iOS and iPadOS, only one video can play at a time, so overlapping or layered clips aren't possible there. If your piece depends on simultaneous playback, plan to perform on desktop.
• Sources are currently YouTube videos and local mp4 files, so your clip library is limited to what you can supply or link.

Next step

Before mapping a full controller, build a three-pad test project — one short clip, one loop, one longer piece — and play them from your keyboard first. Once the timing feels right, assign those same pads to your MIDI controller. If you want to understand the pad-performance idiom more deeply, the project credits Koala Sampler as its main inspiration, and WhoSampled is a good place to trace where your source clips originally came from.

How do you edit the start time, duration, speed, and volume of a video clip in VO Pads?

In VO Pads, clip timing and levels are edited per pad rather than on a global timeline. Tap or trigger a pad to load its clip, then use the playback controls to set the start point, duration, playback speed and volume. Changes apply to that pad's clip, so each pad can hold a differently trimmed and mixed version of a video.

What you can adjust

• Start time – choose where in the source video playback begins.
• Duration – set how long the clip plays before it stops or loops.
• Speed – change the playback rate to slow down or speed up the clip.
• Volume – fine-tune the level of each clip so multiple pads can be balanced against each other.

Because these are per-pad settings, the practical workflow is to build a set of trimmed clips first, then balance volumes across pads so that triggering them together doesn't produce one clip drowning out the others.

Practical example

Suppose you're assembling a short live set from three YouTube clips. On pad 1 you set a 4-second duration starting 30 seconds into the source; on pad 2 you slow a clip to half speed and set a longer duration; on pad 3 you drop the volume because it's a background loop. You then trigger them by pad, keyboard or MIDI, and share the whole setup as a single URL so someone else opens it with your exact timings and levels intact.

Things to keep in mind

• Sources are currently YouTube videos and local mp4 files, so trimming happens inside VO Pads rather than in the original file.
• On iOS and iPadOS, only one video can play at a time, which limits layering regardless of your volume and timing settings.
• Chrome is recommended for the smoothest experience.

Next step

Load one clip into a pad and set a short start time and duration first, then adjust speed and volume while triggering it repeatedly. Once one pad feels right, copy that approach across your remaining pads and share the project URL to check the mix on another device.

For sample-source inspiration, the project credits Who Sampled and Koala Sampler as influences on its pad-based approach.

How do you share a VO Pads project with a single URL?

VO Pads shares a project by generating a single URL that contains the whole setup. Anyone who opens that link gets your pads, clips, and playback settings loaded in their browser — no file transfer, account, or install needed. The page describes this under "Share Your Creation": "Share your entire project with a single URL. No downloads, no installs - just open and play."

This works because VO Pads is a browser-based player. Your pads can point at YouTube videos or local mp4 files, and the shared link is meant to reproduce your arrangement as you configured it — which pads trigger which clip, plus start time, duration, speed, and volume.

H3 Practical caveats

• Local mp4 files are the weak spot. A link can carry the pad layout and settings, but a file that lives only on your machine generally can't travel with a URL. If your project depends on local files, expect recipients to supply their own copies or for those pads to come up empty. Test the link in a different browser profile before relying on it.
• YouTube sources are the safer bet for sharing, since the clip is referenced rather than uploaded.
• iOS and iPadOS play only one video at a time, so a layered, multi-pad sequence won't behave the same there as on desktop Chrome.

H3 Who this suits

• Collaborators reviewing a sequence: send the link, they open it and see your timing and mix decisions rather than a description of them.
• Live performers: a URL is a fast way to move a set between machines, provided the media sources resolve.
• Teachers or demo-makers: good for handing out a playable example instead of a video recording.

If your goal is a performance you can trust, treat the URL as the arrangement and the media as a separate dependency. Before sending, open the link on a second device and confirm each pad fires.

For background on the sampling culture that shapes this kind of tool, Who Sampled is a useful reference, and Koala Sampler is cited by the project as a key inspiration.

What video sources can you load into VO Pads and how do you add them?

VO Pads accepts two kinds of video sources: YouTube videos and local MP4 files. According to the site's FAQ, you add either one by tapping a pad, which opens a selector where you can either paste a YouTube URL or add a file from your device.

That split matters in practice:

• YouTube URLs are the quickest route when you want to sketch out a set or share a project, since nothing needs to live on your machine. The trade-off is that playback depends on YouTube being reachable and on its embed rules.
• Local MP4 files give you tighter control over clips you own or have already prepared, and they keep working without a network connection to YouTube. The trade-off is that the file has to be available wherever the project is opened.

A practical next step: if you plan to share a project by URL, test it with a local MP4 first and then with a YouTube clip, because a collaborator opening your link may not have your local files. If sharing needs to be frictionless, lean on YouTube sources; if reliability and exact clip timing matter more, keep your own MP4s.

One caveat worth knowing before you build around it: on iOS and iPadOS, only one video can play at a time, so layered or overlapping playback works best on desktop browsers such as Chrome.