Package: mimms Version: 3.2.1-2 Severity: wishlist I'm not sure if this is even meaningful in the mms: world, maybe the specifications are always the same, I don't know, but it might be useful to people like me who aren't too familiar with mms: and related stream formats. Any way a --identify/-i switch which would just dump out the specifics of the stream, similar to ffprobe (which doesn't handle mms:), mkvmerge --identify, file etc. Perhaps a validate switch, to sample enough of the stream to verify that it is valid mms:, with appropriate return code. If this in invariant on valid mms: and related, then the --identify could dump out some hard coded info on the format, otherwise real technical specs of the stream in question. This was spurred on by a friend who didn't want to capture the whole stream, but encode and save the audio on the fly direct to mp3. I was trying to analyze the stream to find out if it was simply a question of dumping the raw audio to a file or actual encoding. I ended up mimms -vt 1 mms://.... and analyzing the captured file. Thanks for any consideration, and your work on this fine package.
-- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mimms depends on: ii libmms0 0.6-1 MMS stream protocol library - shar ii python 2.5.4-2 An interactive high-level object-o ii python-support 1.0.6 automated rebuilding support for P mimms recommends no packages. mimms suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
