SageTV Community  

Go Back   SageTV Community > Hardware Support > Hardware Support
Forum Rules FAQs Community Downloads Today's Posts Search

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
  #1261  
Old 09-30-2016, 12:05 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
What version are you currently using?

Edit: I ask because these out of memory issues were addressed in a fairly recent version.
__________________
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; 09-30-2016 at 12:26 PM.
Reply With Quote
  #1262  
Old 09-30-2016, 01:15 PM
HokiePerogi HokiePerogi is offline
Sage Advanced User
 
Join Date: Oct 2008
Posts: 187
Quote:
Originally Posted by EnterNoEscape View Post
What version are you currently using?

Edit: I ask because these out of memory issues were addressed in a fairly recent version.
The logs in the zip file from last night's primetime were with 0.5.9, which I had installed around 7:50 PM ET.

Upgraded a few hours ago to 0.5.10 when I saw it was available.

I'm still seeing an OutOfMemory issue:

Code:
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.024 [NIORTPProducerImpl-4311:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  NIORTPProducerImpl - Producer thread has disconnected.
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.024 [NIORTPProducerImpl-4311:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  NIORTPProducerImpl - Producer thread has stopped.
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.024 [FFmpegTransSageTVConsumerImpl-4314:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.024 [FFmpegTransSageTVConsumerImpl-4314:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] WARN  mpegts - Repeated 2 times: [612f5ca0] Value -9223372036853775360.000000 for parameter 'analyzeduration' out of range [0 - 9.22337e+018].
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.024 [FFmpegTransSageTVConsumerImpl-4314:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] WARN  mpegts - [612f5720] PES packet size mismatch
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.025 [FFmpegTransSageTVConsumerImpl-4314:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  FFmpegTranscoder - FFmpeg transcoder ended with code 0
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.025 [FFmpegTransSageTVConsumerImpl-4314:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder consumer thread stopped.
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.025 [dct_infinitv-144-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVTuning - Stopping streaming from tuner number 4 at '192.168.200.1'.
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.025 [dct_infinitv-144-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVTuning - Connecting to InfiniTV tuner using the URL 'http://192.168.200.1/stream_request.cgi'
INFO   | jvm 1    | 2016/09/30 14:13:19.150 | 14:13:19.122 [dct_infinitv-144-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  OfflineChannelScan - Scanned channel 144 (Oxygen East). Signal strength is now '34', CCI is now 'COPY_FREELY' and tunable is now 'true'.
INFO   | jvm 1    | 2016/09/30 14:13:21.150 | 14:13:21.122 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  OfflineChannelScan - Scanning the channel '567' (Universal HDTV).
INFO   | jvm 1    | 2016/09/30 14:13:21.150 | 14:13:21.122 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVCaptureDevice - Starting a channel scan for the channel '567' from the device 'DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4'...
INFO   | jvm 1    | 2016/09/30 14:13:21.150 | 14:13:21.122 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVTuning - Connecting to InfiniTV tuner using the URL 'http://192.168.200.1/channel_request.cgi'
INFO   | jvm 1    | 2016/09/30 14:13:21.250 | 14:13:21.182 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVCaptureDevice - Configuring and starting the new RTP producer...
INFO   | jvm 1    | 2016/09/30 14:13:21.250 | 14:13:21.183 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVTuning - Starting streaming from tuner number 4 to local port '8356'.
INFO   | jvm 1    | 2016/09/30 14:13:21.250 | 14:13:21.183 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVTuning - Connecting to InfiniTV tuner using the URL 'http://192.168.200.1/stream_request.cgi'
INFO   | jvm 1    | 2016/09/30 14:13:21.250 | 14:13:21.183 [NIORTPProducerImpl-4332:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  NIORTPProducerImpl - Producer thread is running.
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 14:13:21.953 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVCaptureDevice - Configuring and starting the new SageTV consumer...
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 14:13:21.954 [FFmpegTransSageTVConsumerImpl-4335:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder consumer thread is now running.
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 14:13:22.029 [FFmpegTransSageTVConsumerImpl-4335:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] ERROR FFmpegContext - initTsStream: avformat_open_input returned error code -12
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 14:13:22.029 [FFmpegTransSageTVConsumerImpl-4335:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] ERROR FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder created an unexpected exception => java.lang.NullPointerException
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at opendct.video.ffmpeg.FFmpegContext.allocIoContext(FFmpegContext.java:914)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at opendct.video.ffmpeg.FFmpegContext.allocInputIoTsFormatContext(FFmpegContext.java:641)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at opendct.video.ffmpeg.FFmpegStreamDetection.detectStreams(FFmpegStreamDetection.java:96)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at opendct.video.ffmpeg.FFmpegContext.initTsStream(FFmpegContext.java:567)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at opendct.consumer.FFmpegTransSageTVConsumerImpl.run(FFmpegTransSageTVConsumerImpl.java:191)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at java.lang.Thread.run(Unknown Source)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 14:13:22.030 [FFmpegTransSageTVConsumerImpl-4335:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder consumer thread stopped.
INFO   | jvm 1    | 2016/09/30 14:13:23.360 | [GC pause (young) 98M->24M(128M), 0.0035052 secs]
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 14:13:28.139 [NIORTPProducerImpl-4321:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  NIORTPProducerImpl - Producer thread has disconnected.
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | Exception in thread "NIORTPProducerImpl-4321:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1" java.lang.OutOfMemoryError
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at sun.misc.Unsafe.allocateMemory(Native Method)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at java.nio.DirectByteBuffer.<init>(Unknown Source)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at java.nio.ByteBuffer.allocateDirect(Unknown Source)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at opendct.consumer.buffers.SeekableCircularBufferNIO.write(SeekableCircularBufferNIO.java:202)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at opendct.consumer.FFmpegTransSageTVConsumerImpl.write(FFmpegTransSageTVConsumerImpl.java:239)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at opendct.producer.NIORTPProducerImpl.run(NIORTPProducerImpl.java:203)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at java.lang.Thread.run(Unknown Source)
INFO   | jvm 1    | 2016/09/30 14:13:28.662 | 14:13:28.640 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:29.164 | 14:13:29.142 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:29.666 | 14:13:29.644 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:30.168 | 14:13:30.146 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:30.670 | 14:13:30.648 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:31.172 | 14:13:31.160 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:31.772 | 14:13:31.702 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
__________________
Server: AMD Phenom II X6 3.20 GHz ♠ 16 GB RAM (15.7 usable)
Capture: HDHomeRun PRIME ♠ Ceton InfiniTV 4 PCIe (Clear-QAM only)
Tuning: OpenDCT v0.5.20-RC2
Software: Windows 7 Ultimate 64-bit ♠ SageTV v9.0.12.504 ♠ Java 1.8.0_111
Clients: 4 x STX-HD300 ♠ 3 x STX-HD200 ♠ MacOS Placeshifter
Reply With Quote
  #1263  
Old 09-30-2016, 02:01 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by HokiePerogi View Post
The logs in the zip file from last night's primetime were with 0.5.9, which I had installed around 7:50 PM ET.

Upgraded a few hours ago to 0.5.10 when I saw it was available.

I'm still seeing an OutOfMemory issue:

Code:
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.024 [NIORTPProducerImpl-4311:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  NIORTPProducerImpl - Producer thread has disconnected.
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.024 [NIORTPProducerImpl-4311:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  NIORTPProducerImpl - Producer thread has stopped.
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.024 [FFmpegTransSageTVConsumerImpl-4314:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.024 [FFmpegTransSageTVConsumerImpl-4314:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] WARN  mpegts - Repeated 2 times: [612f5ca0] Value -9223372036853775360.000000 for parameter 'analyzeduration' out of range [0 - 9.22337e+018].
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.024 [FFmpegTransSageTVConsumerImpl-4314:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] WARN  mpegts - [612f5720] PES packet size mismatch
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.025 [FFmpegTransSageTVConsumerImpl-4314:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  FFmpegTranscoder - FFmpeg transcoder ended with code 0
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.025 [FFmpegTransSageTVConsumerImpl-4314:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder consumer thread stopped.
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.025 [dct_infinitv-144-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVTuning - Stopping streaming from tuner number 4 at '192.168.200.1'.
INFO   | jvm 1    | 2016/09/30 14:13:19.050 | 14:13:19.025 [dct_infinitv-144-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVTuning - Connecting to InfiniTV tuner using the URL 'http://192.168.200.1/stream_request.cgi'
INFO   | jvm 1    | 2016/09/30 14:13:19.150 | 14:13:19.122 [dct_infinitv-144-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  OfflineChannelScan - Scanned channel 144 (Oxygen East). Signal strength is now '34', CCI is now 'COPY_FREELY' and tunable is now 'true'.
INFO   | jvm 1    | 2016/09/30 14:13:21.150 | 14:13:21.122 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  OfflineChannelScan - Scanning the channel '567' (Universal HDTV).
INFO   | jvm 1    | 2016/09/30 14:13:21.150 | 14:13:21.122 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVCaptureDevice - Starting a channel scan for the channel '567' from the device 'DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4'...
INFO   | jvm 1    | 2016/09/30 14:13:21.150 | 14:13:21.122 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVTuning - Connecting to InfiniTV tuner using the URL 'http://192.168.200.1/channel_request.cgi'
INFO   | jvm 1    | 2016/09/30 14:13:21.250 | 14:13:21.182 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVCaptureDevice - Configuring and starting the new RTP producer...
INFO   | jvm 1    | 2016/09/30 14:13:21.250 | 14:13:21.183 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVTuning - Starting streaming from tuner number 4 to local port '8356'.
INFO   | jvm 1    | 2016/09/30 14:13:21.250 | 14:13:21.183 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVTuning - Connecting to InfiniTV tuner using the URL 'http://192.168.200.1/stream_request.cgi'
INFO   | jvm 1    | 2016/09/30 14:13:21.250 | 14:13:21.183 [NIORTPProducerImpl-4332:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  NIORTPProducerImpl - Producer thread is running.
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 14:13:21.953 [dct_infinitv-567-191:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  InfiniTVCaptureDevice - Configuring and starting the new SageTV consumer...
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 14:13:21.954 [FFmpegTransSageTVConsumerImpl-4335:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder consumer thread is now running.
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 14:13:22.029 [FFmpegTransSageTVConsumerImpl-4335:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] ERROR FFmpegContext - initTsStream: avformat_open_input returned error code -12
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 14:13:22.029 [FFmpegTransSageTVConsumerImpl-4335:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] ERROR FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder created an unexpected exception => java.lang.NullPointerException
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at opendct.video.ffmpeg.FFmpegContext.allocIoContext(FFmpegContext.java:914)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at opendct.video.ffmpeg.FFmpegContext.allocInputIoTsFormatContext(FFmpegContext.java:641)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at opendct.video.ffmpeg.FFmpegStreamDetection.detectStreams(FFmpegStreamDetection.java:96)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at opendct.video.ffmpeg.FFmpegContext.initTsStream(FFmpegContext.java:567)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at opendct.consumer.FFmpegTransSageTVConsumerImpl.run(FFmpegTransSageTVConsumerImpl.java:191)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 	at java.lang.Thread.run(Unknown Source)
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 
INFO   | jvm 1    | 2016/09/30 14:13:22.050 | 14:13:22.030 [FFmpegTransSageTVConsumerImpl-4335:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 4] INFO  FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder consumer thread stopped.
INFO   | jvm 1    | 2016/09/30 14:13:23.360 | [GC pause (young) 98M->24M(128M), 0.0035052 secs]
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 14:13:28.139 [NIORTPProducerImpl-4321:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  NIORTPProducerImpl - Producer thread has disconnected.
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | Exception in thread "NIORTPProducerImpl-4321:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1" java.lang.OutOfMemoryError
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at sun.misc.Unsafe.allocateMemory(Native Method)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at java.nio.DirectByteBuffer.<init>(Unknown Source)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at java.nio.ByteBuffer.allocateDirect(Unknown Source)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at opendct.consumer.buffers.SeekableCircularBufferNIO.write(SeekableCircularBufferNIO.java:202)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at opendct.consumer.FFmpegTransSageTVConsumerImpl.write(FFmpegTransSageTVConsumerImpl.java:239)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at opendct.producer.NIORTPProducerImpl.run(NIORTPProducerImpl.java:203)
INFO   | jvm 1    | 2016/09/30 14:13:28.160 | 	at java.lang.Thread.run(Unknown Source)
INFO   | jvm 1    | 2016/09/30 14:13:28.662 | 14:13:28.640 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:29.164 | 14:13:29.142 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:29.666 | 14:13:29.644 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:30.168 | 14:13:30.146 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:30.670 | 14:13:30.648 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:31.172 | 14:13:31.160 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
INFO   | jvm 1    | 2016/09/30 14:13:31.772 | 14:13:31.702 [FFmpegTransSageTVConsumerImpl-4324:DCT-Ceton InfiniTV PCIe (00-80-27-6c) Tuner 1] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
I can see your heap is currently 128MB and that's really small in reality. I have it set to be able to grow to 768MB max by default, so this situation you're having is a little confusing. It's worth noting that the direct buffers are allocated directly in RAM, so that doesn't give me the full picture of what's going on. How much ram is the wrapper.exe process using? And how much free ram do you have?
__________________
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
  #1264  
Old 09-30-2016, 02:20 PM
HokiePerogi HokiePerogi is offline
Sage Advanced User
 
Join Date: Oct 2008
Posts: 187
Quote:
Originally Posted by EnterNoEscape View Post
I can see your heap is currently 128MB and that's really small in reality. I have it set to be able to grow to 768MB max by default, so this situation you're having is a little confusing. It's worth noting that the direct buffers are allocated directly in RAM, so that doesn't give me the full picture of what's going on. How much ram is the wrapper.exe process using? And how much free ram do you have?
Well, it looked like OpenDC died, as the wrapper log hadn't recorded anything for about 2 hours. I reboot my server to start with a clean slate.

Currently, wrapper.exe is using 1,456K (private working set) as reported by Task Manager.

Task manager reports physical memory as following (MB):
  • Total: 7934
  • Cached: 3940
  • Available: 4464
  • Free: 557
__________________
Server: AMD Phenom II X6 3.20 GHz ♠ 16 GB RAM (15.7 usable)
Capture: HDHomeRun PRIME ♠ Ceton InfiniTV 4 PCIe (Clear-QAM only)
Tuning: OpenDCT v0.5.20-RC2
Software: Windows 7 Ultimate 64-bit ♠ SageTV v9.0.12.504 ♠ Java 1.8.0_111
Clients: 4 x STX-HD300 ♠ 3 x STX-HD200 ♠ MacOS Placeshifter
Reply With Quote
  #1265  
Old 09-30-2016, 02:33 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by HokiePerogi View Post
Well, it looked like OpenDC died, as the wrapper log hadn't recorded anything for about 2 hours. I reboot my server to start with a clean slate.

Currently, wrapper.exe is using 1,456K (private working set) as reported by Task Manager.

Task manager reports physical memory as following (MB):
  • Total: 7934
  • Cached: 3940
  • Available: 4464
  • Free: 557
That looks reasonable, but that's also right after a reboot if I'm reading what you're saying correctly. The only other possibility that I can think of is that the direct buffer can't allocate enough contiguous ram because it's heavily fragmented. I'll post a new version in a little bit here that will allow you to disable the direct allocation of the circular buffer which might help someone in your situation out.
__________________
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
  #1266  
Old 09-30-2016, 02:38 PM
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
I have no issues getting to work on this and the changes look fairly simple, but if we are going to push for 4.0, I would prefer that we collect more ideas about what we would like to add to the new version.

I do have a few concerns. This could get very confusing for people using pooling because the the device reported offline might not match up with the device that's actually offline. Also many users want SageTV to take over capture devices even if they are in use by another program as a last resort. If we are telling SageTV they aren't available and it creates a conflict, SageTV is not going to know the reason why a capture device is unavailable. For example, lets say the last available tuner is locked and all other tuners are already in use by SageTV. We would probably like it to force the use of the locked tuner only if it prevents a conflict, otherwise just reschedule that recording. Adding this kind of logic would probably require scheduler changes.
Yeah, with pooling I can see that as a bit of an issue. I have never used the pooling feature, so I'm not familiar with how you've got it implemented. How are the tuner 'slots' in the pool presented to Sage? Are they named as 'DCT_Pool 1', 'DCT_Pool 2', etc, or are they still the named tuners, but not necessarily referring to the actual same hardware if the pool needs to switch it up? If the former (they way I envision it 'should' be done), then if x drops in the pool are unavailable, then the highest x numbered CDI's would respond with whatever NOOP response we deem for an offline tuner. If OpenDCT is configured to force unlock an in-use tuner on a sage request, than it would still respond OK to sage if they are simply in use by something else, or offline if they are genuinely not there.

I was not envisioning this in the 'tuner used by something else scenario'. I've never seen a need to use my HDHR or Prime in anything but Sage.
__________________
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
  #1267  
Old 09-30-2016, 02:48 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
OpenDCT 0.5.11-Beta


  • Added longer timeouts for offline scanning when all of the capture devices are being used.
  • Added dynamic disabling of direct buffer allocation of the circular buffer when it appears to be causing issues. Direct allocation can also be turned off by changing the value of buffers.nio.direct=true to false.
  • Fixed the possibility of FFmpeg returning a negative duration.
  • Improved some of the FFmpeg logging rejection conditions.
__________________
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
  #1268  
Old 09-30-2016, 02:57 PM
HokiePerogi HokiePerogi is offline
Sage Advanced User
 
Join Date: Oct 2008
Posts: 187
Quote:
Originally Posted by EnterNoEscape View Post
That looks reasonable, but that's also right after a reboot if I'm reading what you're saying correctly. The only other possibility that I can think of is that the direct buffer can't allocate enough contiguous ram because it's heavily fragmented. I'll post a new version in a little bit here that will allow you to disable the direct allocation of the circular buffer which might help someone in your situation out.
That would be phenomenal. I've also gone ahead and dropped $100 on 4x 4GB RAM sticks to double the amount I have today. It should be here Sunday.
__________________
Server: AMD Phenom II X6 3.20 GHz ♠ 16 GB RAM (15.7 usable)
Capture: HDHomeRun PRIME ♠ Ceton InfiniTV 4 PCIe (Clear-QAM only)
Tuning: OpenDCT v0.5.20-RC2
Software: Windows 7 Ultimate 64-bit ♠ SageTV v9.0.12.504 ♠ Java 1.8.0_111
Clients: 4 x STX-HD300 ♠ 3 x STX-HD200 ♠ MacOS Placeshifter
Reply With Quote
  #1269  
Old 09-30-2016, 03:43 PM
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
Yeah, with pooling I can see that as a bit of an issue. I have never used the pooling feature, so I'm not familiar with how you've got it implemented. How are the tuner 'slots' in the pool presented to Sage? Are they named as 'DCT_Pool 1', 'DCT_Pool 2', etc, or are they still the named tuners, but not necessarily referring to the actual same hardware if the pool needs to switch it up? If the former (they way I envision it 'should' be done), then if x drops in the pool are unavailable, then the highest x numbered CDI's would respond with whatever NOOP response we deem for an offline tuner. If OpenDCT is configured to force unlock an in-use tuner on a sage request, than it would still respond OK to sage if they are simply in use by something else, or offline if they are genuinely not there.

I was not envisioning this in the 'tuner used by something else scenario'. I've never seen a need to use my HDHR or Prime in anything but Sage.
They are still named the original capture device names. I didn't want to make it a pain to transition between using pooling and not using pooling. Your first method would require users to at the very least, make the config change, then restart SageTV and redo all of their capture devices. For some users there would be a lot of confusion over what devices they should be using, others complaining about the extra capture devices and still more asking how to rename everything because they don't like the automated names. I thought about doing things that way and decided against it for those reasons. You can however rename all of your capture devices if you want to use the names you suggested and then they will show up in SageTV with those names.

There is a merit order to the pools on the OpenDCT side of things and the capture devices belong to pool groups. These groups are auto-generated and can be changed if needed. If any capture device present in the group is requested, the highest merit, non-locked device is mapped and used. If they are all locked, the highest merit locked device is used. If forced unlocking isn't enabled, the capture device will be mapped, but the tuning will of course fail.

I am following your suggestion, and I don't see any reason why it couldn't be implemented with the current topology. The pooled capture devices are maintained in lists in order of merit. We should be able to work with that to ensure that if we are short on available devices, we would only return the top-most capture devices less the number of offline devices as available. This is not all that different from using slots and has the same probability of SageTV using a capture device that suddenly is "offline." For example, let's say we have 3 capture devices named CD1, CD2 and CD3 that can be mapped to any of the 3 pool capture devices PD1, PD2 and PD3. SageTV starts a recording on PD3 which ends up mapping to CD1. During the recording, CD2 goes offline. Now we are telling SageTV that PD1 and PD2 are available and PD3 is offline. It's using PD3 and now thinks it's offline disrupting the recording. You can get around this with additional logic to keep already in use devices from being reported offline if they really are still online, but now you need to compensate when the pool is being checked to make sure you don't return more devices are available than could be used. You can see how this becomes a mess.

I don't use my hardware in any other software than SageTV either, but there are a number of users that do, so I tried to keep that on the table when these kinds of conversations come up.
__________________
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
  #1270  
Old 09-30-2016, 06:36 PM
jusjoken jusjoken is offline
SageTVaholic
 
Join Date: Dec 2005
Location: Strathmore, AB
Posts: 2,727
Quote:
Originally Posted by EnterNoEscape View Post
Keep in mind that if you're using Windows, you'll need to install VS2015 and set things up per the directions on the SageTV GitHub to be able to compile JavaRemuxer2.dll. Linux is a little easier. Just make sure if you're running Ubuntu that build-essential is installed and you should be able to make libJavaRemuxer2.so. This would be in addition to compiling a new Sage.jar. If you only compile a new Sage.jar, the new library will not be able to load and you will not be writing anything to disk. Eventually new install packages for Windows and Linux will be released, so if this looks daunting, I would just wait.
Took me quite a while but the latest installer (9.0.8.429 1.004 uploading right now) has this file included now

k
__________________
If you wish to see what I am up to and support my efforts visit my Patreon page
Reply With Quote
  #1271  
Old 09-30-2016, 06:42 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by jusjoken View Post
Took me quite a while but the latest installer (9.0.8.429 1.004 uploading right now) has this file included now

k
I'm just glad we have someone taking care of the Windows installer. We really needed 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
Reply With Quote
  #1272  
Old 09-30-2016, 07:35 PM
HokiePerogi HokiePerogi is offline
Sage Advanced User
 
Join Date: Oct 2008
Posts: 187
Quote:
Originally Posted by EnterNoEscape View Post

  • Added longer timeouts for offline scanning when all of the capture devices are being used.
  • Added dynamic disabling of direct buffer allocation of the circular buffer when it appears to be causing issues. Direct allocation can also be turned off by changing the value of buffers.nio.direct=true to false.
  • Fixed the possibility of FFmpeg returning a negative duration.
  • Improved some of the FFmpeg logging rejection conditions.
Well shoot. Unfortunately the buffers.nio.direct=false with 0.5.11 didn't seem to address my out of memory issues. My recordings failed again today during primetime. I've attached my zipped log files for OpenDCT 0.5.11 during today's primetime.

After noticing halts again on my extender, I checked the Task Manager and saw I had 0 physical memory free. This was after seeing 700-1000MB free at all times with nothing recording just after install 0.5.11

It seems that as soon as there are real recordings something sucks my memory to zero. The biggest memory hog seems to be java.exe *32. Wrapper seems to stay really low at around 1400K while java.exe *32 continually grows.
Attached Files
File Type: zip wrapper.log.zip (400.7 KB, 99 views)
File Type: zip opendct.log.zip (462.3 KB, 104 views)
__________________
Server: AMD Phenom II X6 3.20 GHz ♠ 16 GB RAM (15.7 usable)
Capture: HDHomeRun PRIME ♠ Ceton InfiniTV 4 PCIe (Clear-QAM only)
Tuning: OpenDCT v0.5.20-RC2
Software: Windows 7 Ultimate 64-bit ♠ SageTV v9.0.12.504 ♠ Java 1.8.0_111
Clients: 4 x STX-HD300 ♠ 3 x STX-HD200 ♠ MacOS Placeshifter
Reply With Quote
  #1273  
Old 09-30-2016, 07:35 PM
tmiranda's Avatar
tmiranda tmiranda is offline
SageTVaholic
 
Join Date: Jul 2005
Location: Central Florida, USA
Posts: 5,851
Quote:
Originally Posted by EnterNoEscape View Post
I'm just glad we have someone taking care of the Windows installer. We really needed that.
+1
__________________

Sage Server: 8th gen Intel based system w/32GB RAM running Ubuntu Linux, HDHomeRun Prime with cable card for recording. Runs headless. Accessed via RD when necessary. Four HD-300 Extenders.
Reply With Quote
  #1274  
Old 09-30-2016, 08:11 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by HokiePerogi View Post
Well shoot. Unfortunately the buffers.nio.direct=false with 0.5.11 didn't seem to address my out of memory issues. My recordings failed again today during primetime. I've attached my zipped log files for OpenDCT 0.5.11 during today's primetime.

After noticing halts again on my extender, I checked the Task Manager and saw I had 0 physical memory free. This was after seeing 700-1000MB free at all times with nothing recording just after install 0.5.11

It seems that as soon as there are real recordings something sucks my memory to zero. The biggest memory hog seems to be java.exe *32. Wrapper seems to stay really low at around 1400K while java.exe *32 continually grows.
Sorry, I led you in the wrong direction on what process to monitor. wrapper.exe loads java.exe, so that is of interest too. The reason that keeps on growing is because the circular buffer is overflowing and when it does that it tries to help you out by queuing up the data outside of the buffer to a limit. Once that limit is hit, data starts being discarded. The backup queue buffering is really only there to provide a little padding when there's a surge and really shouldn't be triggered that often outside of surges such as multiple recordings starting at the same time. On your machine, it's happening about every 5-20 seconds. This can be a good indicator that you are placing too much of a load on your hard drive or possibly it's having issues of it's own. Things like live Comskip can also contribute to performance issues.

One other thing I've noticed is that you have offline channel scanning enabled. This normally would not be a problem, but it's possible it's too much of a load on your machine when you are recording. Try turning that off too.
__________________
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
  #1275  
Old 09-30-2016, 08:43 PM
HokiePerogi HokiePerogi is offline
Sage Advanced User
 
Join Date: Oct 2008
Posts: 187
Quote:
Originally Posted by EnterNoEscape View Post
Sorry, I led you in the wrong direction on what process to monitor. wrapper.exe loads java.exe, so that is of interest too. The reason that keeps on growing is because the circular buffer is overflowing and when it does that it tries to help you out by queuing up the data outside of the buffer to a limit. Once that limit is hit, data starts being discarded. The backup queue buffering is really only there to provide a little padding when there's a surge and really shouldn't be triggered that often outside of surges such as multiple recordings starting at the same time. On your machine, it's happening about every 5-20 seconds. This can be a good indicator that you are placing too much of a load on your hard drive or possibly it's having issues of it's own. Things like live Comskip can also contribute to performance issues.

One other thing I've noticed is that you have offline channel scanning enabled. This normally would not be a problem, but it's possible it's too much of a load on your machine when you are recording. Try turning that off too.
I'll try disabling offline channel scanning for both the Ceton InfiniTV 4 and HDHomeRun.

I ran the SMART diagnostics on 2 of my 3 recording drives (each 1TB). SMART reports OK across all categories. My 3rd drive doesn't report any SMART data. I have SageTV set to balance equally across my three recording drives. Each one is only at 39% full at the moment.
__________________
Server: AMD Phenom II X6 3.20 GHz ♠ 16 GB RAM (15.7 usable)
Capture: HDHomeRun PRIME ♠ Ceton InfiniTV 4 PCIe (Clear-QAM only)
Tuning: OpenDCT v0.5.20-RC2
Software: Windows 7 Ultimate 64-bit ♠ SageTV v9.0.12.504 ♠ Java 1.8.0_111
Clients: 4 x STX-HD300 ♠ 3 x STX-HD200 ♠ MacOS Placeshifter
Reply With Quote
  #1276  
Old 09-30-2016, 09:18 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by HokiePerogi View Post
I'll try disabling offline channel scanning for both the Ceton InfiniTV 4 and HDHomeRun.

I ran the SMART diagnostics on 2 of my 3 recording drives (each 1TB). SMART reports OK across all categories. My 3rd drive doesn't report any SMART data. I have SageTV set to balance equally across my three recording drives. Each one is only at 39% full at the moment.
What does the CPU usage look like on java.exe while you're having problems with recordings?
__________________
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
  #1277  
Old 10-01-2016, 10:19 AM
uberpixel uberpixel is offline
Sage Advanced User
 
Join Date: Nov 2008
Posts: 238
Hmm...

Can't tune ESPN this morning. Discovery Network tunes fine. HDHomerun View tunes everything fine still.

Portland area Comcast. Anyone else have this problem?

No time to troubleshoot now - just wondering if anyone else is seeing this problem?

Any suggestions for troubleshooting?

-uberpixel
__________________
{Server} | i5-3330S | Z77X-UD5H | 8gb DDR3 | Windows 10 Pro |
{Tuners} | (1) HDHomerun (OTA) | (1) HDHomerun Prime + OpenDCT on Comcast |
{Client} | (2) HD300 Extenders | (1) PC Client | Mi Box Android Client | FireTV Stick |
Reply With Quote
  #1278  
Old 10-01-2016, 11:10 AM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by uberpixel View Post
Hmm...

Can't tune ESPN this morning. Discovery Network tunes fine. HDHomerun View tunes everything fine still.

Portland area Comcast. Anyone else have this problem?

No time to troubleshoot now - just wondering if anyone else is seeing this problem?

Any suggestions for troubleshooting?

-uberpixel
You could try rolling back to 0.5.8 to make sure it's not an issue related to the FFmpeg upgrade.
__________________
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
  #1279  
Old 10-01-2016, 01:09 PM
uberpixel uberpixel is offline
Sage Advanced User
 
Join Date: Nov 2008
Posts: 238
Quote:
Originally Posted by EnterNoEscape View Post
You could try rolling back to 0.5.8 to make sure it's not an issue related to the FFmpeg upgrade.
Well... Restarted my server and the HDHomerun Prime and it didn't help. Went and watched my daughter play soccer and now it's working again.

Weird.

-uberpixel
__________________
{Server} | i5-3330S | Z77X-UD5H | 8gb DDR3 | Windows 10 Pro |
{Tuners} | (1) HDHomerun (OTA) | (1) HDHomerun Prime + OpenDCT on Comcast |
{Client} | (2) HD300 Extenders | (1) PC Client | Mi Box Android Client | FireTV Stick |
Reply With Quote
  #1280  
Old 10-01-2016, 02:37 PM
Telecore's Avatar
Telecore Telecore is offline
Sage Aficionado
 
Join Date: Oct 2010
Location: Allen, TX
Posts: 347
I've been trying to keep up with the latest OpenDCT, probably upgraded 3x in the past few days - having a problem with the current beta tuning in a football game on ABC - all other channels seem to tune OK. Log attached.
__________________
SageTV-V9(64bit): Win10/i3-4370/OpenDCT/HDHR-Quatro (OTA)
AndroidTV+Miniclient: Nvidia Shield(x3)/FireTV-4K(x8)
Channels-DVR:Win10/i3-4340/HDHR Quatro 4K/TVE(YTTV)

Last edited by Telecore; 09-30-2017 at 09:34 AM.
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 2 (0 members and 2 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
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 08:46 PM.


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