![]() ![]() Separate Midi Designer Pro layouts will be required per algorithm creating further cumbersome complications. There are a lot of possible controls per algorithm, so there will be more than one page per algorithm. Every manufacturer with somewhat different terminology is part of the learning curve.and various users with different terminologies can blur the lines, too. I just got a PCM81, so learning that first will clearly take some time. I'm just getting started on using Midi Designer Pro to control PCM-81 with ipad. It does not however replace the mental time and energy it takes to 'build' a preset of your own. Makes editing of an existing preset easier and could be used in a live scenario as an alternative to multiple pedals. You'll need to carefully consider which parameters to map to sliders and also will need to make separate maps for each algorithm you want to use. Map a variable sysex string to each of the 16 sliders to control a parameter so you can tweak settings a bit easier in real time. Most decent fx units can receive sysex and have a MIDI implementation guide. Find yourself a desktop midi controller that can send advanced sysex with variable bits in the string, eg Peavey PC1600(x). There is a slightly easier route to go if you like. To spend 15 minutes hunched over to see that little blue screen & twiddle knobs was the easy part and therefore very well tolerated. Then I've spent a week thinking how I'm going to make it work with hours of discussion over Skype with We both tried multiple ways how to do it - failed / troubleshooted / succeeded AND discovered some new ideas and tips on the machine in the process. Probably has taken me 30 years of listening to music with a critical ear, 3-4 years of reading HRI / TGP / gearslutz / reddit / etc posts, studying many of the factory presets to understand how they have been constructed and many many hours of direct conversation with people who know the unit like the back of their hand. So this week I've created a 16 step sequencer / arpeggiator using quad>hall. Choosing the algorithm template, managing the modulation sources and destinations, setting up controls like the soft row, pedals & external modulators and often working within the limitations of the unit and thinking about ways to work around and exploit these. Once you know what you want to achieve, how do you go about setting it up. Then on the PCM8x for example you need to choose an algorithm template that would best suit your requirements for 'adjuncts', ie do you build a circular delay on CHORUS+RVB so you can use voice 4-6 to add a chorus in parallel or do you build it on M-BAND+RVB so you can use the filters and diffusion in the feedback path? If you want to 'build' any effect from scratch you must know what building blocks are required. For this a deep understanding of how effects are made is required and this takes a long time, experimentation and a critical ear. The first step is UNDERSTANDING what you're trying to set out to achieve. ![]() Also that might take 5-15 minutes total if you have used the unit for a while and are familiar with it. For me making a new preset is a three step process, the last and easiest by far is twidling the knobs on the machine, viewing the little blue screen. However, things need to be put into perspective. Wish I'd had a computer editor to do that a bit quicker. I spent 10 minutes the other day entering in 36 pivot points for pitch voices the other day for a new preset I'll be posting soon. Making one for PCM8x would be very difficult as the sysex strings change per algorithm, ie the sysex command to change reverb diffusion on concert hall is different to quad>hall. Not likely going to happen - minimal financial incentive for anyone who would want to do it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |