Stream Setup
Encoder, scenes and audio for a professional stream
Twitch Stream Setup System
Write your briefSample result, from a real run
Made from this brief: Ryzen 7 5800X, 32GB RAM, RTX 3070, streaming from the same machine I code on. Elgato Cam Link 4K with a Sony ZV-E10 as the webcam, a Shure SM7B into a Focusrite Scarlett Solo, and a Stream Deck Mini.…
HARDWARE VERDICT
You have a Ryzen 7 5800X, 32GB RAM, and an RTX 3070, which places you in the high-end tier for encoding. The RTX 3070 allows for hardware encoding via NVENC, which is the recommended encoder for your setup. However, it's noted that you're streaming from the same machine you use for coding, which may impact performance if resource-intensive tasks are running in the background.
ENCODER SETTINGS
For your high-end setup with an RTX 3070, the recommended encoder settings are:
- Encoder: NVENC (H.264)
- Preset: Quality or Performance, depending on your specific needs and the complexity of your streams
- Bitrate: This will be determined by your upload speed (see UPLOAD MATH section)
- Resolution: 1080p or 936p/720p60, depending on the content type and your internet upload speed
- Frame Rate: 60fps for fast-paced content like gameplay, or 30fps for more static content like Just Chatting or creative streams
- Keyframe Interval: 2 seconds
- Rate Control: CBR (Constant Bit Rate) for consistency
UPLOAD MATH
Given your upload speed is 18 Mbps, the maximum bitrate for streaming should not exceed half of this, which is:
18 Mbps * 1000 kbps/Mbps / 2 = 9000 kbps
However, considering the high-end tier's bitrate band (6,000–8,000 kbps) and to ensure stability and quality, a bitrate of 6,000 kbps could be a more conservative and suitable target for 1080p60 content, keeping in mind the specific requirements of your content and the performance of your hardware.
SCENE SET
Given the clarkbuilds streamer's creative coding and generative art focus, with a calm and studio-like brand vibe, the following scene set is designed to enhance the viewer experience:
SCENE: Starting Soon
Purpose: Displayed while viewers arrive, before the stream goes live
Sources (bottom to top):
- Image - 0%, 0%, 100%, 100% (static graphic with channel name, socials, and a muted background)
- Text - 40%, 40%, 20%, 10% (countdown timer)
Changes from previous scene: N/A, this is the first scene
SCENE: Just Chatting
Purpose: Viewer interaction before main content, with a focus on chat
Sources (bottom to top):
- Camera - 10%, 10%, 80%, 80% (Sony ZV-E10 webcam feed)
- Chat widget - 80%, 10%, 20%, 80% (positioned for easy reading)
Changes from previous scene: Replaces static graphic with camera feed, adds chat widget
SCENE: Main Content
Purpose: Primary stream content, such as coding or generative art
Sources (bottom to top):
- Screen capture - 0%, 0%, 100%, 100% (focused on the coding or art area)
- Chat widget - 0%, 0%, 20%, 80% (kept on screen for continuous interaction)
- Alert box - 80%, 0%, 20%, 10% (for subscriptions, donations, etc.)
Changes from previous scene: Moves focus to main content, keeps chat visible
MIXER LEVELS
| Source | Target | Why |
|---|---|---|
| Microphone | −12 to −6 dB, peaks around −12 | loud enough to sit above the game, short of clipping |
| Desktop / game audio | −20 to −12 dB | present, never competing with the voice |
| Music | −25 to −18 dB | audible, not the reason people leave |
| Alerts | at or below desktop audio | an alert that startles the viewer is a mixing error |
To check these levels, speak at a normal volume and observe where the meter sits. Then, shout once to confirm that the peak does not hit the red. Adjust the microphone level while talking quietly into it to avoid a level that's too low, which is a common issue with first streams.
FILTER CHAIN
For the microphone in OBS, apply the following filters in this order:
- Noise Gate: Set the close threshold below your quiet speaking level to prevent clipping of your first syllable.
- Noise Suppression: Use the RNNoise filter for a free and effective solution. Paid options like the GPU-vendor ones offer cleaner suppression for constant noises.
- Compressor: Apply a modest ratio to even out the gap between a whisper and a shout. Avoid heavy compression, which can make your stream sound like a call centre.
- Limiter: Always place this last, as it acts as a safety net to prevent one loud reaction from clipping the whole stream.
SOFTWARE SETTINGS
PRE-STREAM
- Verify microphone level: speak at normal volume and confirm the meter sits near −12 dB, not in the red.
- Check camera framing and lighting: ensure the camera captures your face and workspace clearly, and adjust lighting to minimize harsh shadows and glare.
- Confirm every scene loads: test each scene to ensure all sources are visible and functioning as expected.
- Ensure chat widget or second-screen chat is live: verify that chat is updating in real-time and is easily readable.
- Close unnecessary applications: silence notifications and close any apps that may cause distractions or interfere with the stream.
- Select the correct stream key: double-check that you're using the correct stream key for your account.
- Enable recording or VOD saving: if desired, ensure that the stream will be recorded or saved for later use.
- Set up the Starting Soon scene: confirm that this scene is live before the stream key goes live.
- Prepare the go-live announcement: have the announcement ready to post when the stream goes live.
- Enable captions: widen your audience and improve accessibility by enabling captions, which help in noisy rooms and can be clipped for short-form platforms.
GO LIVE
How it works
Add your computer, camera and microphone
CPU, GPU, RAM, camera and mic, as specifically as you can. "Ryzen 5 5600X, RTX 4060, 16GB, Logitech C920, Blue Yeti" gets you real encoder settings. "A gaming PC" gets you a guess, and we will tell you it is a guess rather than dressing it up as a spec.
We draft it
The app works through its steps and hands back:
- Encoding Plan
- Scene Plan
- Audio Chain
- Go Live Runbook
Refine and export
Change the brief and run it again, or open the full run to read, copy and download each file.
Questions
What is a credit?
The unit a run is priced in. Each app has a fixed price in credits, shown on its Generate button, and a run costs exactly that. Nothing is metered by length or time.
Am I charged if a run fails?
No. Starting a run holds the credits rather than spending them. The hold becomes a charge only when the run succeeds; a failed or cancelled run releases it.
Can I edit the brief and run it again?
Yes. Change any input and press Generate again, or open an earlier run and choose Adjust and run again to start from a copy of its brief. Uploaded files need attaching again. Each run is new and costs the applet's price; the earlier run stays as it was.
Where are my results kept?
Every run you start is listed under Your runs at /create/runs. Each one opens its own page, where you can read, copy and download the files it produced.
More apps
All Community apps- Comment RepliesA full comment section answered in your voiceTry it · 5 credits
- Community PostsA quarter of Community tab posts, ready to pasteTry it · 8 credits
- Collab PitcherPick the right creators and write the pitch they answerTry it · 8 credits
- LinkedIn PostsTwo weeks of LinkedIn posts built on one authority lineTry it · 8 credits