SageTV Community  

Go Back   SageTV Community > Hardware Support > Hardware Support
Reload this Page OpenDCT: An open source digital cable tuner.
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
Page 113 of 148 « First 1363103111112 113 114115123 Last »
 
Thread Tools Search this Thread Display Modes
  #2241  
Old 01-02-2018, 03:27 PM
Telecore's Avatar
Telecore Telecore is offline
Sage Aficionado
  
Join Date: Oct 2010
Location: Allen, TX
Posts: 347
Quote:
Originally Posted by mwittl View Post
My entire network is gigabit, end-to-end.




No idea of the CPU usage when it's recording. Most of our recordings occur after I go to bed!

Storage consists of several multi-terabyte disks, one is internal to the Sage box and one connected via USB 3.0

I double checked my Video Recording Path Optimization Style setting and it's already set to BANDWIDTH.

Any other thoughts or things for me to check?
Are you running Windows? If so, check your network adapter settings. Turn interrupt moderation OFF. Maximize the # of transmit and receive buffers. Enable all "Offload" type features.

I used to run two HDHR primes and would get occasional pixelation when recording 3+ shows but when I switched to a Ceton PCIe6 the problem went away. Changing network settings improved the issue with the HDHRs. Also, 2 HDDs should be fine recording 3 shows each.
__________________
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)
Reply With Quote
  #2242  
Old 01-02-2018, 05:57 PM
KryptoNyte's Avatar
KryptoNyte KryptoNyte is offline
SageTVaholic
  
Join Date: Dec 2006
Posts: 2,754
I currently have one SageTV server that records 6 simultaneous streams (3 from each of two HDHR Primes) to one hard drive without issue. This system has done this with both a 3TB WD Green drive and a Seagate 3TB Barricuda 7200 rpm drive. This is with TV shows that are 8 mbits/second to 15 mbits/second. This system is not using the on board network, but an Intel Nic (the common $30 desktop nic).

I'm always surprised when folks find the single hard drive as the source of a problem. In any case, it doesn't seem to be the problem here.
Reply With Quote
  #2243  
Old 01-02-2018, 06:29 PM
waylo waylo is offline
Sage Advanced User
  
Join Date: Feb 2006
Posts: 238
Quote:
Originally Posted by KryptoNyte View Post
I currently have one SageTV server that records 6 simultaneous streams (3 from each of two HDHR Primes) to one hard drive without issue. This system has done this with both a 3TB WD Green drive and a Seagate 3TB Barricuda 7200 rpm drive. This is with TV shows that are 8 mbits/second to 15 mbits/second. This system is not using the on board network, but an Intel Nic (the common $30 desktop nic).

I'm always surprised when folks find the single hard drive as the source of a problem. In any case, it doesn't seem to be the problem here.
I'm definitely impressed with that. Wouldn't the HD head be going crazy with those 6 separate write commands? Maybe my older system just can't keep up.

As I recall, the Barricuda are among the faster HDs? Though the WD Greens are definitely not fast.
__________________

Server: SageTV 9.2.6x64 on Win10 x64 Home, i7-2600, 8gb RAM, OpenDCT, Java 1.8, 20TB storage
Display: EVGA GT 1030 fanless to Sony LED TV via DVI-HDMI
Capture Devices: HDHR Prime for Comcast, HDHR Dual for OTA (retired)
Clients: Nvidia Shield Android miniclient
Reply With Quote
  #2244  
Old 01-02-2018, 06:43 PM
KryptoNyte's Avatar
KryptoNyte KryptoNyte is offline
SageTVaholic
  
Join Date: Dec 2006
Posts: 2,754
Quote:
Originally Posted by waylo View Post
I'm definitely impressed with that. Wouldn't the HD head be going crazy with those 6 separate write commands? Maybe my older system just can't keep up.

