INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: [FEATURE REQUEST]Tuner Warm up period  (Read 1546 times)

muzicman0

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1239
[FEATURE REQUEST]Tuner Warm up period
« on: June 29, 2020, 10:53:42 pm »

My tuners (HDHomeRuns) spit out some corrupted packets when recordings start.  I have read that other tuners can be significantly worse than mine.  It's not a huge problem until I try to transcode the .ts file.  The AV sync will drift (significantly).  I find that if I start the encode 10 seconds in, then 100% of the time, the AV sync is fine (but doing this has other issues with closed caption extraction).

It would be awesome if we could configure a 'Tuner Warm up Time' where it tunes the channel x number of seconds prior to the scheduled recording start.  Then start writing to disk at the scheduled start time.  Of course, it should default to no warm up time.
Logged

astromo

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2251
Re: [FEATURE REQUEST]Tuner Warm up period
« Reply #1 on: June 30, 2020, 09:04:43 am »

I've probably missed something.

MC defaults by starting recording 5 minutes prior to the EPG scheduled start time. That works for me. I've never noticed an AV sync issue and no-one else in the house complains. Can't say the same for subtitles but MC's shift function deals with that pretty well, so no issues from me.
Logged
MC33, Win10 x64, HD-Plex H5 Gen2 Case, HD-Plex 400W Hi-Fi DC-ATX / AC-DC PSU, Gigabyte Z370 ULTRA Gaming 2.0 MoBo, Intel Core i7 8700 CPU, 4x8GB GSkill DDR4 RAM, Schiit Modi Multibit DAC, Freya Pre, Nelson Pass Aleph J DIY Clone, Ascension Timberwolf 8893BSRTL Speakers, BJC 5T00UP cables, DVB-T Tuner HDHR5-4DT

muzicman0

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1239
Re: [FEATURE REQUEST]Tuner Warm up period
« Reply #2 on: June 30, 2020, 09:21:07 am »

What I am asking for is different than padding.  I already have 1 minute start and end padding (starting 1 minute prior, and ending 1 minute after scheduled program times).

What I am asking for is for the tuner to start streaming data say 30 seconds before the padded time.  The stream would in essence go nowhere, and would not be written to disk.  It would also only happen prior to the padding time, not after.

I don't have issues if I am simply watching and deleting tv shows.  The problem happens when I compress (for archiving) the recorded .ts file.  If I compress the show to h.264 or h.265 (or really whatever), the AV sync in the compressed file is significantly off by the end of the show.

The resulting file would end up the same length as it is now.

I have seen reports of some lower end tuners taking minutes to start streaming clean data.  Sometimes it is minor like mine, other times, the resulting video is really bad, but ultimately is cleans up after a certain amount of time.

By the way, I am not asking for anything new or innovative, this feature has been implemented in at least one other TV recording software (probably more) for the very reasons I mention above.
Logged

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: [FEATURE REQUEST]Tuner Warm up period
« Reply #3 on: June 30, 2020, 06:29:06 pm »

Are these HDHomerun Primes, or some other tuners?

Regardless I guess, if the video is taking a while to stabilise, then just increase the pre-padding to two or five minutes, and then transcode from the program start time. That is part of what the pre-padding is for, after all. See if that fixes the problem.

The problem is, as you say, different brands and models of tuners take different times to stabilise, and so if what you are requesting was implemented it would need to be set according to the tuner behaviour, which means it would need to be user-configurable. So MC would have a tuner warm-up time, then a pre-padding time, both of which must be configurable. That would need to be taken into account with tuner clashes, scheduling, etc. That is a lot of complexity in an already complex system.

Just add a bit more pre-padding, and trim it off during transcoding.
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

muzicman0

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1239
Re: [FEATURE REQUEST]Tuner Warm up period
« Reply #4 on: June 30, 2020, 06:47:18 pm »

yes, as I mentioned, they are HDHomeruns.  and yes, I know there are work arounds, however, the problem with 'just start transcoding 10 seconds in' (which by the way, is what I do now), is that I need to rip the closed captions (hard of hearing) using CCExtractor, and then I have to push  the closed captions by 10 seconds ahead, but they are never quite right, because the 10 seconds in on the transcode is never exactly 10 seconds. 

I have 8 HDHomeruns (4 OTA, and 4 primes), and every last one of them do this.  I may be alone in wanting to archive, but I for sure am not alone in this issue since I see it on other forums.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72444
  • Where did I put my teeth?
Re: [FEATURE REQUEST]Tuner Warm up period
« Reply #5 on: June 30, 2020, 07:01:38 pm »

I don't think I've ever seen this problem.  Is it possible that the conversion you do later is causing it?
Logged

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: [FEATURE REQUEST]Tuner Warm up period
« Reply #6 on: June 30, 2020, 08:18:39 pm »

If the Closed Captions work correctly when you playback the original recording in MC, then I would focus on the transcoding and CCExtractor.

I would definitely increase the pre-padding to get a more stable signal for the actual program. Give the tuner more time.

You haven't said what you use for the transcode, or if you extract CC from the TS file before transcoding, or from the transcoded file after transcoding.

If using MC to transcode, which has issues in terms of the audio produced always being stereo, then I would set the Playback Range for the file before transcoding, so that it only includes the program, and would most likely get the audio and Closed Caption synchronisation correct. Besides, once you have the Closed Captions in SRT Subtitle form, MC can adjust there timing in 100 millisecond steps. So unless the video is stretched or compressed in the timeline by the transcoding function, you should be able to get them aligned correctly and they should stay aligned for the duration of the program.


I'm sorry but I think you have requested a solution that doesn't address the problem. To test that theory, try this simple process.

Pick a program that is going to be recorded, and which will have CC and you will want to archive.
Start playback of the TV channel live five minutes before MC is due to start recording, allowing for the pre-padding.
Process the resulting recording exactly as you do now.

Did that fix the issue? It should have, if your requested solution was going to work, because all you did was manually warm up the tuner and get it stabilised on the channel before starting the recording, just as per your request.

Of course, I'm sure the issue happens to greater and lesser degrees with different programs, so repeat the above test a few times to be sure that it does, in fact, eliminate the problem. One test that works is not the basis of a reasonable conclusion.
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

muzicman0

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1239
Re: [FEATURE REQUEST]Tuner Warm up period
« Reply #7 on: July 01, 2020, 01:16:19 pm »

I don't think I've ever seen this problem.  Is it possible that the conversion you do later is causing it?
Yes, the conversion is what causes it sorta...it's a chicken and the egg scenario.  The AV sync issue is caused when it is transcoded, but it happens because the original file has some corrupted frames at the beginning.  to avoid the issue, simply start the transcoding 10 seconds in (with ffmpeg, "-ss 00:00:10").  Every transcoder is different, and I have used more than 1 to try this. 

I ended up moving on, and while I still use MC for a few things, I moved my TV recording engine back to a linux based solution.

Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72444
  • Where did I put my teeth?
Re: [FEATURE REQUEST]Tuner Warm up period
« Reply #8 on: August 28, 2020, 12:45:01 pm »

If this is easy to do, we'll do it.
Logged

muzicman0

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1239
Re: [FEATURE REQUEST]Tuner Warm up period
« Reply #9 on: August 28, 2020, 04:18:24 pm »

I'll keep an eye out.
Logged
Pages: [1]   Go Up