OpenDCT: An open source digital cable tuner.

[Jabroni]

Originally Posted by EnterNoEscape

The variable doesn't work in the URL's, but I can't really see any reason why I couldn't add support for that. It just will not work cleanly for ATSC since SageTV and the HDHomeRun disagree on notation in that regard.

Yeah that would have to be taken care directly from the user end point to keep channel guide scan / synced. That would be the limitation of this particular setup but at least we can out of our region OTA channels to our sage without having much equipment on remote site. Having the HDHomeRun doing the scan and the user to take care of the channel lineup via the EPG data and the SageTV physical channel (1-1,9-1,14-1,etc) would be more than enough. Hope you could add that parameter to the URL and if you want help testing just let me know and I can be a ginea pig

UPDATE

I started playing with the hdhomerun_config, I was able to trigger a remote scan using
./hdhomerun_config <device.ip> scan 0

Does OpenDCT uses libhdhomerun api to do all the comunication with the HDHomeRuns ?

[EnterNoEscape]

Originally Posted by Jabroni

Yeah that would have to be taken care directly from the user end point to keep channel guide scan / synced. That would be the limitation of this particular setup but at least we can out of our region OTA channels to our sage without having much equipment on remote site. Having the HDHomeRun doing the scan and the user to take care of the channel lineup via the EPG data and the SageTV physical channel (1-1,9-1,14-1,etc) would be more than enough. Hope you could add that parameter to the URL and if you want help testing just let me know and I can be a ginea pig

UPDATE

I started playing with the hdhomerun_config, I was able to trigger a remote scan using
./hdhomerun_config <device.ip> scan 0

Does OpenDCT uses libhdhomerun api to do all the comunication with the HDHomeRuns ?

OpenDCT fully re-implements what those libraries do in Java. It's 100% network based and there's no real reason to use native libraries because of this. The reason that worked for you was because you provided the IP address. OpenDCT uses TCP/IP to communicate with the HDHomeRuns and if given the IP address, it would be able to do that same thing. I moved away from relying on the IP addresses since they can change for various reasons on a network with DHCP. It is generally recommended that you refer to the HDHomeRuns by their hex ID for this reason. However you gave me a slightly better idea on dealing with your situation. I'll just add the option to specifically tell the HDHomeRun discover to try to load a comma separated list of IP addresses.

[Jabroni]

Originally Posted by EnterNoEscape

OpenDCT fully re-implements what those libraries do in Java. It's 100% network based and there's no real reason to use native libraries because of this. The reason that worked for you was because you provided the IP address. OpenDCT uses TCP/IP to communicate with the HDHomeRuns and if given the IP address, it would be able to do that same thing. I moved away from relying on the IP addresses since they can change for various reasons on a network with DHCP. It is generally recommended that you refer to the HDHomeRuns by their hex ID for this reason. However you gave me a slightly better idea on dealing with your situation. I'll just add the option to specifically tell the HDHomeRun discover to try to load a comma separated list of IP addresses.

That would be sweet... I got another suggestion, maybe it would be nice to have like the GenericHTTP, but a GenericPipe, where one could specify a command to execute, and pipe the output and threat it like a stream. With that we could extend more the reach of OpenDCT to other interfaces/plugins. Currently thats how I manage with my Network Encoder that I worked as a Java plugin within sage, but with a more basic approach and not as well build as your solution. I just pipe a perl script to ffmpeg to "smooth the stream", and save the output to the Network Encoder supplied local file.

[EnterNoEscape]

Originally Posted by Jabroni

That would be sweet... I got another suggestion, maybe it would be nice to have like the GenericHTTP, but a GenericPipe, where one could specify a command to execute, and pipe the output and threat it like a stream. With that we could extend more the reach of OpenDCT to other interfaces/plugins. Currently thats how I manage with my Network Encoder that I worked as a Java plugin within sage, but with a more basic approach and not as well build as your solution. I just pipe a perl script to ffmpeg to "smooth the stream", and save the output to the Network Encoder supplied local file.

It was asked of me to implement something kind of like this before. The reason I did not do it was because the rational was to support v4l by reading from the device under /dev like it was a file (which would work). My opinion in this area is that if you're going to do v4l, implement proper v4l device detection and the native code to support it.

