Timeshifting in 97.13

[jsteele]

I've just upgraded to 97.13 and had occasion to try Timeshifting today. In the first instance I tried TS on an Ad Hoc basis and received an error message:

Error item has already been added. Key in dictionary: "[x=0 ...."

The logs from this are attached as:
"timeshift-dictionary-error-20060715.zip"

I then changed the configuration to start in TS mode. In this case the system ran in TS fine EXCEPT that every hour on the hour the audio/video freezes. It is not a terminal event in that several clicks of the Back/exit button will eventually return to the main menu and I can reselect LiveTV and continue. This problem is then repeated again every hour. The lofs for this are attached to the next Post in this thread

[jsteele]

I then changed the configuration to start in TS mode. In this case the system ran in TS fine EXCEPT that every hour on the hour the audio/video freezes. It is not a terminal event in that several clicks of the Back/exit button will eventually return to the main menu and I can reselect LiveTV and continue. This problem is then repeated again every hour. The lofs for this are attached as:
"timeshift-permanent-20060715.zip"

[sub]

I've just upgraded to 97.13 and had occasion to try Timeshifting today. In the first instance I tried TS on an Ad Hoc basis and received an error message:

Error item has already been added. Key in dictionary: "[x=0 ...."

The logs from this are attached as:
"timeshift-dictionary-error-20060715.zip"

In the logs it looks like it might be a skin related error. Can you try it with the blue skin?

[sub]

I then changed the configuration to start in TS mode. In this case the system ran in TS fine EXCEPT that every hour on the hour the audio/video freezes. It is not a terminal event in that several clicks of the Back/exit button will eventually return to the main menu and I can reselect LiveTV and continue. This problem is then repeated again every hour. The lofs for this are attached as:
"timeshift-permanent-20060715.zip"

This is related to an error in your logs. I'm not sure of the cause though. I've not seen any other reports of it.

7/15/2006 1:08:12 PM.640 ERROR [1] Encounter unexpected exception in timerRefresh_Tick:Object reference not set to an instance of an object.
7/15/2006 1:08:12 PM.656 ERROR [1]
Server stack trace:
at GBPVR.RecordingService.x93f60a55016d55c4.xb8da78bd4ee79bb8(Int32 xeba3e20435eb0e32, Boolean x03f525c749695de4, String& x8b1d9e3189e6e73d, Int32& x73dd716c35ea457b)
at GBPVR.RecordingService.RecordingRemote.xb8da78bd4ee79bb8(Int32 xeba3e20435eb0e32, Boolean x03f525c749695de4, String& x8b1d9e3189e6e73d, Int32& x73dd716c35ea457b)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at GBPVR.Backend.Common.IRecordingService.xb8da78bd4ee79bb8(Int32 xeba3e20435eb0e32, Boolean x03f525c749695de4, String& x8b1d9e3189e6e73d, Int32& x73dd716c35ea457b)
at GBPVR.Backend.Common.x396614b3dae3b1da.xb8da78bd4ee79bb8(Boolean x03f525c749695de4, String& xea99cc8af6f9bef1, Programme& x5d1dc8495c0908a9)
at GBPVR.xbe83d16b02243330.RefreshOSD()
at GBPVR.xbb1566157f5f8b1f.xb1cbc922a07ef39b(Object xdf2e3583f942db7b, EventArgs xc4f45905cb1fc7ba)

[jsteele]

So where do we go from here?

Any thoughts on the "dictionary" error trying to start TS in ad hoc mode?

Overall TS runs much better for me in 97.13 than in any prior version. There is no hesitation, stuttering, etc., much better than anything i saw in 95.x for example.

[sub]

So where do we go from here?

Any thoughts on the "dictionary" error trying to start TS in ad hoc mode?

This was the thing that looked like the skin error I mentioned in my first post above. Try switching to the blue skin.

[jsteele]

OH, now I understand.

[jsteele]

Well, I changed to the default blue screen. Now when I select LiveTV and try to TS in ad hoc mode it displays the Starting TS message, then the inidcatior bar across the top and FREEZES SOLID. I have to use the TaskMgr End Process to kill GBPVR.

[jsteele]

I changed the Config to start in TS mode and that seems to start OK. I'll have to keep an eye on it to see if it freezes after an hour.

[jsteele]

Here's the latest. I have installed the BaseSkin.ContourBlue and now when KI try to run TS in ad hoc mode it freezes the video/audio. This is NOT terminal as I can hit Back/Exit and it goes back to the Main Menu. I'm currently testing fulltime TS using the BaseSkin and I'll report back if there is any problem.

Logs attached for the ad hoc TS problem.