As I recall, the Barricuda are among the faster HDs? Though the WD Greens are definitely not fast.
I don't claim to fully understand the underlying technology of the data transfer here, so bear with me. The system is a Core i5 4670K in a Gigabyte B85M-DS3H motherboard with 8GB of RAM. What little I do know is that I can transfer large files to these hard drives at about 100 megabytes per second - so 800 megabits per second. It doesn't seem like much of a reach to think that it could pull off 6 x 15 = 90 megabits per second. On the other hand, from my early SSD experiences from back in 2008, I know that small file writes are slower ... what would be the correct math to determine if this is really a problem or not?

I will admit, I did the upgrade [from the WD Green] to the Seagate drive a bit ago when Silicondust was having a problem with their Prime tuners, and subsequently [finally] released a firmware that properly addressed it.
Reply With Quote
  #2245  
Old 01-02-2018, 06:47 PM
KryptoNyte's Avatar
KryptoNyte KryptoNyte is offline
SageTVaholic
  
Join Date: Dec 2006
Posts: 2,754
Would it be accurate to simply copy/paste (6) large files from the Seagate back to the WD Green drive simultaneously, and then divide the amount of data moved by the time it took to do it? Both drives are still in the system.
Reply With Quote
  #2246  
Old 01-02-2018, 08:55 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
  
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by mwittl View Post
Storage consists of several multi-terabyte disks, one is internal to the Sage box and one connected via USB 3.0

I double checked my Video Recording Path Optimization Style setting and it's already set to BANDWIDTH.

Any other thoughts or things for me to check?
I'm skeptical that USB 3.0 is handling the simultaneous streams well. It works much like USB 2.0 (just a lot more bandwidth) and it doesn't do well with with random writing in my experience. I believe there's some newer way via a special driver to work with USB 3.0 that handles random writes a lot better, but I can't recall what is it at the moment and a quick Google isn't getting me there. Have you tried removing the 3.0 drive from the mix temporarily?
__________________
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
  #2247  
Old 01-02-2018, 09:07 PM
waylo waylo is offline
Sage Advanced User
  
