"Hendrik Jan Veenstra" <h@...> wrote: > I'm sorry but to me this sounds exactly identical to the proposed > "cycle" solution. Yes it is. Only in my case, without occasional playback errors that stop Logic and thus stop the exs updating. > The point obviously is to have *only* the "next > instrument" command in the cycle, and not have the exs play any > "real" midi stuff at the same time. Sure. For me, if Logic is playing and the exs is searching for samples or loading big samples, Logic's playback gets delayed as the disk interrupts slow down playback, so Logic complains of lost sync or a sample rate change or something (I forget offhand). Logic is rock solid otherwise, and I can get a pretty good performance on my p3-600... > No overloads or whatever. Cool. I'm just saying for *me*, the cycle way doesn't work as well, so I posted this for anyone else who *may* have experienced a similar problem. > The only problem that might occur is if you have multiple > samples with the same name, and the exs asks which one you want to > use -- then you'll be stuck with a dialog somewhere midway during > processing. Yep. Ben Hall www.benhall.co.uk
Message
Re: [exs] EXS24 scanning for instruments
2002-11-14 by Ben Hall
Attachments
- No local attachments were found for this message.