Your video should not contain any intro, outro animation nor general watermark (i.e. event logo) as those will be added downstream by Brainsonic Live.
### Format Our operators are expecting two file exports: - A full edit that includes lower thirds - A clean edit that does not include lower third. We might have to use this and add lower thirds ourselves in case of a sudden change in frame organisation. {{@11#bkmrk-container-mp4-file-e}} ### Delivery timeline - We recommend third parties to provide their asset a week before the event. - In case of an unpredictable change, the final version pre-recorded files need to be provided within a minimum of 4 days before airing. # Live sources ##### Content Brainsonic Live might send you graphic assets to use during production, that might includes: - Backgound slate for multi frame or PiP compositions - Full frame video animations including audio that intend to be played for physical audience ##### Protocol Our operators are expecting a single stream sent to two different ingest endpoints (main/primary and backup/secondary) The protocol we accept is SRT1. SRT is compatible with a majority of encoding software and hardware like [VMix](https://www.vmix.com/help23/index.htm?SRT.html), [OBS](https://obsproject.com/kb/srt-protocol-streaming-guide#:~:text=Stream%20with%20SRT,-Go%20to%20Settings&text=In%20the%20Service%20dropdown%2C%20select,enter%20anything%20for%20the%20key.) or [Tricaster](https://support.newtek.com/hc/en-us/article_attachments/1260802200430). Brainsonic Live provides two local (closest datacenters) SRT, of type `srt-listener`, ingest points IPs. Those ingest points are reachable though port `10 000`. A monitoring output (loop out of what you send on port `10 000`) is provided as well. The final program output can be provided though SRT upon request. *1 In some rare cases SRT cannot be used at event location. Even if we do not recommend it, we can accept RTMP ingest following the same encoding specifications.* ##### Encoding {{@250#bkmrk-container-mp4-file-e}} # Médias pré-enregistrés ### Contenu Vous pouvez envisager deux scénarios : - Vous produisez un contenu prêt à être diffusé - Brainsonic Live intègre vos ressources dans un programme maître. ##### Vous produisez un contenu prêt à être diffusé Dans ce cas, nous attendons des fichiers vidéo, respectant le format, qui sont prêts à être lus. Ce contenu ne doit pas contenir de boucles vidéo pre et post comme expliqué dans la page Grille de programmes. ##### Brainsonic Live intègre vos ressources dans un programme maître Brainsonic Live peut vous envoyer des ressources graphiques à utiliser lors de la post-production : - Un modèle de tiers inférieur personnalisable dans un format pratique (fichiers[ .mogtr compatibles Adobe CC](https://helpx.adobe.com/premiere-pro/using/motion-graphics-templates.html)) - Une image de fond pour les compositions multi-images ou PiPVotre vidéo ne doit pas contenir d'animation d'intro ou d'outro, ni de filigrane général (par exemple le logo de l'événement), car ceux-ci seront ajoutés en aval par Brainsonic Live.
### Format Nos opérateurs attendent deux exportations de fichiers : - Un montage complet incluant les tiers inférieurs - Un montage propre qui n'inclut pas les tiers inférieurs. Nous pourrions être amenés à utiliser ce dernier et à ajouter nous-mêmes les tiers inférieurs en cas de changement soudain dans l'organisation du cadre. {{@11#bkmrk-container-mp4-file-e}} ### Délai de livraison - Nous recommandons aux tiers de fournir leur matériel une semaine avant l'événement. - En cas de changement imprévisible, les fichiers préenregistrés de la version finale doivent être fournis au minimum 4 jours avant la diffusion. # Program schedule To not take any chance to get late and start out of cue sync, we recommend the following schedule, especially if you are planning a massive output (i.e., multiple channels):
To avoid useless complexity we ask organizers to fill and use our template for simulive and thrid parties streaming projects. It's available in [Microsoft Excel](https://docs.streamaura.net/attachments/2 "Third parties streaming template") format.
# Expected pre-recorded video file format| Container | MP4 |
| File extension | .mp4 |
| Video codec | H264 (Profil High, Level 4.2) |
| Video resolution | 1920x1080 (1080x1920 for 9:16 ratio) |
| Video interlacing | Progressive |
| Video frame rate | 25 or 30 fps |
| Video bitrate | 10 to 17 Mbps - Constant Bitrate (CBR) |
| Audio codec | AAC |
| Audio tracks / Channels | 1 track / 1 or 2 channels |
| Audio sampling rate | 44,1 - 48kHz |
| Audio bitrate | 128 - 256 kbps |
These parameters are intentionally chosen to provide the **best balance between quality, compatibility and performance**: **Excellent visual quality** for Full HD (1080p) content **Maximum device compatibility** (desktop, mobile, tablets, smart TVs, set‑top boxes) **Predictable playback performance**, including hardware decoding **Optimized storage, bandwidth usage and transfer times**
For video content with alpha channel a Apple ProRes 4444 encoding is requiererd
# Expected live source stream format| Protocol | SRT push |
| Latency | 200ms |
| Video codec | H264 |
| Video resolution | 1920x1080 (1080x1920 for 9:16 ratio) |
| Video interlacing | Progressive |
| Video frame rate | 25 or 30 fps |
| Video bitrate | 5 to 7 Mbps - Constant Bitrate (CBR) |
| Audio codec | AAC |
| Audio tracks / Channels | 1 track / 1 or 2 channels |
| Audio sampling rate | 44,1 - 48kHz |
| Audio bitrate | 128 - 256 kbps |