User manual

OinkScape is a Windows desktop application from OinkWave that brings together scheduled playback, playlists, optional video and web surfaces, Streaming player (incoming network streams), Web Broadcasting (outbound to providers), text-to-speech, and Windows-level mixer controls in one window. It is aimed at operators who want a single control surface for shows, routines, and experiments—without chaining half a dozen separate utilities.

This manual describes the user-visible behavior of the app: what each major area does, how queues and schedules interact, and where Windows or third-party components (FFmpeg, PyQt WebEngine, optional volume APIs) affect results. It is not a legal contract; product details can change between beta builds.

What OinkScape is not: It is not a full digital audio workstation (DAW), not a replacement for a dedicated broadcast chain, and not guaranteed to drive every third-party DJ or media program on a timer. Scheduled launch or termination of external executables (e.g. other DJ apps) is not part of the current build; that may be reconsidered later based on feedback.

• OS: Windows 10 or 11 (64-bit). Other platforms are out of scope for this product line today.
• RAM / CPU: A dual-core system with 4 GB RAM meets minimums; 8 GB+ and a quad-core CPU are recommended for heavy schedules and simultaneous audio + video + web.
• Disk: The installed app (Qt, optional WebEngine, Python runtime) uses hundreds of megabytes; allow extra space for media, caches, and recorded clips.
• FFmpeg: Many compressed formats (e.g. MP3, OGG) need FFmpeg available to the app—either bundled next to the executable, under a configured ffmpeg folder, or on PATH. WAV is the most friction-free format without FFmpeg.
• PyQt WebEngine: The Web tab renders pages inside the app when the WebEngine component is installed. If it is missing, the app may open links in your default external browser instead.
• Windows audio bridge (pycaw / COM): Master volume and per-application session sliders depend on Windows exposing sessions. Behavior varies by app and driver; not every program reports volume the same way.
• Network: Useful for loading remote URLs, playing incoming streams, Web Broadcasting (outbound), feedback forms, and help pages. There is no in-app auto-updater in the current beta; you install new builds manually.

Install from the published Windows installer when OinkWave provides one. The first launch may create or migrate user data under your profile (settings, schedules, caches). If the build is a beta, the app shows an expiry date—after that date it stops until you install a newer build (see Beta builds & expiry).

Grant administrator rights during install if the installer requests them; some audio or firewall scenarios are easier when the app is installed to a standard location with proper permissions.

The main window is organized as tabs, including Audio, Video, Web, Streaming player (play incoming network streams), Web Broadcasting (send your show out to the web), TTS, Schedule, and surfaces such as Control room / Master overview depending on your version and settings. Streaming player and Web Broadcasting are not the same tab—one pulls media in, the other pushes your program out. A status area typically shows the current time and transport-related hints. Tab order and visibility may be configurable in Settings.

Use tooltips (hover over controls) for field-specific explanations—the app ships with descriptive tips on many buttons, sliders, and lists.

Queue & playback

The main audio player maintains a queue of tracks. You can add files, remove or clear entries, and control play / pause / stop, seek position, and volume. When a track ends, the app advances according to the current mode (e.g. next in list).

M3U playlists

OinkScape reads and writes standard M3U files through the file dialog. Build your queue in the app, then save as M3U, or open an M3U produced by another tool. Drag-and-drop directly onto the queue is not relied on as the primary workflow in the current beta—use add/browse actions and M3U where needed.

Folder pools

You can treat a folder as a pool of media: the app scans for compatible files and can play in shuffle or sequential order. Where metadata exists, genre / tag filters (backed by mutagen) help narrow the pool. A rolling pool mode keeps the queue topped up: as tracks finish, new random picks from the same folder can refill the list toward a cap—so long sessions do not require a giant static queue.

Preload & cache

Settings may expose limits for preload size and decode cache (upper bounds on the order of gigabytes in recent builds). Larger values can smooth transitions on big libraries at the cost of RAM and disk I/O.

Transforms & speed

Where exposed in the UI, playback may support speed / pitch style adjustments for the main audio path—use these for temporary fixes or creative effects; extreme settings can affect quality.

The Video tab has its own queue and playback controls separate from the main audio queue. You can load files, manage order, adjust aspect or playback speed where supported, and use M3U-style workflows analogous to audio. Folder-pool behavior may mirror audio (including rolling refill) with smaller typical queue caps for video.

Scheduled actions can inject a specific video path or list in line with automation (see Schedule).

When PyQt WebEngine is available, the Web tab shows pages inside OinkScape (navigation, URL bar, tabs as implemented). If WebEngine is not installed, the app may fall back to opening URLs in your default system browser.

Web content is subject to site policies, mixed content, and autoplay rules—identical pages may behave differently than in Chrome or Edge depending on the embedded engine version.

OinkScape exposes two different streaming-related tabs. They solve opposite problems—do not treat them as one feature.

8.1 Streaming player (incoming)

Use the Streaming player tab when you need to bring media in from the network: paste or enter a stream URL and play it inside OinkScape (for example HLS (.m3u8) or other formats the build supports). This path is for playback and monitoring of remote sources—not for pushing your mix to Twitch, YouTube, etc.

Reliability depends on the remote server, your connection, and codec support (often via FFmpeg where applicable). If a URL fails, confirm it plays in a known-good player and that firewalls or TLS policies are not blocking the feed.

8.2 Web Broadcasting (outgoing)

Use the Web Broadcasting tab when you want to broadcast your show outward—for example RTMP or RTMPS to a provider—using FFmpeg after you set destination URL, codecs, and audio/video sources. You typically choose capture devices or system audio endpoints consistent with your sound card and drivers.

Outbound streaming is resource-intensive; close unnecessary apps and verify bitrate and resolution against your upload bandwidth. Follow your provider's current ingest guidance for bitrate, resolution, and keyframe interval.

The TTS tab uses Windows speech APIs (e.g. SAPI voices) to read text you provide. Controls typically include voice selection, rate and volume, and optional ducking—temporarily lowering other OinkScape audio so speech is intelligible.

TTS is intended for IDs, announcements, and automation—not for long-form narration at broadcast quality.

The Schedule tab combines a calendar with timed events. Events can be one-shot or recurring (daily, weekly, by interval, etc., as implemented). Each event can run a multi-step scene: ordered or layered actions involving audio, video, web, Streaming player / Web Broadcasting (as exposed in your build), and TTS as the app supports.

Scheduled actions may inject specific files into the audio or video tab (similar to loading an M3U or a single path) with flags for override and one-shot behavior—consult on-screen options when creating an event.

Export / import of schedule data is available for backup and migration between machines (alongside full environment backup—see below).

The Control room / Master overview area aggregates transport, DJ-style decks, and quick access to related surfaces (e.g. video, Streaming player, Web Broadcasting, web toggles depending on version). It is meant as an operational dashboard for live sessions: start/stop, cue, and see status at a glance.

The mixer surfaces master volume and balance for the default playback device when the Windows bridge is active. Per-session sliders adjust individual applications that appear in Windows’ audio session list—useful for balancing browser, game, or chat against your show audio.

Clip decks hold short sounds (IDs, stingers). You can record from a chosen input device (mic, line-in, or virtual cable) into slots when the OS lists the device. Levels and metering help avoid clipping.

Settings cover theme (light/dark or accent choices as implemented), tab order, audio preload limits, optional mirror or backup paths, network-related diagnostics, and other environment options. Changes may require restarting specific subsystems or the whole app—follow any on-screen prompts.

Diagnostics collects health information and readable logs to help troubleshoot audio devices, permissions, and crashes. When you choose to send feedback, the app may ask for an email address so OinkWave can reply; log paths are scrubbed for privacy before transmission.

The web feedback form accepts the same diagnostic blob when pasted from the app.

OinkScape can export a full environment archive (ZIP) containing settings, schedules, and related data—useful before OS reinstalls or moving to a new PC. Store backups securely; they may contain paths and preferences you consider sensitive.

• Common formats: MP3, WAV, FLAC, OGG and others work when decoders are available; WAV is the safest default without extra setup.
• Place ffmpeg.exe and ffprobe.exe where the app expects them, or set environment variables documented in the README shipped with your build.
• Network paths and removable drives can be slower or intermittently unavailable—prefer local SSD for performance-critical shows.

Beta builds include a published expiry date. After that date the application stops until you install a newer build from OinkWave. There is no in-app update checker in the current line—watch email, the product site, or OinkWave announcements for replacements.

• No drag-and-drop as the primary queue workflow—plan around add buttons and M3U.
• No scheduled start/stop of arbitrary external programs in the current build.
• Per-app volume depends on Windows exposing sessions; some apps behave oddly or not at all.
• No in-app auto-update yet.
• Legal use of streamed or recorded content is your responsibility—comply with copyright, licensing, and platform terms.

© 2026 OinkWave. OinkScape user manual. For product news: OinkScape home.