Debian Codegraph @

debian/docs/dvd-rw.html

raw
1 <HTML>
2
3 <HEAD>
4 <BASE HREF="http://fy.chalmers.se/~appro/linux/DVD+RW/-RW/">
5 <TITLE>DVD-R[W] for Linux</TITLE>
6 <META NAME="keywords" CONTENT="dvd, rewritable, dvd-rw, dvd-r, linux">
7 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
8 <LINK REL="icon" HREF="dvdforum.ico" TYPE="image/x-icon">
9 <LINK REL="shortcut icon" HREF="dvdforum.ico" TYPE="image/x-icon">
10 </HEAD>
11
12 <BODY BGCOLOR="#C0C0C0" TEXT="#000000"
13 LINK="#0000D0" VLINK="#502090" ALINK="#FF0000">
14
15 <H2>... as of version 5.0<SUP><IMG SRC="../linuxfund-tiny.gif" WIDTH=38
16 HEIGHT=11 ALT="(*)"></SUP> <A HREF="../tools/">dvd+rw-tools</A> provide
17 support even for <A HREF="http://www.dvdforum.org/">DVD-R[W]</A>
18 recordings.</H2>
19
20 <TABLE BORDER="0" WIDTH="95%" ALIGN="CENTER">
21 <TR VALIGN="TOP" ALIGN="JUSTIFY">
22 <TD><A HREF="http://www.linuxfund.org/"><IMG SRC="../linuxfund.gif"
23 BORDER=0 ALT="(*)"></A>
24 <TD><FONT SIZE="-1">Up to version 5.12 the support was classified as
25 &quot;experimental,&quot; because it was based solely on user feedback.
26 In time for 5.13 release <A
27 HREF="http://www.linuxfund.org/">LinuxFund.org</A> has donated DVD-dash
28 capable unit, which permits me to perform pre-release tests on site and
29 thus renders the &quot;experimental&quot; status obsolete:-)</FONT></TR>
30 </TABLE>
31
32 <!--
33 <P><HR>
34
35 <H3><P ALIGN="justify"><IMG SRC="/icons/Disclaimer.gif"
36 ALIGN="LEFT">This is a <I>preliminary</I> informational page! Note that
37 the code currently available for public download does <I>not</I>
38 support DVD-RW recording! For this [presumably short] moment the DVD-RW
39 code is provided upon <A
40 HREF="mailto:[email protected]?subject=dvd+rw-tools-5.0%20test-drive">explicit
41 request</A> only. Do state which unit do you have as well as other
42 background information [such as DVD-ROM compatibility experience]! At
43 this point I'd prefer to hear from Pioneer unit owners. If you don't
44 get a reply [within couple of days or so], then the code is already
45 being finalized and will be available for public download shortly.</H3>
46 -->
47
48 <P><HR>
49
50 <P><TABLE CELLPADDING=4>
51 <TR VALIGN="top" ALIGN="justify">
52 <TH>Q. <TH ALIGN="left">How are dvd+rw-tools different from <A
53 HREF="ftp://ftp.berlios.de/pub/cdrecord/ProDVD/">cdrecord-ProDVD</A>?
54 When it comes to DVD-R[W] burning that is...</TR>
55 <TR VALIGN="top" ALIGN="justify">
56 <TD>A. <TD>DVD-R[W] specification defines following recording strategies:
57 <UL><LI>Disk-at-once;
58 <LI>Incremental Sequential;
59 <LI>Restricted Overwrite (DVD-RW only);
60 </UL>
61 <P ALIGN="justify">Now, cdrecord-ProDVD supports Disk-at-once
62 strategy only, while dvd+rw-tools all the <I>others</I>. That's
63 it<TT>:-)</TT></TR>
64 </TABLE>
65
66 <P><TABLE CELLPADDING=4>
67 <TR VALIGN="top" ALIGN="justify">
68 <TH>Q. <TH ALIGN="left">What is the difference between these recording
69 strategies? Which one is the one for me?</TR>
70 <TR VALIGN="top" ALIGN="justify">
71 <TD>A. <TD><P ALIGN="justify">Disk-at-once is the one
72 <I>guaranteed</I> to provide <I>full</I> compatibility with
73 DVD-ROM/-Video. But apparently only as long as recording didn't
74 suffer from buffer underruns (see <A
75 HREF="../#plusvsminus">this paragraph on +RW page</A> for
76 technical details). DAO recordings are unappendable. Oh! It
77 should be explicitly noted that &quot;<I>full</I> compatibility
78 with DVD-Video&quot; doesn't really mean that DVD-R<B>W</B>
79 media recorded in this mode will be <I>universally</I>
80 playable! DVD-RW reportedly suffers from compatibility issues
81 very similar to DVD+RW. In other words these incompatibilities,
82 both -RW and +RW, have way more to do with low reflectivity of
83 these media, than with their logical formats.
84
85 <P ALIGN="justify">As for Incremental strategy [limited]
86 DVD-ROM/-Video compatibility is provided at single
87 packet/extent &quot;level.&quot; Good news are that growisofs
88 burns the whole filesystem image as a single extent, so that
89 you have all the rights to expect it to come out as compatible
90 as DAO recorded with [eventual] buffer underruns. Yes, buffer
91 underrun protection gets engaged, so that you don't have to
92 worry about how much <I>extra</I> load your system can sustain
93 during the burning process. In addition Incremental strategy
94 provides for <I>multiple sessions</I> and dvd+rw-tools do
95 utilize it. But you should keep in mind that very few DVD-ROM
96 players actually support DVD multi-sessioning! Even among those
97 explicitly supporting DVD-R most will play till the first
98 Border-out only.
99
100 <P ALIGN="justify">Restricted Overwrite (DVD-RW only) provides
101 for arbitrary overwrite (well, with certain restrictions:-),
102 meaning that it's possible to grow ISO9660 volumes <I>within a
103 &quot;single session,&quot;</I> in the very same way as with
104 DVD+RW (or -RAM/plain file for that matter). So that <I>if</I>
105 your DVD-ROM unit can play media recorded in this mode (it most
106 likely just does as long as it can play DVD-RW at all), but
107 doesn't support multi-sessioning, then this is the mode for you
108 (provided that you wish to add data at different occasions that
109 is). Buffer underrun protection is unconditionally on. As for
110 compatibility with DVD-ROM/-Video. Apparently user Data Zone is
111 equivalent to one recorded in DAO, but as if every 32KB block
112 has suffered from buffer underrun.
113
114 <P ALIGN="justify">Disk-at-once and Incremental recording
115 strategies are applicabe to DVD-R media and DVD-RW media in
116 Sequential mode. Restricted Overwrite strategy is applicable to
117 DVD-RW media explicitely formated for Restricted
118 Overwrite.</TR>
119 </TABLE>
120
121 <P><TABLE CELLPADDING=4>
122 <TR VALIGN="top" ALIGN="justify">
123 <TH>Q. <TH ALIGN="left">How do I switch between DVD-RW modes?</TR>
124 <TR VALIGN="top" ALIGN="justify">
125 <TD>A. <TD><P ALIGN="justify">Initially blank DVD-RW media is in
126 Sequential mode. To format for Restricted Overwrite invoke
127 '<TT><NOBR>dvd+rw-format</NOBR> /dev/scd<FONT
128 COLOR="red">N</FONT></TT>'. <!--Unfortunately this might turn
129 out to be a lengthy procedure, it takes a whole hour to format
130 1x media<NOBR>:-(</NOBR> &quot;Might&quot; in the last sentence
131 means that even though dvd+rw-format attempts to invoke so
132 called Quick Format procedure, some units apparently choose to
133 perform full format anyway. On the bright side,--> Once the
134 media is formatted you don't have to reformat it to zap the
135 content, it's more than enough to simply write over the
136 existing data [with <TT>growisofs -Z ...</TT>]. <!--If your
137 unit supports truly Quick Format, it--> Your unit might report
138 some bogus media capacity (e.g. Pioneer DVR-x05 reports ~8GB or
139 178.5% of real capacity) right after initial format. It
140 apparently just does so till you burn some data on it, so don't
141 get fixated on this...
142
143 <P ALIGN="justify">To change [back] to Sequential mode [or to
144 reuse the media in Sequential mode for a new dataset] invoke
145 '<TT><NOBR>dvd+rw-format</NOBR> -blank /dev/scd<FONT
146 COLOR="red">N</FONT></TT>'. Unfortunately specification
147 requires <I>lengthy, an hour per 1x media,</I>
148 <TT>-blank=full</TT> procedure applied <!--(which is as lengthy
149 as full format)--> before you can reuse the media for
150 Incremental Sequential (but apparently not for Disk-at-once)
151 recording. I really fail to understand why does it have to be
152 that way, but that's the way it is. Period.</TR>
153 </TABLE>
154
155 <P><TABLE CELLPADDING=4>
156 <TR VALIGN="top" ALIGN="justify">
157 <TH>Q. <TH ALIGN="left">How do I burn?</TR>
158 <TR VALIGN="top" ALIGN="justify">
159 <TD>A. <TD><P ALIGN="justify">For practical burning instructions see
160 the <A HREF="../#growisofs">growisofs paragraph</A> on +RW
161 page.</TR>
162 </TABLE>
163
164 <P><TABLE CELLPADDING=4>
165 <TR VALIGN="top" ALIGN="justify">
166 <TH>Q. <TH ALIGN="left">Any [other] caveats?</TR>
167 <TR VALIGN="top" ALIGN="justify">
168 <TD>A. <TD><P ALIGN="justify">When burning DVD-R[W] growisofs
169 recognizes an extra command line option, namely
170 <TT>-speed=<FONT COLOR="red">X</FONT></TT>, which lets you
171 choose the burning speed. If you use brand-name media, you're
172 unlikely to have to use this option. Your unit will determine
173 optimal velocity automagically. But if you use no-name media,
174 <TT>-speed=1</TT> might turn out to be a must. Problem is that
175 some units reportedly fail to determine optimal speed for
176 no-name media and pick higher one, higher than media can stand,
177 which results in unplayable recording. This may vary from
178 firmware to firmware (Pioneer users should consult <A
179 HREF="http://www.pioneeraus.com.au/multimedia/dvd/dvd-r_writing_speed_cl.htm">this
180 page</A>).
181
182 <P ALIGN="justify">As for -speed option in more general sense.
183 You might find yourself in situation when media rated as 4x is
184 recorded at lower speed, even if you explicitly specify
185 -speed=4. This is because that particular brand is poorly
186 supported by your particular unit firmware. It's not an
187 application problem, as growisofs asks unit for list of
188 supported velocities for currently loaded media and picks
189 <I>closest</I> to one specified in command line. The list is
190 updated upon every media load and can be found in
191 <NOBR>dvd+rw-mediainfo</NOBR> output.
192
193 <P ALIGN="justify">Futhermore quoting <A
194 HREF="http://sony.storagesupport.com/dvdrw/mediainfo_na.htm">SONY
195 support page</A>: &quot;... some of discs on the market do not
196 meet the recognized quality and performance standards.&quot;
197 Question is how does it show? Apparently in bizarre ways...
198 DVD-RW media might [reportedly] perform as write-once or maybe
199 twice or three times. Blank/format procedure might appear
200 successful, but deferred failure is reported upon actual
201 recording attempt. It might be possible to blank the media in
202 one unit, but not in another one [of different brand]. DVD-R
203 recording might [reportedly] fail around 95% of advertised
204 capacity... Or recording might fail at start-up with
205 &quot;INCOMPATIBLE MEDIUM&quot; error code. At all these
206 occasions switching to another media brand [reportedly] helped.
207
208 <P ALIGN="justify">As for DVD-ROM/-Video compatibility of
209 Restricted Overwrite mode. Playability might be limited for
210 reasons <I>similar</I> to DVD+ lead-out issues (see from <A
211 HREF="../#compat">2nd paragraph</A>), when legacy unit is
212 tricked to calibration on virgin surface. In case you find
213 media recorded in this mode unplayable, attempt to
214 <OL>
215 <LI>fill it up with '<TT>growisofs <FONT COLOR="red">-M</FONT>
216 /dev/scd0<FONT COLOR="red">=/dev/zero</FONT></TT>', and if it
217 still remains unplayable attempt to;
218 <LI>re-record it &quot;sequentially.&quot;
219 </OL>
220 <P ALIGN="justify">In order to facilitate for the latter test
221 and be excused from wasting an hour on full blanking procedure,
222 growisofs version 5.6 implements rudimentary support for DVD-RW
223 DAO recordings (yes, for DVD-RW only). Recall that DAO
224 recordings come out unappendable, which goes so to say against
225 growisofs' spirit:-)
226
227 <P ALIGN="justify">As of version 5.6 growisofs no longer relies
228 on logical unit to do all the magic, but explicitly asks the
229 burner to perform OPC, Optimal Power Calibration, prior
230 recording. It seems that it's not necessarily a &quot;good
231 thing&trade;,&quot; as it's maintained that media profiles
232 pre-defined in unit firmware might be more optimal than those
233 obtained as result of auto-calibration. I explicitly check if
234 the unit returns any OPC descriptors in reply to <TT>READ DISC
235 INFORMATION</TT> command [assuming that if it does, then
236 pre-defined media profile is in effect], but it wasn't actually
237 observed to be a case so far. If anybody can elaborate on this
238 further, I appreciate a note...</TR>
239 </TABLE>
240
241 <!---
242 <P><TABLE CELLPADDING=4>
243 <TR VALIGN="top" ALIGN="justify">
244 <TH>Q. <TH ALIGN="left">Why is the support classified as
245 <I>&quot;experimental&quot;</I>?</TR>
246 <TR VALIGN="top" ALIGN="justify">
247 <TD>A. <TD><P ALIGN="justify">The sole reason why it's <B>still</B>
248 classified as &quot;experimental&quot; is that I don't have
249 DVD-R[W] capable unit in my disposal and can't perform
250 regression and other tests myself. The support is therefore
251 based on your feedback, which is the actual reason for
252 why...</TR>
253 </TABLE>
254 --->
255
256 <!---
257 <P><TABLE CELLPADDING=4>
258 <TR VALIGN="top" ALIGN="justify">
259 <TH>Q. <TH ALIGN="left">I can't mount the media right after it's
260 burned. What did I do wrong?</TR>
261 <TR VALIGN="top" ALIGN="justify">
262 <TD>A. <TD>Reload the media, i.e. eject and push the tray back, before
263 you draw the final conclusion...</TR>
264 </TABLE>
265 --->
266
267 <P><HR>
268
269 <!---
270 <P ALIGN="justify">For practical burning instructions see the <A
271 HREF="../#growisofs">growisofs paragraph</A>. Oh! When burning DVD-R[W]
272 growisofs recognizes an extra command line option, namely
273 <TT>-speed=<FONT COLOR="red">X</FONT></TT>, which lets you control the
274 burning speed. If you use brand-name media, you're unlikely to have to
275 use this option. Your unit will determine optimal velocity
276 automagically. But if you use no-name media, <TT>-speed=1</TT> might
277 turn out to be a must. Problem is that some units reportedly fail to
278 determine optimal speed for no-name media and pick higher one, higher
279 than media can stand, which results in unplayable recording.
280
281 <P><HR>
282 --->
283
284 </BODY>
285 </HTML>