Jump to content

gno

Member
  • Posts

    176
  • Joined

  • Last visited

gno's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. In addition to some of the notes sticking, I'm noticing that the Marimba timing isn't right. I've got notes on the Marimba that are "octave tripled" that are supposed to play in unison and you can hear that the notes aren't all playing together. If I stop playback and move the play head right before the marimba part, they play perfectly. So this has to be a Midi congestion problem. This never happened before El Capitan. This project is one of my largest - 59 tracks - mostly midi tracks using big sound libraries from EastWest, Vienna Symphony, Trilian, Superior Drummer. And Logic seems to be choking. But in reality my project is small compare to others using even larger libraries. I've set my I/O buffer to 1024 and it doesn't seem to help. Sonar had a separate Midi note buffer, ( different from audio ) that used to take care of midi congestion problems like this. Does logic have any other buffers that I can set?
  2. I've got a project where some notes of Violins and Clarinet are not turning off. This project has worked fine in the past prior to El Capitan. When I solo one of these tracks, the problem seems to go away, However, even if it seems that the problem is gone, when I bounce, the problem comes back. It is not always repeatable, making me think there is a midi traffic issue where the midi note off signal didn't get received by Play. I increased the I/O buffer size to 1024 but that didn't fix it. I hadn't updated Play for a while, and noticed there was a new version available, which I installed. But the problem persists even with the new version of play.
  3. I found it - Preferences - Audio - General and change Sample Accurate Automation to include Plug-in parameters. Not sure why this wouldn't be the default? Seems kind of strange.
  4. I'm trying out my new Waves OneKnob Filter on a track and it isn't working correctly. I'm drawing automation curves to control the Filter Frequency, and for some reason, during playback, the Filter Frequency is moving too fast toward the next node. You can see below on the first image, that the knob moved to 7.0 way before it was supposed to. http://i687.photobucket.com/albums/vv239/guitartrek/OneKnob2_zpsvpucuj5s.png If I manually move the playhead, the knob correctly stays at 4.0 http://i687.photobucket.com/albums/vv239/guitartrek/OneKnob1_zpskiem8gvx.png I checked other automation curves that are controlling, for example, volume, and those are working perfectly. This seems like a Logic issue, as it must be telling the OneKnob when to move and giving the instructions prematurely?
  5. Upgraded my MBP with lots of plugins and everything working except Ozone4. Looks like Izotope is aiming for the end of November for El Capitan compatibility. Unfortunately Ozone4 is not on the list. I never upgraded to Ozone5 or 6 or 7 because Ozone4 had what I needed. I guess I may have to shell out some bucks.
  6. Ok I upgraded my iMac to El Capitan with no problems...I'm only using UAD and Waves on this machine. I then upgraded my MacBook Pro where I use a lot of different plug-ins. Everything worked except for Ozone4. On the first page of this thread there was a link for a workaround for iZotope plugins. But that link doesn't bring up any workaround. And they still say that their plug-ins will not work with El Capitan Does anybody know where that workaround is? Or if it works?
  7. This is what I got from Sound Radix: "32 Lives is fully compatible with OS X El Capitan, however, some older plug-ins may not be compatible with the system and therefore won't work with 32 Lives as well." This is what I got from PSPAudioWare when I asked about their plugins: "According to our testers they work without any problems."
  8. Eric - Thanks for keeping track of these driver / plug-in issues! Very helpful! I guess I'm going to wait to upgrade for a while yet.. I'm sure you've thought of this but wanted to ask: are you planning on updating the original post when each issue is fixed? Would be cool like at the end of a fixed issue you would say "FIXED ...." or something. I will then keep watching this list to know when it is safe for me to upgrade, once all my drivers / plug-ins are ready. Sorry for appearing to suggest you do even more work. I really appreciate all that you do and I cannot expect anything more.
  9. Thats encouraging. I haven't yet tried my Apollo twin duo. Unfortunately the on-board MBP audio is choking a bit on my system. I've got some pretty intensive midi projects though - I'm seeing the issue with midi synchronization. Do you use a lot of midi or mostly audio clips?
  10. I'm running a faster and newer MBP on the latest OS X but it seems the new release is taxing on my system too - even without Alchemy. My system choked to the point of getting the message: "Error while trying to synchronize Audio and MIDI". The worst was when I opened the MIDI editor on my drum track with lots of midi notes. Finally I had to bump up the I/O buffer from 32 to 512 - and set the Process Buffer Range to "Large". I still get some crackles but for the most part this has taken care of the problem. This is definitely an issue as the program is running inefficiently. Probably something simple like synchronizing the midi editor screen too often. I hope Apple fixes this soon.
  11. They fixed a small bug in Event List In Event List, if you wanted to change the channel numbers of all the events to be the same channel - you could shift+option drag up or down and all the selected events would change to a single channel number, and be changed to whatever channel number you were dragging to. The only thing was that for some reason you couldn't drag them down to channel 1 - it stopped at Channel 2.. No big deal, you let go of the Shift+Option and dragged down to 1. With the new release you don't have to let go of Shift+Option - it doesn't stop at 2 - it can go all the way to 1 This was really a minor bug, but I'm glad they are paying attention to some of these small things. This would probably only be important for guys like me who are transferring projects from another DAW to Logic and the midi channels need cleanup.
  12. Thanks David for your suggestions. When I selected "spread" from the "2 DirMix" dropdown, the curve appeared. What I didn't notice (and you can see it in my previous screenshot) is that "spread" is bolded. And I also noticed that each automation parameter is listed in the first dropdown menu at the bottom (you can see in my previous screenshot). It was right there all the time and I didn't notice! I guess I'm still getting used to some of the nuances of Logic. I usually don't have a bunch of automation on the same track. Thanks for your help. http://i687.photobucket.com/albums/vv239/guitartrek/Logic%20Automation5_zpshsliwecw.png
  13. Here is an updated screenshot. I'm only automating EQ - both low cut and high cut, and DirMix (spread). I'm starting with a monophonic sound cutting out the highs and lows (simulating low fidelity) and then transitioning to full frequency and stereo. You can see that the drop down doesn't even have the "spread" checked, even though it is being automated. I guess I could delete all automation and start over, but I like what I have and the timing of the curves were a bit of a pain to get perfect. So I'd rather keep what I have. You can see the curves in faint colored lines on the Output track, but none of the lanes show the automation. So I can't even copy them - there seems to be no way to isolate a curve and select it for copy. I tried automating other effects, and then deleted the effects, playing around with different sounds. So I probably had "orphaned automation". I tried "delete orphaned automation", but it didn't get rid of any of the lanes that don't show anything. http://i687.photobucket.com/albums/vv239/guitartrek/Logic%20Automation3_zps2hggunvt.png
  14. I've got some questions on Automation - I am automating two effects on the output track: DirMix and Channel EQ. You can see the curves on the Output track, but you can't see the curves on their Automation lanes. DirMix says Unused even though I am using it. Also, you can see other unused lanes, where I tried other effects but decided not to use them. 1) Why don't the curves show up on the individual automation lanes from DirMix and Channel EQ? 2) How do I delete the truly unused automation curves? 3) Why does the DirMix lane say Unused? Thanks for your help http://i687.photobucket.com/albums/vv239/guitartrek/Logic%20Automation%20Issue_zpszgawo1co.png
  15. I'm trying to fix up a clip with some Region Relative Volume automation. I'm trying to clean up some open guitar noise when there shouldn't be any sound. I am using relative volume so that I can later set the Track Volume for the best mix. But when I do this it affects the Global Track Volume. For example, my Track Absolute Volume is set to -12db. The Region Relative Volume starts out at 0db, and I've got a small section where I've dropped the relative volume down to -17db, and then back up to 0db. When I playback, the Track Absolute Volume starts out at -12db, but after the relative region volume drops and comes back up to 0db, the Absolute Track Volume goes to -6db. Am I doing something wrong or is this a bug? As I understand, any relative volume changes should not affect the Absolute track values?
×
×
  • Create New...