SageTV Community  

Go Back   SageTV Community > Hardware Support > Hardware Support

Notices

Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here.

Reply
 
Thread Tools Search this Thread Display Modes
  #601  
Old 03-19-2016, 08:04 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
0.4.36-RC1 Release



This is a cleanup of a few things I noticed could be improved a little along with a few fixes for things no one so far has reported, but I discovered in testing.
  • Fixed opendct.properties was being version backed up every single time the program was started. It now only does a backup on version and/or config upgrade like it was supposed to do.
  • Improved audio stream selection for FFmpeg transcoder. Bitrate when available is now a tie-breaker which helps with channels like PBS that have three two channel audio streams.
  • Fixed the COPY lineup update method not saving newly added channels.
  • Fixed a potentially very long hang when tuning InfiniTV devices that have rebooted.
  • Detection speed increase for FFmpeg transcoder.
  • Improved handling of FFmpeg transcoder direct file writing failures.
  • Improved re-tuning efficiency for HDHomeRun devices. Now instead of a thread for each device, there is one thread for all of them that creates a new re-tuning thread only if the device needs to be re-tuned. This feature will also benefit future capture devices.
__________________
SageTV v9 Server: ASRock Z97 Extreme4, Intel i7-4790K @ 4.4Ghz, 32GB RAM, 6x 3TB 7200rpm HD, 2x 5TB 7200rpm HD, 2x 6TB 7200rpm HD, 4x 256GB SSD, 4x 500GB SSD, unRAID Pro 6.7.2 (Dual Parity + SSD Cache).
Capture: 1x Ceton InfiniTV 4 (ClearQAM), 2x Ceton InfiniTV 6, 1x BM1000-HDMI, 1x BM3500-HDMI.

Clients: 1x HD300 (Living Room), 1x HD200 (Master Bedroom).
Software: OpenDCT :: WMC Live TV Tuner :: Schedules Direct EPG
Reply With Quote
  #602  
Old 03-21-2016, 07:31 AM
Greg2dot0's Avatar
Greg2dot0 Greg2dot0 is offline
Sage Advanced User
 
Join Date: Dec 2008
Posts: 82
Tying to figure out what's going wrong

I've been trying to get OpenDCT up and running for a while and have run into these consistent errors. I've installed this both on my existing Windows 10 install and a brandy-new clean Unbuntu 14.4 Server build. I've tried to eliminate as many environmental variables as I could but even after replacing all of the cables and installing 0.4.36 RC I get the same errors. On my windows box, I am running PrimeNetEncoder and do notice some dropouts occasionally which I am guessing is the cause (although, my signal strength and quality show as good (Signal Strength 100% (11.4 dBmV), Signal Quality 100% (37.2 dB) which also is reflected in the logs (attached).

I occasionally get these messages and I'm not sure what they mean
07:54:28.827 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] DEBUG ffmpeg - null
07:54:28.827 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] DEBUG ffmpeg - null
07:54:28.975 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - null
07:54:28.985 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - null
07:54:29.024 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - null
07:54:29.035 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - null
07:54:29.035 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] DEBUG ffmpeg - null
07:54:29.035 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] INFO ffmpeg - null
07:54:29.036 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] DEBUG ffmpeg - null

and then I will get a slew of these messages which seem to mess up the recording:

08:04:12.880 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29495221
08:04:12.884 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29496723
08:04:12.889 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29498224
08:04:12.907 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29467144
08:04:12.911 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29499726
08:04:12.915 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29501227

I also notice some unhandled exceptions in the log (seems to be around UPNP discovery. This IP address is a NAS Box)

06:42:04.098 [HDHomeRunDiscoveryReceive-36] ERROR HDHomeRunDiscoverer - Unable to communicate with HDHomeRun device 'HDHomeRunDevice{ipAddress=/192.168.1.201, deviceId=-1}' => java.net.ConnectException: Connection refused
at sun.nio.ch.Net.connect0(Native Method)
at sun.nio.ch.Net.connect(Net.java:454)
at sun.nio.ch.Net.connect(Net.java:446)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
at java.nio.channels.SocketChannel.open(SocketChannel.java:189)
at opendct.tuning.hdhomerun.HDHomeRunControl.connectSocket(HDHomeRunControl.java:243)
at opendct.tuning.hdhomerun.HDHomeRunControl.setVariable(HDHomeRunControl.java:112)
at opendct.tuning.hdhomerun.HDHomeRunControl.getVariable(HDHomeRunControl.java:66)
at opendct.tuning.hdhomerun.HDHomeRunDevice.getSysHwModel(HDHomeRunDevice.java:267)
at opendct.tuning.hdhomerun.HDHomeRunDevice.getUniqueDeviceName(HDHomeRunDevice.java:353)
at opendct.tuning.discovery.discoverers.HDHomeRunDiscoverer.addCaptureDevice(HDHomeRunDiscoverer.java:440)
at opendct.tuning.hdhomerun.HDHomeRunDiscovery$ReceiveThread.run(HDHomeRunDiscovery.java:385)
at java.lang.Thread.run(Thread.java:745)

Any help in identifying the issues or pointing me in a next step for troubleshooting is greatly appreciated. I'd love to be able to take advantage of OpenDCT's features. Thanks!
Attached Files
File Type: zip opendct.zip (176.5 KB, 96 views)
__________________
Production SageTV Server: ASUS P8P67-Pro, 16gb RAM, Crucial m4 256GB SSD, Unbunto 16.4.04 LTS (Server x64), WDC Red 4TB
Capture: 1x HDHR Prime, 1x HDHomeRun (ClearQAM)
Clients: 1x HD300, 2x HD200, 2x Placeshifters
Reply With Quote
  #603  
