Start by checking which protocol your receiving service accepts. Set your iPhone in its intended filming position, open the destination’s instructions, and choose a protocol it explicitly supports.
Key Takeaways
- The receiving input’s instructions determine the supported protocol and connection details.
- Matched trials show the observed differences in picture delay and interruptions.
- A fixed rig keeps framing consistent across connection checks.
- The K12 requires a PD 5V/3A charger.
If both options are available, make a separate test connection for each and compare what arrives at the receiver. Keep the phone, network, destination, and other settings as consistent as you can; the useful answer is the one that fits your own broadcast, not a blanket claim that either protocol always wins.
Larix Broadcaster SRT vs RTMP starts with the receiver
The receiving platform or service determines which connection details you need. Before changing anything in Larix, find the current instructions for the specific destination you intend to send to. A service may give you an SRT option, an RTMP option, or instructions for both. Use the option it explicitly identifies for your intended input.
Check the actual input you will use, rather than relying on a general feature list. For example, if your broadcast goes first to a receiving service and then onward to a public platform, configure the phone for the service receiving the phone’s feed. The later destination is a separate part of the workflow.
Collect the information the receiver gives you for that input. It may include a connection address, a stream key, or other credentials. For RTMP, Larix’s documentation shows combining the server URL and stream key with a slash for the Connection URL field. For SRT, use the receiver’s destination address and port in an srt:// URL. Softvelum’s 2018 SRT walkthrough shows creating a connection and entering a passphrase if encryption is used; check the labels against your installed Larix version. Copy the receiver’s values into a private note for setup, and keep them out of screenshots or shared notes.
Use this decision path:
- One protocol is listed for your input: start with that option and its corresponding connection details.
- Both are listed: prepare the details for each separately so you can compare them without mixing values.
- The instructions are unclear: check the receiving service’s current setup guidance or ask its support which input and connection details to use.
Seeing a protocol name in a phone app is not a substitute for checking the destination. The first successful test is the useful milestone: the receiver gets the picture you intended to send.
A Larix Broadcaster test connection makes the setup manageable
Set up one connection before building a more elaborate broadcast. Have the receiving service’s instructions open on another screen, or keep its connection details available in a private note. On the phone, follow the labels currently shown in Larix and enter the values requested for the selected destination.
- Prepare the destination. Open the intended input or test destination and have its connection information ready. If it offers a private preview, use that for the initial check.
- Choose the supported connection. In Larix, use the option corresponding to the protocol the receiver specifies. Follow the app’s displayed prompts rather than copying a menu path from an unrelated device or version.
- Enter the supplied details. Copy the receiver’s values carefully, keeping addresses, keys, and credentials in their appropriate places wherever the current interface asks for them.
- Check camera and audio access. Allow the permissions needed for your planned picture and sound, then frame the shot and select the intended audio source.
- Start a test and inspect the receiving side. Look for the expected image, listen for the intended sound, and confirm that the destination you opened is receiving the phone’s feed.
Before going live publicly, check the destination’s publishing controls and identify where to see both the incoming feed and its public visibility. These are separate checks.
Once the connection works, record the destination, network, camera orientation, and relevant settings privately so you can rebuild it or set up a second connection.
Matched trials reveal which feed suits your broadcast
When the receiver supports both SRT and RTMP, compare the complete path you actually plan to use. Keep the same phone, camera position, network, receiving input or equivalent destination, and comparable video and audio settings. Change the protocol connection for the second trial rather than changing the entire production at once.
Before starting, decide where you will observe the received feed. Use the same receiving screen and monitoring arrangement for both trials. If you watch through a different preview or add another stage to only one trial, your comparison will describe different paths rather than just your two setups.
For picture delay, show a hand movement to the camera and compare it with the received picture to see whether the delay feels acceptable for your production. If you need a more precise figure, use a clock or measurement method you can apply consistently to both trials and write down what you observe.
For interruptions, note what happens on the receiving screen: whether the picture stops, whether sound is affected, and whether the feed returns. If the receiver or network display offers a packet-loss indicator, record its reading alongside the connection used. Treat that reading as part of your own test record rather than assuming it explains every visible problem.
A simple private log can contain these fields:
- Protocol and receiving input: ______
- Phone position and network: ______
- Video and audio settings: ______
- Observed picture delay and how it was checked: ______
- Visible interruptions or packet-loss reading, if available: ______
- What happened after an interruption: ______
Compare the notes against what matters to the broadcast. An interactive show may put more weight on the delay you see, while a fixed-camera feed may make uninterrupted picture and recovery more important to its operator. If your first comparison is inconclusive, repeat it under the conditions in which you expect to stream and record the new observations.
Connection checks separate setup errors from viewing problems

