Support |
With all the stuff you want to do, the approach is to use a VST host plus several plugins to do the stuff you like. First question is the host: there are the sequencer-based solutions - Steinberg Cubase/Nuendo (the latter only mentioned for completeness, as it most probably is too "professional" for your application), Sony (formerly Sonic Foundry) ACID, Ableton Live! - did I forget anything? Then there are the more modular setups - these are basically applications which allow to freely connect VST (and sometimes VSTi) components and route your ASIO and MIDI interfaces to and from them and use automation. I can think of two right now, AudioMulch and Plogue Bidule. I have been working a little bit with AudioMulch and it's a great tool - most of the really professional people seem to go for Bidule. Then, you do all the effects (including loops and sample triggering) with VST(i) plugins. Live! comes with an acceptable sampler for your D) requirement, as well as some "normal" delays and a cool and flexible reverb which allows from normal up to completely whacked (I think Per here makes great use of it...). The plugins...do a search for "free VST plugin" to get an overview on the freeware/shareware/donateware stuff. The most powerful looper (for the PC) is afaik Mobius (basically eight brother-synced EDP pairs), then there's LloopyLama (a syncable DL4) and AngstroLooper. There are TONS of crazy effects on lots of sites - smartelectronics.com would be the first one which comes to (my) mind, but just do a search on the web - they are easy to find. So the "least number of components used" solution for your requirements might be Live! plus Mobius. Latency is in fact a function of the power of your computer, the other major influence being the interface hardware you use. It works some like this (hey, everyone here - please correct if this is bullshit): First you have a static latency caused by the interface which brings the audio data stream into your computer. This is an idependent value for input and output. Then, your ASIO driver layer uses input and output buffers to allow your application a certain freedom when serving the inputs and outputs. Bigger buffers means more latency. Smaller buffers means more strenuos requirements on how often (and how regularily) your application serves the input/output task. Some applications allow you to set the priority of these tasks (high priority here means less performance available for your creative tasks). And of yourse, the "power" of your computer plays a role here. Interface-wise, the stuff by RME has earned a great reputation with regard to low-latency (haven'd tried their devices myself - yet). The simple rule goes like this: Get a good interface, set your ASIO buffers short, set the I/O tasks to high priority, then your latency is very low - but you need a fast computer to still be able to do something useful. Rainer -----Ursprüngliche Nachricht----- Von: Romain [mailto:rtristelune@yahoo.fr] Gesendet: Freitag, 10. Juni 2005 22:34 An: Loopers-Delight@loopers-delight.com Betreff: Re: Building A Sampler/Looper around a barebone computer. Thanks for the tips. I was interested in Linux because I believed it could be good in the looping department regarding latency...but Windows might be as good if you tune it, and as you said, there is more available audio software. What I expect to get is: A) A simple and good quality live looping. I mean for example, I press button 1 on the foot controller, record let's say a guitar rythm, and if I press button 2 the rythm plays along, and if I play button 3, the loop is saved but no played + some tricks about quantization => the sample would be cut nicely, not in the middle of 2 beats !! + ability to play stop the recorded loops independantly B) Some good delays and reverbs, switchable via foot controller C) Weird FX (bit-crusher, octaver) switchable as well D) Ability to trigger some pre-recorded samples as well. I guess I can achieve this with little latency on a pretty small computer with windows OS if I tune it for music only. --- Jeff Larson <Jeffrey.Larson@Sun.COM> a écrit : > Romain Rochas wrote: > > 3)- A pedal board => should be plugged directly > via USB or Via a > > MIDI->USB interface (Midiman) (any suggestions ?) > > Behringer FCB 1010 with any single port MIDI->USB > interface. > > > About software, I need: > > 4) - a live processing main software which can > loop and which can map > > the pedal actions to actual sampling/processing > command > > Well, this is a rather large topic that is discussed > at least > once a month here and on many other forums. If > you're determined > to use Linux you should explore some forums devoted > to Linux audio > applications. There are some good Linux looping > applications such > as SooperLooper and Freewheeling, but in general I > think you will > find that there aren't many choices unless you are > willing to write > your own software. By far the majority of audio > applications run > on Mac or Windows. > > > The idea will be to have the audio main > application being launched at OS > > startup, so I would'nt even need a screen (could > display the presets > > info on the pedal board ?) > > I doubt you will be able to do this without a > screen. Even dedicated > hardware devices have LCD's and LED's to give you > some idea of what > is happening. There are no pedal boards that I'm > aware of that display > messages sent to it by the computer. > > If you were more specific about exactly the kinds of > looping/sampling/fx > functions you want you may get better advice. But > unless you can find > what you need on Linux or are willing to invest many > months of time writing > your own software, you will be better off buying a > cheap Windows laptop > or Mac Mini, learning about VST plugins, and > exploring the very large world > of audio software for those platforms. > > Jeff > > ________________________________________________________________________ ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com