Lines Matching +full:128 +full:m

199 The CCIR has defined different standards: A,B,D,E,F,G,D,H,I,K,K1,L,M,N,...
205 When you speak about NTSC, you usually mean the standard: CCIR - M using
247 - can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC N, NTSC 4.43 and SECAM
253 - can handle: PAL B/G, NTSC M and SECAM
259 - can handle: PAL B/G/D/H/I/N, PAL N, PAL M, NTSC M, NTSC 4.43 and SECAM
265 - can handle: PAL B/D/G/H/I, NTSC M
271 - can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC 44, PAL 60, SECAM,NTSC Comb
277 - can handle: NTSC-M/N/44, PAL-M/N/B/G/H/I/D/K/L and SECAM
292 - can generate: PAL B/G, NTSC M
298 - can generate: PAL B/D/G/H/I/N, PAL M, NTSC M, PAL-N (Argentina)
304 - can generate: PAL B/D/G/H/I/N, PAL M, NTSC M, PAL 60
310 - can generate: PAL B/D/G/H/I/N, PAL M, NTSC M
322 - can generate: NTSC/PAL, PAL-M, PAL-N
326 to generate PAL N, maybe it would work if you use the PAL M settings.
469 > -q 50 -b 128 : 24.283.332 Bytes
471 > -q 25 -b 128 : 24.655.992
477 Let's do some math using a width of 704 pixels. I'm not sure whether the Buz
481 3168 blocks per field. Each pixel consist of two bytes; 128 bytes per block;
494 But wait a second! -b128 gives 128kB buffers! It's not possible to cram
495 202752 bytes of JPEG data into 128kB!
500 128kB is 131072 bytes. In this buffer, we want to store two fields, which
510 6/8 of the specified buffers. (I'm not sure why. "Playing it safe" seem to be
514 per block, the equivalence of -q24. With 128kB buffers, you can't use greater