Old 03-21-2016, 11:00 AM
jgsouthard jgsouthard is offline
Sage Advanced User
 
Join Date: Jul 2004
Posts: 143
Should pooling be the default?

Over the last several betas, the only change I have made to default properties is to turn on pooling and forced unlocking by changing the following properties:

Default: pool.enabled=false
Changed to: pool.enabled=true

Default: sagetv.device.<device_id>.always_force_external_unlock=false
Changed to: sagetv.device.<device_id>.always_force_external_unlock=true

Although I only have one SageTV server accessing my six tuners (two HDHomeRun Primes), I occasionally use HDHomeRun View to view live TV from one of my PC's and I don't want that to ever prevent a recording from being able to start. That happened in the past with other network encoders.

I haven't seen any negative consequences from using pooling, nor can I think of any.

EnterNoEscape, everything you've done with OpenDCT is well thought out. So I'm just curious why pooling isn't enabled by default? Are there downsides to using it that I should be aware of, and/or other reasons it is turned off by default?
__________________

Windows 10 Home 64-bit, i5-2500K, 8GB RAM, 2TB and 4TB SATA HDD's
SageTV v9.1.2.662, SageTV7.xml STV, Java v1.8.0_121
Server operating headless with 3 HD300 extenders as clients
Two HDHomeRun Primes (6 tuners) with 20170512beta1 firmware
Comcast cable TV, two cablecards in HDHRP's
OpenDCT 0.5.28 network encoder
Reply With Quote
  #604  
Old 03-21-2016, 11:21 AM
nyplayer nyplayer is offline
SageTVaholic
 
Join Date: Sep 2005
Posts: 4,799
Quote:
Originally Posted by jgsouthard View Post
Over the last several betas, the only change I have made to default properties is to turn on pooling and forced unlocking by changing the following properties:

Default: pool.enabled=false
Changed to: pool.enabled=true

Default: sagetv.device.<device_id>.always_force_external_unlock=false
Changed to: sagetv.device.<device_id>.always_force_external_unlock=true

Although I only have one SageTV server accessing my six tuners (two HDHomeRun Primes), I occasionally use HDHomeRun View to view live TV from one of my PC's and I don't want that to ever prevent a recording from being able to start. That happened in the past with other network encoders.

I haven't seen any negative consequences from using pooling, nor can I think of any.

EnterNoEscape, everything you've done with OpenDCT is well thought out. So I'm just curious why pooling isn't enabled by default? Are there downsides to using it that I should be aware of, and/or other reasons it is turned off by default?
That is exactly how I run it I also disable UPNP not needed when using HdHomerun devices. That way it does not scan my PLEX and nas devices.

upnp.enabled=false
__________________
Windows 10 I3 Dual Core 3.0 Server, SageTV9... OpenDCT with 2 HDHRPrimes and 4 HDHRconnects for a total of 14 Tuners.
Reply With Quote
  #605  
Old 03-21-2016, 12:21 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by Greg2dot0 View Post
I've been trying to get OpenDCT up and running for a while and have run into these consistent errors. I've installed this both on my existing Windows 10 install and a brandy-new clean Unbuntu 14.4 Server build. I've tried to eliminate as many environmental variables as I could but even after replacing all of the cables and installing 0.4.36 RC I get the same errors. On my windows box, I am running PrimeNetEncoder and do notice some dropouts occasionally which I am guessing is the cause (although, my signal strength and quality show as good (Signal Strength 100% (11.4 dBmV), Signal Quality 100% (37.2 dB) which also is reflected in the logs (attached).

I occasionally get these messages and I'm not sure what they mean
07:54:28.827 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] DEBUG ffmpeg - null
07:54:28.827 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] DEBUG ffmpeg - null
07:54:28.975 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - null
07:54:28.985 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - null
07:54:29.024 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - null
07:54:29.035 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - null
07:54:29.035 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] DEBUG ffmpeg - null
07:54:29.035 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] INFO ffmpeg - null
07:54:29.036 [FFmpegSageTVConsumerImpl-846CT-HDHomeRun Prime Tuner 13142E5A-2] DEBUG ffmpeg - null

and then I will get a slew of these messages which seem to mess up the recording:

08:04:12.880 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29495221
08:04:12.884 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29496723
08:04:12.889 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29498224
08:04:12.907 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29467144
08:04:12.911 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29499726
08:04:12.915 [FFmpegSageTVConsumerImpl-859CT-HDHomeRun Prime Tuner 13142E5A-0] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 29501227

I also notice some unhandled exceptions in the log (seems to be around UPNP discovery. This IP address is a NAS Box)

06:42:04.098 [HDHomeRunDiscoveryReceive-36] ERROR HDHomeRunDiscoverer - Unable to communicate with HDHomeRun device 'HDHomeRunDevice{ipAddress=/192.168.1.201, deviceId=-1}' => java.net.ConnectException: Connection refused
at sun.nio.ch.Net.connect0(Native Method)
at sun.nio.ch.Net.connect(Net.java:454)
at sun.nio.ch.Net.connect(Net.java:446)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
at java.nio.channels.SocketChannel.open(SocketChannel.java:189)
at opendct.tuning.hdhomerun.HDHomeRunControl.connectSocket(HDHomeRunControl.java:243)
at opendct.tuning.hdhomerun.HDHomeRunControl.setVariable(HDHomeRunControl.java:112)
at opendct.tuning.hdhomerun.HDHomeRunControl.getVariable(HDHomeRunControl.java:66)
at opendct.tuning.hdhomerun.HDHomeRunDevice.getSysHwModel(HDHomeRunDevice.java:267)
at opendct.tuning.hdhomerun.HDHomeRunDevice.getUniqueDeviceName(HDHomeRunDevice.java:353)
at opendct.tuning.discovery.discoverers.HDHomeRunDiscoverer.addCaptureDevice(HDHomeRunDiscoverer.java:440)
at opendct.tuning.hdhomerun.HDHomeRunDiscovery$ReceiveThread.run(HDHomeRunDiscovery.java:385)
at java.lang.Thread.run(Thread.java:745)

