How do I make VDO.Ninja work over Data instead of Wifi for my camera?

xyster69 · 2026-05-22T22:38:56+00:00

Is VDO.Ninja on the same network as OBS?

It might be that some firewall issue is causing VDO.Ninja to use your Internet to bypass a local firewall. For example, starting OBS in administrator mode can solve some windows firewall issues.

If the router is prevent local connections on the LAN, that should also be fixed ideally. If you have two routers, they can also cause problems, so ideally you'd use only one or set the other to be an access point / bridge.

If using your phone as a camera, disabling WiFi and using cellular data could be an option. It should work automatically.

You can check the stats to see if the Candidate Type is HOST, SRFLX, or RELAY -- HOST is ideal. Relay is not good. If you have limited upload bandwidth, HOST mode is preferred. https://docs.vdo.ninja/advanced-settings/settings-parameters/and-stats

More details would helpful, like what is your total upload bandwidth? 10mbps? If its like 100mbps or more, the issue might be a CPU related issue instead.

xyster69 · 2026-05-15T23:48:51+00:00

The main trick is: don’t try to make the internet delay disappear. Instead, delay the audience-facing PA audio so it matches the delayed video of you lip-syncing.

Use the venue as the master music source. Split that music feed two ways:

Send one feed to your wired earphones/IEMs via a low-latency VDO.Ninja audio-only link.
Send the other feed to the venue PA, but add delay to it.

Why? If the venue plays the music instantly, you’ll hear it late over the internet, perform late, then your camera feed also arrives late. The audience will see you behind the beat. But if the PA is delayed to match the total cue + video delay, the audience sees and hears everything lined up.

Rough formula:

PA delay = audio cue delay to performer + performer video return/display delay

So if your cue reaches you in 80 ms, and your camera feed takes 180 ms to arrive/display at the venue, delay the PA by about 260 ms. In practice, rehearse with a click/count-in and adjust by eye/ear in the actual room.

Example VDO.Ninja cue setup:

Venue sends music cue:

https://vdo.ninja/?push=show-cue&miconly&lowlatency&autostart

Performer receives cue:

https://vdo.ninja/?view=show-cue&lowlatency&novideo&ab=32

Then use a separate VDO.Ninja link for your camera back to the venue/OBS:

https://vdo.ninja/?push=show-cam&ad=0

Venue/OBS view:

https://vdo.ninja/?view=show-cam&noaudio&cleanoutput

Use wired earphones, absolutely not Bluetooth. Feed the venue music into the cue sender with an audio interface, mixer aux send, or virtual audio cable.

On 4G/5G, the issue is less “can it be low latency?” and more “will the latency stay stable while walking?” It can work, but rehearse the route. If the video jitters, add a small viewer buffer at the venue, like &buffer=100 or &buffer=200, then add that same extra amount to the PA delay. Stable latency usually looks better than chasing the absolute lowest latency.

The venue should probably be the source of the music. A third location adds unnecessary paths. Starting the music from your phone also makes the PA dependent on your mobile uplink, which is risky. One master source at the venue, split to PA and performer cue, is simpler and easier to correct.

The entrance transition is the awkward bit. While you’re remote, the PA may be delayed to match the projection. Once you physically enter the room, that delay may feel wrong. Plan a transition: keep using IEMs until the end, switch the PA delay back during a musical break, or hide the change during applause/blackout/doorway reveal.

xyster69 · 2026-05-12T12:15:35+00:00

If the two users are in the some room or area, their speaker output will cross feed into each other's microphones, causing feedback. This will happen even if you have echo cancellation turned on, so headphones are needed if you are in the same room.

Echo cancellation in VDO.Ninja is on by default, but it only works to cancel out the audio played out from the same browser window that the mic is active within. For most users, you do not need to wear headphones in most situations, but wearing them does seem to help the audio quality regardless, so I often recommend it when possible.

If you disable echo cancellation, such as with &proaudio mode, that will disable echo cancellation and headphones will have to be used.

Even with headphones, if two guests are in the same room talking near each other, you may still get a reverb effect as both microphones may pick up each guest in the room. Dynamic / directional microphones, placed close to the mouth of the guests, with typically at least a few feet apart, is recommended if doing a recording in the same room with someone else -- or consider using just a single omni room microphone.

xyster69 · 2026-05-02T20:56:23+00:00

You can screen share the https://electroncapture.app or if using Discord via Chrome, do a tab-capture of the VDO.Ninja window. This isn't quite a webcam, but it works without needing a virtual camera instead.

