Jump to content

whinecellarstudio

Member
  • Posts

    33
  • Joined

  • Last visited

whinecellarstudio's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Been happening to me too on Mojave 10.14.6 & Logic 10.5.0. Gets old fast...
  2. Agreed. I tried changing my whole scoring template over to track stacks, but it ended up being a LOT more clicking around to navigate. My template is over 700 tracks, but with the old-style folders I have a screen set for each one so getting around is really fast. There's a crucial key command needed for track stacks: "close containing track stack" for any track selected. As it is now, you first have to select the track stack header to close a track stack. Kinda blows the whole thing without that, IMO. Anyway, they are indeed looking into these issues, presumably because a lot of people still use folders. There are some MAJOR bugs involving folders. so hopefully they get squashed quickly.
  3. Yep, that works, but it's a step backward and a real pain that adds up over a long day of editing, especially when you're used to working really fast with key commands Appreciate you looking into it - thank you! This is one the dev team asked about, so I know it's on their radar...
  4. Nope, just what I typed: the behavior I described is when opening a separate piano roll window - not editor. And again, the issue doesn't occur on the top level of the arrange window - this is only for regions inside older-style folders - not track stacks. There are a lot of bugs when using folders, and thankfully Apple is aware of them and interested in fixing them - they've asked for sample sessions, etc. Hoping for a fix in the next sub- release
  5. Wondering if anyone else is seeing this: Occasionally whatever you choose as the Command/right click tool in a piano roll window will persist as the main tool when you switch to an arrange window. For example, my Command tool in a piano roll window is the pencil. When I close the piano roll, the pencil is now the main tool in the arrange window, and when you’re working fast, you end up accidentally creating regions. Bizarre! New install of 10.2.1, fresh prefs...
  6. For tracks inside folders (not track stacks - actual folders): when you select a region, opening a piano roll window shows the folder level and “no regions selected” in the inspector, as opposed to the selected region content as it should. You then have to open a *second* piano roll to show the selected region’s content. Selecting a region and opening an editor should ALWAYS show that region’s contents...
  7. I'm getting this issue too, consistently. Thought maybe it was a corrupt template, so I opened a fresh empty song. Created a few random markers. Renaming right after creating works, but then after jumping around a little, it won't work anymore. Tried deleting & re-assigning the "rename marker" key command - no go. Definitely a glitch. Also can't rename markers in the marker list by double-clicking on them!
  8. Hey Jim, My scoring template is pretty large and I was really interested in VE Pro for obvious reasons. It's a great product in a lot of ways, but I ended up going a different route that works well for me. I did a thorough review of my experience here: http://www.gearslutz.com/board/music-computers/458444-maximizing-your-mac-s-logic-ve-pro-vs.html Hope it helps! Jim
  9. Hello, Looking for a bit of "power user" feedback specific to running Kontakt (3.5 or later) as a plugin within Logic 9. I've been using Kontakt standalone on my host & slave computers for a few years now as it's always been problematic in plugin mode - but most of those issues have been sorted out as of 3.5. The one biggie that still concerns me is the random sample reloading bug in Logic. Nobody (that I know of) has been able to figure out what causes it, and I'd like to know if it still rears its ugly head before I spend another week of my life rebuilding my working template to incorporate Kontakt as a plugin (I'm also about to make the leap to 10.6 and Logic 9). Anybody care to share your experience? As a point of reference, my current setup has Logic triggering 64 channels of Kontakt running standalone (on the same machine) via IAC MIDI, as well as several slave machines also running Kontakt standalone. I'd love to consolidate all of these Kontakt instances into my Logic template (using KMS of course). However, if this random reloading bug is still there, it would be a nightmare! Thanks in advance, Jim
  10. Happy to do it. I might as well make myself useful if I've got the ear of a few good people at the mother ship Yep, Vienna had nothing to do with it. My contact fully admitted that it got screwed up on their end somehow. It was simply a setting recall issue that somebody must have missed. They did have to work on the EXS architecture a little to implement the new "create sampler instrument" function, so that's probably where it happened... Anyway, good to have a happy ending - now I can finally join the Logic 9 party Take care, Jim
  11. Awesome - that's good news. Ironically, I had just gotten an email from one of my high-up Apple contacts two days ago telling me it was being worked on - then 9.0.1 dropped yesterday. It's encouraging to know they're listening - and responding!
  12. Can you give any specifics? It's definitely fixed here - everything works perfectly now. One thought - did you start with fresh copies of your Vienna EXS instruments after updating to Logic 9.0.1 (copies that haven't been touched by the Logic 9.0 bug)? The first thing I did after updating to 9.0.1 is to pull in some fresh backups of all my Vienna EXS instruments - I figured I'd start from scratch, and it worked for me...
  13. You're welcome Seriously, you ought to copy & paste that at the Logic Feedback page - they need to know that this is serious! http://www.apple.com/feedback/logicpro.html
  14. Wow - that couldn't be more wrong, and I sure hope they don't consider that a viable solution... How do they think we found this bug if it were simply a GUI issue?!? As soon as I started loading many of my go-to insts. in Logic 9, I was freaked out by the obvious corruption. Many of my custom patches were missing their loop points, LFO settings, Vienna Performance Tool status, mod routings, etc. - all of which were immediately noticeable and of course AUDIBLE. I can't use Logic 9 because of this, and I know I'm not alone. If you're in the same boat, please post your details to http://www.apple.com/feedback/logicpro.html Thanks...
  15. Hey Folks, Just a friendly reminder to keep posting feedback to Apple about this issue; may of us are unable to use Logic 9 until this gets resolved. Thanks so much, Jim Daneker
×
×
  • Create New...