Timing.Info creator support thread.

[mvallevand]

Thanks Martin. I have had some recent problems with files where the timeline went way out of whack so might help, but that may be just a poor recorded timeline to start with. I have had some resume issues though. Couple of quick additional q's:

I moved it out of the announcement thread to the support forum so I can keep the announcement part going.

1. Should/can I call from postprocessing.bat? If yes I will put it in the Scripts folder.

Definitely not, it would be a waste of time. writeTime is meant to work with files that don't have a Timing.Info and is not a utility to fix a timeline.

2. If yes, then syntax would be writeTime %1?

No it would be "\Pathto\writeTime" "%1" but it is not a good idea in postprocessing.bat

3. Will filename.ts.Timing.Info be deleted from the folder when the show is deleted (I would like it to be).

Yes, it does for me, but in my config.xml I do have <DeleteAdditionalExtensions>Timing.Info,....

Martin

[jksmurf]

I moved it out of the announcement thread to the support forum so I can keep the announcement part going.

OK

Definitely not, it would be a waste of time. writeTime is meant to work with files that don't have a Timing.Info and is not a utility to fix a timeline.

I don't understand.... no .ts file has an associated Timing.Info file by default anyway?

No it would be "\Pathto\writeTime" "%1" but it is not a good idea in postprocessing.bat

OK. So it is NOT needed by default?

Yes, it does for me, but in my config.xml I do have <DeleteAdditionalExtensions>Timing.Info,.... Martin

OK

k.

[sub]

Definitely not, it would be a waste of time. writeTime is meant to work with files that don't have a Timing.Info and is not a utility to fix a timeline.

I don't understand.... no .ts file has an associated Timing.Info file by default anyway?

All recordings have a timing.info by default. It can either be as an embedded ADS stream (cant be seem in directory listing) or as a separate file. The only reason you wouldn't have it is if you're running some utility that recreates the .ts file, like a utility that crops it or remuxes it. ie, this utility will recreate one if you've lost the original.

[mvallevand]

If you do archive recordings to a NAS or non-NTFS drive, you could easily lose your Timing.Info so you would want to use writeTime (or command line tools) before you archive to copy the hidden Timing.Info. You could of course use writeTime afterwards but it takes more time recalculating everything.

My prime use is for OnDemand recordings that I capture with the TME software that came with my HDPVR. NextPVR and GBPVR aren't the best way to record VCR style.

Martin

[Lao Pan]

Does the ADS file follow it's parent over networks between computers with NTFS Drives?

Would it be sensible / how would you save the new timing.info to ADS?
(I normally edit programs I will keep more than a few days for padding/adverts with VideoRedo, over the network then overwrite the original back on the HTPC - would it be possible to create the new timing info as an ADS and send back together?)

[mvallevand]

Does the ADS file follow it's parent over networks between computers with NTFS Drives?

Normally yes if you use Windows tools to copy. The major issue is you never know when they aren't copied and if you don't like how it performs they are more difficult to remove.

Would it be sensible?

I decided against doing this natively in witeTime since the only value to a ADS is that it is hidden to explorer and you don't have to copy two files. The only program that uses it is NextPVR and NextPVR won't show them anyway, but normally other programs like MPC HD won't display them either because it is not a valid media type. If copying two files is the issue run writeTime on the HTPC

how would you save the new timing.info to ADS?

A batch file like this could do what you wanted

\path to\writeTime %1
if not exist  "%~1.Timing.Info" goto nextstep
more "%~1.Timing.Info" > "%~1:Timing.Info"
del "%~1.Timing.Info"
:nextstep

Martin

[Lao Pan]

Thanks for the answers Martin - I can see the advantages of being able to see the file now - just have to make sure its on the delete list in config.

[Lao Pan]

Martin

Been using version you posted yesterday, with your recursive script on individual folders successfully and just had a thought - if I set up a batch file on the Video Recordings directory and run it occasionally it should only generate the missing timing info, not redo all the ones that have been generated already. Is that correct?

[mvallevand]

Been using version you posted yesterday, with your recursive script on individual folders successfully and just had a thought - if I set up a batch file on the Video Recordings directory and run it occasionally it should only generate the missing timing info, not redo all the ones that have been generated already. Is that correct?

That's right, by default it won't recreate an external Timing.Info if it has one, and it also won't copy the hidden ADS file. Since you probably want to break this especially if you have lots of files, you might want to consider something like

for /R %%i in (*.ts) do call :timing "%%i"
goto :exit
:timing
@echo %1 > c:\temp\current.txt
\Path To\writeTime "%1"
:exit

The current.txt file will show you the file that is being worked on if you abort. You probably will want to delete the Timing.Info Note that it is only %1 in the subroutine and that is not the same %1 has the original batch file.

Martin