GeeMan Posted March 3 Share Posted March 3 For some reason, my hihats are getting values of 10, 20 and 30 when generated by Drummer, then converted to Midi files for manual editing. I seem to remember them being generally about 1-7 in value before. When I share the track with people with earlier Logic the hats are SILENT in many cases. The hats have to be manually edited (select equal in Events) to get back into the correct articulation values and to even play. Which for some people is a nightmare. Anyone know anything about this - or work arounds?? Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted March 3 Share Posted March 3 Hi @GeeMan, There was a change in Logic 10.7.5: Quote Resolves an issue where Drummer regions converted to MIDI regions could play back unexpected kit pieces or articulations. It's looks like due to that change, the hi-hats in a MIDI region that was converted from a Drummer region in Logic 10.7.5+ will get articulation IDs that produce no sound (at least with DKD) if the project is opened in Logic Pro 10.7.4 or below. So that would be a breaking change. 1 hour ago, GeeMan said: The hats have to be manually edited (select equal in Events) to get back into the correct articulation values and to even play. Which for some people is a nightmare. To get the hi-hats to "even play" is easy, to get them to play with the same nuances as the original Drummer "performance" is a different story because like you say, in 10.7.5+ there can be three or (maybe) more articulations IDs at play so not too cool of a task in the context of collaborating with others not running the same version of Logic as you. The obvious workaround is for you and your people to work with the same version on Logic when you intend to collaborate. J. 1 Quote Link to comment Share on other sites More sharing options...
GeeMan Posted March 3 Author Share Posted March 3 (edited) 13 minutes ago, Jordi Torres said: The obvious workaround is for you and your people to work with the same version on Logic when you intend to collaborate. J. Hi. Right thanks for the info. No chance of them upgrading until it's part of their overall strategy. And I agree totally with them. All upgrades seem to do is introduce new problems, after watching this process for over 20 years. I normally wait until really stable versions / combinations of the machines and software, but my old machine went down and I took an impulsive leap. And I get other problems too. (I've never seen logic delete of the last few seconds of a recorded part before now, for instance). My bad. Edited March 3 by GeeMan 1 Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted March 3 Share Posted March 3 @GeeMan, 7 minutes ago, GeeMan said: Hi. Right thanks for the info. No problem. 8 minutes ago, GeeMan said: No chance of them upgrading until it's part of their overall strategy. And I agree totally with them. By working on the same version I wasn't necessarily implying they should upgrade, If you still have backups of earlier versions (which we all should have just in case) you could simply work on a version matching theirs when you want to collaborate. Of course if you don't have any backups of previos versions then you'll have to rely on others workarounds I'm afraid. 9 minutes ago, GeeMan said: All upgrades seem to do is introduce new problems, after watching this process for over 20 years. Yes. And fix old ones too. But that's not just with Logic. That's just the norm in the software world, especially with large codebases. I've seen this firsthand having worked in or close to R&D teams at companies where software is developed. J. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.