>Actually, this is just a way to separate implementation from the >design. I have a FILE_IO class, which has above read() and write() >functions. My app uses this interface. What happens on the >implementation level is another thing. Basicly I have subclasses >FILE_IO_STUPID and FILE_IO_CLEVER which actually implement the >read() and write() functions. The first class simply uses fread() >and fwrite(), while the second one launches a disk butler thread and >does more intelligent disk i/o. Kai, I don't suppose you have FILE_IO_EDL implemented yet, do you ? That is, I/O to and from a "file" that is accompanied by an edit decision list. The actual "file" may consist of one or more disk files. I'm going to need to do this for Ardour in the fall. It seems quite difficult to do with buffering etc. If anyone wants to volunteer to write such a beast, that would be great. --p
- Re: [linux-audio-dev] Realtim... Erik Steffl
- Re: [linux-audio-dev] Realtim... David Olofson
- Re: [linux-audio-dev] Realtim... Erik Steffl
- Re: [linux-audio-dev] Realtim... Paul Barton-Davis
- Re: [linux-audio-dev] Realtim... David Olofson
- Re: [linux-audio-dev] Realtim... David Olofson
- [linux-audio-dev] Re: Realtim... David Olofson
- [linux-audio-dev] Re: Realtim... Kai Vehmanen
- Re: [linux-audio-dev] Re: Rea... David Olofson
- Re: [linux-audio-dev] Re: Rea... Kai Vehmanen
- Re: [linux-audio-dev] Re: Rea... Paul Barton-Davis
- Re: [linux-audio-dev] Re: Rea... Kai Vehmanen
- Re: [linux-audio-dev] Re: Rea... David Olofson
- No Subject Frank Carmickle
- No Subject Paul Davis
- [linux-audio-dev] Re: your mail Frank Carmickle
- [linux-audio-dev] Re: your mail Paul Davis
- [linux-audio-dev] alsamixer+ardour Frank Carmickle
- [linux-audio-dev] Re: alsamixer+a... Paul Davis
- Re: [linux-audio-dev] Re: als... Jörn Nettingsmeier
- Re: [linux-audio-dev] Re: als... Frank Carmickle