Any help in identifying the issues or pointing me in a next step for troubleshooting is greatly appreciated. I'd love to be able to take advantage of OpenDCT's features. Thanks!
The null FFmpeg logging is my fault. It's not supposed to log in Linux and when I improved the logging filter, I apparently didn't do as well of a job as I thought at keeping those entries from appearing. The reason logging was turned off in Linux is because on previous FFmpeg builds, it would crash the JVM. The text isn't being parsed which is what caused the problem and that's why you get null. This crash appears to have been fixed in the FFmpeg version that we are currently using. I'm going to have it turned on by default in the next RC. To enable it right now, edit opendct.properties and change consumer.ffmpeg.linux_logging to true. You will then see meaningful messages.

I noticed something odd after looking at a long list of dts errors in the log. Your decode time stamps circle back very unexpectedly. I noticed in one instance, they went from 2861631 to 250673 which really should never be happening. dts wrap around should be a lot closer to 8589934592 (33 bits). I may need a raw sample of this "rogue" content if the troubleshooting below doesn't help.

The last stack trace you posted happens because your NAS for some reason is replying to the UDP broadcast to port 65001 that's used to discover HDHomeRun devices. I can tell based on your opendct.properties file that the problem stops there since as soon as it realizes it's not actually an HDHomeRun, it stops trying to load it. The only thing that's concerning is that the broadcast to discover HDHomeRun devices is a rather specifically formatted packet and your NAS is responding to it.

Troubleshooting:
1) Before making any changes, try recording with the NAS turned off if you haven't already. I realize that means you will probably need to change your recording path temporarily.
2) Stop the OpenDCT service.
3) Open opendct.properties
4) Change consumer.ffmpeg.linux_logging to true
6) Start the OpenDCT service and test. At least you'll know what FFmpeg is complaining about.

7) If it's still not working.
8) Stop the OpenDCT service.
9) Open opendct.properties
10) Change all of the entries for sagetv.device.<unique_id>.consumer to opendct.consumer.FFmpegTransSageTVConsumerImpl
11) Start the OpenDCT service and test.

12) If it's still not working.
13) Stop the OpenDCT service.
14) Open opendct.properties
15) Change all of the entries for sagetv.device.<unique_id>.consumer to opendct.consumer.RawSageTVConsumerImpl
16) Start the OpenDCT service and test. If it still isn't working, try to create a short (< 5 mins) using this consumer so I can take a look at it.
__________________
SageTV v9 Server: ASRock Z97 Extreme4, Intel i7-4790K @ 4.4Ghz, 32GB RAM, 6x 3TB 7200rpm HD, 2x 5TB 7200rpm HD, 2x 6TB 7200rpm HD, 4x 256GB SSD, 4x 500GB SSD, unRAID Pro 6.7.2 (Dual Parity + SSD Cache).
Capture: 1x Ceton InfiniTV 4 (ClearQAM), 2x Ceton InfiniTV 6, 1x BM1000-HDMI, 1x BM3500-HDMI.

Clients: 1x HD300 (Living Room), 1x HD200 (Master Bedroom).
Software: OpenDCT :: WMC Live TV Tuner :: Schedules Direct EPG
Reply With Quote
  #606  
Old 03-21-2016, 12:38 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by jgsouthard View Post
EnterNoEscape, everything you've done with OpenDCT is well thought out. So I'm just curious why pooling isn't enabled by default? Are there downsides to using it that I should be aware of, and/or other reasons it is turned off by default?
There aren't any downsides that I know of. I use it in production at home and don't actually need it. I just want to be using everything anyone might be using. In fact I've hardly needed to touch that code since the very first 0.4 release.

The reason it's not enable by default is because the behavior is not what most people expect when using a network encoder. Also it will group all discovered devices in a particular pool based on category (qam, atsc_xxxxxxxx, dct) which might cause you to use a capture device that you did not intend to even use in SageTV. The pools can be changed in opendct.properties, but I'd rather not surprise anyone by enabling this by default. ATSC is made unique because unlike QAM and DCT, there's a higher possibility that they might not all tune the same channels.
__________________
SageTV v9 Server: ASRock Z97 Extreme4, Intel i7-4790K @ 4.4Ghz, 32GB RAM, 6x 3TB 7200rpm HD, 2x 5TB 7200rpm HD, 2x 6TB 7200rpm HD, 4x 256GB SSD, 4x 500GB SSD, unRAID Pro 6.7.2 (Dual Parity + SSD Cache).
Capture: 1x Ceton InfiniTV 4 (ClearQAM), 2x Ceton InfiniTV 6, 1x BM1000-HDMI, 1x BM3500-HDMI.

Clients: 1x HD300 (Living Room), 1x HD200 (Master Bedroom).
Software: OpenDCT :: WMC Live TV Tuner :: Schedules Direct EPG
Reply With Quote
  #607  
Old 03-21-2016, 12:53 PM
waylo waylo is offline
Sage Advanced User
 
Join Date: Feb 2006
Posts: 238
Quote:
Originally Posted by EnterNoEscape View Post


