Skip to contentSkip to conversation

File descriptors and Sound

DISCUSSION Rui Sousa 4 participants 5 messages Aug 8, 1999 – Aug 13, 1999 Sound

lore
Share & tools
lore

Rui Sousa

author
#0 lore raw

Hi,

Can someone give me some pointers on how to get control over /dev/audio by two different applications?

I realized that it's not possible to open /dev/audio in two separate applications while trying to setup speakfreely...

If the device is full-duplex how can I have one application reading it and another writing?

Thanks in advance

Signature · 1 line
Rui Sousa
#1 lore raw
Quoted 2 lines

If the device is full-duplex how can I have one application reading it and another writing?

You either do file handle passing (funky) or normally one program runs the
other: ie

	open file
	fork()
	
	child:
		exec other app (which inherits file)
		exit

	parent:
		run code
author
#2 lore raw
In reply to Rui Sousa
Quoted 10 lines · Alan Cox
Quoted 3 lines

If the device is full-duplex how can I have one application reading it and another writing?

You either do file handle passing (funky) or normally one program runs the
other: ie

open file
fork()

Quoted 6 lines

child:
exec other app (which inherits file) exit

parent:
run code

As I said before I'm trying to get speakfreely to work in full-duplex mode.
This program has two components (two independent processes) that try to access /dev/audio. The thing is that during execution they open/close /dev/audio multiple times so I think that the second method wont work (correct me if I am wrong).

Can you indicate me some (online) documentation concerning file handle passing?

Thanks

Signature · 1 line
Rui Sousa
#3 lore raw
In reply to Rui Sousa
Quoted 2 lines · Rui Sousa

Can you indicate me some (online) documentation concerning file handle passing?

man 7 unix in very recent manpage distributions (formerly part of netman).

Signature · 4 lines
Matthew Wilcox <[email protected]>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson
#4 lore raw
In reply to Rui Sousa
Quoted 6 lines · Alan Cox
Quoted 2 lines

If the device is full-duplex how can I have one application reading it and another writing?

You either do file handle passing (funky) or normally one program runs the
other: ie

Quoted 9 lines
	open file
	fork()
	
	child:
		exec other app (which inherits file)
		exit

	parent:
		run code

ok,
but what if one wants to implement some sort of MIDI-thru util ? (not related to /dev/audio but /dev/midi , but the problem is the same:
2 different apps want to access to the same device,
the one in O_RDONLY , the other in O_WRONLY mode)

For example:

/dev/midi00 external midi port
/dev/midi01 AWE64 internal synth

Assume the midi-thru util opens /dev/midi00 in O_RDONLY and /dev/midi01 in O_WRONLY mode.
The app reads the incoming midi data from the midi00 device and applies certain event filters and then writes the data to /dev/midi01. (the synth).

It would be nice if a sequencer was still able to to write to /dev/midi00 to drive an external synth.

Since the sequencer tries to open /dev/midi00
(assuming that the sequencer opens the device only in O_WRONLY mode),
I can't use the fork() method to inherit filehandles.
Is there a way to do this ?

What is in your opinion the best way to implement a virtual midi device in userspace ? Like the midi-thru example
Using a regular named pipe ?
But sequencers would not recognize this virtual device since they look in /dev/sndstat for available devices.

regards,
Benno.