Feature Enhancement request - crop video filter controls

we watch a lot of PBS and the local affiliate’s 2nd sub channel is SD. so you end up with a lot of HD-in-SD programs. outside of that, i agree that whatever is being presented in these formats are probably infomercials or something :slight_smile:

i guess my thinking is that this was a feature found in that “cat” product for the mac and we used it all the time, and i’m missing it now.

Been working on this most of the day. The version now on dropbox uses crf encoding and some extra x264 options. It is very efficient. Uses a fraction of the cpu I was using before. Using about 15% of my cpu (Intel® Pentium® CPU N3710 @ 1.60GHz). This is a crap cpu that comes with the synology.

I’m very satisfied with the progress. Still need to make wrapper work with other vendors.

The channels DVR auto updates often however. It undos my modifications. Will need to create another job to monitor if they pushed a new release and make necessary corrections.

For those members of the community who state a feature like this is only applicable to a subset of users please stop functionality is functionality not all channels are broadcasted HD that all stations have HD frequencies.
I have full premium packages 584 channels yet some stations just did not plan to spend for HD as an example Nicktoons on Comcast those cheap SOB's.

Referring to channels development team simply added stop being lazy you're already re encoding "autpcrop" the channels DVR service is sweet low-fat and dependable the price is steep so I expect so I expect you divvy up that workload and get it done

Why don’t you just use the wrapper supplied by @HolyRoses?

@tmm1 already mentioned he would be looking into it this fall. Calling people lazy is not very nice, and doesn’t normally excite people to help. He has to prioritize fixes and features.

1 Like

@djcastaldo
“Why don’t you just use the wrapper supplied by @HolyRoses?”

I’m using the dockerized channels, as part of a bigger whole purposely focusing on the data and not the underlying config effective keeping my setup wonderfully easy to support. I may have to implement the wrapper but hoped to see this brought to the main line. Thanks to the creator for the effort BTW. as for the numerous channel pass-through recommendations given to my customers, i wont be able to assist them.

@ImNotSerious
@tmm1 already mentioned he would be looking into it this fall. Calling people lazy is not very nice, and doesn’t normally excite people to help. He has to prioritize fixes and features”

IMO i call it as I see it and MO is a vastly creditable.

I should not justify calling an entity lazy, but if it should have been address then tell my a better reason why it has not happened.

This product does what?

  • warehouse guide info
  • record / save a stream from tuner
  • can be later played back

Those functions should always be at the top of the offering / capability matrix

if “can be later played back” but with inherit visibility defect happens it should be addressed. losing 1/3 picture is a defect.

upon examining the reason why, and seeking out a resolution.

cropdetect

possibly at 33% 66% to avoid inaccurate cropping.

I retract and apologize for calling Channels Lazy . I should have said, Channels you charge $20 /app + 8$ / mo why wouldn’t you add more resources to address this.

your

  • warehouse guide info – is working stable
  • record / save a stream from tuner-- is working stable
  • can be later played back – possibly 70% working

A fix for this is in the works. It’s much more technically challenging than you might guess at first glance.

much appreciated, and for such a wonderfully developed app i wouldn’t call the solution a fix. / i.e. was never broken just overlooked or not exposed.
To be 100% clear channels is tight / small and 100% a must have app to complement a HDhomerun(s).

post processing for file size (encoding), cropping would be terrific with these sometimes watered down broadcast. You’re already keeping me from using the plexdvr attributed to your great interface and better live TV experience.

Your Nick Toons case is an interesting one, because it’s not even a true letterbox. They’ve added the logo into the letterbox area.

How does your regular cable box or TV deal with this case? I assume it displays the same way as Channels, until you click the zoom button and then part of the logo is cut off?

I’d really like to understand how this works with your regular TV/cable box.

Also if you can send me a 1 minute recording from the nick toons channel to [email protected] that would be helpful.

I did some tests on my SD cable channels, and the results are pretty mixed.

Some channels have simple letterboxing of 16x9 content:

Some letterbox, but put their logo in the letterbox area:

Sometimes a postage stamp is built-in, because they took original 4x3 content and pillarboxed it for the HD channel, then take that and letterbox it again for the SD version:

Some channels put their logo in the letterbox, but overlap it partially with the content:

Worse, they'll even show other content overlapped along with the logo:

It's almost impossible to deal with all these cases automatically. Even as a human I'm not sure what the proper crop for each of these situations should be.

The problem is that the cable company is broadcasting video with black bars added. They expect that the video will be displayed with the bars, and that's why they've started putting other stuff in that area.

Interestingly enough, the SCTE (society of cable tech engineers) even came up with a broadcast standard that transmits BAR DATA, specifying exactly which areas of the picture are black bars. Unfortunately, no one actually uses it.

I’ve never understood why this is such an issue in the US. Surely not that many people still have 4:3 TVs or don’t have a STB that converts a 16:9 picture properly. In the UK, 16:9 is the standard on SD channels, with automatic switching to 4:3 for older programmes…’fake’ letterbox or pillarbox bars are never added to the video itself.

Hi @tmm1

Glad to see you looking into. I haven’t used this wrapper in quite a while as it was always a hack solution. Currently I am using plex with their post processor option. I am going to link you my plex post processing script as it may have solutions to many of the technical challenges you are facing.

You are right however it is not easy because many channels do things differently. I approach it based on shows and or incoming formats that I know need cropping by default. This is why I said there would have to be many options and override capabilities per recording.

The ffmpeg filters are very useful because you can do a lot of transformations without using your own mathematics to calculate things. You can see many examples in the code.

Thanks for sharing. I guess post-processing the video file to fix it is the best solution, since then everything else just works as expected. Unfortunately the amount of work required to special case channels and even specific shows is more than I would expect most users are interested in investing.

My plan going forward for Channels is to (1) fix the generated preview thumbnails using an approach like this, and (2) add a Zoom feature to the iOS/tvOS player so you can crop letterbox during playback easily.

This won’t help with web/roku playback, but that’s a whole other project especially since we use hardware transcoding which makes it much more complicated to do both cropdetection and to crop.

zoom would probably satisfy most users, seen that in other competitor apps and works fine. You should remember zoom settings per channel so people dont have to keep pushing that zoom button.

I gave you a fix for screenshot here:

Yea we will definitely remember zoom settings per channel.

Your screenshot fix is based on resolution/sar only which doesn’t work for some of my channels which actually broadcast 4:3 natively without any letterbox included. This we need to use cropdetect, but that currently requires multiple invocations. The patch I wrote for ffmpeg will allow cropdetect+crop in a single go.

it doesn’t do any cropping. It just creates a correctly scaled 640 by X image for any incoming source. Your native 4:3 image will still create a correct screenshot. I never modified my wrapper to look at incoming source and crop the screenshot to correct size. If it was scaled properly I was happy. Skewed/streched images bother me.

1 Like

Ah you’re right. That’s an easy fix then.

1 Like

I know this is reviving an older thread, but was this ever implemented? The only options I see with regards to zooming is a stretch to fit feature, which does not help with the situation in regards to SD cable content. I’m in the same boat as others in that not all channels in my lineup contain HD equivalents (BBC in particular).

Reviving this again, has anyone looked into this feature at all? Im guessing no since there hasn't been activity for many years.