similar to: Strange behavior of command line parameter passing to linux

Hi, When I encode a file, with the command line (for example): oggenc h:\wavs\abc.wav -a sunshine as expected, it creates a file h:\wavs\abc.ogg. However, adding the '-t' command line option: oggenc h:\wavs\abc.wav -a sunshine -t MrSunny causes it to now create a file called MrSunny.ogg This behaviour could be expected if I had used the '-n' option, but I have not, so

On 04/02/2017 01:31 PM, Kay Schenk wrote: > > > On 03/29/2017 06:43 AM, ken wrote: >> On 03/28/2017 08:53 PM, ken wrote: >>> The www has failed me with this, so I'm trying you guys. Sound worked >>> great out of the box when I installed 7.2... Yay! I could watch all >>> kinds of videos, like on facebook and youtube. And I could listen to

On 03/28/2017 05:53 PM, ken wrote: > The www has failed me with this, so I'm trying you guys. Sound worked > great out of the box when I installed 7.2... Yay! I could watch all > kinds of videos, like on facebook and youtube. And I could listen to > most podcasts too. But then something happened. It was either a kernel > upgrade or that I installed vlc (for watching videos

On 03/28/2017 08:53 PM, ken wrote: > The www has failed me with this, so I'm trying you guys. Sound worked > great out of the box when I installed 7.2... Yay! I could watch all > kinds of videos, like on facebook and youtube. And I could listen to > most podcasts too. But then something happened. It was either a > kernel upgrade or that I installed vlc (for watching

On Tue, 28 Mar 2017, Alice Wonder wrote: > On 03/28/2017 05:53 PM, ken wrote: >> The www has failed me with this, so I'm trying you guys. Sound worked >> great out of the box when I installed 7.2... Yay! I could watch all >> kinds of videos, like on facebook and youtube. And I could listen to >> most podcasts too. But then something happened. It was either a

Hi, On Thu, Mar 5, 2015 at 2:18 PM, SellBuy Sammamish <sellbuysam at gmail.com> wrote: > Friends, > > My name is Igor, I am new to this forum. > > I have a peculiar problem with my OGG/Speex implementation: I encode a short > PCM stream in OGG/Speex, but the result can not be read by VLC and MediaInfo > reports that the file is too short (240ms). In reality the file

---see below -- On Mon, Apr 3, 2017 at 9:53 AM, ken <gebser at mousecar.com> wrote: > On 04/02/2017 01:31 PM, Kay Schenk wrote: > >> >> >> On 03/29/2017 06:43 AM, ken wrote: >> >>> On 03/28/2017 08:53 PM, ken wrote: >>> >>>> The www has failed me with this, so I'm trying you guys. Sound worked >>>> great out of

Thanks for the two suggestions. I tried VLC, and that did help with Firefox support. Unfortunately, VLC registers itself as a player only for the "application/ogg" type, not for "audio/x-speex". If I change my object code to request an application/ogg MIME type, it plays. I wish that it also showed player controls like QuickTime and other players do, but I am not complaining!

On Sat, Nov 12, 2005 at 10:29:15AM -0500, Scott C. Brown 02 wrote: > There are a few flac players on OS X now, but none (at least none that i know > of) seem to use Core Audio. So they all freak out if i try to play a 24/96 > file. Without even worrying about your 24/96 issue, which OSX flac player have you been using? Here's what I've tried, and why it doesn't work well

On 03/29/2017 04:05 AM, ken wrote: > On 03/28/2017 11:40 PM, Alice Wonder wrote: >> On 03/28/2017 05:53 PM, ken wrote: >>> The www has failed me with this, so I'm trying you guys. Sound worked >>> great out of the box when I installed 7.2... Yay! I could watch all >>> kinds of videos, like on facebook and youtube. And I could listen to >>> most

Hi, I have a file fileFoo.R, say that contains these two lines, invoking function foo that is specified in "foo_details.R": source("foo_details.R") foo(parameter1) I want to specify and pass parameter1 in my command line when invoking R in linux: R --no-save <fileFoo.R. How can I do that? And how can I retrieve the value of parameter1 in my fileFoo.R function

The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I

On Mon, Apr 03, 2017 at 12:53:54PM -0400, ken wrote: > On 04/02/2017 01:31 PM, Kay Schenk wrote: > > > > > >On 03/29/2017 06:43 AM, ken wrote: > >>On 03/28/2017 08:53 PM, ken wrote: > >>>The www has failed me with this, so I'm trying you guys. Sound worked > >>>great out of the box when I installed 7.2... Yay! I could watch all >

sox works great. to splice out a 10-minute segment starting 12m34s into a .wav file: sox infile.wav outfile.wav trim 12:34 10:00 to splice two segments together, well: cat seg1.wav seg2.wav > joined.wav <p>samurai.fm wrote: > SOX might work? > > -----Original Message----- > From: owner-icecast@xiph.org [mailto:owner-icecast@xiph.org] On Behalf Of > Mailing List Receiver

I spent some more time with the Ogg and Speex format specs, and I realized that using the "application/ogg" MIME type is technically sound, since Speex is contained in an Ogg wrapper. To get full browser support, though, it is best to rename it so its file extension is "ogg". Some browsers do not support files where the MIME type and file extension are different, based on

Friends, My name is Igor, I am new to this forum. I have a peculiar problem with my OGG/Speex implementation: I encode a short PCM stream in OGG/Speex, but the result can not be read by VLC and MediaInfo <http://mediaarea.net/nn/MediaInfo> reports that the file is too short (240ms). In reality the file contains about 2.7 sec worth of audio. Another interesting thing I noticed is that the

On 03/28/2017 11:40 PM, Alice Wonder wrote: > On 03/28/2017 05:53 PM, ken wrote: >> The www has failed me with this, so I'm trying you guys. Sound worked >> great out of the box when I installed 7.2... Yay! I could watch all >> kinds of videos, like on facebook and youtube. And I could listen to >> most podcasts too. But then something happened. It was either a

> > I think the easiest way to make all of this "just work" would be to > provide > > a default output filename for both encoding and decoding, e.g.: > > > > flac file.wav > > > > would produce file.flac, and > > > > flac -d file.flac > > > > would produce file.wav. That way, flac *.wav and flac -d *.flac > are >

On Tue, May 01, 2001 at 12:28:40PM -0700, Josh Coalson wrote: > OK, I kind of like Matt's usage idea best. I think there are only > two minor downsides: > > 1. You won't be able to do basename renaming within the command > anymore, i.e. 'flac 01.wav songname.flac', you have to do a > 'flac 01.wav && mv 01.flac songname.flac' Or: flac 01.wav -

I may be a bit behind, since I haven't looked at the latest documentation in CVS. My apologies if these problems have already been solved. I think having a default file name is a good idea, but it should be just a default. There should also be a '-o' option to specify the output file name. This option would only apply if there is one input. '-o' should also accept a