Jump to content

MonoPoly307

Member
  • Posts

    112
  • Joined

  • Last visited

Recent Profile Visitors

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

MonoPoly307'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. Hey guys I'm using a two-tier setup with MainStage for the first time. I've started with a template ("Two Keyboards"), which by default seems to send all MIDI from both physical keyboards to the upper and lower keyboard layer in MainStage. This seems easy enough to fix, in the Layout section. However, when I add a second sustain pedal, to use with the upper physical keyboard, I'm struggling to assign this. Ideally I'd just like every control (pedal, mod/pitch wheels, keys themselves) to all be grouped together automatically so I don't have to assign them all to the respective upper or lower keyboard in MainStage. I'd love some tips on how to sort this out. Thanks guys! Mike
  2. Done! Let's see if that helps. Thanks so much! Mike
  3. Thanks heaps - I've just done that. (Seems sustain chase is a subset of note chase, now... but I've unticked the box). I'll see if that makes a difference. Thanks for the suggestion! Mike
  4. Hey guys My partner is a piano teach and has been recording some piano accompaniments in Logic over the past few months. I've set her up with a simpler setup than my studio... just Logic (latest version) running on her 2018 MacBook Pro. Her projects are very straight-forward, often just one track in the project - using the Native Instruments Grandeur piano. Sometimes she'll record additional tracks with other MIDI (for example, a guitar). In several of her recent projects, she's gotten part way through recording the piano MIDI part, perhaps edited some of the MIDI (although not always), and then started recording additional piano on the same track. She is always very careful to ensure that there isn't a "pedal-on" event before the point where she's dropping in the new MIDI. The issue that keeps occurring is basically a failure of the pedal-on/pedal-off messages to happen at the right place. So a whole phrase with quick on/off of the pedal might only record a long pedal. Or sections which were supposed to have pedal have nothing at all. The result is that the new section sounds like a mess, pedal-wise. With no way to rectify the problem, we have to simply start a new project. Sometimes, the piano parts are complex, and as a new Logic user, my partner's finding it discouraging! We've checked her hardware (including a pedal swap-out), and it doesn't seem to be hardware-related. Some whole projects are fine, without this occurring. I know my way around Logic well, having used it for several years, and I'm completely stumped by this issue. I'd love ANY suggestions as to where we can start. Thanks heaps guys, Mike
  5. Hey guys I've recently upgraded the studio Mac to a 16" MacBook Pro with an M1 Max processor. Was biding by time until the Apple silicon Macs became available with larger quantities of RAM. I'm super happy with the machine so far, especially the quietness of its performance. Unfortunately I'm hitting a few troubles when running Logic. From time to time, the project I'm working on will stop playing, and instead I will hear very loud bursts of what sounds like white noise, at intervals of approximately one second. This continues until I turn my interface off an on again. Looking at TotalMix (RME's mixing app that controls the UFX interface), the source of the white noise seems to be Logic, as it's coming through the DAW channels. The interface I'm using is an RME UFX (the original version) with the latest firmware and latest drivers. RME typically make rock-solid drivers and update them frequently, so I wouldn't expect this issue to be caused by the interface necessarily... although when I run Logic through the Mac's internal interface and speakers, as a test, the problem doesn't seem to occur. Here's a video of what's happening: Really keen to hear if anyone else has had this problem - especially with an M1-based Mac and/or when using an RME interface. I'm still trying to nut out whether it's the RME drivers, or Logic, or the RME hardware itself, that might be causing the issue. Thanks in advance for any light you might be able to shed, or how you might have solved this problem if you've experienced it too. Cheers and stay safe, Mike
  6. Hey guys I was super excited when Logic introduced all their Ableton-like looping features last year. We're hoping to do some loop-based gigs later this year. While Logic's looping interface is amazing, it still doesn't easily let you set up and control your instruments and plug-ins for live playing. MainStage does this brilliantly - so I'm thinking I will run Logic for all looping and realtime control of the set, but MainStage for all my patches. Planning to do this on the same machine. (To ensure the incoming MIDI doesn't interfere with Logic, I'll turn all MIDI inputs off in Logic's prefs). I've had a quick test to see how this might work, and all seems fine. But I wanted to ask... are there any technical reasons whey LPX and MainStage shouldn't run at the same time, on a single machine? I'm using a 2019 MacBook Pro with plenty of RAM (64GB). But I'm wondering if there are other things that could go wrong when running these two programs together. Thanks in advance for any thoughts or experiences you've had that you're willing to share. Cheers Mike
  7. Thanks heaps for sharing your thoughts! I think you’re probably right to be honest... suspect that any gains in the way the GPU handles my external monitor will be lost as the smaller processor, with less thermal capacity, tries to keep up. Most of my projects are pretty RAM-dependent, as I usually work with sample sets like Spitfire and Omnisphere... so potentially as long as I had 32GB of RAM, I’d be OK with the 13” quad core... but equally, it’s really a big risk and a disruptive process too. At this point, I’m probably better holding onto the 16”, putting up with the fan noise, and waiting until the higher-level M2(?) chipped MacBooks arrive next year. Thanks again for your reply! Mike
  8. Hey guys I've been using a MacBook Pro 16" for a couple of months in the studio. It performs well, but when connected to an external monitor, it gets ridiculously hot even during simple projects, and the fan noise is excessive - far beyond anything I've heard from any previous Mac during Logic sessions. I've read that this is a problem with the 2019 MacBook Pro 16, due to the automatic switching to the dGPU whenever an external display is in use. The dGPU works hard even if there's no significant load, and drives temperature and fan noise up as a result. It appears there is no way to switch to the integrated GPU when using an external display. So... I'm considering switching to a 13" MacBook Pro (2020). These only have integrated graphics, which, ironically means that using an external monitor will not make a shift to a dGPU, and hence the temperature and fans won't go off the charts. My current 16" is specified with the 8-core i9 processor, and I went the whole way and got 64GB of RAM - intended, at the time of purchase, to future proof me for a few years. If I move to a 13", I would be choosing the quad-core i7 processor (2.3GHz), and would of course need to opt for 32GB RAM, as 64GB doesn't exist. (As an aside, I won't be opting for an M1-equipped Mac, as RAM is limited to 16GB, and there are other limitations like number of ports, etc... of course, in 2 years or so, I will be making the jump to Apple silicon when the specs increase a little from a RAM and ports perspective.) So... that's the background. My question is this: is anyone using a 2020 MBP 13", similarly specced, for large projects using resource-heavy plugins like Superior Drummer, Spitfire orchestral samples, Omnisphere, etc? If so, I would love to hear your experience running at low latencies (32 or 64 samples), when working on large projects using heavyweight plugins. Does your Mac's temperature stay under control? And therefore, are the fans relatively quiet? And crucially, are your projects running glitch-free? Of course, if you've come from a 16" MacBook and made the move to the 13", I'd be really keen to hear your experience too! Thanks guys, appreciate your input and thoughts as always. Cheers, Mike
  9. Hey again everyone, Second question from me this morning... just wondering if anyone knows a way to set different tempos for different "scenes" when using Live Loops? As far as I can tell, this isn't a possibility - I've not been able to find anything about it in the user manual for 10.5. But wondering if anyone's aware of a workaround, or if I've perhaps missed something. Thanks guys! Cheers Mike
  10. Hey guys I'm experimenting more with live looping - it's pretty amazing! Wondering if anyone has tried to create a track stack in live looping mode? I've just done so, using a summing stack, and tried to add effects to the track stack (bus). It seems that in live looping mode, summing track stacks don't work with effects. I've been able to add the effects to the summing stack just fine - but even when activated, the audio isn't been routed through the effect. Keen to hear whether anyone else has had any luck with this? Thanks everyone! Mike
  11. OK - thanks heaps for the suggestion! If anyone happens to answer here, I'm happy with that too. Looking forward to any help anyone can offer. Cheers, Mike
  12. Hey guys I'm about to update the studio computer, replacing a desktop Mac and a MacBook Pro combo that I have now, with a single computer for studio and location. Given that the desktop being replaced is a healthily-specced Mac mini, I'm looking for a well-specced laptop. I'm going with the 16" MacBook Pro, and will opt for 64GB of RAM. That's the easy part! There has been a lot of discussion about overheating on the current MacBook Pro 16". It appears that i9 units are most severely effected (although some feel the i7s are problematic, too), and depending on who you ask, it seems that the problems aren't combined to a specific DAW. It's clear that Logic is affected by these problems, though. There's also a general anecdotal consensus that these MacBooks usually only produce excessive fan noise and heat when they're used with an external display. Of course, like many of these things, there haven't been any solid analytical tests done - but it does appear that lots of people have suffered these issues with their new MacBook Pro 16". So. I'm looking for some guidance with my purchase - to try to minimise fan noise and heat to the extent that's possible, by choosing the right specs. As context: my setup revolves around Logic Pro X primarily, and I use fairly sample-heavy / processor heavy plug-ins like Omnisphere, Superior Drummer, and a number of large orchestral sample libraries from Spitfire. I'm aware that the choice of 64GB of RAM will significantly help with performance from these large libraries. Anyway - here are my questions. First: Does the internal GPU make a difference to the way an external screen functions, and the demands placed on the laptop? If I'm choosing between the Radeon 5300M or 5500M (the 5600M is out of my price range), will one of these do a better job of comfortably operating my external display, and minimising fan noise and excessive heat? It seems pretty simple to choose either, and the pricing isn't wildly different, so I'm keen to understand whether the more powerful GPU (5500M) is more capable at keeping noise and heat at bay. (I'm not overly technical when it comes to graphics, as I don't do video work or gaming.) Second: How about the processor? The choices I have are the 2.6GHz 6-core i7, the 2.3GHz 8 core i9, or the slight bump to a 2.4GHz 8 core i9. I'm fairly confident that all of these would run the projects I intend to run... so my question relates specifically to fan noise and heat. Does the 2.6GHz 6-core i7 unit run cooler and quieter by nature? Or do the 8-core i9 processors have the edge here? Or are these processors (all from the same 9th generation family) all similar in the circumstances in which they produce heat and noise? If anyone has experienced both the 6 and 8 core processors personally, and compared them, I'd love to hear your thoughts? (I recall that early in the piece, a few people on here posted about returning 8-core MBP16s and replacing them with 6-core units, to try to deal with excessive fan noise they were experiencing). If anyone's able to help - either with a better understanding of these spec choices (especially the GPUs - in a music context), or your own first-hand experience with these processors and how hot and noisy they've been when under heavy and light loads, I'd really value your thoughts! Thanks again guys! Mike
  13. Hey guys I'm about to update the studio computer, replacing a desktop Mac and a MacBook Pro combo that I have now, with a single computer for studio and location. Given that the desktop being replaced is a healthily-specced Mac mini, I'm looking for a well-specced laptop. I'm going with the 16" MacBook Pro, and will opt for 64GB of RAM. That's the easy part! There has been a lot of discussion about overheating on the current MacBook Pro 16". It appears that i9 units are most severely effected (although some feel the i7s are problematic, too), and depending on who you ask, it seems that the problems aren't combined to a specific DAW. It's clear that Logic is affected by these problems, though. There's also a general anecdotal consensus that these MacBooks usually only produce excessive fan noise and heat when they're used with an external display. Of course, like many of these things, there haven't been any solid analytical tests done - but it does appear that lots of people have suffered these issues with their new MacBook Pro 16". So. I'm looking for some guidance with my purchase - to try to minimise fan noise and heat to the extent that's possible, by choosing the right specs. As context: my setup revolves around Logic Pro X (with some occasional Cubase use), and I use fairly sample-heavy / processor heavy plug-ins like Omnisphere, Superior Drummer, and a number of large orchestral sample libraries from Spitfire. I'm aware that the choice of 64GB of RAM will significantly help with performance from these large libraries. Anyway - here are my questions. First: Does the internal GPU make a difference to the way an external screen functions, and the demands placed on the laptop? If I'm choosing between the Radeon 5300M or 5500M (the 5600M is out of my price range), will one of these do a better job of comfortably operating my external display, and minimising fan noise and excessive heat? It seems pretty simple to choose either, and the pricing isn't wildly different, so I'm keen to understand whether the more powerful GPU (5500M) is more capable at keeping noise and heat at bay. (I'm not overly technical when it comes to graphics, as I don't do video work or gaming.) Second: How about the processor? The choices I have are the 2.6GHz 6-core i7, the 2.3GHz 8 core i9, or the slight bump to a 2.4GHz 8 core i9. I'm fairly confident that all of these would run the projects I intend to run... so my question relates specifically to fan noise and heat. Does the 2.6GHz 6-core i7 unit run cooler and quieter by nature? Or do the 8-core i9 processors have the edge here? Or are these processors (all from the same 9th generation family) all similar in the circumstances in which they produce heat and noise? If anyone has experienced both the 6 and 8 core processors personally, and compared them, I'd love to hear your thoughts? (I recall that early in the piece, a few people on here posted about returning 8-core MBP16s and replacing them with 6-core units, to try to deal with excessive fan noise they were experiencing). If anyone's able to help - either with a better understanding of these spec choices (especially the GPUs - in a music context), or your own first-hand experience with these processors and how hot and noisy they've been when under heavy and light loads, I'd really value your thoughts! Thanks again guys! Mike
  14. Hey guys Wondering if there's any way that you know of to have different vertical groups of loops, in the 10.5 update, play at different tempos? I'm looking at ways I could trigger different sections of pieces that may use different time signatures and tempos, but it appears that currently, everything just follows the tempo and signature set by the song. Hoping I'm wrong... does anyone know if there's a way to do this? Cheers Mike
  15. Hey guys, Hope you're keeping well and making lots of music in this crazy time. Wondering if anyone has purchased the recently-released (2020) MacBook Air, and is using it to make music? I use a Mac mini in the studio, but am looking for a machine for off-site work and live gigging (using LPX/ MainStage). I'm considering a new Air with the i7 quad processor, and 16GB of RAM... along with a decent SSD (2TB). I use some reasonably heavy plug-ins (Spitfire orchestral stuff, Ominsphere, Superior Drums, etc) but I'll try to keep them under control for live stuff so I don't risk processor overloads during gigs. My previous portable machine was a MacBook Pro 13" from 2017. I'd love to hear from anyone who is using the new Air for music production / performance - especially if you're using the 1.1GHz i5 or 1.2GHz i7. How are you finding the processor? The speed (disregarding turbo boost) are slower than anything I've used, but these are 10th gen processors and the RAM is crazy fast. If you have first hand experience of these new Airs, I'd love to hear your thoughts! Cheers, Mike
×
×
  • Create New...