Jump to content

cinningbao

Member
  • Posts

    571
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

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

cinningbao's Achievements

  1. Please delete this if necessary, it isn't a question.. I just wanted to post a 10-minute video I made about a trick I re-discovered (and possibly even actually requested from Apple as it appeared after I sent a feature request asking for Phase control of the waveforms) which focuses on generating random values on every keypress using the MIDI FX Modulator. It can generate gentle chaos or mind-numbing maximum modulation depending on your desires. Anyway, wasn't sure where to post it so it ended up here πŸ™‚ I hope someone finds this useful πŸ™‚
  2. Automation! You can see the yellow Automation line for the Volume in the screenshot you posted, create another Automation lane in that audio track, and automate the Pan move you want from there. https://support.apple.com/en-gb/guide/logicpro/lgcpb1a1ea03/mac
  3. Thanks David, it isn't my machine it's running on - their machine is at one of the later OSs. And yes, all regular scrolling on the other machine, mouse and trackpad, works fine.
  4. I'm just trying to clarify something as there isn't many folks talking about it (which makes me think this limitation is by-design) These Audient iD24's have that big ScrollControl wheel which appears to behave like an extra scrollwheel on your mouse, except that it's a physical knob on the soundcard. This ScrollControl works great with plugin interfaces and, from what I can gather, scrolling the arrangement window up and down, but the ability to attach the knob to a channel volume, pan, send or anything on a mixer strip seems to be non-functioning. Does anyone hear have that device and can confirm that my buddy shouldn't expect it work like this? It's funny because there is a short video of some chap with an old Logic doing exactly that, but from testing now it seems the functionality has been removed. Can anyone confirm this? thanks! πŸ™‚
  5. My pleasure! This modifier command works across a lot of elements in Logic; moving regions, send levels, track volume.. Happy fine -uning everything πŸ™‚
  6. Press and hold the automation line you want to fine-tune, and hold cmd & ctrl while you wiggle your mouse up and down for the finer values.
  7. So it's just a random bug which I can't workaround apart from to upgrade? Oh well.. thanks πŸ™‚
  8. Oh guys, I'm sure I get this about once a year but I can never remember how to search for the answer. What has made Logic decide that it won't fully instantiate plugins in an audio channel? Attached photo has my 12 string bus, and an EQ and comp in the chain, but the interfaces are half bright and the knobs can't be moved. There's nothing unusual about this channel; it's a summing stack. What crucial information has left my brain? thanks πŸ™‚ Actually any plugins inserted on this channel are blocked from processing and interface manipulation. But you probably knew that already πŸ™‚ ------- EDIT a little closer look reveals that the plugins _are_ processing but the interfaces cannot be adjusted. What on earth have I done? πŸ™‚
  9. Just tried a few things, but unfortunately I don't think so. Logic wants to know how it's supposed to deal with the audio material. It really doesn't take half a second to press ctrl-alt-a to create a new audio track. Maybe just do that?
  10. In your situation, where removing plugins which introduce latency change the sound too much, and then affect ongoing performances, I just: - bounce down what I need - Save that project - delete the part which introduced latency so only the bounce remains - record the new part(s) - Save as new project - import problem part when finished recording Organising things in summing stacks really helps in this regard.
  11. Happy to help! If you can mark the post with the working solution in as 'solved', David (site mod) will also be happy πŸ™‚
  12. You can just (well, this is what I do for forwarding crash reports) ctrl-a the text of the crash report, and save it to an appropriately-named text file, and forward that to the dev.
  13. If the Logic guys had decided to make the Velocity processor running all the modes on at the same time, they would have had a lot of complaints! I'm pretty sure it only does the thing it's currently set to. Just watched your videos, I can see what's going wrong: I completely mis-appropriated the Velocity Processor. I thought the 'Range' was a kind of Velocity 'gate' which only allowed notes which sat within the Velocity range specified - how wrong I was! I'm surprised there isn't a simple Velocity Gate in the MIDI FX. There are 2 ways round this: - build a thing in SCRIPTER (which need scripting knowledge) - I would automatically go for plogue bidule to build a simple velocity gate as a MIDI FX, it's probably just as easy in Reaktor as well. - OR, the final easiest answer (which only just occurred to me), use the Inspector to adjust the Velocity range of the track. Look for 'Vel Limit' and the left value is the lower limit, and the right value is the upper limit.
  14. I've just realised I mistakenly incremented the Note numbers when you could actually assign multiple pads to the same note, (all C1 for example), just a diff velocity range.. have fun!
  15. Since DMD creates a new instrument channel for each pad, why not just spread your samples across multiple pads and use Velocity - Range (MIDI FX) to manage the triggers? EG, low vel kick on C1, vel range 1-49; mid vel kick on C#1, vel range 50-80; hard vel kick on D1, vel range 81-128 It's a hack but it works.
×
×
  • Create New...