This is a cleanup of a few things I noticed could be improved a little along with a few fixes for things no one so far has reported, but I discovered in testing.
  • Fixed opendct.properties was being version backed up every single time the program was started. It now only does a backup on version and/or config upgrade like it was supposed to do.
  • Improved audio stream selection for FFmpeg transcoder. Bitrate when available is now a tie-breaker which helps with channels like PBS that have three two channel audio streams.
  • Fixed the COPY lineup update method not saving newly added channels.
  • Fixed a potentially very long hang when tuning InfiniTV devices that have rebooted.
  • Detection speed increase for FFmpeg transcoder.
  • Improved handling of FFmpeg transcoder direct file writing failures.
  • Improved re-tuning efficiency for HDHomeRun devices. Now instead of a thread for each device, there is one thread for all of them that creates a new re-tuning thread only if the device needs to be re-tuned. This feature will also benefit future capture devices.
Thanks again for all your incredible work on this project.

This is my first time upgrading (from .35 to .36), so I was wondering if I did this correctly.

I stopped the OpenDCT service and ran the new install package.

I then executed the 'run as console' shortcut. I don't know if this was needed or not. I then exited via ctrl-c.

I then restarted the service.

Sage was running the whole time. But it seems to be tuning channels just fine.
__________________

Server: SageTV 9.2.6x64 on Win10 x64 Home, i7-2600, 8gb RAM, OpenDCT, Java 1.8, 20TB storage
Display: EVGA GT 1030 fanless to Sony LED TV via DVI-HDMI
Capture Devices: HDHR Prime for Comcast, HDHR Dual for OTA (retired)
Clients: Nvidia Shield Android miniclient

Last edited by waylo; 03-21-2016 at 03:18 PM.
Reply With Quote
  #608  
Old 03-21-2016, 04:04 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by waylo View Post
Thanks again for all your incredible work on this project.

This is my first time upgrading (from .35 to .36), so I was wondering if I did this correctly.

I stopped the OpenDCT service and ran the new install package.

I then executed the 'run as console' shortcut. I don't know if this was needed or not. I then exited via ctrl-c.

I then restarted the service.

Sage was running the whole time. But it seems to be tuning channels just fine.
The console thing is only recommended for the first time; after that it usually has no benefit. You can get the equivalent by just starting the service, then stopping it after waiting about 30 seconds. Once the web interface is in place, I plan on getting rid of that shortcut. I think it has confused more than it has helped.

I upgrade that way too. I just make sure nothing is currently recording first. Most of the time SageTV doesn't even appear to notice. If it does, I can usually get everything back to working by just visiting a tuner in video sources instead of restarting the service.
__________________
SageTV v9 Server: ASRock Z97 Extreme4, Intel i7-4790K @ 4.4Ghz, 32GB RAM, 6x 3TB 7200rpm HD, 2x 5TB 7200rpm HD, 2x 6TB 7200rpm HD, 4x 256GB SSD, 4x 500GB SSD, unRAID Pro 6.7.2 (Dual Parity + SSD Cache).
Capture: 1x Ceton InfiniTV 4 (ClearQAM), 2x Ceton InfiniTV 6, 1x BM1000-HDMI, 1x BM3500-HDMI.

Clients: 1x HD300 (Living Room), 1x HD200 (Master Bedroom).
Software: OpenDCT :: WMC Live TV Tuner :: Schedules Direct EPG
Reply With Quote
  #609  
Old 03-21-2016, 04:41 PM
Greg2dot0's Avatar
Greg2dot0 Greg2dot0 is offline
Sage Advanced User
 
Join Date: Dec 2008
Posts: 82
Quote:
Originally Posted by EnterNoEscape View Post
The last stack trace you posted happens because your NAS for some reason is replying to the UDP broadcast to port 65001 that's used to discover HDHomeRun devices. I can tell based on your opendct.properties file that the problem stops there since as soon as it realizes it's not actually an HDHomeRun, it stops trying to load it. The only thing that's concerning is that the broadcast to discover HDHomeRun devices is a rather specifically formatted packet and your NAS is responding to it.
Thanks for the detailed response. I'll be testing tomorrow early am due to prime time schedule. One thought was that I had the SiliconDust DVR beta on my Qnap NAS. Wonder if that has something to do with it. Good thing is that it needs to be loaded manually after a reboot, so if I pass the first test, I can reload it to see if the problem starts again. I've turned it off now (I actually am totally local on the Linux box I built, so no recording path issues).
__________________
Production SageTV Server: ASUS P8P67-Pro, 16gb RAM, Crucial m4 256GB SSD, Unbunto 16.4.04 LTS (Server x64), WDC Red 4TB
Capture: 1x HDHR Prime, 1x HDHomeRun (ClearQAM)
Clients: 1x HD300, 2x HD200, 2x Placeshifters

Last edited by Greg2dot0; 03-21-2016 at 04:44 PM.
Reply With Quote
  #610  
Old 03-21-2016, 08:22 PM
troll5501 troll5501 is offline
Sage Advanced User
 
Join Date: Jun 2006
Posts: 136
I upgraded from 0.4.27 which was working very well, to 0.4.36...and now I'm getting PES packet size mismatch and Continuity check failed errors very frequently (last night it was happening every 5 minutes or so). It's enough to cause a brief break in the stream which appears on screen as pixelation and an audio drop but it only affects 1-2 seconds of the recording each time. Here's an example from tonight:

Code:
21:01:05.063 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] INFO  ffmpeg - Last message repeated 27 times.
21:01:05.071 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] DEBUG ffmpeg - [mpegts @ 0x7f4d1016d080] Continuity check failed for pid 1553072288 expected 0 got 0
21:01:05.075 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] INFO  ffmpeg - Last message repeated 7 times.
21:01:05.075 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] WARN  ffmpeg - [mpegts @ 0x7f4d1016d080] PES packet size mismatch
21:01:05.076 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] DEBUG ffmpeg - [mpegts @ 0x7f4d1016d080] Continuity check failed for pid 1553072288 expected 0 got 0
21:01:05.079 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] INFO  ffmpeg - Last message repeated 1 time.
21:01:05.079 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] WARN  ffmpeg - [mpegts @ 0x7f4d1016d080] PES packet size mismatch
21:01:05.101 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] DEBUG ffmpeg - [mpegts @ 0x7f4d1016d080] Continuity check failed for pid 1553072288 expected 0 got 0
21:01:05.111 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] INFO  ffmpeg - Last message repeated 9 times.
21:01:05.111 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] WARN  ffmpeg - [mpegts @ 0x7f4d1016d080] PES packet size mismatch
21:08:41.236 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] INFO  ffmpeg - Last message repeated 1 time.
21:08:41.236 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] DEBUG ffmpeg - [mpegts @ 0x7f4d1016d080] Continuity check failed for pid 1553072288 expected 0 got 0
21:08:41.239 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] INFO  ffmpeg - Last message repeated 9 times.
21:08:41.239 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] WARN  ffmpeg - [mpegts @ 0x7f4d1016d080] PES packet size mismatch
21:16:05.454 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] INFO  ffmpeg - Last message repeated 1 time.
21:16:05.480 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] DEBUG ffmpeg - [mpegts @ 0x7f4d1016d080] Continuity check failed for pid 1553072288 expected 0 got 0
21:16:05.480 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] INFO  ffmpeg - Last message repeated 1 time.
21:16:05.480 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] WARN  ffmpeg - [mpegts @ 0x7f4d1016d080] PES packet size mismatch
21:20:49.469 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] INFO  ffmpeg - Last message repeated 1 time.
21:20:49.469 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] DEBUG ffmpeg - [mpegts @ 0x7f4d1016d080] Continuity check failed for pid 1553072288 expected 0 got 0
21:20:49.472 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] WARN  ffmpeg - [mpegts @ 0x7f4d1016d080] PES packet size mismatch
21:41:08.868 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] DEBUG ffmpeg - [mpegts @ 0x7f4d1016d080] Continuity check failed for pid 1553072288 expected 0 got 0
21:41:08.873 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] INFO  ffmpeg - Last message repeated 7 times.
21:41:08.873 [FFmpegSageTVConsumerImpl-8345:DCT-HDHomeRun Prime Tuner 13191941-2] WARN  ffmpeg - [mpegts @ 0x7f4d1016d080] PES packet size mismatch
I'm guessing this may be related to the switch from UDP to TCP/HTTP for the producer, but I know there were many other changes between 27 and 36.

Any suggestions on where I should be looking? Is this potentially another buffering issue somewhere? I'm not seeing any dropped packets in VMware, and recent Linux kernels seem to have autotuning for TCP so I don't know if any tweaking is necessary in the network stack (unlike UDP which required the increased net.core.rmem_max).
__________________
Server: HP DL380 G6, VMware ESXi 5.0 with HW passthrough for USB and Firewire, 4 x HD-PVR, ZFS storage
SageTV: Production: 7.1.9+Java 1.6.0_32 on XP, Test: 9.0.4.291+Java 1.8.0_72 on Linux 64-bit
Clients: 2 x Sage HD200 Extender, 1 x Sage HD100 Extender
Sources: 4 x Motorola DCH-3200 (firewire channel changing), HD Homerun Prime, OpenDCT 0.5.7
Reply With Quote
  #611  
Old 03-21-2016, 09:50 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
To verify that it's the http tuning at fault, in opendct.properties, change hdhr.allow_http_tuning to false.

Unfortunately if it is the http tuning causing the problem for you, there isn't much you can do other than not use it. I was able to trip it up a little today by transferring a large file, but nowhere near as bad as it can get with UDP. So while the TCP/IP connection might not be disconnected, it would appear that the HDHomeRun will drop TS packets silently if you're not keeping up.

You could also try just re-muxing with the new transcoding consumer. Without a profile set (the default) it will just remux the stream. You would want to change sagetv.device.<unique_id>.consumer to opendct.consumer.FFmpegTransSageTVConsumerImpl. The reason this might help is because the writer is asyncronous to FFmpeg and the producer. This was done because it was actually faster and a little less CPU intensive when actually transcoding.
__________________
SageTV v9 Server: ASRock Z97 Extreme4, Intel i7-4790K @ 4.4Ghz, 32GB RAM, 6x 3TB 7200rpm HD, 2x 5TB 7200rpm HD, 2x 6TB 7200rpm HD, 4x 256GB SSD, 4x 500GB SSD, unRAID Pro 6.7.2 (Dual Parity + SSD Cache).
Capture: 1x Ceton InfiniTV 4 (ClearQAM), 2x Ceton InfiniTV 6, 1x BM1000-HDMI, 1x BM3500-HDMI.

Clients: 1x HD300 (Living Room), 1x HD200 (Master Bedroom).
Software: OpenDCT :: WMC Live TV Tuner :: Schedules Direct EPG

Last edited by EnterNoEscape; 03-21-2016 at 10:05 PM.
Reply With Quote
  #612  
Old 03-22-2016, 06:33 AM
Fuzzy's Avatar
Fuzzy Fuzzy is offline
SageTVaholic
 
Join Date: Sep 2005
Location: Jurupa Valley, CA
Posts: 9,957
Quote:
Originally Posted by HelenWeathers View Post
I don't remember the nitty gritty details of how it worked but - you could set up channels/ranges to ignore. I was using DirecTV at the time and didn't need to run comskip on my premium channels so I configured 500-599 to be excluded by comskip.

I suppose you could use another seperator in listings for ranges i.e. 10-1,17-1,500~599 where 10-1 & 17-1 are individual channels and 500~599 is a range.
I can't really see much of a reason to have different consumers for different subchannels on the same main channel, as they'd all be in the same stream anyway, so a consumer that works well for one is likely to work well for the others as well. So said consumer selection list could handle just the major channel numbers.
__________________
Buy Fuzzy a beer! (Fuzzy likes beer)

unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers.
Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA.
Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S
Other Clients: Mi Box in Master Bedroom, HD-200 in kids room
Reply With Quote
  #613  
Old 03-22-2016, 06:47 AM
Greg2dot0's Avatar
Greg2dot0 Greg2dot0 is offline
Sage Advanced User
 
Join Date: Dec 2008
Posts: 82
Quote:
Originally Posted by EnterNoEscape View Post
Troubleshooting:
1) Before making any changes, try recording with the NAS turned off if you haven't already. I realize that means you will probably need to change your recording path temporarily.
2) Stop the OpenDCT service.
3) Open opendct.properties
4) Change consumer.ffmpeg.linux_logging to true
6) Start the OpenDCT service and test. At least you'll know what FFmpeg is complaining about.

7) If it's still not working.
8) Stop the OpenDCT service.
9) Open opendct.properties
10) Change all of the entries for sagetv.device.<unique_id>.consumer to opendct.consumer.FFmpegTransSageTVConsumerImpl
11) Start the OpenDCT service and test.

12) If it's still not working.
13) Stop the OpenDCT service.
14) Open opendct.properties
15) Change all of the entries for sagetv.device.<unique_id>.consumer to opendct.consumer.RawSageTVConsumerImpl
16) Start the OpenDCT service and test. If it still isn't working, try to create a short (< 5 mins) using this consumer so I can take a look at it.
I haven't fully tested this yet, but early indications are that changing sagetv.device.<unique_id>.consumer to opendct.consumer.FFmpegTransSageTVConsumerImpl (#10) has had a dramatic improvement. I still have gotten a few PES packet size mismatches followed by Continuity check failed but that was early on. I will continue to test over the next couple of days and report back all of my findings.

On a side note, I did turn back on the NAS and doesn't seem to be impacting the current settings.
__________________
Production SageTV Server: ASUS P8P67-Pro, 16gb RAM, Crucial m4 256GB SSD, Unbunto 16.4.04 LTS (Server x64), WDC Red 4TB
Capture: 1x HDHR Prime, 1x HDHomeRun (ClearQAM)
Clients: 1x HD300, 2x HD200, 2x Placeshifters
Reply With Quote
  #614  
Old 03-22-2016, 10:33 AM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by Fuzzy View Post
I can't really see much of a reason to have different consumers for different subchannels on the same main channel, as they'd all be in the same stream anyway, so a consumer that works well for one is likely to work well for the others as well. So said consumer selection list could handle just the major channel numbers.
Understood, but I like to be thorough. I'm sure one day there will be that one exception that likely will have nothing to do with ATSC broadcast and I'll be adding support anyway. The way I have it coded right now for the 0.5 release is if there are two dashes between commas, it's considered a channel and not a range. It wasn't hard to accommodate this configuration, so why not.

Ex. "508-510,21-4-1,2-4" would cover the channels 508, 509, 510, 21-4-1, 2, 3, 4
__________________
SageTV v9 Server: ASRock Z97 Extreme4, Intel i7-4790K @ 4.4Ghz, 32GB RAM, 6x 3TB 7200rpm HD, 2x 5TB 7200rpm HD, 2x 6TB 7200rpm HD, 4x 256GB SSD, 4x 500GB SSD, unRAID Pro 6.7.2 (Dual Parity + SSD Cache).
Capture: 1x Ceton InfiniTV 4 (ClearQAM), 2x Ceton InfiniTV 6, 1x BM1000-HDMI, 1x BM3500-HDMI.

Clients: 1x HD300 (Living Room), 1x HD200 (Master Bedroom).
Software: OpenDCT :: WMC Live TV Tuner :: Schedules Direct EPG
Reply With Quote
  #615  
Old 03-22-2016, 10:37 AM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by Greg2dot0 View Post
I haven't fully tested this yet, but early indications are that changing sagetv.device.<unique_id>.consumer to opendct.consumer.FFmpegTransSageTVConsumerImpl (#10) has had a dramatic improvement. I still have gotten a few PES packet size mismatches followed by Continuity check failed but that was early on. I will continue to test over the next couple of days and report back all of my findings.

On a side note, I did turn back on the NAS and doesn't seem to be impacting the current settings.
Good to hear things are improving. I'm starting to think about making that one the default since it seems to fix things for some users and I haven't heard anyone say it made things worse. If you just see those when the recording starts, it's a non-issue. It's expected since you can't really go to the "start" of a broadcast, so the first few TS packets might be the tail end of a PES packet.
__________________
SageTV v9 Server: ASRock Z97 Extreme4, Intel i7-4790K @ 4.4Ghz, 32GB RAM, 6x 3TB 7200rpm HD, 2x 5TB 7200rpm HD, 2x 6TB 7200rpm HD, 4x 256GB SSD, 4x 500GB SSD, unRAID Pro 6.7.2 (Dual Parity + SSD Cache).
Capture: 1x Ceton InfiniTV 4 (ClearQAM), 2x Ceton InfiniTV 6, 1x BM1000-HDMI, 1x BM3500-HDMI.

Clients: 1x HD300 (Living Room), 1x HD200 (Master Bedroom).
Software: OpenDCT :: WMC Live TV Tuner :: Schedules Direct EPG
Reply With Quote
  #616  
Old 03-22-2016, 10:51 AM
jarredduq's Avatar
jarredduq jarredduq is offline
Sage Advanced User
 
Join Date: Mar 2009
Location: Stockton, CA - Most miserable city in the USA, SageTV makes it bearable
Posts: 201
Thumbs up Thank you

