Can DnD from Edison (only) to DirectWave (only). Cannot DnD from other hosts/appz to DirectWave
This is bad: Cannot DnD from DirectWave to anything else, not even Edison.
DnD from Windows Explorer to DirectWave works.
Keymap is a Mac-only application. The EXS24 format is supported by all major sample players, and Keymap can write mapping data inside samples, so that any reasonably implemented sampler can actually import the files either from the instrument data or from the mapping data inside sample files.shamann wrote:Judging from their website, am I correct in assuming that it only works with EXS24? So, one would need both a Mac and Logic to make use of Keymap?spectrum wrote:Well....try Keymap. It's pretty much light years ahead of everything.
This "Keymap" is a cruel joke. Aside from the very lovely Mac interface, let's take a look at what's really being provided here. "Keymap" seems to be nothing more than an EXS-format bank creation utility, that does not even have sample editing.spectrum wrote:Well....try Keymap. It's pretty much light years ahead of everything.
Well, Keymap *has* a built in sample editor. Actually there is a sample editor in each editor window, and they are all interconnected.lordvader48 wrote:This "Keymap" is a cruel joke. Aside from the very lovely Mac interface, let's take a look at what's really being provided here. "Keymap" seems to be nothing more than an EXS-format bank creation utility, that does not even have sample editing.
Ok, but we have the sample editor....lordvader48 wrote:How useful can something like this be? I mean think about it for just a second. Sure, "Keymap" may or may not be able to "integrate with an external Editor", but so what? Isn't preparing the samples for an EXS bank a central part of what this kind of a program should do? "Externalizing" the waveform editing destroys workflow, and makes it a lot harder to create banks because of all of the back-and-forth required with samples.
Yes, but we have a sample editor, a loop editor, and many other editorslordvader48 wrote:And what about preview? Don't you really need to be able to listen to the samples in context, so you have some idea of what you're creating? Well I think so.
Here I disagree with you. I mean: integration is wonderful, and we integrated a lot of things in Keymap (streaming audio engine, instrument editor, sample editor, surround mixer, loop editor, setup editor, etc) but how many times should the wheel (the sample player plugin) be re-invented? How many samplers do you really need? What about getting some more independence from the sample playback engine when building your instruments? What about saving processed samples so you can use them anywhere right now and in the future?lordvader48 wrote:These days, building a softsampler is just not that difficult. Look at both Image-Line and 112db.com, who have each built SAMPLING softsamplers in less than a year's time. The point is that the "distributed sampling model" has really rotten workflow, and it's much better to have INTEGRATION of some core, usable features in one program or VSTi than it is to have everything (lots and lots of features) spread out all over the place with terrible integration.
Keymap was designed to be the "Photoshop" of sampled instruments, and guess what? Photoshop isn't a DVD creation app, or a presentation app, or a movie app, or a web creation app, but it works very well with all these apps and gives you amazing additional capabilities.lordvader48 wrote:"Keymap" clearly delivers the latter.
But here's somewhere that positions differ in this thread. I think many of us who hold that sampling, sample editing, resampling, drag and drop, etc, are good features to have in the sample playback software itself aren't using samplers to make reusable instrument libraries. I've used samplers in my music for about a decade (and prior to that with tape), I've never once felt the need normalize a sample. I use samplers immediately, as I would a synthesizer or a guitar. Stuff goes in, I set it to how I want it to sound, and I start playing it back. I almost never map samples in advance of making music, it is nearly always a function of writing the music itself (or the music comes out of the process of working with the sampler). And that's where the "sampler-bots" come in, because we are looking for sampling tools designed as instruments, not really as archival utilities. I almost never use sounds a second time after they've gone in to a project. There are just too many sounds out there to repeat myself.agoz wrote:The real point for us was looking at the sampling experience and noticing that, after 30 years since the start of the sampling revolution, we still are doing things more or less as we did on the Emulator I: you take a sample, you trim it, you normalize it, you map it on your keyboard, you loop it crossing fingers that you can do that quickly and well, and then you go to the next sample and the next and the next, which if you allow me the comparison, looks more like a Ford car manufacturing line than a creative process.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026