Jump to content

KenKennedy

Member
  • Posts

    22
  • Joined

  • Last visited

KenKennedy's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Many thanks for the replies - I think I just gave up. Other regions on the same track were audible, muting/un-muting culprit region made no difference. Very strange. Thanks for the replies and for chiming in, I appreciate it, and apologies for late response from me. If it happens again on another project I'll post a screen shot on this thread.
  2. Hi there, I have a strange thing happening (see thread title). I think it's something to do wtih the change of how Logic X works with MIDI regions to how it used to be in Logic 9, but I cna't work out how to 'force' the region to un-grey and play the note it contains. What am I missing? It's not muted - and there're other regions on the same track that play. Muting/unmuting it makes the dot disappear/re-appear. Thanks in advance for your help
  3. Annnnd, closing Logic X and restarting it, it's behaving again. As you were. Weird glitch perhaps.
  4. Hi, I have been merrily assigning controls (in 'expert view'). Now, (still definitely in 'expert view'), the different assignments have disappeared from view and it is only showing one assignment at a time. What have I done? What have I accidently pressed?
  5. "At least CPU usage is very low which always was and still is EXS/Sampler's biggest asset." - yep, very good point. Sometimes I am amazed at how much it lets you throw at it and doesn't complain.
  6. 7 years later, and now called 'Sampler', but ... 'multiple matches found' still requires an individual decision about which filepath to point each sample. On that window, there should ideally be additional options to point the instrument to that file path for all samples, and also a 'cancel' button to just come out. Currently, without these, you're not going anywhere until you've told Sampler, one sample at a time, what you want to do. For an instrument with hundreds of samples ...
  7. You could automate the EQ/Compression to just come in for that moment in the song
  8. Yep, I second not doing it, particularly if your laptop's already struggling.
  9. ...you can also do an onscreen text meta fader in the Global layer (set to '48' and the range just to the screen set numbers you want to flip between). Doesn't need to be cabled to anything, just magically does its stuff.
  10. Yep, as said its the screensets. Being Logic, it's a slightly backward way of working, but you choose the screenset number first (press any number 1-9 to select, hold down control for anything 10 and above, zero on its own doesn't work), then arrange the screen how you want it, accessing which window(s) etc. Once you've got it how you want it, go to screensets again and lock it, and also name it if you want.
  11. There's probably a much easier solution that someone will chime in with but if you're desperate in the meantime: If the BCN44 is always connected, you could do this in the Environment by cabling up from the physical input to faders objects (which you'll need to create, setting the input chan and cc as per the outputs of the different faders on the BCN44) and then cabling these fader objects to the various faders you want to be controlled as standard. If the BCN44 is sometimes unplugged, it's worth sticking an ornament object in between 'physical input' and your virtual faders, so if the physical input gets muddled up, you just have to do one cable to the ornament again, rather than re-cable all the different faders. Having typed that, that looks as clear as mud. It will mean though that if this is in any template you use, all the stuff you want connected will be connected every time. Anyone with more knowledge than me (not difficult), please feel free to flame this solution down.
  12. Anyone? I'm completely stumped on how to get Logic to record the output of a Sysex transformer object, without going a convoluted route of going out of Logic to something like MIDI OX and back in again. Has anyone managed to do this all within the walls of Logic?
  13. I've drawn a blank re. getting Logic to record the Sysex generated transformer objects in Logic 9. 1) Movements from a Sysex fader cabled into the sequencer input record fine. 2) Movements from a transformer object working as a MIDI fader (ie. being driven by a controller fader) generates Sysex fine (cabling a monitor object in between confirms this and the synth receiving it reacts as expected) but Logic only records the CC controller fader movements, and ignores the Sysex. In settings/preferences, everything is set to enable Sysex coming in (obviously, otherwise scenario 1 wouldn't work). Curiously, the monitor/transport bar shows the Sysex as '1 4 0' for the Sysex fader, and '1 0 0' for the Sysex transformer object. So there is some difference in what Logic is seeing/generating somehow. What am I doing wrong? Or if I'm not doing anything wrong, is there a work around that doesn't involve using the Sysex fader object?
×
×
  • Create New...