> And how do I configure ALSA midi for wine? Well, alsa should be your driver for Wine, so you shouldn't need to set anything up. > Kontakt listed no MIDI ports on the MIDI tab of settings. hmmm, i would double-check that alsa is being used, there is a page in the WineHQ Wiki on sound, that will describe where to look in the wine registry. maybe i'll install Kontakt here and have a look. > I have tried a2jmidid before, and it worked; so if I can configure ALSA midi > input for WINE app, then it should be sufficient. should be. For midi, i just have my VSTi use my midi-keyboard using alsa-midi. since it's at lower latencies it works perfectly.(while, most vsti are using FST, aside from 2). >> FST/Festige uses Jack-midi exclusively with wine/VSTs. > > That sound promising. I am trying that next. FST is pretty good. i use it for most things. > I have not (yet) given up in WineASIO; I will keep experimenting with it > later. I'm sure you'll get it working. it's given me hassles before, too. >> running windows proaudio apps in wine + >> jack-audio-connection-kit can be a bit confusing at first. > > Well, I have no problem with having to do a bit of experimenting .... if it > works in the end. It can work very well. > I understand what you say, but i simply can't find a satisfactory native > Linux app for what I want to do. (Which is, authentic piano sound.) > > A good piano synth engine is quite a bit more than a sampler; there are > many, many sophisticated interactions between the various notes, the damper > pedal, etc, etc... it's hard to get it right. It's not just a matter of > playing back samples. (Galaxy Pianos does this with sophisticated Kontakt > scripts.) The only app that comes close is Pianoteq: it has a native Linux > version, and can use JACK midi and audio. I have successfully used it with > my system (the demo version of it, anyway), but the sound is just not > satisfactory. (It is almost completely modeled, uses very small sample set, > smaller than 50M. Ivory II is 40G (for 4 pianos); Galaxi Pianos are about > 5G, per piano.) I don't really need you to explain to me the fundementals of sampling or of modeling in general. I attended a music technology program, so i'm well-aware. Have you considered that jack allows you the flexibility to help accomplish what you are describing?? When i said LinuxSampler for sampling, i meant JUST that - sampling. I myself am using multi-gigabyte piano libraries (in linuxsampler), in combination with modelling and reverb models. with a bit of creativity, and some good libraries, you could probably get some pretty decent sounds, if kontakt doesn't work out. > So I would like to try to get Galaxy Pianos working first. Since I am not > going to do any commercial performances, a few xruns here and there can be > acceptable. (And I plan to improve the quality by adding RAM, so that most > samples can be cached.) I can't say how Galaxy will work, it may work well, it may not. the xruns won't bother you if there is the odd one or two, but it will bother you if they are bursts. it will depend a lot on your hardware, as much as the software. > Can you suggest a simple windows application, the runs in wine, and I can > use it for testing my WineASIO installation, independently of Kontakt? I've sort of already done that. i recommended SAVIhost. - it hosts a single VST (.dll) - there are hundreds, if not thousands of free vsts all over the internet. you can also google around to see what runs in wine. Easiest way to figure that out, is to visit KVRaudio, search for VSTs and select the option to only show VSTs that are 'known to work with the Receptor' option. The Receptor uses wine/linux so it's likely the vst will work, in this case.. download one, wrap it using savihost and try it out. But honestly a lot of ASIO applications work. cheerz