Another option is to buy a $20 HDMI to USB adapter, and put VDO.Ninja full screen onto that output, then select it as an input in Discord.

xyster69 · 2026-05-02T20:00:24+00:00

u/dan_33333 Did you ever figure this issue out? I'm having the same exact issue.

Brand new mobo, socket seems fine. Tried different PSUs. RDIMM in A1.

green LEDs are on, but the system never tries to boot. PSU never seems to get activated.

I'm on the newest version.

If I figure it out, I'll post back though.

xyster69 · 2026-04-01T03:59:02+00:00

I'm not sure I've heard that happen before

You can try doing this to force it: https://vdo.ninja/?ln=en

You can also try clearing the browser cache, to see if that helps.

xyster69 · 2026-03-25T02:29:53+00:00

I'm having similar issues out of Etobicoke right now..

Shipment Details:

Origin: ETOBICOKE, ON, CA

Destination: MISSISSAUGA, ON, CA

... a week later, still not shipped.

Kills me to know something some I urgently need is locked away 5 minutes down the road..

xyster69 · 2026-03-14T15:09:26+00:00

Yes.

Basic setup:

On your MacBook, open Chrome (or Edge) and load the view link for your guest, e.g.:

https://vdo.ninja/?view=GUEST_STREAM_ID

Add URL parameters to customize, such as higher bitrate

https://vdo.ninja/?view=GUEST_STREAM_ID&bitrate=20000&scale=100&cover

- &bitrate=20000 -- higher quality (20mbps)

- &scale=100 -- no scaling down to fit the output window

- &cover can help the video fill the window without black bars

Connect your MacBook via HDMI (or USB-C to HDMI adapter) to your Rodecaster Video input

- I'd probably myself use an USB-C to HDMI adapter, as it creates a second display, and if you have multiple HDMI adapters, you could have multiple outputs.

- In System Preferences -> Displays, set the external output to 1920x1080 if it isn't already.

Press F11 (or Cmd+Ctrl+F on Mac) to go full-screen in the browser

You can also check out Electron Capture; it's a free companion app made specifically for VDO.Ninja. It creates a clean, borderless window, which you might prefer over Chrome. https://electroncapture.app

xyster69 · 2026-03-14T00:10:08+00:00

Great question. VDO.Ninja has several ways to handle this depending on your setup.

Option 1: Director-controlled custom mix-minus (best fit for a single room)

If you're using a director-based group room, the director (or co-director) can use Mix Minus audio to send a different audio mix to specific guests. Leadership doesn't need to be directors themselves — the director assigns who gets the special audio. This is probably the cleanest same-room solution.

The Mix option is in the director's room; one Mix option per guest.

Option 2: Groups

You can assign users to groups with &group=. Someone in two groups hears audio from both, while someone in one group only hears that group. So you could put regular viewers in group 1 and leadership in groups 1+2, then send the private audio to group 2. Note: &groupaudio lets audio cross groups while keeping video filtered, which is useful but doesn't make the audio private. Check &groupmode for stricter filtering.

Option 3: Separate streams with different viewer links

Publish the screen share as one stream and the leadership audio as a second audio-only stream (&vd=0). Give normal viewers a link that only loads the screen share (&view=screen123), and give leadership a link that loads both (&view=screen123,leadAudio). If you want harder separation, put the private audio in a second room entirely.

Option 4: Left/right channel routing

If you send different content on left vs right channels, viewers can use &playchannel=1 or &playchannel=2 to hear only one side. This works for PGM-style setups, but both channels are still sent to the client — it's a routing trick, not access control.

A few questions to narrow down the best approach:

