WEBVTT
00:00:17.320 --> 00:00:21.620
Hello and welcome to another episode of Inside the Recording Studio.
00:00:22.020 --> 00:00:25.740
I am Jody Whitesides and with me as always is mister Chris Hellstrom.
00:00:25.740 --> 00:00:26.740
How are you today, Chris?
00:00:27.440 --> 00:00:29.980
I'm doing good Jody. I'm doing really well. How about you?
00:00:28.780 --> 00:00:34.120
Great! I'm doing good too. I'm not going to complain about too much. I'm going to do that
00:00:34.260 --> 00:00:45.300
and save that for today's episode. The change has already happened. It's not even that it's
00:00:37.300 --> 00:00:41.080
Yes. Do you feel like there is a change coming for you?
00:00:43.640 --> 00:00:49.280
Yeah. Do you feel like, do you feel like a better man from the journey?
00:00:45.300 --> 00:00:53.940
coming it's already happened no no I do not yes
00:00:50.960 --> 00:00:58.540
No. All right, let's explain shall we both Mac and Windows have new operating systems coming.
00:00:58.880 --> 00:01:06.080
Mac is about to go on from Big Sur to Monterey as the time of recording this episode and Windows
00:01:06.180 --> 00:01:14.160
is about to roll out Windows 11. Yeah, so we thought we would talk today about when should you
00:01:08.040 --> 00:01:08.980
oh boy
00:01:14.240 --> 00:01:20.500
upgrade your operating system on your production system. And fair
00:01:19.200 --> 00:01:20.060
Yes, yes.
00:01:20.580 --> 00:01:25.340
warning to all Windows users out there that this will be a Mac
00:01:25.520 --> 00:01:29.280
centric topic. But a lot of the things that we're talking about
00:01:29.400 --> 00:01:33.520
will be valid for PC or Windows users as well. Some of the
00:01:33.540 --> 00:01:37.860
advice here. So even though we end up talking about Mac, let me
00:01:34.619 --> 00:01:34.780
Let's hope.
00:01:37.900 --> 00:01:41.959
post the question to you, Jody, then right off the bat, new OS
00:01:39.620 --> 00:01:39.920
Oh, huh.
00:01:41.960 --> 00:01:45.800
comes out. Do you jump on it right away? Yes or no?
00:01:46.140 --> 00:01:52.060
Currently? No. No. Years ago? Damn right I did.
00:01:47.560 --> 00:01:54.980
Currently? No. Did you? Yes. Yeah, you were one of the
00:01:55.100 --> 00:02:01.740
early adopters of like when OS 10 came out, you were you were
00:01:57.179 --> 00:02:04.640
Bleeding edge. Oh yeah, I jumped on OS X immediately. Like almost immediately, yes.
00:02:03.160 --> 00:02:07.500
right. Because that was a big change because obviously not
00:02:07.020 --> 00:02:26.480
massive. Yeah, and one of the biggest reasons why I started early on with it was technically
00:02:07.660 --> 00:02:11.940
just the underlying code, but everything the way it looked and
00:02:11.940 --> 00:02:14.920
that plugins and everything had to run was different.
00:02:15.000 --> 00:02:19.060
So that was a sea change when it came to the mac at least.
00:02:19.200 --> 00:02:42.980
right. Yeah.
00:02:26.790 --> 00:02:32.720
almost like giving myself a limitation like having a four track cassette machine, like
00:02:32.780 --> 00:02:37.220
the task and port of one. And the reason for it was, is it got me back to being a bit more
00:02:37.280 --> 00:02:42.960
creative in a sense of like, shit, I don't have my plethora of plugins yet. So I was
00:02:43.060 --> 00:02:47.820
kind of stuck primarily with what came with logic, because that was like really the first
00:02:48.060 --> 00:02:54.160
DAW that went into OS 10. And I had numerous friends that were like, dude, I'm not going
00:02:49.960 --> 00:02:50.240
Yeah.
00:02:54.300 --> 00:02:59.099
off OS nine for as long as I can help it. And I know the main reason why was because
00:02:59.100 --> 00:03:03.960
Because they had tens of thousands of dollars worth of software that was cracked, that they
00:03:02.960 --> 00:03:04.120
Yeah.
00:03:03.960 --> 00:03:08.140
were running, and that they direly needed for their work and they hadn't paid for it.
00:03:08.410 --> 00:03:09.200
And I get that.
00:03:09.920 --> 00:03:12.640
It's not something I condone, but I get it.
00:03:13.180 --> 00:03:19.380
And for me, having gone to OS X early in the game, whenever something new finally arrived
00:03:19.520 --> 00:03:25.739
on OS X, I was able to immediately purchase it and not feel the sting of dropping tens
00:03:25.740 --> 00:03:30.580
of thousands of dollars all at once to get all the plugins again.
00:03:30.100 --> 00:03:34.520
Yeah, there was a time when plugins were a lot more expensive than they are today.
00:03:35.000 --> 00:03:42.420
So yeah, right. Yeah, no, that was a big thing. And I think you've touched on that in, I think
00:03:35.240 --> 00:03:35.780
This is true.
00:03:41.500 --> 00:03:41.900
episodes.
00:03:42.560 --> 00:03:47.300
you you've justified it there. Just like you said, now it was a way to make the migration
00:03:47.420 --> 00:03:53.400
process actually smoother because it wasn't like you said, it wasn't, oh, I have to invest
00:03:53.780 --> 00:03:58.579
huge amount of money to kind of get up and running right off the bat, you know. So that
00:03:58.580 --> 00:04:01.340
That's a big one, you know, but what?
00:03:59.299 --> 00:04:04.400
It is, but that was the last time I was truly, in my mind, bleeding edge.
00:04:05.860 --> 00:04:08.940
Right. So what made you stop doing that?
00:04:09.020 --> 00:04:13.760
Because I've I might have done that around the same time in a similar way.
00:04:13.900 --> 00:04:18.239
But I think I've always been at least a month behind you
00:04:18.820 --> 00:04:19.380
(laughs)
00:04:19.320 --> 00:04:23.000
because I've always like, OK, well, shit goes really side.
00:04:21.579 --> 00:04:23.580
If it worked for him. (laughs)
00:04:23.580 --> 00:04:26.780
Yeah, I can always call George or I can call Jody, right?
00:04:26.820 --> 00:04:28.140
because they're gonna be up on it.
00:04:28.600 --> 00:04:29.660
You know, I'll ask the question again,
00:04:29.780 --> 00:04:31.560
what made you stop doing that?
00:04:31.479 --> 00:04:34.040
It was around the time that,
00:04:34.620 --> 00:04:36.860
might have been around the time of Sierra or High Sierra,
00:04:37.380 --> 00:04:41.860
where I still had the cheese grater Mac Pro that I had.
00:04:37.600 --> 00:04:37.760
Mm.
00:04:41.980 --> 00:04:42.420
Right?
00:04:42.360 --> 00:04:46.240
And I believe that was no longer capable of running
00:04:46.760 --> 00:04:48.580
if it was Sierra or high Sierra.
00:04:48.740 --> 00:04:50.660
I can't recall which OS it was
00:04:50.860 --> 00:04:53.780
that stopped running on the old Mac Pros.
00:04:54.160 --> 00:04:56.940
And then I ended up having to hack the machine
00:04:57.120 --> 00:04:59.640
in order to run the newer OS
00:05:00.320 --> 00:05:03.100
because they were trying to get rid of whatever chip
00:05:00.760 --> 00:05:00.860
Yeah.
00:05:03.260 --> 00:05:03.900
they were running.
00:05:04.960 --> 00:05:06.579
And that's when I kind of stopped
00:05:06.580 --> 00:05:08.580
because that became a major pain in the ass.
00:05:09.300 --> 00:05:14.620
Then that machine died unmercifully in a power surge
00:05:15.100 --> 00:05:19.380
through battery protected backup system, the APS.
00:05:18.500 --> 00:05:20.060
Oh, yeah, remember that.
00:05:20.090 --> 00:05:20.920
Yeah, that was brutal.
00:05:20.120 --> 00:05:23.220
A gigantic storm that had a surge of electricity
00:05:23.660 --> 00:05:25.240
that just it fried everything.
00:05:25.960 --> 00:05:27.580
And that was unfortunate.
00:05:28.180 --> 00:05:30.200
So I ended up getting a new machine that was capable
00:05:30.240 --> 00:05:32.040
of running the OSes with no issue.
00:05:32.720 --> 00:05:36.160
It was easier to kind of stay up to date.
00:05:36.640 --> 00:05:39.060
However, in the last couple of years,
00:05:39.680 --> 00:05:41.840
developers are having a harder time keeping up.
00:05:41.860 --> 00:05:42.460
Yeah.
00:05:42.460 --> 00:05:47.620
Yeah. No, there have been some, some drastic changes on the OS level here with not only
00:05:47.740 --> 00:05:54.340
the implementation of finally just going like 64 bit some while ago, right? Then how with
00:05:54.340 --> 00:05:58.760
the new M1 chips and all this kind of stuff. So there are these hurdles now for them to
00:05:58.800 --> 00:06:03.720
kind of overcome. You know, you brought up a lot of points there that we're actually
00:05:59.880 --> 00:06:00.480
Yes.
00:06:00.720 --> 00:06:03.040
Okay.
00:06:03.770 --> 00:06:09.180
going to talk about. So let's take a step back and say, well, what would be the pros
00:06:09.180 --> 00:06:15.500
and cons of immediately wanting the new OS. And the first one I can think of, and I can
00:06:15.540 --> 00:06:21.460
relate to, is people want the newest, shiniest thing. Right? So, oh, yeah, this is awesome.
00:06:20.780 --> 00:06:22.180
Sure.
00:06:21.880 --> 00:06:27.920
You know, it that I mean, that appeals to us on a very human level, I suppose. Right?
00:06:28.440 --> 00:06:32.600
Well, it's like, oh, yeah, I got, yeah, I'm not slumming it to OS is ago. What's wrong
00:06:32.600 --> 00:06:33.980
with you type of thing, right?
00:06:33.639 --> 00:06:41.020
Yeah, I for me, I don't know if I necessarily care about the newest look or the shiniest
00:06:41.240 --> 00:06:41.840
toy in that regard.
00:06:42.360 --> 00:06:45.980
I'm more about what extra functionality am I getting?
00:06:46.460 --> 00:06:51.560
I'm not saying I agree without mindset, I'm just saying that that's a reality. I mean, there are people
00:06:46.660 --> 00:06:47.560
That's the biggest thing.
00:06:48.720 --> 00:06:48.960
Right.
00:06:52.600 --> 00:06:58.680
that I know on certain music boards and things that they're just like, yeah, I'm jumping in with both feet.
00:06:58.720 --> 00:07:04.860
I don't care. I'm going for it and see what works or not. People that even download the public
00:07:05.180 --> 00:07:14.380
bait is and things like that. Yeah. No, I'm not that brave. Yeah, right. Yeah. Yeah.
00:07:05.720 --> 00:07:08.780
Yeah, I don't do that anymore.
00:07:09.520 --> 00:07:12.180
I prefer to get paid for my beta testing, damn it.
00:07:13.800 --> 00:07:18.899
And I still feel like I'm beta testing shit even though I'm not getting paid for testing
00:07:18.900 --> 00:07:20.700
OS's anymore.
00:07:21.800 --> 00:07:27.999
And if you are, you know, if that's your income, that's your line of work. It's time that you don't
00:07:28.000 --> 00:07:33.460
have you can't afford to spend doing that kind of stuff. So I think that's why a lot of people
00:07:33.940 --> 00:07:39.280
who are in this business tend to not stay on the bleeding edge because, again, you got a working
00:07:39.540 --> 00:07:46.280
solid system, there's no reason to upgrade the other thing unless there's drastic added functionality.
00:07:42.080 --> 00:07:43.480
Right.
00:07:43.480 --> 00:07:43.600
Right.
00:07:47.060 --> 00:07:52.960
Right. Which sometimes it can be, but I think a little bit less so perhaps on the OS level,
00:07:53.520 --> 00:08:00.640
at least from my perspective when it comes to music applications. But when Apple actually rolled
00:08:00.920 --> 00:08:05.760
out the AU format, that was part of the operating system and that was a big thing that it was,
00:08:06.000 --> 00:08:11.280
yeah, we're going to be able to run music plugins on an operating system level type of thing.
00:08:11.199 --> 00:08:13.460
So what are some of the cons of upgrading?
00:08:13.460 --> 00:08:14.080
too soon.
00:08:14.480 --> 00:08:21.039
What conflicts primarily, right, where it could be, like you mentioned, plugins that are no longer
00:08:21.040 --> 00:08:24.300
compatible, right, that you rely on, and then you'll have to
00:08:24.340 --> 00:08:27.320
decide that if there is such a big part of your workflow that
00:08:27.380 --> 00:08:30.520
you need them, well, I would strongly suggest not upgrading
00:08:30.660 --> 00:08:34.780
yet, and waiting until they are or if they ever will become
00:08:35.460 --> 00:08:43.599
compatible. So yeah, it because that was the thing with
00:08:36.380 --> 00:08:40.880
That's a big key right there, whether or not they'll ever be upgraded.
00:08:43.860 --> 00:08:48.159
obviously this shift from 32 to 64. And we had sort of like
00:08:48.160 --> 00:08:53.660
patches for that was that it was 32 lives at one point, right? There was like a wrapper
00:08:53.730 --> 00:08:57.960
of sorts, I believe, that allowed you to do it. But then at some point also that went,
00:08:58.400 --> 00:09:03.640
you know, tits up and didn't work anymore. So there are those things and even on the
00:09:03.680 --> 00:09:08.820
hardware level, right, just compatibility, like there's software that you rely on in
00:09:08.880 --> 00:09:14.679
your day to day work, make sure it's compatible before you take the plunge. Developers are
00:09:14.680 --> 00:09:19.440
usually pretty good at that. And they even send out mailers like I got one from Slate
00:09:19.700 --> 00:09:24.580
just this week and say, Hey, don't upgrade to Monterey yet. You know, we're working on
00:09:24.580 --> 00:09:28.340
it again as fast as possible. But I think everybody kind of does that. If you want to
00:09:28.360 --> 00:09:37.820
be on the bleeding edge, maybe you're going to get cut sometimes, right? Yeah. Right.
00:09:31.660 --> 00:09:35.020
You mentioned real briefly their hardware and then you went right back to software.
00:09:35.300 --> 00:09:36.880
So hardware conflicts.
00:09:37.480 --> 00:09:40.900
Let's say that in my example where the computer got fried
00:09:41.020 --> 00:09:43.960
and I had to get a new machine, my old audio interface
00:09:44.180 --> 00:09:46.160
no longer interfaced with the new computer.
00:09:46.440 --> 00:09:50.240
I had to get an audio interface upgrade, so to speak,
00:09:50.480 --> 00:09:51.720
along with the new computer.
00:09:50.860 --> 00:10:05.740
Yeah. Yeah. I had that happen. It was an older piece of kit
00:09:52.240 --> 00:09:53.700
You have gone through the problem
00:09:54.140 --> 00:09:58.380
of having an audio interface that was no longer compatible
00:09:58.640 --> 00:10:02.420
due to its drivers when you updated to a certain OS.
00:10:05.960 --> 00:10:09.280
fully functional, work great. I love the converters and all this
00:10:09.420 --> 00:10:15.140
kind of stuff. But it was an older piece of hardware. The
00:10:15.140 --> 00:10:21.040
newer versions of said interface. And we're no longer supporting it with the older drivers
00:10:21.240 --> 00:10:26.940
for that. It's like it's legacy software. It just, well, that's the reality of the situation
00:10:22.020 --> 00:10:23.620
Those rat bastards!
00:10:27.020 --> 00:10:27.500
Of course.
00:10:27.080 --> 00:10:32.460
though, right? You know, whether it's a driver issue or, you know, a connectivity thing,
00:10:32.700 --> 00:10:44.200
you know, Firewire 400 has gone away, even 800 has gone away. PCIe slot, right? Yeah,
00:10:38.000 --> 00:10:38.060
Right.
00:10:38.280 --> 00:10:42.720
Well, that was my reasoning for having to get the new interface is that the port no longer
00:10:42.820 --> 00:10:43.160
existed.
00:10:44.540 --> 00:10:48.600
So you can deal with dongles and things like that, but I think you're possibly just kicking
00:10:48.760 --> 00:10:50.300
the can further down the road, right?
00:10:50.460 --> 00:10:55.180
Because there will inevitably be something that that's not going to work anymore, right?
00:10:55.250 --> 00:10:59.460
Or there will be conflicts that just make it pain to kind of work with.
00:10:59.700 --> 00:11:00.980
[laughs]
00:10:59.960 --> 00:11:01.120
I ended up with an update.
00:11:01.340 --> 00:11:07.200
I had to get a new interface and I could eventually move on from the OS I was on, because I was
00:11:07.240 --> 00:11:09.280
starting to use other software as well.
00:11:10.020 --> 00:11:17.480
in true Apple fashion, that was only going to work on a certain OS forward.
00:11:18.260 --> 00:11:23.700
Right? So it was like, okay, well, all right. And then you upgrade, and then you
00:11:23.700 --> 00:11:29.020
have to decide what which one weighs out or what wins out. Do you go with a
00:11:29.040 --> 00:11:32.960
newer functionality and upgrade some hardware or are you really satisfied with
00:11:33.040 --> 00:11:37.340
what you have and keep working on that until you're not anymore? And then you
00:11:37.340 --> 00:11:42.780
have to do it. So conflicts are something that we have to be aware of. You and I have talked about
00:11:42.780 --> 00:11:48.780
it before and you might even mention on the podcast, but when the latest Mac Pros came out,
00:11:49.220 --> 00:11:49.740
Yeah.
00:11:49.560 --> 00:11:54.300
these monster machines that could cost as much of a house in certain parts of the country,
00:11:49.860 --> 00:11:50.000
is.
00:11:54.570 --> 00:12:01.100
if you max them out, are now going to not be able to run. I think it's on whatever is going to come
00:12:01.220 --> 00:12:06.640
after Monterey, I think is not going to be able to run the latest OS anymore.
00:12:07.380 --> 00:12:12.020
be careful. I think so. And we'll see even with all the universal
00:12:07.620 --> 00:12:09.080
That's the understanding that I have.
00:12:12.100 --> 00:12:15.020
bind reasons, top is good. Nope, it's going to be just m one and
00:12:15.060 --> 00:12:21.760
forward, right? So you have to there you go. Thank you. Yeah.
00:12:16.620 --> 00:12:19.500
Yep, Apple Silicon going forward.
00:12:22.740 --> 00:12:26.640
So yeah, compatibility, that that's, that's the big one. And as
00:12:26.680 --> 00:12:30.000
always, it can, you know, you mentioned drivers and things.
00:12:30.160 --> 00:12:33.540
And that one of the pros is obviously like possible bug
00:12:33.540 --> 00:12:40.160
fixes, but it can also create new bugs. Right. So functionality that you yeah, that I would
00:12:36.540 --> 00:12:38.700
Yes, big con right there.
00:12:40.200 --> 00:12:44.440
say so. Absolutely. So these are things that you have to put in mind.
00:12:44.920 --> 00:12:48.360
Before we move on to the next section here in the podcast, let's just take a word from
00:12:48.420 --> 00:12:48.880
our sponsors.
00:12:51.040 --> 00:12:51.560
And we're back.
00:12:52.000 --> 00:12:53.220
What are we talking about now, Chris?
00:12:53.880 --> 00:13:03.520
Well, the next thing that we're going to talk about is, are you working on a solid system? And
00:13:03.520 --> 00:13:03.840
on that
00:13:04.500 --> 00:13:10.740
Because my recent experience has been made with doing an upgrade as of like a week and
00:13:10.740 --> 00:13:16.240
a half ago, it came down to, yes, I did have a working solid system.
00:13:16.460 --> 00:13:25.920
However, due to the ecosystem that I was in, certain problems arose when a couple of devices
00:13:19.459 --> 00:13:20.860
Yeah.
00:13:26.180 --> 00:13:30.040
were updated to the latest OS and a couple of them were not.
00:13:30.420 --> 00:13:31.720
And then there were software conflicts.
00:13:32.440 --> 00:13:38.820
And of course, the big tech company was like, not talking about it is the best way to put
00:13:38.880 --> 00:13:39.000
it.
00:13:39.840 --> 00:13:47.220
And their answer after spending hours beta testing, so to speak, came back saying, we
00:13:43.060 --> 00:13:44.460
Yeah.
00:13:47.300 --> 00:13:49.740
know about this, we're not talking about it.
00:13:50.040 --> 00:13:54.260
If it's a problem for you, tough shit is essentially what the answer was.
00:13:52.740 --> 00:13:53.080
Yeah.
00:13:54.800 --> 00:13:57.140
And that's the big middle finger that Apple will give you.
00:13:57.340 --> 00:14:02.580
At that point, I had to heavily weigh, do I upgrade the OS on the other devices in order
00:14:02.680 --> 00:14:06.760
to get rid of this conflict because it's going to drive me out of my mind, even though
00:14:06.240 --> 00:14:06.480
Yeah.
00:14:06.760 --> 00:14:08.100
I had a solid working system?
00:14:08.470 --> 00:14:13.340
The answer to that question was, after doing a software check of everything that I use
00:14:13.890 --> 00:14:19.360
and making the determination of if there's anything I'm using that isn't compatible,
00:14:19.590 --> 00:14:21.880
do I wish to continue using it going forward?
00:14:22.620 --> 00:14:26.440
And after weighing that all out, it was like, fuck it, I'm going for the upgrade.
00:14:22.660 --> 00:14:22.900
Yeah.
00:14:26.940 --> 00:14:32.380
Because literally like 98% of everything was there to work in Big Sur.
00:14:32.760 --> 00:14:37.220
And this is what a year, almost a year after Big Sur was released.
00:14:37.880 --> 00:14:39.460
I finally upgraded to Big Sur.
00:14:38.100 --> 00:14:43.680
Yeah, I mean, yeah, I mean, they're rolling them out every year now, right?
00:14:43.020 --> 00:14:44.320
Well, they always have.
00:14:43.780 --> 00:14:50.160
Every year, I guess, but it felt like it was more, and this might be just, you know, selective
00:14:50.160 --> 00:14:54.380
memory, but it felt like it was more of incremental changes in
00:14:54.440 --> 00:14:57.460
the past. But has it really been I mean, after it rolled into
00:14:57.540 --> 00:15:05.760
10? Was it really every year that something new came out? I must
00:15:00.760 --> 00:15:01.120
Pretty much.
00:15:01.240 --> 00:15:04.800
They've done a new OS literally just about every year.
00:15:05.900 --> 00:15:09.260
have selective memory because I, it feels like they've sped them
00:15:09.400 --> 00:15:11.480
up. But maybe it's just because I'm paying attention to it more.
00:15:12.580 --> 00:15:14.280
I don't know. Yeah.
00:15:13.099 --> 00:15:13.260
Maybe.
00:15:14.220 --> 00:15:19.940
So that was me waiting almost a year to go to Big Sur and now they're announcing Monterey.
00:15:20.000 --> 00:15:20.960
It's like, oh, good God.
00:15:21.050 --> 00:15:24.680
But I'm thinking that the difference between Big Sur and Monterey is going to be a lot
00:15:24.720 --> 00:15:29.340
more minimal, which means I'll probably be upgrading to Monterey sooner than a year.
00:15:30.040 --> 00:15:30.340
We'll see.
00:15:30.880 --> 00:15:36.420
Yeah, it seems like the big shift has possibly been done with, you know, Apple Silicon, right?
00:15:35.960 --> 00:15:37.440
There is one more big shift.
00:15:36.440 --> 00:15:42.940
And that, yeah, there is no Intel chips, like you have an Intel chip chip.
00:15:37.490 --> 00:15:39.340
It comes after Monterey.
00:15:43.100 --> 00:15:45.400
Yeah, sorry. You're locked out.
00:15:43.980 --> 00:15:48.000
out of luck. So Monterey is the EOL of my machines that I currently have.
00:15:48.120 --> 00:15:52.080
And then of course, in about a year, I'm going to have to consider upgrading to
00:15:52.420 --> 00:15:55.860
Apple Silicon. And it's the same sort of thing that's kind of happening right now.
00:15:55.940 --> 00:16:00.400
Also with the people that run Windows, because apparently it's a really massive
00:16:00.700 --> 00:16:03.140
jump to go from Windows 10 to Windows 11.
00:16:03.099 --> 00:16:03.560
Yeah.
00:16:03.840 --> 00:16:07.120
And people are talking about whether the hardware will work with it.
00:16:07.360 --> 00:16:10.080
I actually just read an article this morning. If I'm not mistaken,
00:16:10.220 --> 00:16:14.240
somebody got Windows 11 to run on like a 10 year old PC.
00:16:15.180 --> 00:16:16.840
And I was kind of like, well, that's impressive.
00:16:17.020 --> 00:16:20.900
And I think that's the whole point of the article is just like, yes, we did it.
00:16:21.440 --> 00:16:23.300
But how effective is it in doing that?
00:16:23.380 --> 00:16:23.920
You don't know.
00:16:24.580 --> 00:16:31.420
Kudos to Microsoft then, I suppose, but that is one of the things that is different and
00:16:31.700 --> 00:16:40.100
you could see it as a pro or con, but because Apple in the Mac is a closed ecosystem, they
00:16:40.100 --> 00:16:48.260
can control obviously the entire ecosystem, whereas on the window side, it is much wider. So they have
00:16:40.880 --> 00:16:57.360
Well, the other thing too to think about with Windows is they're still going on with Intel
00:16:48.400 --> 00:16:53.620
all these other parameters to kind of consider or not consider, right? So,
00:16:57.660 --> 00:16:58.940
Nothing's changing there.
00:16:59.160 --> 00:17:05.860
well, there is that as well. But I'm saying just from an operating system standpoint, they can seem
00:17:05.860 --> 00:17:11.240
possibly less ruthless with what they support anymore. But that's
00:17:10.159 --> 00:17:10.760
Mm-hmm.
00:17:11.360 --> 00:17:16.819
something that Apple has done. I mean, forever. And the, yeah,
00:17:14.159 --> 00:17:15.880
They've always been ruthless.
00:17:16.459 --> 00:17:17.120
[laughs]
00:17:17.020 --> 00:17:20.220
and it could be I mean, I remember again, I'm really dating
00:17:20.339 --> 00:17:22.939
myself here. But I remember when they came out, I think it was
00:17:23.040 --> 00:17:26.800
the when they went to the G three, and they said like, Yeah,
00:17:26.880 --> 00:17:29.920
we're not going to have floppy disks anymore. And like, what
00:17:28.780 --> 00:17:28.940
Hmm.
00:17:30.060 --> 00:17:35.840
what? But it's like, yeah, and now it's like floppy disks. What
00:17:30.340 --> 00:17:32.400
Everybody freaks out.
00:17:35.840 --> 00:17:40.740
on that and they did the same with the scuzzy connection and later on with
00:17:40.920 --> 00:17:45.760
firewire 400 800 so they can draw these sort of like hard lines in the sand like
00:17:46.200 --> 00:17:49.660
we're not going to support those anymore because they have that the entire
00:17:49.920 --> 00:17:54.700
ecosystem sort of contained whether you think that's good or bad that's up for
00:17:54.900 --> 00:17:55.760
debate I suppose
00:17:54.960 --> 00:17:56.360
Right.
00:17:56.360 --> 00:18:00.880
The takeaway is that when you have a solid system, if it's not tied to the internet,
00:18:01.040 --> 00:18:04.480
generally speaking, you're probably not going to worry about doing that upgrade because
00:18:04.960 --> 00:18:12.960
the system works and you're good. However, there are times where it's incredibly stupid to pick a
00:18:06.780 --> 00:18:06.880
Yeah.
00:18:06.880 --> 00:18:07.040
Yeah.
00:18:13.020 --> 00:18:17.720
point to upgrade an OS on a machine, and that is when you're in the middle of a giant project.
00:18:18.120 --> 00:18:19.200
Oh God, yes.
00:18:18.460 --> 00:18:23.880
Unless your machine dies, it's incredibly stupid to upgrade right in the middle of a project.
00:18:24.520 --> 00:18:29.500
Pick a point in time where you're going to have downtime in order to do it.
00:18:24.640 --> 00:18:25.120
Yeah.
00:18:29.760 --> 00:18:35.600
Or simply take the downtime and go, I will not be able to take on any work from this and this date.
00:18:35.600 --> 00:18:40.920
So you know that this is set aside to do the hardware and the software upgrades that you might want to do
00:18:41.300 --> 00:18:44.000
Yes, that's the wise way of doing it.
00:18:43.760 --> 00:18:44.640
you I
00:18:44.740 --> 00:18:50.160
See that again, and it's not like it's necessarily reflective of the real world
00:18:50.380 --> 00:18:55.540
But people are complaining like well, I was in the middle of mixing this project and now my plugins don't work
00:18:55.840 --> 00:19:01.580
Well, what'd you do? Well, I upgraded something. Well, why did you do that? You know, it is
00:18:55.920 --> 00:18:56.120
Oops.
00:18:56.120 --> 00:18:56.220
Oops.
00:18:58.540 --> 00:18:59.020
(laughs)
00:19:02.540 --> 00:19:05.580
alarmingly common I think and it
00:19:04.180 --> 00:19:05.940
Oh yeah, people don't think about it.
00:19:05.980 --> 00:19:10.680
I mean, you probably shouldn't mention the name, but it was a friend and
00:19:10.720 --> 00:19:15.820
collaborator of yours that just had a similar experience, right? And it had to
00:19:13.360 --> 00:19:14.520
About a year ago, yeah.
00:19:15.840 --> 00:19:22.520
do with OSs, right? Yeah, and yeah, again, if you're in the middle
00:19:17.700 --> 00:19:18.140
It did.
00:19:22.640 --> 00:19:27.600
of a project, don't upgrade. If there's a plugin update that promises to fix
00:19:27.800 --> 00:19:31.620
something you have an issue with, that might be a different story, but don't
00:19:31.620 --> 00:19:38.740
upgrade just for the upgrade sake of it. It is never strong word, but I would say it would never
00:19:39.120 --> 00:19:41.040
work out the way that you're hoping it will.
00:19:41.200 --> 00:19:46.480
Even if you're ready to do it, there's times when it doesn't work out the way you hope it would.
00:19:46.020 --> 00:19:50.100
Yes. Yeah, this is something you want to get off your chest here.
00:19:47.300 --> 00:19:47.740
(laughs)
00:19:50.300 --> 00:19:50.700
Yes.
00:19:51.940 --> 00:19:53.800
I'm gonna touch on this since we're talking about
00:19:53.520 --> 00:19:54.760
Yeah, you should. You should.
00:19:53.960 --> 00:19:55.300
affecting the workflow and whatnot.
00:19:55.860 --> 00:19:57.880
I made that choice and I figured, okay,
00:19:58.020 --> 00:20:01.000
I've got this span of time from a Thursday to a Tuesday
00:20:01.380 --> 00:20:02.900
where I can make this happen.
00:20:03.160 --> 00:20:04.720
And I did that jump to Big Sur.
00:20:05.400 --> 00:20:08.860
My first experience of doing it is something
00:20:09.020 --> 00:20:11.380
that I tend to recommend, especially when it's a big
00:20:11.520 --> 00:20:14.500
OS change like it was from Catalina to Big Sur,
00:20:14.620 --> 00:20:18.320
which it will be from Monterey to whatever the next OS is for Apple.
00:20:18.900 --> 00:20:23.100
And essentially what it is right now with Windows 10 going to Windows 11,
00:20:23.220 --> 00:20:27.060
from what I understand. And that is I wiped the machine clean.
00:20:27.700 --> 00:20:32.620
And I start with a fresh install of the OS and I'm porting over literally
00:20:28.200 --> 00:20:28.360
Yeah.
00:20:33.100 --> 00:20:37.480
whatever documents. Of course I've made a giant backup in order to do that.
00:20:37.060 --> 00:20:40.280
Yeah, I was just going to say, make sure that you get that out there, that you make it a
00:20:40.280 --> 00:20:58.160
backup of the working system to a separate drive. Yeah.
00:20:42.180 --> 00:20:44.780
And I do have that backup sitting on a RAID system
00:20:44.920 --> 00:20:47.420
so that if even one of the RAID drives dies,
00:20:48.060 --> 00:20:50.560
I still have the backup and I can stick another RAID drive
00:20:50.640 --> 00:20:52.660
in there and it recreates itself and it's all good.
00:20:53.200 --> 00:20:56.820
I do do massive backups whenever something big like that
00:20:56.880 --> 00:20:59.440
happens so that I can run it.
00:20:59.540 --> 00:21:02.680
In addition to that, I also set up a virtual machine
00:21:03.400 --> 00:21:06.260
to run that system, which is something I've never done
00:21:06.300 --> 00:21:07.960
before, it's the first time I've ever done that.
00:21:08.720 --> 00:21:10.520
So I did that as well, I did two things.
00:21:10.620 --> 00:21:15.440
I did a major backup and then I created a virtual machine that could still run that
00:21:15.500 --> 00:21:17.300
machine from the new OS.
00:21:17.880 --> 00:21:19.820
Now I wiped the machine clean.
00:21:20.360 --> 00:21:21.240
I did an install.
00:21:22.020 --> 00:21:28.380
The new OS did something funky in the disk management system that I had never
00:21:28.580 --> 00:21:31.380
seen before, and it split my hard drive in two.
00:21:31.820 --> 00:21:32.240
Oops
00:21:33.200 --> 00:21:37.180
It isn't technically, apparently it's not an oops, it's meant to do this, but
00:21:37.180 --> 00:21:42.820
it renamed it the same thing with the same name, but with an extension on the other name,
00:21:42.720 --> 00:21:45.040
Oh, that would yeah, that would
00:21:43.100 --> 00:21:46.940
which didn't make sense to me. And I booted up, I had problems going on, and all of a
00:21:46.960 --> 00:21:52.500
sudden I go back into the ability to deal with the OS on a non-computer level, so to
00:21:52.520 --> 00:21:58.940
speak, from the user situation. And I delete the extra drive and try to boot again, thinking
00:21:59.060 --> 00:22:03.960
that that was creating the problem. And that hosed the machine completely. Now I'm freaking
00:22:03.320 --> 00:22:03.640
Ach.
00:22:03.960 --> 00:22:08.860
out because the machine won't boot. And eventually I got the machine back into what they call
00:22:08.900 --> 00:22:15.740
recovery mode and tried to wipe it again and reinstall the OS. And instead of allowing me to do the
00:22:15.780 --> 00:22:22.460
latest and greatest in Big Sur for the Mac Pro that I have, it took me back to Yosemite, which is the
00:22:22.760 --> 00:22:29.360
OS that came with the machine. And then I had to install Yosemite. Once I got that back up,
00:22:22.880 --> 00:22:25.680
Oh wow
00:22:29.400 --> 00:22:34.940
Then I go back into recovery mode again and then it allowed me to wipe it again and put on Big Sur.
00:22:35.300 --> 00:22:41.020
That is not to say that it hasn't been problematic. Now that I've had Big Sur and I've installed all
00:22:41.020 --> 00:22:45.260
the software and everything, I still have little weird things happening. I've been dealing with
00:22:45.390 --> 00:22:51.900
Apple for hours on these little things and they can't figure it out. Even after big data dumps,
00:22:51.960 --> 00:22:58.760
they've got senior engineers working on it. And my understanding is it probably come Monday
00:22:58.760 --> 00:23:00.820
of next week, they will tell me,
00:23:00.990 --> 00:23:02.680
"You need to reinstall the system again."
00:23:02.880 --> 00:23:06.480
At which point I'm gonna just be like, "Shit!"
00:23:06.560 --> 00:23:08.160
However, the good thing is,
00:23:08.240 --> 00:23:10.040
is I won't have to reinstall all the software,
00:23:10.280 --> 00:23:11.960
being that it's already on the OS,
00:23:12.140 --> 00:23:15.100
it can allow for a clean install over the OS
00:23:15.170 --> 00:23:17.540
and keep all the data, so that's what I plan on doing.
00:23:18.780 --> 00:23:19.600
When I get told that.
00:23:20.000 --> 00:23:20.760
Hmm.
00:23:20.480 --> 00:23:23.220
So, it was not as smooth as I had hoped,
00:23:23.360 --> 00:23:27.540
it was probably the least smooth OS upgrade I've ever had.
00:23:27.760 --> 00:23:33.620
I generally have not had problems like that when I've gone for a clean install of an OS.
00:23:28.260 --> 00:23:28.740
And do you think?
00:23:33.800 --> 00:23:39.580
It's usually just you install it, you install your software, you pull your documents that you want back
00:23:39.760 --> 00:23:44.400
off of your backups onto your computer and you're good to go. This is the first time where that's
00:23:44.500 --> 00:23:54.440
not happened and it's a little frustrating. I did make the backups. I did make a virtual machine.
00:23:46.620 --> 00:23:50.700
Sure. Incredibly frustrating, no matter what kind of issues arise.
00:23:50.700 --> 00:23:50.960
eyes.
00:23:55.120 --> 00:23:59.500
I could technically go back, although I'm not going to, because there were other things with
00:23:59.530 --> 00:24:04.060
the updates of other devices that caused me to really rethink of like, hey, I need to do this
00:24:04.140 --> 00:24:10.840
going forward. Plus, there was a recent update in addition to all of this with the main DAW that I
00:24:10.900 --> 00:24:16.920
use for tracking and sometimes mixing, because now I'm switching it off between two different DAWs.
00:24:12.500 --> 00:24:12.720
Yeah.
00:24:17.320 --> 00:24:23.680
And they've added functionality to logic that apparently you can't upgrade to because you're
00:24:20.140 --> 00:24:30.400
Yeah. Right. Yeah. I'm on Catalina. You know, it shouldn't be taken necessarily as an indicative,
00:24:23.680 --> 00:24:27.500
not running big sir yet yet.
00:24:30.740 --> 00:24:36.320
but you and I being as close as we are in hearing your war stories there, I am not tempted
00:24:36.320 --> 00:24:42.020
at all to go to Big Sur until I get the chance. That, of course, is not to say that I will
00:24:42.080 --> 00:24:50.120
have the same issues doing that. So anybody listening, don't let that sway too much. It's
00:24:48.840 --> 00:24:50.240
Yes.
00:24:50.120 --> 00:24:53.380
And, you know, things that you want to take into consideration.
00:24:54.100 --> 00:24:59.980
If you're relying on your system for your living, then, yeah, be a little hesitant,
00:25:00.340 --> 00:25:05.240
check out user groups, and wait a while, you know, unless you're, you know, one of those
00:25:05.300 --> 00:25:09.400
people that you like to carry a sword in one hand and a torch in the other and just, "Let's
00:25:09.160 --> 00:25:14.820
Well, and I generally like to do that. It's just that this wasn't the most pleasant experience,
00:25:09.500 --> 00:25:10.920
go, let's do this," you know?
00:25:15.020 --> 00:25:19.400
and I'm still kind of dealing with it even after a week and a half, which is not to say
00:25:19.400 --> 00:25:23.600
that I'm not working, I'm back to working. It's just there's little functionality things
00:25:23.720 --> 00:25:30.260
that may require me to actually install the OS yet again, which is a drag, but I'm not
00:25:27.740 --> 00:25:29.140
Yeah.
00:25:29.140 --> 00:25:29.260
Yeah.
00:25:30.320 --> 00:25:35.760
against it. And the bigger thing, I know that you're not one of those people to constantly
00:25:35.940 --> 00:25:41.500
wipe your machine and start fresh. I am. I feel like it's just because the new OS is
00:25:37.260 --> 00:25:39.140
No, no, I'm not.
00:25:39.400 --> 00:25:39.580
Yeah.
00:25:41.580 --> 00:25:48.240
probably going to have weird anomalies with the old OS, that kind of thing. So me having
00:25:48.240 --> 00:25:53.380
problems having upgraded want to clean machine is a little strange.
00:25:54.039 --> 00:25:55.360
You know, I can see the point
00:25:55.500 --> 00:25:57.360
'cause I've had both experiences.
00:25:57.540 --> 00:26:02.820
I've had cases where just doing the upgrade has been absolutely fine.
00:26:03.840 --> 00:26:08.320
But then in my experience, it's been also that, you know, you do that
00:26:08.700 --> 00:26:10.620
twice, maybe even a third time.
00:26:11.400 --> 00:26:13.240
And then weird things start happening.
00:26:13.440 --> 00:26:19.040
I had that happen when I made the jump to Mojave.
00:26:19.660 --> 00:26:23.480
And it's like, yeah, it slowed my system down to a crawl.
00:26:23.640 --> 00:26:25.480
It was like, this is not happening.
00:26:25.900 --> 00:26:27.620
Now, thankfully, I have a separate system.
00:26:27.650 --> 00:26:30.600
I have my laptop system that I like to check things on.
00:26:30.780 --> 00:26:31.000
Okay.
00:26:31.360 --> 00:26:33.800
And it was similarly specced to the main machine
00:26:33.810 --> 00:26:34.800
I was running at the time.
00:26:35.260 --> 00:26:37.900
So I didn't lose functionality at that point,
00:26:38.000 --> 00:26:42.320
but then I wiped it clean and fresh installed
00:26:42.540 --> 00:26:44.340
and everything was beautiful.
00:26:45.200 --> 00:26:48.180
And I think it has to do with just old code
00:26:48.640 --> 00:26:51.360
being overwritten and old preference files
00:26:51.580 --> 00:26:53.940
and all this kind of junk that just kind of stays there.
00:26:53.780 --> 00:26:57.080
Well, that's a key thing that you just said right there, those old preference files, which
00:26:54.220 --> 00:26:56.520
and yeah
00:26:57.180 --> 00:27:00.020
is why I like to wipe clean and just do a fresh install.
00:27:00.420 --> 00:27:05.840
The other thing it causes me to do is take stock of what am I actually using?
00:27:04.220 --> 00:27:04.620
yeah
00:27:06.200 --> 00:27:07.000
What do I need to keep?
00:27:07.180 --> 00:27:08.740
What do I not need to reinstall?
00:27:09.660 --> 00:27:15.840
And in addition to that, when developers are updating software, you get the freshest install
00:27:15.900 --> 00:27:16.660
on a clean OS.
00:27:17.080 --> 00:27:18.640
That's the best way I like looking at it.
00:27:19.120 --> 00:27:22.260
And I don't mind taking the time to do the install.
00:27:19.179 --> 00:27:19.540
yeah
00:27:23.020 --> 00:27:26.040
If everything's clean and it's awesome, I'm good, I'm cool.
00:27:26.760 --> 00:27:29.740
But one other thing you need to think about, and it's interesting you bring up the fact
00:27:29.840 --> 00:27:32.920
you have your laptop and then you have your other machine and they're similarly the expect,
00:27:34.100 --> 00:27:36.920
is can your machine actually run the new OS?
00:27:37.920 --> 00:27:37.960
Yeah.
00:27:37.960 --> 00:27:38.040
Yeah.
00:27:38.080 --> 00:27:42.300
Because running a new OS on an old machine could mean that your processor is suddenly
00:27:42.380 --> 00:27:46.120
going to be like, "Motherfucker, I'm getting hot!"
00:27:44.380 --> 00:27:45.280
Yeah.
00:27:46.120 --> 00:27:46.580
[laughs]
00:27:46.820 --> 00:27:47.020
Absolutely.
00:27:47.480 --> 00:27:47.900
Yeah.
00:27:48.120 --> 00:27:51.160
It's one of those things that it tends to be.
00:27:51.160 --> 00:27:56.760
to, you know, make use of the newer chips and all the power and stuff that comes along
00:27:56.920 --> 00:28:04.000
with newer machines. And it doesn't mean that your old machine can handle it. And sometimes
00:28:04.160 --> 00:28:09.920
it's even worse, like we upgrade to what we think is going to be better. And it just worsens
00:28:10.020 --> 00:28:14.420
everything because it's so slow and it's sluggish to do what we used to take for granted.
00:28:14.760 --> 00:28:20.560
So the upgrade doesn't. Yes. Yes.
00:28:15.800 --> 00:28:19.520
However, sometimes those upgrades can make things faster.
00:28:20.040 --> 00:28:23.120
And as my experience in this last week and a half
00:28:23.300 --> 00:28:26.280
has proven to myself other than the other weird anomalies
00:28:26.380 --> 00:28:28.160
that are happening with Catalina,
00:28:28.680 --> 00:28:31.740
my machine would take forever to boot up.
00:28:31.760 --> 00:28:32.520
Yeah.
00:28:32.460 --> 00:28:34.500
But once it was booted, it was lightning fast.
00:28:35.000 --> 00:28:38.400
With Big Sur, my machine boots up instantly.
00:28:38.460 --> 00:28:39.860
Wow.
00:28:38.700 --> 00:28:39.580
It's fast.
00:28:39.860 --> 00:28:40.020
Wow.
00:28:40.520 --> 00:28:42.620
However, there's a couple of other things
00:28:42.800 --> 00:28:44.960
that have slowed down a little bit.
00:28:45.440 --> 00:28:50.880
And that is opening sessions with plugins that aren't quite
00:28:51.240 --> 00:28:52.400
Big Sur compatible yet.
00:28:52.640 --> 00:28:55.120
So I do have a couple of plugins that are running in
00:28:55.260 --> 00:29:00.260
Big Sur, but they are not Big Sur compatible, even though
00:28:56.860 --> 00:28:57.200
Mm-hmm.
00:28:59.800 --> 00:29:00.780
Gotcha.
00:29:00.340 --> 00:29:01.680
I've got the latest installers.
00:29:01.800 --> 00:29:05.260
And those cause sessions to load a little bit slow.
00:29:05.640 --> 00:29:07.100
But once they're open, they're running.
00:29:05.960 --> 00:29:06.220
Yeah.
00:29:07.940 --> 00:29:10.740
I'm not noticing any speed difference there.
00:29:08.340 --> 00:29:08.820
They're fine.
00:29:10.860 --> 00:29:12.780
It's just opening a file once in a while.
00:29:12.900 --> 00:29:13.800
It's just a little bit slow.
00:29:13.980 --> 00:29:15.380
Yeah.
00:29:14.880 --> 00:29:18.340
And I have no idea how that would work between Windows 10 and Windows 11,
00:29:18.500 --> 00:29:19.860
but that might be the same case.
00:29:20.000 --> 00:29:23.760
Even though somebody's got Windows 11 to run on a really old PC,
00:29:24.320 --> 00:29:28.540
it's probably not running efficiently is the best way to think about it.
00:29:27.130 --> 00:29:27.560
Yeah.
00:29:27.560 --> 00:29:27.720
Yeah.
00:29:29.400 --> 00:29:32.060
So now we're on this topic of talking about
00:29:32.280 --> 00:29:33.340
reinstalling everything.
00:29:33.980 --> 00:29:35.920
I just want to say that I'm one of those people
00:29:36.280 --> 00:29:40.620
that I am firmly planted in the pro-iLock camp.
00:29:40.660 --> 00:29:41.760
I'm right there with you.
00:29:42.300 --> 00:29:43.940
Because when you do a clean install,
00:29:44.520 --> 00:29:48.280
it's so much easier to just, you reinstall the software,
00:29:48.840 --> 00:29:51.620
plug in your iLock and boom, you're good to go.
00:29:51.940 --> 00:29:53.000
Mm-hmm, agreed.
00:29:52.300 --> 00:29:52.920
All right, so.
00:29:53.480 --> 00:29:56.980
That way you don't have to worry about, "Oh, God, did I not deauthorize my machine?
00:29:57.590 --> 00:29:59.000
Do I need to reauthorize it?
00:29:59.080 --> 00:30:00.940
Where's my serial number?"
00:30:00.940 --> 00:30:02.040
That stuff sucks.
00:30:01.780 --> 00:30:04.060
I think so too.
00:30:02.940 --> 00:30:03.940
There's no question about it.
00:30:04.140 --> 00:30:05.020
I just hate it.
00:30:04.370 --> 00:30:04.800
Yeah.
00:30:05.490 --> 00:30:05.960
Yeah.
00:30:06.160 --> 00:30:07.500
So I'm with you on that.
00:30:07.640 --> 00:30:09.200
The iLock is so much better.
00:30:09.520 --> 00:30:11.320
Install the software plug in the I lock.
00:30:11.420 --> 00:30:13.220
You're good to go and you're ready to rock.
00:30:13.600 --> 00:30:14.540
I agree.
00:30:13.610 --> 00:30:18.540
And with that, let's talk about our Friday finds for this week.
00:30:18.620 --> 00:30:19.880
Chris, what have you got?
00:30:20.500 --> 00:30:25.520
Well, I haven't got this, but my find for this week is, of course, it was announced
00:30:25.610 --> 00:30:31.480
the new MacBook Pros that came out with the new M1 chip.
00:30:28.500 --> 00:30:29.020
Hmm.
00:30:31.660 --> 00:30:33.880
It's going to be the M1 Pro or the M1 Max.
00:30:34.800 --> 00:30:35.260
Yummy.
00:30:35.580 --> 00:30:39.260
And yeah, the specs on that just look amazing.
00:30:40.340 --> 00:30:46.100
I've been asking for for the first iteration of the max silicon was the the RAM limit, right?
00:30:46.280 --> 00:30:46.580
Mm-hmm.
00:30:46.780 --> 00:30:54.840
Now you can go up to 32 and 64 and more processors and yeah, they just look sexy as all hell, man.
00:30:55.120 --> 00:31:02.920
So that has to be yeah, yeah, so that that has to be my Friday fun for this week. What about you,
00:30:55.880 --> 00:30:57.620
You ready to have sex with the machine?
00:31:02.920 --> 00:31:03.700
Jody what do you got?
00:31:03.679 --> 00:31:10.880
I'm going in with something a little bit different. I'm looking at the Roland Zenn tracker and that is a brand new DAW.
00:31:11.720 --> 00:31:12.700
Not really a DAW,
00:31:13.560 --> 00:31:17.320
But it is a multi-track audio program for your iPhone and your iPad.
00:31:18.500 --> 00:31:23.300
Put out by Roland, where you can then record audio multi-track form.
00:31:18.800 --> 00:31:19.260
Okay
00:31:23.400 --> 00:31:26.420
It's kind of like going back to a task and port of one in a sense,
00:31:26.580 --> 00:31:28.420
but you're doing it with a phone or your iPad.
00:31:29.040 --> 00:31:33.400
So I'm looking at the Zen tracker. I'm going to check that out. Yeah.
00:31:32.280 --> 00:31:34.820
Cool good. All right, awesome
00:31:34.280 --> 00:31:35.900
And while we've got your attention,
00:31:36.300 --> 00:31:39.399
we would like you to go to our website and leave us a review at inside the
00:31:39.400 --> 00:31:46.520
recordingstudio.com/review or just go to inside the recording studio.com and sign up for our email list.
00:31:47.300 --> 00:31:51.040
Doing so gets you weekly reminders about the Tuesday tips that we put out
00:31:51.480 --> 00:31:56.580
and we'll make sure you don't miss any episodes in the future. Plus the extra bonuses when you're on
00:31:56.660 --> 00:32:02.119
our email list and we're doing a giveaway, you're automatically entered for that giveaway. How cool is
00:32:02.120 --> 00:32:07.560
that if you send us an email to goldstar g old s t a r at
00:32:07.640 --> 00:32:11.460
inside the recording studio dot com with the phrase operating
00:32:11.620 --> 00:32:15.800
system, you will get something cool back in your inbox. If you
00:32:15.840 --> 00:32:18.940
have a topic of suggestion for Chris and I to explain in a
00:32:18.980 --> 00:32:23.660
future episode, contact us on the contact page at the website
00:32:23.840 --> 00:32:26.340
and we'll put it into consideration for a future
00:32:26.680 --> 00:32:31.440
episode. And with that, I'll say see you next week.
00:32:32.260 --> 00:32:34.340
we go on jody thank you for listening everybody
00:32:59.840 --> 00:33:01.240
සම�
00:00:17.320 --> 00:00:21.620
Hello and welcome to another episode of Inside the Recording Studio.
00:00:22.020 --> 00:00:25.740
I am Jody Whitesides and with me as always is mister Chris Hellstrom.
00:00:25.740 --> 00:00:26.740
How are you today, Chris?
00:00:27.440 --> 00:00:29.980
I'm doing good Jody. I'm doing really well. How about you?
00:00:28.780 --> 00:00:34.120
Great! I'm doing good too. I'm not going to complain about too much. I'm going to do that
00:00:34.260 --> 00:00:45.300
and save that for today's episode. The change has already happened. It's not even that it's
00:00:37.300 --> 00:00:41.080
Yes. Do you feel like there is a change coming for you?
00:00:43.640 --> 00:00:49.280
Yeah. Do you feel like, do you feel like a better man from the journey?
00:00:45.300 --> 00:00:53.940
coming it's already happened no no I do not yes
00:00:50.960 --> 00:00:58.540
No. All right, let's explain shall we both Mac and Windows have new operating systems coming.
00:00:58.880 --> 00:01:06.080
Mac is about to go on from Big Sur to Monterey as the time of recording this episode and Windows
00:01:06.180 --> 00:01:14.160
is about to roll out Windows 11. Yeah, so we thought we would talk today about when should you
00:01:08.040 --> 00:01:08.980
oh boy
00:01:14.240 --> 00:01:20.500
upgrade your operating system on your production system. And fair
00:01:19.200 --> 00:01:20.060
Yes, yes.
00:01:20.580 --> 00:01:25.340
warning to all Windows users out there that this will be a Mac
00:01:25.520 --> 00:01:29.280
centric topic. But a lot of the things that we're talking about
00:01:29.400 --> 00:01:33.520
will be valid for PC or Windows users as well. Some of the
00:01:33.540 --> 00:01:37.860
advice here. So even though we end up talking about Mac, let me
00:01:34.619 --> 00:01:34.780
Let's hope.
00:01:37.900 --> 00:01:41.959
post the question to you, Jody, then right off the bat, new OS
00:01:39.620 --> 00:01:39.920
Oh, huh.
00:01:41.960 --> 00:01:45.800
comes out. Do you jump on it right away? Yes or no?
00:01:46.140 --> 00:01:52.060
Currently? No. No. Years ago? Damn right I did.
00:01:47.560 --> 00:01:54.980
Currently? No. Did you? Yes. Yeah, you were one of the
00:01:55.100 --> 00:02:01.740
early adopters of like when OS 10 came out, you were you were
00:01:57.179 --> 00:02:04.640
Bleeding edge. Oh yeah, I jumped on OS X immediately. Like almost immediately, yes.
00:02:03.160 --> 00:02:07.500
right. Because that was a big change because obviously not
00:02:07.020 --> 00:02:26.480
massive. Yeah, and one of the biggest reasons why I started early on with it was technically
00:02:07.660 --> 00:02:11.940
just the underlying code, but everything the way it looked and
00:02:11.940 --> 00:02:14.920
that plugins and everything had to run was different.
00:02:15.000 --> 00:02:19.060
So that was a sea change when it came to the mac at least.
00:02:19.200 --> 00:02:42.980
right. Yeah.
00:02:26.790 --> 00:02:32.720
almost like giving myself a limitation like having a four track cassette machine, like
00:02:32.780 --> 00:02:37.220
the task and port of one. And the reason for it was, is it got me back to being a bit more
00:02:37.280 --> 00:02:42.960
creative in a sense of like, shit, I don't have my plethora of plugins yet. So I was
00:02:43.060 --> 00:02:47.820
kind of stuck primarily with what came with logic, because that was like really the first
00:02:48.060 --> 00:02:54.160
DAW that went into OS 10. And I had numerous friends that were like, dude, I'm not going
00:02:49.960 --> 00:02:50.240
Yeah.
00:02:54.300 --> 00:02:59.099
off OS nine for as long as I can help it. And I know the main reason why was because
00:02:59.100 --> 00:03:03.960
Because they had tens of thousands of dollars worth of software that was cracked, that they
00:03:02.960 --> 00:03:04.120
Yeah.
00:03:03.960 --> 00:03:08.140
were running, and that they direly needed for their work and they hadn't paid for it.
00:03:08.410 --> 00:03:09.200
And I get that.
00:03:09.920 --> 00:03:12.640
It's not something I condone, but I get it.
00:03:13.180 --> 00:03:19.380
And for me, having gone to OS X early in the game, whenever something new finally arrived
00:03:19.520 --> 00:03:25.739
on OS X, I was able to immediately purchase it and not feel the sting of dropping tens
00:03:25.740 --> 00:03:30.580
of thousands of dollars all at once to get all the plugins again.
00:03:30.100 --> 00:03:34.520
Yeah, there was a time when plugins were a lot more expensive than they are today.
00:03:35.000 --> 00:03:42.420
So yeah, right. Yeah, no, that was a big thing. And I think you've touched on that in, I think
00:03:35.240 --> 00:03:35.780
This is true.
00:03:41.500 --> 00:03:41.900
episodes.
00:03:42.560 --> 00:03:47.300
you you've justified it there. Just like you said, now it was a way to make the migration
00:03:47.420 --> 00:03:53.400
process actually smoother because it wasn't like you said, it wasn't, oh, I have to invest
00:03:53.780 --> 00:03:58.579
huge amount of money to kind of get up and running right off the bat, you know. So that
00:03:58.580 --> 00:04:01.340
That's a big one, you know, but what?
00:03:59.299 --> 00:04:04.400
It is, but that was the last time I was truly, in my mind, bleeding edge.
00:04:05.860 --> 00:04:08.940
Right. So what made you stop doing that?
00:04:09.020 --> 00:04:13.760
Because I've I might have done that around the same time in a similar way.
00:04:13.900 --> 00:04:18.239
But I think I've always been at least a month behind you
00:04:18.820 --> 00:04:19.380
(laughs)
00:04:19.320 --> 00:04:23.000
because I've always like, OK, well, shit goes really side.
00:04:21.579 --> 00:04:23.580
If it worked for him. (laughs)
00:04:23.580 --> 00:04:26.780
Yeah, I can always call George or I can call Jody, right?
00:04:26.820 --> 00:04:28.140
because they're gonna be up on it.
00:04:28.600 --> 00:04:29.660
You know, I'll ask the question again,
00:04:29.780 --> 00:04:31.560
what made you stop doing that?
00:04:31.479 --> 00:04:34.040
It was around the time that,
00:04:34.620 --> 00:04:36.860
might have been around the time of Sierra or High Sierra,
00:04:37.380 --> 00:04:41.860
where I still had the cheese grater Mac Pro that I had.
00:04:37.600 --> 00:04:37.760
Mm.
00:04:41.980 --> 00:04:42.420
Right?
00:04:42.360 --> 00:04:46.240
And I believe that was no longer capable of running
00:04:46.760 --> 00:04:48.580
if it was Sierra or high Sierra.
00:04:48.740 --> 00:04:50.660
I can't recall which OS it was
00:04:50.860 --> 00:04:53.780
that stopped running on the old Mac Pros.
00:04:54.160 --> 00:04:56.940
And then I ended up having to hack the machine
00:04:57.120 --> 00:04:59.640
in order to run the newer OS
00:05:00.320 --> 00:05:03.100
because they were trying to get rid of whatever chip
00:05:00.760 --> 00:05:00.860
Yeah.
00:05:03.260 --> 00:05:03.900
they were running.
00:05:04.960 --> 00:05:06.579
And that's when I kind of stopped
00:05:06.580 --> 00:05:08.580
because that became a major pain in the ass.
00:05:09.300 --> 00:05:14.620
Then that machine died unmercifully in a power surge
00:05:15.100 --> 00:05:19.380
through battery protected backup system, the APS.
00:05:18.500 --> 00:05:20.060
Oh, yeah, remember that.
00:05:20.090 --> 00:05:20.920
Yeah, that was brutal.
00:05:20.120 --> 00:05:23.220
A gigantic storm that had a surge of electricity
00:05:23.660 --> 00:05:25.240
that just it fried everything.
00:05:25.960 --> 00:05:27.580
And that was unfortunate.
00:05:28.180 --> 00:05:30.200
So I ended up getting a new machine that was capable
00:05:30.240 --> 00:05:32.040
of running the OSes with no issue.
00:05:32.720 --> 00:05:36.160
It was easier to kind of stay up to date.
00:05:36.640 --> 00:05:39.060
However, in the last couple of years,
00:05:39.680 --> 00:05:41.840
developers are having a harder time keeping up.
00:05:41.860 --> 00:05:42.460
Yeah.
00:05:42.460 --> 00:05:47.620
Yeah. No, there have been some, some drastic changes on the OS level here with not only
00:05:47.740 --> 00:05:54.340
the implementation of finally just going like 64 bit some while ago, right? Then how with
00:05:54.340 --> 00:05:58.760
the new M1 chips and all this kind of stuff. So there are these hurdles now for them to
00:05:58.800 --> 00:06:03.720
kind of overcome. You know, you brought up a lot of points there that we're actually
00:05:59.880 --> 00:06:00.480
Yes.
00:06:00.720 --> 00:06:03.040
Okay.
00:06:03.770 --> 00:06:09.180
going to talk about. So let's take a step back and say, well, what would be the pros
00:06:09.180 --> 00:06:15.500
and cons of immediately wanting the new OS. And the first one I can think of, and I can
00:06:15.540 --> 00:06:21.460
relate to, is people want the newest, shiniest thing. Right? So, oh, yeah, this is awesome.
00:06:20.780 --> 00:06:22.180
Sure.
00:06:21.880 --> 00:06:27.920
You know, it that I mean, that appeals to us on a very human level, I suppose. Right?
00:06:28.440 --> 00:06:32.600
Well, it's like, oh, yeah, I got, yeah, I'm not slumming it to OS is ago. What's wrong
00:06:32.600 --> 00:06:33.980
with you type of thing, right?
00:06:33.639 --> 00:06:41.020
Yeah, I for me, I don't know if I necessarily care about the newest look or the shiniest
00:06:41.240 --> 00:06:41.840
toy in that regard.
00:06:42.360 --> 00:06:45.980
I'm more about what extra functionality am I getting?
00:06:46.460 --> 00:06:51.560
I'm not saying I agree without mindset, I'm just saying that that's a reality. I mean, there are people
00:06:46.660 --> 00:06:47.560
That's the biggest thing.
00:06:48.720 --> 00:06:48.960
Right.
00:06:52.600 --> 00:06:58.680
that I know on certain music boards and things that they're just like, yeah, I'm jumping in with both feet.
00:06:58.720 --> 00:07:04.860
I don't care. I'm going for it and see what works or not. People that even download the public
00:07:05.180 --> 00:07:14.380
bait is and things like that. Yeah. No, I'm not that brave. Yeah, right. Yeah. Yeah.
00:07:05.720 --> 00:07:08.780
Yeah, I don't do that anymore.
00:07:09.520 --> 00:07:12.180
I prefer to get paid for my beta testing, damn it.
00:07:13.800 --> 00:07:18.899
And I still feel like I'm beta testing shit even though I'm not getting paid for testing
00:07:18.900 --> 00:07:20.700
OS's anymore.
00:07:21.800 --> 00:07:27.999
And if you are, you know, if that's your income, that's your line of work. It's time that you don't
00:07:28.000 --> 00:07:33.460
have you can't afford to spend doing that kind of stuff. So I think that's why a lot of people
00:07:33.940 --> 00:07:39.280
who are in this business tend to not stay on the bleeding edge because, again, you got a working
00:07:39.540 --> 00:07:46.280
solid system, there's no reason to upgrade the other thing unless there's drastic added functionality.
00:07:42.080 --> 00:07:43.480
Right.
00:07:43.480 --> 00:07:43.600
Right.
00:07:47.060 --> 00:07:52.960
Right. Which sometimes it can be, but I think a little bit less so perhaps on the OS level,
00:07:53.520 --> 00:08:00.640
at least from my perspective when it comes to music applications. But when Apple actually rolled
00:08:00.920 --> 00:08:05.760
out the AU format, that was part of the operating system and that was a big thing that it was,
00:08:06.000 --> 00:08:11.280
yeah, we're going to be able to run music plugins on an operating system level type of thing.
00:08:11.199 --> 00:08:13.460
So what are some of the cons of upgrading?
00:08:13.460 --> 00:08:14.080
too soon.
00:08:14.480 --> 00:08:21.039
What conflicts primarily, right, where it could be, like you mentioned, plugins that are no longer
00:08:21.040 --> 00:08:24.300
compatible, right, that you rely on, and then you'll have to
00:08:24.340 --> 00:08:27.320
decide that if there is such a big part of your workflow that
00:08:27.380 --> 00:08:30.520
you need them, well, I would strongly suggest not upgrading
00:08:30.660 --> 00:08:34.780
yet, and waiting until they are or if they ever will become
00:08:35.460 --> 00:08:43.599
compatible. So yeah, it because that was the thing with
00:08:36.380 --> 00:08:40.880
That's a big key right there, whether or not they'll ever be upgraded.
00:08:43.860 --> 00:08:48.159
obviously this shift from 32 to 64. And we had sort of like
00:08:48.160 --> 00:08:53.660
patches for that was that it was 32 lives at one point, right? There was like a wrapper
00:08:53.730 --> 00:08:57.960
of sorts, I believe, that allowed you to do it. But then at some point also that went,
00:08:58.400 --> 00:09:03.640
you know, tits up and didn't work anymore. So there are those things and even on the
00:09:03.680 --> 00:09:08.820
hardware level, right, just compatibility, like there's software that you rely on in
00:09:08.880 --> 00:09:14.679
your day to day work, make sure it's compatible before you take the plunge. Developers are
00:09:14.680 --> 00:09:19.440
usually pretty good at that. And they even send out mailers like I got one from Slate
00:09:19.700 --> 00:09:24.580
just this week and say, Hey, don't upgrade to Monterey yet. You know, we're working on
00:09:24.580 --> 00:09:28.340
it again as fast as possible. But I think everybody kind of does that. If you want to
00:09:28.360 --> 00:09:37.820
be on the bleeding edge, maybe you're going to get cut sometimes, right? Yeah. Right.
00:09:31.660 --> 00:09:35.020
You mentioned real briefly their hardware and then you went right back to software.
00:09:35.300 --> 00:09:36.880
So hardware conflicts.
00:09:37.480 --> 00:09:40.900
Let's say that in my example where the computer got fried
00:09:41.020 --> 00:09:43.960
and I had to get a new machine, my old audio interface
00:09:44.180 --> 00:09:46.160
no longer interfaced with the new computer.
00:09:46.440 --> 00:09:50.240
I had to get an audio interface upgrade, so to speak,
00:09:50.480 --> 00:09:51.720
along with the new computer.
00:09:50.860 --> 00:10:05.740
Yeah. Yeah. I had that happen. It was an older piece of kit
00:09:52.240 --> 00:09:53.700
You have gone through the problem
00:09:54.140 --> 00:09:58.380
of having an audio interface that was no longer compatible
00:09:58.640 --> 00:10:02.420
due to its drivers when you updated to a certain OS.
00:10:05.960 --> 00:10:09.280
fully functional, work great. I love the converters and all this
00:10:09.420 --> 00:10:15.140
kind of stuff. But it was an older piece of hardware. The
00:10:15.140 --> 00:10:21.040
newer versions of said interface. And we're no longer supporting it with the older drivers
00:10:21.240 --> 00:10:26.940
for that. It's like it's legacy software. It just, well, that's the reality of the situation
00:10:22.020 --> 00:10:23.620
Those rat bastards!
00:10:27.020 --> 00:10:27.500
Of course.
00:10:27.080 --> 00:10:32.460
though, right? You know, whether it's a driver issue or, you know, a connectivity thing,
00:10:32.700 --> 00:10:44.200
you know, Firewire 400 has gone away, even 800 has gone away. PCIe slot, right? Yeah,
00:10:38.000 --> 00:10:38.060
Right.
00:10:38.280 --> 00:10:42.720
Well, that was my reasoning for having to get the new interface is that the port no longer
00:10:42.820 --> 00:10:43.160
existed.
00:10:44.540 --> 00:10:48.600
So you can deal with dongles and things like that, but I think you're possibly just kicking
00:10:48.760 --> 00:10:50.300
the can further down the road, right?
00:10:50.460 --> 00:10:55.180
Because there will inevitably be something that that's not going to work anymore, right?
00:10:55.250 --> 00:10:59.460
Or there will be conflicts that just make it pain to kind of work with.
00:10:59.700 --> 00:11:00.980
[laughs]
00:10:59.960 --> 00:11:01.120
I ended up with an update.
00:11:01.340 --> 00:11:07.200
I had to get a new interface and I could eventually move on from the OS I was on, because I was
00:11:07.240 --> 00:11:09.280
starting to use other software as well.
00:11:10.020 --> 00:11:17.480
in true Apple fashion, that was only going to work on a certain OS forward.
00:11:18.260 --> 00:11:23.700
Right? So it was like, okay, well, all right. And then you upgrade, and then you
00:11:23.700 --> 00:11:29.020
have to decide what which one weighs out or what wins out. Do you go with a
00:11:29.040 --> 00:11:32.960
newer functionality and upgrade some hardware or are you really satisfied with
00:11:33.040 --> 00:11:37.340
what you have and keep working on that until you're not anymore? And then you
00:11:37.340 --> 00:11:42.780
have to do it. So conflicts are something that we have to be aware of. You and I have talked about
00:11:42.780 --> 00:11:48.780
it before and you might even mention on the podcast, but when the latest Mac Pros came out,
00:11:49.220 --> 00:11:49.740
Yeah.
00:11:49.560 --> 00:11:54.300
these monster machines that could cost as much of a house in certain parts of the country,
00:11:49.860 --> 00:11:50.000
is.
00:11:54.570 --> 00:12:01.100
if you max them out, are now going to not be able to run. I think it's on whatever is going to come
00:12:01.220 --> 00:12:06.640
after Monterey, I think is not going to be able to run the latest OS anymore.
00:12:07.380 --> 00:12:12.020
be careful. I think so. And we'll see even with all the universal
00:12:07.620 --> 00:12:09.080
That's the understanding that I have.
00:12:12.100 --> 00:12:15.020
bind reasons, top is good. Nope, it's going to be just m one and
00:12:15.060 --> 00:12:21.760
forward, right? So you have to there you go. Thank you. Yeah.
00:12:16.620 --> 00:12:19.500
Yep, Apple Silicon going forward.
00:12:22.740 --> 00:12:26.640
So yeah, compatibility, that that's, that's the big one. And as
00:12:26.680 --> 00:12:30.000
always, it can, you know, you mentioned drivers and things.
00:12:30.160 --> 00:12:33.540
And that one of the pros is obviously like possible bug
00:12:33.540 --> 00:12:40.160
fixes, but it can also create new bugs. Right. So functionality that you yeah, that I would
00:12:36.540 --> 00:12:38.700
Yes, big con right there.
00:12:40.200 --> 00:12:44.440
say so. Absolutely. So these are things that you have to put in mind.
00:12:44.920 --> 00:12:48.360
Before we move on to the next section here in the podcast, let's just take a word from
00:12:48.420 --> 00:12:48.880
our sponsors.
00:12:51.040 --> 00:12:51.560
And we're back.
00:12:52.000 --> 00:12:53.220
What are we talking about now, Chris?
00:12:53.880 --> 00:13:03.520
Well, the next thing that we're going to talk about is, are you working on a solid system? And
00:13:03.520 --> 00:13:03.840
on that
00:13:04.500 --> 00:13:10.740
Because my recent experience has been made with doing an upgrade as of like a week and
00:13:10.740 --> 00:13:16.240
a half ago, it came down to, yes, I did have a working solid system.
00:13:16.460 --> 00:13:25.920
However, due to the ecosystem that I was in, certain problems arose when a couple of devices
00:13:19.459 --> 00:13:20.860
Yeah.
00:13:26.180 --> 00:13:30.040
were updated to the latest OS and a couple of them were not.
00:13:30.420 --> 00:13:31.720
And then there were software conflicts.
00:13:32.440 --> 00:13:38.820
And of course, the big tech company was like, not talking about it is the best way to put
00:13:38.880 --> 00:13:39.000
it.
00:13:39.840 --> 00:13:47.220
And their answer after spending hours beta testing, so to speak, came back saying, we
00:13:43.060 --> 00:13:44.460
Yeah.
00:13:47.300 --> 00:13:49.740
know about this, we're not talking about it.
00:13:50.040 --> 00:13:54.260
If it's a problem for you, tough shit is essentially what the answer was.
00:13:52.740 --> 00:13:53.080
Yeah.
00:13:54.800 --> 00:13:57.140
And that's the big middle finger that Apple will give you.
00:13:57.340 --> 00:14:02.580
At that point, I had to heavily weigh, do I upgrade the OS on the other devices in order
00:14:02.680 --> 00:14:06.760
to get rid of this conflict because it's going to drive me out of my mind, even though
00:14:06.240 --> 00:14:06.480
Yeah.
00:14:06.760 --> 00:14:08.100
I had a solid working system?
00:14:08.470 --> 00:14:13.340
The answer to that question was, after doing a software check of everything that I use
00:14:13.890 --> 00:14:19.360
and making the determination of if there's anything I'm using that isn't compatible,
00:14:19.590 --> 00:14:21.880
do I wish to continue using it going forward?
00:14:22.620 --> 00:14:26.440
And after weighing that all out, it was like, fuck it, I'm going for the upgrade.
00:14:22.660 --> 00:14:22.900
Yeah.
00:14:26.940 --> 00:14:32.380
Because literally like 98% of everything was there to work in Big Sur.
00:14:32.760 --> 00:14:37.220
And this is what a year, almost a year after Big Sur was released.
00:14:37.880 --> 00:14:39.460
I finally upgraded to Big Sur.
00:14:38.100 --> 00:14:43.680
Yeah, I mean, yeah, I mean, they're rolling them out every year now, right?
00:14:43.020 --> 00:14:44.320
Well, they always have.
00:14:43.780 --> 00:14:50.160
Every year, I guess, but it felt like it was more, and this might be just, you know, selective
00:14:50.160 --> 00:14:54.380
memory, but it felt like it was more of incremental changes in
00:14:54.440 --> 00:14:57.460
the past. But has it really been I mean, after it rolled into
00:14:57.540 --> 00:15:05.760
10? Was it really every year that something new came out? I must
00:15:00.760 --> 00:15:01.120
Pretty much.
00:15:01.240 --> 00:15:04.800
They've done a new OS literally just about every year.
00:15:05.900 --> 00:15:09.260
have selective memory because I, it feels like they've sped them
00:15:09.400 --> 00:15:11.480
up. But maybe it's just because I'm paying attention to it more.
00:15:12.580 --> 00:15:14.280
I don't know. Yeah.
00:15:13.099 --> 00:15:13.260
Maybe.
00:15:14.220 --> 00:15:19.940
So that was me waiting almost a year to go to Big Sur and now they're announcing Monterey.
00:15:20.000 --> 00:15:20.960
It's like, oh, good God.
00:15:21.050 --> 00:15:24.680
But I'm thinking that the difference between Big Sur and Monterey is going to be a lot
00:15:24.720 --> 00:15:29.340
more minimal, which means I'll probably be upgrading to Monterey sooner than a year.
00:15:30.040 --> 00:15:30.340
We'll see.
00:15:30.880 --> 00:15:36.420
Yeah, it seems like the big shift has possibly been done with, you know, Apple Silicon, right?
00:15:35.960 --> 00:15:37.440
There is one more big shift.
00:15:36.440 --> 00:15:42.940
And that, yeah, there is no Intel chips, like you have an Intel chip chip.
00:15:37.490 --> 00:15:39.340
It comes after Monterey.
00:15:43.100 --> 00:15:45.400
Yeah, sorry. You're locked out.
00:15:43.980 --> 00:15:48.000
out of luck. So Monterey is the EOL of my machines that I currently have.
00:15:48.120 --> 00:15:52.080
And then of course, in about a year, I'm going to have to consider upgrading to
00:15:52.420 --> 00:15:55.860
Apple Silicon. And it's the same sort of thing that's kind of happening right now.
00:15:55.940 --> 00:16:00.400
Also with the people that run Windows, because apparently it's a really massive
00:16:00.700 --> 00:16:03.140
jump to go from Windows 10 to Windows 11.
00:16:03.099 --> 00:16:03.560
Yeah.
00:16:03.840 --> 00:16:07.120
And people are talking about whether the hardware will work with it.
00:16:07.360 --> 00:16:10.080
I actually just read an article this morning. If I'm not mistaken,
00:16:10.220 --> 00:16:14.240
somebody got Windows 11 to run on like a 10 year old PC.
00:16:15.180 --> 00:16:16.840
And I was kind of like, well, that's impressive.
00:16:17.020 --> 00:16:20.900
And I think that's the whole point of the article is just like, yes, we did it.
00:16:21.440 --> 00:16:23.300
But how effective is it in doing that?
00:16:23.380 --> 00:16:23.920
You don't know.
00:16:24.580 --> 00:16:31.420
Kudos to Microsoft then, I suppose, but that is one of the things that is different and
00:16:31.700 --> 00:16:40.100
you could see it as a pro or con, but because Apple in the Mac is a closed ecosystem, they
00:16:40.100 --> 00:16:48.260
can control obviously the entire ecosystem, whereas on the window side, it is much wider. So they have
00:16:40.880 --> 00:16:57.360
Well, the other thing too to think about with Windows is they're still going on with Intel
00:16:48.400 --> 00:16:53.620
all these other parameters to kind of consider or not consider, right? So,
00:16:57.660 --> 00:16:58.940
Nothing's changing there.
00:16:59.160 --> 00:17:05.860
well, there is that as well. But I'm saying just from an operating system standpoint, they can seem
00:17:05.860 --> 00:17:11.240
possibly less ruthless with what they support anymore. But that's
00:17:10.159 --> 00:17:10.760
Mm-hmm.
00:17:11.360 --> 00:17:16.819
something that Apple has done. I mean, forever. And the, yeah,
00:17:14.159 --> 00:17:15.880
They've always been ruthless.
00:17:16.459 --> 00:17:17.120
[laughs]
00:17:17.020 --> 00:17:20.220
and it could be I mean, I remember again, I'm really dating
00:17:20.339 --> 00:17:22.939
myself here. But I remember when they came out, I think it was
00:17:23.040 --> 00:17:26.800
the when they went to the G three, and they said like, Yeah,
00:17:26.880 --> 00:17:29.920
we're not going to have floppy disks anymore. And like, what
00:17:28.780 --> 00:17:28.940
Hmm.
00:17:30.060 --> 00:17:35.840
what? But it's like, yeah, and now it's like floppy disks. What
00:17:30.340 --> 00:17:32.400
Everybody freaks out.
00:17:35.840 --> 00:17:40.740
on that and they did the same with the scuzzy connection and later on with
00:17:40.920 --> 00:17:45.760
firewire 400 800 so they can draw these sort of like hard lines in the sand like
00:17:46.200 --> 00:17:49.660
we're not going to support those anymore because they have that the entire
00:17:49.920 --> 00:17:54.700
ecosystem sort of contained whether you think that's good or bad that's up for
00:17:54.900 --> 00:17:55.760
debate I suppose
00:17:54.960 --> 00:17:56.360
Right.
00:17:56.360 --> 00:18:00.880
The takeaway is that when you have a solid system, if it's not tied to the internet,
00:18:01.040 --> 00:18:04.480
generally speaking, you're probably not going to worry about doing that upgrade because
00:18:04.960 --> 00:18:12.960
the system works and you're good. However, there are times where it's incredibly stupid to pick a
00:18:06.780 --> 00:18:06.880
Yeah.
00:18:06.880 --> 00:18:07.040
Yeah.
00:18:13.020 --> 00:18:17.720
point to upgrade an OS on a machine, and that is when you're in the middle of a giant project.
00:18:18.120 --> 00:18:19.200
Oh God, yes.
00:18:18.460 --> 00:18:23.880
Unless your machine dies, it's incredibly stupid to upgrade right in the middle of a project.
00:18:24.520 --> 00:18:29.500
Pick a point in time where you're going to have downtime in order to do it.
00:18:24.640 --> 00:18:25.120
Yeah.
00:18:29.760 --> 00:18:35.600
Or simply take the downtime and go, I will not be able to take on any work from this and this date.
00:18:35.600 --> 00:18:40.920
So you know that this is set aside to do the hardware and the software upgrades that you might want to do
00:18:41.300 --> 00:18:44.000
Yes, that's the wise way of doing it.
00:18:43.760 --> 00:18:44.640
you I
00:18:44.740 --> 00:18:50.160
See that again, and it's not like it's necessarily reflective of the real world
00:18:50.380 --> 00:18:55.540
But people are complaining like well, I was in the middle of mixing this project and now my plugins don't work
00:18:55.840 --> 00:19:01.580
Well, what'd you do? Well, I upgraded something. Well, why did you do that? You know, it is
00:18:55.920 --> 00:18:56.120
Oops.
00:18:56.120 --> 00:18:56.220
Oops.
00:18:58.540 --> 00:18:59.020
(laughs)
00:19:02.540 --> 00:19:05.580
alarmingly common I think and it
00:19:04.180 --> 00:19:05.940
Oh yeah, people don't think about it.
00:19:05.980 --> 00:19:10.680
I mean, you probably shouldn't mention the name, but it was a friend and
00:19:10.720 --> 00:19:15.820
collaborator of yours that just had a similar experience, right? And it had to
00:19:13.360 --> 00:19:14.520
About a year ago, yeah.
00:19:15.840 --> 00:19:22.520
do with OSs, right? Yeah, and yeah, again, if you're in the middle
00:19:17.700 --> 00:19:18.140
It did.
00:19:22.640 --> 00:19:27.600
of a project, don't upgrade. If there's a plugin update that promises to fix
00:19:27.800 --> 00:19:31.620
something you have an issue with, that might be a different story, but don't
00:19:31.620 --> 00:19:38.740
upgrade just for the upgrade sake of it. It is never strong word, but I would say it would never
00:19:39.120 --> 00:19:41.040
work out the way that you're hoping it will.
00:19:41.200 --> 00:19:46.480
Even if you're ready to do it, there's times when it doesn't work out the way you hope it would.
00:19:46.020 --> 00:19:50.100
Yes. Yeah, this is something you want to get off your chest here.
00:19:47.300 --> 00:19:47.740
(laughs)
00:19:50.300 --> 00:19:50.700
Yes.
00:19:51.940 --> 00:19:53.800
I'm gonna touch on this since we're talking about
00:19:53.520 --> 00:19:54.760
Yeah, you should. You should.
00:19:53.960 --> 00:19:55.300
affecting the workflow and whatnot.
00:19:55.860 --> 00:19:57.880
I made that choice and I figured, okay,
00:19:58.020 --> 00:20:01.000
I've got this span of time from a Thursday to a Tuesday
00:20:01.380 --> 00:20:02.900
where I can make this happen.
00:20:03.160 --> 00:20:04.720
And I did that jump to Big Sur.
00:20:05.400 --> 00:20:08.860
My first experience of doing it is something
00:20:09.020 --> 00:20:11.380
that I tend to recommend, especially when it's a big
00:20:11.520 --> 00:20:14.500
OS change like it was from Catalina to Big Sur,
00:20:14.620 --> 00:20:18.320
which it will be from Monterey to whatever the next OS is for Apple.
00:20:18.900 --> 00:20:23.100
And essentially what it is right now with Windows 10 going to Windows 11,
00:20:23.220 --> 00:20:27.060
from what I understand. And that is I wiped the machine clean.
00:20:27.700 --> 00:20:32.620
And I start with a fresh install of the OS and I'm porting over literally
00:20:28.200 --> 00:20:28.360
Yeah.
00:20:33.100 --> 00:20:37.480
whatever documents. Of course I've made a giant backup in order to do that.
00:20:37.060 --> 00:20:40.280
Yeah, I was just going to say, make sure that you get that out there, that you make it a
00:20:40.280 --> 00:20:58.160
backup of the working system to a separate drive. Yeah.
00:20:42.180 --> 00:20:44.780
And I do have that backup sitting on a RAID system
00:20:44.920 --> 00:20:47.420
so that if even one of the RAID drives dies,
00:20:48.060 --> 00:20:50.560
I still have the backup and I can stick another RAID drive
00:20:50.640 --> 00:20:52.660
in there and it recreates itself and it's all good.
00:20:53.200 --> 00:20:56.820
I do do massive backups whenever something big like that
00:20:56.880 --> 00:20:59.440
happens so that I can run it.
00:20:59.540 --> 00:21:02.680
In addition to that, I also set up a virtual machine
00:21:03.400 --> 00:21:06.260
to run that system, which is something I've never done
00:21:06.300 --> 00:21:07.960
before, it's the first time I've ever done that.
00:21:08.720 --> 00:21:10.520
So I did that as well, I did two things.
00:21:10.620 --> 00:21:15.440
I did a major backup and then I created a virtual machine that could still run that
00:21:15.500 --> 00:21:17.300
machine from the new OS.
00:21:17.880 --> 00:21:19.820
Now I wiped the machine clean.
00:21:20.360 --> 00:21:21.240
I did an install.
00:21:22.020 --> 00:21:28.380
The new OS did something funky in the disk management system that I had never
00:21:28.580 --> 00:21:31.380
seen before, and it split my hard drive in two.
00:21:31.820 --> 00:21:32.240
Oops
00:21:33.200 --> 00:21:37.180
It isn't technically, apparently it's not an oops, it's meant to do this, but
00:21:37.180 --> 00:21:42.820
it renamed it the same thing with the same name, but with an extension on the other name,
00:21:42.720 --> 00:21:45.040
Oh, that would yeah, that would
00:21:43.100 --> 00:21:46.940
which didn't make sense to me. And I booted up, I had problems going on, and all of a
00:21:46.960 --> 00:21:52.500
sudden I go back into the ability to deal with the OS on a non-computer level, so to
00:21:52.520 --> 00:21:58.940
speak, from the user situation. And I delete the extra drive and try to boot again, thinking
00:21:59.060 --> 00:22:03.960
that that was creating the problem. And that hosed the machine completely. Now I'm freaking
00:22:03.320 --> 00:22:03.640
Ach.
00:22:03.960 --> 00:22:08.860
out because the machine won't boot. And eventually I got the machine back into what they call
00:22:08.900 --> 00:22:15.740
recovery mode and tried to wipe it again and reinstall the OS. And instead of allowing me to do the
00:22:15.780 --> 00:22:22.460
latest and greatest in Big Sur for the Mac Pro that I have, it took me back to Yosemite, which is the
00:22:22.760 --> 00:22:29.360
OS that came with the machine. And then I had to install Yosemite. Once I got that back up,
00:22:22.880 --> 00:22:25.680
Oh wow
00:22:29.400 --> 00:22:34.940
Then I go back into recovery mode again and then it allowed me to wipe it again and put on Big Sur.
00:22:35.300 --> 00:22:41.020
That is not to say that it hasn't been problematic. Now that I've had Big Sur and I've installed all
00:22:41.020 --> 00:22:45.260
the software and everything, I still have little weird things happening. I've been dealing with
00:22:45.390 --> 00:22:51.900
Apple for hours on these little things and they can't figure it out. Even after big data dumps,
00:22:51.960 --> 00:22:58.760
they've got senior engineers working on it. And my understanding is it probably come Monday
00:22:58.760 --> 00:23:00.820
of next week, they will tell me,
00:23:00.990 --> 00:23:02.680
"You need to reinstall the system again."
00:23:02.880 --> 00:23:06.480
At which point I'm gonna just be like, "Shit!"
00:23:06.560 --> 00:23:08.160
However, the good thing is,
00:23:08.240 --> 00:23:10.040
is I won't have to reinstall all the software,
00:23:10.280 --> 00:23:11.960
being that it's already on the OS,
00:23:12.140 --> 00:23:15.100
it can allow for a clean install over the OS
00:23:15.170 --> 00:23:17.540
and keep all the data, so that's what I plan on doing.
00:23:18.780 --> 00:23:19.600
When I get told that.
00:23:20.000 --> 00:23:20.760
Hmm.
00:23:20.480 --> 00:23:23.220
So, it was not as smooth as I had hoped,
00:23:23.360 --> 00:23:27.540
it was probably the least smooth OS upgrade I've ever had.
00:23:27.760 --> 00:23:33.620
I generally have not had problems like that when I've gone for a clean install of an OS.
00:23:28.260 --> 00:23:28.740
And do you think?
00:23:33.800 --> 00:23:39.580
It's usually just you install it, you install your software, you pull your documents that you want back
00:23:39.760 --> 00:23:44.400
off of your backups onto your computer and you're good to go. This is the first time where that's
00:23:44.500 --> 00:23:54.440
not happened and it's a little frustrating. I did make the backups. I did make a virtual machine.
00:23:46.620 --> 00:23:50.700
Sure. Incredibly frustrating, no matter what kind of issues arise.
00:23:50.700 --> 00:23:50.960
eyes.
00:23:55.120 --> 00:23:59.500
I could technically go back, although I'm not going to, because there were other things with
00:23:59.530 --> 00:24:04.060
the updates of other devices that caused me to really rethink of like, hey, I need to do this
00:24:04.140 --> 00:24:10.840
going forward. Plus, there was a recent update in addition to all of this with the main DAW that I
00:24:10.900 --> 00:24:16.920
use for tracking and sometimes mixing, because now I'm switching it off between two different DAWs.
00:24:12.500 --> 00:24:12.720
Yeah.
00:24:17.320 --> 00:24:23.680
And they've added functionality to logic that apparently you can't upgrade to because you're
00:24:20.140 --> 00:24:30.400
Yeah. Right. Yeah. I'm on Catalina. You know, it shouldn't be taken necessarily as an indicative,
00:24:23.680 --> 00:24:27.500
not running big sir yet yet.
00:24:30.740 --> 00:24:36.320
but you and I being as close as we are in hearing your war stories there, I am not tempted
00:24:36.320 --> 00:24:42.020
at all to go to Big Sur until I get the chance. That, of course, is not to say that I will
00:24:42.080 --> 00:24:50.120
have the same issues doing that. So anybody listening, don't let that sway too much. It's
00:24:48.840 --> 00:24:50.240
Yes.
00:24:50.120 --> 00:24:53.380
And, you know, things that you want to take into consideration.
00:24:54.100 --> 00:24:59.980
If you're relying on your system for your living, then, yeah, be a little hesitant,
00:25:00.340 --> 00:25:05.240
check out user groups, and wait a while, you know, unless you're, you know, one of those
00:25:05.300 --> 00:25:09.400
people that you like to carry a sword in one hand and a torch in the other and just, "Let's
00:25:09.160 --> 00:25:14.820
Well, and I generally like to do that. It's just that this wasn't the most pleasant experience,
00:25:09.500 --> 00:25:10.920
go, let's do this," you know?
00:25:15.020 --> 00:25:19.400
and I'm still kind of dealing with it even after a week and a half, which is not to say
00:25:19.400 --> 00:25:23.600
that I'm not working, I'm back to working. It's just there's little functionality things
00:25:23.720 --> 00:25:30.260
that may require me to actually install the OS yet again, which is a drag, but I'm not
00:25:27.740 --> 00:25:29.140
Yeah.
00:25:29.140 --> 00:25:29.260
Yeah.
00:25:30.320 --> 00:25:35.760
against it. And the bigger thing, I know that you're not one of those people to constantly
00:25:35.940 --> 00:25:41.500
wipe your machine and start fresh. I am. I feel like it's just because the new OS is
00:25:37.260 --> 00:25:39.140
No, no, I'm not.
00:25:39.400 --> 00:25:39.580
Yeah.
00:25:41.580 --> 00:25:48.240
probably going to have weird anomalies with the old OS, that kind of thing. So me having
00:25:48.240 --> 00:25:53.380
problems having upgraded want to clean machine is a little strange.
00:25:54.039 --> 00:25:55.360
You know, I can see the point
00:25:55.500 --> 00:25:57.360
'cause I've had both experiences.
00:25:57.540 --> 00:26:02.820
I've had cases where just doing the upgrade has been absolutely fine.
00:26:03.840 --> 00:26:08.320
But then in my experience, it's been also that, you know, you do that
00:26:08.700 --> 00:26:10.620
twice, maybe even a third time.
00:26:11.400 --> 00:26:13.240
And then weird things start happening.
00:26:13.440 --> 00:26:19.040
I had that happen when I made the jump to Mojave.
00:26:19.660 --> 00:26:23.480
And it's like, yeah, it slowed my system down to a crawl.
00:26:23.640 --> 00:26:25.480
It was like, this is not happening.
00:26:25.900 --> 00:26:27.620
Now, thankfully, I have a separate system.
00:26:27.650 --> 00:26:30.600
I have my laptop system that I like to check things on.
00:26:30.780 --> 00:26:31.000
Okay.
00:26:31.360 --> 00:26:33.800
And it was similarly specced to the main machine
00:26:33.810 --> 00:26:34.800
I was running at the time.
00:26:35.260 --> 00:26:37.900
So I didn't lose functionality at that point,
00:26:38.000 --> 00:26:42.320
but then I wiped it clean and fresh installed
00:26:42.540 --> 00:26:44.340
and everything was beautiful.
00:26:45.200 --> 00:26:48.180
And I think it has to do with just old code
00:26:48.640 --> 00:26:51.360
being overwritten and old preference files
00:26:51.580 --> 00:26:53.940
and all this kind of junk that just kind of stays there.
00:26:53.780 --> 00:26:57.080
Well, that's a key thing that you just said right there, those old preference files, which
00:26:54.220 --> 00:26:56.520
and yeah
00:26:57.180 --> 00:27:00.020
is why I like to wipe clean and just do a fresh install.
00:27:00.420 --> 00:27:05.840
The other thing it causes me to do is take stock of what am I actually using?
00:27:04.220 --> 00:27:04.620
yeah
00:27:06.200 --> 00:27:07.000
What do I need to keep?
00:27:07.180 --> 00:27:08.740
What do I not need to reinstall?
00:27:09.660 --> 00:27:15.840
And in addition to that, when developers are updating software, you get the freshest install
00:27:15.900 --> 00:27:16.660
on a clean OS.
00:27:17.080 --> 00:27:18.640
That's the best way I like looking at it.
00:27:19.120 --> 00:27:22.260
And I don't mind taking the time to do the install.
00:27:19.179 --> 00:27:19.540
yeah
00:27:23.020 --> 00:27:26.040
If everything's clean and it's awesome, I'm good, I'm cool.
00:27:26.760 --> 00:27:29.740
But one other thing you need to think about, and it's interesting you bring up the fact
00:27:29.840 --> 00:27:32.920
you have your laptop and then you have your other machine and they're similarly the expect,
00:27:34.100 --> 00:27:36.920
is can your machine actually run the new OS?
00:27:37.920 --> 00:27:37.960
Yeah.
00:27:37.960 --> 00:27:38.040
Yeah.
00:27:38.080 --> 00:27:42.300
Because running a new OS on an old machine could mean that your processor is suddenly
00:27:42.380 --> 00:27:46.120
going to be like, "Motherfucker, I'm getting hot!"
00:27:44.380 --> 00:27:45.280
Yeah.
00:27:46.120 --> 00:27:46.580
[laughs]
00:27:46.820 --> 00:27:47.020
Absolutely.
00:27:47.480 --> 00:27:47.900
Yeah.
00:27:48.120 --> 00:27:51.160
It's one of those things that it tends to be.
00:27:51.160 --> 00:27:56.760
to, you know, make use of the newer chips and all the power and stuff that comes along
00:27:56.920 --> 00:28:04.000
with newer machines. And it doesn't mean that your old machine can handle it. And sometimes
00:28:04.160 --> 00:28:09.920
it's even worse, like we upgrade to what we think is going to be better. And it just worsens
00:28:10.020 --> 00:28:14.420
everything because it's so slow and it's sluggish to do what we used to take for granted.
00:28:14.760 --> 00:28:20.560
So the upgrade doesn't. Yes. Yes.
00:28:15.800 --> 00:28:19.520
However, sometimes those upgrades can make things faster.
00:28:20.040 --> 00:28:23.120
And as my experience in this last week and a half
00:28:23.300 --> 00:28:26.280
has proven to myself other than the other weird anomalies
00:28:26.380 --> 00:28:28.160
that are happening with Catalina,
00:28:28.680 --> 00:28:31.740
my machine would take forever to boot up.
00:28:31.760 --> 00:28:32.520
Yeah.
00:28:32.460 --> 00:28:34.500
But once it was booted, it was lightning fast.
00:28:35.000 --> 00:28:38.400
With Big Sur, my machine boots up instantly.
00:28:38.460 --> 00:28:39.860
Wow.
00:28:38.700 --> 00:28:39.580
It's fast.
00:28:39.860 --> 00:28:40.020
Wow.
00:28:40.520 --> 00:28:42.620
However, there's a couple of other things
00:28:42.800 --> 00:28:44.960
that have slowed down a little bit.
00:28:45.440 --> 00:28:50.880
And that is opening sessions with plugins that aren't quite
00:28:51.240 --> 00:28:52.400
Big Sur compatible yet.
00:28:52.640 --> 00:28:55.120
So I do have a couple of plugins that are running in
00:28:55.260 --> 00:29:00.260
Big Sur, but they are not Big Sur compatible, even though
00:28:56.860 --> 00:28:57.200
Mm-hmm.
00:28:59.800 --> 00:29:00.780
Gotcha.
00:29:00.340 --> 00:29:01.680
I've got the latest installers.
00:29:01.800 --> 00:29:05.260
And those cause sessions to load a little bit slow.
00:29:05.640 --> 00:29:07.100
But once they're open, they're running.
00:29:05.960 --> 00:29:06.220
Yeah.
00:29:07.940 --> 00:29:10.740
I'm not noticing any speed difference there.
00:29:08.340 --> 00:29:08.820
They're fine.
00:29:10.860 --> 00:29:12.780
It's just opening a file once in a while.
00:29:12.900 --> 00:29:13.800
It's just a little bit slow.
00:29:13.980 --> 00:29:15.380
Yeah.
00:29:14.880 --> 00:29:18.340
And I have no idea how that would work between Windows 10 and Windows 11,
00:29:18.500 --> 00:29:19.860
but that might be the same case.
00:29:20.000 --> 00:29:23.760
Even though somebody's got Windows 11 to run on a really old PC,
00:29:24.320 --> 00:29:28.540
it's probably not running efficiently is the best way to think about it.
00:29:27.130 --> 00:29:27.560
Yeah.
00:29:27.560 --> 00:29:27.720
Yeah.
00:29:29.400 --> 00:29:32.060
So now we're on this topic of talking about
00:29:32.280 --> 00:29:33.340
reinstalling everything.
00:29:33.980 --> 00:29:35.920
I just want to say that I'm one of those people
00:29:36.280 --> 00:29:40.620
that I am firmly planted in the pro-iLock camp.
00:29:40.660 --> 00:29:41.760
I'm right there with you.
00:29:42.300 --> 00:29:43.940
Because when you do a clean install,
00:29:44.520 --> 00:29:48.280
it's so much easier to just, you reinstall the software,
00:29:48.840 --> 00:29:51.620
plug in your iLock and boom, you're good to go.
00:29:51.940 --> 00:29:53.000
Mm-hmm, agreed.
00:29:52.300 --> 00:29:52.920
All right, so.
00:29:53.480 --> 00:29:56.980
That way you don't have to worry about, "Oh, God, did I not deauthorize my machine?
00:29:57.590 --> 00:29:59.000
Do I need to reauthorize it?
00:29:59.080 --> 00:30:00.940
Where's my serial number?"
00:30:00.940 --> 00:30:02.040
That stuff sucks.
00:30:01.780 --> 00:30:04.060
I think so too.
00:30:02.940 --> 00:30:03.940
There's no question about it.
00:30:04.140 --> 00:30:05.020
I just hate it.
00:30:04.370 --> 00:30:04.800
Yeah.
00:30:05.490 --> 00:30:05.960
Yeah.
00:30:06.160 --> 00:30:07.500
So I'm with you on that.
00:30:07.640 --> 00:30:09.200
The iLock is so much better.
00:30:09.520 --> 00:30:11.320
Install the software plug in the I lock.
00:30:11.420 --> 00:30:13.220
You're good to go and you're ready to rock.
00:30:13.600 --> 00:30:14.540
I agree.
00:30:13.610 --> 00:30:18.540
And with that, let's talk about our Friday finds for this week.
00:30:18.620 --> 00:30:19.880
Chris, what have you got?
00:30:20.500 --> 00:30:25.520
Well, I haven't got this, but my find for this week is, of course, it was announced
00:30:25.610 --> 00:30:31.480
the new MacBook Pros that came out with the new M1 chip.
00:30:28.500 --> 00:30:29.020
Hmm.
00:30:31.660 --> 00:30:33.880
It's going to be the M1 Pro or the M1 Max.
00:30:34.800 --> 00:30:35.260
Yummy.
00:30:35.580 --> 00:30:39.260
And yeah, the specs on that just look amazing.
00:30:40.340 --> 00:30:46.100
I've been asking for for the first iteration of the max silicon was the the RAM limit, right?
00:30:46.280 --> 00:30:46.580
Mm-hmm.
00:30:46.780 --> 00:30:54.840
Now you can go up to 32 and 64 and more processors and yeah, they just look sexy as all hell, man.
00:30:55.120 --> 00:31:02.920
So that has to be yeah, yeah, so that that has to be my Friday fun for this week. What about you,
00:30:55.880 --> 00:30:57.620
You ready to have sex with the machine?
00:31:02.920 --> 00:31:03.700
Jody what do you got?
00:31:03.679 --> 00:31:10.880
I'm going in with something a little bit different. I'm looking at the Roland Zenn tracker and that is a brand new DAW.
00:31:11.720 --> 00:31:12.700
Not really a DAW,
00:31:13.560 --> 00:31:17.320
But it is a multi-track audio program for your iPhone and your iPad.
00:31:18.500 --> 00:31:23.300
Put out by Roland, where you can then record audio multi-track form.
00:31:18.800 --> 00:31:19.260
Okay
00:31:23.400 --> 00:31:26.420
It's kind of like going back to a task and port of one in a sense,
00:31:26.580 --> 00:31:28.420
but you're doing it with a phone or your iPad.
00:31:29.040 --> 00:31:33.400
So I'm looking at the Zen tracker. I'm going to check that out. Yeah.
00:31:32.280 --> 00:31:34.820
Cool good. All right, awesome
00:31:34.280 --> 00:31:35.900
And while we've got your attention,
00:31:36.300 --> 00:31:39.399
we would like you to go to our website and leave us a review at inside the
00:31:39.400 --> 00:31:46.520
recordingstudio.com/review or just go to inside the recording studio.com and sign up for our email list.
00:31:47.300 --> 00:31:51.040
Doing so gets you weekly reminders about the Tuesday tips that we put out
00:31:51.480 --> 00:31:56.580
and we'll make sure you don't miss any episodes in the future. Plus the extra bonuses when you're on
00:31:56.660 --> 00:32:02.119
our email list and we're doing a giveaway, you're automatically entered for that giveaway. How cool is
00:32:02.120 --> 00:32:07.560
that if you send us an email to goldstar g old s t a r at
00:32:07.640 --> 00:32:11.460
inside the recording studio dot com with the phrase operating
00:32:11.620 --> 00:32:15.800
system, you will get something cool back in your inbox. If you
00:32:15.840 --> 00:32:18.940
have a topic of suggestion for Chris and I to explain in a
00:32:18.980 --> 00:32:23.660
future episode, contact us on the contact page at the website
00:32:23.840 --> 00:32:26.340
and we'll put it into consideration for a future
00:32:26.680 --> 00:32:31.440
episode. And with that, I'll say see you next week.
00:32:32.260 --> 00:32:34.340
we go on jody thank you for listening everybody
00:32:59.840 --> 00:33:01.240
සම�
