Well, it might have helped if I had actually bothered to crack the manual, too. I pride myself on the fact that I never have to do any heavy mental lifting to get around DP or hunt it down in the manual -- most of it's just that straight-forward and logical to find with a couple of clicks. Also, I keep forgetting that DP's audio side, while highly, HIGHLY evolved from where it was back in the days of DP 2 (when I started using it strictly for MIDI composition), isn't as highly-evolved as its MIDI side, so while the ability to do what I needed to do was there, it might not be as obvious as it is when you need to perform a complex MIDI task. Again, I see where I got confused!bayswater wrote:I agree. It would have been a lot easier for everyone if MOTU had just called Soundbites Regions like everyone else.
Of course! That also sounds close to the way I'm used to working with audio files/tracks. I cut my teeth on Vision DSP, where you could open a window to see a list of your audio files. You edited said audio in the context of the audio track, just like you do in DP, but that operation was never represented in Vision. Each chunk of remaining audio was simply labelled whatever the name of the corresponding audio file was on the waveform itself. The markers were all added under the hood, I guess, until you opened Vision's waveform editor and compacted the audio file. So all you really dealt with were audio files, not even "regions" or "clips" -- they existed, you just had no way to look at them other than your edited audio track.I think you get pretty close to seeing a list of audio files if you set the Soundbites window to View By: Filename. It will display a hierarchical list of Files and Soundbites with flippy triangles so you can hide the Soundbites, and just have a list of Files. I'm not sure this a purely a list of source files: it will at least show files from Bounces, Merges, etc.