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
  #621  
Old 03-22-2016, 06:02 PM
nyplayer nyplayer is offline
SageTVaholic
 
Join Date: Sep 2005
Posts: 4,061
Quote:
Originally Posted by waylo View Post
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.
It is in the HDHomerun DVR section. We get updates first there.
https://www.silicondust.com/forum/vi...?f=119&t=20613
https://www.silicondust.com/forum/vi...32339&start=15
Attached Images
File Type: jpg sdwebpage.jpg (130.0 KB, 57 views)
__________________
Windows 10 I3 Dual Core 3.0 Server, SageTV9... OpenDCT with 2 HDHRPrimes and 4 HDHRconnects for a total of 14 Tuners.

Last edited by nyplayer; 03-22-2016 at 06:11 PM.
Reply With Quote
  #622  
Old 03-22-2016, 08:50 PM
matt91's Avatar
matt91 matt91 is offline
Sage Icon
 
Join Date: Feb 2005
Location: Washington, DC
Posts: 1,185
HI -
Trying OpenDCT for the first time - previously had been using PrimeNetEncoder. I grabbed the beta 0.4.36 version to try.

I seem to be hitting some errors when I run ./console_only. I can actually get the /etc/opendct/conf/lineup generated (looks ok to me) but am having issues in Sage getting that lineup to work.

