PlayList_Manager & Record_This - Page 93

If you give it a try, 802.11n on the 5GHz band works better than 802.11n on the 2.4GHz band, since the 5GHz band is reserved for WiFi, and other devices can use 2.4GHz.

I have also read that many people have good luck with powerline networking.

-Dave

Allen has updated RT to be compatible with CW_EPG.

For existing RT users

All reservations can go through the CWHelper portion of CW_EPG. This eliminates the need for RT_Helper on remote PCs. Also, CWHelper handles HDHR recordings, so you no longer need HDHRCorder. Finally, CWHelper provides persistence, so HDHR and Fusion recordings interrupted by a power interruption or BSOD/reboot will resume. Also, if you boot up your PC after a reservation was scheduled to start, the recording will be started by CWHelper. Note that the MyHD application already had this functionality.


For new RT users

CW_EPG has a nice installer, so it simplifies the initial RT configuration since you do not need to manually configure HDHRCorder and RT_Helper.


For existing CW_EPG users

RT provides an easy way to insert manual reservations into CW_EPG. RT also has a few more specialized scheduling options, such as joining back-to-back programs on the same channel into a single reservation, or the ability to add additional padding to a program if a different trigger program aired earlier in the day (which works well for certain live events that delays schedules).

-Dave

ok, i was able to get the new rt+cwepg to work using hdhr and ota but something is not quite there for qam... what am i missing???

see rt log below:

07/31/10 00:11:31 Record_This: ************************************************************
07/31/10 00:11:31 Record_This: Compile date/time Jul 28 2010 11:14:29
07/31/10 00:11:31 Record_This: Ini filename Record_This.ini
07/31/10 00:11:31 Get_Next_Record: >> ChannelTable HDHRota0
07/31/10 00:11:31 Get_Next_Record: >> Channel wjctdt 70 0 1 qam256
07/31/10 00:11:31 Get_Next_Record: test_Movie [at 00:15-00:17 on wjctdt date 07/31/2010]
07/31/10 00:11:31 Get_Next_Record:
07/31/10 00:11:31 Get_Next_Record: >> local HDHR [DeviceId 10161ADA tuner 0 Folder "c:\\hdtv" Identifier HDHRota0 CWHDHR 8181]
07/31/10 00:11:31 Record_This: Run date/time 2010/07/31 0:11:31 DST 1
07/31/10 00:11:31 Record_This: Recording date 2010/07/31
07/31/10 00:11:31 HDHR_Parse_Message: HTTP/1.0 200 OK
07/31/10 00:11:31 Store_Dont_Care: >>>>>>>>>>>>>>>>>>>> Inserting manual reservation for test_Movie on 7/31/2010 at 0:15-0:17 channel wjctdt
07/31/10 00:11:31 List_Scheduled: Program 0 wjctdt 0:15- 0:17 7/31 0 test_Movie
07/31/10 00:11:31 Insert_Here: Program 0 on local HDHR tuner 0(0)
07/31/10 00:11:31 Schedule_Using_CWHDHR: CWHelper call capture?channelname=70.1&datetime=7/31/2010 0:15&datetimeend=7/31/2010 0:17&tuner=10161ADA-0&filename=c:\\hdtv\ est_Movie.tp&protocol=qam&title=test_Movie
07/31/10 00:11:31 HDHR_Parse_Message: HTTP/1.0 200 OK
07/31/10 00:11:31 HDHR_Parse_Message:

CW_EPG Helper Interface

Not able to schedule capture for 70.1 Slot: start [07/31/10 00:15:00] stop [07/31/10 00:16:59]
Sat Jul 31 00:11:31 EDT 2010 ERROR - capture was not defined.
channel 70.1 qam not found on 10142327-0 lineup.
channel 70.1 qam not found on 10142327-1 lineup.
channel 70.1 qam not found on 10161ADA-0 lineup.
channel 70.1 qam not found on 10161ADA-1 lineup.
channel 70.1 qam not found on HDTV3Silver+/3Gold.3 lineup.
channel 70.1 qam not found on MYHD lineup.

getAvailableCapturesForChannelNameAndSlot returned no captures for 70.1 10161ADA-0 Slot: start [07/31/10 00:15:00] stop [07/31/10 00:16:59]

Done

