Plex now has commercial removal built in

No arguments about that for completed files. But try writing to a MKV and using it at the same for Live TV and you will find yourself in a world of hurt. :slight_smile:

@AmazingRando24 said:

@fecaleagle said:

@cayars said:
One of the major issues with MKV is that it’s very hard to use for LiveTV. The TS format is perfect for this.

It’s perfect to use for clients that support it and support it well, but when it hits a bad audio block on an insufficient player (mostly due to signal drop), the audio will fall out of sync.

(cough… Plex Windows Store app… cough…)

Yea, cough, cough is about right. :slight_smile:

@cayars said:
No arguments about that for completed files. But try writing to a MKV and using it at the same for Live TV and you will find yourself in a world of hurt. :slight_smile:

Ah, good to know. I’m definitely interested in LiveTV so I guess I’ll give up on MKV. Maybe Plex could instead fix the issues with TS files? My issue is that it takes 10 seconds to skip forward/back. I’m sure that’s not the only issue with TS files, but that’s the one that affects me the most.

Being from the UK, any mcebuddy and comskip configs for uk broadcasts Ive tried in the past has never worked, but sofar plexs implication has worked pretty damn well - so good bloody job from me

@timeslip1974 said:
Being from the UK, any mcebuddy and comskip configs for uk broadcasts Ive tried in the past has never worked, but sofar plexs implication has worked pretty damn well - so good bloody job from me

Thanks! I think it has to do with our custom comskip.ini configuration we ship with it. You can add your own custom file, and there are tons floating around, which would change the behavior.

@kinoCharlino said:

@timeslip1974 said:
Being from the UK, any mcebuddy and comskip configs for uk broadcasts Ive tried in the past has never worked, but sofar plexs implication has worked pretty damn well - so good bloody job from me

Thanks! I think it has to do with our custom comskip.ini configuration we ship with it. You can add your own custom file, and there are tons floating around, which would change the behavior.

Definitely encouraging to see the commercial cuts working for several people. Personally I’m waiting for public release before I give it a shot.

@kinoCharlino Question though, from what I understand, comskip has been a difficult process to get 100% accurate in the past. And some users testing out the function have already indicated that parts of their shows are getting cut. Is Plex seriously proposing that they’ve unlocked a secret to make the commercial cuts 100% accurate on all channels? If so, obviously huge kudos to the dev team.

@mbarylski said:
Definitely encouraging to see the commercial cuts working for several people. Personally I’m waiting for public release before I give it a shot.

Totally understand.

@kinoCharlino Question though, from what I understand, comskip has been a difficult process to get 100% accurate in the past. And some users testing out the function have already indicated that parts of their shows are getting cut. Is Plex seriously proposing that they’ve unlocked a secret to make the commercial cuts 100% accurate on all channels? If so, obviously huge kudos to the dev team.

You’re correct, it’s difficult to get perfect. I’m not sure if that’s possible, maybe it is with a lot of trial and error. But making it perfect for everyone… now that, maybe truly impossible. Still, it’s going to be improved over time to make it work better for more people. I don’t think our implementation is perfect, but the aim is that it should eventually work very well. It’s certainly easier to use and doesn’t require knowing how to do post-processing via script, so more convenient for many users.

@kinoCharlino Question though, from what I understand, comskip has been a difficult process to get 100% accurate in the past. And some users testing out the function have already indicated that parts of their shows are getting cut. Is Plex seriously proposing that they’ve unlocked a secret to make the commercial cuts 100% accurate on all channels? If so, obviously huge kudos to the dev team.

So far i have had a great experience with plex’s implementation of comskip, thanks a bunch PLEX Team! i do have a question in regards to mbaryski’s question above: is the plex team actively working on the comskip ini file for various TV channels/providers to improve its performance?

It works well for me because I don’t care much. It certainly isn’t perfect, but I’m also not perfect on stopping on the Whammy when fast forwarding, and I don’t often rewind to make sure I caught every second unless I feel like I really missed something. Plex seems to be picking up the ball and running well for me in this manner.

