M. Hlatky, S. Heise, and J. Loviscach, "File System Tricks for Audio Production," Paper 7545, (2008 October.). doi:
M. Hlatky, S. Heise, and J. Loviscach, "File System Tricks for Audio Production," Paper 7545, (2008 October.). doi:
Abstract: Not every file presented by a computer operating system needs to be an actual stream of independent bits. We demonstrate that different types of virtual files and folders including so-called "Filesystems in Userspace" (FUSE) allow streamlining audio content management with relatively little additional complexity. For instance, an off-the-shelf database system may present a distributed sound library through (seemingly) standard files in a project-specific hierarchy with no physical copying of the data involved. Regions of audio files may be represented as separate files; audio effect plug-ins may be displayed as collections of folders for on-demand processing while files are read. We address differences between operating systems, available implementations, and lessons learned when applying such techniques.
@article{hlatky2008file,
author={hlatky, michael and heise, sebastian and loviscach, jörn},
journal={journal of the audio engineering society},
title={file system tricks for audio production},
year={2008},
volume={},
number={},
pages={},
doi={},
month={october},}
@article{hlatky2008file,
author={hlatky, michael and heise, sebastian and loviscach, jörn},
journal={journal of the audio engineering society},
title={file system tricks for audio production},
year={2008},
volume={},
number={},
pages={},
doi={},
month={october},
abstract={not every file presented by a computer operating system needs to be an actual stream of independent bits. we demonstrate that different types of virtual files and folders including so-called "filesystems in userspace" (fuse) allow streamlining audio content management with relatively little additional complexity. for instance, an off-the-shelf database system may present a distributed sound library through (seemingly) standard files in a project-specific hierarchy with no physical copying of the data involved. regions of audio files may be represented as separate files; audio effect plug-ins may be displayed as collections of folders for on-demand processing while files are read. we address differences between operating systems, available implementations, and lessons learned when applying such techniques.},}
TY - paper
TI - File System Tricks for Audio Production
SP -
EP -
AU - Hlatky, Michael
AU - Heise, Sebastian
AU - Loviscach, Jörn
PY - 2008
JO - Journal of the Audio Engineering Society
IS -
VO -
VL -
Y1 - October 2008
TY - paper
TI - File System Tricks for Audio Production
SP -
EP -
AU - Hlatky, Michael
AU - Heise, Sebastian
AU - Loviscach, Jörn
PY - 2008
JO - Journal of the Audio Engineering Society
IS -
VO -
VL -
Y1 - October 2008
AB - Not every file presented by a computer operating system needs to be an actual stream of independent bits. We demonstrate that different types of virtual files and folders including so-called "Filesystems in Userspace" (FUSE) allow streamlining audio content management with relatively little additional complexity. For instance, an off-the-shelf database system may present a distributed sound library through (seemingly) standard files in a project-specific hierarchy with no physical copying of the data involved. Regions of audio files may be represented as separate files; audio effect plug-ins may be displayed as collections of folders for on-demand processing while files are read. We address differences between operating systems, available implementations, and lessons learned when applying such techniques.
Not every file presented by a computer operating system needs to be an actual stream of independent bits. We demonstrate that different types of virtual files and folders including so-called "Filesystems in Userspace" (FUSE) allow streamlining audio content management with relatively little additional complexity. For instance, an off-the-shelf database system may present a distributed sound library through (seemingly) standard files in a project-specific hierarchy with no physical copying of the data involved. Regions of audio files may be represented as separate files; audio effect plug-ins may be displayed as collections of folders for on-demand processing while files are read. We address differences between operating systems, available implementations, and lessons learned when applying such techniques.
Authors:
Hlatky, Michael; Heise, Sebastian; Loviscach, Jörn
Affiliation:
Hochschule Bremen (University of Applied Sciences)
AES Convention:
125 (October 2008)
Paper Number:
7545
Publication Date:
October 1, 2008Import into BibTeX
Subject:
Audio Content Management
Permalink:
http://www.aes.org/e-lib/browse.cfm?elib=14697