Creating and Uploading an Event in Spalk
An event represents a live broadcast within the Spalk platform. Before commentators, producers, or outputs can be connected, you must first create and configure an event.
This guide walks through the standard upload workflow and explains the key configuration options available during setup.
Before You Start
To create an event, you will need:
- Event title
- Start date and time
- End date and time
- Details of the incoming video feed from your encoder or uplink provider
Step 1 — Navigate to the Upload Page
From the Spalk Dashboard, navigate to the Upload page.
Here you will configure your incoming video feed and event settings.
Step 2 — Select Your Input Type
Spalk supports multiple ingest methods:
- RTMP
- SRT
- MediaConnect
Select the protocol being used by your feed provider
If you are unsure which protocol to use, please contact your Spalk representative or onsite technical team.
Step 3 - SRT Location
Select the ingest region geographically closest to the location the feed is being sent from.
For example:
- London for UK/Europe events
- Sydney for Australia/New Zealand events
- North Virginia for North American events
Selecting the closest region typically provides the most stable and lowest latency connection.
Step 4 — Choose Your Endpoint Type
You can choose between:
Single Use Endpoint
A temporary SRT endpoint generated specifically for this event.
A new address will be created each time you upload a new event.
Persistent Endpoint
A permanent SRT endpoint that can be reused across multiple broadcasts.
Persistent endpoints are useful if:
- You regularly use the same encoder
- You have fixed onsite infrastructure
- You want to avoid reconfiguring encoder settings each event
To configure a persistent endpoint:
1. Select Persistent Endpoint
2. Click Add New
3. Enter the required endpoint details
Please speak with your Spalk support representative before configuring any persistent endpoints.
Step 5 — Configure Ingest Settings
Ingest Bitrate
Set the maximum bitrate being sent to Spalk from your encoder.
This is important as Spalk provisions cloud resources based on the bitrate entered.
Example
Stream Bitrate | Value to Enter
8 Mbps | 8000000
10 Mbps | 10000000
Latency
Set the required SRT latency.
Typical values are:
- 120 ms — Lower latency, commonly used for stable and geographically closer events
- 340 ms — Higher stability for longer-distance or less stable connections
As a general rule:
- Longer-distance contribution feeds should use higher latency values
- Higher latency usually improves connection stability
Bitrate Control
Spalk strongly recommends using CBR (Constant Bitrate) wherever possible.
Please work with your encoder or uplink provider to ensure they are delivering a true CBR feed.
CBR streams are generally:
- More stable
- Easier to decode
- More suitable for live broadcast workflows
Listener vs Caller Mode
Listener Mode
Spalk generates the connection details.
You provide these details to the onsite encoder or uplink provider.
This is the most common workflow.
Caller Mode
The onsite provider supplies the SRT connection details.
Spalk connects outbound to receive the feed.
Use this option when the onsite provider requires your system to initiate the connection.
Step 6 — Select an Encoder Configuration
If you need to transcode the feed, please select the transcode option and then select an encoder configuration.
Encoder configurations determine:
- Video codec settings
- Audio codec settings
- Resolution
- Bitrate profiles
- Audio track mappings
There are multiple preset configurations available within the platform.
Important
Always test encoder configurations before going live.
We strongly recommend testing:
- Several days before the event
- With the exact encoder and workflow being used onsite
This helps identify compatibility or configuration issues before broadcast day.
Step 7 — Upload Optional Assets
You may optionally upload:
Thumbnail Image
Used to help producers and commentators easily identify the event.
No Signal Slate
A fallback image displayed if the incoming feed is lost.
This provides a significantly better viewer and commentator experience than:
- Black video
- Frozen frames
- Loading wheels
Important
No Signal Slates are only available when transcoding is enabled.
Step 8 — Configure Event Information
Event Title
Enter a clear and identifiable event title.
Start Date and Time
This is when Spalk prepares infrastructure and becomes ready to receive your feed.
We recommend scheduling events:
- 30–60 minutes before going live
This provides time for:
- Encoder testing
- Audio checks
- Troubleshooting
- Commentator setup
End Date and Time
This is when:
- Streams stop
- Infrastructure shuts down
You can modify the end time up before the scheduled finish.
We recommend setting a later-than-expected end time to account for:
- Delays
- Overtime
- Extended coverage
Once finished, end the event manually if required.
Production Notes
Use this field to add:
- Internal notes
- Technical instructions
- Production links
- Contact information
- Runbooks or workflows
These notes are visible to producers and dashboard users working on the event.
Step 9 — Confirm Permissions
Before continuing, confirm:
- You have permission to upload the content to Spalk
Then click Next.
Step 10 — Add Commentators and Outputs
After creating the event you will be able to:
- Invite commentators
- Configure producer access
- Schedule outputs
- Configure destinations and delivery settings
Timezones
All dates and times displayed within the upload workflow use your system timezone.
Comments
0 comments
Please sign in to leave a comment.