looks like rt does not like my channel definition for some reason.
here's a partial dump of my channels :


steve

Steve, your protocol needs to be "QAM256" in the captures for HDHR and Fusion. It is "QAM" only for MyHD captures. (Thanks to Dave P. for reminding me of that)

Steve,

You found the last issue that I know about.

If you look at the request, RT is sending "protocol=qam" to CWHelper. Originally, RT was sending "protocol=qam256".

During testing I asked Allen to make the change because MyHD reservations were broken. It turns out that this varies by tuner, and Fusion and HDHR want "protocol=qam256", and MyHD wants "protocol=qam". My request fixed MyHD, but broke Fusion and HDHR.

I expect that Allen will probably fix this pretty quickly.

-Dave

Edit: Terry beat me by a minute.

i wonder what an rt scheduled event for the hdpvr would look like in cwepg...

steve

I doubt you would see anything, since those reservations do not go through CWHelper, and CW_EPG and CWHelper know nothing about HD PVRs.

By the way, do you really get all those HBO channels in clear QAM?

-Dave

ok, i tried qam and qam256 and even qam64 (upper and lower case too) before posting. i thought that was already fixed from reading earlier messages...

steve

eh... no those are "fake" channels i added to one of my hdhr tuners so i could see what's on hbo. i also added a few of the "fake" hd channels after comcast encrypted some of my analogs, i watch. the hdhr does capture zero byte files when it matches shows i want.

i really use the info from the auto email to see what i have to watch live or set the hdpvr to capture.

steve

ok, this works for hdhr qam and 8svb. i didn't check fusion or myhd.

i do seem to have a problem when defining more than one hdhr tuner at the same time.

for example, one hdhr tuner on qam has its own channel table and another hdhr tuner is connected ota has a different channel map. if scheduling two captures, one on each tuner, i get an error, but if i comment out the capture and program statement individually, i can capture both.
see attached rt log and ini:

 

Record_This_Log.txt 9.5146484375k . file

 

Record_This ini.txt 0.4169921875k . file

I am not sure if this is the issue, and I don't think it explains your success. However, I think the correct usage of the channel tables and manual scheduling is to define the station call letters and the network. For example:

>> Channel KTVUDT/FOX 79 2 2 1 CABD

then refer to the network in the manual reservation:

Test_Recording [at 18:30-18:35 on FOX every A]

IIRC, it was done this way because some users lived between large cities and could get the same network from multiple sources, and this configuration provided additional scheduling flexibility.

I don't think the text you pick matters, so try defining a channel for something like KXYZDT/ABC, and then schedule to ABC.

-Dave

still the same error.

i think i found the problem. it is the way i have my ini constructed. i guess i should have read all the documentation.
here's the info:
<< The general format
<< of an ini file is to define the options, list the programs to be recorded and
<< then the card(s). Programs listed after a card will be recorded on that card.
<< Programs listed before all cards will be recorded and the first available card in
<< the card list based on an available time slot. A simple ini looks like:
<<
<< >> Option entry
<< >> Option entry
<< Program1
<< Program2
<< >> Card entry
<< >> Card entry

so, reconstructing my ini seems to have fixed the problem.
my new ini and the resulting rt log:


steve

 

Record_This ini2.txt 0.4208984375k . file

 

Record_This_Log.txt 9.5146484375k . file

(Edit: Looks like you figured it out while I was composing this, but I figured I would post it anyway after spending time writing it.)

One more thing to try. Put all your channel table statements at the top. It is possible that RT needs to read in all the channel table statements before scheduling. Then list all your shows, and then all tuners.

According to the documentation:


That means there are two possible formats. For example:

>> tuner 1
program 1
>> tuner 2
program 2

or

program 1
program 2
>> tuner 1
>> tuner 2

I think you are doing this:

program 1
>> tuner 1
program 2
>> tuner 2

So your arrangement is not what RT is expecting.

-Dave

Nothing ventured, nothing gained.

yes, i read the documentation and figured it out before the smoke got too thick...

steve

Hi Allen,

Came to download the latest PLM. Haven't been on for a year. PLM is still a vital link for me to run between GB-PVR Hauppauge for recording and MYHD for playback. Thanks for continuing to support these much appreciated apps!

Hi Allen,

Thanks for the update. My hybrid RT/CW_EPG setup is still working great!

-Dave