Jump to content

ralphonz

Member
  • Posts

    190
  • Joined

  • Last visited

Recent Profile Visitors

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

ralphonz's Achievements

Explorer

Explorer (4/14)

  • Dedicated Rare
  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare

Recent Badges

9

Reputation

  1. If this happens I'll almost exclusively use Pro Tools I think. I probably won't pay another subscription. For a Mixing workflow one of Logics strongest points over Pro Tools is its price point and it's control surface support. Otherwise, it's missing a few really great features that pro tools has.
  2. Yeah, I can confirm the "+" no longer works 🥲
  3. Ah, when the lines between bugs and forgotten features become blurred! I think only the developers could give us an answer! Either way, you should be able to I think. Worth dropping them a request I suppose.
  4. For example, if I increment that last "position" number by one, thats equal to 13 samples. I can see this my looking at the main time display. It shows Hours : Minutes : Seconds . Samples and under it shows bars beats etc... That last position number seems to represent a beat sub-division not actual samples.
  5. Yeah I got that, it's definitely moving it by more than samples though... That last number definitely doesn't represent samples. At least not in my projects.
  6. Actually, this doesn't seem to be moving it by samples... It moves too far.
  7. Even better, thanks! Saves me having to use spotlight as a calculator 🤣
  8. I'm just going to revive this thread and update it for anyone else looking for a quicker solution. In Preferences -> Display set your main time display to Hours : Minutes : Seconds . Samples Workout where you want your region to be in the timeline. Take your playhead reference position (for many this may be 01:00:00.00000) and add or subtract the number of samples you want to move. Put your playhead there by dragging the samples portion of the main time display. So if I wanted move the region by 87 samples, I'd hover over the samples section of the display and drag up to 87. Select the region and use ";" to move it to the playhead position.
  9. Absolutely! They did at least sort out the latency with busses/aux channels a few updates ago but I can't help but fell the whole PDC concept needs reworking in Logic.
  10. I don't know, I've never tried to mix a big session in anything other than Logic or Pro Tools before - But even discounting plugin GUI's, you at least expect the mixer meters to be in time with the audio, and the automation lines which currently they are not in Logic. Again, all works as you would expect in PT, no matter how many latency-inducing plugins you have in the session.
  11. I disagree with this statement: You're treating this as a bug, but it isn't really, it's the nature of how the process works, and really is imo the *correct* behaviour (once you understand what's going on). It doesn't have to be how the process works - in Pro Tools the GUI is compensated for in the same way as the audio so things at least appear in time. Logic's issue is that it is not compensating for latency with anything displayed on screen, only with the audio. So you might not class it as a "bug" but it's certainly poor design and far from "correct" - correct being ideal or what you'd expect to happen. It makes it very ugly to use in a large mix session with things like UAD plugins. The bigger the session the worse it gets. I wish they'd delay compensate the graphics - at least with the mixer meters and built-in GUI components. Inserts are always going to be a little bit out depending on the chain but could still be brought much closer to what you're hearing. But to the original post, unfortunately there's nothing we can do about it - other than use pro tools which comes with all of it's own issues!
  12. Anyone get anywhere with this? I'm having issues with groups not behaving properly (esp. fader levels), but the issue seems to come and go depending on which window/object I have selected when I enable/disable the group clutch. The issues are difficult to replicate and seem intermittent, the groups are just buggy and it's finally ticked me off enough to enquire about it! On a side note, undoing a fader level change on a track that belongs to a group snaps all fader levels for that group to the same value, even if they weren't at the same values before the change. Probably a separate issue but possibly related...
  13. Funnily enough I just stopped getting the flex time error as well! I didn't do anything!...
  14. Fingers crossed it has stopped since the UAD restart, but I'll do as you suggest if it starts up again. Thanks as always!
  15. Same project gives me this every time it gets to a certain point in the drum tracks (near the end): Unexpected request for audio data. See console. (Flex Audio) (click ok) But I have no idea how to get rid of it. Removing the flex time (i.e. doing a BIP) is not really an option at this point as I need to leave it editable for now.
×
×
  • Create New...