Zoran 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580
  1. Frequently Asked Questions:
  2. ===========================
  3. subject: unified zoran driver (zr360x7, zoran, buz, dc10(+), dc30(+), lml33)
  4. website: http://mjpeg.sourceforge.net/driver-zoran/
  5. 1. What cards are supported
  6. 1.1 What the TV decoder can do an what not
  7. 1.2 What the TV encoder can do an what not
  8. 2. How do I get this damn thing to work
  9. 3. What mainboard should I use (or why doesn't my card work)
  10. 4. Programming interface
  11. 5. Applications
  12. 6. Concerning buffer sizes, quality, output size etc.
  13. 7. It hangs/crashes/fails/whatevers! Help!
  14. 8. Maintainers/Contacting
  15. 9. License
  16. ===========================
  17. 1. What cards are supported
  18. Iomega Buz, Linux Media Labs LML33/LML33R10, Pinnacle/Miro
  19. DC10/DC10+/DC30/DC30+ and related boards (available under various names).
  20. Iomega Buz:
  21. * Zoran zr36067 PCI controller
  22. * Zoran zr36060 MJPEG codec
  23. * Philips saa7111 TV decoder
  24. * Philips saa7185 TV encoder
  25. Drivers to use: videodev, i2c-core, i2c-algo-bit,
  26. videocodec, saa7111, saa7185, zr36060, zr36067
  27. Inputs/outputs: Composite and S-video
  28. Norms: PAL, SECAM (720x576 @ 25 fps), NTSC (720x480 @ 29.97 fps)
  29. Card number: 7
  30. AverMedia 6 Eyes AVS6EYES:
  31. * Zoran zr36067 PCI controller
  32. * Zoran zr36060 MJPEG codec
  33. * Samsung ks0127 TV decoder
  34. * Conexant bt866 TV encoder
  35. Drivers to use: videodev, i2c-core, i2c-algo-bit,
  36. videocodec, ks0127, bt866, zr36060, zr36067
  37. Inputs/outputs: Six physical inputs. 1-6 are composite,
  38. 1-2, 3-4, 5-6 doubles as S-video,
  39. 1-3 triples as component.
  40. One composite output.
  41. Norms: PAL, SECAM (720x576 @ 25 fps), NTSC (720x480 @ 29.97 fps)
  42. Card number: 8
  43. Not autodetected, card=8 is necessary.
  44. Linux Media Labs LML33:
  45. * Zoran zr36067 PCI controller
  46. * Zoran zr36060 MJPEG codec
  47. * Brooktree bt819 TV decoder
  48. * Brooktree bt856 TV encoder
  49. Drivers to use: videodev, i2c-core, i2c-algo-bit,
  50. videocodec, bt819, bt856, zr36060, zr36067
  51. Inputs/outputs: Composite and S-video
  52. Norms: PAL (720x576 @ 25 fps), NTSC (720x480 @ 29.97 fps)
  53. Card number: 5
  54. Linux Media Labs LML33R10:
  55. * Zoran zr36067 PCI controller
  56. * Zoran zr36060 MJPEG codec
  57. * Philips saa7114 TV decoder
  58. * Analog Devices adv7170 TV encoder
  59. Drivers to use: videodev, i2c-core, i2c-algo-bit,
  60. videocodec, saa7114, adv7170, zr36060, zr36067
  61. Inputs/outputs: Composite and S-video
  62. Norms: PAL (720x576 @ 25 fps), NTSC (720x480 @ 29.97 fps)
  63. Card number: 6
  64. Pinnacle/Miro DC10(new):
  65. * Zoran zr36057 PCI controller
  66. * Zoran zr36060 MJPEG codec
  67. * Philips saa7110a TV decoder
  68. * Analog Devices adv7176 TV encoder
  69. Drivers to use: videodev, i2c-core, i2c-algo-bit,
  70. videocodec, saa7110, adv7175, zr36060, zr36067
  71. Inputs/outputs: Composite, S-video and Internal
  72. Norms: PAL, SECAM (768x576 @ 25 fps), NTSC (640x480 @ 29.97 fps)
  73. Card number: 1
  74. Pinnacle/Miro DC10+:
  75. * Zoran zr36067 PCI controller
  76. * Zoran zr36060 MJPEG codec
  77. * Philips saa7110a TV decoder
  78. * Analog Devices adv7176 TV encoder
  79. Drivers to use: videodev, i2c-core, i2c-algo-bit,
  80. videocodec, sa7110, adv7175, zr36060, zr36067
  81. Inputs/outputs: Composite, S-video and Internal
  82. Norms: PAL, SECAM (768x576 @ 25 fps), NTSC (640x480 @ 29.97 fps)
  83. Card number: 2
  84. Pinnacle/Miro DC10(old): *
  85. * Zoran zr36057 PCI controller
  86. * Zoran zr36050 MJPEG codec
  87. * Zoran zr36016 Video Front End or Fuji md0211 Video Front End (clone?)
  88. * Micronas vpx3220a TV decoder
  89. * mse3000 TV encoder or Analog Devices adv7176 TV encoder *
  90. Drivers to use: videodev, i2c-core, i2c-algo-bit,
  91. videocodec, vpx3220, mse3000/adv7175, zr36050, zr36016, zr36067
  92. Inputs/outputs: Composite, S-video and Internal
  93. Norms: PAL, SECAM (768x576 @ 25 fps), NTSC (640x480 @ 29.97 fps)
  94. Card number: 0
  95. Pinnacle/Miro DC30: *
  96. * Zoran zr36057 PCI controller
  97. * Zoran zr36050 MJPEG codec
  98. * Zoran zr36016 Video Front End
  99. * Micronas vpx3225d/vpx3220a/vpx3216b TV decoder
  100. * Analog Devices adv7176 TV encoder
  101. Drivers to use: videodev, i2c-core, i2c-algo-bit,
  102. videocodec, vpx3220/vpx3224, adv7175, zr36050, zr36016, zr36067
  103. Inputs/outputs: Composite, S-video and Internal
  104. Norms: PAL, SECAM (768x576 @ 25 fps), NTSC (640x480 @ 29.97 fps)
  105. Card number: 3
  106. Pinnacle/Miro DC30+: *
  107. * Zoran zr36067 PCI controller
  108. * Zoran zr36050 MJPEG codec
  109. * Zoran zr36016 Video Front End
  110. * Micronas vpx3225d/vpx3220a/vpx3216b TV decoder
  111. * Analog Devices adv7176 TV encoder
  112. Drivers to use: videodev, i2c-core, i2c-algo-bit,
  113. videocodec, vpx3220/vpx3224, adv7175, zr36050, zr36015, zr36067
  114. Inputs/outputs: Composite, S-video and Internal
  115. Norms: PAL, SECAM (768x576 @ 25 fps), NTSC (640x480 @ 29.97 fps)
  116. Card number: 4
  117. Note: No module for the mse3000 is available yet
  118. Note: No module for the vpx3224 is available yet
  119. Note: use encoder=X or decoder=X for non-default i2c chips (see i2c-id.h)
  120. ===========================
  121. 1.1 What the TV decoder can do an what not
  122. The best know TV standards are NTSC/PAL/SECAM. but for decoding a frame that
  123. information is not enough. There are several formats of the TV standards.
  124. And not every TV decoder is able to handle every format. Also the every
  125. combination is supported by the driver. There are currently 11 different
  126. tv broadcast formats all aver the world.
  127. The CCIR defines parameters needed for broadcasting the signal.
  128. The CCIR has defined different standards: A,B,D,E,F,G,D,H,I,K,K1,L,M,N,...
  129. The CCIR says not much about the colorsystem used !!!
  130. And talking about a colorsystem says not to much about how it is broadcast.
  131. The CCIR standards A,E,F are not used any more.
  132. When you speak about NTSC, you usually mean the standard: CCIR - M using
  133. the NTSC colorsystem which is used in the USA, Japan, Mexico, Canada
  134. and a few others.
  135. When you talk about PAL, you usually mean: CCIR - B/G using the PAL
  136. colorsystem which is used in many Countries.
  137. When you talk about SECAM, you mean: CCIR - L using the SECAM Colorsystem
  138. which is used in France, and a few others.
  139. There the other version of SECAM, CCIR - D/K is used in Bulgaria, China,
  140. Slovakai, Hungary, Korea (Rep.), Poland, Rumania and a others.
  141. The CCIR - H uses the PAL colorsystem (sometimes SECAM) and is used in
  142. Egypt, Libya, Sri Lanka, Syrain Arab. Rep.
  143. The CCIR - I uses the PAL colorsystem, and is used in Great Britain, Hong Kong,
  144. Ireland, Nigeria, South Africa.
  145. The CCIR - N uses the PAL colorsystem and PAL frame size but the NTSC framerate,
  146. and is used in Argentinia, Uruguay, an a few others
  147. We do not talk about how the audio is broadcast !
  148. A rather good sites about the TV standards are:
  149. http://www.sony.jp/ServiceArea/Voltage_map/
  150. http://info.electronicwerkstatt.de/bereiche/fernsehtechnik/frequenzen_und_normen/Fernsehnormen/
  151. and http://www.cabl.com/restaurant/channel.html
  152. Other weird things around: NTSC 4.43 is a modificated NTSC, which is mainly
  153. used in PAL VCR's that are able to play back NTSC. PAL 60 seems to be the same
  154. as NTSC 4.43 . The Datasheets also talk about NTSC 44, It seems as if it would
  155. be the same as NTSC 4.43.
  156. NTSC Combs seems to be a decoder mode where the decoder uses a comb filter
  157. to split coma and luma instead of a Delay line.
  158. But I did not defiantly find out what NTSC Comb is.
  159. Philips saa7111 TV decoder
  160. was introduced in 1997, is used in the BUZ and
  161. can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC N, NTSC 4.43 and SECAM
  162. Philips saa7110a TV decoder
  163. was introduced in 1995, is used in the Pinnacle/Miro DC10(new), DC10+ and
  164. can handle: PAL B/G, NTSC M and SECAM
  165. Philips saa7114 TV decoder
  166. was introduced in 2000, is used in the LML33R10 and
  167. can handle: PAL B/G/D/H/I/N, PAL N, PAL M, NTSC M, NTSC 4.43 and SECAM
  168. Brooktree bt819 TV decoder
  169. was introduced in 1996, and is used in the LML33 and
  170. can handle: PAL B/D/G/H/I, NTSC M
  171. Micronas vpx3220a TV decoder
  172. was introduced in 1996, is used in the DC30 and DC30+ and
  173. can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC 44, PAL 60, SECAM,NTSC Comb
  174. Samsung ks0127 TV decoder
  175. is used in the AVS6EYES card and
  176. can handle: NTSC-M/N/44, PAL-M/N/B/G/H/I/D/K/L and SECAM
  177. ===========================
  178. 1.2 What the TV encoder can do an what not
  179. The TV encoder are doing the "same" as the decoder, but in the oder direction.
  180. You feed them digital data and the generate a Composite or SVHS signal.
  181. For information about the colorsystems and TV norm take a look in the
  182. TV decoder section.
  183. Philips saa7185 TV Encoder
  184. was introduced in 1996, is used in the BUZ
  185. can generate: PAL B/G, NTSC M
  186. Brooktree bt856 TV Encoder
  187. was introduced in 1994, is used in the LML33
  188. can generate: PAL B/D/G/H/I/N, PAL M, NTSC M, PAL-N (Argentina)
  189. Analog Devices adv7170 TV Encoder
  190. was introduced in 2000, is used in the LML300R10
  191. can generate: PAL B/D/G/H/I/N, PAL M, NTSC M, PAL 60
  192. Analog Devices adv7175 TV Encoder
  193. was introduced in 1996, is used in the DC10, DC10+, DC10 old, DC30, DC30+
  194. can generate: PAL B/D/G/H/I/N, PAL M, NTSC M
  195. ITT mse3000 TV encoder
  196. was introduced in 1991, is used in the DC10 old
  197. can generate: PAL , NTSC , SECAM
  198. Conexant bt866 TV encoder
  199. is used in AVS6EYES, and
  200. can generate: NTSC/PAL, PAL­M, PAL­N
  201. The adv717x, should be able to produce PAL N. But you find nothing PAL N
  202. specific in the registers. Seem that you have to reuse a other standard
  203. to generate PAL N, maybe it would work if you use the PAL M settings.
  204. ==========================
  205. 2. How do I get this damn thing to work
  206. Load zr36067.o. If it can't autodetect your card, use the card=X insmod
  207. option with X being the card number as given in the previous section.
  208. To have more than one card, use card=X1[,X2[,X3,[X4[..]]]]
  209. To automate this, add the following to your /etc/modprobe.conf:
  210. options zr36067 card=X1[,X2[,X3[,X4[..]]]]
  211. alias char-major-81-0 zr36067
  212. One thing to keep in mind is that this doesn't load zr36067.o itself yet. It
  213. just automates loading. If you start using xawtv, the device won't load on
  214. some systems, since you're trying to load modules as a user, which is not
  215. allowed ("permission denied"). A quick workaround is to add 'Load "v4l"' to
  216. XF86Config-4 when you use X by default, or to run 'v4l-conf -c <device>' in
  217. one of your startup scripts (normally rc.local) if you don't use X. Both
  218. make sure that the modules are loaded on startup, under the root account.
  219. ===========================
  220. 3. What mainboard should I use (or why doesn't my card work)
  221. <insert lousy disclaimer here>. In short: good=SiS/Intel, bad=VIA.
  222. Experience tells us that people with a Buz, on average, have more problems
  223. than users with a DC10+/LML33. Also, it tells us that people owning a VIA-
  224. based mainboard (ktXXX, MVP3) have more problems than users with a mainboard
  225. based on a different chipset. Here's some notes from Andrew Stevens:
  226. --
  227. Here's my experience of using LML33 and Buz on various motherboards:
  228. VIA MVP3
  229. Forget it. Pointless. Doesn't work.
  230. Intel 430FX (Pentium 200)
  231. LML33 perfect, Buz tolerable (3 or 4 frames dropped per movie)
  232. Intel 440BX (early stepping)
  233. LML33 tolerable. Buz starting to get annoying (6-10 frames/hour)
  234. Intel 440BX (late stepping)
  235. Buz tolerable, LML3 almost perfect (occasional single frame drops)
  236. SiS735
  237. LML33 perfect, Buz tolerable.
  238. VIA KT133(*)
  239. LML33 starting to get annoying, Buz poor enough that I have up.
  240. Both 440BX boards were dual CPU versions.
  241. --
  242. Bernhard Praschinger later added:
  243. --
  244. AMD 751
  245. Buz perfect-tolerable
  246. AMD 760
  247. Buz perfect-tolerable
  248. --
  249. In general, people on the user mailinglist won't give you much of a chance
  250. if you have a VIA-based motherboard. They may be cheap, but sometimes, you'd
  251. rather want to spend some more money on better boards. In general, VIA
  252. mainboard's IDE/PCI performance will also suck badly compared to others.
  253. You'll noticed the DC10+/DC30+ aren't mentioned anywhere in the overview.
  254. Basically, you can assume that if the Buz works, the LML33 will work too. If
  255. the LML33 works, the DC10+/DC30+ will work too. They're most tolerant to
  256. different mainboard chipsets from all of the supported cards.
  257. If you experience timeouts during capture, buy a better mainboard or lower
  258. the quality/buffersize during capture (see 'Concerning buffer sizes, quality,
  259. output size etc.'). If it hangs, there's little we can do as of now. Check
  260. your IRQs and make sure the card has its own interrupts.
  261. ===========================
  262. 4. Programming interface
  263. This driver conforms to video4linux and video4linux2, both can be used to
  264. use the driver. Since video4linux didn't provide adequate calls to fully
  265. use the cards' features, we've introduced several programming extensions,
  266. which are currently officially accepted in the 2.4.x branch of the kernel.
  267. These extensions are known as the v4l/mjpeg extensions. See zoran.h for
  268. details (structs/ioctls).
  269. Information - video4linux:
  270. http://roadrunner.swansea.linux.org.uk/v4lapi.shtml
  271. Documentation/video4linux/API.html
  272. /usr/include/linux/videodev.h
  273. Information - video4linux/mjpeg extensions:
  274. ./zoran.h
  275. (also see below)
  276. Information - video4linux2:
  277. http://linuxtv.org
  278. http://v4l2spec.bytesex.org/
  279. /usr/include/linux/videodev2.h
  280. More information on the video4linux/mjpeg extensions, by Serguei
  281. Miridonovi and Rainer Johanni:
  282. --
  283. The ioctls for that interface are as follows:
  284. BUZIOC_G_PARAMS
  285. BUZIOC_S_PARAMS
  286. Get and set the parameters of the buz. The user should always do a
  287. BUZIOC_G_PARAMS (with a struct buz_params) to obtain the default
  288. settings, change what he likes and then make a BUZIOC_S_PARAMS call.
  289. BUZIOC_REQBUFS
  290. Before being able to capture/playback, the user has to request
  291. the buffers he is wanting to use. Fill the structure
  292. zoran_requestbuffers with the size (recommended: 256*1024) and
  293. the number (recommended 32 up to 256). There are no such restrictions
  294. as for the Video for Linux buffers, you should LEAVE SUFFICIENT
  295. MEMORY for your system however, else strange things will happen ....
  296. On return, the zoran_requestbuffers structure contains number and
  297. size of the actually allocated buffers.
  298. You should use these numbers for doing a mmap of the buffers
  299. into the user space.
  300. The BUZIOC_REQBUFS ioctl also makes it happen, that the next mmap
  301. maps the MJPEG buffer instead of the V4L buffers.
  302. BUZIOC_QBUF_CAPT
  303. BUZIOC_QBUF_PLAY
  304. Queue a buffer for capture or playback. The first call also starts
  305. streaming capture. When streaming capture is going on, you may
  306. only queue further buffers or issue syncs until streaming
  307. capture is switched off again with a argument of -1 to
  308. a BUZIOC_QBUF_CAPT/BUZIOC_QBUF_PLAY ioctl.
  309. BUZIOC_SYNC
  310. Issue this ioctl when all buffers are queued. This ioctl will
  311. block until the first buffer becomes free for saving its
  312. data to disk (after BUZIOC_QBUF_CAPT) or for reuse (after BUZIOC_QBUF_PLAY).
  313. BUZIOC_G_STATUS
  314. Get the status of the input lines (video source connected/norm).
  315. For programming example, please, look at lavrec.c and lavplay.c code in
  316. lavtools-1.2p2 package (URL: http://www.cicese.mx/~mirsev/DC10plus/)
  317. and the 'examples' directory in the original Buz driver distribution.
  318. Additional notes for software developers:
  319. The driver returns maxwidth and maxheight parameters according to
  320. the current TV standard (norm). Therefore, the software which
  321. communicates with the driver and "asks" for these parameters should
  322. first set the correct norm. Well, it seems logically correct: TV
  323. standard is "more constant" for current country than geometry
  324. settings of a variety of TV capture cards which may work in ITU or
  325. square pixel format. Remember that users now can lock the norm to
  326. avoid any ambiguity.
  327. --
  328. Please note that lavplay/lavrec are also included in the MJPEG-tools
  329. (http://mjpeg.sf.net/).
  330. ===========================
  331. 5. Applications
  332. Applications known to work with this driver:
  333. TV viewing:
  334. * xawtv
  335. * kwintv
  336. * probably any TV application that supports video4linux or video4linux2.
  337. MJPEG capture/playback:
  338. * mjpegtools/lavtools (or Linux Video Studio)
  339. * gstreamer
  340. * mplayer
  341. General raw capture:
  342. * xawtv
  343. * gstreamer
  344. * probably any application that supports video4linux or video4linux2
  345. Video editing:
  346. * Cinelerra
  347. * MainActor
  348. * mjpegtools (or Linux Video Studio)
  349. ===========================
  350. 6. Concerning buffer sizes, quality, output size etc.
  351. The zr36060 can do 1:2 JPEG compression. This is really the theoretical
  352. maximum that the chipset can reach. The driver can, however, limit compression
  353. to a maximum (size) of 1:4. The reason for this is that some cards (e.g. Buz)
  354. can't handle 1:2 compression without stopping capture after only a few minutes.
  355. With 1:4, it'll mostly work. If you have a Buz, use 'low_bitrate=1' to go into
  356. 1:4 max. compression mode.
  357. 100% JPEG quality is thus 1:2 compression in practice. So for a full PAL frame
  358. (size 720x576). The JPEG fields are stored in YUY2 format, so the size of the
  359. fields are 720x288x16/2 bits/field (2 fields/frame) = 207360 bytes/field x 2 =
  360. 414720 bytes/frame (add some more bytes for headers and DHT (huffman)/DQT
  361. (quantization) tables, and you'll get to something like 512kB per frame for
  362. 1:2 compression. For 1:4 compression, you'd have frames of half this size.
  363. Some additional explanation by Martin Samuelsson, which also explains the
  364. importance of buffer sizes:
  365. --
  366. > Hmm, I do not think it is really that way. With the current (downloaded
  367. > at 18:00 Monday) driver I get that output sizes for 10 sec:
  368. > -q 50 -b 128 : 24.283.332 Bytes
  369. > -q 50 -b 256 : 48.442.368
  370. > -q 25 -b 128 : 24.655.992
  371. > -q 25 -b 256 : 25.859.820
  372. I woke up, and can't go to sleep again. I'll kill some time explaining why
  373. this doesn't look strange to me.
  374. Let's do some math using a width of 704 pixels. I'm not sure whether the Buz
  375. actually use that number or not, but that's not too important right now.
  376. 704x288 pixels, one field, is 202752 pixels. Divided by 64 pixels per block;
  377. 3168 blocks per field. Each pixel consist of two bytes; 128 bytes per block;
  378. 1024 bits per block. 100% in the new driver mean 1:2 compression; the maximum
  379. output becomes 512 bits per block. Actually 510, but 512 is simpler to use
  380. for calculations.
  381. Let's say that we specify d1q50. We thus want 256 bits per block; times 3168
  382. becomes 811008 bits; 101376 bytes per field. We're talking raw bits and bytes
  383. here, so we don't need to do any fancy corrections for bits-per-pixel or such
  384. things. 101376 bytes per field.
  385. d1 video contains two fields per frame. Those sum up to 202752 bytes per
  386. frame, and one of those frames goes into each buffer.
  387. But wait a second! -b128 gives 128kB buffers! It's not possible to cram
  388. 202752 bytes of JPEG data into 128kB!
  389. This is what the driver notice and automatically compensate for in your
  390. examples. Let's do some math using this information:
  391. 128kB is 131072 bytes. In this buffer, we want to store two fields, which
  392. leaves 65536 bytes for each field. Using 3168 blocks per field, we get
  393. 20.68686868... available bytes per block; 165 bits. We can't allow the
  394. request for 256 bits per block when there's only 165 bits available! The -q50
  395. option is silently overridden, and the -b128 option takes precedence, leaving
  396. us with the equivalence of -q32.
  397. This gives us a data rate of 165 bits per block, which, times 3168, sums up
  398. to 65340 bytes per field, out of the allowed 65536. The current driver has
  399. another level of rate limiting; it won't accept -q values that fill more than
  400. 6/8 of the specified buffers. (I'm not sure why. "Playing it safe" seem to be
  401. a safe bet. Personally, I think I would have lowered requested-bits-per-block
  402. by one, or something like that.) We can't use 165 bits per block, but have to
  403. lower it again, to 6/8 of the available buffer space: We end up with 124 bits
  404. per block, the equivalence of -q24. With 128kB buffers, you can't use greater
  405. than -q24 at -d1. (And PAL, and 704 pixels width...)
  406. The third example is limited to -q24 through the same process. The second
  407. example, using very similar calculations, is limited to -q48. The only
  408. example that actually grab at the specified -q value is the last one, which
  409. is clearly visible, looking at the file size.
  410. --
  411. Conclusion: the quality of the resulting movie depends on buffer size, quality,
  412. whether or not you use 'low_bitrate=1' as insmod option for the zr36060.c
  413. module to do 1:4 instead of 1:2 compression, etc.
  414. If you experience timeouts, lowering the quality/buffersize or using
  415. 'low_bitrate=1 as insmod option for zr36060.o might actually help, as is
  416. proven by the Buz.
  417. ===========================
  418. 7. It hangs/crashes/fails/whatevers! Help!
  419. Make sure that the card has its own interrupts (see /proc/interrupts), check
  420. the output of dmesg at high verbosity (load zr36067.o with debug=2,
  421. load all other modules with debug=1). Check that your mainboard is favorable
  422. (see question 2) and if not, test the card in another computer. Also see the
  423. notes given in question 3 and try lowering quality/buffersize/capturesize
  424. if recording fails after a period of time.
  425. If all this doesn't help, give a clear description of the problem including
  426. detailed hardware information (memory+brand, mainboard+chipset+brand, which
  427. MJPEG card, processor, other PCI cards that might be of interest), give the
  428. system PnP information (/proc/interrupts, /proc/dma, /proc/devices), and give
  429. the kernel version, driver version, glibc version, gcc version and any other
  430. information that might possibly be of interest. Also provide the dmesg output
  431. at high verbosity. See 'Contacting' on how to contact the developers.
  432. ===========================
  433. 8. Maintainers/Contacting
  434. The driver is currently maintained by Laurent Pinchart and Ronald Bultje
  435. (<laurent.pinchart@skynet.be> and <rbultje@ronald.bitfreak.net>). For bug
  436. reports or questions, please contact the mailinglist instead of the developers
  437. individually. For user questions (i.e. bug reports or how-to questions), send
  438. an email to <mjpeg-users@lists.sf.net>, for developers (i.e. if you want to
  439. help programming), send an email to <mjpeg-developer@lists.sf.net>. See
  440. http://www.sf.net/projects/mjpeg/ for subscription information.
  441. For bug reports, be sure to include all the information as described in
  442. the section 'It hangs/crashes/fails/whatevers! Help!'. Please make sure
  443. you're using the latest version (http://mjpeg.sf.net/driver-zoran/).
  444. Previous maintainers/developers of this driver include Serguei Miridonov
  445. <mirsev@cicese.mx>, Wolfgang Scherr <scherr@net4you.net>, Dave Perks
  446. <dperks@ibm.net> and Rainer Johanni <Rainer@Johanni.de>.
  447. ===========================
  448. 9. License
  449. This driver is distributed under the terms of the General Public License.
  450. This program is free software; you can redistribute it and/or modify
  451. it under the terms of the GNU General Public License as published by
  452. the Free Software Foundation; either version 2 of the License, or
  453. (at your option) any later version.
  454. This program is distributed in the hope that it will be useful,
  455. but WITHOUT ANY WARRANTY; without even the implied warranty of
  456. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  457. GNU General Public License for more details.
  458. You should have received a copy of the GNU General Public License
  459. along with this program; if not, write to the Free Software
  460. Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
  461. See http://www.gnu.org/ for more information.