futzu
commented
4 months ago First thing you need to understand, splice points must be at iframes. Other types of frames that occur between iframes are modifications to the iframe and not complete images themselves. x9k3 is not an encoder, but it is a segmenter If you need to re-encode, re-encode and then pass it to x9k3 and let it segment the video. If you are accepting video from lots of different sources,
you probably will need to re-encode to a standard format, and when you do that, I'd add an iframe at every second. A lot of people will balk at that, and they also miss a lot of splice points. Having an iframe every second means that in a worst case scenario, your splice point would be off by one second, and I have a technique that will reduce the worst case from 1 second down to 0.45 seconds.
This is what I do for a living. For the last four years I have done nothing except SCTE-35 and HLS. If you want to hire me, this is absolutely in my skill set and honestly I am the best person at know at this sort of thing.
Just to put things in perspective, if you hire me to do a project, let's say it takes 3 months, if you do it by yourself, it will take at least a year.
What I just told you about iframes, would have taken a couple of months to sort out, if not longer. Five years ago, it was common to see one iframe every six seconds, now that's considered insane, and most people are using two to four seconds. I spent months testing GOP sizes and that's why I say one every second.
Adrian
raggedstetson
I am new to the field of video production, and I was attempting to use x9k3 to solve a problem, but I am not certain if it is the correct tool. I was hoping I might be able to contact you via email or even jump on a phone call.
I am working with a company that produces live streamed events. We save the video stream from those events, and then also make them available as VOD on different platforms. I would like to integrate with google ad manager, but google requires "preconditioning" the videos. In particular, I would like to do server-side ad injection (SSAI, also often called DAI) using a stitcher. I see that google ad manager can accept an MRSS feed (which has a google-specific namespace to identify cue-points) or they can accept files from BrightCove.
My goal is to allow my content editors to create a new piece of content (maybe an edited live stream or even a highlight reel pieced together from many streams). I would then like the editors to be able to place ad breaks (maybe cue-points, maybe SCTE 35 markers, I'm not sure) into the video at any points they choose. I attempted to do this with your x9k3 tool and adbreak tool, but it seemed as if the resultant m3u8 file was not re-encoded (but rather just split on the nearest I-Frame) - I say this because it appeared that the cue-out was not at the offset I had configured, but somewhat close.
I would like my users to be able to place ad breaks at specific locations and then have google ad manager respect those locations - possibly by having an MRSS feed that google ad manager can ingest. I am somewhat shaky on the details since it seems redundant to me that I should need cue-points in the MRSS feed but then also need the m3u8 file to reflect those same cue points.
In short, I would be very grateful for any assistance you might be able to provide to help me solve this problem. If you know how to add ad breaks to existing videos so they work with google ad manager server-side ad injection, I would love to learn how. I am also happy to compensate you for any assistance, or I would be grateful if you could refer me to another person if you are not familiar with this particular situation.
Thank you.