I also never intend to keep recordings long term… so I don’t need them to be perfect for history. I’ll RIP full seasons from a more formal presentation of the show if I want to keep them in the archive.

If this is how you’re using your DVR, then I recommend giving it a shot.

@toxlab said:
is the plex team actively working on the comskip ini file for various TV channels/providers to improve its performance?

We’re not at this time, but users could override the config if they want more control.

@kinoCharlino said:

@mbarylski said:
Definitely encouraging to see the commercial cuts working for several people. Personally I’m waiting for public release before I give it a shot.

Totally understand.

@kinoCharlino Question though, from what I understand, comskip has been a difficult process to get 100% accurate in the past. And some users testing out the function have already indicated that parts of their shows are getting cut. Is Plex seriously proposing that they’ve unlocked a secret to make the commercial cuts 100% accurate on all channels? If so, obviously huge kudos to the dev team.

You’re correct, it’s difficult to get perfect. I’m not sure if that’s possible, maybe it is with a lot of trial and error. But making it perfect for everyone… now that, maybe truly impossible. Still, it’s going to be improved over time to make it work better for more people. I don’t think our implementation is perfect, but the aim is that it should eventually work very well. It’s certainly easier to use and doesn’t require knowing how to do post-processing via script, so more convenient for many users.

Got it, if that’s the case, might be good to have some way of tracking success per channel and pin it to the top of the forum. Maybe some kind of poll that shows accuracy per channel to make it easier for users to decide which shows they should enable commercial cuts and which they shouldn’t. And implement chapter marks that can be auto-skipped vs actually cutting the commercials out. That’s the preferred solution and the one implemented by both TiVo and PlayOn.

Really appreciate the function regardless though. I’ve been debating getting a new TiVo so I can do commercial cuts. While TiVo is 100% reliable (given they have people manually mark commercials), it requires another box and several steps to get from recording, to cuts, to Plex, rather than a single solution with Plex.

@AmazingRando24 said:
It works well for me because I don’t care much. It certainly isn’t perfect, but I’m also not perfect on stopping on the Whammy when fast forwarding, and I don’t often rewind to make sure I caught every second unless I feel like I really missed something. Plex seems to be picking up the ball and running well for me in this manner.>
I also never intend to keep recordings long term… so I don’t need them to be perfect for history. I’ll RIP full seasons from a more formal presentation of the show if I want to keep them in the archive.>
If this is how you’re using your DVR, then I recommend giving it a shot.

Exactly! That’s basically what I’m saying as well. Not perfect but neither am I. MUCH easier and simpler than setting up MCEBuddy.

@mbarylski You can somewhat easily tell if it’s going to work. If the stations you watch normally have a Station logo before or after a commercial break, or a ratings like PG13 shows in the upper corner it picks that up and uses that and those channels always seem to work well. Discovery, and History channels are my headache channels. Never seems to work well on them…

P.S> Night two I had 3 shows recording every hour on the hour for primetime 8-11 and when it went to work removing commercials from This is Us, it crashed Plex. I didn’t realize until I went to bed and couldn’t find my server on my Shield and went to see what happened. Wasn’t sure how, if I could go back and save my recordings that didn’t get edited?! In all fairness I did just turn the experimental processing on yesterday to try so that might be what happened. We shall see.

@kinoCharlino said:

@toxlab said:
is the plex team actively working on the comskip ini file for various TV channels/providers to improve its performance?

We’re not at this time, but users could override the config if they want more control.

What I think we’re getting at is that we’d like to see the ability to specify a per-channel or per-recording comskip.ini. Just being able to customize the global configuration used for everything isn’t really sufficient. When I was doing this in post-processing, I was using per-channel configurations by mapping the program names we record to channels, and it really made a difference. So far though, Plex’ configuration has been very solid for me (US broadcast television, mostly news). We’ll see how it handles Svengoolie on Saturday night, though! Thanks so much for the inclusion of this feature.