this is the last "crash.log"
Code:
22:31:20.579 [WrapperSimpleAppMain] INFO  Main - Starting OpenDCT 0.4.36...
22:31:20.599 [WrapperSimpleAppMain] DEBUG Config - OSVersion is parsing the name 'Linux'.
22:31:20.599 [WrapperSimpleAppMain] DEBUG Config - OSVersion determined that 'Linux' is LINUX.
22:31:20.632 [WrapperSimpleAppMain] INFO  Main - OpenDCT logging to the directory '/var/log/opendct'.
22:31:20.643 [WrapperSimpleAppMain] INFO  UpnpManager - Logging Cling UPnP to '/var/log/opendct/opendct_cling.log'.
22:31:20.643 [WrapperSimpleAppMain] DEBUG UpnpManager - Logging level for Cling UPnP is set to 'severe'.
22:31:20.645 [WrapperSimpleAppMain] WARN  LinuxPowerMessagePump - System power state messages are currently not implemented for Linux.
22:31:20.646 [FFmpegAsyncInit-21] INFO  Main - FFmpeg loading...
22:31:20.648 [WrapperSimpleAppMain] INFO  NetworkPowerEventManger - Network interfaces which are up and have an IP4 address are: 
name:eth0 (eth0) 192.168.1.9
22:31:20.706 [WrapperSimpleAppMain] INFO  UpnpManager - Starting UPnP services...
22:31:20.728 [WrapperSimpleAppMain] INFO  DCTDefaultUpnpServiceConfiguration - Using the interface 'eth0' with IP address 192.168.1.9 for UPnP discovery.
22:31:20.749 [WrapperSimpleAppMain] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
22:31:20.759 [WrapperSimpleAppMain] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
22:31:20.762 [UPnPDiscovery-33] INFO  UpnpManager - UPnP discovery thread has started.
22:31:20.774 [WrapperSimpleAppMain] DEBUG Config - OSVersion is parsing the name 'Linux'.
22:31:20.774 [WrapperSimpleAppMain] DEBUG Config - OSVersion determined that 'Linux' is LINUX.
22:31:20.774 [WrapperSimpleAppMain] DEBUG Config - OSVersion is parsing the name 'Linux'.
22:31:20.774 [WrapperSimpleAppMain] DEBUG Config - OSVersion determined that 'Linux' is LINUX.
22:31:20.834 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - HDHomeRun discovery sender thread started.
22:31:20.835 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscovery - HDHomeRun discovery receive thread for /192.168.1.255:65001 broadcast started.
22:31:20.837 [WrapperSimpleAppMain] INFO  Main - Running in daemon mode...
22:31:20.840 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26
22:31:20.843 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26
22:31:20.845 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
22:31:20.848 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 33
22:31:20.848 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/hwmodel' value: 'null' lockKey: '0' sendLength: 23
22:31:20.849 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscoverer - Discovered a new HDHomeRun device 'HDHomeRun DRI Tuner 131C22D1'.
22:31:21.179 [FFmpegAsyncInit-21] INFO  Main - FFmpeg loaded in 535ms.
22:31:21.190 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26
22:31:21.191 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/model' value: 'null' lockKey: '0' sendLength: 21
22:31:21.192 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/version' value: 'null' lockKey: '0' sendLength: 23
22:31:21.193 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/features' value: 'null' lockKey: '0' sendLength: 24
22:31:21.197 [HDHomeRunDiscoveryReceive-37] DEBUG HDHRNativeCaptureDevice - HDHomeRun details: HDHR3-CC, hdhomerun3_cablecard, 20150826, HDHomeRunFeatures{channelmap=[us-cable, us-hrc, us-irc, kr-cable], modulation=[auto, auto6c, qam], autoModulation=[]}
22:31:21.197 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: 'help' value: 'null' lockKey: '0' sendLength: 15
22:31:21.199 [HDHomeRunDiscoveryReceive-37] DEBUG HDHRNativeCaptureDevice - HDHomeRun help: [Supported configuration options:, /card/status, /ir/target <protocol>://<ip>:<port>, /lineup/scan, /oob/channel <modulation>:<freq>, /oob/debug, /oob/status, /sys/copyright, /sys/debug, /sys/features, /sys/hwmodel, /sys/model, /sys/restart <resource>, /sys/version, /tuner<n>/channel <modulation>:<freq|ch>, /tuner<n>/channelmap <channelmap>, /tuner<n>/debug, /tuner<n>/filter "0x<nnnn>-0x<nnnn> [...]", /tuner<n>/lockkey, /tuner<n>/program <program number>, /tuner<n>/streaminfo, /tuner<n>/status, /tuner<n>/target <ip>:<port>, /tuner<n>/vchannel <vchannel>, /tuner<n>/vstatus]
22:31:21.199 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/card/status' value: 'null' lockKey: '0' sendLength: 23
22:31:21.241 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/card/status' value: 'null' lockKey: '0' sendLength: 23
22:31:21.245 [HDHomeRunDiscoveryReceive-37] DEBUG RTPCaptureDeviceServices - Initializing RTSP client...
22:31:21.246 [HDHomeRunDiscoveryReceive-37] DEBUG RTPCaptureDeviceServices - Getting a port for incoming RTP data...
22:31:21.246 [HDHomeRunDiscoveryReceive-37] INFO  HDHRNativeCaptureDevice - Encoder Manufacturer: 'Silicondust', Number: 0, Remote IP: '/192.168.1.2', Local IP: '/192.168.1.9', CableCARD: true, Lineup: 'dct_hdhomerun', Offline Scan Enabled: false, RTP Port: 8412
22:31:21.249 [HDHomeRunDiscoveryReceive-37] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 131C22D1-0' is ready.
22:31:21.251 [HDHomeRunDiscoveryReceive-37] DEBUG SageTVSocketServer - Setting listening flag...
22:31:21.251 [HDHomeRunDiscoveryReceive-37] INFO  SageTVSocketServer - Opening ServerSocket on port 9000...
22:31:21.251 [SageTVTuningMonitor-53] INFO  SageTVTuningMonitor - Tuning monitor thread started.
22:31:21.252 [HDHomeRunDiscoveryReceive-37] ERROR SageTVSocketServer - Unable to open SocketServer on port 9000 => java.net.BindException: Address already in use
22:31:21.253 [HDHomeRunDiscoveryReceive-37] FATAL ExitCode - OpenDCT experienced a fatal error: SageTVManager was unable to open a required socket server listening port.
this sage version is the newest installed via the script here.

Have I missed a step in setting up OpenDCT and getting the channels to populate? (I ran ./console_only, ran Sage, added tuner, ran channel scan)
__________________
Server: Ubuntu 16.04 running Sage for Linux v9
Reply With Quote
  #623  
Old 03-23-2016, 05:38 AM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,519
Quote:
Originally Posted by matt91 View Post
HI -
Trying OpenDCT for the first time - previously had been using PrimeNetEncoder. I grabbed the beta 0.4.36 version to try.

I seem to be hitting some errors when I run ./console_only. I can actually get the /etc/opendct/conf/lineup generated (looks ok to me) but am having issues in Sage getting that lineup to work.

this is the last "crash.log"
Code:
22:31:20.579 [WrapperSimpleAppMain] INFO  Main - Starting OpenDCT 0.4.36...
22:31:20.599 [WrapperSimpleAppMain] DEBUG Config - OSVersion is parsing the name 'Linux'.
22:31:20.599 [WrapperSimpleAppMain] DEBUG Config - OSVersion determined that 'Linux' is LINUX.
22:31:20.632 [WrapperSimpleAppMain] INFO  Main - OpenDCT logging to the directory '/var/log/opendct'.
22:31:20.643 [WrapperSimpleAppMain] INFO  UpnpManager - Logging Cling UPnP to '/var/log/opendct/opendct_cling.log'.
22:31:20.643 [WrapperSimpleAppMain] DEBUG UpnpManager - Logging level for Cling UPnP is set to 'severe'.
22:31:20.645 [WrapperSimpleAppMain] WARN  LinuxPowerMessagePump - System power state messages are currently not implemented for Linux.
22:31:20.646 [FFmpegAsyncInit-21] INFO  Main - FFmpeg loading...
22:31:20.648 [WrapperSimpleAppMain] INFO  NetworkPowerEventManger - Network interfaces which are up and have an IP4 address are: 
name:eth0 (eth0) 192.168.1.9
22:31:20.706 [WrapperSimpleAppMain] INFO  UpnpManager - Starting UPnP services...
22:31:20.728 [WrapperSimpleAppMain] INFO  DCTDefaultUpnpServiceConfiguration - Using the interface 'eth0' with IP address 192.168.1.9 for UPnP discovery.
22:31:20.749 [WrapperSimpleAppMain] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
22:31:20.759 [WrapperSimpleAppMain] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
22:31:20.762 [UPnPDiscovery-33] INFO  UpnpManager - UPnP discovery thread has started.
22:31:20.774 [WrapperSimpleAppMain] DEBUG Config - OSVersion is parsing the name 'Linux'.
22:31:20.774 [WrapperSimpleAppMain] DEBUG Config - OSVersion determined that 'Linux' is LINUX.
22:31:20.774 [WrapperSimpleAppMain] DEBUG Config - OSVersion is parsing the name 'Linux'.
22:31:20.774 [WrapperSimpleAppMain] DEBUG Config - OSVersion determined that 'Linux' is LINUX.
22:31:20.834 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - HDHomeRun discovery sender thread started.
22:31:20.835 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscovery - HDHomeRun discovery receive thread for /192.168.1.255:65001 broadcast started.
22:31:20.837 [WrapperSimpleAppMain] INFO  Main - Running in daemon mode...
22:31:20.840 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26
22:31:20.843 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26
22:31:20.845 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
22:31:20.848 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 33
22:31:20.848 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/hwmodel' value: 'null' lockKey: '0' sendLength: 23
22:31:20.849 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscoverer - Discovered a new HDHomeRun device 'HDHomeRun DRI Tuner 131C22D1'.
22:31:21.179 [FFmpegAsyncInit-21] INFO  Main - FFmpeg loaded in 535ms.
22:31:21.190 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26
22:31:21.191 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/model' value: 'null' lockKey: '0' sendLength: 21
22:31:21.192 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/version' value: 'null' lockKey: '0' sendLength: 23
22:31:21.193 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/features' value: 'null' lockKey: '0' sendLength: 24
22:31:21.197 [HDHomeRunDiscoveryReceive-37] DEBUG HDHRNativeCaptureDevice - HDHomeRun details: HDHR3-CC, hdhomerun3_cablecard, 20150826, HDHomeRunFeatures{channelmap=[us-cable, us-hrc, us-irc, kr-cable], modulation=[auto, auto6c, qam], autoModulation=[]}
22:31:21.197 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: 'help' value: 'null' lockKey: '0' sendLength: 15
22:31:21.199 [HDHomeRunDiscoveryReceive-37] DEBUG HDHRNativeCaptureDevice - HDHomeRun help: [Supported configuration options:, /card/status, /ir/target <protocol>://<ip>:<port>, /lineup/scan, /oob/channel <modulation>:<freq>, /oob/debug, /oob/status, /sys/copyright, /sys/debug, /sys/features, /sys/hwmodel, /sys/model, /sys/restart <resource>, /sys/version, /tuner<n>/channel <modulation>:<freq|ch>, /tuner<n>/channelmap <channelmap>, /tuner<n>/debug, /tuner<n>/filter "0x<nnnn>-0x<nnnn> [...]", /tuner<n>/lockkey, /tuner<n>/program <program number>, /tuner<n>/streaminfo, /tuner<n>/status, /tuner<n>/target <ip>:<port>, /tuner<n>/vchannel <vchannel>, /tuner<n>/vstatus]
22:31:21.199 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/card/status' value: 'null' lockKey: '0' sendLength: 23
22:31:21.241 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/card/status' value: 'null' lockKey: '0' sendLength: 23
22:31:21.245 [HDHomeRunDiscoveryReceive-37] DEBUG RTPCaptureDeviceServices - Initializing RTSP client...
22:31:21.246 [HDHomeRunDiscoveryReceive-37] DEBUG RTPCaptureDeviceServices - Getting a port for incoming RTP data...
22:31:21.246 [HDHomeRunDiscoveryReceive-37] INFO  HDHRNativeCaptureDevice - Encoder Manufacturer: 'Silicondust', Number: 0, Remote IP: '/192.168.1.2', Local IP: '/192.168.1.9', CableCARD: true, Lineup: 'dct_hdhomerun', Offline Scan Enabled: false, RTP Port: 8412
22:31:21.249 [HDHomeRunDiscoveryReceive-37] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 131C22D1-0' is ready.
22:31:21.251 [HDHomeRunDiscoveryReceive-37] DEBUG SageTVSocketServer - Setting listening flag...
22:31:21.251 [HDHomeRunDiscoveryReceive-37] INFO  SageTVSocketServer - Opening ServerSocket on port 9000...
22:31:21.251 [SageTVTuningMonitor-53] INFO  SageTVTuningMonitor - Tuning monitor thread started.
22:31:21.252 [HDHomeRunDiscoveryReceive-37] ERROR SageTVSocketServer - Unable to open SocketServer on port 9000 => java.net.BindException: Address already in use
22:31:21.253 [HDHomeRunDiscoveryReceive-37] FATAL ExitCode - OpenDCT experienced a fatal error: SageTVManager was unable to open a required socket server listening port.
this sage version is the newest installed via the script here.

Have I missed a step in setting up OpenDCT and getting the channels to populate? (I ran ./console_only, ran Sage, added tuner, ran channel scan)
Do you have something you know about already using port 9000? If you don't, double check that you're not running the console and the service at the same time. If you do, you can just change the port OpenDCT will use in /etc/opendct/conf/opendct.properties.

To change the port if needed, stop OpenDCT, then change sagetv.device.<unique_id>.encoder_listen_port and sagetv.new.device.socket_server_shared_port to another port number. Then start it back up again.

Also make sure that in Sage.properties you have network_encoder_discovery set to true.

Update: It just occurred to me that you saw the tuner SageTV and the channel scan didn't return any channels. The channel scan will by default only work if you have run a channel scan on the HDHomeRun itself and is based off of that.
__________________
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-23-2016 at 05:40 AM.
Reply With Quote
  #624  
Old 03-23-2016, 05:57 AM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,519


This should address the issues a few of you saw with the dts filter.

FFmpeg logging in Linux is now enabled by default.

Pre-release support for Ubuntu 16.04 (systemd) was added to the Debian installer. If having the package intelligently decide what you're using doesn't work out, we might need separate packages, so let me know if the installer fails in any interesting way. I tested it across many different Ubuntu versions and flavors, so it should be ok.
__________________
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
  #625  
Old 03-23-2016, 06:12 AM
Greg2dot0's Avatar
Greg2dot0 Greg2dot0 is offline
Sage Advanced User
 
Join Date: Dec 2008
Posts: 82
So, after testing a bunch more recordings, I'm still having some (different) issues after getting to step 10 and updating the consumer to: opendct.consumer.FFmpegTransSageTVConsumerImpl

I've attached the log but wanted to supplement with the times that things started to get "interesting". I set up 3 shows to record from 5pm-6pm and the results are not great.

17:24 (5:24pm)
The device input "DCT-HDHomeRun Prime Tuner 13142E5A-0 on sagetvsa:9000 Digital TV Tuner" stopped producing data while recording "Deadliest Catch" on DSCHD on physical channel 620. SageTV will try to reset the device. This may be caused by a channel that is no longer available.

2 Messages. Last Occurrence: Tue, Mar 22 5:38:15 PM

I actually have 3 segments of the show which support that message
DeadliestCatch-S10E15-275245-0.ts
DeadliestCatch-S10E15-275245-1.ts
DeadliestCatch-S10E15-275245-2.ts

Warning Message Details

The device input "DCT-HDHomeRun Prime Tuner 13142E5A-2 on sagetvsa:9000 Digital TV Tuner" stopped producing data while recording "The Situation Room" on CNNHD on physical channel 600. SageTV will try to reset the device. This may be caused by a channel that is no longer available.

2 Messages. Last Occurrence: Tue, Mar 22 5:59:16 PM
(Same situation where there are 3 segments)

I also noticed that there are a number of errors in the log which started with my testing which I'm not sure if they are related since they also showed up on earlier recordings that didn't have the halts.

17:30:45.068 [FFmpegTransSageTVConsumerImpl-3867CT-HDHomeRun Prime Tuner 13142E5A-0] ERROR ffmpeg - [mpeg2video @ 0x7fcebc00ba80] Invalid frame dimensions 1375953408x0.

I can go ahead and proceed to switching the consumer over to raw mode but considering the inconsistency of this error, not sure how I could do a 5 minute clip that captures the events. Let me know how you want me to proceed. Happy to do anything since this is a testing box.

Lastly, I wanted to add that this is FIOS (since I saw you mention that different systems introduce different nuances).
Attached Files
File Type: txt opendct.txt (735.4 KB, 31 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

Last edited by Greg2dot0; 03-23-2016 at 06:13 AM. Reason: additional info
Reply With Quote
  #626  
Old 03-23-2016, 07:11 AM
matt91's Avatar
matt91 matt91 is offline
Sage Icon
 
Join Date: Feb 2005
Location: Washington, DC
Posts: 1,185
Quote:
Originally Posted by EnterNoEscape View Post
Do you have something you know about already using port 9000?
So I saw the port 9000 last night in the log, but it didn't hit me until you noted it above. I do have something else running on that port [Squeezebox Server, in cast that helps anyone else.] I've changed the OpenDCT port as you suggested, and I can finish the console run without any errors now.

However, I'm still not quite there. I can load up a tuner in Sage, but still can't get it to tune a channel. I'm seeing errors like this in the log:

Code:
08:57:15.618 [SageTVRequestHandler-106:DCT-HDHomeRun Prime Tuner 131C22D1-0] DEBUG HDHomeRunControl - key: '/tuner0/vchannel' value: '4.1' lockKey: '1062731511' sendLength: 39
08:57:15.621 [SageTVRequestHandler-106:DCT-HDHomeRun Prime Tuner 131C22D1-0] ERROR HDHRNativeCaptureDevice - HDHomeRun is unable to tune into channel because the command did not work '133-4-1' => opendct.tuning.hdhomerun.GetSetException: ERROR: invalid virtual channel
	at opendct.tuning.hdhomerun.HDHomeRunControl.setVariable(HDHomeRunControl.java:200)
	at opendct.tuning.hdhomerun.HDHomeRunTuner.set(HDHomeRunTuner.java:135)
	at opendct.tuning.hdhomerun.HDHomeRunTuner.setVirtualChannel(HDHomeRunTuner.java:485)
	at opendct.capture.HDHRNativeCaptureDevice.startEncodingSync(HDHRNativeCaptureDevice.java:606)
	at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:510)
	at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:461)
	at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:234)
	at java.lang.Thread.run(Thread.java:745)

