16 Sep
2008
16 Sep
'08
2:30 p.m.
Fons Adriaensen:
On Wed, Sep 10, 2008 at 05:02:12PM +0200, Kjetil S. Matheussen wrote:
Thanks for the input. But do you think ch>2 wavex
files are supported by more software than ch>2 wav
files? Because I haven't even heard of wavex files
before... (wavex files are supported in jack_capture
though, "-f wavex" should do the job, thanks to libsndfile)
jack_capture
============
jack_capture is a program for recording soundfiles with jack. Its default
operation is to capture whatever sound is going out to your speakers into
a file. (But it can do a number of other operations as well...)
Very useful, just one remark: for more than 2 channels
the default should be WAVEX instead of WAV (easy enough
if you use libsndfile). WAVs with more than 2 channels
are technically illegal and refused by some software.
16 Sep
16 Sep
3:15 p.m.
New subject: jack_capture
Am Dienstag, 16. September 2008 schrieb Kjetil S. Matheussen:
Thanks for the input. But do you think ch>2 wavex
files are supported by more software than ch>2 wav
files? Because I haven't even heard of wavex files
before... (wavex files are supported in jack_capture
though, "-f wavex" should do the job, thanks to libsndfile)
wavex is supported by all apps using libsndfile. Where as "standard" wav with
more then 2 channels seems to be supported by proprietary apps on other OSes
(because they decide on the ending or the magic if the file is the right
format) but probably isn't. And will just fill you bug-tracker with "I can't
open jack_captures wav files in app XYZ, your app is broken".
Arnold
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a "rm -rf /". Or ask your
administrator to do so...
3:56 p.m.
New subject: jack_capture
Arnold Krille:
wavex is supported by all apps using libsndfile. Where
as "standard" wav
with
more then 2 channels seems to be supported by proprietary apps on other
OSes
(because they decide on the ending or the magic if the file is the right
format) but probably isn't. And will just fill you bug-tracker with "I
can't
open jack_captures wav files in app XYZ, your app is broken".
Can you clarify this? Do you think wav>2ch is
less supported than wavex>2ch? I'm not going
to set default format based on ideological reasons.
4:08 p.m.
New subject: jack_capture
On Tuesday 16 September 2008 01:54:53 pm Kjetil S. Matheussen wrote:
Can you clarify this? Do you think wav>2ch is
less supported than wavex>2ch? I'm not going
to set default format based on ideological reasons.
I think it's a question of specification. With the original RIFF/WAVE format,
at channels>2, elements of the data layout (specifically, the sample packing
in the 'data' chunk) were explicitly declared to be undefined (essentially
meaning, left up to the implementor), whereas in WAVE-EX they are explicitly
defined. Thus, you have a much better chance of achieving successful
inter-operability for channels>2 with WAVE-EX.
Cheers!
|-------------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|-------------------------------------------------------------------------|
| beta test, v: |
| To voluntarily entrust one's data, one's livelihood and one's |
| sanity to hardware or software intended to destroy all three. |
| In earlier days, virgins were often selected to beta test |
| volcanoes. |
|-------------------------------------------------------------------------|
4:38 p.m.
New subject: jack_capture
On Tue, Sep 16, 2008 at 02:09:36PM -0400, Fred Gleason wrote:
On Tuesday 16 September 2008 01:54:53 pm Kjetil S.
Matheussen wrote:
Absolutely right. A number of different interpretations of the
sample packing have been used by various authors, and they are
not compatible. For this reasons MS has been encouraging (or
forcing) Windows software authors to use WAVEX for >2 ch for
years. Also the channel mapping is undefined in a WAV for >2
channels.
Ciao,
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
Wie der Mond heute Nacht aussieht !
Ist es nicht ein seltsames Bild ?
Can you clarify this? Do you think wav>2ch is
less supported than wavex>2ch? I'm not going
to set default format based on ideological reasons.
I think it's a question of specification. With the original RIFF/WAVE format,
at channels>2, elements of the data layout (specifically, the sample packing
in the 'data' chunk) were explicitly declared to be undefined (essentially
meaning, left up to the implementor), whereas in WAVE-EX they are explicitly
defined. Thus, you have a much better chance of achieving successful
inter-operability for channels>2 with WAVE-EX.
4:47 p.m.
New subject: jack_capture
Am Dienstag, 16. September 2008 schrieb Kjetil S. Matheussen:
Arnold Krille:
I think that when you write non-standard wav files people will try to use them
in other apps (not using libsndfile) and complain about broken/non-working
files created by your app.
Whereas when the files are wave-ex the other apps will either import them
correctly or not import them at all. The later case will (hopefully) result
in people realizing that wav with >2 channels are illegal and wave-ex is
better and demanding wave-ex support from the vendors of those other apps.
It is all theoretical thoughts, but when it comes to inter-operability my
experience is that MS-users will complain if you don't speak their format
while not seeing that open-source apps speak more formats than closed source
apps. Just compare the list of import-filters of MS-Word and OO-Writer, if
you are lucky you can find an Word95 import filter in the standard
word-installation, don't even think about Lotus or other formats...
Have fun,
Arnold
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a "rm -rf /". Or ask your
administrator to do so...
wavex is supported by all apps using libsndfile.
Where as "standard" wav
with
more then 2 channels seems to be supported by proprietary apps on other
OSes
(because they decide on the ending or the magic if the file is the right
format) but probably isn't. And will just fill you bug-tracker with "I
can't
open jack_captures wav files in app XYZ, your app is broken".
Can you clarify
this? Do you think wav>2ch is
less supported than wavex>2ch? I'm not going
to set default format based on ideological reasons.
17 Sep
17 Sep
6:39 a.m.
New subject: jack_capture
Thanks to all. Those sounds like good arguments.
I'm still a little bit reluctant against wavex
though, because googling for the wavex format
hardly gives any relevant hits.
But I guess it's better than wav anyway, so
I'm going to change something. Are you sure
there's no other format that might be a
better alternative than wavex?
And I also wonder if wavex are able
to handle >4GB files? (I couldn't find
any spec about the format on the net)
Because if wavex is not able to handle
more than 4>GB files I have to enable
the same workaround as for wav files.
10:53 p.m.
New subject: jack_capture
On Wed, Sep 17, 2008 at 6:38 PM, Kjetil S. Matheussen
<k.s.matheussen(a)notam02.no> wrote:
Thanks to all. Those sounds like good arguments.
I'm still a little bit reluctant against wavex
though, because googling for the wavex format
hardly gives any relevant hits.
But I guess it's better than wav anyway, so
I'm going to change something. Are you sure
there's no other format that might be a
better alternative than wavex?
And I also wonder if wavex are able
to handle >4GB files? (I couldn't find
any spec about the format on the net)
Because if wavex is not able to handle
more than 4>GB files I have to enable
the same workaround as for wav files.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
you get a lot more useful hits on google with WAVE_FORMAT_EXTENSIBLE
than wavex it seems.
Loki
19 Sep
19 Sep
5:16 a.m.
New subject: jack_capture
hi kjetil!
Kjetil S. Matheussen wrote:
Thanks to all. Those sounds like good arguments.
I'm still a little bit reluctant against wavex
though, because googling for the wavex format
hardly gives any relevant hits.
But I guess it's better than wav anyway, so
I'm going to change something. Are you sure
there's no other format that might be a
better alternative than wavex?
And I also wonder if wavex are able
to handle >4GB files? (I couldn't find
any spec about the format on the net)
Because if wavex is not able to handle
more than 4>GB files I have to enable
the same workaround as for wav files.
fwiw, steve harris used .w64 for his timemachine application. haven't
looked into it myself, but i recall someone over on the sursound mailing
list saying that it was quite sane.
maybe steve will chime in if he reads this...
best,
jörn
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
Kurt is up in Heaven now.
5905
days inactive
5908
days old
linux-audio-dev@lists.linuxaudio.org
8 comments
6 participants
participants (6)
-
Arnold Krille -
Fons Adriaensen -
Fred Gleason -
Joern Nettingsmeier -
Kjetil S. Matheussen -
Loki Davison