Displaying 3 results from an estimated 3 matches for "ao_open".
Did you mean:
do_open
2001 Jan 02
0
ogg123: close_dsp_on_suspend and next_on_SIGUSR1 patches submission
...(current->driver_id);
+
+ if (param.quiet < 1) {
+ fprintf(stderr, "Device: %s\n", info->name);
+ fprintf(stderr, "Author: %s\n", info->author);
+ fprintf(stderr, "Comments: %s\n", info->comment);
+ }
+
+ current->device = ao_open(current->driver_id,bits,rate,channels,
+ current->options);
+ if (current->device == NULL)
+ {
+ fprintf(stderr, "Error opening device.\n");
+ exit(1);
+ }
+ if (param.quiet < 1)
+ fprintf(stderr, "\n"); // Gotta keep 'em separated ......
2001 Aug 21
2
ao changes
Why has ao been changed so that there are now two open() functions ?
IMHO the original ao_open() was fine - if you wanted to set the
filename for output, you could add an option via ao_append_option
and if you wanted to avoid overwriting an existing file, you could
stat() it yourself.
Having ao_open_live() and ao_open_file() just makes more work for
the user of the library for no gain, AFAI...
2001 Aug 21
2
ao changes
Why has ao been changed so that there are now two open() functions ?
IMHO the original ao_open() was fine - if you wanted to set the
filename for output, you could add an option via ao_append_option
and if you wanted to avoid overwriting an existing file, you could
stat() it yourself.
Having ao_open_live() and ao_open_file() just makes more work for
the user of the library for no gain, AFAI...