| View previous topic :: View next topic |
| Author |
Message |
moonguide
Replay fan
Joined: 16 Jun 2011
Posts: 53
|
 Posted: Mon Jan 16, 2012 9:00 pm Post subject: Sending recording schedule from WiRNS to Replay 4xxx |
 |
|
What causes the recording schedules I do with WiRNS to get to my Replay 4xxx? I received instructions some time ago, but they don't seem to be working. When I schedule a program to be recorded I don't see it on the Replay list of shows to be recorded until the next day, and sometimes longer than that. The instructions I have are as follows:
1. Schedule recordings with WiRNS.
2. Click on Configuration > Replays > Net Connect
3. Click on Tools > Replay Guide > Refresh
4 Click on Tools > ToDo > Refresh
I did this last night. I happened to be working from my laptop in front of the TV so I watched the Replay "power off" after executed step 2. I powered the Replay back on and saw the message telling me about the things it was doing. None of those things appeared to relate to transferring the programming schedule I just did. I waited until it was finished I continued with steps 3 and 4. Nothing new appeared on the ToDo list.
What am I missing?
Thanks.
_________________
Regards,
Moonguide |
|
| Back to top |
|
 |
hdonzis
Moderator
Joined: 05 Jan 2005
Posts: 7830
Location: San Antonio, TX
|
| Posted: Mon Jan 16, 2012 10:44 pm Post subject: |
|
|
The main thing about a 4K and lower models is that they require a net connect in order to transfer show scheduling information (which is the MyReplayTV.com interface). So, this means getting the RTV to perform a net connect is key. The "Net Connect" button in WiRNS only works if the RTV is doing pretty much nothing. It uses the same mechanism that one would use from the RTV remote control...
So, here's how I would check things out:
1. Schedule recordings with WiRNS.
2. Turn on the RTV-connected TV and make sure it is viewing the RTV (regardless of if the RTV is turned on or off, just leave it the way you had it, but make sure the TV is monitoring the RTV).
3. Click on Configuration > Replays > Net Connect
4. Watch the TV monitor and make sure what happens. Make sure that you see the RTV perform a net connect (you may have to manually power it on as you posted if you have WiRNS configred to power it off). And, make sure that while it is performing a net connect, when it says something like Transferring addition informaiton that you see the Please Wait picture come up.
5. Look in the WiRNS log and see what it shows for the net connect. You should see WiRNS log a net connect and you should see GetXact say that it uploaded some changes and then you should see PutXact say how many uploaded changes were successful.
If you don't see things happen in this way, then post what you did and what you observed.
Finally, if you want to see the changes from WiRNS, you only need to Refresh ToDo as it refreshes the Replay Guide first, so you don't need to do that separately (your step 3 is unnecessary if you perform your step 4). If you simply want to see the recording guide change, then you can Refresh Replay Guide and view Recording Schedule and see if the schedule change shows up...
Henry
_________________
Here's my Poop |
|
| Back to top |
|
|
moonguide
Replay fan
Joined: 16 Jun 2011
Posts: 53
|
| Posted: Tue Jan 17, 2012 5:56 pm Post subject: Resolved: Sending recording schedule to Replay 4xxx |
|
|
| hdonzis wrote: | The main thing about a 4K and lower models is that they require a net connect in order to transfer show scheduling information (which is the MyReplayTV.com interface). So, this means getting the RTV to perform a net connect is key. The "Net Connect" button in WiRNS only works if the RTV is doing pretty much nothing. It uses the same mechanism that one would use from the RTV remote control...
|
Thanks for the response. While I wasn't fully aware of the need for the Net Connect, that makes some sense. The piece that I didn't know that makes a difference is the need for the RTV to be idle while the Net Connect is in progress. This, too, makes sense now that I think about it. I couldn't say for sure but it is entirely possible that some of the times I've tried setting up new programming schedules the RTV was in the middle of recording another show. It make sense that it would prioritize a current recording over a Net Connect.
Anyway, I followed your instructions, below ...
| Quote: |
So, here's how I would check things out:
1. Schedule recordings with WiRNS.
2. Turn on the RTV-connected TV and make sure it is viewing the RTV (regardless of if the RTV is turned on or off, just leave it the way you had it, but make sure the TV is monitoring the RTV).
3. Click on Configuration > Replays > Net Connect
4. Watch the TV monitor and make sure what happens. Make sure that you see the RTV perform a net connect (you may have to manually power it on as you posted if you have WiRNS configured to power it off). And, make sure that while it is performing a net connect, when it says something like Transferring addition information that you see the Please Wait picture come up.
|
I did all of the above and saw the message about transferring additional information and the message about combining data. The messages went away and I looked at the recording schedule on the RTV. The program I just added is there.
The only thing that makes any sense to me is that in the past the RTV was busy and I wasn't aware of it.
| Quote: |
5. Look in the WiRNS log and see what it shows for the net connect. You should see WiRNS log a net connect and you should see GetXact say that it uploaded some changes and then you should see PutXact say how many uploaded changes were successful.
If you don't see things happen in this way, then post what you did and what you observed.
|
I assume these are the two events to which you referred:
[1/17/2012 17:18:46] [PLUGIN] XactProvider uploaded 1 schedule change to: 192.168.0.239
[1/17/2012 17:18:49] [PLUGIN] XactProvider 1 schedule change successful, 0 failed to: 192.168.0.239
| Quote: |
Finally, if you want to see the changes from WiRNS, you only need to Refresh ToDo as it refreshes the Replay Guide first, so you don't need to do that separately (your step 3 is unnecessary if you perform your step 4). If you simply want to see the recording guide change, then you can Refresh Replay Guide and view Recording Schedule and see if the schedule change shows up...
Henry |
This worked, too, just as you described. I refreshed ToDo and it took care of refreshing Replay Guide.
Thanks for the guidance and instructions.
_________________
Regards,
Moonguide |
|
| Back to top |
|
|
hdonzis
Moderator
Joined: 05 Jan 2005
Posts: 7830
Location: San Antonio, TX
|
| Posted: Tue Jan 17, 2012 7:53 pm Post subject: Re: Resolved: Sending recording schedule to Replay 4xxx |
|
|
| moonguide wrote: | | hdonzis wrote: | The main thing about a 4K and lower models is that they require a net connect in order to transfer show scheduling information (which is the MyReplayTV.com interface). So, this means getting the RTV to perform a net connect is key. The "Net Connect" button in WiRNS only works if the RTV is doing pretty much nothing. It uses the same mechanism that one would use from the RTV remote control...
|
Thanks for the response. While I wasn't fully aware of the need for the Net Connect, that makes some sense. The piece that I didn't know that makes a difference is the need for the RTV to be idle while the Net Connect is in progress. This, too, makes sense now that I think about it. I couldn't say for sure but it is entirely possible that some of the times I've tried setting up new programming schedules the RTV was in the middle of recording another show. It make sense that it would prioritize a current recording over a Net Connect. |
I'm not totally sure about this, but as I said, the way the Net Connect button works is by simply sending the same sequence to the RTV as you would from the remote control itself. So, if you can cause a net connect with the remote, then WiRNS can cause it as well. The 4K should probably be able to perform a net connect while it is recording, but I'm not positive about that...
| moonguide wrote: | Anyway, I followed your instructions, below ...
| Quote: |
So, here's how I would check things out:
1. Schedule recordings with WiRNS.
2. Turn on the RTV-connected TV and make sure it is viewing the RTV (regardless of if the RTV is turned on or off, just leave it the way you had it, but make sure the TV is monitoring the RTV).
3. Click on Configuration > Replays > Net Connect
4. Watch the TV monitor and make sure what happens. Make sure that you see the RTV perform a net connect (you may have to manually power it on as you posted if you have WiRNS configured to power it off). And, make sure that while it is performing a net connect, when it says something like Transferring addition information that you see the Please Wait picture come up.
|
I did all of the above and saw the message about transferring additional information and the message about combining data. The messages went away and I looked at the recording schedule on the RTV. The program I just added is there. |
You also should have seen the "Please Wait" screen flash while it said transferring addition information as it was uploading the recording schedule changes...
| moonguide wrote: | | The only thing that makes any sense to me is that in the past the RTV was busy and I wasn't aware of it. |
This is where watching and experimenting would come into play. You could just turn on the RTV and press the record button to start it recording, turn it back off, and then try the Net Connect from WiRNS to see what happens. Or, schedule a recording on the RTV and turn it off, and when it starts recording then try the Net Connect from WiRNS. Either way, you should certainly be able to see the progress in the WiRNS log. So, that should indicate if the net connect even took place or not...
But, my main point was that the RTV has to be in one of the idle screens in order to be able to command it to net connect. So, if, for example, you left in in the Replay Guide or Channel Guide, then WiRNS wouldn't be able to command it to net connect, just as you can't from the remote control either...
| moonguide wrote: | | Quote: |
5. Look in the WiRNS log and see what it shows for the net connect. You should see WiRNS log a net connect and you should see GetXact say that it uploaded some changes and then you should see PutXact say how many uploaded changes were successful.
If you don't see things happen in this way, then post what you did and what you observed.
|
I assume these are the two events to which you referred:
[1/17/2012 17:18:46] [PLUGIN] XactProvider uploaded 1 schedule change to: 192.168.0.239
[1/17/2012 17:18:49] [PLUGIN] XactProvider 1 schedule change successful, 0 failed to: 192.168.0.239 |
Yeah, sorry the first event is the GetXact event and the second event is the PutXact event. I couldn't remember if it explained that detail on those particular log messages or not. For example:
[1/17/2012 03:14:15] [PLUGIN] XactProvider skipping GetXact for: 1.2.3.4
[1/17/2012 03:14:23] [PLUGIN] XactProvider skipping PutXact for: 1.2.3.4
Specifically mentions those events. Although, you might also see log lines like:
[1/17/2012 04:22:09] [PLUGIN] XactProvider requesting ReplayGuide for: 1.2.3.4
[1/17/2012 04:22:11] [PLUGIN] XactProvider refreshing RecordingGuide, 20 of 37GB available for: 1.2.3.4
Which also doesn't detail those events. Anyway, I'm glad you were able to get the gist of what I was saying from "uploaded" and "successful" log lines...
Henry
_________________
Here's my Poop |
|
| Back to top |
|
|
moonguide
Replay fan
Joined: 16 Jun 2011
Posts: 53
|
| Posted: Wed Jan 18, 2012 9:27 am Post subject: Re: Resolved: Sending recording schedule to Replay 4xxx |
|
|
| hdonzis wrote: |
I'm not totally sure about this, but as I said, the way the Net Connect button works is by simply sending the same sequence to the RTV as you would from the remote control itself. So, if you can cause a net connect with the remote, then WiRNS can cause it as well. The 4K should probably be able to perform a net connect while it is recording, but I'm not positive about that...
<snip>
You also should have seen the "Please Wait" screen flash while it said transferring addition information as it was uploading the recording schedule changes... |
I don't recall seeing that, but I might have blinked.
| Quote: |
| moonguide wrote: | | The only thing that makes any sense to me is that in the past the RTV was busy and I wasn't aware of it. |
This is where watching and experimenting would come into play. You could just turn on the RTV and press the record button to start it recording, turn it back off, and then try the Net Connect from WiRNS to see what happens. Or, schedule a recording on the RTV and turn it off, and when it starts recording then try the Net Connect from WiRNS. Either way, you should certainly be able to see the progress in the WiRNS log. So, that should indicate if the net connect even took place or not...
But, my main point was that the RTV has to be in one of the idle screens in order to be able to command it to net connect. So, if, for example, you left in in the Replay Guide or Channel Guide, then WiRNS wouldn't be able to command it to net connect, just as you can't from the remote control either... |
I misunderstood that. Now it makes even more sense.
| Quote: |
<snip>
Anyway, I'm glad you were able to get the gist of what I was saying from "uploaded" and "successful" log lines...
Henry |
Well, yes and no. It worked yesterday but not since. After watching it work for the one program I set up for last evening I went back to WiRNS and set up another program for next Sunday. i have the morning football game scheduled with an instruction to continue recording for another 30 minutes. I wanted to schedule the afternoon game, too, but it's scheduled to start at the same time the morning game is scheduled to end. I noticed the ability with WiRNS to delay the start of a recording so I did that for 30 minutes. (I don't find that option on the RTV itself. I'm hoping it's something the RTV will do and not a feature added to a later model. Mine started out as a 4080. I replaced the 80 Gb hard drive with a 160 Gb model shortly after I bought the used RTV.)
Anyway, I checked on the RTV this morning and the second football game is not in the list of programs to be recorded. I clicked Exit on the RTV remote control and with WiRNS started a Net Connect. I didn't see any messages on the TV. The time it took WiRNS to return to the status screen was about 5 seconds and the new recording schedule still didn't have the 2nd football game.
Next, I initiated a Net Connect from the RTV. I watched most of it take place but was distracted at the point when I should have seen "Transferring additional information" so I don't know if it did or not. I'm guessing not because the 2nd football game is still not on the list.
Looking at the logs I can see that something is wrong but I don't understand how it could work one time and then not work several times after that. Also, since the RTV initiated Net Connect looked like it was working -- since it took so long and cycled through several status messages -- how could it be getting the day-to-day stuff from WiRNS and not get the recording schedule?
Normally I would extract just a few log lines, but since I'm not sure what is important, here are today's lines from the log file. (Anon is the name of the virtual machine running WiRNS. Family Room is the name of the RTV.)
[1/17/2012 21:12:59] Updating ReplayGuide/ToDo information
[1/17/2012 21:12:59] Stopping ToDo Timer
[1/17/2012 21:12:59] Processing ReplayGuide Information.
[1/17/2012 21:12:59] Processing local shows.
[1/17/2012 21:12:59] Processing local shows done.
[1/17/2012 21:12:59] Refreshing Replays.
[1/17/2012 21:12:59] Refreshing RecordingGuide for: Family Room(192.168.0.239)
[1/17/2012 21:12:59] Parsed 12/12 entries.
[1/17/2012 21:12:59] Refreshing PhotoGuide for: Family Room
[1/17/2012 21:12:59] Found 0 files on Family Room
[1/17/2012 21:12:59] Refreshing RecordingGuide for: anon(192.168.0.240)
[1/17/2012 21:12:59] Parsed 0/0 entries.
[1/17/2012 21:12:59] Refreshing Replays done.
[1/17/2012 21:12:59] Refreshing ReplayGuide information.
[1/17/2012 21:12:59] Added 0 ReplayGuide shows for anon
[1/17/2012 21:12:59] Added 2 ReplayGuide shows for Family Room
[1/17/2012 21:12:59] Added 0 ReplayGuide shows for all
[1/17/2012 21:12:59] Refreshing ReplayGuide information done.
[1/17/2012 21:12:59] Checking for shows to hide from Poopli.
[1/17/2012 21:12:59] Checking for shows to hide from Poopli done.
[1/17/2012 21:12:59] Updating ReplayGuide flags...
[1/17/2012 21:13:00] Updated ReplayGuide flags in 0.050072 seconds.
[1/17/2012 21:13:00] Uploading ReplayGuide data to Poopli.
[1/17/2012 21:13:01] Uploading ReplayGuide data to Poopli done.
[1/17/2012 21:13:01] Scheduling JIT Recordings
[1/17/2012 21:13:01] Scheduling JIT Recordings complete
[1/17/2012 21:13:01] Checking Manual Recordings.
[1/17/2012 21:13:02] Checking One-Time Recordings.
[1/17/2012 21:13:02] Added 8 One-Time Recordings to the database.
[1/17/2012 21:13:02] Processing ToDo Information.
[1/17/2012 21:13:02] Building ToDo List for: Family Room
[1/17/2012 21:13:04] Added 10 ToDo entries for Family Room in 2.103024 seconds.
[1/17/2012 21:13:04] Determining conflicts...
[1/17/2012 21:13:04] Completed conflict determination in 0 seconds.
[1/17/2012 21:13:04] Done.
[1/17/2012 21:13:05] Configured to refresh ToDo and Replay Guide every 240 minutes.
[1/17/2012 21:13:05] Update of ReplayGuide/ToDo information done
[1/18/2012 01:12:59] Updating ReplayGuide/ToDo information
[1/18/2012 01:12:59] Stopping ToDo Timer
[1/18/2012 01:12:59] Processing ReplayGuide Information.
[1/18/2012 01:12:59] Processing local shows.
[1/18/2012 01:12:59] Processing local shows done.
[1/18/2012 01:12:59] Refreshing Replays.
[1/18/2012 01:13:04] Refreshing RecordingGuide for: Family Room(192.168.0.239)
[1/18/2012 01:13:04] There was an error refreshing the recording guide for Family Room
[1/18/2012 01:13:04] Attempting to use a cached version if one is available.
[1/18/2012 01:13:04] Parsed 12/12 entries.
[1/18/2012 01:13:04] Refreshing RecordingGuide for: anon(192.168.0.240)
[1/18/2012 01:13:04] Parsed 0/0 entries.
[1/18/2012 01:13:04] Refreshing Replays done.
[1/18/2012 01:13:04] Refreshing ReplayGuide information.
[1/18/2012 01:13:04] Added 0 ReplayGuide shows for anon
[1/18/2012 01:13:04] Added 2 ReplayGuide shows for Family Room
[1/18/2012 01:13:04] Added 0 ReplayGuide shows for all
[1/18/2012 01:13:04] Refreshing ReplayGuide information done.
[1/18/2012 01:13:04] Checking for shows to hide from Poopli.
[1/18/2012 01:13:04] Checking for shows to hide from Poopli done.
[1/18/2012 01:13:04] Updating ReplayGuide flags...
[1/18/2012 01:13:04] Updated ReplayGuide flags in 0.050072 seconds.
[1/18/2012 01:13:04] Uploading ReplayGuide data to Poopli.
[1/18/2012 01:13:05] Uploading ReplayGuide data to Poopli done.
[1/18/2012 01:13:05] Scheduling JIT Recordings
[1/18/2012 01:13:05] Scheduling JIT Recordings complete
[1/18/2012 01:13:06] Checking Manual Recordings.
[1/18/2012 01:13:07] Checking One-Time Recordings.
[1/18/2012 01:13:07] Added 8 One-Time Recordings to the database.
[1/18/2012 01:13:07] Processing ToDo Information.
[1/18/2012 01:13:07] Building ToDo List for: Family Room
[1/18/2012 01:13:09] Added 10 ToDo entries for Family Room in 2.09301 seconds.
[1/18/2012 01:13:09] Determining conflicts...
[1/18/2012 01:13:09] Completed conflict determination in 0 seconds.
[1/18/2012 01:13:09] Done.
[1/18/2012 01:13:09] Configured to refresh ToDo and Replay Guide every 240 minutes.
[1/18/2012 01:13:09] Update of ReplayGuide/ToDo information done
[1/18/2012 02:08:45] [DNS] Returning 192.168.0.240 for production.replaytv.net to 192.168.0.102
[1/18/2012 02:08:45] [PLUGIN] LoginLogout Skipping Login (nightly) for 192.168.0.102
[1/18/2012 02:08:45] [DNS] Returning 192.168.0.240 for ntp-production.replaytv.net to 192.168.0.102
[1/18/2012 02:08:45] [NTP] Proxying request to pool.ntp.org for 192.168.0.102
[1/18/2012 02:08:45] [NTP] Proxying request to pool.ntp.org for 192.168.0.102
[1/18/2012 02:08:45] [NTP] Proxying request to pool.ntp.org for 192.168.0.102
[1/18/2012 02:08:45] [NTP] Proxying request to pool.ntp.org for 192.168.0.102
[1/18/2012 02:08:45] [NTP] Proxying request to pool.ntp.org for 192.168.0.102
[1/18/2012 02:08:46] [PLUGIN] AuthCtrl Processing Time Verification for 192.168.0.102
[1/18/2012 02:08:46] [PLUGIN] AuthCtrl Processing Auth Categories for 192.168.0.102
[1/18/2012 02:08:46] [PLUGIN] ZipcodeProvider: Added 1 lineup for 192.168.0.102.
[1/18/2012 02:08:47] Hijacking headend request for WiRNS lineup 1 from 192.168.0.102, because we serve it locally with 461 channels.
[1/18/2012 02:08:48] Serving guide data for: 2012-01-18 to 192.168.0.102
[1/18/2012 02:08:52] Loaded 11891 shows for 461 channels in 3.41491 second(s).
[1/18/2012 02:09:00] Serving guide data for: 2012-01-19 to 192.168.0.102
[1/18/2012 02:09:04] Loaded 11841 shows for 461 channels in 3.394881 second(s).
[1/18/2012 02:09:12] Serving guide data for: 2012-01-21 to 192.168.0.102
[1/18/2012 02:09:16] Loaded 12122 shows for 461 channels in 3.885587 second(s).
[1/18/2012 02:09:24] Serving guide data for: 2012-01-25 to 192.168.0.102
[1/18/2012 02:09:28] Loaded 11810 shows for 461 channels in 3.565126 second(s).
[1/18/2012 02:09:35] Serving guide data for: 2012-01-30 to 192.168.0.102
[1/18/2012 02:09:38] Loaded 469 shows for 461 channels in 1.91275 second(s).
[1/18/2012 02:09:38] [PLUGIN] NoReplayZones initialized (rz-home) for 192.168.0.102.
[1/18/2012 02:09:38] [PLUGIN] NoReplayZones initialized (rz-more) for 192.168.0.102.
[1/18/2012 02:09:38] [PLUGIN] NoReplayZones initialized (rz-xzone) for 192.168.0.102.
[1/18/2012 02:09:39] [PLUGIN] NoReplayZones initialized (rz-sitcom) for 192.168.0.102.
[1/18/2012 02:09:39] [PLUGIN] NoReplayZones initialized (rz-scifi2) for 192.168.0.102.
[1/18/2012 02:09:39] [PLUGIN] NoReplayZones initialized (rz-music) for 192.168.0.102.
[1/18/2012 02:09:40] [PLUGIN] NoReplayZones initialized (rz-sports) for 192.168.0.102.
[1/18/2012 02:09:40] [PLUGIN] NoReplayZones initialized (rz-family) for 192.168.0.102.
[1/18/2012 02:09:40] [PLUGIN] NoReplayZones initialized (rz-movies) for 192.168.0.102.
[1/18/2012 02:09:41] [PLUGIN] NoReplayZones initialized (sys-setup-gaea) for 192.168.0.102.
[1/18/2012 02:09:41] [PLUGIN] NoReplayZones initialized (sys-parentalcontrol) for 192.168.0.102.
[1/18/2012 02:09:41] [PLUGIN] NoReplayZones initialized (sys-customize) for 192.168.0.102.
[1/18/2012 02:09:41] [PLUGIN] NoReplayZones initialized (sys-mainMenu) for 192.168.0.102.
[1/18/2012 02:09:42] [PLUGIN] NoReplayZones initialized (messages) for 192.168.0.102.
[1/18/2012 02:09:42] [PLUGIN] NoReplayZones initialized (amgr-grp1) for 192.168.0.102.
[1/18/2012 02:09:42] [PLUGIN] XactProvider uploaded 1 schedule change to: 192.168.0.102
[1/18/2012 02:09:43] [PLUGIN] XactProvider 0 schedule changes successful, 1 failed to: 192.168.0.102
[1/18/2012 02:09:44] [PLUGIN] GetNextCall initialized.
[1/18/2012 02:09:44] [PLUGIN] GetNextCall Time: 02:08 for 12 min to 192.168.0.102.
[1/18/2012 02:09:44] [PLUGIN] NoServers initialized.
[1/18/2012 02:09:44] [PLUGIN] MyPhoneNumbers initialized (global) for 192.168.0.102.
[1/18/2012 02:09:44] [PLUGIN] MyPhoneNumbers (global) returning configured phone number for 192.168.0.102.
[1/18/2012 02:09:44] [PLUGIN] GetShellCommands initialized.
[1/18/2012 02:09:44] [PLUGIN] GetShellCommands using shellcmds from: C:\WiRNS\shellcmds for 192.168.0.102
[1/18/2012 02:09:45] [PLUGIN] NoSoftwareUpdate initialized.
[1/18/2012 02:09:45] [PLUGIN] LoginLogout Skipping Logout (nightly) for 192.168.0.102
[1/18/2012 05:12:59] Updating ReplayGuide/ToDo information
[1/18/2012 05:12:59] Stopping ToDo Timer
[1/18/2012 05:12:59] Processing ReplayGuide Information.
[1/18/2012 05:12:59] Processing local shows.
[1/18/2012 05:12:59] Processing local shows done.
[1/18/2012 05:12:59] Refreshing Replays.
[1/18/2012 05:13:04] Refreshing RecordingGuide for: Family Room(192.168.0.239)
[1/18/2012 05:13:04] There was an error refreshing the recording guide for Family Room
[1/18/2012 05:13:04] Attempting to use a cached version if one is available.
[1/18/2012 05:13:04] Parsed 12/12 entries.
[1/18/2012 05:13:04] Refreshing RecordingGuide for: anon(192.168.0.240)
[1/18/2012 05:13:04] Parsed 0/0 entries.
[1/18/2012 05:13:04] Refreshing Replays done.
[1/18/2012 05:13:04] Refreshing ReplayGuide information.
[1/18/2012 05:13:04] Added 0 ReplayGuide shows for anon
[1/18/2012 05:13:04] Added 2 ReplayGuide shows for Family Room
[1/18/2012 05:13:04] Added 0 ReplayGuide shows for all
[1/18/2012 05:13:04] Refreshing ReplayGuide information done.
[1/18/2012 05:13:04] Checking for shows to hide from Poopli.
[1/18/2012 05:13:04] Checking for shows to hide from Poopli done.
[1/18/2012 05:13:04] Updating ReplayGuide flags...
[1/18/2012 05:13:04] Updated ReplayGuide flags in 0.050072 seconds.
[1/18/2012 05:13:04] Uploading ReplayGuide data to Poopli.
[1/18/2012 05:13:05] Uploading ReplayGuide data to Poopli done.
[1/18/2012 05:13:05] Scheduling JIT Recordings
[1/18/2012 05:13:05] Scheduling JIT Recordings complete
[1/18/2012 05:13:06] Checking Manual Recordings.
[1/18/2012 05:13:07] Checking One-Time Recordings.
[1/18/2012 05:13:07] Added 8 One-Time Recordings to the database.
[1/18/2012 05:13:07] Processing ToDo Information.
[1/18/2012 05:13:07] Building ToDo List for: Family Room
[1/18/2012 05:13:09] Added 10 ToDo entries for Family Room in 2.062966 seconds.
[1/18/2012 05:13:09] Determining conflicts...
[1/18/2012 05:13:09] Completed conflict determination in 0.0100144 seconds.
[1/18/2012 05:13:09] Done.
[1/18/2012 05:13:09] Configured to refresh ToDo and Replay Guide every 240 minutes.
[1/18/2012 05:13:09] Update of ReplayGuide/ToDo information done
[1/18/2012 08:07:47] Starting netconnect for Replay at 192.168.0.239
[1/18/2012 08:09:34] [DNS] Returning 192.168.0.240 for production.replaytv.net to 192.168.0.102
[1/18/2012 08:09:34] [PLUGIN] LoginLogout Skipping Login (nightly) for 192.168.0.102
[1/18/2012 08:09:34] [DNS] Returning 192.168.0.240 for ntp-production.replaytv.net to 192.168.0.102
[1/18/2012 08:09:34] [NTP] Proxying request to pool.ntp.org for 192.168.0.102
[1/18/2012 08:09:34] [NTP] Proxying request to pool.ntp.org for 192.168.0.102
[1/18/2012 08:09:34] [NTP] Proxying request to pool.ntp.org for 192.168.0.102
[1/18/2012 08:09:34] [NTP] Proxying request to pool.ntp.org for 192.168.0.102
[1/18/2012 08:09:34] [NTP] Proxying request to pool.ntp.org for 192.168.0.102
[1/18/2012 08:09:35] [PLUGIN] AuthCtrl Processing Time Verification for 192.168.0.102
[1/18/2012 08:09:35] [PLUGIN] AuthCtrl Processing Auth Categories for 192.168.0.102
[1/18/2012 08:09:35] [PLUGIN] ZipcodeProvider: Added 1 lineup for 192.168.0.102.
[1/18/2012 08:09:36] Hijacking headend request for WiRNS lineup 1 from 192.168.0.102, because we serve it locally with 461 channels.
[1/18/2012 08:09:37] Serving guide data for: 2012-01-18 to 192.168.0.102
[1/18/2012 08:09:41] Loaded 11891 shows for 461 channels in 3.424925 second(s).
[1/18/2012 08:09:49] Serving guide data for: 2012-01-19 to 192.168.0.102
[1/18/2012 08:09:53] Loaded 11841 shows for 461 channels in 3.765414 second(s).
[1/18/2012 08:10:00] Serving guide data for: 2012-01-21 to 192.168.0.102
[1/18/2012 08:10:05] Loaded 12122 shows for 461 channels in 4.186019 second(s).
[1/18/2012 08:10:11] Serving guide data for: 2012-01-25 to 192.168.0.102
[1/18/2012 08:10:15] Loaded 11810 shows for 461 channels in 3.635227 second(s).
[1/18/2012 08:10:22] Serving guide data for: 2012-01-30 to 192.168.0.102
[1/18/2012 08:10:24] Loaded 469 shows for 461 channels in 1.922765 second(s).
[1/18/2012 08:10:25] [PLUGIN] NoReplayZones initialized (rz-home) for 192.168.0.102.
[1/18/2012 08:10:25] [PLUGIN] NoReplayZones initialized (rz-more) for 192.168.0.102.
[1/18/2012 08:10:25] [PLUGIN] NoReplayZones initialized (rz-xzone) for 192.168.0.102.
[1/18/2012 08:10:25] [PLUGIN] NoReplayZones initialized (rz-sitcom) for 192.168.0.102.
[1/18/2012 08:10:26] [PLUGIN] NoReplayZones initialized (rz-scifi2) for 192.168.0.102.
[1/18/2012 08:10:26] [PLUGIN] NoReplayZones initialized (rz-music) for 192.168.0.102.
[1/18/2012 08:10:26] [PLUGIN] NoReplayZones initialized (rz-sports) for 192.168.0.102.
[1/18/2012 08:10:27] [PLUGIN] NoReplayZones initialized (rz-family) for 192.168.0.102.
[1/18/2012 08:10:27] [PLUGIN] NoReplayZones initialized (rz-movies) for 192.168.0.102.
[1/18/2012 08:10:27] [PLUGIN] NoReplayZones initialized (sys-setup-gaea) for 192.168.0.102.
[1/18/2012 08:10:28] [PLUGIN] NoReplayZones initialized (sys-parentalcontrol) for 192.168.0.102.
[1/18/2012 08:10:28] [PLUGIN] NoReplayZones initialized (sys-customize) for 192.168.0.102.
[1/18/2012 08:10:28] [PLUGIN] NoReplayZones initialized (sys-mainMenu) for 192.168.0.102.
[1/18/2012 08:10:28] [PLUGIN] NoReplayZones initialized (messages) for 192.168.0.102.
[1/18/2012 08:10:29] [PLUGIN] NoReplayZones initialized (amgr-grp1) for 192.168.0.102.
[1/18/2012 08:10:30] [PLUGIN] GetNextCall initialized.
[1/18/2012 08:10:30] [PLUGIN] GetNextCall Time: 02:08 for 12 min to 192.168.0.102.
[1/18/2012 08:10:30] [PLUGIN] NoServers initialized.
[1/18/2012 08:10:30] [PLUGIN] MyPhoneNumbers initialized (global) for 192.168.0.102.
[1/18/2012 08:10:30] [PLUGIN] MyPhoneNumbers (global) returning configured phone number for 192.168.0.102.
[1/18/2012 08:10:31] [PLUGIN] GetShellCommands initialized.
[1/18/2012 08:10:31] [PLUGIN] GetShellCommands using shellcmds from: C:\WiRNS\shellcmds for 192.168.0.102
[1/18/2012 08:10:31] [PLUGIN] NoSoftwareUpdate initialized.
[1/18/2012 08:10:31] [PLUGIN] LoginLogout Skipping Logout (nightly) for 192.168.0.102
[1/18/2012 08:13:30] Starting netconnect for Replay at 192.168.0.239
[1/18/2012 08:16:45] NetConnect Done.
[1/18/2012 08:22:28] NetConnect Done.
[1/18/2012 09:08:39] Starting netconnect for Replay at 192.168.0.239
[1/18/2012 09:12:59] Updating ReplayGuide/ToDo information
[1/18/2012 09:12:59] Stopping ToDo Timer
[1/18/2012 09:12:59] Processing ReplayGuide Information.
[1/18/2012 09:12:59] Processing local shows.
[1/18/2012 09:12:59] Processing local shows done.
[1/18/2012 09:12:59] Refreshing Replays.
[1/18/2012 09:13:04] Refreshing RecordingGuide for: Family Room(192.168.0.239)
[1/18/2012 09:13:04] There was an error refreshing the recording guide for Family Room
[1/18/2012 09:13:04] Attempting to use a cached version if one is available.
[1/18/2012 09:13:04] Parsed 12/12 entries.
[1/18/2012 09:13:04] Refreshing RecordingGuide for: anon(192.168.0.240)
[1/18/2012 09:13:04] Parsed 0/0 entries.
[1/18/2012 09:13:04] Refreshing Replays done.
[1/18/2012 09:13:04] Refreshing ReplayGuide information.
[1/18/2012 09:13:04] Added 0 ReplayGuide shows for anon
[1/18/2012 09:13:04] Added 2 ReplayGuide shows for Family Room
[1/18/2012 09:13:04] Added 0 ReplayGuide shows for all
[1/18/2012 09:13:04] Refreshing ReplayGuide information done.
[1/18/2012 09:13:04] Checking for shows to hide from Poopli.
[1/18/2012 09:13:04] Checking for shows to hide from Poopli done.
[1/18/2012 09:13:04] Updating ReplayGuide flags...
[1/18/2012 09:13:05] Updated ReplayGuide flags in 0.050072 seconds.
[1/18/2012 09:13:05] Uploading ReplayGuide data to Poopli.
[1/18/2012 09:13:06] Uploading ReplayGuide data to Poopli done.
[1/18/2012 09:13:06] Scheduling JIT Recordings
[1/18/2012 09:13:06] Scheduling JIT Recordings complete
[1/18/2012 09:13:06] Checking Manual Recordings.
[1/18/2012 09:13:07] Checking One-Time Recordings.
[1/18/2012 09:13:07] Added 8 One-Time Recordings to the database.
[1/18/2012 09:13:07] Processing ToDo Information.
[1/18/2012 09:13:07] Building ToDo List for: Family Room
[1/18/2012 09:13:09] Added 10 ToDo entries for Family Room in 2.103024 seconds.
[1/18/2012 09:13:09] Determining conflicts...
[1/18/2012 09:13:09] Completed conflict determination in 0 seconds.
[1/18/2012 09:13:09] Done.
[1/18/2012 09:13:10] Configured to refresh ToDo and Replay Guide every 240 minutes.
[1/18/2012 09:13:10] Update of ReplayGuide/ToDo information done
WiRNS Debug Log
[1/18/2012 01:13:02] IsReplayAlive(192.168.0.239): timed out, trying again
[1/18/2012 01:13:04] IsReplayAlive(192.168.0.239): timed out
[1/18/2012 05:13:01] IsReplayAlive(192.168.0.239): timed out, trying again
[1/18/2012 05:13:04] IsReplayAlive(192.168.0.239): timed out
[1/18/2012 08:08:08] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:08:29] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:08:51] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:09:12] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:09:34] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:09:55] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:10:17] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:10:38] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:11:01] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:11:23] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:11:44] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:13:51] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:14:13] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:14:34] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:14:56] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:15:17] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:15:39] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:16:00] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:16:22] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:16:45] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:17:06] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 08:17:28] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:09:00] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:09:21] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:09:43] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:10:04] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:10:26] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:10:47] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:11:09] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:11:30] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:11:53] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:12:15] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:12:36] HTTPClient: HTTP error connecting to 192.168.0.239 (ConnectFailure)
[1/18/2012 09:13:02] IsReplayAlive(192.168.0.239): timed out, trying again
[1/18/2012 09:13:04] IsReplayAlive(192.168.0.239): timed out
_________________
Regards,
Moonguide |
|
| Back to top |
|
|
hdonzis
Moderator
Joined: 05 Jan 2005
Posts: 7830
Location: San Antonio, TX
|
| Posted: Wed Jan 18, 2012 10:05 am Post subject: Re: Resolved: Sending recording schedule to Replay 4xxx |
|
|
| moonguide wrote: | Well, yes and no. It worked yesterday but not since. After watching it work for the one program I set up for last evening I went back to WiRNS and set up another program for next Sunday. i have the morning football game scheduled with an instruction to continue recording for another 30 minutes. I wanted to schedule the afternoon game, too, but it's scheduled to start at the same time the morning game is scheduled to end. I noticed the ability with WiRNS to delay the start of a recording so I did that for 30 minutes. (I don't find that option on the RTV itself. I'm hoping it's something the RTV will do and not a feature added to a later model. Mine started out as a 4080. I replaced the 80 Gb hard drive with a 160 Gb model shortly after I bought the used RTV.)
Anyway, I checked on the RTV this morning and the second football game is not in the list of programs to be recorded. I clicked Exit on the RTV remote control and with WiRNS started a Net Connect. I didn't see any messages on the TV. The time it took WiRNS to return to the status screen was about 5 seconds and the new recording schedule still didn't have the 2nd football game.
Next, I initiated a Net Connect from the RTV. I watched most of it take place but was distracted at the point when I should have seen "Transferring additional information" so I don't know if it did or not. I'm guessing not because the 2nd football game is still not on the list.
Looking at the logs I can see that something is wrong but I don't understand how it could work one time and then not work several times after that. Also, since the RTV initiated Net Connect looked like it was working -- since it took so long and cycled through several status messages -- how could it be getting the day-to-day stuff from WiRNS and not get the recording schedule?
Normally I would extract just a few log lines, but since I'm not sure what is important, here are today's lines from the log file. (Anon is the name of the virtual machine running WiRNS. Family Room is the name of the RTV.) |
Well, attempting to schedule a recording to start late or end early simply changes the time that it tells the RTV to setup the recording. However, the RTV looks at the actual show air time when it sets up the recording, so these parameters are only to help it find the show that you want to record. Basically, you still ended up with a conflict, so that's why the second show didn't get scheduled to record...
If you looked at the WiRNS log from last night, you should have seen something like uploaded 2 schedule changes and 1 successful, 1 failed. Here are the lines of interest:
| moonguide wrote: | [1/18/2012 02:09:42] [PLUGIN] XactProvider uploaded 1 schedule change to: 192.168.0.102
[1/18/2012 02:09:43] [PLUGIN] XactProvider 0 schedule changes successful, 1 failed to: 192.168.0.102 |
Where you tried to reschedule the second recording, which is going to continue to be a conflict and fail...
From your log it looks like you need to update WiRNS, so then you can at least see what is happening when you net connect and there are no schedule changes. Once it sends the schedule change to the RTV, then it is lost, so net connecting a second time without rescheduling the recording isn't going to do anything. Once you update WiRNS, the second net connect would have produced log entries indicating that they were skipping doing anything (as I posted for examples last time), which would have made it clearer that there was nothing to schedule with subsequent net connects...
Anyway, while WiRNS can do some pretty awsome things, it can't manipulate show-based recordings so that they don't conflict. Your two choices are to schedule a manual record for the second show such that you can physically set the time that you want it to start and end recording, or take the padding off the first recording so that it doesn't conflict with the second recording. Technically, in this case, show-based recordings are more for shows that air from week to week and might change their air time, so the RTV tracks the actual air time instead of the record time. You're really setting up more of a VCR, timed recording, so you could just use a manual recording for both recordings to set them up more exactly how you want. Unfortunately, WiRNS doesn't support creating manual recordings, so you have to do them on the RTV (you can edit them from WiRNS once they are created). You also can't create Theme or Zone recordings from WiRNS either, but you can edit them once they are created on the RTV. The other difference with a manual recording is that it doesn't store the show information, so it will just say that it was a manual recording. You can edit the title and description from the RTV's Replay Guide, so you can at least keep track of what's what that way...
Henry
_________________
Here's my Poop |
|
| Back to top |
|
|
moonguide
Replay fan
Joined: 16 Jun 2011
Posts: 53
|
| Posted: Fri Jan 20, 2012 4:42 pm Post subject: Re: Resolved: Sending recording schedule to Replay 4xxx |
|
|
| hdonzis wrote: | Well, attempting to schedule a recording to start late or end early simply changes the time that it tells the RTV to setup the recording. However, the RTV looks at the actual show air time when it sets up the recording, so these parameters are only to help it find the show that you want to record. Basically, you still ended up with a conflict, so that's why the second show didn't get scheduled to record...
If you looked at the WiRNS log from last night, you should have seen something like uploaded 2 schedule changes and 1 successful, 1 failed. Here are the lines of interest:
| moonguide wrote: | [1/18/2012 02:09:42] [PLUGIN] XactProvider uploaded 1 schedule change to: 192.168.0.102
[1/18/2012 02:09:43] [PLUGIN] XactProvider 0 schedule changes successful, 1 failed to: 192.168.0.102 |
Where you tried to reschedule the second recording, which is going to continue to be a conflict and fail...
|
That makes sense, but without a deeper understanding of what's going on under the RTV hood I wouldn't have assumed as much. Now I understand more.
| Quote: | | From your log it looks like you need to update WiRNS, so then you can at least see what is happening when you net connect and there are no schedule changes. |
Do you mean up Configuration > WiRNS > [UPDATE]? How often should I be doing that?
| Quote: | Once it sends the schedule change to the RTV, then it is lost, so net connecting a second time without rescheduling the recording isn't going to do anything. Once you update WiRNS, the second net connect would have produced log entries indicating that they were skipping doing anything (as I posted for examples last time), which would have made it clearer that there was nothing to schedule with subsequent net connects...
Anyway, while WiRNS can do some pretty awsome things, it can't manipulate show-based recordings so that they don't conflict. Your two choices are to schedule a manual record for the second show such that you can physically set the time that you want it to start and end recording, or take the padding off the first recording so that it doesn't conflict with the second recording. |
Okay. The reason I added the padding is to address the issue of a game running into overtime -- or even just taking longer than the schedule allows. I think I'll do what I did last Sunday which is to check at 3:30 and see if the first game is still running. If it has finished I'll stop the recording save the recorded segment, and start recording the second game. If I miss some of the beginning of the second game I'm not concerned.
| Quote: | | Technically, in this case, show-based recordings are more for shows that air from week to week and might change their air time, so the RTV tracks the actual air time instead of the record time. You're really setting up more of a VCR, timed recording, so you could just use a manual recording for both recordings to set them up more exactly how you want. |
I should probably do this in case something keeps me from checking at 3:30.
| Quote: | Unfortunately, WiRNS doesn't support creating manual recordings, so you have to do them on the RTV (you can edit them from WiRNS once they are created). You also can't create Theme or Zone recordings from WiRNS either, but you can edit them once they are created on the RTV. The other difference with a manual recording is that it doesn't store the show information, so it will just say that it was a manual recording. You can edit the title and description from the RTV's Replay Guide, so you can at least keep track of what's what that way...
Henry |
Thanks for all the info.
I'm seeing some errors related IsReplayAlive, but this probably should be a separate post. I'll create one with IsReplayAlive in the subject.
_________________
Regards,
Moonguide |
|
| Back to top |
|
|
hdonzis
Moderator
Joined: 05 Jan 2005
Posts: 7830
Location: San Antonio, TX
|
| Posted: Fri Jan 20, 2012 10:20 pm Post subject: Re: Resolved: Sending recording schedule to Replay 4xxx |
|
|
| moonguide wrote: | | hdonzis wrote: | Well, attempting to schedule a recording to start late or end early simply changes the time that it tells the RTV to setup the recording. However, the RTV looks at the actual show air time when it sets up the recording, so these parameters are only to help it find the show that you want to record. Basically, you still ended up with a conflict, so that's why the second show didn't get scheduled to record...
If you looked at the WiRNS log from last night, you should have seen something like uploaded 2 schedule changes and 1 successful, 1 failed. Here are the lines of interest:
| moonguide wrote: | [1/18/2012 02:09:42] [PLUGIN] XactProvider uploaded 1 schedule change to: 192.168.0.102
[1/18/2012 02:09:43] [PLUGIN] XactProvider 0 schedule changes successful, 1 failed to: 192.168.0.102 |
Where you tried to reschedule the second recording, which is going to continue to be a conflict and fail...
|
That makes sense, but without a deeper understanding of what's going on under the RTV hood I wouldn't have assumed as much. Now I understand more. |
Well, I didn't make up the way that the MyReplayTV interface works nor how remote scheduling operates on the 4K... 
| moonguide wrote: | | Quote: | | From your log it looks like you need to update WiRNS, so then you can at least see what is happening when you net connect and there are no schedule changes. |
Do you mean up Configuration > WiRNS > [UPDATE]? How often should I be doing that? |
That's completely up to you. I guess you could read these forums to see when updates are posted, or you could just try updating every once in awhile. The update I made to make the XactProvider log better was a pretty good while ago: http://planetreplay.com/phpBB2/viewtopic.php?p=79680#79680. You also can configure automatic updates in WiRNS...
| moonguide wrote: | | Quote: | Once it sends the schedule change to the RTV, then it is lost, so net connecting a second time without rescheduling the recording isn't going to do anything. Once you update WiRNS, the second net connect would have produced log entries indicating that they were skipping doing anything (as I posted for examples last time), which would have made it clearer that there was nothing to schedule with subsequent net connects...
Anyway, while WiRNS can do some pretty awsome things, it can't manipulate show-based recordings so that they don't conflict. Your two choices are to schedule a manual record for the second show such that you can physically set the time that you want it to start and end recording, or take the padding off the first recording so that it doesn't conflict with the second recording. |
Okay. The reason I added the padding is to address the issue of a game running into overtime -- or even just taking longer than the schedule allows. I think I'll do what I did last Sunday which is to check at 3:30 and see if the first game is still running. If it has finished I'll stop the recording save the recorded segment, and start recording the second game. If I miss some of the beginning of the second game I'm not concerned.
| Quote: | | Technically, in this case, show-based recordings are more for shows that air from week to week and might change their air time, so the RTV tracks the actual air time instead of the record time. You're really setting up more of a VCR, timed recording, so you could just use a manual recording for both recordings to set them up more exactly how you want. |
I should probably do this in case something keeps me from checking at 3:30. |
Yeah, I know exactly what you're trying to accomplish and I'm just giving you different ideas on how to accomplish it. Unfortunately, as far as automatic recordings go, if you want to record a show later than the start time, I don't think there's any other way than to schedule a manual recording. That's automatic. If you want to manually record a show late, then that's no problem either...
| moonguide wrote: | | I'm seeing some errors related IsReplayAlive, but this probably should be a separate post. I'll create one with IsReplayAlive in the subject. |
I saw those and was going to mention you that you were obviously having a problem with that RTV, but I figured you were already aware of it and were more concerned about remote scheduling issues...
Henry
_________________
Here's my Poop |
|
| Back to top |
|
|
moonguide
Replay fan
Joined: 16 Jun 2011
Posts: 53
|
| Posted: Sat Jan 21, 2012 10:48 am Post subject: Re: Resolved: Sending recording schedule to Replay 4xxx |
|
|
| hdonzis wrote: | | moonguide wrote: | | Quote: | | From your log it looks like you need to update WiRNS, so then you can at least see what is happening when you net connect and there are no schedule changes. |
Do you mean up Configuration > WiRNS > [UPDATE]? How often should I be doing that? |
That's completely up to you. I guess you could read these forums to see when updates are posted, or you could just try updating every once in awhile. The update I made to make the XactProvider log better was a pretty good while ago: http://planetreplay.com/phpBB2/viewtopic.php?p=79680#79680. You also can configure automatic updates in WiRNS... |
Sounds like automatic updates is what I should have done from the start.
| moonguide wrote: | The reason I added the padding is to address the issue of a game running into overtime -- or even just taking longer than the schedule allows. I think I'll do what I did last Sunday which is to check at 3:30 and see if the first game is still running. If it has finished I'll stop the recording save the recorded segment, and start recording the second game. If I miss some of the beginning of the second game I'm not concerned.
| Quote: | | Technically, in this case, show-based recordings are more for shows that air from week to week and might change their air time, so the RTV tracks the actual air time instead of the record time. You're really setting up more of a VCR, timed recording, so you could just use a manual recording for both recordings to set them up more exactly how you want. |
I should probably do this in case something keeps me from checking at 3:30. |
Yeah, I know exactly what you're trying to accomplish and I'm just giving you different ideas on how to accomplish it. Unfortunately, as far as automatic recordings go, if you want to record a show later than the start time, I don't think there's any other way than to schedule a manual recording. That's automatic. If you want to manually record a show late, then that's no problem either...[/quote]
Understood. I've set up a manual recording starting at 4:00 tomorrow afternoon and running till 7:00.
| moonguide wrote: | | I'm seeing some errors related IsReplayAlive, but this probably should be a separate post. I'll create one with IsReplayAlive in the subject. |
I saw those and was going to mention you that you were obviously having a problem with that RTV, but I figured you were already aware of it and were more concerned about remote scheduling issues...
Henry[/quote]
Thanks. I've responded over there, too.
_________________
Regards,
Moonguide |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