Weirdly enough, I can see your use case as being something flexible enough that it actually makes some sense and would make it trivial for more advanced uses that I am unlikely to code. If you piped through stdout into OpenDCT an MPEG-TS stream, it can actually use it's own internal FFmpeg implementation to remux the stream for you. Depending on the device, it might not really be needed to remux the stream at all. I'll definitely consider adding this.

[EnterNoEscape]

See the 0.5.17 release notes for better details on some of the new features.

This might be a little more than just the highlights, but a lot of things were added in this release.

• Added basic HTTP authentication support to generic HTTP producer. (make sure you remove this information from opendct.properties if you post it)
• Added redirect support for HTTP producers.
• Added experimental Generic Pipe capture device. The creation of pipe capture devices is similar to Generic HTTP capture device except the stream is captured from the standard output of a custom script. (Support thread)
• Added timeout for when a program cannot be detected. The property name is consumer.ffmpeg.no_program_timeout_ms, the timeout is in milliseconds and defaults conservatively to 10000. The minimum value is 5000 and the maximum value is 60000. If you are missing audio streams in your recordings, you will want to increase this value.
• Added property to disable re-tuning. The property name is retune_enable and defaults to true. Set this property to false to disable retuning.
• Added a channel lineup update to be automatically triggered when a channel scan is initiated. This ensures that the latest information from the capture device if it provides any is used for the scan.
• Added property to force ClearQAM lookups to happen whenever possible. If the lookup is not able to be performed likely due to no CableCARD capture devices being available, it will use the last known value. If there isn't a last known value, the tuning will fail which is the same as the old behavior. The property for InfiniTV devices is upnp.always_remap_lookup=false. The property for HDHomeRun devices is hdhr.always_remap_lookup=false. Change the value from false to true to enable this feature.
• Added property to allow HDHomeRun devices to be statically defined by IP address. This is useful if you have an HDHomeRun device on another subnet that would not be detectable any other way. The property name is hdhr.static_addresses_csv=. If it is populated with comma delimited values, the program will attempt to convert those values to IP addresses and will send a discovery packet directly to the that IP address.
• Added support for %c% variable (channel string) for the properties sagetv.device.<unique_id>.streaming_url= and sagetv.device.<unique_id>.streaming_url2=.
• Added check and timeout for APIPA addresses on any network adapters on startup. If any interfaces have an APIPA address, it is as good as not having any interfaces available for up to 2 minutes.
• Added better handling when a local interface cannot be determined by a remote IP address.
• Fixed InfiniTV ClearQAM program selection confirmation always timing out.
• Fixed media server (upload id) disconnecting too soon under some circumstances resulting in missing a few last seconds of a stream that would have otherwise been written to disk.
• Fixed potential write deadlock in termination of the Generic HTTP capture device discoverer.
• Reverted back to FFmpeg 2.8.1 until the deprecated features can be managed.
• Upgraded GSON library to 2.8.0.
• Upgraded Cling to 2.1.1.

[technazz]

With the new version you released today I get errors with my IPTV stream. Any Idea?

Thanks

Chris

