File: BUGS

package info (click to toggle)
ucbmpeg 1r2-6
  • links: PTS
  • area: non-free
  • in suites: hamm, potato, slink
  • size: 9,504 kB
  • ctags: 7,643
  • sloc: ansic: 79,920; tcl: 2,985; perl: 313; asm: 284; makefile: 269; csh: 13
file content (62 lines) | stat: -rw-r--r-- 1,879 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
Known BUGS:

1. <fixed>

2. rate control and specifics files interact badly

3. using REMOTE parallel execution:
   `command` to find INPUT files does not work
   SPECIFICS_FILE (CDL_FILE)
   USER_DATA 
     dont work (should send the files over the socket, but do not

4. using any sort of parallel code:
     REFERENCE_FRAME	DECODED
   does not work

5. Cannot use both STDIN and CDL_FILEs (ok, since it doesnt make sense...)

6. <fixed>

7. Patterns of BBI...  seem to cause problems for parallel encoding.  
   I believe the bugs are fixed for sequential, but if you hit one, let us
   know!

8. Sometimes parallel encoding results in a zero size being written into
   the stream.  To fix, specify SIZE of the actual size.

8.1 (related? minor, anyway) in parallel is also writes the Quant matrix
   even when it is the default one

9. It is unclear (to us anyway) if we should generate Y's from 0..255 or 16..224

10. <fixed>

11. <fixed>

12. reading JPEG from stdin, the encoder will sometimes stop before the end
of the stream (if the images are smaller than half the buffer size).

13. Sometimes INPUT_CONVERT * is not good (requires "cat *"), in a parallel
case reported by a user it was needed.

14. Parallel encoding often generates improper temporal_ref's...
Reporting bugs:
    If you find any bugs in this software, please send them to
    mpeg-bugs@plateau.cs.berkeley.edu.  Since this software
    is unsupported, we make no guarantees about how long it will
    take to fix the bug, or if it will be fixed at all.  Bug fixes
    will be cheerfully accepted.  Please include as much detailed
    information as possible, including:

	1) the version number of the program you are using (cf. VERSION)
	2) the data file that caused the bug (if possible)
	3) the OS version and machine type you ran the program on
	4) the compiler used to compile the program