Jump to content

Zillion

Member
  • Posts

    35
  • Joined

  • Last visited

Zillion's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Fellow Logicians, I’ve just acquired a 2018 MacBook Pro so that I can access Logic 10.7 projects in Big Sur. My 2016 MBP is on High Sierra and Logic 10.4.8, and frankly it works like a dream so I want to keep it in ‘stasis’! What’s now the best way to load Logic (10.7) on the new MBP, complete with my custom default settings from my old version (10.4.8) on my old MBP? Is Migration Assistant now more reliable? Or should I just Clean Install and manually compare & adjust between the old and new Logic versions? Fwiw, my sound library, plugins and samples are stored on an external SSD. All projects are also stored on various external SSDs. Big thanks for your experience and advice!
  2. Wow, aren't those OWC hubs brilliant - great shout! Yes, how to ease into this new M1 world... My instinct still wants to separate out the machine itself from all the peripheral stuff (like screen, keyboard, mouse), because I already have more ergonomic solutions to those things, and I want to keep all accompanying external SSDs out of the way of damage. Given that travelling isn't what it was, the Mac mini M1 feels like the rig to embrace. And if being mobile becomes a requirement again at a later date, I could probably justify a basic Air with the savings from the mini. I really appreciate being able to sound this out with you all!
  3. Yep, dual core. According to the System Report: Number of Processors: 1 Total Number of Cores: 2 L2 Cache (per Core): 256 KB L3 Cache: 3 MB Basic by current standards. And yet it works like a dream. Go figure. Must be the perfect intersection of macOS, Logic version, and workflow. But yep, I think you're right, triplets re. a new Mac - I'm just bracing myself for the outlay (£££). I prefer the 'modular' (and cheaper) approach of the Mac mini but my work-travel commitments mean that I need the more encompassing solution of a laptop. I'm looking at the MacBook Pros now (they're all M1)... Even the most basic 13" would suffice tbh. I have additional screens at home etc. But the issue is then how to deal with having so few ports? Some kind of Thunderbolt hub contraption? God, I miss the days when Mac supplied us with a bounty of port requirements!
  4. Thank you for your responses - that's very helpful and much appreciated. So I'm at the very limit of my LPX versions. OK, that makes sense re. the OS update but damn, that'd be quite a leap forward in OS. I'm not sure my humble MBP has the processing to make that jump. Intel Core i5, 2.7 GHz, 8GB memory - amazing it even still works as smoothly as it does (FWIW it probably helps that I'm a bit old school and always bounce to audio wherever possible and deliberately limit my track count, but still). Is this where I either have to take the plunge on an OS update or a machine update...?
  5. Dear Logicians, I currently use Logic 10.4.8 on my 2016 Mac OS High Sierra 10.13.6. Both of these versions are - or are close enough to - the native softwares my Mac came with. Logic runs like a dream, I use it for critical projects, and my livelihood essentially relies on it. Until now, clients have been able to send me their Logic projects and, regardless of their version, I've been able to open at my end and keep working. This is especially useful for vocal sessions where I will remotely record multiples takes on their machine and then they will send me the project for me to comp, edit, and continue production. The problem is that now some of them have updated to 10.7 and the compatibility has ceased. Am I able to additionally download Logic 10.7 (or any later version than my current 10.4.8 that my OS will manage)? This way I can trial it with existing projects but will still have the failsafe of being able to revert to my prior version if problems arise and persist? Thank you for you time and knowledge.
  6. Good shout - I'll try that, if only to rule out the drive itself.
  7. Yep, TM is always on a dedicated drive. In fact, I spend a small fortune on buying drives as a pair so I always have an exact duplicate SSD for each of my work SSDs, ie the TM drive is effectively a clone of the drive it is backing up. In theory, is it not possible to copy the Library onto each of my work SSDs so that I can always access it from there? And then just TM that SSD as normal?
  8. Library is relocated to that SSD (along with Plugins and Samples folders). That SSD is essentially an extension of my Mac and Logic. I call it my 'Work SSD'. Why would TimeMachining or manually copying the Library to my backup SSD now cause the Work SSD to either dismount or produce an 'Error Code 43'? My thinking re. storage is: - Option 1: once I finish working on a project (eg an album / body of work) on my Work SSD, I copy it from this Work SSD to another SSD which I then also backup. I can then delete it from my Work SSD thereby freeing up space for the next project. - Option 2: Before beginning a new project, I copy my Library, Plugins, and Samples folders from my Work SSD to a new SSD ready for this new project. This way I never have to move and delete the project (plus I don't need to have the Work SSD plugged in). I then backup this SSD. But in both these scenarios, neither TimeMachine nor manual dragging/copying is working with the Library. - In Option 1 I now cannot TimeMachine my Work SSD which hitherto has been fine. Work SSD dismounts. - In Option 2 I cannot copy the Library to a new SSD. Error code 43.
  9. Hey guys, So I'm doing a regular ol' TimeMachine backup of my external SSD which contains folders for my Logic Library, Plugins, and Samples. It also contains the Logic projects I am currently working on. I've named this 'Work SSD' as it's an extension of my Mac and Logic. The TimeMachine backup is also an external SSD and is a straight clone (i.e nothing excluded from the Work SSD). Suddenly the Work SSD dismounts midway. Never done that before. Presumably as a result of TimeMachine itself struggling with something? I try to eliminate the issue by using different ports and cables. I also run Disk Utility's First Aid. I even reformat the backup SSD to try a fresh TimeMachine backup from scratch. The problem still persists. Now I'm getting worried. So I go deeper by trying to manually copy across the folders to see if I can identify the problem area. Everything copies across fine except the Library (which I relocated from my Mac HD a while back to save space). Why is this? Furthermore, why would TimeMachine suddenly stop being able to backup the Library? It's never had a problem before! Can there be only one instance of the Library? To clarify: my intended workflow was/is to have a copy of my Library folder, Plugins folders and Samples folders on each of my work project SSDs to minimise port requirements (otherwise I'll aways need to keep an SSD with all that utility stuff plugged in along with whatever SSD has my work project on). I realise I've asked a lot of questions here, still I would appreciate any clarity on any of this. In our line of work, backup failure is the only thing which gives me the heebie-jeebies!! Thank you so much. I now sit awaiting any response..!
  10. Hey all, I’m reamping a DI guitar recording using a Signal Art ‘AngReAmp’ box (passive) which is sending the signal to my amp to be captured via mic. On my DI guitar channel strip, I’m using the I/O plug-in to configure the Line Out (‘3’ in my case). I’ve also hit ‘Ping’ to check for latency, and I’ve disabled the Stereo Out on the DI guitar channel strip. So far so good: I’m hearing the DI guitar coming out of my amp. But when I hit record to capture this via the mic, Logic is recording my reamped guitar (green in pic) earlier than the DI part (grey in pic). If it were later, I’d understand it re. round trip latency. So is Logic overcompensating for some kind of latency? My recording delay is set to 0 samples and my buffer size is at 1024. These settings are where I’ve always had them and I’ve so far never had any sync issues with mic/instr/line recording. I’m using Logic 10.4.8 with a MBP OS High Sierra 10.13.6 and an Apollo x6. Any guidance to correct this would be wonderful. I’m totally stumped!
  11. Hey all, I’m having exactly the same issue: Logic recording my reamped guitar (green in pic) earlier than the DI part (grey in pic). My recording delay is already set to 0 samples. I’m using Logic 10.4.8 with a MBP OS High Sierra 10.13.6 and an Apollo x6. Any help would be wonderful. Totally stumped!
  12. Hey guys, I have two SSDs which contain separate work on each. I also have a two more matched SSDs to use as a backup for each. For clarity: SSD1 & SSD1 backup | SSD2 & SSD2 backup Am I able to use Time Machine to backup both drives, as-and-when, by simply changing the preferences when I go to backup? Setting up Time Machine to backup SSD1 is fine, but will Time Machine still recognise this setup if I then change preferences to backup SSD2? i.e. will the SSD1 Backup still carry on where it left off when I change preferences back again, or will it try to backup from scratch? Thank you for any your advice on this!
  13. Zillion

    Reset ruler

    Brilliant, thank you both - that's worked. David, is it good practice to start all projects at the 1 1 1 1 bar mark? I tend to start at bar 3 - to give me two bars of wiggle room - but I'm happy to amend this practice if it avoids unexpected behaviours...!
×
×
  • Create New...