Converting TS files to small size on the fly

[sub]

Yep, I'm pretty happy with NZ waiting as well, and ending up with H.264.

I'm guessing North America will do some big catchup in the next few years though, when they're forced to do something about 4K for broadcasts (requiring a move to H.265).

[Over]

The OP's math is still way off as Graham pointed He should get 250 hours at that bit rate and there a some channels (here anyway) that do 720p


Martin[/QUOTE]
[ATTACHMENT NOT FOUND]

This is a before and after screen shot of a directory.

6GB is straight from NextPVR, 2.5GB is using MKV Buddy.

If you know how to shrink the file size from within NextPVR, let me know.

Over

[mvallevand]

I'm not sure why you quoted me 2.5GB is what I get from my HDPVR and HDTC, my point is on your 37 files, which seems like it probably is over 300.

Martin

[Over]

Hello
I have 37 shows stored on the hard drive taking up 1.27 TB!

Each show has it's unique folder name. Some folder have more than one episode. When I stated the total disk space, I was going off the folder sizes.

Over

[Graham]

When I stated the total disk space, I was going off the folder sizes.

I misunderstood ... I get it now ... you have 37 show folders with any number of individual recordings in each folder. Apologies for raising a spurious side issue.

[longjohn119]

Yep, I'm pretty happy with NZ waiting as well, and ending up with H.264.

I'm guessing North America will do some big catchup in the next few years though, when they're forced to do something about 4K for broadcasts (requiring a move to H.265).

Are you kidding? With all the infighting between broadcast networks, broadcast affiliates and cable it took Congress over 20 years to finally set an HDTV standard ..... I wouldn't hold my breathe for 1000 or so HDTV transmitters in the US to agree to converting over to h.264 anytime in the next ten years, maybe 20

[sub]

Yeah, I hear you

I do think it's gonna have to happen within 10 years though. Things would have moved on so far by then. No one will be using MPEG-2 for anything by then.

[Tompeel]

Hi All, Reviving an old thread.

Seems like there are plenty of ways to trans code to keep file size down, not explored if there is much 265 support yet which would be ideal but i was wondering how once transcoded will the front end still read the files as "new recordings" etc. The system is mostly used by my parents and they are just about up to speed with it all now as is but i would like to streamline the storage.

what I'm asking is, is there a way the XMLs can still link the meta data to a file with the same name but different file type?

Thanks

[Graham]

... i was wondering how once transcoded will the front end still read the files as "new recordings" etc.

NextPVR stores information about recordings in the database file npvr.db3 ... http://www.nextpvr.com/nwiki/pmwiki.php?...alledParts

The stored information includes the filename and folder. Transcoding of recording files requires that the database is updated if the filename (or folder) changes (perhaps using nscripthelper.exe).

NextPVR expects recordings to be in a .TS container file (the .TS container file may contain MPEG2 or H.264 or whatever). NextPVR will dictate the decoders that are to be used for playback of .TS files using the values in NextPVR Settings --> Decoders.

NextPVR lets Windows choose the decoders for files that are not .TS files.

It is my firm opinion that you will regret the complexities that are introduced by attempts to transcode to a smaller file ... I predict that you will wish that you had bought a bigger disk instead of attempting to transcode.

[gEd]

Transcoding of recording files requires that the database is updated if the filename (or folder) changes (perhaps using nscripthelper.exe).

Whilst I agree with the main sentiment of your post, this part is not quite correct. NextPVR can search for alternative file extensions if the .ts file is not there (configurable in config.xml) so if you convert myshow.ts to myshow.mp4, it will work fine.