Just want to say thank you for creating this awesome add-on for Sage. It's great to see development continuing to move forward.
__________________
Server: HP w/Intel i7-4770S CPU @ 3.10GHz , 500GB SSD, 16GB DDR3, Win 10 64-bit, 4TB of SSD for recording
SageTV: 9.2 - 64-Bit
Capture Devices: 2xHD Homerun Prime and HD-PVR (Comcast Premium/Music Channels)
Client 1, 2, 3, and 4: HD200.
NAS: Synology DS220+ 8TB (Movie Storage)
Sage Add-ons: Jetty, Neilms Webserver (Jetty), Mobile Web, Play-On Plug-in, Comskip Plug-in
Reply With Quote
  #617  
Old 03-22-2016, 12:52 PM
troll5501 troll5501 is offline
Sage Advanced User
 
Join Date: Jun 2006
Posts: 136
Quote:
Originally Posted by EnterNoEscape View Post
To verify that it's the http tuning at fault, in opendct.properties, change hdhr.allow_http_tuning to false.

Unfortunately if it is the http tuning causing the problem for you, there isn't much you can do other than not use it. I was able to trip it up a little today by transferring a large file, but nowhere near as bad as it can get with UDP. So while the TCP/IP connection might not be disconnected, it would appear that the HDHomeRun will drop TS packets silently if you're not keeping up.

You could also try just re-muxing with the new transcoding consumer. Without a profile set (the default) it will just remux the stream. You would want to change sagetv.device.<unique_id>.consumer to opendct.consumer.FFmpegTransSageTVConsumerImpl. The reason this might help is because the writer is asyncronous to FFmpeg and the producer. This was done because it was actually faster and a little less CPU intensive when actually transcoding.
Thanks for the tips, I'll do some more testing with some of these options. I'm trying to see if I can correlate the errors with other activities such as writes/flushes to NFS storage (which is also tcp) but nothing too obvious so far.

I've also noticed another issue several times, and I think maybe it's the same thing that Greg2dot0 experienced. Occasionally (one time when starting a recording, and most recently during a recording) it seems to get stuck in a loop with lots of "Read frame with same dts as last frame. Skipping this frame." with a constantly increasing dts value, like this:

Code:
14:30:04.416 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] INFO  ffmpeg - Last message repeated 1 time.
14:30:04.416 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG ffmpeg - [mpegts @ 0x7efce8222880] Delay between the first packet and last packet in the muxing queue is 139625885384864 > 0: forcing output
14:30:06.854 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] INFO  ffmpeg - Last message repeated 161 times.
14:30:06.854 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG ffmpeg - [mpegts @ 0x7efce80b62a0] Continuity check failed for pid 793559200 expected 0 got 0
14:30:06.858 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] INFO  ffmpeg - Last message repeated 1 time.
14:30:06.858 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] WARN  ffmpeg - [mpegts @ 0x7efce80b62a0] PES packet size mismatch
14:30:06.861 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG ffmpeg - [mpegts @ 0x7efce80b62a0] Continuity check failed for pid 793559200 expected 0 got 0
14:30:06.861 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] WARN  ffmpeg - [mpegts @ 0x7efce80b62a0] PES packet size mismatch
14:30:06.963 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] WARN  ffmpeg - [mpegts @ 0x7efce80b62a0] DTS 139625885384864 < 0 out of order
14:30:07.051 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471089126
14:30:07.075 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471092129
14:30:07.075 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471095132
14:30:07.076 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG ffmpeg - [mpegts @ 0x7efce8222880] Delay between the first packet and last packet in the muxing queue is 139625885384864 > 0: forcing output
14:30:07.077 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471098135
14:30:07.082 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471101138
14:30:07.099 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471104141
14:30:07.111 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471107144
14:30:07.156 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471110147
14:30:07.166 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471113150
14:30:07.177 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471116153
14:30:07.221 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471119156
14:30:07.233 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471122159
14:30:07.243 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471125162
14:30:07.278 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471128165
14:30:07.289 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471131168
14:30:07.301 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471134171
14:30:07.350 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471137174
14:30:07.364 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471140177
14:30:07.392 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471143180
14:30:07.451 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471146183
14:30:07.466 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471149186
14:30:07.492 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471152189
14:30:07.531 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471155192
14:30:07.560 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471158195
14:30:07.593 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471161198
14:30:07.627 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471164201
14:30:07.660 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471167204
14:30:07.693 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471170207
14:30:07.738 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471173210
14:30:07.760 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471176213
I just happened a few minutes ago and when this happens there is no video in SageTV. After a minute or so of these errors, I stopped the recording and restarted it immediately and it worked fine.
__________________
Server: HP DL380 G6, VMware ESXi 5.0 with HW passthrough for USB and Firewire, 4 x HD-PVR, ZFS storage
SageTV: Production: 7.1.9+Java 1.6.0_32 on XP, Test: 9.0.4.291+Java 1.8.0_72 on Linux 64-bit
Clients: 2 x Sage HD200 Extender, 1 x Sage HD100 Extender
Sources: 4 x Motorola DCH-3200 (firewire channel changing), HD Homerun Prime, OpenDCT 0.5.7
Reply With Quote
  #618  
Old 03-22-2016, 01:56 PM
nyplayer nyplayer is offline
SageTVaholic
 
Join Date: Sep 2005
Posts: 4,799
In case anyone is interested the new HDHomerun Firmware lets you know if the channel is AVC or not on the Web Page. 95% of my channels are now H.264.
__________________
Windows 10 I3 Dual Core 3.0 Server, SageTV9... OpenDCT with 2 HDHRPrimes and 4 HDHRconnects for a total of 14 Tuners.
Reply With Quote
  #619  
Old 03-22-2016, 02:07 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by troll5501 View Post
Thanks for the tips, I'll do some more testing with some of these options. I'm trying to see if I can correlate the errors with other activities such as writes/flushes to NFS storage (which is also tcp) but nothing too obvious so far.

I've also noticed another issue several times, and I think maybe it's the same thing that Greg2dot0 experienced. Occasionally (one time when starting a recording, and most recently during a recording) it seems to get stuck in a loop with lots of "Read frame with same dts as last frame. Skipping this frame." with a constantly increasing dts value, like this:

Code:
14:30:04.416 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] INFO  ffmpeg - Last message repeated 1 time.
14:30:04.416 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG ffmpeg - [mpegts @ 0x7efce8222880] Delay between the first packet and last packet in the muxing queue is 139625885384864 > 0: forcing output
14:30:06.854 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] INFO  ffmpeg - Last message repeated 161 times.
14:30:06.854 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG ffmpeg - [mpegts @ 0x7efce80b62a0] Continuity check failed for pid 793559200 expected 0 got 0
14:30:06.858 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] INFO  ffmpeg - Last message repeated 1 time.
14:30:06.858 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] WARN  ffmpeg - [mpegts @ 0x7efce80b62a0] PES packet size mismatch
14:30:06.861 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG ffmpeg - [mpegts @ 0x7efce80b62a0] Continuity check failed for pid 793559200 expected 0 got 0
14:30:06.861 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] WARN  ffmpeg - [mpegts @ 0x7efce80b62a0] PES packet size mismatch
14:30:06.963 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] WARN  ffmpeg - [mpegts @ 0x7efce80b62a0] DTS 139625885384864 < 0 out of order
14:30:07.051 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471089126
14:30:07.075 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471092129
14:30:07.075 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471095132
14:30:07.076 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG ffmpeg - [mpegts @ 0x7efce8222880] Delay between the first packet and last packet in the muxing queue is 139625885384864 > 0: forcing output
14:30:07.077 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471098135
14:30:07.082 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471101138
14:30:07.099 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471104141
14:30:07.111 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471107144
14:30:07.156 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471110147
14:30:07.166 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471113150
14:30:07.177 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471116153
14:30:07.221 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471119156
14:30:07.233 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471122159
14:30:07.243 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471125162
14:30:07.278 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471128165
14:30:07.289 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471131168
14:30:07.301 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471134171
14:30:07.350 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471137174
14:30:07.364 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471140177
14:30:07.392 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471143180
14:30:07.451 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471146183
14:30:07.466 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471149186
14:30:07.492 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471152189
14:30:07.531 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471155192
14:30:07.560 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471158195
14:30:07.593 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471161198
14:30:07.627 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471164201
14:30:07.660 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471167204
14:30:07.693 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471170207
14:30:07.738 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471173210
14:30:07.760 [FFmpegSageTVConsumerImpl-3780:DCT-HDHomeRun Prime Tuner 13191941-1] DEBUG FFmpegSageTVConsumerImpl - Read frame with same dts as last frame. Skipping this frame. dts = 471176213
I just happened a few minutes ago and when this happens there is no video in SageTV. After a minute or so of these errors, I stopped the recording and restarted it immediately and it worked fine.
That's interesting. Particularly what happens first. It looks like a dts of the first packet is read incorrectly and then sets the tone for the rest of the recording. I'll see if I can make OpenDCT discern what's a good or bad packet better. The reason you might not have seen this in the past because before we were only interested in packets that were the exact same number as the last packet. Now it's checking for <= because of some Comcast content that would do some strange things. I need to also add checking for the sanity of the number since that number way above 8589934592 and is the reason everything is being thrown off.
__________________
SageTV v9 Server: ASRock Z97 Extreme4, Intel i7-4790K @ 4.4Ghz, 32GB RAM, 6x 3TB 7200rpm HD, 2x 5TB 7200rpm HD, 2x 6TB 7200rpm HD, 4x 256GB SSD, 4x 500GB SSD, unRAID Pro 6.7.2 (Dual Parity + SSD Cache).
Capture: 1x Ceton InfiniTV 4 (ClearQAM), 2x Ceton InfiniTV 6, 1x BM1000-HDMI, 1x BM3500-HDMI.

Clients: 1x HD300 (Living Room), 1x HD200 (Master Bedroom).
Software: OpenDCT :: WMC Live TV Tuner :: Schedules Direct EPG
Reply With Quote
  #620  
Old 03-22-2016, 05:02 PM
waylo waylo is offline
Sage Advanced User
 
Join Date: Feb 2006
Posts: 238
Quote:
Originally Posted by nyplayer View Post
In case anyone is interested the new HDHomerun Firmware lets you know if the channel is AVC or not on the Web Page. 95% of my channels are now H.264.
Can you confirm the version #? I'm looking on the silicondust website but do not see anything newer than 8/2015. My local website channel page only shows DRM status.
__________________

Server: SageTV 9.2.6x64 on Win10 x64 Home, i7-2600, 8gb RAM, OpenDCT, Java 1.8, 20TB storage
Display: EVGA GT 1030 fanless to Sony LED TV via DVI-HDMI
Capture Devices: HDHR Prime for Comcast, HDHR Dual for OTA (retired)
Clients: Nvidia Shield Android miniclient
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ATI TV Wonder Digital Cable Tuner & SageTV nyle Hardware Support 4 02-17-2009 10:12 PM
ATI TV Wonder Digital Cable Tuner rajczi Hardware Support 4 01-14-2008 08:24 PM
ATI TV Wonder™ Digital Cable Tuner dadams Hardware Support 4 01-09-2007 10:55 AM
Digital Cable - one guide - need HD on one tuner reg tv on other Kimper SageTV Beta Test Software 14 11-27-2006 08:15 PM
Multi-tuner Digital Cable mlbdude SageTV Software 0 06-26-2003 01:08 PM


All times are GMT -6. The time now is 04:03 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2022, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.