Jump to content

JT3_Jon

Member
  • Posts

    666
  • Joined

  • Last visited

JT3_Jon's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I’m trying to get some of the keyboard patches I made in a recent Logic project to load in Logic 10. I’ve saved these as channel strip presets, and they show up in my “instrument channel strips” in MainStage, but when I try to load them nothing happens. For example, I have a patch I build in ES 2 w/ compression and reverb in the channel strip. If I try to load this, it will act like it loaded something, but the ES2 never shows up in my channel strips. However, if I just load any logic factory channel strip, they load fine and the ES2 and effects like compression space designer, etc load fine. Is this some sort of bug? Or are instrument presets from Logic 10 not compatible with MainStage 2.1.3? Can anyone confirm that this works in MainStage 3? (i.e. save a instrument channel strip preset in logic 10.1 and load it in MainStage 3 - does everything load?
  2. Ended up using a combination of folders which I solo'd and muted, and alternative signature & tempo tracks and it worked ok. Of course you run the risk of forgetting to change the tempo track on occasion, but no big deal. I didn't do any extensive automation for each version, so I'm unsure how well that would work in more complicated alternative versions of things. Guess we will find out in the future. I do wish "Alternatives" worked more like DP's chunks feature where you really can have completely different alternatives in a single session and they load instantaneously since they are all referencing instruments that stay loaded when you switch. I could see Logic doing something similar with its environment architecture, as this is kind of what the folders are already doing, but on an entire project scale would make this much easier to manage. Doubt its high on a feature list unfortunately. Too bad.
  3. I’m working on a song using mainly midi instruments and want to listen to two different arrangements of a section. I thought Logic X’s Alternatives would be the answer, but it seems Alternatives is just a fancy word for two different projects, and it has to reload all my Virtual instruments for each version, which makes it impossible to A-B quickly. I know I can bounce down the one as audio, and A/B them that way, but then I can no longer edit the midi of version that I bounced down as audio. To make things more challenging, the two different versions of the two songs have two different time signatures and two different tempos, along with different parts on multiple instruments. Is my best bet making two different folder objects, two different signature and tempo sets, and do it that way? Or is there an Alternative to Alternatives?
  4. OMG - I AM SUCH AN IDIOT!! I thought it might be a preference, so I went digging and found in the Audio -> General tab the setting called "Sample Accurate Automation." When I put this to Volume, Pan, Sends, Plug-in Parameters and do my test in a blank session everything works as expected! YEAY!! I was about to re-install my entire system as I didn't have these issues in Logic 9. Turns out I had this preference on in Logic 9 and not in Logic 10, lol! Who would ever want this off I do not know. Well, I'm so glad I found this. Even though I wasted many hours tonight, at least I can sleep easy knowing tomorrow I can get back to work.
  5. I'm having issues as well - anyone able to figure this out? edit: turns out my problem was that the preference for sample accurate automation was off. Turned it on and everything is working as expected. Are you still having issues? If so - perhaps your preferences are corrupted somehow?
  6. First off Eric, THANK YOU VERY MUCH for your help! Its very late here and I'm going to bed as I can no longer thing straight, but incase you (or someone else) might be able to give me suggestions here is what else I've tried: I tried launching Logic Pro X while holding Control-Shift - nothing seemed to happen? So I took and old Logic 9 song, opened it in Logic 10, and tried drawing automation and it too was playing back before it happened (i.e. drew on bar 17, started playing back in bar 16). However, what was completely weird about this project is when I played it back, what I was hearing was almost a full beat behind what I was seeing in Logic! For example I would have a tempo change and it would occur in logic well before I would hear it, which is completely the opposite of what is going on with insert automation (I hear it before I see it change). Talk about frightening! I then loaded the same project in Logic 9 and it seems to work as expected. I then created a brand new empty logic file, created an instrument and drew in some automation, and again its playing back automation before it actually gets to that point in Logic!!! How is this even possible?! I even went so far as to uncheck all plugins & instruments from the AU manager in Logic and using only logic plugins in a blank session I STILL get the same behavior! This was all done on "fresh" preferences (removed all com.apple.logic preferences from my user -> Library folder. I've tried both using my audio interface (Apollo) and built in audio. I never experienced problems like these back when I was on 10.8 (upgraded to 10.9.5 for the latest logic update) but granted I didn't use Logic 10 much then, so perhaps this has always been a problem on my system? Any advice would be greatly appreciated!!
  7. Scarily enough dumping the preferences didn't fix the issue! I then switched the audio preferences from my Apollo to my computers built-in audio hardware and it too exhibited the odd behavior! Any further advice would be appreciated as frankly I'm at a loss as to what to do next? I recently made the switch to Logic 10, and this was actually my first song in Logic 10. Maybe I'll try loading a different project started in Logic 9 and see what happens... Is there an easy way to launch the plugin without any 3rd party AU's and see if that fixes it? edit: I manually removed all plugins expect for logic plugins its still exhibiting the behavior on my main system - something must be wrong with my system.
  8. Hello Eric!! Nice to hear from you again!! Well, I just moved my logic file to my laptop (which doesn't have all the UAD plugins and ilok plugins installed) and the automation functions correctly, so I'm sure it will function correctly for you as well. Seems like its a system specific problem - maybe to do with UAD and plugin delay compensation or something (spitballing). I'm going to try rebuilding my preferences and see what happens. Any other advice would be appreciated.
  9. Hello everyone, I'm experiencing a weird situation with automation that hopefully someone can help me with. For some reason Logic is playing back track automation before it actually occurs in my project! Specifically when I automate plugin or instrument parameters. For example, say I'm running Logics chorus and want to automate the wet level and draw it to happen from bar 7-10, when I play back the song it will actually read the mix automation somewhere in the middle of bar 5 - almost 2 bars early! This is true of logic plugins & 3rd party plugins, both as inserts and instruments. Oddly enough, this is only occurring on plugin parameters - the track volume & pan automation seem to read and play back just fine. This project was created in Logic 10.1 from scratch (i.e. did not continue off a template), but I did import tracks from a different Logic 10 project. I dont know how long this has been going on as today was the first time I tried automating a plugin and got confused as to why it wasn't playing back correctly. Let me know if you need more information and/or an actual video showing whats going on. I'm hoping there is some sort of weird preference I clicked or something, but I dont see how anyone would want this as a "feature." Perhaps there is something wonky going on with my plugin delay compensation? Thanks in advance for any help you can provide!
  10. first off, ALWAYS have a backup of your current system before upgrading anything, that way you can get back to exactly where you were should something tragic happen. I believe time machine can do this, but I personally use SuperDuper and keep a clone of my system drive on an external HD. I'm running a 2009 Nehalem mac pro and too had reservations about upgrading my OS, but I'm running Logic 10.1 on OS 10.9.5 and though I only upgraded a few weeks ago, there have been no show stopping bugs. Again if you adequately backup your system before upgrading, there is no harm in trying updates and see how you get along on your system, as you can always revert.
  11. I know you can do this in Cubase, so I'm hoping its possible in Logic though so far every tutorial I've watched on youtube doesn't show this so I'm starting to worry its not possible. I'd like to look at the pitches of my original vocal track while making 2-3 part harmonies in flex pitch. Similar to how I would like to view all 3-4 notes of my piano chords in the piano roll, I want to be able to view all my harmony vocals at the same time in flex pitch so I can build correct chords. Is this possible? If so do you mind explaining how as I can't seem to figure it out.
  12. BTW, if you are keeping all the midi on one track just so you can see both instruments in the piano roll, you can still see both tracks in a single piano roll by selecting both regions first and then opening the piano editor. You have make sure in the "view" pulldown that "selected regions" is checked. This way you can view both tracks in a single piano roll. Then if at any time you want to just view one of the selected tracks, double click on a note in that track and it will just show that regions midi. Want to view all selected again, double click the background and all selected regions will be shown again. So IMO there is really no reason not to keep each instrument on its own track by using the "new with next midi channel" key command. Still a bug though, and hopefully you reported it.
  13. Well you got me curious so I ran a test. I created a fresh project with 5 fully loaded omnispheres using either multitimbral instruments with 8 total tracks vs multitimbral instrument with the instrument + 7 aux tracks. To make sure it was fair, even though the multitimbral without auxes would normally be a stereo instance of omnisphere, I loaded each with the same “multi-output” version of the instrument. Also to make sure it was fair I created both in blank Logic sessions and restarted my computer after creating the first test, and created the 2nd second one from scratch. Also incase it matters I did not duplicate any instruments to create this, and each omnisphere had completely different instruments per session, all loaded from scratch as I would in a normal composing situation. Activity Monitor Results: Midi Channels Version CPU: 255% memory: 2.07GB Aux Channels Version CPU: 258% Memory: 2.08GB So to me, at least in this test, they both run the same! Very interesting!! So I guess additional Aux tracks do not seem to adversely effect performance so it looks like I can use the aux track versions with no fear!
  14. Yeah, I understand that thinking too, but ins't there a difference between new audio objects vs midi objects? I dont know what "new with next midi channel" creates, but in my mind an Aux track is for sure a new audio object that Logic has to create (new internal audio routing), while the "new with next midi channel" points to an audio object (no new internal audio routing as its still going out the same instrument) and might be similar to how a alias points to a file? I dont know, but though "new with next midi channel" creates a new object in the environment, If I make 15 of them it is still pointing to a single audio object (in this case an instrument) while creating 15 new aux tracks is for sure creating 15 new audio objects with Logic internal audio routing to each aux. In my mind, the latter would take more audio resources. Like I said I dont have any hard data to back this up (and unsure how I would gather it or I would gladly test it) but I'd be surprised if both methods use the same amount of CPU resources. Again, I could be WAY off though, as Logic has surprised me in the past (i.e. creating a multiple Kontakt instance uses less resources than the first instance - still unsure how that works, haha) What do you think?
  15. Well, every aux you create is another audio object in Logic, so your taxing your audio system more. Where as an additional track set to the same instrument (but different midi channel) is not adding anything additional to the audio system. Thats my thought process anyway, have no actual data to back this up, except that it takes noticeably longer to load a project full of aux tracks vs one with just midi tracks. (at least this was true in Logic 9 - just started using Logic 10 recently). Wonder if anyone has hard data as it would be nice to know.
×
×
  • Create New...