Channel 133.4.1 is correct for the channel I was trying to tune. I can confirm that with the HDHR GUI app I'm running.

Any further thoughts? I have attached the current opendct.log file as well.

thanks again,
matt


edit: Just to be clear, I have run the channel scan via the HDHR web interface, and it locates ~300 channels. I can tune and watch them via VLC (and also with Sage, when I was using PrimeNetEncoder previously)
Attached Files
File Type: txt opendct.log.txt (42.9 KB, 32 views)
__________________
Server: Ubuntu 16.04 running Sage for Linux v9

Last edited by matt91; 03-23-2016 at 07:39 AM.
Reply With Quote
  #627  
Old 03-23-2016, 07:17 AM
Greg2dot0's Avatar
Greg2dot0 Greg2dot0 is offline
Sage Advanced User
 
Join Date: Dec 2008
Posts: 82
Just wanted to note a small order issue for 14.04: The syntax is backwards:

To start the OpenDCT service type:
Ubuntu 14.04:
sudo service start opendct
Ubuntu 16.04:
sudo systemctl enable opendct.service
sudo systemctl start opendct.service
greg@sagetvsa:~$ sudo service start opendct
start: unrecognized service
greg@sagetvsa:~$ sudo service opendct start
Starting OpenDCT Digital Cable Tuner for SageTV...
__________________
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
  #628  
