Jump to content

TequilaKez

Member
  • Posts

    70
  • Joined

  • Last visited

Recent Profile Visitors

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

TequilaKez's Achievements

Apprentice

Apprentice (3/14)

  • Collaborator Rare
  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later Rare

Recent Badges

2

Reputation

  1. Ok so for anyone encountering this, and its come up a few times unanswered in this forum, here's the skinny. So I found my presets in ~/Library/Audio/Presets/ on my old install and copied them over to ~/Library/Audio/Presets/ on the new one. Now for plugins that I have saved presets for, Logic is now displaying them in the list and knows where to save new ones. For plugins that I have never saved a preset for, logic still pops a dialog to the desktop, not knowing where to look. So why might this be? Looking at the permissions, on the old install (and my laptop) the permissions are drwxr-xr-x me:staff Presets where as the fresh install for some reason it's owned by root drwxr-xr-x root:staff Presets Presumably this means when the plugin installers tried to create the folder structure, they couldn't write to the folder. Then when logic doesn't find a folder there for a particular plugin it goes ¯\_(ツ)_/¯ So now with permissions fixed, for the rest of the plugins I guess I just need to run the plugin installers again. Hope that helps.
  2. Thanks I thought that was the case. But before that folder structure was generated automatically and the presets just went in without intervention by me. It's as though I have to make those folders manually and tell logic where they are each time. Apart from being tedious, something doesnt seem right. Does anyone know exactly what the permissions should be on ~/Library/Audio/Presets?
  3. I've seen this question or similar asked a few times but I'm not seeing a real answer, only just pick a location and live with it. Bt I'd really like to get to the bottom of it because it means I've lost a lot of presets otherwise. And it doesn't feel right having to direct logic each time. So usually on a fresh install, when you press save on logic's plugin window header, it just saves to a default location somewhere and they show up in the menu. But I had to do a fresh os install and migrate from a backup and now Logic not only has lost all my 3rd party plugin presets, but it seems to not know where they live and pop up a dialog defaulting to an arbitrary folder each time, usually desktop. Since a few versions back it seems Logic has moved its preset locations from ~/Library/Application Support to ~/Music/Audio Music Apps Indeed all my presets for Logic's internal plugins are still there, and they show up in the menu fine. Does anyone know where the default location for saving of 3rd party plugins presets is supposed to be? I'm referring to saving a preset with Logic's plugin window header, not within the plugin itself. It could/should be one of the following, but Logic seems to have forgotten where they're supposed to go. /LibraryApplication Support/Logic/Plugin Presets/ ~/LibraryApplication Support/Logic/Plugin Presets/ ~/Music/Audio Music Apps/Plug-In Settings /Library/Audio/Presets ~/Library/Audio/Presets
  4. This doesn't seem to work for me. I could have sworn in the EXS24 days, the currently playing zone would be automatically selected/highlighted when it was triggered. I still love dropping a bunch of drum samples in Sampler and using transpose to audition options while the track I playing. But it makes it hard to know which zone is actually playing considering there are a few places transpositions can happen and they can be applied simultaneously. Am I missing something. e.g the yellow zone in the screenshot is not the currently playing zone, just the last one I clicked with the mouse. Midi Out is definitely on. It's C1, then transposed +20 in the region inspector.So it should be selecting the last zone.
  5. I've made a simple script for sending midi CC data with sliders, affectively allowing CCs for external synths have names and be automated like soft synth parameters. Problem is, if I've just designed a nice new patch on my synth, and then I drop in the Scripter and load my script, it sends all the parameter values at their defaults value (all 0) wiping my patch. From the docs. ParameterChanged is called each time one of the plug-in parameters is set to a new value. ParameterChanged is also called once for each parameter when you load a plug-in setting. How can I stop the second thing happening?
  6. Ahhh so we just have to role our own. Ok think I have that working, thanks for the tip!
  7. Hello Script lords. Anyone know if there's any way at all to get Scripted to receive NRPNs? It definitely isn't one of the stand event types, but perhaps there's another way?
  8. Oh cool. Never heard of Keyboard Maestro but it does look handy. I'll check it out. Thanks!
  9. Ahhh how did I miss those. Not as great as typing in a value, but I'll take it for now.
  10. Not sure Logic version but pretty sure its up to date. The delay is presumably caused by Logic not having complete control of all the variables which induce latency when 3rd party drivers and plugins are involved. The UAD Console has an 'Extra Buffer' setting, as well as 'Input Delay Compensation' and upon testing, these all play apart in how off the recording is. I believe the idea is that 3rd party devices and plugins *should* report their latency to logic, logic *should* do some math and figure it all out. But in practice, for whatever reason it often doesn't work. I've tested on multiple systems, and friends confirm the same as me using UAD and other 3rd party interfaces, but it's never consistent. Factors affecting how off the recording will be are.. - UAD Extra Buffer - UAD Input Delay Compensation - Logic buffer Size - Low Latency Mode on? - Plugins in the Master Bus? - Track routed to a Bus? - Does the bus have plugins? Considering how complicated it can be, I'll let them off this time. I just want a wait to *tell* logic in numbers how out the recording was, after the fact (because my table does know).
  11. By Slip I mean move the audio inside the regions without moving the regions themselves (like in Final Cut etc) I've never been able to work out why logic consistently records out of time, but as there appear to be so many variables, I've just made a big table of tests and recorded results so I know. For pure audio I can consult the table and adjust the 'Recording Delay' in preferences to accomodate. But for recording External Instrument tracks, while monitoring the audio with the track playing and hearing everything in time, the recorded audio is always out. Low Latency Mode can minimise, albeit not fix, the delay. But usually it means half the plugins get disabled so it won't sound right while recording which can kill the vibe if you're also tweaking synth knobs while recording etc. This means Low Latency Mode needs to off, which means the recorded region audio can wind up anywhere up to 250ms out of time. Some times it easy enough to find a transient you know should be exactly on a beat, and chop and move the region that way, but sometimes there are no visible markers. In this case it would be great to select all the regions and just type in a 'Slip' value (from my table) to move all the audio. Any idea if this could be done? Even nudge with the nudge amount set to 1ms would suffice, but I don't want to nudge regions. I want to nudge audio and have the regions stay where they are.
  12. Damn shame. Seems like a bit of an oversight and one of the reasons why people seem to hate on looping regions so much. Too much workflow killer. That and the fact its hard to grab hold of them when zoomed out. But they seem to have cottoned on to both those issues with pattern regions, hopefully they've got improvements planned.
  13. So I use looped regions a lot, like always until there's a reason not to. But when the track is playing it's like you only have 2 options. 1. Turn off catch playhead and view/edit the source region, but then you loose the visible representation the playhead moving over the notes so its hard to know what note is actually playing. 2. Turn on catch playhead and see the playhead rolling over the midi notes, but everything is greyed out so you can't edit anything because it's not showing the source region. Either way it sucks and I end up having to go find the source clip, cycle around just that region to have editing abilities, but now i'm in a different part of the song. The new pattern editor is great for drums and certain mono stuff. It doesn't suffer this problem as you always get the editable source pattern wherever you are. But I can't see how to replicate that behaviour with the piano roll. Have I missed something?
  14. So internet speeds are plenty good these days for a fast Screenshare / VNC over the web. This opens up tantalising opportunities for using a laptop as just a node to make edits to projects that live on a beefy studio DAW. Problem with screen share of course as there's no audio. This can be alleviated on a LAN using AUNetsend on the Logic master channel, and AUNetreceive on the laptop. In fact to my surprise this works extremely well, I can barely notice any extra latency. But the idea is of course to whip out the laptop and a pair of headphones anywhere on the go, and that means using phone's hotspot. But Hotspots have NATs and no portforwarding, so that means we can't open a port for AUNetrecieve. Does anyone know of a way to stream Logic's output to another computer? Or even to an iPhone? Extra latency is tolerable for the convenience, but it wouldn't want to be much more than a second. The only thing I can think of is HOST:Logic>Black Hole>OBS-Studio>-------->CLIENT:VLC But that's a bit convoluted and a pain to setup each time, and the OBS step adds unnecessary latency. Could there be a better way?
  15. Yes I imagine that would turn the developers off, because there's pitfalls and performance issues related to bouncing a mix just to get a waveform. But when you're actually using logic hands on with stacks, it becomes clear you'd be happy with something rather than nothing. For a solution than doesn't require mix downs, right[or control] click the track and tick 'use for stack preview'. Easy.
×
×
  • Create New...