Jump to content

Splaaat

Member
  • Posts

    91
  • Joined

  • Last visited

1 Follower

Splaaat's Achievements

Newbie

Newbie (1/14)

0

Reputation

1

Community Answers

  1. Since my last struggle with AAF import at the start of this thread, I've switched to Nuendo 10 as well. I tried using a Protools subscription to convert the files, bought AAT to try and get it to work in Reaper and just found it too unreliable and tedious a workflow. Other than the minor annoyance with the dongle, Nuendo has been very reliable for working with AAF's and post sessions. Logic hasn't been updated in a while and I figured, AAF wouldn't be on their immediate list of fixes.
  2. You get a free Mac Pro with this update
  3. If I remember correctly, Autopunch also auto activates if you set a loop, use your marquee tool to select a point before the loop and hit record? If OP didn't hit the key command, this could be how it popped up. Used to drive me nuts.
  4. I’ll have a look again, but last I checked, Flex and Follow was off. I even tried selecting all the regions and double checked the region inspector.
  5. I'm once again struggling with a smart tempo related issue or can’t figure out how to get around it. So here's the scenario: I’m mixing a track for a client and have imported all the stems. I didn’t set the project tempo at the start of the session and the song has a few tempo changes around 110. My project is currently at the default 120. After sending across the first mix, the client wants me to add some delays and time based fx. I’ve tried the 'Keep Tempo, Adapt & Automatic' modes before dropping the tempo, but they mess up my regions and everything goes out of time. Regions get shorter too. In the 'Smart Tempo' settings I have the options set to 'Off'. I can’t seem to figure out how to change tempo without affecting my regions. Is that not possible anymore? Any help is appreciated. Thank you!
  6. I had this issue on my 2016 recently. Repeating keys and fans would ramp up very quickly especially in Live. Battery health was also failing. They replaced the top-case keyboard and battery and strangely I can't reproduce the fans ramping up issue. I didn't expect that to be fixed and assumed it was just Mojave. I upgraded to the Mini because of the fan issue on the laptop. UPDATE : A clean install seems to have fixed my problems. Still in the process of installing all my software, but a quick test running Logic & Live at 32/64 buffer settings and no crackles or pops anymore. I previously migrated my laptop partition to avoid having to install and transfer all my software and settings. I have a mix/master coming in later this week and will be pushing the Mini to see how it fares under load!
  7. Is your interface connected to Mac Mini via Firewire and the Apple dongles or a dock?
  8. This is exactly the issue I have, simple projects crackling and popping all over the place! I would take it to the store, but the 32GB RAM I added is a pain to replace back to stock. Not sure if it voids my warranty. I'll try a clean install before figuring out what to do.
  9. I'm definitely having some low latency issues and it's not normal. I've been running Macs since 2005 and my MBP 2016 doesn't show any such issues. I run low buffers all the time when I start writing music or working on sound design. I can definitely feel the latency at 256 when I play, so I prefer starting around 64. Once again, my issues are more severe in Live. Logic has a Low Latency Mode which kind of fixes some of my problems. I still hear crackles here and there, which should not be happening. As Ploki mentioned, my issue could be that I migrated from my laptop OS instead of a clean install. But, then there are tons of forum posts showing similar issues on clean installs as well pointing to USB 2 and 2018 Macs. The RME devs have posted some good research and even they agree that there are problems. I will try a clean install in the coming week. Ploki, you mentioned you returned your i9 MBP, what were the issues that you were facing?
  10. Mac Mini i7 6 Core 3.2GHz 32GB RAM here and sad to say everything is not flawless. I've been testing this against my MBP 2016 connected via a RME UFX running USB 2.0. Here are the problems I've faced, 1) I opted for 8GB RAM from factory and on the day it arrived, running Logic/Live at low buffer settings was impossible. 256 was the lowest I could go. UI was sluggish as well. After my 32GB upgrade, things are much better, Logic runs fine at 64, 32 still crackles a bit. Live is comfortable only around 128 sadly. I usually test by running Falcon, Repro-5, Maschine or Legend. Tried a session today morning on Logic and Live. Logic fared much better, still kept seeing 1 (last) core overloading which would lead to crackles at times. I don't seem to recall seeing this single core spiking on my MBP. 2) RME Forums have mentioned issues using USB 2 interfaces. TB3 seems to work flawlessly. To bypass the issue you can pick up a TB3 dock. I tried running the FW400 connection on my UFX. It didn't seem to improve anything for me. According to the RME forum, it should have worked. I'm guessing that my low buffer issues are due to the USB 2.0/Core Audio/T2 chip problem plaguing the 2018 Macs. 3) Not much of an issue for me yet, but the reason for my upgrade was the fan noise from my laptop was annoying me during sessions. The 2018 Mac Mini runs a bit too silent at the expense of running super hot. A light session hits about 90C and the fans are slow to ramp up. Even once the fans kick in, it's a lot quieter than the MBP. From other forums, it also doesn't seem to throttle below base frequency, so that's good. 4) Intermittent Bluetooth connectivity issues. Trackpad loses connection at times. Moving my USB hubs around seem to make it better. I still have all my USB devices hooked up (around 14 devices). But, the issues is definitely there. My biggest problem with the Mac Mini 2018 is the operating at low buffer settings especially in Live. Logic's Low Latency Mode works fine for recording synths. I've yet to test really heavy sessions. These issues I've been facing are with just 10-12 synth tracks. I don't want to upgrade my interface to TB3 just to tackle this problem. I've been quite happy with my RME UFX and it runs flawlessly on the MBP 2016. For people with no issues, what buffer sizes are you running at and how heavy a session have you tested? I don't think I'd face any of these issues if I was just mixing or mastering in Logic at 512/1024 or running light sessions.
  11. I ran into similar problems over the past 2 weeks. Had 3 different projects exported from Premiere Pro CC 2018 as AAF. Importing in Logic worked, but the clips were all out of place. For the first project, I just asked the client to export XML and then had to manually select each clip, but at least sync was maintained even though it was tedious. For the next 2 projects, I decided to download the demo for Protools Ultimate to see if it worked fine on Protools. I was surprised to find the same sync issues in Protools. A quick search revealed a lot of people complaining on Adobe's forums about this issue. Something to do with Premiere Pro 2018's export of OMF/AAF. I've only recently started working with OMF/AAF and was quite disappointed to find that even Reaper doesn't support it officially. I really don't want to buy Protools. I'd rather switch to Cubase.
  12. Is there a setting that you need to enable? This used to work for me, but currently, on Mojave it doesn't seem to function.
  13. *Bump* Any input on this guys?
  14. Hey guys, I've used the Maschine with Logic since 2012 and always believed I couldn't get Maschine's pad input to directly record into DAWs. The only option was to put Maschine into MIDI mode and record using its pads or record into the Maschine plugin and then exporting MIDI. The disadvantage with MIDI mode is that it isn't as responsive as recording into Maschine's own software. Also, you can't use note repeats, arps, velocity functions etc. Recently, I came across a thread on the NI forums which have workflows to get this working in Live, Reaper & DP. https://www.native-instruments.com/forum/threads/send-notes-to-daw-using-maschines-pads-without-midi-mode.336443/ I tested this on Live and it works really well. Once you setup Live to see the MIDI coming in from Maschine you can record all your parts straight into Live and use it's MIDI functions. No one has figured out how to do this on Logic yet or if it's even possible. While running the Maschine AU plugin, playing the pads don't show any MIDI input being received on the MIDI monitor. Is this a limitation of working with AUi? Not sure if this has to be implemented by the Logic team or NI. How can I get Logic to see the MIDI note messages being sent from the Maschine pads? Is some Environment hack possible to get this to work? The link I posted above also mentions that even Reaper doesn't see MIDI information coming in, but it still works. Any Logic/environment experts want to take a crack at this?
×
×
  • Create New...