Please check the following to determine possible causes
- When switching to the pre-recorded content, make sure the live source is no longer connected to the IVS input. Simultaneous sources will cause ingest conflict.
- Is the pre-recorded content being sent to IVS with a bit rate less than 8Mbps? If a source is greater than 8Mbps this may cause problems with the IVS ingest process and a Starvation error could occur.
4K Live Streaming Solution - How to get there?asked 6 months ago
Creating a "Live With" Experience similar to Instagramasked 4 months ago
View live stream 404asked a year ago
Exact semantics of IVS Player getLiveLatency()?asked 6 months ago
IVS or Live Streaming?asked a year ago
AWS S3: Live video streaming data storing into S3asked 14 days ago
AWS IVS player sample code to display Status, Health, Duration and Viewersasked 6 months ago
IVS - live streaming issue - Starvation startasked 7 months ago
How can i use s3 url as Ingestion endpoint to stream video in IVSasked 13 days ago
Media Live detailsasked a year ago