johnodon Posted February 5, 2016 Share Posted February 5, 2016 I know that this probably only serve a few people, but I figured I would share the channel logos that I use for TVH/Myth/Kodi. Here are some examples: Here is a link to a zip that has my OTA channels + a blank.png that you can use to create your own: https://www.dropbox.com/s/2lnzt7g6hrdccc7/icons.zip?dl=0 John Quote Link to comment
johnodon Posted February 5, 2016 Share Posted February 5, 2016 I think I actually did it! I have 2 containers for zap2xml perl script: One is simply called zap2xml and is for users who need to scrape only one zipcode on zap2it.com. The other is called zap2xml-2lineups. This is for users (like me) who need to scrape guide data for 2 different zipcodes to cover all of their channels. This requires 2 unique accounts/configurations on zap2it.com. The resulting XMLs that are generated are merged into a single one at the end (guide.xml). Docker Reporisitory Templates: https://github.com/johnodon/unraid-templates I tried to put as much instruction in the template as possible. Be warned that I have not yet added the cron job to run the scrape every 12 or 24 hours. In the meantime, just restart the zap2xml container every so often and your guide data will be refreshed. Major props to Chis Pollard and saarg for helping me along! With any luck saarg will be able to incorporate this directly into his TVH container. Please feel free to provide feedback or ask questions. John UPDATE: Same changes were pushed to master zap2xml and new image has been built. Both zap2xml and zap2xml-2lineups have been fully updated and built with the changes below. Some updates made to the zap2xml-2lineups container and unraid template: - Added cron job (editable in /config/) to run @ 11:30 and 23:30 daily - Miscellaneous files cleanup - unRAID template cleanup Working on the master zap2xml now in dev and will update later. Be sure you also refresh your unraid docker template repositories to get the updated templates. John It's Friday and I'm lazy So... Why do we need two different versions for more than one line up? We don't. One version is for single lineup and one version is for 2 lineups. Quote Link to comment
JM2005 Posted February 5, 2016 Share Posted February 5, 2016 Johnodon Just wondering why you left mythtv for TVheadend? Quote Link to comment
saarg Posted February 5, 2016 Author Share Posted February 5, 2016 We don't. One version is for single lineup and one version is for 2 lineups. My question didn't come out the way it was ment. Why do we need two containers? Isn't it possible to only have one container and just checking if there are more than one config file and then run the correct command? Quote Link to comment
bungee91 Posted February 5, 2016 Share Posted February 5, 2016 I know that this probably only server a few people, but I figured I would share the channel logos that I use for TVH/Myth/Kodi. Here are some examples: Here is a link to a zip that has my OTA channels + a blank.png that you can use to create your own: https://www.dropbox.com/s/2lnzt7g6hrdccc7/icons.zip?dl=0 John Thanks, yours were nicer than mine! Quote Link to comment
bungee91 Posted February 5, 2016 Share Posted February 5, 2016 Johnodon Just wondering why you left mythtv for TVheadend? Info here https://lime-technology.com/forum/index.php?topic=46299.0 Quote Link to comment
johnodon Posted February 5, 2016 Share Posted February 5, 2016 Johnodon Just wondering why you left mythtv for TVheadend? Info here https://lime-technology.com/forum/index.php?topic=46299.0 For me the main reasons were... 1. Chanel change speeds. 2. Ability to limit timeshift based on time/size. 3. Lots of current development on the TVH side. 4. Footprint is MUCH smaller for TVH. 5. Ability to use zap2xml for guide data (no more SD sub). 6. Dork note: can see signal strength with TVH addon in Kodi (I am antenna). I'll add more as I come up with them. John Quote Link to comment
JM2005 Posted February 6, 2016 Share Posted February 6, 2016 Thanks for taking the time to respond. I did see that other thread but was curious if anything had changed. I to use an antenna and use SD sub as well. I haven't switched from mythtv yet but do like looking at other options. Quote Link to comment
johnodon Posted February 6, 2016 Share Posted February 6, 2016 TBH...Myth was working just fine for me. I guess the inner dork just got the best of me and wanted to try (retry) something new. One major thing I left out of my reasons is the ability to completely manage TVH from the webui without the need to RDP in. John Quote Link to comment
johnodon Posted February 6, 2016 Share Posted February 6, 2016 Another small update to the zap2xml containers to set permissions correctly on the /data folder. I have also asked to be given access to the Docker Containers sub-forum so I can announce/support my containers their rather than hijack saarg's thread. John Quote Link to comment
johnodon Posted February 6, 2016 Share Posted February 6, 2016 zap2xml is officially available in Community Apps now. All support is moving to this thread: https://lime-technology.com/forum/index.php?topic=46330.0 Please ask questions there. John Quote Link to comment
saarg Posted February 14, 2016 Author Share Posted February 14, 2016 I made some changes in the templates for Tvheadend. There is only two templates for each version now. One without DVB pass through and one with that will pass through all DVB adapters available. In Oscam I added PCSCD as a service so it's possible to use a PCSC card reader. See first post for more info on how to do it (like they do on the Discovery Channel Sorry, couldn't resist ) Quote Link to comment
CHBMB Posted February 14, 2016 Share Posted February 14, 2016 I made some changes in the templates for Tvheadend. There is only two templates for each version now. One without DVB pass through and one with that will pass through all DVB adapters available. So basically, you told us all the wrong way to do it originally? We could have just used --device=/dev/dvb/ instead of --device=/dev/dvb/adapter0/demux0:/dev/dvb/adapter0/demux0 --device=/dev/dvb/adapter0/dvr0:/dev/dvb/adapter0/dvr0 --device=/dev/dvb/adapter0/frontend0:/dev/dvb/adapter0/frontend0 --device=/dev/dvb/adapter0/net0:/dev/dvb/adapter0/net0 --device=/dev/dvb/adapter1/demux0:/dev/dvb/adapter1/demux0 --device=/dev/dvb/adapter1/dvr0:/dev/dvb/adapter1/dvr0 --device=/dev/dvb/adapter1/frontend0:/dev/dvb/adapter1/frontend0 --device=/dev/dvb/adapter1/net0:/dev/dvb/adapter1/net0 --device=/dev/dvb/adapter2/demux0:/dev/dvb/adapter2/demux0 --device=/dev/dvb/adapter2/dvr0:/dev/dvb/adapter2/dvr0 --device=/dev/dvb/adapter2/frontend0:/dev/dvb/adapter2/frontend0 --device=/dev/dvb/adapter2/net0:/dev/dvb/adapter2/net0 --device=/dev/dvb/adapter3/demux0:/dev/dvb/adapter3/demux0 --device=/dev/dvb/adapter3/dvr0:/dev/dvb/adapter3/dvr0 --device=/dev/dvb/adapter3/frontend0:/dev/dvb/adapter3/frontend0 --device=/dev/dvb/adapter3/net0:/dev/dvb/adapter3/net0 Quote Link to comment
saarg Posted February 15, 2016 Author Share Posted February 15, 2016 I made some changes in the templates for Tvheadend. There is only two templates for each version now. One without DVB pass through and one with that will pass through all DVB adapters available. So basically, you told us all the wrong way to do it originally? We could have just used --device=/dev/dvb/ instead of --device=/dev/dvb/adapter0/demux0:/dev/dvb/adapter0/demux0 --device=/dev/dvb/adapter0/dvr0:/dev/dvb/adapter0/dvr0 --device=/dev/dvb/adapter0/frontend0:/dev/dvb/adapter0/frontend0 --device=/dev/dvb/adapter0/net0:/dev/dvb/adapter0/net0 --device=/dev/dvb/adapter1/demux0:/dev/dvb/adapter1/demux0 --device=/dev/dvb/adapter1/dvr0:/dev/dvb/adapter1/dvr0 --device=/dev/dvb/adapter1/frontend0:/dev/dvb/adapter1/frontend0 --device=/dev/dvb/adapter1/net0:/dev/dvb/adapter1/net0 --device=/dev/dvb/adapter2/demux0:/dev/dvb/adapter2/demux0 --device=/dev/dvb/adapter2/dvr0:/dev/dvb/adapter2/dvr0 --device=/dev/dvb/adapter2/frontend0:/dev/dvb/adapter2/frontend0 --device=/dev/dvb/adapter2/net0:/dev/dvb/adapter2/net0 --device=/dev/dvb/adapter3/demux0:/dev/dvb/adapter3/demux0 --device=/dev/dvb/adapter3/dvr0:/dev/dvb/adapter3/dvr0 --device=/dev/dvb/adapter3/frontend0:/dev/dvb/adapter3/frontend0 --device=/dev/dvb/adapter3/net0:/dev/dvb/adapter3/net0 Hey! Careful now baldy Quote Link to comment
binhex Posted February 15, 2016 Share Posted February 15, 2016 I made some changes in the templates for Tvheadend. There is only two templates for each version now. One without DVB pass through and one with that will pass through all DVB adapters available. So basically, you told us all the wrong way to do it originally? We could have just used --device=/dev/dvb/ instead of --device=/dev/dvb/adapter0/demux0:/dev/dvb/adapter0/demux0 --device=/dev/dvb/adapter0/dvr0:/dev/dvb/adapter0/dvr0 --device=/dev/dvb/adapter0/frontend0:/dev/dvb/adapter0/frontend0 --device=/dev/dvb/adapter0/net0:/dev/dvb/adapter0/net0 --device=/dev/dvb/adapter1/demux0:/dev/dvb/adapter1/demux0 --device=/dev/dvb/adapter1/dvr0:/dev/dvb/adapter1/dvr0 --device=/dev/dvb/adapter1/frontend0:/dev/dvb/adapter1/frontend0 --device=/dev/dvb/adapter1/net0:/dev/dvb/adapter1/net0 --device=/dev/dvb/adapter2/demux0:/dev/dvb/adapter2/demux0 --device=/dev/dvb/adapter2/dvr0:/dev/dvb/adapter2/dvr0 --device=/dev/dvb/adapter2/frontend0:/dev/dvb/adapter2/frontend0 --device=/dev/dvb/adapter2/net0:/dev/dvb/adapter2/net0 --device=/dev/dvb/adapter3/demux0:/dev/dvb/adapter3/demux0 --device=/dev/dvb/adapter3/dvr0:/dev/dvb/adapter3/dvr0 --device=/dev/dvb/adapter3/frontend0:/dev/dvb/adapter3/frontend0 --device=/dev/dvb/adapter3/net0:/dev/dvb/adapter3/net0 Hey! Careful now baldy [me=binhex]walks by with a smug grin on his face :-) :-)[/me] Quote Link to comment
CHBMB Posted February 15, 2016 Share Posted February 15, 2016 I did see your post binhex and was waiting for the opportunity to say something to saarg... Especially after all the stick he gives me.. Quote Link to comment
binhex Posted February 15, 2016 Share Posted February 15, 2016 I did see your post binhex and was waiting for the opportunity to say something to saarg... Especially after all the stick he gives me.. lol, always nice to get your own back eh ;-) Quote Link to comment
CHBMB Posted February 15, 2016 Share Posted February 15, 2016 Revenge is a dish best served cold.... Quote Link to comment
saarg Posted February 15, 2016 Author Share Posted February 15, 2016 Revenge is a dish best served cold.... It didn't work when I used a Dvb card a year ago, so sorry for not trying again every release of unraid > I thought you were the DVB guru now Quote Link to comment
Cmc0619 Posted February 19, 2016 Share Posted February 19, 2016 I've been popping in, pre-unRAID, on the tvheadend project for years trying to get it to work every few months or when a new release would come out. I've FINALLY gotten some forward motion while trying the 4.1 docker . 4.0.8 did nothing like the releases before. Any plans to release 4.2? 4.1, while finding all of my services (FINALLY! WHOOOO!), still isn't as user friendly as I'd like it to be and I'm hopeful to see if 4.2 is any better. Quote Link to comment
saarg Posted February 19, 2016 Author Share Posted February 19, 2016 I've been popping in, pre-unRAID, on the tvheadend project for years trying to get it to work every few months or when a new release would come out. I've FINALLY gotten some forward motion while trying the 4.1 docker . 4.0.8 did nothing like the releases before. Any plans to release 4.2? 4.1, while finding all of my services (FINALLY! WHOOOO!), still isn't as user friendly as I'd like it to be and I'm hopeful to see if 4.2 is any better. When 4.2 is released I'll release it also Quote Link to comment
saarg Posted February 23, 2016 Author Share Posted February 23, 2016 In case you didn't know about the documentation online for tvheadend, here is is Here is a link to the documentation for 4.0 http://docs.tvheadend.org/#tvheadend-40-user-guide And this is for unstable http://docs.tvheadend.org/#tvheadend-42-user-guide Quote Link to comment
Cornelius Posted February 24, 2016 Share Posted February 24, 2016 Hi, I have a little problem. Somehow i cant get my smartcard reader to work with oscam. After i plug it into the server my system log shows me the following: Feb 24 13:08:20 media-server kernel: usb 1-6: new full-speed USB device number 12 using xhci_hcd Feb 24 13:08:20 media-server kernel: ftdi_sio 1-6:1.0: FTDI USB Serial Device converter detected Feb 24 13:08:20 media-server kernel: usb 1-6: Detected FT232BM Feb 24 13:08:20 media-server kernel: ftdi_sio ttyUSB0: Unable to read latency timer: -32 Feb 24 13:08:20 media-server kernel: usb 1-6: FTDI USB Serial Device converter now attached to ttyUSB0 I added the following --device tag in Extra parameters: --device=/dev/ttyUSB0 But when I run this command: docker exec -it Oscam /usr/bin/pcsc_scan I dont get any result. Maybe there is some sort of mistake but i dont know where? Any help is greatly appreciated Quote Link to comment
saarg Posted February 24, 2016 Author Share Posted February 24, 2016 There is no reason for you to run the pcsc scan. That's only if you have a pcsc reader which you do not. Go add a reader in Oscam and use /dev/ttyUSB0 in the device field. If you have used this reader before with oscam, you can use the same setup. Quote Link to comment
Cornelius Posted February 26, 2016 Share Posted February 26, 2016 perfect! Everything is working now Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.