Jump to content

redlester

Member
  • Posts

    15
  • Joined

  • Last visited

redlester's Achievements

  1. Just as an addendum to this thread, every time I close then re-open Logic I have to toggle Enable Performance Recording on and back off in order to enable automatic input monitoring. Very frustrating. Is this a bug, or is it just me? Addendum to the addendum: Solved this by enabling automatic input monitoring then re-saving as Default.logicx file under Audio Music Apps/Project Templates
  2. Just to close this one: I've now checked and I DID NOT have "Enable Performance Recording" turned on. My heart sank, as the problem was still there. However, when I toggled Enable Performance Recording on then off again - hey presto, the problem is fixed. I now have input monitoring turned on automatically when I select a track. Phew!!
  3. Am not at my computer right now but think I’ve found the answer in another thread here: The last time I used Logic I was messing around with the step sequencer and Live Loops so I expect I’ve enabled the setting mentioned in the above post by mistake. Hopefully this will sort it but I won’t find out until I get home Monday evening!
  4. Ok. I haven’t used Logic for a while, but that’s not how I remember it. So I create a new software instrument track, and assign a plugin to it. By default I can’t hear anything when I play my keyboard. I have to then manually turn on the record enable button for the track, then I can hear it. Surely that’s not normal? If I have several software instruments loaded I thought I could switch between them and audition them without having to also click record enable each time? Should the focussed track not become automatically enabled?
  5. As described in the title. I can only hear software instruments when I set the track they are on to record enable. If I turn off the red 'R' button, how do I hear the plugin? Software Monitoring is turned on.
  6. Am sure the alias method is fine, but the way I deal with this is, when initially setting up after a new install of the OS or Logic, to simply add the folder I use for my projects to the sidebar in Finder. Then, in Logic, when I click Save As.. as long as I have the Sidebar shown in the Save dialog it only takes one click to go straight to my default drive/folders for my Projects.
  7. OK, first of all thank you David for sending me that little file. Needless to say it worked as expected, with the step sequencer behaving as it normally should. So I knew from that it was something I'd done in my default template that was causing the issue. Turns out it was simply down to the fact that I had my default Project Start marker set at -5 bars. I cannot remember why but when I worked on something a long time ago I needed some pre-roll for some reason and had changed it by just dragging the start marker. Everything has worked as normal in this scenario, until I realised this issue with the step sequencer. For anyone reading in future, I was still getting the problem even though my first region in the project was commencing at 1 1 1 1, but turns out because there were bars in negative numbers before that, Logic clearly doesn't like that. Have now put my default template back to project start at 1 1 1 1 and all is working fine. Lesson learned!
  8. That’s very helpful, thanks. Am at work right now will let you know later when I get to my computer.
  9. Interesting, thanks. Will take a look into that later. Although am pretty sure if happens on all sequences whether looped or not.
  10. Ok. Does that occur even in a new empty project where you create a new pattern region? Yes, happens on all whether I create a new region in a new blank project or whether I use one of the predefined loops.
  11. That's precisely the point - I don't see the white frame. There is nothing to indicate moving from one step to the next.
  12. Very strange problem with the Step Sequencer in Logic 10.6.3. If I create a new sequence or load a pre-defined sequence in to the Step Sequencer, looking at the Step Sequencer editor in the lower half of the screen when I start the transport running am sure in the past it used to highlight each step, moving horizontally along the steps as the sequence plays. This no longer happens on my copy. The sequence plays as normal, however the steps do not 'light up' as the playhead moves along the time line. If I stop the transport and use the Preview Sequence button in the editor, the steps light up as normal. But when I actually run the transport, the steps are not visually highlighted as they play. Is this a bug in the latest Logic update or have I switched something off somewhere? I've been searching for ages and cannot find anything which relates.
  13. I had this just today, I am working on a movie project and instead of clicking the red dot to close the movie window (which places it into a tiny window top right in the Inspector) I accidentally clicked the red dot on Logic itself, which immediately closed everything except for the movie window. Can confirm Open Main Window is still the command to sort it out, on Logic 10.6.1.
  14. Yes, I agree it must be something within the app. My Default template is stored along with all my other templates and is set to 48k. I do always try to open that, but sometimes I forget and accidentally go File>New. It's not a major issue so hopefully when I eventually update my computer and re-install from scratch it should go away!
  15. Using Logic 10.5.1, I have all my templates set up to work at 48k, including my Default template. When I initially start up Logic, it opens the Default project, at 48k, as expected. With Logic open, if I Create New From Template, using any of my templates, it opens it at 48k as expected. However, with Logic already open, if I select File>New and create a new project without using a template, while opening the new project it switches my interface over to 44.1k for a few seconds, then switches back to 48k when the Default project completes opening. This is annoying as I use a UA Apollo interface which makes a loud click when switching sample rates. What is going on here, how can I stop it from temporarily switching sample rate during a File>New command? As stated above, this only happens with File>New, not when opening a new instance of Logic itself.
×
×
  • Create New...