Let me explain - I perform live, and need to control my synths and plugs in real time, with unexpected patch changes and controller changes. One of my master keyboards is limited in what it can send for patch change (only, and in order, 1,2,5,3,6,8,18.) I change instruments by changing midi transmit channels on my keyboard. So to make things work together properly, I have to remap many patches to specific slots in the synth, the VSTi patch, the Single and the Multi patches. I have been avoiding the Singles mostly, as they dont seem to be relavant to what I'm doing. I send ccs to Sources, to control the plug params directly.
The problem is in trying to save things in a consistent manner. All kinds of unexpected patch name changes and controller re-mapping occur when I try to load/save setups, and I am lost. Typically here is what I do:
Let's select a typical patch, say FM7 in mixer slot5, midi channel 4 wiith the patch in program slot 3. I now have a patch I wish to recall exactly the way it currently is configured, every time I press the button to recall program 3.
1: edit a plug's sound, or copy a patch to this patch, (patch 3.)
2: Save the patch - press Store to save to the FM7 internal set, then Save/File to Patch Bank 'Live Performance' patch 3,
3: To be sure the patch is loaded from this bank and slot, I load the freshly-saved patch back into the synth, this time from the Patch bank.
4: Press Store on the FM7 synth to store the patch (including where it came from) into the FM7 lib. At this point, I may optionally store the entire lib as an FM7 fxa bank.
5: Re-store the patch to the Receptor Patch bank.
When I have loaded all of the patches this way, I save the FM7 bank, and then save the Multi.
In theory, if I understand correctly, all I need to do is recall this setup and all the pieces should be in place, but frequently I get the factory default lib instead, or thelib names have all been messed up because when I issue a patch change, the new sound is loaded but the name is copied to the current preset program slot name (if the synth was resting at patch 3, pressing preset 5 loads preset 5 to the buffer, changes the name of preset 3 to match and generally fouls up the layout.
Can anyone help me clarify: I need to have all my patch setups self-consistent, how do I save things to make this happen? (Notice I am eing very generic in my language here, because I don't see how I can be so far off, I must be not just DOING something wrong, but THINKING about the layout incorrectly, I need a paradigm shift. Help. please..
OK, I'm still confused re files structure-long post,, sorry
Moderators: Meffy, farhan, Bryan@MuseResearch, gary@museresearch, Kevin@MuseResearch
OK, I'm still confused re files structure-long post,, sorry
2006-07-04T19:21:58+00:00
Let me explain - I perform live, and need to control my synths and plugs in real time, with unexpected patch changes and controller changes. One of my master keyboards is limited in what it can send for patch change (only, and in order, 1,2,5,3,6,8,18.) I change instruments by changing midi transmit channels on my keyboard. So to make things work together properly, I have to remap many patches to specific slots in the synth, the VSTi patch, the Single and the Multi patches. I have been avoiding the Singles mostly, as they dont seem to be relavant to what I'm doing. I send ccs to Sources, to control the plug params directly.
The problem is in trying to save things in a consistent manner. All kinds of unexpected patch name changes and controller re-mapping occur when I try to load/save setups, and I am lost. Typically here is what I do:
Let's select a typical patch, say FM7 in mixer slot5, midi channel 4 wiith the patch in program slot 3. I now have a patch I wish to recall exactly the way it currently is configured, every time I press the button to recall program 3.
1: edit a plug's sound, or copy a patch to this patch, (patch 3.)
2: Save the patch - press Store to save to the FM7 internal set, then Save/File to Patch Bank 'Live Performance' patch 3,
3: To be sure the patch is loaded from this bank and slot, I load the freshly-saved patch back into the synth, this time from the Patch bank.
4: Press Store on the FM7 synth to store the patch (including where it came from) into the FM7 lib. At this point, I may optionally store the entire lib as an FM7 fxa bank.
5: Re-store the patch to the Receptor Patch bank.
When I have loaded all of the patches this way, I save the FM7 bank, and then save the Multi.
In theory, if I understand correctly, all I need to do is recall this setup and all the pieces should be in place, but frequently I get the factory default lib instead, or thelib names have all been messed up because when I issue a patch change, the new sound is loaded but the name is copied to the current preset program slot name (if the synth was resting at patch 3, pressing preset 5 loads preset 5 to the buffer, changes the name of preset 3 to match and generally fouls up the layout.
Can anyone help me clarify: I need to have all my patch setups self-consistent, how do I save things to make this happen? (Notice I am eing very generic in my language here, because I don't see how I can be so far off, I must be not just DOING something wrong, but THINKING about the layout incorrectly, I need a paradigm shift. Help. please..
thesoundsmith
https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=79237
-
- KVRian
- 524 posts since 25 Aug, 2005
Post by thesoundsmith »
Locked
1 post
• Page 1 of 1
Return to “Muse Research and Development”
Jump to
- The Main Forums
- ↳ KVR Studio Manager
- ↳ Getting Started (AKA What is the best...?)
- ↳ Instruments
- ↳ Effects
- ↳ Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)
- ↳ Guitars
- ↳ Mobile Apps and Hardware
- ↳ Soundware
- ↳ Samplers, Sampling & Sample Libraries
- ↳ Hardware (Instruments and Effects)
- ↳ Modular Synthesis
- ↳ Sound Design
- ↳ Production Techniques
- ↳ Music Theory
- ↳ Computer Setup and System Configuration
- ↳ DSP and Plugin Development
- ↳ DIY: Build it and they will come
- ↳ Music Cafe
- ↳ Sell & Buy (+Special Offers, Deals & Promos)
- ↳ KVR Experts
- ↳ KVR Developer Challenge 2026
- ↳ Everything Else (Music related)
- ↳ Off Topic
- ↳ Off Topic Classics
- ↳ Machine Learning and AI for Music Creation
- Official Company Forums
- ↳ 2getheraudio
- ↳ accSone
- ↳ Acon Digital
- ↳ AcousticsampleS
- ↳ AcousModules
- ↳ Agitated State
- ↳ AIR Music Technology
- ↳ AMG
- ↳ Ample Sound
- ↳ Antares Audio Technologies
- ↳ Apisonic Labs
- ↳ APU Software
- ↳ apulSoft
- ↳ AriesCode
- ↳ Arts Acoustic
- ↳ Arturia
- ↳ Audjoo
- ↳ AudioSpillage
- ↳ Audiority
- ↳ Best Service
- ↳ Big Tick
- ↳ Bitwig
- ↳ Controller Scripting
- ↳ Blue Cat Audio
- ↳ Cherry Audio
- ↳ CWITEC
- ↳ Embertone
- ↳ energyXT
- ↳ Eventide
- ↳ Expert Sleepers
- ↳ forward audio
- ↳ Future Audio Workshop
- ↳ FXpansion
- ↳ g200kg
- ↳ Harrison Mixbus
- ↳ HG Fortune
- ↳ Homegrown Sounds
- ↳ HoRNet Plugins
- ↳ Ilya Efimov Production
- ↳ Image Line
- ↳ Impact Soundworks
- ↳ Indiginus
- ↳ Insert Piz Here
- ↳ Ju-X
- ↳ Kirk Hunter Studios
- ↳ Kirnu
- ↳ Kong Audio
- ↳ Krotos
- ↳ Kuassa
- ↳ KV331 Audio
- ↳ LennarDigital
- ↳ Les Productions Zvon
- ↳ Liqube Audio
- ↳ Loomer
- ↳ LVC-Audio
- ↳ Maizesoft
- ↳ Manytone Music
- ↳ Media Overkill (MOK)
- ↳ MeldaProduction
- ↳ Mellowmuse
- ↳ MIDIMood
- ↳ moForte
- ↳ Mozaic Beats
- ↳ mucoder
- ↳ MusicDevelopments
- ↳ Tips & Tricks
- ↳ MusicLab
- ↳ MuTools
- ↳ New Sonic Arts
- ↳ NUSofting
- ↳ Oli Larkin Plugins
- ↳ Orange Tree Samples
- ↳ patchpool
- ↳ Photosounder
- ↳ PlugInGuru
- ↳ Polyverse Music
- ↳ Precisionsound
- ↳ Premier Sound Factory
- ↳ Psychic Modulation
- ↳ Realitone
- ↳ Resonance-Sound
- ↳ Reveal Sound
- ↳ Roger Linn Design
- ↳ rs-met
- ↳ S3A: Spatial Audio
- ↳ SaschArt
- ↳ Smart Electronix
- ↳ sonible
- ↳ SonicBirth
- ↳ Sonic Reality / eSoundz.com
- ↳ Soundiron
- ↳ SPC Plugins
- ↳ Sugar Bytes
- ↳ TAL Software
- ↳ Tokyo Dawn Labs
- ↳ Tracktion
- ↳ Tweakbench
- ↳ u-he
- ↳ u-he Linux support
- ↳ UJAM
- ↳ United Plugins
- ↳ VAZ Synths
- ↳ Virharmonic
- ↳ xoxos
- ↳ XSRDO - SynthCraft
- ↳ ZynAddSubFX
- Site Stuff
- ↳ Site Stuff
- Archived Forums
- ↳ AlgoMusic
- ↳ easytoolz
- ↳ Elevayta
- ↳ Hollow Sun
- ↳ LinPlug
- ↳ Muse Research and Development
- ↳ Shuriken
- ↳ SoHa Sound Design
- ↳ Soniccouture
- ↳ Topten Software
- ↳ Valhalla DSP
- ↳ CK Modules & VST
- ↳ Sennheiser AMBEO
- ↳ Muon Software
- ↳ Westgatesounds.net
- ↳ Squaredheads
- ↳ Sonigen
- ↳ CFA-Sound
- ↳ Back In Time Records
- ↳ Livelab.dk
- ↳ Skytopia
- ↳ audioD3CK
- ↳ Inspire Audio
- ↳ Krakli
- ↳ Drumdrops
- ↳ Futucraft
- ↳ OverTone DSP
- ↳ RaXnTraX
- ↳ solar3d-software
- ↳ Signaldust
- ↳ Soundemote
- ↳ ReleaseLab (Powered by Artist Expansion)
- ↳ Wolfgang Palm
- KVR Forum index
- All times are UTC
- Delete cookies
