MLCG Editor lets you design broadcast graphics visually, publish an HTML output and control its data and animation from your application.
This workflow combines three components: the editor creates the graphics, the REST client controls them, and the SDK HTML5 Overlay plugin renders them over video. The examples below show how those components fit together.
MLCG is optional. The HTML5 Overlay plugin can also render your own HTML/CSS/JavaScript without MLCG or its REST client.
In this guide: integration workflow, sample paths, video sources, and data and animation controls.
What each component does
| Component | Responsibility |
|---|---|
| MLCG browser editor | Design templates, configure animation, expose editable data bindings and publish live sessions. |
| SDK HTML5 Overlay plugin | Render an HTML output URL on the SDK machine and composite it over video. Your application controls video playback, processing and output. |
| MLCG.RestControl | Discover accessible sessions, update binding values and send animation commands. It does not decode video or render graphics. |
A template is a reusable design. A published session is a live instance of that design that your application can control. Its output URL is the read-only HTML view you load into the plugin—not the editor page or a REST endpoint.
Integrate a published session
- Create the design in MLCG Editor. Expose values such as headline, team or score with clear data-binding keys.
- Publish a session through the editor's live controls. Saving a template in the Library does not publish it.
- Discover the session with an authorized REST token, then read its bindings. Use a returned session ID, not a Library template ID.
-
Load the output URL into the SDK HTML5 plugin on your video path. Copy it from the editor or create it with
BuildOverlayUrl. - Send binding updates and animation commands through the REST client. The output page receives the changes, and the plugin renders the graphics locally.
For design and publishing, see the MLCG Editor documentation on GitBook and Editor Overview. For a complete read-only C# example and control methods, see Control MLCG graphics from C# (REST client).
The hosted REST and HTML output addresses are normally both https://cg.medialooks.com. For an on-premises deployment, configure the hosts for that installation.
Deployment: MLCG Editor is available free of charge to HTML5 Plugin users. On-premises installation is available for an additional fee; see MLCG on-premises installation requirements.
SDK samples and installation paths
The MLCG HTML REST C# samples provide the same graphics workflow for MPlatform and MFormats. Use the edition that matches your application's SDK API family.
Default executable and solution paths:
MPlatform executable:
C:\Program Files (x86)\Medialooks\MPlatform SDK\Samples Basic\C#\MLCG HTML REST\bin\x64\Debug\MLCG HTML REST.exe
MPlatform solution:
C:\Program Files (x86)\Medialooks\MPlatform SDK\Samples Basic\C#\MLCG HTML REST\MLCG HTML REST.sln
MFormats executable:
C:\Program Files (x86)\Medialooks\MFormats SDK\Samples\C#\MLCG HTML REST\bin\x64\Debug\MLCG HTML REST.exe
MFormats solution:
C:\Program Files (x86)\Medialooks\MFormats SDK\Samples\C#\MLCG HTML REST\MLCG HTML REST.sln
Replace the SDK root if you installed it elsewhere. For shared runtime, architecture, licensing and build requirements, see Before you start.
Try real graphics in the sample
- Click Try demo to create a private temporary workspace with real server templates. No account token is needed.
- Choose File or URL / Stream in the Source dropdown and open your video source.
- Select a template. The sample prepares the output and starts its animation once over video.
- Edit exposed binding values and click Apply data to update the graphics.
Each demo launch has separate session copies: your changes do not affect another launch. The sample displays the expiry time, renews the lease while in use and releases control on close. Demo edits are temporary; no shared user password is involved.
Use your own published sessions
Enter an authorized REST token and click Connect instead of Try demo. The list shows published sessions visible to that token, subject to account and workspace permissions. It is not a list of every template in your Library.
MPlatform edition
MPlatform connects its source and preview objects and attaches the HTML5 plugin to the video path. This sample uses one video source and one selected graphics session; it is not a playlist scheduler.
MPlatform edition using a private Demo Workspace and the real “News Pro • Anchor Lower Third” template from cg.medialooks.com, with its original data.
MFormats edition
MFormats uses an application-owned frame loop: pull and convert a video frame, process it with HTML5 Overlay, then send the composite frame to preview. The sample controls frame ownership and releases its frames and SDK objects during cleanup.
MFormats edition using a private Demo Workspace and the real “News Pro • Breaking Banner + Crawl” template from cg.medialooks.com, with its original data.
Video shown in the screenshots: Big Buck Bunny, Blender Foundation, CC BY 3.0.
Choose a video source
The Source dropdown starts with File and URL / Stream, followed by currently discovered SDK mp:// senders.
- File opens a native file picker immediately. Choose a local file or an accessible network file. Browse… opens the picker again.
- URL / Stream opens the stream-address dialog immediately. Enter a UDP, SRT, RTSP, RTMP or other transport address supported by your installed SDK. Open… reopens the dialog. The address must identify media, not a web-player page.
-
Select a discovered
mp://Sender Nameto open it immediately. An MSink/MFSink or other SDK sender must already be publishing on the same computer. Sender names can contain spaces. - Open the dropdown or click refresh to rescan senders. Refresh does not reopen the active source or restart graphics. If the selected sender disappears, it is marked unavailable; the sample does not silently select a different source.
An mp:// input displays LIVE and disables file Pause because the sending application owns playback. MPlatform excludes its own source from discovery to avoid a self-link.
The sample fits video to 1920 × 1080 before HTML composition, preserving aspect ratio with letterboxing where needed. It retains the source frame rate rather than forcing 60 fps. This conversion happens during playback; it does not transcode the file.
Use graphics designed for a 1920 × 1080 canvas. For another output format, change the video conversion and HTML sizing together.
Edit data and control graphics
- Show prepares the selected output and starts its animation from the beginning.
- Hide removes this application's overlay locally, without a REST command. It also works for a visible prepared overlay after demo control expires.
- Apply data sends only changed binding values. Reload reads the current data and discards unsent field edits.
- Restart starts the scene from zero. Graphics Play/Pause is independent of video playback.
- Release the animation seek slider to send one pause-at-position command. Video can continue while graphics stay at that position.
- Loop controls the scene animation, not video-file looping. Intrinsic ticker scrolling and per-layer repeats may continue independently.
REST data and animation commands affect every output using the same session. Local Hide, preview mute and fullscreen affect only this application. Use a private Demo Workspace or a dedicated test session while learning.
To avoid two visible starts, the sample loads a new output hidden with autoplay disabled. It waits for the scene, fonts and images, sends one Restart, then reveals the output.
The graphics playhead estimates the commands issued by this sample; it is not a remote rendering acknowledgement. Processed FPS measures the SDK processing path, not browser paint rate or monitor presentation.
These REST samples do not provide frame-accurate synchronization between graphics and source-video pause or seek. A completed HTTP command does not confirm that a particular video frame has been painted.
Local preview: mute and fullscreen
Find the speaker and fullscreen buttons in the Video + graphics header. They control the local preview, not the graphics session.
- Mute / Unmute changes preview audio monitoring. The setting survives video pause/resume, source changes and fullscreen transitions during the same run.
- Fullscreen / F11 moves the existing preview into a borderless window. Video and graphics continue without reloading the template or restarting animation.
- Press Esc or F11, or click Exit fullscreen, to return. The fullscreen toolbar also includes Mute / Unmute.
Mute does not change source media, pause playback, mute another receiver or send a REST command. Fullscreen changes display placement, not design resolution or animation timing.
Fullscreen uses the same running video-and-graphics preview. Use Esc, F11 or Exit fullscreen to return to the main sample window.
Activity and troubleshooting
Activity… opens a sanitized diagnostic log in a separate, nonmodal window. You can keep it open while using the sample without shrinking the preview. Closing the log does not stop playback.
- No sessions: check the account, token permissions and publishing status, or start a private demo.
- Demo expired: start a new demo to continue REST editing. Local source/video controls and Hide remain available independently of the lease.
- Graphics not ready: inspect the page-ready state and Activity log. A successful REST connection does not mean the browser has finished preparing the page.
- Unexpected performance: compare Processed FPS with the source properties. To diagnose rendering or audio, check actual output as well; this counter alone cannot prove browser paint rate, audible audio or frame-accurate output.
Use the public REST client in your application
The samples use public MLCG.RestControl 1.0.2 from NuGet.org. It provides Demo Workspaces, named animation commands, timing metadata and seeking without a private feed or wrapper source-project reference.
<PackageReference Include="MLCG.RestControl" Version="1.0.2" />
For code examples, see Control MLCG graphics from C# (REST client). These examples use the standard SDK HTML5 Overlay plugin and the public REST client package.
Keep control credentials separate from output links
Store REST tokens in secure application configuration. Do not put them in source code, screenshots, logs or HTML output URLs.
An output link does not grant REST editing, but anyone with a usable link may be able to view its graphics and data. Share it only with intended viewers. Use separate sessions when operators or outputs need independent data.
Related documentation
- Control MLCG graphics from C# (REST client)
- Public MLCG REST Client GitHub repository
- MLCG.RestControl 1.0.2 release
- MLCG Editor documentation on GitBook
- C# REST Wrapper reference on GitBook
- HTML5 Overlay overview and quick start
Explore the MLCG template gallery for real default designs, animated previews and editable-content examples.
Still have questions?
Tell us what didn’t work or what you’d like clarified.