![]() Setup was straightforward once I figured it out, though not easy, particularly where expansion cards were concerned. Korg Z1), Cakewalk Sonar had all of them except the 307, which was easily found. With my hardware (Roland JV1010, MC307, XP60. Some DAWs will have instrument definitions for some hardwhere, while other DAWs will have instrument definitions with other hardware. That's a tricky statement, because it's dependent upon which hardware you're using, and which DAW you're using. These things should come with Logic (as with most other DAWs) These things should come with Logic (as with most other DAWs) and Apple should provide a much simpler process for setting up external synths. My point here is that this whole process is ridiculous. #SONAR INSTRUMENT DEFINITIONS KORG M1 PATCH#So in order for my system to work, I either need to find all the SRX boards and an M3 somewhere, or I need to manually enter hundreds of patch names and bank changes to create the objects from scratch. I haven't been able to find a Korg M3 object anywhere. The ones I have found I copied into the 5080 object and they don't work. I have likewise found an XV-5080, but have not been able to find all the SRX cards for the XV. I also located and copied the JV expansion boards - they now work fine. I found a JV-2080 object on the web, and it works fine. I have searched the web for multi-instrument objects for each synth, and have found a few. The two Roland units each have several expansion boards installed. Here's the problem: I have three external synths, a Korg M3, a Roland JV-2080, and a Roland XV-5080. "You haven't said what your hassle is! Entering patch names? Configuring bank changes?" There are several people here who are very knowledgeable about the Environment who can help you. But if there's something else you're looking to achieve through Environment programming, post back. If there's anything other than synth patch names that are causing you to mess with the Environment, then just STOP. Voila, done.įinally, you shouldn't have to do ANY Environment programming to get MIDI synths to work (other than what I said above, and even that's not always necessary if you've set up your synths in AMS prior to launching Logic). nightmare? How? It should be a piece of cake even if you didn't first define your synths in AMS: all you have to do is create a new instrument (or multi-instrument) in the Environment and set the MIDI port it's connected to. The Environment isn't about pulling in patch names, so your gripe, while not unfounded, has no bearing on the Environment. Seems that what you're after is having the patch names of your synths appear in Logic automatically, and no, that's not something that Logic does automatically. If you're going to go so far as to say the whole Environment sucks then that's going too far. I have spent hours and hours trying to get the Environment configured so I can change patch settings on external synths. Why doesn't Apple just include all the objects with the Logic package? Or find another way to set up patch names within Logic. ![]() Why do I need to go to all the hassle of entering patch names, or finding environment objects on the Web? This is something all the other DAWs provide - but not Logic. ![]() Logic should be able to look at my setup and configure what it needs from that. What are the people at Apple thinking? I've already set up my "environment" in the Audio MIDI Setup utility. This is the most convoluted, bass-ackward system for controlling external synths I've ever seen. Logic is great if you work 100% in the box however, try to use external synths and it's an absolute nightmare. I absolutely loved the program until I got to the Environment. #SONAR INSTRUMENT DEFINITIONS KORG M1 PRO#Ok, I've been using Logic Pro 8 for 3 months. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |