Jump to content

mysticfm

Member
  • Posts

    178
  • Joined

  • Last visited

mysticfm's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. No, I wasn't aware of that, and at least on the computer I currently have access to, that appears to be the reason. Thanks! Is that a new feature? (I haven't used the Library much prior to this, but when I was, I don't remember ever having trouble getting to the Library's contents. And I don't remember seeing that blue triangle before at all, either. If it has been there all along, then wow ... can't believe I never noticed it before.)
  2. Since 10.4.1 I've started noticing that sometimes the Library tab has no contents. The most common situation in which this happens is immediately after I have created a new track, but it isn't the only time. I've reproduced this on both of my music computers ... an older one running Sierra, and a brand new iMac Pro running High Sierra. While the issue occurs on both, it seems worse on High Sierra in that the Library tab is empty more frequently, including on pre-existing tracks, but then decides at some random time to display its contents again. Is anyone else seeing this, or (better yet) who knows why it is happening?
  3. It's not iLok, it's Elicenser (still a dongle, though). IMO, VEPro is an amazing tool for any composer, especially for those with large templates. If you ever get the chance, try the demo. iLok, eLicensor ... I often get them confused, because they both repel me equally. I have every reason to believe that VEPro would be a terrific tool to have at my disposal, and I wouldn't hesitate to purchase it ... if only they would adopt a less onerous method of protection. By the way, so far my template of individually created Aux tracks is working pretty well, even without the record buttons (the absence of which I am quickly adjusting to).
  4. I was baffled by this for a few minutes, as all of my projects have a "Stereo Buss" in them. Then I dug a little bit, and realized that the channel I was referring to is called "Stereo Out" by default. It's just that I have been using a custom channel strip on that channel for a very long time now, present in all of my custom templates, which ends up naming the channel "Stereo Buss" instead (why, I don't know ... I probably just forgot the exact name when I created it). Apologies for the confusion, but thanks again for the details on Stereo Out vs. Master.
  5. Same thing: bouncing = writing the stream of zeroes and ones that you send to your audio interface in a file. As for the master fader, it's a VCA for the outputs, no signal actually goes through it, so it's not in the signal chain at all. Aha, thank you. There has been some confusion in this thread, I think, between the stereo buss fader and the master fader and the nebulous "output fader". I always thought the former (stereo buss) was the one that should be pulled back to control overall volume of a mix (and to eliminate clipping, if it is occurring), and judging from your response it seems I was correct.
  6. What about when you are bouncing? Since the Bnc button appears on the Stereo Buss fader rather than the Master fader, would turning down at the Master fader be too late in the chain to keep the bounced output from being clipped?
  7. Wouldn't clocking issues produce distortion or artifacts all of the time, not just when the CPU is peaking? I get plenty of audible artifacts and glitches, but only when at least one core of my CPU peaks.
  8. I start getting audible glitches during heavy CPU loading with my Apogee Duet 2, and I almost never see that error you are referring to. So from my perspective it seems to be normal. However, if the glitching appears only during loud segments, you may also want to check your gain staging to make sure you aren't overloading something that can't deal with it. (I know that floating point pathways means gain staging isn't as critical as on an analogue mixer, but still, audio plugins and the main output can both be overloaded, which I know because I've accidentally done both at various times and found myself scratching my head over all the distortion and garbage in the signal until I noticed this was happening.
  9. On the first recommendation, I'd always thought the same thing, but I reached the point where I had to try to create a large orchestral template in order to facilitate my work, and so I did a direct comparison of a multi-timbral setup to one with standalone Kontakt instruments. The multi-timbral setup saved me close to half of the RAM footprint (with purged instrument samples in both cases), and also loaded far more quickly ... it was enough to be the difference between being able to use such a template and not, so I switched. Unfortunately I won't use VEPro because I won't touch iLok with a ten foot pole.
  10. It is a struggle, to be sure, and there doesn't seem to be a wholly satisfactory solution. Nonetheless, the DAW you know is always better (read: more useful in practice) than the one you don't, so I don't have any plans of making a switch right now. Until (if ever) I can afford to get a Mac Pro with 64GB or more of RAM and too many cores to count on one's fingers, the only way I can possibly get my work done is with a multi-timbral, purged template, so I'll just have to do the best I can with whatever Logic will give me.
  11. That was kind of a strange read - not really anything different from what I have tried, but it seemed like they were mixing together both of the approaches I described, as well as just accepting the creation of even more aux tracks for automation. Not sure what, if anything, I can take away from that … seemed a little messy to me. Nonetheless, thanks much for the response! I'm leaning toward using my 2nd method and just accepting the loss of the Record Enable buttons. I did notice that Record Enable buttons still light up and function on my control surface for all of the tracks, so perhaps I can get used to relying upon the external controller more than the screen. I also am less concerned about my having missed something since reading an Ask.Audio article today quoting an Apple engineer as saying they don't put any effort into improving or fixing multitimbral mode because they consider it a dying technology that is rendered moot by more powerful computers. Trouble with that idea is that, from what I can tell, one would pretty much have to have a fully-speced Mac Pro for it to be true. My i7 iMac is far from a wimpy computer, but still it maxes out at 32GB of RAM, and even using the multitimbral Kontakt instances and all samples purged, a 200 track orchestral template uses over 10GB before I've recorded a single note. If I was to use standalone tracks like Apple suggests, that base size zooms up to over 16GB, leaving even less space for samples in RAM ... plus, such a template takes about twice as long to load.
  12. I've been trying to get a template setup for LPX 10.3.2 that uses multitimbral instances of Kontakt, since some testing I did showed there were memory use and loading time benefits to doing so. But I've been stopped in my tracks twice now, and I am wondering if there is something I am missing, or if LPX just isn't up to this challenge. The first time, I created multiple multitimbral tracks all at once, using the New Tracks dialog. I selected "Multi-timbral" with the needed number of parts specified in the dialog, and selected a multi-output instance of the Kontakt plugin. This gave me the tracks and channels and allowed me to record on each ... but selecting a channel in the mixer would often only select the first track in the instrument in the Tracks pane, and when it came time to try applying automation, Logic didn't seem able to connect the channels with their tracks either and always wanted to create a separate 2nd track for the automation (which then never worked right). So now I have tried the other method I know of, which is to create a single multi-timbral track in the New Tracks dialog (selecting "Multi-timbral" but specifying just one part, and still selecting a multi-output Kontakt instance). Then I clicked on the plus sign on the created mixer channel to add a 2nd channel, and then pressed ^T with that channel selected to create a corresponding track in the Track view, and repeated those steps for as many additional multi-timbral tracks as I needed for that Kontakt instance. This appears to work much better with regards to Logic selecting the right track or channel when I select its counterpart, and also allows me to record automation on whatever channel and track I have selected, in the same fashion that I could with standalone tracks. All good so far ... until I noticed that none of the tracks I added with ^T have a Record Enable button. It appears I can still record on those tracks as long as I have them selected and press Record on the keyboard or controller, but I find this a little disconcerting (as I rely upon that for a visual confirmation that I am recording on the right track), and now I'm worried about what else might not work right when I set my template up in this fashion. (I already know that Solo, Mute and Freeze buttons on the tracks are useless with either of these multi-timbral solutions, so I was not entirely happy even before this latest round of discouragement.) Am I overlooking a better way to do this, one that would make Logic actually behave in the fashion I would expect? Or am I limited to using one or the other imperfect solution (in which case I'll have to go without record buttons, because not being able to do proper automation was a deal-breaker)?
  13. It does indeed, thank you. I've come around to considering the Behringer my best option for a replacement, if it is needed. Although ... now it seems a replacement may not be needed after all, or at least not quite yet. As a last resort to get my MCU Pro working again, even though I'd gone through all of the preference file deletions and such without any improvement, I completely deleted LPX from my system today and then reinstalled it. And hey presto, all of the sudden the MCU Pro works correctly with it again. I am saying this with my fingers crossed that it doesn't go right back to being screwed up tomorrow, of course … if it does, the Behringer will probably be my next stop. But hopefully not, because when the MCU Pro is working, I do love it very much.
  14. Another vote for a RAM-unloading option for tracks when they are powered down, and for the same reason: that would allow me to make a truly useful orchestral template that doesn't require me to start loading it the night before I want to work with it.
  15. The Fader Bank and Channel selection buttons aren't able to select the latter tracks in my projects ... it's as if it is sending a different selection to the Tracks pane of LPX than to the Mixer pane. I thought it must be a Logic problem, but was told that everyone else's MCUs are working properly with the latest Logic patch. And then I started having issues yesterday with the state of the MCU lagging behind actions I take in the DAW ... like many minutes behind. Weird to see the MCU's Play button clicking on and off, and the timecode on the display changing, when I'm not using Logic at all anymore. I've described the main issue in detail here: /viewtopic.php?f=1&t=131018 Yeah, I really love the MCU Pro, but I have to have a functional studio, and right now I don't and this is the only thing I can think of to change. I've tried plugging it into a different USB port on my iMac, into a powered USB hub, and tried a different USB cable ... same misbehavior. I've deleted my CS preferences and my Logic preferences ... same misbehavior. I've re-flashed the MCU Pro firmware ... same misbehavior. I'm nearing my wit's end on this.
×
×
  • Create New...