Jump to content

jnchristp

Member
  • Posts

    145
  • Joined

  • Last visited

Recent Profile Visitors

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

jnchristp's Achievements

  1. You are correct. I opened an older project that was made a few years back and with that project everything is fine. Using a new empty project it's messed up.
  2. It's a bug that's there for some time. And it's the same with surround-formats. When you change the output to Surround angle is at -2.
  3. jnchristp

    Soundflow

    Hej, is anyone here using Soundflow with the newly added Logic Pro Package? I'm checking that out myself at the moment. I like the idea of automating some tasks in Logic. Like: I would love to have a script that automatically uses "Remove Silence" on selected tracks, one after the other. I'm not into programming macros myself, but I hope that this kind of macros will be added in the future. Also, stem processing. Etc. Most of the commands that are inside of SoundFlow are already there in Logic and can be used with Logic Remote. So it is clearly in it's infancy. Integration of Soundflow and Pro Tools is on another level. My thoughts at the moment: I know my shortcuts quite well so I'm fast with Logic. But I'm very dependent on PlugSearch for inserting plugins etc. That's a real timesaver. And it works great. Cheers Jan
  4. I still feel that Flextime is really sensible. And it only seems to work for takes that are nearly there. Nothing crazy. No big changes. I did some experiments last week to find a way to get better results. My observations: I add or distract flextime-markers BEFORE I turn on flextime. I open the kick drum, let Logic detect transients and try to make everything perfect there, deleting everything that's not needed. Then I do the same for the snare (and maybe for the toms). When I have done that I turn on flextime with phase-lock and chose Kick and Snare (and Toms, maybe) as the Q for Flextime. This way Logic uses just the flexmarkers that I created. Then I quantize the drums to whatever value. And hope for the best. And I have to check everything of course. Delete some changes. It's far from "automatic", as far as I can see. Its tricky. But that's the thing: Quantizing audio is tricky. It always is. Hope that helps? Cheers Jan
  5. No, I didn't. I started fresh and recognised the change later. I had to change the shortcuts back to the way I was used to. Not a big deal, but strange. Why change the default keystrokes?
  6. Hej, I just had to reinstall my MacBook and installed the last Logic version on it. Afterwards I recognised that some solo-shortcuts were suddenly different. Before updating I had the "old" shortcuts: contrl-s to solo a region, contrl-option-command-s to unsolo. Now it's a different thing: contrl-s is soloing the track and the region. option-s is unsolo. Didn't anyone notice this change? Did hey change this with 10.8? Why? Cheers Jan
  7. You are correct. When I open an older project in Logic 10.7.9 and turn off MIDI-clock ALL in the sync settings (a default in my template), I can open that project in 10.8 without any hiccups. With sync on it takes forever. Great find! And well worth sending to the Logic team.
  8. Right. Didn't recognise it before, but I will report it to Apple.
  9. Hej, just recognised that everytime I create a track that is routed to surround or i change a track to surround, the resulting panner-angle is of by -2. And resetting that value doesn't help. When I open that panner-window again, angle is again of by -2. Does anyone else have that behaviour? This happens in Logic 10.7.9 and 10.8 for me. Cheers Jan
  10. Think, I found a solution for my MIDI-timeout problem: When I open Logic 10.8 without any projects and open a project from within the app via menu, everything seems to work. That's strange. When I launch Logic by clicking on an existing project or launch via dock and recent projects, it doesn't work. That's kind of strange.
  11. Right, very strange. Everything works with 10.7.9. Also, when I try do deactivate a MIDI-devoice in 10.8 I get a duplicate of that device. Somethings not working right. Will report it to Apple.
  12. Seems to me that this is somehow connected to my UAD Apollos. When I have it turned off so Logic uses another audio-interface like the internal speakers, everything seems to work just fine. Still, it's a new thing with 10.8, as with older Logic versions there isn't this failure. Does anybody have the same behaviour with UAD Apollos and MIDI timeout messages?
  13. Just downloaded 10.8 and tried to open some of my older projects. Strangely enough I get the dreaded beach-ball and then the news that there was a midi-timeout problem. Even when there's only audio in the project. First observation: Opening that same project with 10.7.9 works without any flaws. When I open Logic 10.8 with a completely new project there is no MIDI-timeout message. Does anybody encounter that same problem? What to do about it? My MacBook is on Sonoma. Cheers Jan
  14. If I'm not wrong, it's the swing parameter that has changed...
  15. I think the same: IO-Labels should be session-based. Or at least one should have the option to use the receiving AUX-names instead of the numbered busses. So you don't see "Bus 1" but "Cathedral Hall" or whatever, because the Aux is named that way. If you don't like that, turn it off. Back to "Bus 1", "Bus 10" etc. But I'm using the great PlugSearch-software and don't care that much for the numbers anymore. When I want to insert a send to some place I use Plugsearch and type in the name auf the AUX. Done. I don't have to remember the Bus-number anymore. But I like to keep sessions consistent. I like Pro Tools for this. Naming sends. Logic should do the same. Cheers Jan
×
×
  • Create New...