SageTV Community  

Go Back   SageTV Community > SageTV Products > SageTV Linux > SageTV for unRAID/Docker
Forum Rules FAQs Community Downloads Today's Posts Search

Notices

SageTV for unRAID/Docker Discussion related to SageTV for unRAID/Docker. Questions, issues, problems, suggestions, etc. relating to SageTV for unRAID/Docker should be posted here.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 07-27-2017, 08:23 AM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
 
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
Network encoders missed show - delay to wait setting?

I'm starting to miss a couple shows due to perceived "Halt Decected in Recording"

On my old setup I had
Code:
mmc/encoders/xxxxx/delay_to_wait_after_tuning=10000
For most of my encoders.

But on my new setup with unraid it's set to 0.
I also see this in the opendct properties file.

Where do I modify this property? in the OpenDCT file? or in sage?

And have any of you had to bump this up from 0 for the prime tuners?

Thanks,

Jim
Reply With Quote
  #2  
Old 07-27-2017, 08:46 AM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by jbuszkie View Post
I'm starting to miss a couple shows due to perceived "Halt Decected in Recording"

On my old setup I had
Code:
mmc/encoders/xxxxx/delay_to_wait_after_tuning=10000
For most of my encoders.

But on my new setup with unraid it's set to 0.
I also see this in the opendct properties file.

Where do I modify this property? in the OpenDCT file? or in sage?

And have any of you had to bump this up from 0 for the prime tuners?

Thanks,

Jim
The value in the OpenDCT properties is passed to SageTV when the device is discovered, but I believe this only happens if it's new to SageTV. You will want to change the value on the SageTV side of things for it have any effect. I am however not certain that delays work on digital tuners.
__________________
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
  #3  
Old 07-27-2017, 08:50 AM
Fuzzy's Avatar
Fuzzy Fuzzy is offline
SageTVaholic
 
Join Date: Sep 2005
Location: Jurupa Valley, CA
Posts: 9,957
Quote:
Originally Posted by EnterNoEscape View Post
The value in the OpenDCT properties is passed to SageTV when the device is discovered, but I believe this only happens if it's new to SageTV. You will want to change the value on the SageTV side of things for it have any effect. I am however not certain that delays work on digital tuners.
Yes, this setting is only used on devices that have a separate tuning process (like using an IR blaster). It's the delay between sending the channel change, and actually asking the encoder to start recording.
__________________
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
  #4  
Old 07-27-2017, 09:06 AM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
 
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
Here is the OpentDCT log for a failing show.. Why it's so small and in the archive is beyond me..

