Jump to content

nebula

Member
  • Posts

    125
  • Joined

  • Last visited

nebula's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I know this is a late response, but I am presently thinking about my upgrade path from Mac Pro 5,1 (also with PCIe SSD) as well. For posterity, here's my take: Presently I use an 828mkII, and I want more I/O (and perhaps higher audio specs). I want a replacement interface that sounds great, is stable and future-friendly. I think MOTU's AVB interfaces fit the bill really well, with USB and Thunderbolt connectivity. Their USB 2.0 driver supports up to 64 audio channels, which is more than I need. So I'll use USB for now, and perhaps Thunderbolt in the future. IMHO there is no reason in the world to get rid of a Mac Pro 5,1 tower unless you desperately need Thunderbolt (or a retina display) right now.
  2. Is there an example I could hear? Maybe post a SoundCloud link?
  3. Back when Apple sold mechanical hard disks, all the laptops came with 5400 rpm drives, and Logic worked just fine. (I don't know how well it would do 8 stereo 24 bit 192 kHz tracks, but I assume that's not what you meant.) A bit off-topic here, but ... People (myself included) were very disappointed when Apple announced the new Mac Mini in 2014, because none of the new offerings are as fast as the previous top-end config, from 2011. Back then I held off buying the then-current 2011 model, as the rumor sites said the Mini was about to get its long-overdue refresh. I decided to wait a month or two, until the next Apple event. Surely enough, a new Mac Mini was announced: the low-end models got a very modest speed improvement, but there was no longer a quad-core configuration available, and you can't upgrade the RAM. I decided not to buy it, because the new Mac Mini would not run Logic as well as my 2006 Mac Pro, and I would need some sort of thunderbolt docking solution to use my 30" monitor and my FireWire audio interface at the same time. Nowadays I absolutely would not buy one, largely on principle - I don't want to buy a 2-year old computer that can't outperform a 5-year old computer. Instead I bought a used 8-core 2008 Mac Pro tower in mint condition from a Craigslist ad. I only had to swap out my old tower and I was in business. Apple just announced last week that my 2008 machine is not on the "supported hardware" list for the next version of OS X, but I have no regrets. This computer is really fast - certainly faster than a Mac Mini, with the added benefit of more legacy connectivity, accessible drive bays and RAM. 2 years ago it cost me a little less than i would have spent on a new 2014 Mac Mini. If you do go with a Mac Mini, I recommend you pick a configuration with as much memory as you can get, just for some extra confidence it will run tomorrow's potentially RAM-hungry software.
  4. Did you ever get this resolved? I'm having a terrible time recording the output of the sysex mapper in 10.2.1. It outputs sysex correctly (I can cable it to MIDI Instrument and it works). But when I cable the transformer to the sequencer input and hit record, all that's captured is the controller data from the fader I'm moving. Adding monitors everywhere shows that my array of other transformers are working as expected, but for some reason Logic chooses to record only the un-transformed output directly from the fader. Unfortunately Logic can't get the checksums right on its own, or I'd be using a sysex fader.
  5. Thanks for the reply - first let me say that the operation performed in the gif is different from the operation I described. Eric first performed a shift-option drag to an arbitrary value to make all the selected events equal, then he entered a numeric value for one of the events. Since Logic will then change all events relative to the change of the event you edited, and because he just made them all equal, they all jumped to the same value. The functionality that is gone is the ability to select multiple events, double-click on a value to change it, then hold option-shift while pressing enter to absolutely apply that value to all selected events (i.e. not relative to their original values). Eric's method works and is almost as quick as how it used to work. And I never thought to do it that way. It's still an extra step, but it's a good timesaver.
  6. I think Apple's Logic team dropped the ball on this one. In all versions of Logic up to version 8, if you had multiple events selected in the event list, you could simply double-click to edit one value, and hold option-shift while pressing Enter - then all selected events would jump to the value you edited (note number, velocity, duration or position) A few years ago I mentioned its absence here on LPH, and I have submitted this as "feedback" to Apple. I can understand if they took this away by accident, but they have even removed references to this feature from the documentation. I guess now they expect us to use the MIDI Transform window. It works, but it's cumbersome and inelegant
  7. Please forgive the soapbox post that follows - I feel the same way as the OP, just not for the exact same reason: I've using Logic since version 2.5, and I just started working with Logic X a few weeks ago. I can now say I have some serious concerns with the UI as well. The dark color scheme to me is OK in the "tracks area" and graphic editors, but the list editors, libraries, browsers, drop-down and pop-up menus are indeed harder to work with. The new vintage synth to me is really, really stupid. Why on earth do we have multiple completely different synths in one plugin, instead of a plug-in for each synth? The new UI on the compressor really bothers me as well. Like all the new plug-in designs it occupies far too much screen real estate, and I have a 30" display. Being resizable is cool, except that it it's impossible to use at smaller sizes because the controls are so relatively small with vast fields of wasted unused space in between. Analog meters are stupid on plug-ins, because it is much harder to see a moving needle moving across a large space than a simple, skinny, brightly-colored bar graph. And what's with the disappearing knobs when you switch compressor models? Couldn't we just gray them out like before? Every time I try to audition a different model it seems like 3 controls disappear or change function instantly (too fast for my brain to process), and I then need to switch back and forth a few times to visually identify what has changed. I really, really dislike the insert slots on the new channel strips. The problem is that your eyes tend to follow your mouse pointer along the screen, and as soon as your pointer passes over the insert slots, THE NAME OF THE PLUGIN DISAPPEARS so it can change into three tiny, separate buttons (bypass/adjust/change). This continually slows me down, because I almost always need to hover the mouse on and off the control a few times to make sure I've got the right one, and the clickable areas for bypass/adjust/change are so tiny now I frequently click the wrong button. I really wish the legacy behavior could be selected in preferences, in which the name doesn't disappear when you point at it, you click-hold to choose a plug-in for the slot, you double-click to "open" (adjust) the plug-in, option-click to toggle bypass status, and command-click to move the plug-in to a different slot. I spend so much time in the mixer, and the basic task of managing inserts and instruments now requires much more visual effort and concentration. Since iOS7 and Yosemite, Apple is obviously moving away from their past practice of "Skeumorphism" (i.e. attempting to emulate 3-dimensional, real-world devices in computer software). Yosemite's new cleaned-up interface is a bright, stripped down, minimalist 2D affair, but apparently the Logic team didn't get the memo. Emagic used to boast that Logic's plugins don't follow the industry trend of displaying stupid woodgrain panels, clunky knobs and meters for a user interface. Their design is utilitarian, but logical and easy to understand. Signal flow is left-to-right. Controls are usually sliders because their movement follows the mouse, and they take less screen space. Some menu options have now been made hierarchal, but those choices seem arbitrary, as many of the functions I use regularly are now buried behind a triangle. Window zoom controls have changed AGAIN. Apple needs to stop changing this with every new Logic release. One of the best zoom solutions - user-resizable scroll thumbs - were only recently been added to Logic (in version 8 or 9), and now they're taken away. And the vertical/horizontal zoom controls have moved from the bottom-right to the top-right, where I don't think they've been since version 6. I use Logic when I'm in a creative headspace. When the UI changes for the worse, I can't help but think of the older, faster way of working EVERY TIME I have to do it the new way. For example I now get just a little bit pissed off every time I try to adjust something in an insert slot. These little things keep reminding me of functionality that has been sacrificed in the name of flashy, marketable designs, and my resulting personal annoyance is a negative emotion that interferes with my creative process, constantly as I use the software. For electronic artists the software has become the instrument - the "main axe". My well-crafted musical software is as important as my favorite instruments, or perhaps even more so. Apple's Logic team must learn to respect this by being more judicious in their UI adjustments, and providing options to allow longtime users to revert to their familiar way of working. Ableton Live costs about $500 more than Logic. Live's UI is an attrocity to me, but at least it has been relatively unchanged since version 1.0. For creative professionals this is essential. Ableton gets that, Emagic got that. Apple wrote the book on that, but they have lost their way. I will have to jump ship if this doesn't get better, for artistic reasons.
  8. I briefly owned a BCF2000. I returned it because I didn't like the way it worked with Logic without an LCD. Mind you this was a long time ago, before Logic had a little colored strip telling you which channels are active on your control surface. Did you try putting the BCF2000 into "Logic Control" mode? Then you should be able to add it to Logic as a "Logic Control".
  9. I have found a solution. Control-click the solo button on the output channel in the mixer. A little red line will appear in the button indicating that it is "solo immune", and it also stops responding to the Master. Unfortunately I also found a bug. Once you engage the red-line-solo feature on an output channel, you can disengage the feature and the output still won't respond to the master fader. Restarting Logic returns the output channel to its normal behavior!
  10. That surprises me because it would seem that if you are using outputs to process audio externally, you might not want to adjust those levels as it would change the sound of your song. (Example: you have an output connected to a reverb unit. You turn down your master volume, so your stereo output level goes down, but you also reduce your reverb send.)
  11. nebula

    Loop question

    If you option-drag the right corner of a MIDI region it will time compress/expand the notes. So ... hold down option and drag the right edge of the MIDI loop to make it twice the length (and thus half the tempo)
  12. I would like my Logic Pro X "Master" channel to adjust some audio outputs but not others. Some of my outputs are generating control voltages for analog synths using "Silent Way" (via ADAT-connected ES-3). If I move the master fader, those control voltages change, causing all sorts of havoc. Am I overlooking something simple?
  13. After years of using Logic 2 through 9, I'm now starting to use X 10.1.1 .... presently just getting a feel for things. Which brought me to this thread - I use a MOTU 828mkII and I have a do-nothing knob at the top of my audio tracks. Which is interesting, because the feature was introduced in 10.1 ("Mixer now allows remote control of microphone and other input settings for compatible audio interfaces"), then fixed in 10.1.1 ("Audio Device controls no longer sometimes display non-functional buttons for the attached audio interface") ... I'm glad I found this thread, or I'd probably still be wondering what they're supposed to be. Since this cool feature currently just takes up space on my screen, I just hid the audio device controls in the mixer by unchecking View > Channel Strip Components > Audio Device Controls.
  14. What kind of data do you want Lemur to receive? If you want it to process notes from a recorded track, you should be able to just create a new External MIDI track and select the Lemur Daemon as the device you want to send to (just like any other external MIDI device). Start out with a simple Lemur template that will respond to (or display) incoming MIDI data, and make sure it's getting data from Logic. I found that the Daemon would repeatedly stop working with Logic for no apparent reason, with no evidence that it had "crashed". Sometimes it just wouldn't appear at all. I did not try it with any other DAW. I haven't got my new system set up yet so I can't really try stuff with you, but I will suggest that unless they rewrite the Daemon, don't bother with it. I don't know or care whether it's a Logic problem or a Lemur problem, it still made me miserable for weeks.
  15. I found the Lemur Daemon to be so horribly unstable, I bought a MIDIsport class-compliant 1x1 MIDI interface and plugged it into my iPad using the USB camera connection kit. The MIDI plugs talk to Logic through a Unitor 8. All my problems went away. I've also heard the iConnect products are really awesome for this purpose, allowing you to power your device at the same time. So far all I've done with Lemur is create a pretty good virtual front panel for the Korg DW-6000, but I plan to set it up to control all of my 1980s one-knob synths.
×
×
  • Create New...