Wrong output estimated size

[Xmonster]

Hi,

I am very satisfied this program, but there is a little problem...

Sorry, I already wrote about it in the 1.2 version, but nothing happened.
I see it exists in the current version too.
I hope, somebody read it now and it will be corrected.
I think it is not so difficult to solve.

The problem:
The output estimated size is not correct, it depends on the cutting position.
The progress bar while saving follows this wrong value.

Eg.
I have a big video file: 80 GB, 23:58:30 duration.
The free space on the output drive is 70 GB.
I cut a little part for saving, duration 01:00:00, size below 100 MB.
If the cutting position is close to the beginning, no problem.
When the position moves toward the end, the required space grows (for the  100 MB)...
If the cutting position at 23:54:00, the 70 GB is not enough, I get a warning...
I say No for the question, so the saving starts...The progress bar finishes at max. 1%...

I know it is not a big problem, but somewhat annoying...
I have to check always the free space before saving.

[Mam]

you should rethink the way of your recording 
The current broadcast standard contains an ever-ticking timer called PCR that will wrap around after ~23 hours. Recordings longer than this cannot be processed because time positions are doubled then.
You have to cut (better already record less than 23hrs in a row) the whole file with the "raw cutter" then process each part seperately.
The part containing the wrap will result into a warning ("PCR wrap detected!") when loaded into the doc, it offers to rebuild the whole file, renumbering the timer from base 0 onwards. The resulting file can then be processed normally again (UNLESS ITS STILL LONGER THAN 23hrs, ELSE THE "Fixed" VERSION WILL ALSO CONTAIN A WRAP AGAIN AND THE WHOLE ACTION IS ONLY A WASTE OF TIME).

The whole processing takes up a lot of time, is error-prone and can ruin your day. So better follow the advice and DO NOT RECORD THAT LONG !!!

[Xmonster]

Thanks Mam...

The wrap is more than 23 hours, 23,8 hours at 100 kHz base and more than 26 hours at 90 kHz base.
I rarely record such a big file, and the DVBViewer is correct, it doesn't enable recordings above the wrap limit.
So I never get PCR wrap error.

The example above was only for an extreme representation of the problem.
Sorry...

I am afraid the problem will not be solved again so I write it again with less values.

I already wrote about it in the 1.2 version, but nothing happened.
I see it exists in the current version too.
I hope, somebody read it now and it will be corrected.
I think it is not so difficult to solve.

The problem:
The output estimated size is not correct, it depends on the cutting position.
The progress bar while saving follows this wrong value.

Eg.
I have a big video file: 40 GB,12:58:30 duration.
The free space on the output drive is 30 GB.
I cut a little part for saving, duration 01:00:00, size below 100 MB.
If the cutting position is close to the beginning, no problem.
When the position moves toward the end, the required space grows (for the  100 MB)...
If the cutting position at 12:54:00, the 30 GB is not enough, I get a warning...
I say No for the question, so the saving starts...The progress bar finishes at max. 1%...

I know it is not a big problem, but somewhat annoying...
I have to check always the free space before saving.

[Xmonster]

Sorry, I am disappointed a bit...
Every other topics has a reply by Cypheros...
This little problem is easy to check, easy to correct, I think.

[Cypheros]

Your description is not correct. Independent from the cutting point, the estimated output size is identical with the input size. So, you need to have 70GB free space on the destination drive, if your input file has a size of 70GB and don't want to get a warning.
Sorry for that, it's only a guess and a warning.

At the moment I see no simple way to estimate more precisely at the moment. But I will try to find a solution in the future.

I read every message here but sometime find not the time to answer complicated questions or need some time to investigate.

[Xmonster]

Thanks for the reply....
You are right, the warning always appears.
But the second one I mentioned is true...
The end of rhe progress bar % depends on the cutting position.
I want to cut one little part with 1 minute duration.
If The cutting position is at the beginning it end at 100%.
If the position at the end of the video, the progress ends at 1%.
I thought the warning follows that too.
Sorry if I mentioned this little problem...I will never do more.

[Cypheros]

No problem, suggestions and problem reports are important to evolve the product.

As small as your problems are, don't hesitate to mention it.

Next version has a "better" estimation of the diskspace needed on the destination drive, related to the percent of time being cutted. If you cut 50% of the recording, you will need 50% + 5% (safety) of the source file size as free disk space, if you don't want the warning to appear.