Code:
00:01:26.656 [SageTVRequestHandler-2045:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'START DCT-HDHomeRun Prime Tuner 13115570-0 Digital TV Tuner|214079676|835|3002256173308|/var/media/tv/Suits-S07E03-Mudmare-40510755-0.ts|Great'
00:01:26.885 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG HDHRNativeCaptureDevice - Capture device is now re-locked.
00:01:26.885 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG SageTVRequestHandler - Starting network encoder via upload ID '214079676' to file name '/var/media/tv/Suits-S07E03-Mudmare-40510755-0.ts'.
00:01:26.885 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.92
00:01:27.022 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: '1062731234' lockKey: '1062731234' sendLength: 45 address: 192.168.2.92
00:01:27.022 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  HDHRNativeCaptureDevice - HDHomeRun is now locked.
00:01:27.022 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG RTPCaptureDeviceServices - Producer was not running.
00:01:27.022 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG BasicCaptureDevice - Consumer is not in progress.
00:01:27.023 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG DynamicConsumerImpl - Using default consumer 'opendct.consumer.MediaServerConsumerImpl' for channel '835'
00:01:27.023 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  HDHRNativeCaptureDevice - Starting the encoding for the channel '835' from the device 'DCT-HDHomeRun Prime Tuner 13115570-0' to the file '/var/media/tv/Suits-S07E03-Mudmare-40510755-0.ts' via the upload id '214079676'...
00:01:27.023 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.92
00:01:27.024 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'none' lockKey: '1062731234' sendLength: 39 address: 192.168.2.92
00:01:27.024 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.92
00:01:27.024 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  NIOHTTPProducerImpl - Connecting to source using the URL 'http://192.168.2.92:5004/tuner0/v835'
00:01:27.492 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG NIOHttpDownloader - HTTP response: 'HTTP/1.1 200 OK', 'Server: HDHomeRun/1.0', 'Connection: close', 'Content-Type: video/mpeg', 'Cache-Control: no-cache', 'Pragma: no-cache', 'transferMode.dlna.org: Streaming', 'Date: Thu, 27 Jul 2017 04:01:26 GMT', 
00:01:27.493 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG HDHomeRunControl - key: '/tuner0/program' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.92
00:01:27.493 [NIOHTTPProducerImpl-2055:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  NIOHTTPProducerImpl - Producer thread is running.
00:01:27.494 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  HDHRNativeCaptureDevice - Configuring and starting the new SageTV consumer...
00:01:27.494 [NIOHTTPProducerImpl-2055:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG NIOHTTPProducerImpl - Thread priority is 9.
00:01:27.494 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG BasicCaptureDevice - Consumer is not in progress.
00:01:27.495 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG HDHomeRunControl - key: '/tuner0/vstatus' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.92
00:01:27.495 [MediaServerConsumerImpl-2057:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  MediaServerConsumerImpl - MediaServer thread started.
00:01:27.496 [MediaServerConsumerImpl-2057:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG MediaServerConsumerImpl - Thread priority is 8.
00:01:27.496 [MediaServerConsumerImpl-2057:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  MediaServerConsumerImpl - Opening file via MediaServer...
00:01:27.496 [MediaServerConsumerImpl-2057:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  NIOSageTVMediaServer - Connecting to SageTV server on socket /192.168.2.30:7818...
00:01:27.497 [MediaServerConsumerImpl-2057:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  NIOSageTVMediaServer - Sending 'WRITEOPEN /var/media/tv/Suits-S07E03-Mudmare-40510755-0.ts 214079676' to SageTV server...
00:01:27.906 [MediaServerConsumerImpl-2057:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  MediaServerConsumerImpl - Setting up remuxing on MediaServer...
00:01:27.907 [MediaServerConsumerImpl-2057:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  NIOSageTVMediaServer - Sending 'REMUX_SETUP AUTO PS TRUE' to SageTV server...
00:01:27.913 [MediaServerConsumerImpl-2057:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  MediaServerConsumerImpl - Media Server consumer is now streaming...
00:01:28.538 [PowerMessageManagerShutdown] INFO  Main - Stopping power messages...
00:01:28.814 [SageTVManagerShutdown] INFO  Main - Stopping all SageTV socket servers...
00:01:28.814 [NanoHTTPDShutdown] INFO  Main - Stopping web server...
00:01:28.814 [DiscoveryManagerShutdown] INFO  Main - Stopping device discovery services...
00:01:28.814 [Shutdown] INFO  Main - OpenDCT has received a signal to stop.
00:01:28.814 [ChannelManagerShutdown] INFO  Main - Stopping all channel update threads...
00:01:28.815 [SageTVManagerShutdown] DEBUG SageTVSocketServer - Stopping listening thread...
00:01:28.814 [PowerMessageManagerShutdown] WARN  LinuxPowerMessagePump - System power state messages are currently not implemented for Linux.
00:01:28.815 [UPnPDiscovery-41] INFO  UpnpManager - UPnP discovery thread was interrupted => java.lang.InterruptedException: sleep interrupted
00:01:28.815 [SageTVTuningMonitor-67] INFO  SageTVTuningMonitor - Tuning monitor thread interrupted.
00:01:28.815 [NanoHTTPDShutdown] INFO  NanoHTTPDManager - Stopping webserver on port 9091...
00:01:28.815 [ChannelManagerShutdown] INFO  ChannelManager - Saving the channel lineup 'dct_hdhomerun'.
00:01:28.815 [Shutdown] INFO  Main - Saving current configuration...
00:01:28.816 [SageTVSocketServer-68:9000] INFO  SageTVSocketServer - Stopped listening on port 9000...
00:01:28.816 [SageTVManagerShutdown] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 131953B8-1' is being unloaded.
00:01:28.817 [SageTVManagerShutdown] DEBUG HDHRNativeCaptureDevice - Capture device is now re-locked.
00:01:28.817 [SageTVManagerShutdown] DEBUG RTPCaptureDeviceServices - Producer was not running.
00:01:28.817 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.71
00:01:28.823 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner1/target' value: 'none' lockKey: '0' sendLength: 32 address: 192.168.2.71
00:01:28.824 [SageTVManagerShutdown] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 131953B8-0' is being unloaded.
00:01:28.824 [SageTVManagerShutdown] DEBUG HDHRNativeCaptureDevice - Capture device is now re-locked.
00:01:28.824 [SageTVManagerShutdown] DEBUG RTPCaptureDeviceServices - Producer was not running.
00:01:28.824 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.71
00:01:28.824 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner0/target' value: 'none' lockKey: '0' sendLength: 32 address: 192.168.2.71
00:01:28.824 [SageTVManagerShutdown] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 131953B8-2' is being unloaded.
00:01:28.824 [SageTVManagerShutdown] DEBUG HDHRNativeCaptureDevice - Capture device is now re-locked.
00:01:28.824 [SageTVManagerShutdown] DEBUG RTPCaptureDeviceServices - Producer was not running.
00:01:28.824 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.71
00:01:28.824 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner2/target' value: 'none' lockKey: '0' sendLength: 32 address: 192.168.2.71
00:01:28.824 [SageTVManagerShutdown] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13115570-2' is being unloaded.
00:01:28.825 [SageTVManagerShutdown] DEBUG HDHRNativeCaptureDevice - Capture device is now re-locked.
00:01:28.825 [SageTVManagerShutdown] DEBUG RTPCaptureDeviceServices - Producer was not running.
00:01:28.825 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.92
00:01:28.825 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner2/target' value: 'none' lockKey: '0' sendLength: 32 address: 192.168.2.92
00:01:28.825 [SageTVManagerShutdown] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13115570-1' is being unloaded.
00:01:28.825 [SageTVManagerShutdown] DEBUG HDHRNativeCaptureDevice - Capture device is now re-locked.
00:01:28.825 [SageTVManagerShutdown] DEBUG RTPCaptureDeviceServices - Producer was not running.
00:01:28.825 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.92
00:01:28.825 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner1/target' value: 'none' lockKey: '0' sendLength: 32 address: 192.168.2.92
00:01:28.828 [SageTVManagerShutdown] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13115570-0' is being unloaded.
00:01:28.828 [SageTVManagerShutdown] INFO  HDHRNativeCaptureDevice - Capture device was already locked.
00:01:28.828 [SageTVManagerShutdown] DEBUG HTTPCaptureDeviceServices - Stopping producer thread...
00:01:28.828 [SageTVManagerShutdown] DEBUG HTTPCaptureDeviceServices - Waiting for producer thread to stop...
00:01:28.828 [NIOHTTPProducerImpl-2055:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG NIOHTTPProducerImpl - The socket has been closed.
00:01:28.828 [NIOHTTPProducerImpl-2055:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  NIOHTTPProducerImpl - Producer thread has stopped.
00:01:28.828 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.2.92
00:01:28.830 [SageTVManagerShutdown] DEBUG HDHomeRunControl - key: '/tuner0/target' value: 'none' lockKey: '0' sendLength: 32 address: 192.168.2.92
00:01:29.064 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG SageTVRequestHandler - Replied: 'OK'
00:01:29.064 [SageTVRequestHandler-2045:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG SageTVTuningMonitor - Tuning monitor is not running. This recording will not re-tune automatically.
00:01:29.148 [DiscoveryManagerShutdown] WARN  DiscoveryRegistryListener - Before UPnP shutdown, the registry did not contain any devices.
00:01:29.149 [DiscoveryManagerShutdown] DEBUG DiscoveryRegistryListener - Shutdown of UPnP registry complete.
00:01:29.149 [DiscoveryManagerShutdown] INFO  DiscoveryManager - UPnP discovery stopped.
00:01:29.149 [HDHomeRunDiscoveryReceive-42] DEBUG HDHomeRunDiscovery - Channel was closed while receiving HDHomeRun discovery packets from [/255.255.255.255:65001, /255.255.255.255:65001] => java.nio.channels.ClosedByInterruptException
	at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
	at sun.nio.ch.DatagramChannelImpl.receive(DatagramChannelImpl.java:378)
	at opendct.tuning.hdhomerun.HDHomeRunDiscovery$ReceiveThread.run(HDHomeRunDiscovery.java:364)
	at java.lang.Thread.run(Thread.java:745)

00:01:29.295 [HDHomeRunDiscoveryReceive-42] DEBUG HDHomeRunDiscovery - Channel was closed while receiving HDHomeRun discovery packets from [/255.255.255.255:65001, /255.255.255.255:65001] => java.nio.channels.ClosedByInterruptException
	at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
	at sun.nio.ch.DatagramChannelImpl.receive(DatagramChannelImpl.java:378)
	at opendct.tuning.hdhomerun.HDHomeRunDiscovery$ReceiveThread.run(HDHomeRunDiscovery.java:364)
	at java.lang.Thread.run(Thread.java:745)

00:01:29.295 [HDHomeRunDiscoverySend-42] DEBUG HDHomeRunDiscovery - Interrupted while waiting for next broadcast to be sent => java.lang.InterruptedException: sleep interrupted
	at java.lang.Thread.sleep(Native Method)
	at opendct.tuning.hdhomerun.HDHomeRunDiscovery.run(HDHomeRunDiscovery.java:307)
	at java.lang.Thread.run(Thread.java:745)

00:01:29.295 [DiscoveryManagerShutdown] INFO  DiscoveryManager - HDHomeRun discovery stopped.
00:01:29.295 [DiscoveryManagerShutdown] INFO  DiscoveryManager - Generic HTTP discovery stopped.
00:01:29.295 [DiscoveryManagerShutdown] INFO  DiscoveryManager - Generic Pipe discovery stopped.
It looks like it started just fine ..

Then a little later this:
Code:
00:01:28.828 [NIOHTTPProducerImpl-2055:DCT-HDHomeRun Prime Tuner 13115570-0] DEBUG NIOHTTPProducerImpl - The socket has been closed.
00:01:28.828 [NIOHTTPProducerImpl-2055:DCT-HDHomeRun Prime Tuner 13115570-0] INFO  NIOHTTPProducerImpl - Producer thread has stopped.
If it's not the encoder delay.. Then where else should I look?

Jim
Attached Files
File Type: txt opendct.2017-07-27-1.txt (12.8 KB, 164 views)
Reply With Quote
  #5  
Old 07-27-2017, 12:07 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Change the consumer to use FFmpeg. If things are set up the way I think they are for you, you should just need to change the following in opendct.properties:

Code:
consumer.dynamic.default=opendct.consumer.FFmpegTransSageTVConsumerImpl
__________________
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
  #6  
Old 07-27-2017, 12:31 PM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
 
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
I don't think I changed anything from the default.

Why would I want to send it through ffmpeg if I'm not (at the moment) transcoding anything on the fly?

Is there an issue with
Code:
consumer.dynamic.default=opendct.consumer.MediaServerConsumerImpl
Is everyone sending it through ffmpeg?
Reply With Quote
  #7  
Old 07-27-2017, 12:31 PM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
 
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
And thanks for the help so far!
Reply With Quote
  #8  
Old 07-27-2017, 01:06 PM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
 
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
ok.. I changed it with opendct shutdown and it got changed back!

this is what the log says..

Code:
15:01:42.601 [DynamicAsyncInit-22] INFO  DynamicConsumerImpl - Dynamic consumer default set to use opendct.consumer.MediaServerConsumerImpl
15:01:42.601 [DynamicAsyncInit-22] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.FFmpegTransSageTVConsumerImpl for []
15:01:42.601 [DynamicAsyncInit-22] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.MediaServerConsumerImpl for []
15:01:42.601 [DynamicAsyncInit-22] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.RawSageTVConsumerImpl for []
15:01:42.624 [WrapperSimpleAppMain] WARN  HDHomeRunDiscovery - Broadcast IP address was any local address. Using 255.255.255.255 instead.
15:01:42.624 [WrapperSimpleAppMain] WARN  HDHomeRunDiscovery - Broadcast IP address was any local address. Using 255.255.255.255 instead.
Why is it changing it back?

It physically changes it back to MediaServerConsumerImpl in the properties file.

Do I need to edit the opendct.properties.default file instead?
Reply With Quote
  #9  
Old 07-27-2017, 01:24 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by jbuszkie View Post
I don't think I changed anything from the default.

Why would I want to send it through ffmpeg if I'm not (at the moment) transcoding anything on the fly?

Is there an issue with
Code:
consumer.dynamic.default=opendct.consumer.MediaServerConsumerImpl
Is everyone sending it through ffmpeg?
You're not transcoding, but my bet is that the internal remuxer that SageTV uses is tripping up on these channels. The FFmpeg remuxer even if you're not transcoding tends to deal with these kinds of streams better.

Quote:
Originally Posted by jbuszkie View Post
ok.. I changed it with opendct shutdown and it got changed back!

this is what the log says..

Code:
15:01:42.601 [DynamicAsyncInit-22] INFO  DynamicConsumerImpl - Dynamic consumer default set to use opendct.consumer.MediaServerConsumerImpl
15:01:42.601 [DynamicAsyncInit-22] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.FFmpegTransSageTVConsumerImpl for []
15:01:42.601 [DynamicAsyncInit-22] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.MediaServerConsumerImpl for []
15:01:42.601 [DynamicAsyncInit-22] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.RawSageTVConsumerImpl for []
15:01:42.624 [WrapperSimpleAppMain] WARN  HDHomeRunDiscovery - Broadcast IP address was any local address. Using 255.255.255.255 instead.
15:01:42.624 [WrapperSimpleAppMain] WARN  HDHomeRunDiscovery - Broadcast IP address was any local address. Using 255.255.255.255 instead.
Why is it changing it back?

It physically changes it back to MediaServerConsumerImpl in the properties file.

Do I need to edit the opendct.properties.default file instead?
I was thinking that might happen. The OpenDCT Docker manipulates this value for you and the value it adds overrides your change. Until that is corrected in the Docker, I would just change all of the DynamicConsumerImpl for the devices to FFmpegTransSageTVConsumerImpl since I know it won't manipulate the per capture device settings.
__________________
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
  #10  
Old 07-27-2017, 01:49 PM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
 
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
Quote:
Originally Posted by EnterNoEscape View Post
You're not transcoding, but my bet is that the internal remuxer that SageTV uses is tripping up on these channels. The FFmpeg remuxer even if you're not transcoding tends to deal with these kinds of streams better.
It doesn't always happen.. I haven't had that many fail yet to get a pattern. I do know that I very infrequently got any of these on my win7 V7 server using the win DCT or whatever it was called. It's only after I switched to V9 on Unraid Docker did I see some of these failures.


Quote:
Originally Posted by EnterNoEscape View Post
I was thinking that might happen. The OpenDCT Docker manipulates this value for you and the value it adds overrides your change. Until that is corrected in the Docker, I would just change all of the DynamicConsumerImpl for the devices to FFmpegTransSageTVConsumerImpl since I know it won't manipulate the per capture device settings.
Ok.. I changed all of them and now it seems to be using ffmpeg. It didn't break anything, at least. Time will tell if it's better.

Thanks,

Jim
Reply With Quote
  #11  
Old 03-18-2018, 06:24 PM
Deacon Crusher Deacon Crusher is offline
Sage Expert
 
Join Date: Aug 2004
Location: Berkeley, CA
Posts: 504
Did that fix things for you?

I'm starting to have some issues like this as well.

Thanks
__________________
Server: PhenomII X4 810, 16GB, 4850, C: 256GB Samsung SSD, D: HGST 3TB, E: HGST 4TB, H: 3T Seagate, 1.5 TB on NAS via UNC, Win 10 x64,
Sage 9 Cable provider is Comcast, Schedules Direct
Tuners: 4 ATSC - 2 seperate HD Homeruns all via Channel Master CM2016 on roof, 6 cable via 2 hdhomerun primes (opendct), 1 HD-PVR (in tuner priority order)
Clients: Wired: HD300, HD200, HD200 running Squeeze Slave, Placeshifters, HD200 (via wireless N bridge)
Reply With Quote
  #12  
Old 03-19-2018, 07:01 AM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
 
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
Yes.. I don't have those issues anymore!

Now I'm dealing with the Network encoder just stopping! It happened twice this past weekend. I did a full reboot of everything and hopefully that will fix it..

But yes, using FFMPEG seems to have fixed the halts.

Jim
Reply With Quote
Reply


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

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
Is there a setting for more than 10 encoders? BarkOLounger SageTV Software 8 05-19-2016 04:59 PM
Suggestions required regarding Network Encoders / Network Streams Jabroni SageTV v7 Customizations 2 03-27-2015 12:13 PM
Missed Part Of A Show: Want To Catch It Again If It Ever Airs Again? PeteCress SageTV Software 2 06-08-2009 08:07 PM
Loading Preview. Please wait, and wait and wait... dshields Hardware Support 7 05-10-2006 09:55 PM
Missed show 3 times DynamoBen SageTV Beta Test Software 9 03-27-2004 10:30 PM


All times are GMT -6. The time now is 05:21 PM.


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