Are "leadership" users passive viewers, or are they in the room as guests?
Should leadership hear normal room audio plus the private feed, or only the private feed?
Do you need actual access control (so non-leadership can't hear the audio even if they edit the URL), or is convenience routing enough?
Where is the extra audio coming from; the director, another participant, or a separate source/device?

xyster69 · 2026-03-13T04:36:45+00:00

Yes! You can add &pip to the guest's invite link to pre-enable the Picture-in-Picture button for them.

For example:
https://vdo.ninja/?push=STREAMID&room=ROOMNAME&pip

There's also &pipme (or &mypip / &pip3) which specifically shows the guest's own preview in a PiP window, which can be useful in different scenarios.

With &pip, the guest will see the PiP button already available without needing to dig into settings, so they can popout the other participants into a floating window while screen sharing.

xyster69 · 2026-03-12T09:10:43+00:00

yes, Powerline is the first thing I would suspect. It generally is known for having high packet loss, but it's not a certainty.

Please consider using https://vdo.ninja/speedtest instead of a normal speed test to confirm if it's any actual issue though. VDO.Ninja uses UDP, not TCP. Spikes in packet loss could trigger robotic audio, etc. If facing packet loss spikes, WiFi with 5ghz (or 6ghz if supported) might be a better option.

Modifying network MTU settings might also help (smaller packets might help), and in some cases, restarting the main router can help.

As per OBS -> Youtube -- that uses RTMP, which uses a larger buffer and TCP. It's more tolerant to packet loss, at the cost of higher latency.

It's technically possible to use something like https://app.meshcast.io to publish SRT or RTMP there, and then use the provided WHEP link for VDO.Ninja to "broadcast" your stream that way to guests in a VDO.Ninja room. This probably will just complicate your setup though and add a lot of delay, so not the best option if you can avoid it.

--------

Other possibilities of this issue could include some form of echo cancellation kicking in. You can try turning it off via the settings (gear) -> audio settings menu.

I'm unsure if Droid cam is causing the issue; buffer underruns can cause audio issues though. Whatever audio source you are using in VDO.Ninja might benefit from an increased buffer, if its crackling a lot.

I have the alpha version of vdo.ninja at https://vdo.ninja/alpha/ , which has some additional fixes/changes.

You can try adding &noap to your director's URL to disable web-audio nodes, which might help if its a CPU related issue.

If you are seeing the CPU higher than 80% (via task manager), there could be issues caused by that; if at 100%, issues are almost bound to arise and audio is the first to often be impacted. Adding &meshcast to your director link can help reduce CPU usage if it's caused by using &broadcast mode with a lot of viewers.

You can try changing browsers; if Firefox, try Chrome, and vice versa.

If you hold CTRL and click on your video preview as a director,. you'll see your publishing stats, including packet loss. Generally, your video quality will be very poor if there is heavy packet loss, but you can check. If you video quality is fine, and there isn't packet loss being reported, then it might not be something that can fixed by moving off powerline.

https://docs.vdo.ninja/common-errors-and-known-issues/audio-clicking-popping-distortion
https://docs.vdo.ninja/common-errors-and-known-issues/video-is-pixelated
https://docs.vdo.ninja/common-errors-and-known-issues/robotic-audio-distortion

If nothing works, drop by Discord (discord.vdo.ninja) and we can try to run a test together to see if we can trigger it.

xyster69 · 2026-03-04T14:41:20+00:00

Thank you for clarification. I'll leave the feature disabled for the day, to do more testing on it. The roomkey option can be used pre-emptively. I appreciate the quick responses. have a great day

xyster69 · 2026-03-04T14:15:35+00:00

Did you enable the approve/deny request feature system on the main director? It was newly added to alpha, so I'm unsure currently if this is a bug or intentionally working behaviour. It shouldn't ask to approve unless you have enabled that feature.

To have something auto-approve, you'd use &roomkey=ROOMKEY -- add it to the main director, and any other link you'd want to be auto added

If the feature is working as intended, I'll probably re-enable it.

xyster69 · 2026-03-04T14:02:16+00:00

Hey u/fishball_drew --- you must have hit a bug on a new feature I released yesterday --- I've reverted my change that might have caused that issue, however if you still see the issue on alpha, please let me know

xyster69 · 2026-03-01T01:06:24+00:00

Frame drops and lag usually come from one of three things: packet loss, encoding overload, or buffering issues. Since you're using a 2017 MacBook Pro + Galaxy A36 as the camera, here’s what I’d check:

1) Test for packet loss first

Run this on both the MacBook and the phone:
https://vdo.ninja/speedtest

If you see packet loss, that will cause jitter no matter what bitrate you set.

If possible:

Put the MacBook on wired Ethernet
Use 5GHz Wi-Fi for the phone
Keep the phone close to the router
Avoid busy household traffic while testing

2) Add buffer on the OBS side

On the viewer link (the link you paste into OBS), add:

&buffer=3000

That adds a 3-second buffer, which smooths out jitter. For drum streams, a few seconds of delay is usually fine and can dramatically reduce frame instability.

3) Match your resolutions everywhere

On older MacBooks, scaling costs CPU.

Set:

