Jump to content

66ev

Member
  • Posts

    19
  • Joined

  • Last visited

66ev's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi David - yes it is - (or "Undo Copy and Drag" depending on which you have done - both cause the reload)
  2. have an issue where using Apple-Z (or file menu command) to undo the dragging of a region causes all the software instruments in the session to be re-loaded. it's possible that it only happens in large sessions or sessions that use surround. I've recently updated from 10.4 and it didn't happen there. Has anyone else come across this? Any fixes? Mac Pro Late 2013 2.7 GHz 12 Core, 128GB RAM. OS 11.6, Logic 10.7.0 Thanks
  3. For anyone else having this issue - I can confirm that Ploki's work-around appears to work. Change 'Input Device' to 'none' in Preferences > Devices before opening your project and the bus routings don't get messed up
  4. Hi.. wondering if any new info was available on this - I have the same problem / experience as Ploki: large 5.1 template with almost all busses used, recently switched to a new interface and bus assignments all messed up. I have also had it before when taking projects on my Mac to a studio with a different audio interface to me. Definitely seems to be a change of hardware that causes the assignments to change. Needless to say it's unworkable - would love to know if anyone has found any more info / solutions
  5. Here you go - would love to know if you find anything... EJ project 2 for LPH CLEAN.zip As soon as I delete those audio files, the midi export works again - weird.... Other things I thought could be affecting it, although I have no idea why they would... - Frame rate - Timecode start - Brexit Thanks again
  6. Hi volovicg Thanks so much for helping with this. Deleting the audio file did indeed work. However - I tried it on a different affected project that had no events before bar 1, and the same problem happened. However, when I deleted the audio from that project the midi export worked properly again.... I made another vid to show what I mean. I tried it with the audio time-locked and unlocked but that didn't make any difference I did try making a new project from scratch, and when the audio file is at b1 the midi export works as expected, and indeed when it's before bar 1 it does not. I wasn't able to recreate what happens in the latest video. Anyway, great that there's a workaround of deleting the audio, but it's got to be a bug right? I've been using this workflow for maybe 15 years and never had this problem before, and I know there have been events before bar 1 in some of those projects due to the way I work! once again, HUGELY grateful for your help. Would love to know if anyone else is having this issue
  7. Further update... I opened a couple of these projects on my MBP running Logic 10.3.1 and seems to work fine....
  8. And here's a clean logic project in which I have the problem (I have deleted all instruments and plugins to make it easier to open, but this doesn't have an effect on the problem)EJ Project CLN for LPH.zip
  9. Here's a video demonstrating the issue
  10. Hi David thanks fro your reply, yes, I'll do that today. There's clearly some issue because today I opened a project and midi export worked fine, I saved it and tried to export again and got the error.
  11. Hi Atlas Thanks for your reply, but no it's not any of the things you suggest, no looped or alias regions etc, and there's nothing in MIDI region parameters that would cause note events to be displayed over 10 measures early AFAIK! Also, as I mentioned it's strange that it is only affecting certain projects. It's almost as if they have become corrupted in some way and this is how it is manifesting itself...
  12. Hi all, really need some help! I've had two seemingly related problems today with exporting midi from a Logic project My process is the same as it has been forever: Select midi regions in Logic, export selection as midi file, import into Sibelius. Problem 1: Some midi files appear to export fine from Logic, but when importing it into Sibelius the note events have been moved earlier in time. The tempo / signature map comes in correctly. Problem 2: Some Logic Projects do not allow me to export midi at all; I just get the message 'no tracks or no events found!' - Starting from a blank Logic file seems to work fine, ie I can export midi correctly, and it comes into Sibelius correctly. - The issue doesn't appear to be with Sibelius as I have tried on two different versions and two different computers. - I tried rebuilding an affected project by importing tracks into a blank project, the problem remains; 'no tracks or no events found!'
  13. Thanks Eric... should I do anything to report this to Apple (other than fill in the feedback form, which I have done)
×
×
  • Create New...