@fecaleagle said:
What I think we’re getting at is that we’d like to see the ability to specify a per-channel or per-recording comskip.ini. Just being able to customize the global configuration used for everything isn’t really sufficient. When I was doing this in post-processing, I was using per-channel configurations by mapping the program names we record to channels, and it really made a difference. So far though, Plex’ configuration has been very solid for me (US broadcast television, mostly news). We’ll see how it handles Svengoolie on Saturday night, though! Thanks so much for the inclusion of this feature.

I’ve passed along that idea and posted the (early) response from engineering, along with responses for the rest of the suggestions raised thus far. Check it out here.

Per channel or show comskip.ini support
More complex than the feature was initially scoped out for, but interesting no less for advanced users. Engineering will need to evaluate how complex this is and if it should be scoped out for a future update. The intention was that advanced users would continue to have the option to post-process via script.

That is something that could be done down the road but when you start getting into complex things like this it might be better to do it in post processing where you can really fine tune it for your cable/OTA provider.

Just a thought.

@cayars said:
That is something that could be done down the road but when you start getting into complex things like this it might be better to do it in post processing where you can really fine tune it for your cable/OTA provider.

Yeah, I don’t see why that couldn’t be considered for the long-term, I just wouldn’t expect it to come ahead of some of the other requests.

The problem there is that post processing doesn’t know the channel unless more info is able to be passed to the scripts.

OffTopic, but mentioned in this thread also: I also keep one plex version at 1.6.1 to keep mkv recorded files from the dvr without having to do post processing. I really liked having that feature as a drop down. Usability of clients not being able to fast forward with TS was really an issue for me.

@ImCoKeMaN said:

The problem there is that post processing doesn’t know the channel unless more info is able to be passed to the scripts.

Adding additional arguments (channel + title) to the post-process script call was mentioned in the link provided above. I would be satisfied with this as an alternative to a per-channel comskip.ini.

@fecaleagle said:

Adding additional arguments (channel + title) to the post-process script call was mentioned in the link provided above. I would be satisfied with this as an alternative to a per-channel comskip.ini.

If you’re taking requests on the exposed post-processing arguments, the destination path would be a good one as well. Since post-processing will only pass the original file to the destination path, I’ve been using an inotifywait script to do my post-processing (I don’t prefer my MKVs to have the .ts extension). This allows the file to end up in the destination folder before processing occurs. It also gives me the ability to flag a file for later processing (something I don’t actually utilize but could). If post-processing could expose customizable arguments (a la qbitt******'s implementation), I could do everything I need in post-processing and avoid doing it the hard way.

Here’s a screen-grab of the sort of implementation I’m talking about (with the t-word redacted):

Edit: This could obviously be done without compromising existing post-processing scripts by treating scripts without recognized parameters as they’ve always been treated, i.e., appending the simple grab file path as an argument.

@damoncoursey said:

@kinoCharlino said:

@damoncoursey said:
I don’t have my own comskip.ini configuration file, but I would like to change just one thing. Is it possible to get a copy of the default .ini file that Plex is using and then modify that?

Comskip.ini is included in the PMS install. Here’s where you can find it in Linux: /usr/lib/plexmediaserver/Resources. Wherever the resources folder is, that’s where you’ll find it. I’ve attached the file for your convenience.

You might also want to check out: Tuning Comskip

Perfect thank you! I’ve found it and made my changes…will see how it goes with my next test recording :smile:

Forgot to come back and update this. It didn’t seem to work for me. I created the DVR folder, copied in the default comskip.ini and then set ā€œafter_logo=2ā€, hoping that it would keep 2 seconds of the program after the logo disappeared. No joy for me, it still cuts as soon as the logo disappears.

Can I confirm that I created the DVR folder in the correct location? I have moved the location of the ā€œlocal application dataā€ folder (setting in Server/General when Show Advanced is selected) to D:\Plex\AppData. Therefore I assumed that I should create the DVR folder in "D:\Plex\AppData\Plex Media Server\DVR". Keen to know if I have this in the correct location :smile: