similar to: MSG: sequence number gap

Hi! I don't know much about network programming, or about terminal handling. I wondered about why the command "scp file user at host:path" didn't work. It gave me the following error messages: "stdin: is not a tty" "Write failed flushing stdout buffer." "write stdout: Broken pipe" I tried it with different versions of ssh, first the newest debian

Could someone please tell me what I'm doing wrong here? I have some oggs tagged using other applications and ogginfo doesn't give me any warnings when I use UTF-8 in them. I did the following: $ vorbiscomment --raw -a test.ogg -t "test=åäö" $ vorbiscomment --raw -l test.ogg test=åäö $ ogginfo -v test.ogg Processing file "test.ogg"... New logical stream (#1, serial:

This patch cleans up the vorbis-tools Makefile.am files so they work with both automake 1.4 and 1.6. Some changes to configure.in were also needed in order to get things to work (and to fix some ac 2.50 issues). Please remove config.h from cvs as it is a generated file and empty anyway. automake 1.6 isn't really incompatable with 1.4, it's just more picky about you sticking to the rules:

Sheldon E. Newhouse writes: > Anyone have ideas on what this output from the 'last' command means? > > TIA, > -sen > > xF*@**** otify ***@ Sat Aug 1 20:52 still logged in > xF*@**** otify ***@ Sat Aug 1 20:52 - 20:52 (00:00) > xF*@**** otify ***@ Sat Aug 1 20:52 - 20:52 (00:00) >

Hello Some time ago I posted a lil' patch to this list which adds milliseconds display of playlength to ogginfo. Some folks replied that it's plausible and this patch will be merged to the next version. Vorbistools-1.0.1 got out and the patch is not in it. Why? Anyway, here's this patch for vorbistools-1.0.1. I hope this time you will include it, because milliseconds support is

*sigh* Yes, you're right... It _has_ been a few years. My drive is filling up and all, I probably have tons of old/vulnerable daemons, so it's probably time for a fresh install. I'll let you know what turns up! -P -----Original Message----- From: Jack Moffitt [mailto:jack@xiph.org] Sent: Wednesday, August 08, 2001 1:29 PM To: Kenyon, Paul Cc: icecast-dev@xiph.org Subject: Re:

Ok, I have a small dilemma, and I'm hoping someone here has had to do this before. I have at a site (not PARI) a server running some mission critical software that was written in 1997 for libc5, under AOLserver 2.3.? No, source code is not available for that version of AOLserver (it wasn't open-sourced until version 3.0, and the API changed rather dramatically at that point), not that it

So, I have a client that has an internal use application that needs an ancient version of libc5.? That's not a typo; libc5.? Before the server that ran it died about a year and a half ago (said server was an AMD K6-2/450 with a 6GB Western Digital Caviar drive that had been spinning nearly continuously for almost 20 years!) it was running on Red Hat Linux 5.2.? The last version of CentOS

hi yorn and all, thank you oggvideo tools for windows. it is great... i can live with the command line for now myself but i will need to make some art students work with oggvideotools and they may not be happy with that:D anyway your video tutorial is also good (but it also crashed my firefox 3.5 beta 4 for two times on windows and i have reported that to mozilla), i would love to help for that

With this patch, ogginfo will display bitrate information (upper/lower/nominal/average bitrate). It is patched against today's CVS code (main branch). I am also working on true VBR support in oggenc (the user can specify the minimum & maximum bitrate) and will send a patch when it's done. <HR NOSHADE> <UL> <LI>application/x-gzip attachment: ogginfo-diff.gz

http://bugzilla.mindrot.org/show_bug.cgi?id=336 Summary: ssh does not compile on Linux with libc5 and 2.0 kernel Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at

Hi, I'm using ogginfo a lot to get the comments section on the terminal. However ogginfo always verifies (reads) the whole stream to print some more information. I'd like to see an additional option that does just print the comments efficiently. For a player connected via USB 1, that would clearly make a difference. (I have a Perl script that renames files based on the comments, and I

Hi, > So, I have a client that has an internal use application that needs an > ancient version of libc5.? That's not a typo; libc5.? Before the server > that ran it died about a year and a half ago (said server was an AMD > K6-2/450 with a 6GB Western Digital Caviar drive that had been spinning > nearly continuously for almost 20 years!) it was running on Red Hat > Linux

I have a CD ripped with RC2, ogginfo from 1.0 claims they are all "broken". ogg123 also goes a little wild with them. I'll experiment a little more, maybe play with xmms, etc. RC3's ogginfo do not see anything wrong with them... an example: ---------- ogginfo 1.0 New logical stream (#1, serial: 2aab0567): type vorbis Vorbis headers parsed for stream 1, information follows...

On 04/21/2017 12:11 PM, Lamar Owen wrote: > ... > The latest version of libc5 I know of that was shipped by Red Hat is > in RHL 6.2, libc-5.3.12. (There is a 5.4, but not sure of stability > or compatibility). > ... > I've successfully set up the bridging; a CentOS 7 VM on the same host > has full connectivity. So it's something about the rtl8139 and the >

I have an application with is binary-only, does its job well, and is only available for either libc5 (!) or early early glibc2.0 (!!). It has been running on a Red Hat Linux 5.2 (NOT RHEL; RHL) server for a really long time, and it honestly does its job and it's not easily replaced by an open-source solution at the moment. So, I need to do one of the following things: 1.) Run Red Hat

Hello I need to extract playback length from ogg vorbis file, with 1/100th second precision. The ogginfo program tells the playback length to 1 second precision. Why not to change ogginfo? I suppose many automatic tools need precision higher than 1 second. If you don't want to modify this ogginfo behaviour, please tell me how to get this playback length with high precision. Thank you very

Hiya: Since 1.0.1 is going to include minor tuning fixes that have an effect on audio quality in certain circumstances, I think the vendor tag should be updated according to the attached (and quite trivial) patch. (I chose 20030902 because that's the date of Monty's commits that included the tuning fixes.) -Carsten <p> Index: lib/info.c

2009/4/2 Ian Malone <ibmalone at gmail.com>: > If no-one is keen then I'll take the vorbiscomment and ogginfo > patches. ?They are lower priority than actually updating the wiki, but > I might be able to do that this evening. > Adding a -s option to ogginfo and vorbiscomment to hide METADATA_BLOCK_PICTURE contents git://github.com/imalone/imalone_vorbis-tools.git

On Mon, Sep 26, 2005 at 05:30:11PM +0200, Michael Smith wrote: > > Assuming this is correct, the next question that arises is "Is Vorbis > > when used this way truly gapless?" > > Yes, it is. ... and I can confirm this. No gaps were perceivable decoding in ogg123. However, an interesting effect can be had if all the parts have the same serial number. You get a bump