From: Richard B. <bo...@bo...> - 2002-06-13 08:57:45
|
Chris Cannam wrote: > btw, I see that loading a document fails completely if an audio > file can't be found. I assume this will change? Yes it will. It'll load the file and then ask you where you want to search for the audio files - and then if they can't be found manually it'll get rid of them. > at the moment the only way I can load outofspace.rg is by editing > the file to change the audio path Depends where you have your audio files. The mechanism nows breaks down like this. We have an audio path which is where all newly recorded audio files are set to (the audio record path in the properties). The path will be used to search for any non-absolute path'd (or '~' pathed) audio files found in the RG file. You can also specify audio file by absolute path or relative to $HOME. So for example: <audiofiles> <audioPath value="~/rosegarden/gui/testfiles/audio/"/> <audioLastAddPath value ="~/.kde/share/sounds/"/> <audio id="0" file="909-kick.wav" label="909-kick.wav"/> <audio id="1" file="~/.kde/share/sounds/desktops.wav" label="desktops.wav"/> </audiofiles> Our audio path is ~/rosegarden/gui/testfiles/audio which'll get expanded when the file is read. The "909-kick.wav" audio file is assumed to be in this directory. The other audio file is a home relative path that'll also be expanded. The audioLastAddPath is used to remember where we last added an audio file from so we go back to that directory first next time we want to add. Perhaps these Paths should be just changed to Dirs? They're not really paths at all now (although that was the intention in the first place). B |