22:34:23.834 [SageTVRequestHandler-100:Unknown] INFO  SageTVRequestHandler - Sent PROPERTIES.
22:34:23.835 [SageTVRequestHandler-100:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'QUIT'
22:38:43.566 [SageTVRequestHandler-102:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'BUFFER IPTV1 HDMI|1883994911|1|16777216|E:\E Recordings\IPTV1on1270019000HDMI-0.mpgbuf|Great-H.264'
22:38:43.566 [SageTVRequestHandler-102:IPTV1] DEBUG GenericHttpCaptureDevice - Capture device is now re-locked.
22:38:43.566 [SageTVRequestHandler-102:IPTV1] DEBUG SageTVRequestHandler - Starting buffered network encoder via upload ID '1883994911' to file name 'E:\E Recordings\IPTV1on1270019000HDMI-0.mpgbuf'.
22:38:43.566 [SageTVRequestHandler-102:IPTV1] DEBUG BasicCaptureDevice - Consumer is was not in progress.
22:38:43.570 [SageTVRequestHandler-102:IPTV1] INFO  GenericHttpCaptureDevice - Starting the encoding for the channel '1' from the device 'IPTV1' to the file 'E:\E Recordings\IPTV1on1270019000HDMI-0.mpgbuf'...
22:38:43.570 [SageTVRequestHandler-102:IPTV1] INFO  GenericHttpCaptureDevice - Configuring and starting the new SageTV producer...
22:38:43.570 [SageTVRequestHandler-102:IPTV1] INFO  NIOHTTPProducerImpl - Connecting to source using the URL 'http://flawless-iptv.net:4545/live/xxx@xxx.com/password/165.ts'
22:38:43.839 [SageTVRequestHandler-102:IPTV1] DEBUG HTTPProducerImpl - HTTP response: 'HTTP/1.1 302 Found', 'Server: nginx', 'Date: Thu, 22 Dec 2016 03:38:38 GMT', 'Content-Type: text/html; charset=UTF-8', 'Connection: close', 'Access-Control-Allow-Origin: *', 'Location: http://192.99.40.78:4545/live/xxx@xxx.com/password/165.ts?token=YlZxM21sSnRlb0pYNE9WSnZNeUpTSTZyOVhzaUdHYzN4RUZqRzg5QkhEaVN2Uy9idW9ZRndiWUdieVhUY0xxTU1GZUIzUmhhSE5zZGJoWSsxSUUrMWhnY2hlc3czTTBxcmlaYkFtQnBrdTl0QWRCdm1ycExuaTl3NUJDUktGdk5XZjE0T3VHK251NmJ5VUtqZXB3NUdQSU1RRTNsR0hXejYydGRxU0pNOGZENStDUzA5SDNSaXFsZnlqLzRZcG5sUDdYOW1Fb0R4MElXanVjS2YzeFpwV2YralI0K1RNSUFPc2ZkczVpR0VBZTlueUVBb0dBKzlZVGJLcXVlSUVXT1FlRzdpM2NlZzdYdTc4WUswMmdtZm5rRGg4dm55b3p1bmFwWmN2Y2hqdUw5UHV5cXkybHZGNklGajRlT2x2YkZCS0gvbG5kODhMRFV4ZGs4R0dtb0x4Z3NpTG00cHRCZjNwYU1ZR0sxL2JTVmlIaVQwM05VVnhiYTRQdGxFckM2ekRjS3lmUDFjWUhRVGFQZGY0UUxqd216SnpGR2JlSUc4QUpWUHNRSzU2VGR0eXRzVm9RY1M1amVQYUE3WUNPUDR1b2prTGdLbEYxZGhNQytTRnppTVRQQnVkWEVjOU9XNVFFekMybVlHcDJWRU8zT3RuL2c5OHVubHFyaVJWQ2t8Slk1Z251Z2l5VHlHdEJ0eUJXQWRPb0JGamJaUzcxY2FBODFZUkZ5a045RT0=', 
22:38:43.840 [SageTVRequestHandler-102:IPTV1] INFO  HTTPProducerImpl - HTTP redirect: http://192.99.40.78:4545/live/xxx@xxx.com/password/165.ts?token=YlZxM21sSnRlb0pYNE9WSnZNeUpTSTZyOVhzaUdHYzN4RUZqRzg5QkhEaVN2Uy9idW9ZRndiWUdieVhUY0xxTU1GZUIzUmhhSE5zZGJoWSsxSUUrMWhnY2hlc3czTTBxcmlaYkFtQnBrdTl0QWRCdm1ycExuaTl3NUJDUktGdk5XZjE0T3VHK251NmJ5VUtqZXB3NUdQSU1RRTNsR0hXejYydGRxU0pNOGZENStDUzA5SDNSaXFsZnlqLzRZcG5sUDdYOW1Fb0R4MElXanVjS2YzeFpwV2YralI0K1RNSUFPc2ZkczVpR0VBZTlueUVBb0dBKzlZVGJLcXVlSUVXT1FlRzdpM2NlZzdYdTc4WUswMmdtZm5rRGg4dm55b3p1bmFwWmN2Y2hqdUw5UHV5cXkybHZGNklGajRlT2x2YkZCS0gvbG5kODhMRFV4ZGs4R0dtb0x4Z3NpTG00cHRCZjNwYU1ZR0sxL2JTVmlIaVQwM05VVnhiYTRQdGxFckM2ekRjS3lmUDFjWUhRVGFQZGY0UUxqd216SnpGR2JlSUc4QUpWUHNRSzU2VGR0eXRzVm9RY1M1amVQYUE3WUNPUDR1b2prTGdLbEYxZGhNQytTRnppTVRQQnVkWEVjOU9XNVFFekMybVlHcDJWRU8zT3RuL2c5OHVubHFyaVJWQ2t8Slk1Z251Z2l5VHlHdEJ0eUJXQWRPb0JGamJaUzcxY2FBODFZUkZ5a045RT0=
22:38:43.840 [SageTVRequestHandler-102:IPTV1] ERROR HTTPCaptureDeviceServices - startProducing created an unexpected exception => java.nio.channels.AlreadyConnectedException
	at sun.nio.ch.SocketChannelImpl.ensureOpenAndUnconnected(Unknown Source)
	at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
	at opendct.video.http.NIOHttpDownloader.connect(NIOHttpDownloader.java:89)
	at opendct.video.http.NIOHttpDownloader.connect(NIOHttpDownloader.java:181)
	at opendct.video.http.NIOHttpDownloader.connect(NIOHttpDownloader.java:66)
	at opendct.producer.NIOHTTPProducerImpl.setSourceUrl(NIOHTTPProducerImpl.java:162)
	at opendct.producer.NIOHTTPProducerImpl.selectURL(NIOHTTPProducerImpl.java:99)
	at opendct.producer.NIOHTTPProducerImpl.setSourceUrls(NIOHTTPProducerImpl.java:68)
	at opendct.capture.services.HTTPCaptureDeviceServices.startProducing(HTTPCaptureDeviceServices.java:98)
	at opendct.capture.GenericHttpCaptureDevice.startEncodingSync(GenericHttpCaptureDevice.java:324)
	at opendct.capture.GenericHttpCaptureDevice.startEncoding(GenericHttpCaptureDevice.java:227)
	at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:301)
	at java.lang.Thread.run(Unknown Source)

22:38:43.840 [SageTVRequestHandler-102:IPTV1] ERROR SageTVRequestHandler - SageTV sent: 'BUFFER IPTV1 HDMI|1883994911|1|16777216|E:\E Recordings\IPTV1on1270019000HDMI-0.mpgbuf|Great-H.264', Replied: 'ERROR Device Start Failed'
22:38:43.840 [SageTVRequestHandler-102:IPTV1] ERROR SageTVRequestHandler - Encoder device is unable to start.

[EnterNoEscape]

Originally Posted by technazz

With the new version you released today I get errors with my IPTV stream. Any Idea?

Thanks

Chris

22:34:23.834 [SageTVRequestHandler-100:Unknown] INFO  SageTVRequestHandler - Sent PROPERTIES.
22:34:23.835 [SageTVRequestHandler-100:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'QUIT'
22:38:43.566 [SageTVRequestHandler-102:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'BUFFER IPTV1 HDMI|1883994911|1|16777216|E:\E Recordings\IPTV1on1270019000HDMI-0.mpgbuf|Great-H.264'
22:38:43.566 [SageTVRequestHandler-102:IPTV1] DEBUG GenericHttpCaptureDevice - Capture device is now re-locked.
22:38:43.566 [SageTVRequestHandler-102:IPTV1] DEBUG SageTVRequestHandler - Starting buffered network encoder via upload ID '1883994911' to file name 'E:\E Recordings\IPTV1on1270019000HDMI-0.mpgbuf'.
22:38:43.566 [SageTVRequestHandler-102:IPTV1] DEBUG BasicCaptureDevice - Consumer is was not in progress.
22:38:43.570 [SageTVRequestHandler-102:IPTV1] INFO  GenericHttpCaptureDevice - Starting the encoding for the channel '1' from the device 'IPTV1' to the file 'E:\E Recordings\IPTV1on1270019000HDMI-0.mpgbuf'...
22:38:43.570 [SageTVRequestHandler-102:IPTV1] INFO  GenericHttpCaptureDevice - Configuring and starting the new SageTV producer...
22:38:43.570 [SageTVRequestHandler-102:IPTV1] INFO  NIOHTTPProducerImpl - Connecting to source using the URL 'http://flawless-iptv.net:4545/live/xxx@xxx.com/password/165.ts'
22:38:43.839 [SageTVRequestHandler-102:IPTV1] DEBUG HTTPProducerImpl - HTTP response: 'HTTP/1.1 302 Found', 'Server: nginx', 'Date: Thu, 22 Dec 2016 03:38:38 GMT', 'Content-Type: text/html; charset=UTF-8', 'Connection: close', 'Access-Control-Allow-Origin: *', 'Location: http://192.99.40.78:4545/live/xxx@xxx.com/password/165.ts?token=YlZxM21sSnRlb0pYNE9WSnZNeUpTSTZyOVhzaUdHYzN4RUZqRzg5QkhEaVN2Uy9idW9ZRndiWUdieVhUY0xxTU1GZUIzUmhhSE5zZGJoWSsxSUUrMWhnY2hlc3czTTBxcmlaYkFtQnBrdTl0QWRCdm1ycExuaTl3NUJDUktGdk5XZjE0T3VHK251NmJ5VUtqZXB3NUdQSU1RRTNsR0hXejYydGRxU0pNOGZENStDUzA5SDNSaXFsZnlqLzRZcG5sUDdYOW1Fb0R4MElXanVjS2YzeFpwV2YralI0K1RNSUFPc2ZkczVpR0VBZTlueUVBb0dBKzlZVGJLcXVlSUVXT1FlRzdpM2NlZzdYdTc4WUswMmdtZm5rRGg4dm55b3p1bmFwWmN2Y2hqdUw5UHV5cXkybHZGNklGajRlT2x2YkZCS0gvbG5kODhMRFV4ZGs4R0dtb0x4Z3NpTG00cHRCZjNwYU1ZR0sxL2JTVmlIaVQwM05VVnhiYTRQdGxFckM2ekRjS3lmUDFjWUhRVGFQZGY0UUxqd216SnpGR2JlSUc4QUpWUHNRSzU2VGR0eXRzVm9RY1M1amVQYUE3WUNPUDR1b2prTGdLbEYxZGhNQytTRnppTVRQQnVkWEVjOU9XNVFFekMybVlHcDJWRU8zT3RuL2c5OHVubHFyaVJWQ2t8Slk1Z251Z2l5VHlHdEJ0eUJXQWRPb0JGamJaUzcxY2FBODFZUkZ5a045RT0=', 
22:38:43.840 [SageTVRequestHandler-102:IPTV1] INFO  HTTPProducerImpl - HTTP redirect: http://192.99.40.78:4545/live/xxx@xxx.com/password/165.ts?token=YlZxM21sSnRlb0pYNE9WSnZNeUpTSTZyOVhzaUdHYzN4RUZqRzg5QkhEaVN2Uy9idW9ZRndiWUdieVhUY0xxTU1GZUIzUmhhSE5zZGJoWSsxSUUrMWhnY2hlc3czTTBxcmlaYkFtQnBrdTl0QWRCdm1ycExuaTl3NUJDUktGdk5XZjE0T3VHK251NmJ5VUtqZXB3NUdQSU1RRTNsR0hXejYydGRxU0pNOGZENStDUzA5SDNSaXFsZnlqLzRZcG5sUDdYOW1Fb0R4MElXanVjS2YzeFpwV2YralI0K1RNSUFPc2ZkczVpR0VBZTlueUVBb0dBKzlZVGJLcXVlSUVXT1FlRzdpM2NlZzdYdTc4WUswMmdtZm5rRGg4dm55b3p1bmFwWmN2Y2hqdUw5UHV5cXkybHZGNklGajRlT2x2YkZCS0gvbG5kODhMRFV4ZGs4R0dtb0x4Z3NpTG00cHRCZjNwYU1ZR0sxL2JTVmlIaVQwM05VVnhiYTRQdGxFckM2ekRjS3lmUDFjWUhRVGFQZGY0UUxqd216SnpGR2JlSUc4QUpWUHNRSzU2VGR0eXRzVm9RY1M1amVQYUE3WUNPUDR1b2prTGdLbEYxZGhNQytTRnppTVRQQnVkWEVjOU9XNVFFekMybVlHcDJWRU8zT3RuL2c5OHVubHFyaVJWQ2t8Slk1Z251Z2l5VHlHdEJ0eUJXQWRPb0JGamJaUzcxY2FBODFZUkZ5a045RT0=
22:38:43.840 [SageTVRequestHandler-102:IPTV1] ERROR HTTPCaptureDeviceServices - startProducing created an unexpected exception => java.nio.channels.AlreadyConnectedException
	at sun.nio.ch.SocketChannelImpl.ensureOpenAndUnconnected(Unknown Source)
	at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
	at opendct.video.http.NIOHttpDownloader.connect(NIOHttpDownloader.java:89)
	at opendct.video.http.NIOHttpDownloader.connect(NIOHttpDownloader.java:181)
	at opendct.video.http.NIOHttpDownloader.connect(NIOHttpDownloader.java:66)
	at opendct.producer.NIOHTTPProducerImpl.setSourceUrl(NIOHTTPProducerImpl.java:162)
	at opendct.producer.NIOHTTPProducerImpl.selectURL(NIOHTTPProducerImpl.java:99)
	at opendct.producer.NIOHTTPProducerImpl.setSourceUrls(NIOHTTPProducerImpl.java:68)
	at opendct.capture.services.HTTPCaptureDeviceServices.startProducing(HTTPCaptureDeviceServices.java:98)
	at opendct.capture.GenericHttpCaptureDevice.startEncodingSync(GenericHttpCaptureDevice.java:324)
	at opendct.capture.GenericHttpCaptureDevice.startEncoding(GenericHttpCaptureDevice.java:227)
	at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:301)
	at java.lang.Thread.run(Unknown Source)

22:38:43.840 [SageTVRequestHandler-102:IPTV1] ERROR SageTVRequestHandler - SageTV sent: 'BUFFER IPTV1 HDMI|1883994911|1|16777216|E:\E Recordings\IPTV1on1270019000HDMI-0.mpgbuf|Great-H.264', Replied: 'ERROR Device Start Failed'
22:38:43.840 [SageTVRequestHandler-102:IPTV1] ERROR SageTVRequestHandler - Encoder device is unable to start.

That's my fault. There's a small, but important mistake in the code causing this to happen.

[EnterNoEscape]

• Fixed closing the previous socket when redirecting.

[technazz]

Originally Posted by EnterNoEscape

• Fixed closing the previous socket when redirecting.

Nice it works!

I appreciate it!

Chris

[Greg2dot0]

Originally Posted by EnterNoEscape

• Fixed closing the previous socket when redirecting.

Things have been running very smoothly since 5.13 here. Installed and tested 5.18 first thing this morning and all seems to be working well.

Great work!!

[EnterNoEscape]

Originally Posted by technazz

Nice it works!

I appreciate it!

Chris

Originally Posted by Greg2dot0

Things have been running very smoothly since 5.13 here. Installed and tested 5.18 first thing this morning and all seems to be working well.

Great work!!

Good to hear. I think we'll be starting release candidates soon.

[technazz]

Ok,

Ok now that its working I have access to about 300 more IPTV channels i want to add. They basically have the same url like below

http\://XXX-iptv.net\:4545/live/Login/Password/165.ts
http\://XXX-iptv.net\:4545/live/Login/Password/166.ts
http\://XXX-iptv.net\:4545/live/Login/Password/167.ts
ect..


Can I add them in the same tuner or do I have to make a URL tuner entry for each url? (generic.http.device_names_csv=IPTV1,IPTV2,ect,,)


THanks

Chris

[EnterNoEscape]

Originally Posted by technazz

Ok,

Ok now that its working I have access to about 300 more IPTV channels i want to add. They basically have the same url like below

http\://XXX-iptv.net\:4545/live/Login/Password/165.ts
http\://XXX-iptv.net\:4545/live/Login/Password/166.ts
http\://XXX-iptv.net\:4545/live/Login/Password/167.ts
ect..


Can I add them in the same tuner or do I have to make a URL tuner entry for each url? (generic.http.device_names_csv=IPTV1,IPTV2,ect,,)


THanks

Chris

One of the changes I just made was allowing %c% to be used in a URL. Let me know if it's not working, but in my testing, it looked ok. The URL would then look like the following:
http\://XXX-iptv.net\:4545/live/Login/Password/%c%.ts

Also, you can specify all of the available channels in the property sagetv.device.<device_id>.custom_channels= so they are returned in a channel scan like this:
sagetv.device.<device_id>.custom_channels=165;166;167

If you can access as many at a time as you want, I guess you would just create a capture device for as many as you want to be able to use at a time.

[technazz]

I tried this an no other channels show up in the channel setup. Just Chanel 1-HDMI.

Should I be seeing an HDMI input? Seems like its locked to one channel only.

Also the last channel field is populated with 1 which is not a valid channel, i changed it to 166 and the video previews.

These is also no channel scan option. I think I have something set up wrongly.

An Ideas?

Chris

Originally Posted by EnterNoEscape

One of the changes I just made was allowing %c% to be used in a URL. Let me know if it's not working, but in my testing, it looked ok. The URL would then look like the following:
http\://XXX-iptv.net\:4545/live/Login/Password/%c%.ts

Also, you can specify all of the available channels in the property sagetv.device.<device_id>.custom_channels= so they are returned in a channel scan like this:
sagetv.device.<device_id>.custom_channels=165;166;167

If you can access as many at a time as you want, I guess you would just create a capture device for as many as you want to be able to use at a time.

[EnterNoEscape]

Originally Posted by technazz

I tried this an no other channels show up in the channel setup. Just Chanel 1-HDMI.

Should I be seeing an HDMI input? Seems like its locked to one channel only.

Also the last channel field is populated with 1 which is not a valid channel, i changed it to 166 and the video previews.

These is also no channel scan option. I think I have something set up wrongly.

An Ideas?

Chris

I am referring to the channel scan within SageTV.
Setup > Setup Video Sources > [capture_device] > Channel Setup > Scan for Available Channels > Scan for Available Channels Now
Edit: I just noticed that this isn't available for non-digital tuners. I thought I remembered this option when I used the HD-PVR, I guess I was wrong. I think your best bet is going to be entering the channels manually with the second option mentioned below. I'll need to think about this one a bit since this would be very convenient if it worked.


You can also manually add channels within SageTV.
Setup > Setup Video Sources > [capture_device] > Channel Setup > Edit Channel Lineup > Add Channel to Lineup

[technazz]

Ok that works.


THanks!

Chris

[technazz]

Ok I was able to add more channels no problem but they are working intermittently. Some work 100% in the preview option in the setup menu then not when selected in the EPG.

I attached a log, channel 165 works and then 287 doesn't.

Thanks

Chris

[EnterNoEscape]

Originally Posted by technazz

Ok I was able to add more channels no problem but they are working intermittently. Some work 100% in the preview option in the setup menu then not when selected in the EPG.

I attached a log, channel 165 works and then 287 doesn't.

Thanks

Chris

I don't see anything interesting. The streams are definitely being detected correctly and are streaming. What I would do is create a recording and see if you can open the file outside of SageTV. If you can, the fault is likely SageTV's ability to deal with the formats involved. I also recommend upgrading to SageTV v9 since there have been many improvements in this area.

I noticed that the TS you're downloading is being produced by FFmpeg on their end, so it's probably a very clean stream. I would change to the raw consumer and take FFmpeg out of the picture completely because it's just not necessary in this case.
e.g.
sagetv.device.<device_id>.consumer=opendct.consumer.RawSageTVConsumerImpl

[technazz]

Originally Posted by EnterNoEscape

I don't see anything interesting. The streams are definitely being detected correctly and are streaming. What I would do is create a recording and see if you can open the file outside of SageTV. If you can, the fault is likely SageTV's ability to deal with the formats involved. I also recommend upgrading to SageTV v9 since there have been many improvements in this area.

I noticed that the TS you're downloading is being produced by FFmpeg on their end, so it's probably a very clean stream. I would change to the raw consumer and take FFmpeg out of the picture completely because it's just not necessary in this case.
e.g.
sagetv.device.<device_id>.consumer=opendct.consumer.RawSageTVConsumerImpl

I am running the latest V9

I changed the Consumer setting and Recorded in SageTV.

I opened the recorded .ts file in VLC and it played fine. I get No signal when I try to play in Sagetv.

Could this be a decoder issues? Im remotely loging into my SageTV windows box from work and then playing in the PC client or my HD200 and HD300's

Chris

[EnterNoEscape]

Originally Posted by technazz

I am running the latest V9

I changed the Consumer setting and Recorded in SageTV.

I opened the recorded .ts file in VLC and it played fine. I get No signal when I try to play in Sagetv.

Could this be a decoder issues? Im remotely loging into my SageTV windows box from work and then playing in the PC client or my HD200 and HD300's

Chris

Seeing what sage logs have to say might help a little. I was just going on your signature about the SageTV version.