![]() So this is another reason to name your machines appropriately, is to navigate the machines well on your network. So it’s pretty easy to get around the network, especially when adding keys, and logging in… Obviously, I tend to use the same username to get in as my personal user, because hey, it’s my name… So I don’t even have to put the username before the thing, because it assumes the username recurrently login as via SSH. So I have a simple system… Similarly to this, you know, a couple Raspberry Pi’s, a Linux box… So those all get named appropriately, but that first part is whatever the machine’s name is, dot home, dot LAN. But that actually matters less when you do DNS… So through Pi-hole, you have the option to do CNAMEs, and DNS, and stuff like that. And like this machine, if I’m outside the network and I’m SSH-ing in, and I wanna get at something on this machine for some reason, I want it to have a dedicated IP. The Linux box I have on the network, it has its own. So I tend to issue static IPs to particular machines I know I’m logging into… So the Raspberry Pi’s, they have their own. And then, because I use Pi-hole on the network too, every machine that has or should have a dedicated IP - so DHCP tends to only issue the same IP, but it can change theoretically through DHCP. And if it exists on your destination but not at your source - because you’re syncing source to destination if you do –delete - it’s going to delete whatever exists on the destination that no longer exists on the source. Whereas rsync, if you use the –delete flag on rsync, it will essentially match your source to your destination. ![]() So if the file doesn’t exist on the old – instead of deleting it, it moves it to a folder that eventually purges itself. ![]() The cool thing about Carbon Copy Cloner is that it gives you a chance to do what they call a safety net. But I’m actually gonna move – instead of using Carbon Copy Cloner, I think I’m gonna do it with a cron job and rsync this time around, versus that. I think like three times a day, every six hours… And the same thing now, same concept. So I would always copy my production drive, essentially, which was that drive, to a different machine, several times a day. But I would Carbon Copy Clone that thing to a separate network drive elsewhere on the network, where essentially I have a RAID setup where – I know RAID is not a backup if you’re listening to this, of course, it’s not a backup, but it’s a secondary copy. It was 4 terabytes, so that’s what made me think four terabytes on these machines would be great, because I never used all that… And I always had plenty to consume. So I have one terabyte of storage, so I had to get an external Thunderbolt 3, which was a super-fast external storage. Same for me, I would say, too… That’s pretty true, because in the iMac scenario I didn’t have enough local storage. And for the M1 Macs it’s just like – so far, it’s been really, really fast. It’s got attached to it, it’s equalized, all that good stuff.īut that process would take quite a while, even for my iMac Pro. It’s got broadcast quality attached to it. You mix those down, it takes all those and munges it into one single wav file, then you take that wav file and you run it through a process called match loudness, that exports an mp3, that’s ready for broadcast, essentially. So we have a process when we do our mixdowns, essentially we have different plugins in place, and it essentially takes all the tracks… In some cases, it’s five to eight tracks per session a session is a project, essentially. So I think I really put that machine through its paces, but… ![]() You don’t wanna hit your threshold right away you wanna have it for five years and enjoy it for five years, and get all you can out of it, and that kind of thing. I think it’s great when you buy a pro machine to buy more than you actually need, because you wanna grow into it. I honestly think I had more RAM than you need. Yeah, I think my machine wasn’t that much of an upgrade, honestly… And I went down RAM-wise, but I think what you have with the single-chip design probably makes up for that, where you don’t need that much RAM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |