Jump to content

Ted598

Member
  • Posts

    47
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Ted598's Achievements

  1. Was just about to create a sample couple of bars to grab a screenshot of, when I realized something I hadn't before. Indeed, when I hit record at bar 1, but only begin playing at bar 2, the red bar only begins scrolling at bar 2. However, once I've stopped recording, the region that I just created begins at bar 1. So all is as it should be. I could swear this wasn't happening with the region when I wrote my first post, but of course no jury would find me sane. 🙂 Sometimes Logic Pro Forum helps even when it has no advice to give. Thanks guys.
  2. Sorry, never mind about the post from an hour ago. I just realized the difference between Settings and Project Settings. @Atlas007, I don't think the issue is a synchronization one, because synch is set to Internal. @polanoid, I want to believe you that Logic has always been behaved this way, but I'm so sure it didn't. I continue to suspect Rewind. I will probably try uninstalling it. Will report if that made a difference.
  3. This is weird. I've now gone to my settings to make sure Enable Complete Features is checked, and it is. So Synchronization should appear as an area within Project Settings. But it doesn't. I'm attaching a screenshot of the top bar that I see when I open Settings. Some other areas are also different from what's shown in the article. I'm wondering if this has anything to do with the Rewind app that I downloaded from Monkey. I stupidly began using it at the same time as opening my first session with Logic 10.8, so I can't isolate the issue. (Side note, I'm finding Rewind doesn't do anything for me I couldn't do by other means, so thank goodness it was Black-Friday-cheap.)
  4. I'm using 10.8 for the first time today and am wondering whether this is a new feature, or if it's a bug. When I press R to start recording a software instrument, recording doesn't start (i.e., no red bar appears) until the first note is played. (Before, the red bar would start after the countoff whether I was playing a midi note or not.) It's a little disconcerting. I looked in settings to see if there was something I needed to change, but didn't find anything that seemed relevant.
  5. @des99, you're a genius. I went back to one of the malfunctioning projects. Saw that the meters weren't moving on the output 1&2 channel. (The one labeled Stereo Out.) Tried turning off the 5 plug-ins that were on that channel. VoilĂ ! Output happened. For those keeping score at home, the 5 plug-ins were: Ozone 10 Master Rebalance; Ozone 11 Dynamics; SSL Compressor; Izotope Tonal Balance; and Mastering the Mix Fuser. I turned all of them off, and as I say, I had output again. So then I tried turning them on one by one and seeing if I still had output. The answer was yes--except for Tonal Balance. Turning that one on made the output go away again. I was able to keep all the other 4 on at the same time with no problem; but add Tonal Balance, and the output went silent again. Thank you.
  6. Mac mini M2 Pro running Sonoma 14.1 and Logic 10.7.9. Interface is the Focusrite Clarett+2. All the track meters are moving in Logic Pro, but no sound is outputted. The Focusrite meters aren't moving. However, the problem can't be the interface, and it can't be the Mac's sound output setting, because I'm able to make everything work by opening a brand new session and then using the browser in the new Logic Pro window to import all the tracks from the old session. (This was the workaround suggested by @JakobP in a thread I started on October 7. At that time I thought the problem was limited to one session that was giving me trouble.) Rebuilding every old session into a new session is obviously not a tenable solution going forward! Any ideas on why this is happening and what I can do about it? It's making me crazy.
  7. OK, so further data has me thinking that the issue wasn't with Logic per se, but my Izotope plugins. Here's why. I was able to rebuild the session in a new project along the lines that Jakob laid out. When I did so, I got a dialog box from Izotope that I needed to reinstall their plug-ins onto my hard drive. I surmise this was because of Izotope being acquired by Native Instruments, but who knows. If I had received such a dialog box from Izotope when trying to make the original session play, that would have been helpful! But I didn't. So I had no way to know that was the problem. In any case, once I reinstalled and updated all my Izotope plug-ins, not only did the newly-rebuilt project play fine, so did the original session!
  8. I can do this, and will do it by tomorrow if possible. How do I go about sharing the project here? I'm sure the project is much too large to upload. Or do you just need a screenshot? Speaking of plug-ins (as @polanoid just was), it so happens that yesterday I began to suspect that one or more Izotope plug-ins may have been the culprit in the original session file getting corrupted. (But not a pitch correction plug-in.)
  9. @JakobP, that seems to be working. It didn't, at first, when I tried to import all the tracks/regions for all the instruments at once. And it also didn't work when I tried to import just small groupings of 3 or 4 instruments. However--if I just add one track and its regions at a time, the resulting tracks do play in the new session. Thank you! And, phew! @rAC, thanks also for the monitor vs. internal speaker suggestion, but I'm very sure the problem wasn't the monitors. Thank goodness for this board!
  10. It's just this one session, far as I can tell so far. The track meters in Logic all move, but after about 1-2 seconds, Logic stops sending output to my DAW interface. (Focusrite Clarett+ 2 Pre, although the same problem happens with this session with my Apogee Duet.) The fact that the output plays for those 1-2 seconds before going silent would suggest that there's no problem in any of the connections or routing. I've tried copying the session to a different file, but the new file (same title, with the word "copy" at the end of it) has the identical problem. I've tried increasing the i/o buffer size to 1024. I've tried reducing the size of the session file by deleting some of the Project Alternatives. I've tried quitting and relaunching Logic. I've tried restarting the Mac mini pro 2. None of it solves the problem. What should I try next?
  11. Fantastic news! The piano-roll workaround I discovered and posted about on Thursday turned out either to work by random chance or an accident, because over the weekend I wasn't able to replicate the success. I hope to God 10.7.9 is the answer.
  12. Yes, the issue is that moving the tracks in the main tracks area so that they are optimal does not result in their appearing in the mix window in that order.
  13. None of the tips have worked for me with 10.7.8. Especially frustrating because I want to group some string tracks in the mixer and Logic put my drummer track right in the middle of them. (So I can't group the strings without including the drummer.) Suffice it to say this is not how they are grouped in the main window. In the mixer, when I control click the drummer track (or any track), it doesn't allow me to move it but instead gives me a menu of options (starting with Create New VCA).
  14. I've discovered what (so far) seems to be a reliable and less cumbersome fix of the piano roll problem I've reported. (Problem: Region disappears when trying to edit it in piano roll. Somewhat cumbersome solution: After making sure piano roll is linked to the region, unlink it before editing.) The new way of solving the problem is to open the piano roll in its own window (command 4) rather than at the bottom of the main window. So far, when the piano roll is in its own window, I can edit it without first unlinking it from the region.
  15. This thread has helped me in one regard, which is that I have learned to relax about the bugs I am experiencing. Basically it's good to know that there is no fix, only "workarounds," because this knowledge stops me from trying to figure out what I'm doing wrong or why 10.7.8 on my new Mac mini is uniquely bad. Thanks to this thread I can realize that A., I'm not doing anything wrong, and B., my 10.7.8 is not uniquely bad. This has turned the bugs into annoyances rather than crises. There is peace in powerlessness! FWIW (if anybody's making a list), my two persistent bugs both have to do with regions disappearing when they oughtn't. ~A midi region will sometimes (unpredictably) disappear when I am trying to split that region at the playhead by hitting command-T. The workaround is to hit command-Z which brings the region back, upon which command-T works as it should on the second try. ~A midi region will sometimes (unpredictably) disappear when I am trying to edit its notes in the piano roll. The workaround is to unlink the piano roll from the region. The notes in that region remain in the piano roll and I can edit them.
×
×
  • Create New...