<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">Den 09.12.2022 19:57, skrev Phyllis
Smith:<br>
</div>
<blockquote type="cite"
cite="mid:CAOckJE0HBXhbL=V8ad=-EDQVZYpeVAmOgoZWAntnekJyXcrbmw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr"><span class="gmail_default" style="font-size:small">Working
on bluray updated information and potential changes as I
finally got my bluray burner working again.</span><br>
<div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div><font face="Courier New, Courier, monospace"> Else I
suggest that the # comments in the manual should be
kept to explain what happends.<br>
</font></div>
</blockquote>
<div><span class="gmail_default" style="font-size:small">I
am not sure what the above is referring to. It sounds
like "the # comments should be kept" means "no
changes"? If my interpretation is incorrect, please
provide detailed information so I do not miss something.</span>
<br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div><font face="Courier New, Courier, monospace"> And
also how the mkudffs size was calculated.</font></div>
</blockquote>
<div><span class="gmail_default" style="font-size:small">I
have included the actual calculation in section 14 (not
checked into GIT yet) after the initial mention of
mkudffs in the lines:</span></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div><span class="gmail_default" style="font-size:small"></span>it
creates an empty<span class="gmail_default"
style="font-size:small"> </span>filesystem image
<target>/bd.udfs using mkudffs which makes a big
hole for<span class="gmail_default"
style="font-size:small"> </span>the filesystem data.
The hole is made just a little bigger than the data
written<span class="gmail_default"
style="font-size:small"> </span>by bdwrite<span
class="gmail_default" style="font-size:small">...</span><br>
</div>
</blockquote>
<div><span class="gmail_default" style="font-size:small">Added
line is: "</span>The actual calculation for the mkudffs
size is yourfile.m2ts size-in-bytes/2048 + 4096<span
class="gmail_default" style="font-size:small">."</span></div>
<div><span class="gmail_default" style="font-size:small">In
section 14.6, the calculation was already in the manual
as:</span></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div><span class="gmail_default" style="font-size:small">du
-sb /yourHDVfile.MTS # Determine the size of
your file in bytes.<br>
blocks=((size-in-bytes/2048 + 4096)) # Convert
bytes into blocks + a little more.<br>
mkudffs /tmp/newfilename.udfs blocks # Create a
file with that \# of blocks + some extra.<br>
</span></div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
@ Phyllis<br>
Yeah, my notices were more reminders - and not actually meant as
manual text.<br>
<br>
I would suggest to make three sections in the manual - reflecting
each common, legacy tape-based and current file based digital
camcorder format.<br>
<br>
1. DV to SD-Blu-ray video (re-encoding video to mpeg2, re-encoding
DV LPCM audio to Blu-ray LPCM)<br>
2. HDV to Blu-ray video (copying mpeg2 video, re-encoding MP2 audio
to LPCM or AC-3)<br>
3. AVCHD to Blu-ray video (copying H.264 video and AC-3 audio)<br>
<br>
At least 1 and 2 bdwrite to create the udfs image to burn. And as
most users nowadays are expected to install Cin-GG from Appimage, it
will need an intro section how to enable bdwrite by mounting it from
the Appimage.<br>
<br>
I can help to suggest/edit/reading manual texts for 1 and 2 - with
the format I have tested. Possibly we should not stress to get it
finished this month(?)<br>
And possibly we three should email this process directly outside the
mailing list, or just post the finished text, you decide?<br>
<br>
<br>
<br>
<br>
</body>
</html>