If the receiver shows no picture, begin with the input and connection details. Confirm that you opened the destination associated with the values entered on the phone. Then check for an incomplete address, an incorrect key, or a credential copied into the wrong place. Re-enter values from the receiver’s instructions rather than guessing at their format.
If the phone shows a camera image but the destination does not, inspect the receiving screen as well as the phone. Make sure you are looking at the intended input and understand whether its preview or publication control needs a separate action. A clean local camera view is useful for framing, but it is the receiving view that tells you what has arrived.
If picture arrives without the intended sound, check the selected audio source and permissions on the phone, then listen at the receiver. Make one change at a time and repeat the check so you can identify what changed. Keep the intended microphone position in place during the final trial; handling the phone differently can make the audio check less representative of the actual setup.
If an interruption occurs, write down what you saw before changing settings. Did the receiving picture disappear, freeze, or return? Was the app still showing an active connection? Check the current instructions for both the app and receiver before changing a recovery setting. Those observations give you a clearer problem description if you need help from the service.
When switching protocols for a comparison, return to the known working connection if you need to isolate a new setup issue. Keep its details separate from the second connection’s details, and verify the correct destination again before each test.
A fixed phone rig keeps power and framing organized
Arrange the phone where it will actually film before completing the comparison. Check that the mount holds the intended orientation, that the camera has a clear view, and that you can reach the screen without disturbing the shot. Route cables so their weight does not pull on the phone or obstruct the microphone.
Plan phone power and accessory power as separate parts of the rig. Identify the power source and cable each item needs, then check the assembled setup with the phone in its final position. If you plan to move between locations, make a short packing list of the cables, adapters, and mounting pieces you used during the successful trial.
For a setup that includes active phone cooling, our KryoZon K12 Ultra-Light Magnetic Phone Cooler uses a magnetic attachment and requires a PD 5V-3A power supply. Position it so the attachment, cable, mount, and camera can coexist in your particular rig, and keep its airflow clear. Check your received audio with the complete arrangement in place.
Once the rig is assembled, run the connection you chose and inspect both the phone and receiving screen.
Product Specifications
KryoZon K12 Ultra-Light Magnetic Phone Cooler
- Cooling
- Semiconductor TEC
- Power
- 15W (5V/3A)
- Noise
- 32dB
- Compatibility
- iPhone / Android
Frequently Asked Questions
Should I use SRT or RTMP in Larix Broadcaster?
Use a protocol your receiving input explicitly supports. If it accepts both, we suggest comparing them on the same phone with comparable settings, then choosing based on the delay and interruptions you observe. Larix’s FAQ describes SRT latency as a parameter for packet-loss compensation; total viewing delay also includes other stages.
Where do I get the connection details for my phone stream?
From your receiving service; keep credentials private.
How can I check stream delay without guessing?
Compare an action on camera with the received picture.
What should I check before a public broadcast?
Check picture and sound at the receiver and review its publishing controls. Put the phone, microphone, cables, and power sources in their final positions for the last trial.
References & Citations
- The KryoZon K12 uses a magnetic attachment and requires a PD 5V-3A power supply. (KryoZon K12 Ultra-Light Magnetic Phone Cooler — Wayne-approved product master)