Jump to content

machinesworking

Member
  • Posts

    11
  • Joined

  • Last visited

machinesworking's Achievements

Newbie

Newbie (1/14)

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

Recent Badges

0

Reputation

  1. Oh jeez, that's too bad, I've gotten really used to multiple choices for count in, when using Digital Performer and Reaper. It's a strange miss on the Logic teams part, but I also was waiting years for multi MIDI input to various tracks, which we now have so there's hope.
  2. I was wanting to practice a part at bar 1 in Logic that I wasn't that comfortable with and it struck me that Logic doesn't seem to have the count in option to have it give you 1 or 2 bars of metronome without it being in record, the count in option is tied directly to recording only from what I can tell? Other DAWs™ have count in options, well at least Reaper and Digital Performer do, you can have it click only during count in, only while recording and always click etc. etc. Is there any way to get Logic to count in 1 or 2 bars of Klopgeist without engaging the record button?
  3. There was talk years ago about the limit to the amount of icons you can ad to the Custom Icons folder. I'm looking at around 143, but it seems like some are dropping off the edge here? Talk years ago was that it was a 100 icon limit, that seems off here, but what is the limit? I added two more after a couple just up and disappeared, so will it stay at 145? that's the question..
  4. Popping back into this thread, my interest in getting back into Logic full time is of course influenced by the upcoming more powerful round of Apple Silicon computers and my need for a new laptop that will outclass my Mac Pro in most ways. Another way this Affects Logic Pro users is with VEP. Digital Performer can address over 700 midi tracks from a single instance of VEP in a DAW, this is compared to the possible CPU consuming "instrument tracks" for each MIDI channel in Logic, and what amounts to 16 MIDI tracks per instance of VEP from what I can tell. There's an Environment workaround for this as well, but here we go again... Anyway none of it is a deal breaker and I'm looking into Logic again, and already loving the key commands, and how decently implemented they are.
  5. In the search for the best MPE DAW I ended up buying Logic again, Reaper and Bitwig. I already owned Live and DP. Only Logic has the port limitation, all of the others default to All channels/ports and can be used like you describe, only DP has a slight limitation there in that you cannot get all ports along with all channels in multi Record Mode if I recall correctly, but with that mode turned off it behaves exactly like Logic does in the All setting. There's not a single real world advantage to summing all ports to 16 channels only, it's a leftover from earlier days, and IMO I see no reason changing it would break existing setups. Not saying it would be easy or worth it for the Logic team to do it, but it's not a prerequisite for any of Logic's unique behavior compared to other DAWs. I'm primarily a guitar player, I can play keys enough to write, but auditioning sounds and simple melodies against each other is pretty cool, a bass sound on a regular synth and something on an MPE etc. Mostly you get used to be able to do this and it's bizarre not to be able to. I separated out my Moog to channel 16 years ago in Logic to be able to do this. Auto Demix by Channel is definitely different now, I hopped off Logic at version 8 so it's been a while, but it's behavior is kind of compromised, it works, but there's a delay at first, you have to "prime" the track..
  6. Great explanation thanks, it's been years since I did anything in the Environment but I remember doing something where I took all MIDI input sources in Cluck and Ports got rid of SUM and wired them individually to the Sequencer Input in order to solve some issue related to this. I don't think it solves this particular issue though, and I remember it having issues with Mackie controllers, which I would assume will now translate to issues with Logics control surface support in general. Plus I think I'm making the same mistake I made back then, taking things out of SUM just allows you to do things like attach and arpeggiator to a specific controller, it's the Sequencer Input that's summing the ports. Yeah it's the "Auto Demix by Channel if Multitrack Recording", setting in the project recording options. It's.... different than it used to be. Logic seems to be trying very hard to disarm any track that's not currently being played, I'm still trying to figure out how to turn these settings off, tracks when you load a project, some tracks are completely unloaded, and take one or two seconds to load the first time you arm them. Weird housekeeping scheme, probably useful if you have 120 tracks of AUi's etc. Since MPE instruments ask for 16 channels but in my and most peoples cases we're not doing anything where you need all 16, it's easy though to assign 2-15 to the MPE instrument in the case of the Linnstrument, then use channel one for basic instruments etc. So a basic set up can be done where the MPE instrument gets it's own hardware exclusively. The comparison to the way it works in Bitwig or Reaper is sad though. In either of those DAW all controllers can be assigned to a specific virtual instrument, and you can do things like take the generic All input port and route it to the MPE track, so regular MIDI and MPE controllers controlling the same sound, at the same time. Along with say the moog's keyboard playing only it's own sound. Not to mention being able to arm two MPE tracks at the same time with separate MPE controllers playing each track. It's I think really a problem that doesn't rear it's ugly head if you only use Logic, have a smaller studio, or never really thought of using multiple MIDI controllers at once. I just got spoiled by the other DAWs I've used.
  7. A month later. I'm sitting here surrounded by my set up, MPK88, Seaboard Block, Linnstrument, Beatstep Pro, and Push 2. Plus a Moog with a keyboard attached. Six possible input sources, two MPE devices. I'm sitting in front of one of the worlds most powerful DAWs, developed by the worlds richest company, and lowly Bitwig and Reaper, with less combined staff, let's be honest here, probably 1/8 of the staff combined. both DAWs can have two separate tracks with MPE controllers assigned, plus the other 4 with their own ports and channels as well. I had no idea how often I relied on the ability to test out ideas against each other before commiting MIDI, but it's a real WTF moment to not be able to. Even Live and DP which do not do MPE natively can still have multiple MIDI controllers assigned to various virtual instruments and hardware, along with the 16 separate tracks it takes for an MPE instrument. Anyway, weird limitation, I might try hardwiring the MPE controller port to an instrument track and see if I can figure out how to permanently set it. Not sure that would really work though. Seems like you would have to separate all MIDI from SUM, I'm afraid that will break some things.
  8. 2/ In DAWs the separate by port you can decide to receive all ports and all channels. Since Logic already receives all ports, and separates by channel, I would doubt that any change would change this fundamental behavior. I'm not saying it's trivial, but Logic already sees all ports, it just sums them on input. 3/ Yes, there are definitely things routing wise that other DAWs have no issues with, external sequencers and arpeggiators, and now MPE instruments, really point out this odd design choice of Emagic's back in the day. Past the input stage I suppose is what you meant. I would bet 90% of DAW users have one controller keyboard. The same reason Digital Performer doesn't have key note zone limiting on MIDI tracks as an option, or Bitwig and Live don't do SysEx or NRPN. Only a small portion of people do anything complex with MIDI. As far as it changing in the future though, DP10 introduced object oriented MIDI for the first time to DP in Clips. Of course this was met with grumblings from the regulars because it changes the way looping works in DP, all looped MIDI became Clips. Any time object oriented MIDI was brought up over the years plenty of people objected to it. MOTU are a smaller company, so there's less likely death by committee. The owner does what he wants. Considering it's a "film composers DAW" I don't think a single person expected them to introduce Clips before they got some sort of articulation management for example.
  9. Why? If you've ever used Reaper, Live, Bitwig, DP, they all easily do this. They also all have an "all" setting, where you can just flip around to various tracks and any controller you touch sends MIDI to that track. It's a missing feature, I can't see a single advantage to it.
  10. Yes it only sees midi coming into tracks for recording by channel. If you need to record from multiple ports at the same time, using the same midi channel from each port...you're basically SOL. I wish they would change this, but as you can see from other responses, that opinion is not universal and Apple is unlikely to change it anytime soon... what are you trying to do specifically? Thanks for the reply dewdman42, I run into you all over music forums! I remember being able to do some sort of separation of ports by taking all of them out of SUM in the Click and Ports layer of the Environment, but I remember that breaking controller support for Mackie etc. It's pretty crazy that it's still an issue to me. I'm sitting here with a BeatStep Pro doing drums in Battery on a track, but unless I take all tracks out of the All setting, and assign channel 10 to the Battery track, I'm getting BeatSteps sequencer on any track I select, and obviously I can't do anything MPE until I lay down the Beatstep sequence. This is one of those things where people have no idea how good it can be IMO. Reaper and Bitwig have zero issues with MPE instruments like the Linnstrument assigned to an MPE instrument while another track recieves a sequence from Beatstep or I have the MPK88 playing another VI on a different track. The thing is though, Logic hit the golden triad for me recently, Clip based sequencing with it's grid launcher, and MPE and Articulation maps. Plus just being an old school DAW like Reaper or DP10, with all the features, no hand holding. I love how fast the GUI is, but the record arm switching is weirdly slow. I'm in the market for an iPad, that new Logic Control is just a thing of beauty. In the search for a solid MPE DAW it's funny watching my various controllers get attention or get ignored by them. Bitwig and Reaper love the Push 2 and BeatStep, no support from Slate for the Raven. Logic loves the MPK88, has some issues with the Linnstrument and the BeaStep and ignores the Push 2. Anway I'll bear with it, I remember having a solid fast workflow with Logic 4-8, an if I'm gonna stay on mac it's probably a good idea at the very least to be comfortable with the DAW that's already compatible with the upcoming Apple Silicon macs.
  11. I'm attempting to come back to using Logic X after ten years away. So port assignment in Logic. It's the elephant in the room for me. In other DAWs I use, have used MIDI input into the tracks is assignable by port, i.e. I can assign my MPK88 to to a track with a piano on it, and my Linnstrument to an MPE capable track. This is true and easy in both Reaper and Bitwig for me. In Logic so far from what I remember and what is obvious, I cannot assign a MIDI controller to a specific port, only a specific channel. This of course gets in the way of setting up an MPE instrument along with a regular controller, as the MPE instrument grabs 16 channels on it's own. So before I go deep into the environment attempting to see if I can fix this, is it even possible in Logic? or does Logic just always see all incoming MIDI by channel only??
×
×
  • Create New...