Join Date: Feb 2006
Posts: 238
Quote:
Originally Posted by KryptoNyte View Post
Would it be accurate to simply copy/paste (6) large files from the Seagate back to the WD Green drive simultaneously, and then divide the amount of data moved by the time it took to do it? Both drives are still in the system.
I agree that the raw writing bitrate is probably not an issue, but with only 2 read/write heads per HD platter, there must be a bit of optimization to get those separate data streams written efficiently. Also those heads are not moving independently, as all heads for all platters are connected at the pivot point. (This is from my quick perusal of how current HDs work. To be revised when Seagate comes out with their Multi Actuator technology https://blog.seagate.com/enterprises...-breakthrough/ )

I think if you were to drag/drop those 6 large files in quick succession, that might approximate the throughput of several data streams simultaneously being written.
__________________

Server: SageTV 9.2.6x64 on Win10 x64 Home, i7-2600, 8gb RAM, OpenDCT, Java 1.8, 20TB storage
Display: EVGA GT 1030 fanless to Sony LED TV via DVI-HDMI
Capture Devices: HDHR Prime for Comcast, HDHR Dual for OTA (retired)
Clients: Nvidia Shield Android miniclient
Last edited by waylo; 01-02-2018 at 09:10 PM.
Reply With Quote
  #2248  
Old 01-03-2018, 08:30 AM
Taddeusz Taddeusz is offline
SageTVaholic
  
Join Date: Nov 2004
Location: Yukon, OK
Posts: 3,919
Quote:
Originally Posted by EnterNoEscape View Post
I'm skeptical that USB 3.0 is handling the simultaneous streams well. It works much like USB 2.0 (just a lot more bandwidth) and it doesn't do well with with random writing in my experience. I believe there's some newer way via a special driver to work with USB 3.0 that handles random writes a lot better, but I can't recall what is it at the moment and a quick Google isn't getting me there. Have you tried removing the 3.0 drive from the mix temporarily?
You want to make sure any external USB device supports UASP. In short, it's SCSI over USB rather than the old default USB mass storage.

https://en.wikipedia.org/wiki/USB_Attached_SCSI
__________________
Server: i5 8400, ASUS Prime H370M-Plus/CSM, 16GB RAM, 15TB drive array + 500GB cache, 2 HDHR's, SageTV 9, unRAID 6.6.3
Client 1: HD300 (latest FW), HDMI to an Insignia 65" 1080p LCD and optical SPDIF to a Sony Receiver
Client 2: HD200 (latest FW), HDMI to an Insignia NS-LCD42HD-09 1080p LCD
Reply With Quote
  #2249  
Old 01-03-2018, 11:57 PM
peternm22 peternm22 is offline
Sage Expert
  
Join Date: Jan 2005
Posts: 709
Windows Defender on my Windows 10 system is going crazy right now, it keeps picking up files along the lines of: C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Temp\javacpp11362760879\jniavcodec.dll

This folder appears to be files related to ffmpeg. The only things on my system using ffmpeg are SageTV and OpenDCT. Is this just a false positive?

I cleaned out all of the files in that folder, but every time Windows is restarted a similar javacpp######## folder is created with all of the dll files again. Are these files created by either SageTV or OpenDCT?

I sent some of the DLL's to Virus Total, and they all come up clean. Malware bytes didn't pick up anything either.

Pulling my hair our right now.
Reply With Quote
  #2250  
Old 01-04-2018, 12:04 AM
peternm22 peternm22 is offline
Sage Expert
  
Join Date: Jan 2005
Posts: 709
I think it is OpenDCT creating these files.

I disabled the OpenDCT service and deleted all of these files (again). I restarted the computer, and the files weren't created.

I manually restarted the OpenDCT service and the files appeared almost instantly, and Windows Defender started complaining again.

Looks like it must be a false positive from Windows Defender. A super annoying one at that...

Has anyone else encountered this tonight?
Reply With Quote
  #2251  
Old 01-04-2018, 08:58 PM
waylo waylo is offline
Sage Advanced User
  
Join Date: Feb 2006
Posts: 238
I had an issue earlier with Bitdefender and had to set OpenDCT as an exception. This occurred in late August. So maybe the false-positive virus definitions are finally catching onto Windows Defender.
__________________

Server: SageTV 9.2.6x64 on Win10 x64 Home, i7-2600, 8gb RAM, OpenDCT, Java 1.8, 20TB storage
Display: EVGA GT 1030 fanless to Sony LED TV via DVI-HDMI
Capture Devices: HDHR Prime for Comcast, HDHR Dual for OTA (retired)
Clients: Nvidia Shield Android miniclient
Reply With Quote
  #2252  
Old 01-04-2018, 09:22 PM
peternm22 peternm22 is offline
Sage Expert
  
Join Date: Jan 2005
Posts: 709
Looks like it was a false positive. There were a posts on Reddit with people getting the same trojan detected with a variety of software.
Reply With Quote
  #2253  
Old 01-07-2018, 08:53 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
  
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by Taddeusz View Post
You want to make sure any external USB device supports UASP. In short, it's SCSI over USB rather than the old default USB mass storage.

https://en.wikipedia.org/wiki/USB_Attached_SCSI
Thanks for adding that. I'm fairly certain that's what I was thinking of.
__________________
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
  #2254  
Old 01-09-2018, 10:23 AM
nyplayer nyplayer is offline
SageTVaholic
  
Join Date: Sep 2005
Posts: 4,997
Question about Tuner Merits ?
I pool all my tuners using OpenDCT ... but I noticed you can set merits in SageTV and OpenDCT ... what I would like to know is which one takes precedence when using tuner pooling ? SageTV or OpenDCT merits ?
__________________
Channels DVR UBUNTU Server 2 Primes 3 Connects TVE SageTV Docker with input from Channels DVR XMLTV and M3U VIA Opendct.
Reply With Quote
  #2255  
Old 01-09-2018, 09:08 PM
technazz's Avatar
technazz technazz is offline
Sage Aficionado
  
Join Date: Jul 2004
Location: Hamilton, ON, CA
Posts: 499
Generic Http
I've been using the Generic Http capture from an IPTV source for about 1.5 years without any issues. Recently the source has changed something in the stream that causes recording issues. The same stream plays perfectly from VLC . Attached is logs and config. I've tried to change the consumer to FFMPEG from the raw as well.

I can provide a clip if needed.

I captured the stream withFFMPEG and it played in Sage Fine.

ffmpeg.exe -y -i http://StreamURL.ts -c:v copy -c:a copy -t 00:00:30 myrecording.ts

** EDIT here is more log info for FFMPEG **

Code:
NFO   | jvm 1    | 2018/01/10 07:45:10.925 | 07:45:10.830 [SageTVRequestHandler-61:IPTV1] INFO  GenericHttpCaptureDevice - Configuring and starting the new SageTV consumer...
INFO   | jvm 1    | 2018/01/10 07:45:10.925 | 07:45:10.830 [NIOHTTPProducerImpl-91:IPTV1] INFO  NIOHTTPProducerImpl - Producer thread is running.
INFO   | jvm 1    | 2018/01/10 07:45:10.925 | 07:45:10.835 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder consumer thread is now running.
INFO   | jvm 1    | 2018/01/10 07:45:10.925 | 07:45:10.913 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - Before avformat_find_stream_info() pos=40030 bytes_read=40030 seek_count=0. probesize: 165628 analyzeduration: 2000000.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.125 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - After avformat_find_stream_info() pos=0 bytes_read=503090 seek_count=1. probesize: 165628 analyzeduration: 2000000.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.125 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - current container duration = 1.277333 seconds
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.130 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - Could not find a video stream. Trying again with an extended probe.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.131 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - Before avformat_find_stream_info() pos=462144 bytes_read=462144 seek_count=0. probesize: 639058 analyzeduration: 2277333.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.155 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR h264 - [41805340] cabac decode of qscale diff failed at 25 16
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.155 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR h264 - [41805340] error while decoding MB 25 16, bytestream 15953
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.209 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - After avformat_find_stream_info() pos=0 bytes_read=1097606 seek_count=1. probesize: 639058 analyzeduration: 2277333.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.209 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - current container duration = 2.797333 seconds
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.212 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - Primary program has been detected: 1.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.212 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegTranscoder - Initializing FFmpeg transcoder stream output.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.219 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegContext - Primary: 
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | Input #0, mpegts, from 'input-mpeg-ts.ts':
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |   Duration: 00:00:02.80, start: 43120.064000, bitrate: 3139 kb/s
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |   Program 1
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |     Metadata:
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |       service_name    : Service01
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |       service_provider: FFmpeg
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |     Stream #0:0[0x100], 39, 1/90000: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 704x576 [SAR 16:11 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |     Stream #0:1[0x101](eng), 73, 1/90000: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 196 kb/s
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.222 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegContext - Primary: 
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | Output #0, mpegts, to 'M:\M Recordings\CelebrityBigBrother-Live-17242906-0.ts':
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |     Stream #0:0, 0, 1/90000: Video: h264, yuv420p, 704x576 [SAR 16:11 DAR 16:9], q=2-31, 90k tbn, 50 tbc
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |     Stream #0:1(eng), 0, 1/90000: Audio: aac, 48000 Hz, stereo, fltp, 196 kb/s
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.223 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegTranscoder - Initialized FFmpeg transcoder stream output.
INFO   | jvm 1    | 2018/01/10 07:45:11.325 | 07:45:11.260 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
INFO   | jvm 1    | 2018/01/10 07:45:11.325 | 07:45:11.260 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
INFO   | jvm 1    | 2018/01/10 07:45:11.625 | 07:45:11.559 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 3 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
INFO   | jvm 1    | 2018/01/10 07:45:11.625 | 07:45:11.559 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
INFO   | jvm 1    | 2018/01/10 07:45:11.625 | 07:45:11.559 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing


7:51:55.109 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - sync offsets [-3880944000, -3880944000] to -3880944000, diff = 0, attempts = 5
07:51:56.273 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:51:56.274 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 37749120 == last dts 37749120, pts 37749120, last pts 37749120
07:51:57.179 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 37839360 == last dts 37839360, pts 37839360, last pts 37839360
07:51:59.251 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 37969920 == last dts 37969920, pts 37969920, last pts 37969920
07:52:04.185 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 38453760 == last dts 38453760, pts 38453760, last pts 38453760
07:52:07.187 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 7 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:07.188 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:07.188 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:16.400 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 39548160 == last dts 39548160, pts 39548160, last pts 39548160
07:52:20.202 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 39815040 == last dts 39815040, pts 39815040, last pts 39815040
07:52:24.280 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 2 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:24.280 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:24.280 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:24.352 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 2 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:24.352 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:24.352 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:27.298 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 1 time: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:27.298 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:27.298 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:32.482 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 41032320 == last dts 41032320, pts 41032320, last pts 41032320
07:52:34.368 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 41243520 == last dts 41243520, pts 41243520, last pts 41243520
07:52:40.282 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 41758080 == last dts 41758080, pts 41758080, last pts 41758080
07:52:45.162 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 10 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:45.162 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:45.162 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:48.370 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 161127883, readIndex = 3892754
07:52:48.370 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 161127883, readIndex = 3841483, returnValue = 161127883
07:52:53.361 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 4 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:53.361 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:55.233 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - Repeated 1 time: [41804de0] PES packet size mismatch.
07:52:55.233 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:55.233 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 43104000 == last dts 43104000, pts 43104000, last pts 43104000
07:53:00.377 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 1 time: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:53:00.377 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:53:00.441 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:53:01.165 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 43585920 == last dts 43585920, pts 43585920, last pts 43585920
07:53:01.255 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 165616797, readIndex = 662638
07:53:01.255 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 165616797, readIndex = 466077, returnValue = 165616797
07:53:03.211 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 2 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:53:03.212 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:53:03.212 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:53:05.299 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 43977600 == last dts 43977600, pts 43977600, last pts 43977600
07:53:23.252 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 45582720 == last dts 45582720, pts 45582720, last pts 45582720
07:53:25.324 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 173692498, readIndex = 923134
07:53:25.324 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 173692498, readIndex = 677458, returnValue = 173692498
07:53:27.238 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 4 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:53:27.239 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:53:27.239 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
Thanks

Chris
Attached Files
File Type: zip open dct logs.zip (13.1 KB, 124 views)
__________________
SageTV V9.xx 2 x HD300's, 2 x Nvidia Shields Running Mini Client
Last edited by technazz; 01-10-2018 at 07:36 AM. Reason: Added Extra Info
Reply With Quote
  #2256  
Old 01-10-2018, 12:39 PM
jgsouthard jgsouthard is offline
Sage Advanced User
  
Join Date: Jul 2004
Posts: 143
Quote:
Originally Posted by mwittl View Post
My wife will often try to record 5 shows at a single time period, however, after using OpenDCT on a pretty beefy machine along with 2 HDHR Primes dedicated to our SageTV box, one of the 5 recordings will always get screwy (artifacts, blocking, pixilation, dead spots) when trying to record anything more than 4 shows. I'm trying to see what the limitation is on this, or if there is a setting I can tweek in the profile for OpenDCT to improve the number of simultaneous recordings? Using standard settings right now.
KryptoNyte has already responded regarding his setup (2 X HDHR Primes = 6 Tuners). I have the same setup, all recording to one WD Black internal hard drive. I've tested it with 6 recordings at once without problems, although I typically don't record more than 3 to 4 at a time in normal use.

But I'm commenting because early on I had major battles with the same issues mwittl is seeing - blocking, pixelation, etc. I had issues with packet loss on my Gb motherboard NIC, and ended up having to use a discrete Intel NIC as KryptoNyte did. In mwittl's case, I'd also suspect the USB interface as a possible place for packets to be getting dropped.

My strong recommendation would be to run the network packet loss test provided by SiliconDust (https://forum.silicondust.com/forum/...pic.php?t=5877). Here are the basic instructions:

Low level test for network packet loss - CONNECT/EXTEND/PRIME/EXPAND:

From a cmd prompt run:
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF set /tuner0/vchannel <channel number>
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF save /tuner0 null

Replace "<channel number>" with one of your HD channels. For HDHomeRun PRIME, make sure that it is a non-DRM channel.

If you have more than one HDHomeRun unit then replace "FFFFFFFF" with the device ID of the desired unit.

You should see a series of dots. "n" indicates network packet loss. "t" indicates a reception error. "s" is informational.


If you see ANY packet loss errors then you are going to get pixelation or artifacts in your recordings, so your goal should be to run that test without any errors.

Unfortunately, that packet loss test only tests the stream from the tuners to your computer (i.e. cables, NIC, and any switches in the path), not all the way to the hard drives. So you may need to search elsewhere for similar testing that could be done on streams to the USB external drive to see if you are getting packet loss on those transfers (I suspect that you are).
__________________

Windows 10 Home 64-bit, i5-2500K, 8GB RAM, 2TB and 4TB SATA HDD's
SageTV v9.1.2.662, SageTV7.xml STV, Java v1.8.0_121
Server operating headless with 3 HD300 extenders as clients
Two HDHomeRun Primes (6 tuners) with 20170512beta1 firmware
Comcast cable TV, two cablecards in HDHRP's
OpenDCT 0.5.28 network encoder
Reply With Quote
  #2257  
Old 01-10-2018, 06:10 PM
KeithAbbott KeithAbbott is offline
Sage Icon
  
Join Date: Oct 2009
Location: Southeastern Michigan
Posts: 1,375
HDHomeRun Prime 6 Support?
EnterNoEscape, when the HDHomeRun Prime 6 becomes available this summer, will any changes be necessary to OpenDCT to use all six tuners in Sage?
__________________
Server: MSI Z270 SLI Plus ATX Motherboard, Intel i7-7700T CPU, 32GB Memory, Unraid 6.11.5, sagetvopen-sagetv-server-opendct-java11 Docker (version 2.0.7)
Tuners: 2 x SiliconDust HDHomeRun Prime Cable TV Tuners, SiliconDust HDHomeRun CONNECT 4K OTA Tuner
Clients: Multiple HD300 Extenders, Multiple Fire TV Stick 4K Max w/MiniClient
Miscellaneous: Multiple Sony RM-VLZ620 Universal Remote Controls
Reply With Quote
  #2258  
Old 01-12-2018, 08:16 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
  
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by nyplayer View Post
I pool all my tuners using OpenDCT ... but I noticed you can set merits in SageTV and OpenDCT ... what I would like to know is which one takes precedence when using tuner pooling ? SageTV or OpenDCT merits ?
The OpenDCT merits. However the merits in SageTV will determine what pool OpenDCT pulls from, but after that the OpenDCT merits take precedence.

Quote:
Originally Posted by KeithAbbott View Post
EnterNoEscape, when the HDHomeRun Prime 6 becomes available this summer, will any changes be necessary to OpenDCT to use all six tuners in Sage?
Probably not.
__________________
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
  #2259  
Old 01-12-2018, 08:27 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
  
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,657
Quote:
Originally Posted by technazz View Post
I've been using the Generic Http capture from an IPTV source for about 1.5 years without any issues. Recently the source has changed something in the stream that causes recording issues. The same stream plays perfectly from VLC . Attached is logs and config. I've tried to change the consumer to FFMPEG from the raw as well.

I can provide a clip if needed.

I captured the stream withFFMPEG and it played in Sage Fine.

ffmpeg.exe -y -i http://StreamURL.ts -c:v copy -c:a copy -t 00:00:30 myrecording.ts

** EDIT here is more log info for FFMPEG **

Code:
NFO   | jvm 1    | 2018/01/10 07:45:10.925 | 07:45:10.830 [SageTVRequestHandler-61:IPTV1] INFO  GenericHttpCaptureDevice - Configuring and starting the new SageTV consumer...
INFO   | jvm 1    | 2018/01/10 07:45:10.925 | 07:45:10.830 [NIOHTTPProducerImpl-91:IPTV1] INFO  NIOHTTPProducerImpl - Producer thread is running.
INFO   | jvm 1    | 2018/01/10 07:45:10.925 | 07:45:10.835 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder consumer thread is now running.
INFO   | jvm 1    | 2018/01/10 07:45:10.925 | 07:45:10.913 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - Before avformat_find_stream_info() pos=40030 bytes_read=40030 seek_count=0. probesize: 165628 analyzeduration: 2000000.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.125 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - After avformat_find_stream_info() pos=0 bytes_read=503090 seek_count=1. probesize: 165628 analyzeduration: 2000000.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.125 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - current container duration = 1.277333 seconds
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.130 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - Could not find a video stream. Trying again with an extended probe.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.131 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - Before avformat_find_stream_info() pos=462144 bytes_read=462144 seek_count=0. probesize: 639058 analyzeduration: 2277333.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.155 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR h264 - [41805340] cabac decode of qscale diff failed at 25 16
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.155 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR h264 - [41805340] error while decoding MB 25 16, bytestream 15953
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.209 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - After avformat_find_stream_info() pos=0 bytes_read=1097606 seek_count=1. probesize: 639058 analyzeduration: 2277333.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.209 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - current container duration = 2.797333 seconds
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.212 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegStreamDetection - Primary program has been detected: 1.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.212 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegTranscoder - Initializing FFmpeg transcoder stream output.
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.219 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegContext - Primary: 
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | Input #0, mpegts, from 'input-mpeg-ts.ts':
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |   Duration: 00:00:02.80, start: 43120.064000, bitrate: 3139 kb/s
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |   Program 1
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |     Metadata:
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |       service_name    : Service01
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |       service_provider: FFmpeg
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |     Stream #0:0[0x100], 39, 1/90000: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 704x576 [SAR 16:11 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |     Stream #0:1[0x101](eng), 73, 1/90000: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 196 kb/s
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.222 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegContext - Primary: 
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | Output #0, mpegts, to 'M:\M Recordings\CelebrityBigBrother-Live-17242906-0.ts':
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |     Stream #0:0, 0, 1/90000: Video: h264, yuv420p, 704x576 [SAR 16:11 DAR 16:9], q=2-31, 90k tbn, 50 tbc
INFO   | jvm 1    | 2018/01/10 07:45:11.225 |     Stream #0:1(eng), 0, 1/90000: Audio: aac, 48000 Hz, stereo, fltp, 196 kb/s
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 
INFO   | jvm 1    | 2018/01/10 07:45:11.225 | 07:45:11.223 [FFmpegTransSageTVConsumerImpl-93:IPTV1] INFO  FFmpegTranscoder - Initialized FFmpeg transcoder stream output.
INFO   | jvm 1    | 2018/01/10 07:45:11.325 | 07:45:11.260 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
INFO   | jvm 1    | 2018/01/10 07:45:11.325 | 07:45:11.260 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
INFO   | jvm 1    | 2018/01/10 07:45:11.625 | 07:45:11.559 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 3 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
INFO   | jvm 1    | 2018/01/10 07:45:11.625 | 07:45:11.559 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
INFO   | jvm 1    | 2018/01/10 07:45:11.625 | 07:45:11.559 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing


7:51:55.109 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - sync offsets [-3880944000, -3880944000] to -3880944000, diff = 0, attempts = 5
07:51:56.273 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:51:56.274 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 37749120 == last dts 37749120, pts 37749120, last pts 37749120
07:51:57.179 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 37839360 == last dts 37839360, pts 37839360, last pts 37839360
07:51:59.251 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 37969920 == last dts 37969920, pts 37969920, last pts 37969920
07:52:04.185 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 38453760 == last dts 38453760, pts 38453760, last pts 38453760
07:52:07.187 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 7 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:07.188 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:07.188 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:16.400 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 39548160 == last dts 39548160, pts 39548160, last pts 39548160
07:52:20.202 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 39815040 == last dts 39815040, pts 39815040, last pts 39815040
07:52:24.280 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 2 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:24.280 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:24.280 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:24.352 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 2 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:24.352 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:24.352 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:27.298 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 1 time: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:27.298 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:27.298 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:32.482 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 41032320 == last dts 41032320, pts 41032320, last pts 41032320
07:52:34.368 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 41243520 == last dts 41243520, pts 41243520, last pts 41243520
07:52:40.282 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 41758080 == last dts 41758080, pts 41758080, last pts 41758080
07:52:45.162 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 10 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:45.162 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:45.162 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:48.370 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 161127883, readIndex = 3892754
07:52:48.370 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 161127883, readIndex = 3841483, returnValue = 161127883
07:52:53.361 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 4 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:52:53.361 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:52:55.233 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - Repeated 1 time: [41804de0] PES packet size mismatch.
07:52:55.233 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:52:55.233 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 43104000 == last dts 43104000, pts 43104000, last pts 43104000
07:53:00.377 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 1 time: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:53:00.377 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:53:00.441 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:53:01.165 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 43585920 == last dts 43585920, pts 43585920, last pts 43585920
07:53:01.255 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 165616797, readIndex = 662638
07:53:01.255 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 165616797, readIndex = 466077, returnValue = 165616797
07:53:03.211 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 2 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:53:03.212 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:53:03.212 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
07:53:05.299 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 43977600 == last dts 43977600, pts 43977600, last pts 43977600
07:53:23.252 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegTranscoder - discarding frame stream 1, dts 45582720 == last dts 45582720, pts 45582720, last pts 45582720
07:53:25.324 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 173692498, readIndex = 923134
07:53:25.324 [FFmpegTransSageTVConsumerImpl-93:IPTV1] DEBUG FFmpegCircularBufferNIO - Seek: wence = 0, offset = 173692498, readIndex = 677458, returnValue = 173692498
07:53:27.238 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - Repeated 4 times: [3afc6480] AAC bitstream not in ADTS format and extradata missing.
07:53:27.239 [FFmpegTransSageTVConsumerImpl-93:IPTV1] WARN  mpegts - [41804de0] PES packet size mismatch
07:53:27.239 [FFmpegTransSageTVConsumerImpl-93:IPTV1] ERROR mpegts - [3afc6480] AAC bitstream not in ADTS format and extradata missing
Thanks

Chris
I looked up the error message about AAC and it looks like it might be a bug in FFmpeg, but it's hard to tell. I tried upgrading the version of FFmpeg used by OpenDCT a year ago and it made OpenDCT transcoding unstable because they made a lot of changes and provided no updates for their code examples showing how to do things the new way. If you can run the stream through a newer version of FFmpeg binary without issues, I would recommend you go that route to clean it up for SageTV. Use the generic pipe consumer to try this 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
  #2260  
Old 01-12-2018, 09:08 PM
technazz's Avatar
technazz technazz is offline
Sage Aficionado
  
Join Date: Jul 2004
Location: Hamilton, ON, CA
Posts: 499
Quote:
Originally Posted by EnterNoEscape View Post
I looked up the error message about AAC and it looks like it might be a bug in FFmpeg, but it's hard to tell. I tried upgrading the version of FFmpeg used by OpenDCT a year ago and it made OpenDCT transcoding unstable because they made a lot of changes and provided no updates for their code examples showing how to do things the new way. If you can run the stream through a newer version of FFmpeg binary without issues, I would recommend you go that route to clean it up for SageTV. Use the generic pipe consumer to try this out.
Yes, that what I did. I use generic pipe for all my IP cameras.

The new FFMPEG seems to do a better job at cleaning up my streams and it doesn't take up much CPU.

Chris
__________________
SageTV V9.xx 2 x HD300's, 2 x Nvidia Shields Running Mini Client
Reply With Quote
Reply
Page 113 of 148 « First 1363103111112 113 114115123 Last »

« Previous Thread | Next Thread »

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.

Contact Us - SageTV, LLC - Archive - Privacy Statement - Top

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