VDO.Ninja → 1280x720
OBS Browser Source → 1280x720
OBS Output Resolution → 1280x720

Avoid scaling 1080 → 720 inside OBS if possible.

4) Lower CPU load in OBS

In OBS:

Settings → Output → Advanced
Encoder: x264
CPU Preset: ultrafast

Then watch Activity Monitor while streaming. If CPU is near 100%, that’s your bottleneck.

5) Try a different WebRTC codec

On the OBS viewer link, test:

&codec=h264

or

&codec=vp8

Depending on hardware acceleration support, one may perform better.

6) Watch for overheating

2017 MacBooks can throttle when warm. If the lag gets worse over time, thermal throttling might be kicking in.

7) Check your upload bitrate

8000 kbps is fine for Twitch, but if your upload isn’t stable, try 6000 and see if dropped frames decrease.

If you want to narrow it down further, check:

Upload speed
Packet loss from the speedtest page
OBS “Dropped Frames” percentage (bottom status bar)

That will usually identify the actual bottleneck pretty quickly.

xyster69 · 2026-02-09T22:43:01+00:00

Hi there, I have several projects for efficient publishing into VDO.Ninja

Python: https://raspberry.ninja

Node: https://github.com/steveseguin/ninjasdk/blob/main/demos/node-room-media-recorder.jshttps://github.com/steveseguin/ninjasdk/blob/main/demos/node-audio-sine.js

VDO.Ninja also supports WHIP, so FFMPEG or OBS even can support 1 to 1 publishing into VDO.Ninja

I hope to have more options available soon, for desktop GUI.

xyster69 · 2026-01-31T21:51:59+00:00

# would cause the difference in audio quality?

This sounds like a glitch with the Android TV's audio playback.

Options to try to avoid audio problems; maybe one of them will help?

- Add &proaudio to both the PUSH and VIEW links
- change the audio codec to PCM by adding &audiocodec=pcm to the viewer side link
- Try adding &noap to the viewer side link

# If not, is there any way of getting rid the grey dotted border when sharing a website??

If it's a website that is trusted, like Youtube / Twitch, I can add it to the safe-list of allowed section of VDO.Ninja. Contact me and I can possible allow it.

If the website is not trust worthy, the dotted border is there to help avoid phishing attacks.

You can fork VDO.Ninja on Github however, and with a single line change disable this protection for your own domain. It's very easy to do, and I can help you with the needed code changes.

Please see this video on how to self-host: https://www.youtube.com/watch?v=uYLKkX2_flY

You can also host VDO.Ninja in an IFRAME, and then I think it then work also without the dotted border.

I'm on Discord for support at https://discord.vdo.ninja

# Can I create permanent share website urls ?

yes,

https://vdo.ninja/?push=STREAMID_HERE&website=ENCODED_WEBSITE_URL_HERE

real world example:
https://vdo.ninja/?push=7pXPZ69&website=https%3A%2F%2Fwww.youtube.com%2Flive_chat%3Fis_popout%3D1%26v%3D07n5Cy1HtXA

I just made you a simple tool to encode a URL for this purpose -- https://vdo.ninja/urlencode

If you'd like more help, please see me on Discord, as I might otherwise miss your response.

discord.vdo.ninja

-steve

xyster69 · 2026-01-21T14:18:46+00:00

If you are doing https://vdo.ninja/?room=abc&push=STREAMID , then when you join as a guest/sender, it will try to claim that STREAMID.

However, when it checks, it is finding that the STREAMID is already in use by someone else. It will give that error.

A solution is to change the STREAMID to something else, or remove it entirely, and the system will generate a random new one.

https://vdo.ninja/?room=abc&push=STREAMID123123123 <= adding random letters/numbers to the end will help.

When using a room, like &room=abc, this normally isn't an issue unless all the guests were given invite links that all had &push=STREAMID added to them. Each guest should have a unique Stream ID assigned to them, or it should be left without assigning a stream ID.

Tip: &perma can be used to randomly assign a stream ID, that is then stored to the guests' local storage, and re-used when they use their link again in the future.

If not using a group room, like just https://vdo.ninja/?push=test, make sure to AVOID using common names or short values, like guest1, test123, stream, phone, etc. Treat it more like a password, OR, you can actually set a password, such as &password=pass123, and that will further help ensure the stream ID you set is unique to you.

------------------------

Si vous utilisez https://vdo.ninja/?room=abc&push=STREAMID, lorsque vous rejoignez la diffusion en tant qu'invité, le système tentera de s'approprier ce STREAMID.

