TorchRedRob

saarg, Thanks and excellent work on incorporating xmltv; it makes my half-baked attempt no longer necessary to complete. One question- any idea why it calls itself twice every time? I thought it might have something to do with the cron, so I changed it to operate once daily at 15:15:00 just to see what happened, and it still runs twice, back-to-back. Here is a sample log output of what happens every time it runs: Jan 11 15:15:00 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: grab /usr/local/bin/tv_grab_na_dd Jan 11 15:15:00 Tower tvheadend[18]: spawn: Executing "/usr/local/bin/tv_grab_na_dd" Jan 11 15:15:01 Tower tvheadend[18]: spawn: using config filename /nonexistent/.xmltv/tv_grab_na_dd.conf Jan 11 15:15:05 Tower tvheadend[18]: spawn: Fetching from Schedules Direct Fetched 3480 k/bytes in 3 seconds Jan 11 15:15:05 Tower tvheadend[18]: spawn: loading data Jan 11 15:15:16 Tower tvheadend[18]: spawn: NOTE: Your subscription will expire: Jan 11 15:15:16 Tower tvheadend[18]: spawn: Writing schedule Jan 11 15:15:20 Tower tvheadend[18]: spawn: Downloaded 3557 programs in 19 seconds Jan 11 15:15:21 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: grab took 22 seconds Jan 11 15:15:21 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: parse took 0 seconds Jan 11 15:15:21 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: channels tot= 16 new= 0 mod= 0 Jan 11 15:15:21 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: brands tot= 0 new= 0 mod= 0 Jan 11 15:15:21 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: seasons tot= 2997 new= 132 mod= 132 Jan 11 15:15:21 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: episodes tot= 3083 new= 459 mod= 459 Jan 11 15:15:21 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: broadcasts tot= 3083 new= 478 mod= 479 Jan 11 15:15:21 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: grab /usr/local/bin/tv_grab_na_dd Jan 11 15:15:21 Tower tvheadend[18]: spawn: Executing "/usr/local/bin/tv_grab_na_dd" Jan 11 15:15:22 Tower tvheadend[18]: spawn: using config filename /nonexistent/.xmltv/tv_grab_na_dd.conf Jan 11 15:15:24 Tower tvheadend[18]: spawn: Fetching from Schedules Direct Fetched 3480 k/bytes in 2 seconds Jan 11 15:15:24 Tower tvheadend[18]: spawn: loading data Jan 11 15:15:35 Tower tvheadend[18]: spawn: NOTE: Your subscription will expire: Jan 11 15:15:35 Tower tvheadend[18]: spawn: Writing schedule Jan 11 15:15:40 Tower tvheadend[18]: spawn: Downloaded 3557 programs in 18 seconds Jan 11 15:15:40 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: grab took 19 seconds Jan 11 15:15:40 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: parse took 0 seconds Jan 11 15:15:40 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: channels tot= 16 new= 0 mod= 0 Jan 11 15:15:40 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: brands tot= 0 new= 0 mod= 0 Jan 11 15:15:40 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: seasons tot= 2997 new= 0 mod= 0 Jan 11 15:15:40 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: episodes tot= 3083 new= 0 mod= 0 Jan 11 15:15:40 Tower tvheadend[18]: /usr/local/bin/tv_grab_na_dd: broadcasts tot= 3083 new= 0 mod= 0 Thanks in advance for any suggestions! Rob

I just checked and CPU went from ~15% to ~35% on i5 4590. WG++ is very resource hungry and the grabbing for schedules direct is poorly written in my opinion. Thanks for the quick response, saarg! I'm running an old Sempron 145 (2.8GHz) so I guess that is to be expected, then. I have to agree with your comment about it being poorly written, based on my experience with the same hardware and mc2xml. Thanks again! FYI for US Schedules Direct users: I set up an ubuntu 14.04 docker with XMLTV and it works as it should. I can now grab 14 days of data for 16 channels in about 25 seconds (6MB file). My old CPU still spikes to 100%, but only for 20 seconds instead of 10 hours. I thought this might be of interest to those that are in a similar boat. I'll put together an unraid template for it as an alternative for those in the same boat. WG++ seems awesome, but just not for Schedules Direct users.

I just checked and CPU went from ~15% to ~35% on i5 4590. WG++ is very resource hungry and the grabbing for schedules direct is poorly written in my opinion. Thanks for the quick response, saarg! I'm running an old Sempron 145 (2.8GHz) so I guess that is to be expected, then. I have to agree with your comment about it being poorly written, based on my experience with the same hardware and mc2xml. Thanks again!

Is everyone else pegging their CPU's at 100% every time WG++ goes to work? I'm using schedules direct and during the (very long) grabbing period, the CPU is at 100% the entire time. mdb post processing is off, and I'm grabbing 16 channels. I used to do this with mc2xml with 32-bit unraid, and the entire grab only took a few minutes without adding hardly any CPU load. Thoughts?

To add to the feedback: I also used method 1 and the server did not boot due to the missing syslinux folder on the flash drive. Like others, I downloaded the latest zip file from limetech, copied the syslinux folder over to the flash, ran make_bootable.bat, and then it booted perfectly into 6.1.3.