Jump to content

question

Member
  • Posts

    185
  • Joined

  • Last visited

Personal Information

question'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. Thanks for the tips. Polanoid, yes I looked at the Clicks & Ports Layer in the MIDI Environment window and saw that unintended MIDI data was in fact being received. Normally all controller info from my Keyboard is turned off since I use an external unit, but somehow they got switched back on. I did not see the Pitch bend data because I did not realise that I had the "pitch bend" view option turned off in the Event list! Anyway, thanks!
  2. Hi Fuzzfilth, yes of course I checked the sample rate, which is correct in Logic and on my interfaces. I suspect a corruption since the (same) instrument will sometimes work correctly then suddenly transpose. We are talking about one instrument from several transposing , the rest are working correctly. As I wrote; it happens with both Logic and third party instruments. Thanks for the help.
  3. I am having an issue where software instruments, Logic's as well as third party instruments, are intermittently transposing up exactly a half step. This happens on all projects and with my own templates as well as the Logic factory templates. I suspect it is a corrupted plist, but thought I would post and see if anyone else has seen this issue. I choose a software instrument track (or create one) open an instrument and when playing a note it sounds exactly one half step higher. (sometimes) Somtimes previously recorded software instruments will suddenly start playing a half step up. This happens when using my MIDI keyboard as well as, for example, Kontakt's virtual keyboard. I can see in the MIDI monitor that Logic is receiving the correct MIDI note. I have been using Logic for twenty-something years so I have checked all of the potential suspects that I could think of such as: -Checking if the transpose is set to zero in the MIDI object parameters -disconnecting my MIDI keyboard -Checking the Event list -Starting with a blank Logic template -checking Logic's Environment Any ideas? Since the problem is intermittent, even on the same channels and instruments, I suspect some sort of plist corruption. I know how to back-up and re-install my Key commands, but wanted to know if there is a way to save all other preferences without having to reset them all after erasing the plist. Thanks in advance!
  4. Does anyone know if the issue with the chaotic reassignment of busses, tracks and software instrument assignments discussed in another thread was fixed? Also the (seemingly related) issue of the metronome dropping out? Would Apple normally state that these issues were addressed or just quietly fix them without any mention in the update list?
  5. Does anyone know if the issues discussed in this thread, as well as the disappearing metronome issue, have been fixed in the latest Logic Update? I read David's list of update changes, but I thought it might be possible that Apple would simply quietly fix the issue without first acknowedging its existence.
  6. JakobP, yes that is the point; it seems to be this dynamic changing of the Click and preview channels that is possibly creating the track chaos problem as well as the disappearing metronome issue. I was unaware that Logic increased the potential track amount.
  7. JakobP, yes my mistake! Software tracks not audio tracks. I will see if I can find David's explanation of the change in the click implementation. And yes, for me as well the undo of the tracks seems to be the action that triggers the chaos.
  8. Ben and others, somewhere in this thread David explained that Logic changed the implementation of the click "Klopfgeist", then reverted to how it was previously. The click used to be assigned to track 264 (I believe) then it was changed to be one track above the last audio track in your session. So if you had 3 audio tracks, the click was track 4; if you created a new track the click would then shift to track 5 etc.. This problem with the track/Bus shuffling seems to be related to the "metronome disappearing" issue. (in another thread) David's tip was to use a fresh template from the latest Logic version. My test is not scientific; but I am working on two films each of which has about 50 Logic projects. One film was started from a template created in an older Logic version, and the other from a freshly created template from the (almost) newest Logic version. In the first film the metronome often drops out and the track shuffling has happened about 8 times. In the projects created from the newer template it has not happened once. As others have observed it mostly occurs when performing some sort of Track process (creating, deleting, bouncing etc.) I don't know if this issue has been fixed, but in my case making a fresh template so far has stopped it from occurring. David, please correct me if I have explained the click implementation incorrectly. If Apple responds with an explanation, please post it here as this problem is terrifying!
  9. In any case with undo; with delete I am not sure. Do you see any pattern?
  10. David, as you stated; "never open 2 project files simultaneously" as this creates all sorts of crazy problems. I also never open two project together, but I still sometimes have this track chaos issue when importing data using "File-Import-Logic Projects". If I import, for example, instruments and content then erase what I have imported, this often triggers the chaos. I work primarily with film and noticed that a few other users who are working with film also have this issue, I don't know if this is a factor. In any case, your advice to build and use a new tempate from the latest Logic version seems to have solved the problem; but when opening projects based on my previous tempate the issue still remains.
  11. rmrm, yes, this is my workaround. As soon as the issue occurs, quit Logic and re-open the project without saving. Auto save must be off! As I wrote earlier in this thread, I took David's advice and built a new template from the most current Logic version, which seems to have solved the problem. When I re-open a project built on my previous template the problem occurs. When I say "template" I don't think it matters that I used my actual previous template, just that the project was created in an earlier Logic version. As everyone seems to confirm; the problem is somehow related to track management, which is also related the metronome disappearing problem as well.
  12. danielsonabend, there two other threads where we are discussing this metronome issue as well as the "track chaos" issue. David's tip was to not use a Logic Template from an earlier Logic version. I updated my template and the metronome issue seems to be fixed. Try using a fresh template using the newest Logic version and let us know whether that solves the issue.
  13. Twistiejoe, I am not a programmer so I don't understand the conflict of why you can't lock tempo events to SMPTE. This was an explanation by "Ski" I believe. One more thing; when I work I always lock all audio and MIDI objects to SMPTE, but when I change a tempo event I always unlock the objects which follow this tempo event. If you don't do this, the MIDI can get messed up as it is locked to a SMPTE position that now (temporarily) has another tempo. If that makes sense. If you convince Apple to find a solution I and many others who work with film would be very gratefull!
  14. Twistiejoe, I feel your pain. I also work almost exclusively with film and have agonized over this issue as well. There is a long thread from several years ago where forum member "Ski" and I discussed this issue at length. Have a look as there were several interesting ideas. I have done several 90 minute film projects in one Logic song, but it is extemely complex, especially if you are doing tempo changes within a scene. You can use markers or add a tempo change and re-orient the following cues to the new smpte position. "Ski" explained that Logic works mainly in bars and beats, so adding this lock tempo events to SMPTE would mean re-coding the entire program. There is a function in Digital Performer called "Chunks" which allows you to isolate each cue with its own tempo info etc.. I don't know how DP solved this issue. After working more than 20 years with Logic I dread the idea of relearning another DAW to the level at which I now am. One small tip: I use sort of "buffer" tempo events (two nodes) before a tempo change so that I can fiddle with the tempo change position in order to get the next cue onto the time grid if needed. Another work-around is to do the whole film in one Logic project (which has many pros and cons as was already noted) except for the cues where there are complex tempo events within a scene such as in an action cue. Hope that helps!
  15. H Hoges1, yes the problem that I have is similar. I took David's advice and made a clean new template using the latest Logic version and that seemed to help. It has something to do with track management, and with me always happens after a track action; (creating, deleting, copying, importing channel strips, and particularly when importing then erasing a channel strip) Read David's explanation of the current implementation of the metronome track as this seems to be related to the issue that you are decribing. Today I recorded an audio track, which accidentally got repeated by the locater before I got to the end of the recording. Upon erasing the originally recorded audio and the automatically created new track (due to the locater being on) the tracks got shuffled. My work-around is to constantly save as I work; if the track issue occurs, I simply quit Logic without saving and reopen the project. See if you can reproduce the issue by using the locater then erasing the automatically created track as well as the recorded audio.
×
×
  • Create New...