Old 03-23-2016, 08:44 AM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,519
Quote:
Originally Posted by Greg2dot0 View Post
So, after testing a bunch more recordings, I'm still having some (different) issues after getting to step 10 and updating the consumer to: opendct.consumer.FFmpegTransSageTVConsumerImpl

I've attached the log but wanted to supplement with the times that things started to get "interesting". I set up 3 shows to record from 5pm-6pm and the results are not great.

17:24 (5:24pm)
The device input "DCT-HDHomeRun Prime Tuner 13142E5A-0 on sagetvsa:9000 Digital TV Tuner" stopped producing data while recording "Deadliest Catch" on DSCHD on physical channel 620. SageTV will try to reset the device. This may be caused by a channel that is no longer available.

2 Messages. Last Occurrence: Tue, Mar 22 5:38:15 PM

I actually have 3 segments of the show which support that message
DeadliestCatch-S10E15-275245-0.ts
DeadliestCatch-S10E15-275245-1.ts
DeadliestCatch-S10E15-275245-2.ts

Warning Message Details

The device input "DCT-HDHomeRun Prime Tuner 13142E5A-2 on sagetvsa:9000 Digital TV Tuner" stopped producing data while recording "The Situation Room" on CNNHD on physical channel 600. SageTV will try to reset the device. This may be caused by a channel that is no longer available.

