The MS20 plugin may be most appropriate for this. The result is not really very close but you can see where they were going with it. That series is made to celebrate and somewhat emulate the sound character of the original MS20. That said, the microKorg is a smaller version of the MS2000. It's a fairly simple synth sound that a lot of plugins should be able to do. ![]() So i hope someone can tell me if it's possible to emulate this sound with a Korg vst, or another ? It sound like the A15 (sweepyLead) sound too : ![]() The A52 according to the manual is the "MG Bass1" It's done with the preset A52 according to a comment on this video : "A52 MESS AROUND WITH THE MOD AND CUTOFF AND THERE YOU GO"Īnother example : (the synth is at 10 sec) Posted: Thu 10:40 pm Post subject: Emulate a microKorg sound with a Korg Vst ?ĭo you know if we can emulate this microKorg sound (i know it can be done with the Korg r3 too) with a Korg Vst ? Profile Log in to check your private messages Log inĮmulate a microKorg sound with a Korg Vst ? Owned by Irish Acts Recording Studio & hosted by KORG USAįAQ Search Memberlist Usergroups Register Please use the Contact Us page to send us have your tips.Korg Forums :: View topic - Emulate a microKorg sound with a Korg Vst ?Ī forum for Korg product users and musicians around the world. Please don’t just send shortcuts which are easily found elsewhere, or pull ideas from the manual instead, be creative about your tips & tricks. If you would like the chance to win a stormtrooper iLok, courtesy of iLok, send in tips you think no one has thought about. I route all my internal Pro Tools audio through a final master aux anyway so can just put on a small Time Adjuster delay plug-in to cope with this latency I did a video for some students a while back which should show how to do it. Getting the audio back into Pro Tools if needed can be done by Rewiring the Mac sounds to Pro Tools or use Soundflower which is my preferred option - the latency here should be measured the first time you use it and expect it whenever its used.Note if you dont change the prog change within the track but just in the menu it will revert to the prog change on next play It may be intimidating but its a one off and will work every time you use that IAC bus in this way. Now you can easily find the MIDI instruments by opening prog change on all tracks and you can change them yourself within the track. Hit Change and select your new midinam file and all the names will appear if the syntax is correct. Now in Pro Tools on one IAC MIDI track hit the patch change button and you will see nothing but numbers. Then save with a new name in the same place so if it fails first time youve still got the original. Its usually Apple something for manufacturer and IAC bus for model - but make sure the syntax is exactly the same. Open this in a text editor and open the IAC window in audiomidisetups now all you have to do is change the text file to match Manufacturer and Model from the IAC window. In Library/Audio/MidiPatchNames/Digidesign(orAvidnow)/GeneralMidi folder there should be a GeneralMidi.midinam file. To get the instrument names shown in Pro Tools - they show in the MIDI track program change menu as 1-127 so at this point it is very easy to create a midiname file for use with IAC.Though you have no midi names SimpleSynth just sees the GM MIDI program messages and you should hear all the MIDI on the right instruments from the Mac sound out - not within Pro Tools at this point, but if all you want to do is add decent sounds you can then start creating your PT instruments and bus the MIDI tracks to them ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |