Log in

View Full Version : Erro in Disc Info Scenarist BD [Solved]

jmsmarcelo
26th August 2015, 18:42
Please help,

Warning : The size of layer0 may be larger than the max layer size. (Size: 453,121,892,825bytes, MaxSize: 25,025,314,816bytes)

Layer0 (18%) used.

Video Size: 3,987,439,852 bits, Time: 00:26:35:08, Bit Rate: 34,999,296bps, Frame Rate: 23.976fps, Format: MPEG-4 AVC

encoded with Cinevision:

Bite Rate:
Base Target: 20.00 Mbps, Base Maximum: 35.00 Mbps, Maximum Quantization: 70%

http://s6.postimg.org/cg7rrcwr5/Erro_View1.jpg
http://s6.postimg.org/ti0ltgbm9/Erro_View2.jpg
Alex-Kid
27th August 2015, 19:48
It happened the same to me, but then I realized Scenarist was wrong, because it shows the resulting files are about 100 times bigger! Percentage (18%) shows the correct space used.

Continue MUX though warnings were detected? CONTINUE.

This way I got a BD with no errors.
jmsmarcelo
28th August 2015, 00:43
I managed to fix the bug :D
Open Regedit: HKEY_CURRENT_USER\SOFTWARE\Scenarist\Scenarist BD
Edit MuxStreamSizeCoef: 1,06 to 1
Or uses this patch to fix bug
Alex-Kid
28th August 2015, 14:20
Thanks for this fix! :D
neil wilkes
25th August 2017, 11:14
That's a weird bug.
What build of Scenarist BD is it found in, please?
(I ask only because I have not as yet seen it in 5.3.2 or 5.7, and am not sure if my copy needs to be patched and I have not yet renewed my support deal with Scenarist LLC)
jmsmarcelo
28th August 2017, 12:49
That's a weird bug.
What build of Scenarist BD is it found in, please?
(I ask only because I have not as yet seen it in 5.3.2 or 5.7, and am not sure if my copy needs to be patched and I have not yet renewed my support deal with Scenarist LLC)

Hello, This bug does not affect the project, it only returns wrong information of the final project size in Disc Info. This error appeared in version 6.0, and fixed in v6.1.2.
neil wilkes
29th August 2017, 09:02
Hello, This bug does not affect the project, it only returns wrong information of the final project size in Disc Info. This error appeared in version 6.0, and fixed in v6.1.2.

Ah - that explains why I have not seen it - not (yet) updated to this build (although I will be in October once this years big workload is done)