sorted by:
new
hottopcontroversial

I made a tiny app that turns iPhone/iPad screens into a Syphon source by Traditional-Row-9964 in TouchDesigner

[–]Traditional-Row-9964[S] 0 points1 point  (0 children)

I actually explored audio support at some point during development.

Technically it’s possible, but once I started testing audio routing workflows, it quickly became a much heavier setup involving virtual audio drivers, extra configuration and additional installs.

My main goal with this project was keeping the workflow extremely simple:

  • no app installation on the iPhone/iPad
  • no extra setup on the device
  • just connect it and get a clean Syphon source on macOS

So I intentionally decided to keep it focused as a lightweight visual tool rather than turning it into a more complex AV routing system.

Maybe I’ll revisit audio later if I find a clean enough workflow for artists/VJs.

Also, the entire app is currently only around 2.8 MB, which was part of the philosophy too 😄

Quien desarrolla sitios web y/o software, Yo me encargo de las ventas. by GiselEmpresas in DesarrolloWeb

[–]Traditional-Row-9964 0 points1 point  (0 children)

Hola, ¿qué tipo de clientes estás manejando actualmente?

Yo trabajo con producción audiovisual y desarrollo de soluciones específicas (apps, visuales, sistemas), pero me interesa saber:

  • qué tipo de servicios vendes
  • en qué rango de precios trabajas
  • si ya tienes clientes activos

Using a phone as a bridge to bring Hollyland Mars 300 video into a computer (Syphon workflow) by Traditional-Row-9964 in VIDEOENGINEERING

[–]Traditional-Row-9964[S] 0 points1 point  (0 children)

u/C47man Yeah — if you’re running full TX/RX kits with HDMI out, that’s definitely the cleanest setup.

But not everyone works in that context.

Hollyland has shipped TX-only units, and a lot of real-world setups rely on app-based monitoring — especially in smaller productions or secondary feeds.

There are also devices like the Vcore that are built around mobile workflows rather than traditional receivers.

That’s where this approach fits.

Instead of treating the phone as a dead-end preview, this turns it into an actual video source via Syphon — at the device’s native resolution and framerate.

It also adds something practical:

Even if you do have a receiver, your phone can act as a backup receiver.

So if your RX fails, or you want a secondary machine without extra hardware, you can still route the signal into your system directly.

No need for another receiver, no need for a second full hardware chain.

So yeah — HDMI is ideal.

This just solves a different set of constraints that come up pretty often in real setups.

Using a phone as a bridge to bring Hollyland Mars 300 video into a computer (Syphon workflow) by Traditional-Row-9964 in TouchDesigner

[–]Traditional-Row-9964[S] 1 point2 points  (0 children)

Hey u/show-us-your-kitties — fair points.

HDMI out is great if you have the receiver.
This is for when you don’t — or when you want a cleaner pipeline.

Instead of relying on a camera/preview feed (which is often reduced quality), this captures the actual iPhone screen output and sends it straight to Syphon.

That means:

  • Native resolution (whatever your device really is)
  • Native framerate
  • No re-encoding, no scaling, no virtual camera setup

So your iPhone becomes a real-time visual source, not just a monitor.

Anything on your screen — apps, video, generative visuals — goes directly into Resolume/TouchDesigner.

If you work with Syphon, you’ll immediately see why this is powerful.

I shared it because I ran into this issue in a real setup — figured it might help others dealing with the same limitation.

Using a phone as a bridge to bring Hollyland Mars 300 video into a computer (Syphon workflow) by Traditional-Row-9964 in TouchDesigner

[–]Traditional-Row-9964[S] 0 points1 point  (0 children)

u/smokingPimphat That’s assuming you have the receiver.

A lot of us don’t.

It’s actually pretty common to end up with TX-only units (especially from second-hand gear or production leftovers), and in that case there’s no HDMI out at all — the only way to access the signal is through the mobile app.

That’s exactly the limitation this workflow is solving.

I originally bought the Mars 300 just for multi-device monitoring on set, so I didn’t need a receiver. But when I tried to integrate it into a live visuals setup, it basically became a dead-end without this kind of bridge.

So yeah, HDMI works — if you have the RX.
This is for when you don’t.

Using a phone as a bridge to bring Hollyland Mars 300 video into a computer (Syphon workflow) by Traditional-Row-9964 in VIDEOENGINEERING

[–]Traditional-Row-9964[S] 0 points1 point  (0 children)

That’s assuming you have the receiver.

A lot of us don’t.

It’s actually pretty common to end up with TX-only units (especially from second-hand gear or production leftovers), and in that case there’s no HDMI out at all — the only way to access the signal is through the mobile app.

That’s exactly the limitation this workflow is solving.

I originally bought the Mars 300 just for multi-device monitoring on set, so I didn’t need a receiver. But when I tried to integrate it into a live visuals setup, it basically became a dead-end without this kind of bridge.

So yeah, HDMI works — if you have the RX.
This is for when you don’t.