Jump to content

woods101

Member
  • Posts

    27
  • Joined

  • Last visited

woods101's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later Rare

Recent Badges

2

Reputation

  1. Hi, Late to the party, but @Dewdman42, I had the same issues and then realised plugin was calibrated to a different sample rate. Check that the sample rate in the drop down menu on the plugin matches the project sample rate. Should be fine then.
  2. @des99 Thanks Des, yes got ya with the plugin slots etc., I'm down with that but I'm pretty sure I've created custom instrument folders that then appear in the instrument drop down menu in past versions. Do you just do this in the 'general' Plugin manager window? I thought the plugin manager used to be split into two sections - FX and instruments but it seems it's just one generic one now, though my memory is hazy. @David Nahmani Thanks David, yes I guess this is a weird Logic glitch right? Tbh there's a lot less bugs these days, it almost feels nostalgic!
  3. Greetings people, I always find myself here when it's just been slightly too long for me to remember how to do something I used to know how to do and this is one of them. I know how to make custom effects plugin folders in Logic. I'm trying to make custom instrument folders so I can group the Logic stock instruments and also add some 3rd party synths, samplers etc to those same folders so all my preferred instruments are available from one dropdown. At the moment, the only custom instrument folders seem to be some of the effect plugins that I've just added (see photo), which is pretty weird - I can drop an effect into an instrument slot it seems. Is this an obscure logic glitch? Anyways, can anyone advise? Thanks, Woods.
  4. Another bug. No workaround I can offer at the mo. Changing quantization settings in the track parameters means not being able to undo back to previous settings, even when applying permanent quantization to a midi region and then processing, and then stepping back. Midi region will have notes placed in different positions. Quantization overall seems clunky and unusable. Can't seem to find easy groove settings when playing around with parameters like I usually do. Have been using since Logic 6 so don't feel this is user error.
  5. Another bug in the latest version of Logic (possibly the buggiest version there's ever been!) - the arpeggiator is not working all the time. It will work when playing notes via midi input but won't always activate via recorded midi sequence. It will play the first few notes then silence.
  6. Hi David, can you advise me where online I go to give user feedback to Apple? I'm finding this version to be the buggiest ever. I understand ranting here is not the right place.
  7. Am suffering quite a few other bugs also - EQ thumbnail image on tracks not updating, arpeggiator stalling, notes not playing. Hopefully another update is coming soon.
  8. Not a deal breaker for me but have repeatedly tried to implement dolby atmos in a project (old or new) only to have Logic crash. On reopening Logic, Terminal is then triggered open randomly. I can open the demo spatial audio projects no problem but can't instigate Atmos it in a project of my own from the 'mix' tab at the top of the screen. Anyone else having this problem?
  9. Hi Atlas, Thanks for getting back to me. I think I've solved it. I removed the 'Steinway Piano 2.exs' file from it's original file then put it back in and it seems to have solved it!? Weird but it seems to have worked. Thanks again.
  10. Hi, For no apparent reason, the EXS24 keeps freezing/ crashing every time I use the Steinway Piano patch which I was using absolutely fine seconds before. I simply closed one project, went to open another and it failed to load, stalling on the Steinway piano instrument. Now this is the case in every other project that uses that instrument. All other EXS24 and logic instruments appear to be working fine. I have my EXS24 samples stored on an external HD. The Steinway Piano sample(s) is a consolidated .caf file which is unusual as the Yamaha ones aren't, though there are plenty of other .caf files for other EXS24 instruments so I guess this is fine. I don't think the samples are corrupted or the location is an issue as I always save EXS24 instruments samples with each project, hence there is a .caf file for this instrument in each project it's used in, it's more that it appears that the actual EXS 'instrument' itself is corrupted. I have deleted logic preferences and this hasn't solved the problem so have replaced them back. I'm wondering if there is anywhere on line I can find the 'Steinway Piano 2.exs' file online to replace mine and see if that solves it? Or...can I just delete that EXS instrument file and logic will auto download it again? Or... could someone send me their copy of 'Steinway Piano 2.exs' so I could try? I'm running 10.4.1 and I know there have been changes made to file location options since this version which could cause probs if I have to d/l factory content again. 2 commercial tracks hanging on this so reluctant to try anything fundamental such as an upgrade to resolve the issue at this point. Any ideas/ help greatly appreciated.
  11. Oh Wow. Thanks. does that mean that if/when I update to a relocation featured Logic version I have to actually reinstall everything from Apple or can I just relocate with the updated version by 'showing' it where everything always has been?
  12. Hi, I have all Logic content on an external HD including all Apple loops. My user created Apple loops are stored on my laptop at user/library/audio/apple loops/ user loops/ singlefiles. How can I change the default location that my user loops are stored to also be the external HD as they are taking up space on my main HD? It's a while since I set this up but I think I used symlinks initially. Do I just need to set up a symlink for that folder? At present I'm running 10.4.1 on Sierra if that has some bearing on things as I know file location was addressed with recent updates. Thanks Woods
  13. Hi guys, Got an annoying bug regarding audio and midi 'off-cuts'. I can have a region that is an exact bar length (see vid below), region settings are 'no -overlaps' so there should be no parts of regions underneath other regions, but sometimes when I cut or move a region these little slices appear. As I work through a project more and more are generated and they sit under regions and cause problems when copying or moving stuff around meaning certain regions shrink (to become the same small slices) or just disappear. Anyone else suffering this or have a solution at all? Wasn't sure how to post a vid here so here's a dropbox link: https://www.dropbox.com/s/jr44nd0bdqx4cd3/Glitch%20Bits.mov?dl=0
×
×
  • Create New...