2 Messages. Last Occurrence: Tue, Mar 22 5:59:16 PM
(Same situation where there are 3 segments)

I also noticed that there are a number of errors in the log which started with my testing which I'm not sure if they are related since they also showed up on earlier recordings that didn't have the halts.

17:30:45.068 [FFmpegTransSageTVConsumerImpl-3867CT-HDHomeRun Prime Tuner 13142E5A-0] ERROR ffmpeg - [mpeg2video @ 0x7fcebc00ba80] Invalid frame dimensions 1375953408x0.

I can go ahead and proceed to switching the consumer over to raw mode but considering the inconsistency of this error, not sure how I could do a 5 minute clip that captures the events. Let me know how you want me to proceed. Happy to do anything since this is a testing box.

Lastly, I wanted to add that this is FIOS (since I saw you mention that different systems introduce different nuances).
I have FiOS myself and I haven't seen these particular problems, so we must just watch different shows. Anyhow, upgrade to RC2, I think it will fix the halts. It takes into account if FFmpeg returns any absurd values and also makes sure the gap between dts frames is not ridiculous.
__________________
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
  #629  
Old 03-23-2016, 08:50 AM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,519
Quote:
Originally Posted by Greg2dot0 View Post
Just wanted to note a small order issue for 14.04: The syntax is backwards:

To start the OpenDCT service type:
Ubuntu 14.04:
sudo service start opendct
Ubuntu 16.04:
sudo systemctl enable opendct.service
sudo systemctl start opendct.service
greg@sagetvsa:~$ sudo service start opendct
start: unrecognized service
greg@sagetvsa:~$ sudo service opendct start
Starting OpenDCT Digital Cable Tuner for SageTV...
Fixed for new downloads.
__________________
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
  #630  
Old 03-23-2016, 09:11 AM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,519
Quote:
Originally Posted by matt91 View Post
So I saw the port 9000 last night in the log, but it didn't hit me until you noted it above. I do have something else running on that port [Squeezebox Server, in cast that helps anyone else.] I've changed the OpenDCT port as you suggested, and I can finish the console run without any errors now.

However, I'm still not quite there. I can load up a tuner in Sage, but still can't get it to tune a channel. I'm seeing errors like this in the log:

Code:
08:57:15.618 [SageTVRequestHandler-106:DCT-HDHomeRun Prime Tuner 131C22D1-0] DEBUG HDHomeRunControl - key: '/tuner0/vchannel' value: '4.1' lockKey: '1062731511' sendLength: 39
08:57:15.621 [SageTVRequestHandler-106:DCT-HDHomeRun Prime Tuner 131C22D1-0] ERROR HDHRNativeCaptureDevice - HDHomeRun is unable to tune into channel because the command did not work '133-4-1' => opendct.tuning.hdhomerun.GetSetException: ERROR: invalid virtual channel
	at opendct.tuning.hdhomerun.HDHomeRunControl.setVariable(HDHomeRunControl.java:200)
	at opendct.tuning.hdhomerun.HDHomeRunTuner.set(HDHomeRunTuner.java:135)
	at opendct.tuning.hdhomerun.HDHomeRunTuner.setVirtualChannel(HDHomeRunTuner.java:485)
	at opendct.capture.HDHRNativeCaptureDevice.startEncodingSync(HDHRNativeCaptureDevice.java:606)
	at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:510)
	at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:461)
	at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:234)
	at java.lang.Thread.run(Thread.java:745)

Channel 133.4.1 is correct for the channel I was trying to tune. I can confirm that with the HDHR GUI app I'm running.

Any further thoughts? I have attached the current opendct.log file as well.

thanks again,
matt


edit: Just to be clear, I have run the channel scan via the HDHR web interface, and it locates ~300 channels. I can tune and watch them via VLC (and also with Sage, when I was using PrimeNetEncoder previously)
The message ERROR: invalid virtual channel is coming directly from the HDHomeRun device when it tries to tune the provided vchannel and is not exactly a fault in OpenDCT. It might work if it was being tuned as a channel instead, but that's not how OpenDCT tunes digital cable. 133.4.1 is not a correctly formatted vchannel unless you're trying to tune ATSC. OpenDCT makes no effort to determine if it's a channel or vchannel if the HDHomeRun is detected as a DCT because I can't think of any reason not use the vchannel. I can see that the OpenDCT returns no values with any periods or dashes in them to SageTV from your channel scan, so it's not clear how you have these remapped values in your lineup.

It might help to create a new lineup in SageTV for the OpenDCT provided tuner, do a channel scan and try again. The biggest reason why you would want to use the vchannel over channel is because your provider could change the mapping at random and you'll either be recording the wrong channel or not record anything.
__________________
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-23-2016 at 09:37 AM.
Reply With Quote
  #631  
Old 03-23-2016, 10:54 AM
matt91's Avatar
matt91 matt91 is offline
Sage Icon
 
Join Date: Feb 2005
Location: Washington, DC
Posts: 1,185
Quote:
Originally Posted by EnterNoEscape View Post
The message ERROR: invalid virtual channel is coming directly from the HDHomeRun device when it tries to tune the provided vchannel and is not exactly a fault in OpenDCT. It might work if it was being tuned as a channel instead, but that's not how OpenDCT tunes digital cable. 133.4.1 is not a correctly formatted vchannel unless you're trying to tune ATSC. OpenDCT makes no effort to determine if it's a channel or vchannel if the HDHomeRun is detected as a DCT because I can't think of any reason not use the vchannel. I can see that the OpenDCT returns no values with any periods or dashes in them to SageTV from your channel scan, so it's not clear how you have these remapped values in your lineup.

It might help to create a new lineup in SageTV for the OpenDCT provided tuner, do a channel scan and try again. The biggest reason why you would want to use the vchannel over channel is because your provider could change the mapping at random and you'll either be recording the wrong channel or not record anything.
Thanks. I'll keep trying.

This is a new Sage install, and I haven't done any remapping at all. The channel or vchannel isn't anything that I intentionally set - it's just what sage tried to do when i attempted to tune the channel.

My steps were (from memory):

run HDHR Prime channel scan (via Prime web portal)
run console-only to generate a lineup file
add HDHR Prime (CC) as tuner in sage; download EPG data for cable package
run channel scan in Sage (is this step needed?)
Try to tune channel

I may have to blast this away and try again, but I'm hoping that there will be something else that I can look at to see what may be amiss.

thanks
Matt
__________________
Server: Ubuntu 16.04 running Sage for Linux v9
Reply With Quote
  #632  
Old 03-23-2016, 12:45 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,519
Quote:
Originally Posted by matt91 View Post
Thanks. I'll keep trying.

This is a new Sage install, and I haven't done any remapping at all. The channel or vchannel isn't anything that I intentionally set - it's just what sage tried to do when i attempted to tune the channel.

My steps were (from memory):

run HDHR Prime channel scan (via Prime web portal)
run console-only to generate a lineup file
add HDHR Prime (CC) as tuner in sage; download EPG data for cable package
run channel scan in Sage (is this step needed?)
Try to tune channel

I may have to blast this away and try again, but I'm hoping that there will be something else that I can look at to see what may be amiss.

thanks
Matt
Go to the Channel Setup for one of the tuners, then click on Edit Channel Lineup > Clear all Remapped Channels

I hope that helps. If it doesn't I can add support for the way SageTV is trying to tune the channel for you, but I'm concerned this might be a problem for you in the future due to the reason why vchannels are preferred.
__________________
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
  #633  
Old 03-23-2016, 12:55 PM
matt91's Avatar
matt91 matt91 is offline
Sage Icon
 
Join Date: Feb 2005
Location: Washington, DC
Posts: 1,185
Quote:
Originally Posted by EnterNoEscape View Post
Go to the Channel Setup for one of the tuners, then click on Edit Channel Lineup > Clear all Remapped Channels

I hope that helps. If it doesn't I can add support for the way SageTV is trying to tune the channel for you, but I'm concerned this might be a problem for you in the future due to the reason why vchannels are preferred.
OK, will try that tonight. I've had channels reassigned by Comcast before, so i'm happy to have vchannels instead. No way to force them, is there?
__________________
Server: Ubuntu 16.04 running Sage for Linux v9
Reply With Quote
  #634  
Old 03-23-2016, 01:38 PM
Greg2dot0's Avatar
Greg2dot0 Greg2dot0 is offline
Sage Advanced User
 
Join Date: Dec 2008
Posts: 82
Quote:
Originally Posted by EnterNoEscape View Post
I have FiOS myself and I haven't seen these particular problems, so we must just watch different shows. Anyhow, upgrade to RC2, I think it will fix the halts. It takes into account if FFmpeg returns any absurd values and also makes sure the gap between dts frames is not ridiculous.
Ok, have done a few recordings with 37 (RC2) and so far it seems to have resolved all the issues. I'll continue to do test recordings and monitor the logs.

I did pick up 1 new error which seems to be thrown as the recording is shutting down:

11:00:00.350 [FFmpegTransSageTVConsumerImpl-209CT-HDHomeRun Prime Tuner 13142E5A-2] INFO FFmpegContext - Returning AVERROR_EOF in readCallback.call()
__________________
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
  #635  
Old 03-23-2016, 02:01 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,519
Quote:
Originally Posted by Greg2dot0 View Post
Ok, have done a few recordings with 37 (RC2) and so far it seems to have resolved all the issues. I'll continue to do test recordings and monitor the logs.

I did pick up 1 new error which seems to be thrown as the recording is shutting down:

11:00:00.350 [FFmpegTransSageTVConsumerImpl-209CT-HDHomeRun Prime Tuner 13142E5A-2] INFO FFmpegContext - Returning AVERROR_EOF in readCallback.call()
That's not really an error even though it looks like one. It signals FFmpeg to stop reading and stops the whole recording process "gracefully." A key thing to look at is if it is preceded with WARN, ERROR or FATAL. If it says INFO or DEBUG, it is generally me saying it's expected and just here in case we need to track something down.
__________________
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
  #636  
Old 03-23-2016, 04:38 PM
matt91's Avatar
matt91 matt91 is offline
Sage Icon
 
Join Date: Feb 2005
Location: Washington, DC
Posts: 1,185
I think that I'm in business. I zero'd out everything (deleted OpenDCT configs, sage.properties, Wiz.bin) and restarted.

I think that the secret may have been to NOT run the channel scan in sage. I think doing that is what may have established the channel mappings that I was up against previously.

thanks for the help
__________________
Server: Ubuntu 16.04 running Sage for Linux v9
Reply With Quote
  #637  
Old 03-23-2016, 04:54 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,519
Quote:
Originally Posted by matt91 View Post
I think that I'm in business. I zero'd out everything (deleted OpenDCT configs, sage.properties, Wiz.bin) and restarted.

I think that the secret may have been to NOT run the channel scan in sage. I think doing that is what may have established the channel mappings that I was up against previously.

thanks for the help
No problem. The issue you ran into still perplexes me. I was unable to recreate it, but I'm going to blame it on SageTV since according to the logs OpenDCT wasn't telling SageTV that it could actually tune those channels in that format.
__________________
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
  #638  
Old 03-24-2016, 05:39 AM
Greg2dot0's Avatar
Greg2dot0 Greg2dot0 is offline
Sage Advanced User
 
Join Date: Dec 2008
Posts: 82
Ok, for some reason, 37 blew up on me yesterday afternoon during some recordings. Not sure what happened about about 4:48 I see hundreds of these:

Code:
16:48:25.844 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - [mpegts @ 0x7f234c00f740] Application provided invalid, non monotonically increasing dts to muxer in stream -1300655616: (null) >= (null)
16:48:25.845 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.847 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.853 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.897 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.904 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.910 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.957 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.969 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.974 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.974 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] INFO  ffmpeg - Last message repeated 8 times.
16:48:25.974 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] WARN  ffmpeg - [mpegts @ 0x7f234c155e00] PES packet size mismatch
16:48:26.022 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - [mpegts @ 0x7f234c00f740] Application provided invalid, non monotonically increasing dts to muxer in stream -1300655616: (null) >= (null)
16:48:26.022 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:26.028 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:26.030 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:26.034 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
I will continue to do more testing this AM to see if I can reproduce.
Attached Files
File Type: txt opendct-03-23-16.txt (12.6 KB, 34 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
  #639  
Old 03-24-2016, 06:30 AM
Greg2dot0's Avatar
Greg2dot0 Greg2dot0 is offline
Sage Advanced User
 
Join Date: Dec 2008
Posts: 82
I just wanted to post that I am able to reproduce this error as it happened several times this AM.
__________________
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-24-2016 at 08:07 AM.
Reply With Quote
  #640  
Old 03-24-2016, 09:55 AM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,519
Quote:
Originally Posted by Greg2dot0 View Post
Ok, for some reason, 37 blew up on me yesterday afternoon during some recordings. Not sure what happened about about 4:48 I see hundreds of these:

Code:
16:48:25.844 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - [mpegts @ 0x7f234c00f740] Application provided invalid, non monotonically increasing dts to muxer in stream -1300655616: (null) >= (null)
16:48:25.845 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.847 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.853 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.897 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.904 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.910 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.957 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.969 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.974 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:25.974 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] INFO  ffmpeg - Last message repeated 8 times.
16:48:25.974 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] WARN  ffmpeg - [mpegts @ 0x7f234c155e00] PES packet size mismatch
16:48:26.022 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR ffmpeg - [mpegts @ 0x7f234c00f740] Application provided invalid, non monotonically increasing dts to muxer in stream -1300655616: (null) >= (null)
16:48:26.022 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:26.028 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:26.030 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
16:48:26.034 [FFmpegTransSageTVConsumerImpl-1999:DCT-HDHomeRun Prime Tuner 13142E5A-2] ERROR FFmpegTranscoder - Error from av_interleaved_write_frame: -22
I will continue to do more testing this AM to see if I can reproduce.
The error means that the decode time stamps are not monotonic. Basically it's what we saw before, but since there's an assumption that if the difference between the current and the last time stamp was > 100000, that we must have wrapped around. Because the time stamps are actually not even in the right range to be doing that FFmpeg is freaking out and doesn't know how to remux them in order. The presentation time stamps must have moved backwards too since the code will keep progressing the decode time stamp so long as the presentation time stamp is greater than the last one.

I don't understand why FiOS would do such a crazy thing since that's not how the standard is supposed to work. I can make the muxer perpetually correct the decode and presentation time stamps to what they probably should be, but that doesn't feel like the right solution. The trouble with this approach is it's very easy to make a small mistake that will completely throw the video and audio out of sync. However I'm not sure there is any other way to fix it.

Have you noticed if it's just a particular channel and time? If you would like to switch to the raw consumer and capture the same problematic recording at the same time and just send me the whole recording I can probably get a better idea of what's really going on. Otherwise I can send you a very verbose copy of OpenDCT and you can send me the huge log files, but the video would be preferred since then I can manipulate things without you needing to keep testing.

Also, the log rotates at mid-night, when it reaches 20MB or when OpenDCT is restarted, so I didn't see anything of interest. Can you get me the logs under archive with recording date on them?
__________________
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
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 07:19 AM.


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