DVD-RB 0.65 mutiangle bug

[The eDealer]

Hi jdobbs,
i have problems with multiangle DVD:
I started the conversion "Troy" (RC2) and in addition to the output- and sizebug (http://forum.doom9.org/showthread.php?s=&threadid=84019), i have two other problems:
1. It seams to be that the items in the avs editor are not used, because the result is not croped (no overscan)?!
2. With the beginning of the second cell, the selected german audiostream is gone (no sound anymore)?

If you need more information, please ask.

[hobyho]

I also have an issue with multiangle with Stuart Little 2 (R4). The problem is after the prepare stage there are no avs files for VTS1 and DVD-RB wants to encode them.

This DVD has interleaved cells in VTS1.

[jdobbs]

Please read the readme file. The angled areas are not reencoded, they are simply remerged into the new stream. That may come later. I guess I never thought anyone would resize the main movie. Also remember -- THIS IS A BETA, and this is the FIRST RELEASE of multiangle processing. Finding bugs is what a beta is for...

[The eDealer]

Hi jdobbs,
sorry for that misunderstanding.
I only want to report problems so that they can be fixed.
Isn't that the "job" of a beta tester, to support??

I don't resize, just cropping to save BR. But it was my fault that i
don't understand the meaning of the information, sorry for that.

[hobyho]

Hi jdobbs

Any reason why DVD-RB is behaving in such a manner with that particular dvd? If you require any files please PM me to squash the bug.

[jdobbs]

@The eDealer

Sorry, didn't mean to sound unappreciative. You're right!

[lamster]

Originally posted by jdobbs
The angled areas are not reencoded, they are simply remerged into the new stream. That may come later.
I don't see any indication of how much this is hurting us. It might be nice to have some indication - at least the first; I don't know how hard it would be to estimate the second:

- 3 angles consuming 1,024KB extra space (as opposed to if angles were stripped)
- Estimated compression loss due to angle/ILVU VOBS not being compressed: 6.2%

This would help us decide if we really wanted to have as complete a backup, or if we'd be better off stripping the angles in order to make more space for the video. (Ehh, I'm probably not going to learn Japanese anyway - why keep the Japanese titles... :) )

[jdobbs]

Unfortunately when you require the user have to make those kinds of decisions, the software gets cumbersome and difficult to use. Honestly I was surprised when I saw how little space was actually being used by ILVU sections.

1,024KB is only .02% (2 ten thousandths) of a DVD. More likely you will see somewhere in the range of 150MB of total ILVU space and usually no more than two or three angles. If you stripped two angles you could save about 100MB. Now let's assume you had a two hour movie that averaged 4,100Kbs for video. Removing 100MB would raise the total average bitrate to about 4,211Kbs -- which I wouldn't believe to be noticable in most circumstances.

If you decided to keep the other two angles and compress them by a factor of, say 70% -- you'd only save about 45MB and have even less impact.

This is further complicated by the fact that multiple angles are already compressed more than standard video -- and further compressing it has more of a noticable negative impact. There may be good reasons for further compressing them... I just haven't found it yet -- except maybe for resizing and/or applying filters.

[lamster]

Originally posted by jdobbs
Unfortunately when you require the user have to make those kinds of decisions[ ...]
It's not requiring anyone to make a decision. It's just providing additional information. The knowledgable user might use it to make a decision; the naive user can ignore it along with the rest of the info output during the Prepare phase.
likely you will see somewhere in the range of 150MB of total ILVU space and usually no more than two or three angles. If you stripped two angles you could save about 100MB. Now let's assume you had a two hour movie that averaged 4,100Kbs for video. Removing 100MB would raise the total average bitrate to about 4,211Kbs -- which I wouldn't believe to be noticable in most circumstances.
For most of what I've seen that uses multiple angles / ILVU, you're correct. I was wondering about something like Daredevil, where the main movie is fine; it's the extras that have multiple angles. In this case, VTS_04_1.VOB is about 480 meg, and VTS_06_1.VOB is 644 meg, so we're talking about a total of a gig. Since I typically run with "Half-D1 and half space for extras", it seems as though if this were compressed it would free up a decent amount of space for the main movie. (Note that in this case, every program in each of those VOBs contains 3 angles, except for the intermediate ones which are blank (0.15 seconds). I'm not sure how much space this really translates into - I should probably strip them and see what the difference is.)

[jdobbs]

Understand. I'll start working the option. It may be a version or two before I release it -- I have a lot of testing yet to do on that code.

[The eDealer]

After further tests I could workaround the problems with Troy(RC2):
Fact is, the coding works if both (German and English) sound tracks are chosen. The result has exactly 4,37 GB and the German sound track is available.
Is only the german audio stream selected, the result is to small (exact 2nd audio stream) and the german audio is missing?!

The output issue is already solved here. (http://forum.doom9.org/showthread.php?s=&threadid=84019)

[The eDealer]

All problems with Troy RC2 are solved in the version 0.66a!!
Great work jdobbs. :)