lame --no-res won't magically make separate inputs seamless - it just means that the result can be split with mpgtx or whatever. There will still be a click at the end unless the input makes up an exact number of frames.

There's also the issue of overlap - seamless encoding is intended to be concatenated together, meaning a ½-frame of overlap of the result:


input:

-----------------------------+-----------------------------
file 1 | file 2
-----------------------------+-----------------------------


output 1:

-----+-------+-------+-------+
| | | |
-+---+---+---+---+---+---+---+---+
| | | | |
-+-------+-------+-------+-------+


output 2:

+-------+-------+-------+-----
| | | |
+---+---+---+---+---+---+---+-
| | | |
+-------+-------+-------+-


When encoding single files, the start and end are padded with silence.

I can't find documentation for --nogap, but from what I understand of the code, it should deal with both of these issues.

--
Toby Speight - 040103385
_________________________
Toby Speight
030103016 (80GB Mk2a, blue)
030102806 (0GB Mk2a, blue)