Can't fast forward

[johnsonx42]

Very interesting. I didn't know that. so when the drive is connected through the wd live it creates the file ( i have found it performs better with this file ) when i connect to the pc the file isn't created. I may format the drive to ntfs, i think it already is but will check

I really don't believe that the WD Live can make use of this file. This Timing.Info is sub's own creation, not part of any video file spec.

Just to be clear, the file IS created either way, it's just stored within the .ts file when the drive is connected directly to the PC.

You can extract the embedded ADS version of the Timing.Info into a separate file:

Code:

type filename.ts:Timing.Info > filename.ts.Timing.Info

[Reddwarf]

I seem to remember that there were a setting in Config.xml to store timing.info in a separate file? Or am I wrong?

[march]

Ok thanks. So npvr does create this file but is only used by npvr with playback through npvr. So i do think when the drive is connected directly to wd live that these xml files get updated, but when its through the network i don't think wd live updates them. Because its little database on the root of the drive isn't updated after this. Its like a lite sql dbase that keeps track of where you are i believe. mmmm now how do i get the wd live to update this back to the disk mmmm, lots of food for though here.

[johnsonx42]

Nor is it used on pc-clients, according to Sub.

I'm pretty sure that the PC client now uses the timing.info; I believe there was a patch that added it awhile back. I could be wrong though.

I seem to remember that there were a setting in Config.xml to store timing.info in a separate file? Or am I wrong?

There's a setting to force the metadata.xml to be created as a separate file, but not the Timing.Info (unless it's one of those hidden settings not in the Config-master). The Timing.Info gets created as an ADS when possible, and stored separately when ADS is unavailable.

[mvallevand]

There's a setting to force the metadata.xml to be created as a separate file, but not the Timing.Info (unless it's one of those hidden settings not in the Config-master). The Timing.Info gets created as an ADS when possible, and stored separately when ADS is unavailable.

It's one of those hidden registry settings, with it the filename.Timing.Info is created in additions to the ADS file.

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\NPVR]
"SeparateTimingInfo"=dword:00000001

I think there is an outstanding bug with this, only the ADS Timing.Info is sent to the PCH.

Martin

[march]

Hi everyone and thankyou for your help. I may see how it goes with the fast forward and spend some more time thinking about it. But one other thing is with the automerge of channels. I have 4 tuners. It did merge most of them but some remain unmerged and won't merge. All have exactly the same name. when i had 2 tuners it seemed to work a treat, but then i added the other two. most of the extra's merge and some remain. This is invaluable if you have more than one tuner. Can anyone assist........ again, sorry, i'm nearly there with the perfect system. I can record 5 different channels at once - very happy checked the config.xml and automerge is set to true as it should be.

[johnsonx42]

in the channels tab, click the channels you want to merge while holding the Ctrl-key, then right-click and select Merge.

[Reddwarf]

in the channels tab, click the channels you want to merge while holding the Ctrl-key, then right-click and select Merge.

I'v also seen that sometimes it's impossible to merge more that two channels at a time, one has to merge two by two until all are merged.

[march]

JOHN.......YOU ARE A CHAMPION thankyou, that worked beautifully. ))