Jeremy C. Reed
2004-Jun-08 11:15 UTC
[Vorbis] piping to ogg123: Error opening - using the oggvorbis
module. The file may be corrupted. Message-ID: <Pine.LNX.4.43.0406081110070.26162-100000@pilchuck.reedmedia.net> I am unable to pipe to ogg123 with cat, but redirecting with < works fine. rainier:~$ cat ~/audio/acdc-who_made_who.ogg | ogg123 -v - Audio Device: OSS audio driver output Author: Aaron Holtzman <aholtzma@ess.engr.uvic.ca> Comments: Outputs audio to the Open Sound System driver. Error opening - using the oggvorbis module. The file may be corrupted. I have same problem with a variety of ogg files (but redirecting with < works fine). This works: rainier:~$ ogg123 -v - < ~/audio/acdc-who_made_who.ogg Audio Device: OSS audio driver output Author: Aaron Holtzman <aholtzma@ess.engr.uvic.ca> Comments: Outputs audio to the Open Sound System driver. Playing: - Ogg Vorbis stream: 2 channel, 44100 Hz Vorbis format: Version 0 Bitrate hints: upper=-1 nominal=128000 lower=-1 window=0 Encoded by: Xiphophorus libVorbis I 20010225 Title: Who Made Who Artist: ACDC Album: Who Made Who Time: 00:03.92 [03:23.08] of 03:27.00 (132.4 kbps) Output Buffer 90.6% ... I was unable to get to http://www.vorbis.com/faq.psp to check first. My goal is to use ssh to cat a remote ogg vorbis data file to pipe through my local ogg123. I'd prefer to not run ogg123 on remote box and piping the wav data to my player (which does work fine) because I assume it needs a lot more bandwidth. Any ideas? Jeremy C. Reed technical support & remote administration http://www.pugetsoundtechnology.com/
Jeremy C. Reed
2004-Jun-08 12:31 UTC
[Vorbis] piping to ogg123: Error opening - using the oggvorbis
module. The file may be corrupted. In-Reply-To: <Pine.LNX.4.43.0406081110070.26162-100000@pilchuck.reedmedia.net> Message-ID: <Pine.LNX.4.43.0406081229060.26162-100000@pilchuck.reedmedia.net> I received feedback off-list, so I am sending my notes to the list too. I removed the other sender's comments, since they were not public. I rarely touch Windows. This is under NetBSD/i386 1.6.2_STABLE. I just check and behaves same under Linux too. [input not seekable] That's what it looks like. ktrace shows: 4986 ogg123 CALL lseek(0,0,0xffffffff,0xffffffff,0) 4986 ogg123 RET lseek -1 errno 29 Illegal seek 4986 ogg123 CALL lseek(0,0,0,0,0x1) 4986 ogg123 RET lseek -1 errno 29 Illegal seek 4986 ogg123 CALL lseek(0,0,0xffffffff,0xffffffff,0) 4986 ogg123 RET lseek -1 errno 29 Illegal seek 4986 ogg123 CALL lseek(0,0,0,0,0x1) 4986 ogg123 RET lseek -1 errno 29 Illegal seek 4986 ogg123 CALL lseek(0,0,0xffffffff,0xffffffff,0) 4986 ogg123 RET lseek -1 errno 29 Illegal seek 4986 ogg123 CALL lseek(0,0,0,0,0x1) But when using "ogg123 -v - < file.ogg" ktrace does not show any "Illegal seek" problems. [ogginfo] It appears normal. [http input] Works fine: rainier:~/audio$ grep http /etc/inetd.conf rainier:~/audio$ mini_httpd -p 8080 rainier:~/audio$ ogg123 -v http://localhost:8080/air-supply.ogg Audio Device: OSS audio driver output Author: Aaron Holtzman <aholtzma@ess.engr.uvic.ca> Comments: Outputs audio to the Open Sound System driver. Playing: http://localhost:8080/air-supply.ogg Ogg Vorbis stream: 2 channel, 44100 Hz Vorbis format: Version 0 Bitrate hints: upper=0 nominal=112001 lower=0 window=0 Encoded by: Xiph.Org libVorbis I 20030909 Time: 00:21.48 (124.1 kbps) Input Buffer 100.0% Output Buffer 90.6% ... Piping is broken: rainier:~/audio$ cat air-supply.ogg | ogg123 -v - Audio Device: OSS audio driver output Author: Aaron Holtzman <aholtzma@ess.engr.uvic.ca> Comments: Outputs audio to the Open Sound System driver. Error opening - using the oggvorbis module. The file may be corrupted. Thanks for the feedback. Jeremy C. Reed open source, Unix, *BSD, Linux training http://www.pugetsoundtechnology.com/
Tom Felker
2004-Jun-08 13:48 UTC
[Vorbis] piping to ogg123: Error opening - using the oggvorbis
module. The file may be corrupted. In-Reply-To: <Pine.LNX.4.43.0406081110070.26162-100000@pilchuck.reedmedia.net> References: <Pine.LNX.4.43.0406081110070.26162-100000@pilchuck.reedmedia.net> Message-ID: <200406081548.07489.tcfelker@mtco.com> On Tuesday 08 June 2004 1:15 pm, Jeremy C. Reed wrote:> I am unable to pipe to ogg123 with cat, but redirecting with < works fine. > > rainier:~$ cat ~/audio/acdc-who_made_who.ogg | ogg123 -v - > > Audio Device: OSS audio driver output > Author: Aaron Holtzman <aholtzma@ess.engr.uvic.ca> > Comments: Outputs audio to the Open Sound System driver. > > Error opening - using the oggvorbis module. The file may be corrupted. > > I have same problem with a variety of ogg files (but redirecting with < > works fine). > > This works: > > rainier:~$ ogg123 -v - < ~/audio/acdc-who_made_who.ogg > > Audio Device: OSS audio driver output > Author: Aaron Holtzman <aholtzma@ess.engr.uvic.ca> > Comments: Outputs audio to the Open Sound System driver. > > Playing: - > Ogg Vorbis stream: 2 channel, 44100 Hz > Vorbis format: Version 0 > Bitrate hints: upper=-1 nominal=128000 lower=-1 window=0 > Encoded by: Xiphophorus libVorbis I 20010225 > Title: Who Made Who > Artist: ACDC > Album: Who Made Who > Time: 00:03.92 [03:23.08] of 03:27.00 (132.4 kbps) Output Buffer 90.6% > ... > > > I was unable to get to http://www.vorbis.com/faq.psp to check first. > > My goal is to use ssh to cat a remote ogg vorbis data file to pipe through > my local ogg123. I'd prefer to not run ogg123 on remote box and piping the > wav data to my player (which does work fine) because I assume it needs a > lot more bandwidth. > > Any ideas?When you do ogg123 < file, the shell sets it up so stdin is the file, and is seekable, but when you do cat file | ogg123, stdin is a pipe which isn't seekable. So the problem is that ogg123 apparently can't read from unseekable files. The codec allows it, but ogg123 apparently can't do it. (And it should.) That said, you just set up the remote box as a fileserver, or if you need streaming, try something like IceCast or Video LAN Client. -- Tom Felker, <tcfelker@mtco.com> <http://vlevel.sourceforge.net> - Stop fiddling with the volume knob. McBride: "While I cannot take the time to specify my claim, I have here in my hand a list of two hundred and five lines of code that were known to Linus Torvalds as belonging to SCO, and which, nevertheless, are still transforming Linux from a bicycle to a luxury car."