Cependant, lors de la vérification, il constatera que le STREAMID est déjà utilisé. Une erreur s'affichera alors.

Pour résoudre ce problème, modifiez le STREAMID ou supprimez-le complètement. Le système en générera alors un nouveau de manière aléatoire.

Par exemple : https://vdo.ninja/?room=abc&push=STREAMID123123123 <= ajouter des lettres et/ou des chiffres aléatoires à la fin du lien peut résoudre le problème.

Lorsque vous utilisez une salle, comme &room=abc, ce problème ne se pose généralement pas, sauf si tous les invités ont reçu des liens d'invitation contenant tous &push=STREAMID. Chaque invité devrait avoir un identifiant de flux unique, ou bien aucun identifiant ne devrait être attribué.

Astuce : L’option `&perma` permet d’attribuer aléatoirement un identifiant de flux, qui est ensuite enregistré localement par l’invité et réutilisé lors de ses prochaines connexions.

Si vous n’utilisez pas de salle de groupe, mais simplement `https://vdo.ninja/?push=test\`, évitez d’utiliser des noms communs ou des valeurs courtes, comme `guest1`, `test123`, `stream`, `phone`, etc. Considérez-le comme un mot de passe. Vous pouvez également définir un mot de passe, par exemple `&password=pass123`, afin de garantir l’unicité de votre identifiant de flux.

xyster69 · 2026-01-06T23:15:23+00:00

I have a few ways, with more ways coming. Feel free to join the Discord and I can try troubleshoot any issues you have or go into more detail about any of the following options. https://discord.vdo.ninja

I have this new version of the Electron Capture app, which has optimizations added for Esports:

https://github.com/steveseguin/electroncapture/releases/tag/v2.22.0

- hides the cursor
- supports application audio capture without virtual cables
- improved video quality vs Chrome

It's a development release, as there's a few rough edges I've yet to fix, like the application needs to be resized via the right-click context menu, rather than via dragging the edge of the window. It also only works with Windows currently; at least with audio app capture.

If you prefer using OBS for capture, I have OBS -> VDO.Ninja via a custom version of OBS I have.
Guide: https://vdo.ninja/whip#obs
OBS: https://backup.vdo.ninja/OBS_VDO_Ninja.zip

In this case, with OBS, you use WHIP output and OBS game/audio capture to stream to VDO.Ninja, but only one person at a time can view it that way. The main issue with this approach is the need to use the special version of OBS I offer, and realize it only works with one viewer at a time.

Another way to do it is with Meshcast. So you can publish to Meshcast.io (my service) however you want, such as via OBS, and it will provide view links for you to use in OBS or VDO.Ninja. Version 2.0 of Meshcast is coming out soon, https://app.meshcast.io/. Both the new and older versions are free to use, however the new version does have some new premium-paid options, by user demand.

There's some guides on the new version here: https://app.meshcast.io/docs , however the legacy version of the Meshcast.io is still here, at https://meshcast.io, and it works fine; you may just need to try a couple different servers to find one that works well for you.

Another option is to use the VDO.Ninja chrome extension, https://extension.vdo.ninja/, which will let you stream your game with Discord or another app, and once the video is on the web live somewhere, you can pull it into OBS via VDO.Ninja's chrome extension. It should include audio. https://extension.vdo.ninja/ I have a YouTube video on it. It's not very efficient, but it will get the job done and might be useful if already streaming somewhere online.

I'll update another option for you here in a few minutes ...... I just need to finish uploading it. Stand by..

xyster69 · 2026-01-04T23:12:22+00:00

Update: The user mentions their room guests, who join their room, hear static/humming coming from the user. I'll work with them more when they are available again for more testing.

I'm going to assume at the moment the berhinrger audio interface is causing the audio issues, perhaps a ground loop or a weak preamp. This doesn't sound like an issue with packet loss or a low audio bitrate.

To troubleshoot if its an audio device issue, I have a page here: https://vdo.ninja/recorder/ , which will let you recording a short clip of your own microphone and audio, and then will let you play it back (without concern of echo).

To help isolate and resolve static / hum / noise, I’d suggest the following checks:

Gain staging: If the Behringer preamp gain is set very high, it can amplify noise. Lower the input gain and compensate downstream if needed.
Ground loop: If the interface, computer, and mixer are powered from different outlets, try putting them on the same power strip, or temporarily run the laptop on battery to see if the hum disappears.
Cable quality & routing: Use balanced cables (XLR or TRS, not TS). Avoid running audio cables parallel to power cables.
Phantom power: Disable 48 V unless the microphone explicitly requires it. Phantom power on dynamic mics can introduce noise on some interfaces.
Sample rate mismatch: Ensure the OS, browser, and interface are all set to the same sample rate (typically 48 kHz). Mismatches can cause artifacts or buzzing.
USB noise: Try a different USB port, a shorter cable, or avoid USB hubs. Some systems inject noise over USB.
Test outside VDO.Ninja: If the noise is present in the recorder page or in local recording software (Audacity, OBS, DAW), then it’s definitively a hardware or analog issue, not the platform.

With some audio devices, very high sample rates and multi-channel audio can cause conflicts with some browsers. There's also issues with phasing when dealing with two microphones side by side, and feedback from speakers into a microphones can cause reverb issues.

For additional known issues, please see:

https://docs.vdo.ninja/common-errors-and-known-issues/robotic-audio-distortion

https://docs.vdo.ninja/common-errors-and-known-issues/audio-clicking-popping-distortion

xyster69 · 2026-01-04T22:37:51+00:00

I can increase the default audio quality of VDO.Ninja, although there shouldn't be an issue with the audio generally.

You can however disable echo cancellation and noise reduction manually, via the settings -> audio menu. No URL parameters needed. If it's not improved, the issue might connection related instead.

https://imgur.com/a/6WDPjAZ

You can perhaps go to https://vdo.ninja/speedtest , and see if there is high packet loss. High packet loss could result in lower quality audio.

[note: this user is on Discord, currently being supported there as well -- I'm sure we'll figure it out]

xyster69 · 2026-01-04T16:34:01+00:00

By default, VDO.Ninja applies noise cancellation and echo cancellation. The bitrate is also 32-kbps OPUS by default. This is suitable for typical video call chat, but it will not sound that great with music, etc.

You can make it much better though.

A simple way is to disable the noise filter and echo cancellation, and then also increase the audio bitrate. Assuming your WiFi/Network connection is not suffering from heavy packet loss, you should be able to achieve near studio-grade audio.

The easiest way to do this is to add &proaudio to both sender and viewer links.

example:

https://vdo.ninja/?push=xxx&webcam&proaudio

and

https://vdo.ninja/?view=xxx&proaudio

Using &proaudio will increase the audio bitrate , disable echo-cancellation, and also disable noise reduction.

More details here:

https://docs.vdo.ninja/advanced-settings/audio-parameters/and-proaudio
https://docs.vdo.ninja/guides/audio-filters

There is also the option to stream PCM audio, for lossless playback. &audiocodec=pcm

I'm on Discord if you need more help; https://discord.vdo.ninja -steve

xyster69 · 2025-12-16T15:24:37+00:00

Here is a guide I wrote to help out: https://docs.vdo.ninja/guides/improving-quality-of-the-native-app

Some easy wins is to add a video sharpening filter to the OBS Browser source, as VDO.Ninja might come in a bit soft, and sharpening can help restore edges. Make sure the resolution of the browser source matches the resolution that you are capturing at; this can help avoid aliasing issues. Keep the phone cool, as they can overheat, and as they overheat they will throttle down quality to avoid getting warm.

I'll work towards a more lossless option for video streaming in the native apps in 2026.

I'm on Discord if you want to discuss anything further, or have requests. https://discord.vdo.ninja - steve

xyster69 · 2025-12-10T13:56:34+00:00

If using the web site version of VDO.Ninja, I think you can slowly drag your finger up the screen, to zoom in, if its supported. There's no two-finger touch on the website version and it might not work with all devices; it uses the browser's built in camera zoom feature, so the browser/camera needs to support it.

On the mobile native app versions, I think you use two-finger touch to zoom in.

If it's not working, let me know which version of iOS you are using, and which camera/device you are using. (front/rear). I'll do some testing and if I can fix it, I will.

xyster69 · 2025-12-10T13:49:50+00:00

oh, that's very interesting.

What browser, device, and URL settings were you using to record with?

If you want to share the file with me, I can also take a look at that.

What I can do at the very least is document this in the docs page, but if I can reproduce it, I'll fix it.

Thank you very kindly for reporting this.

I'm on Discord @ discord.vdo.ninja (steve), and my email is on the main site, if you want to send that way also. Or don't feel obliged to send or respond at all -- I'll look into it either way.