Transcript
[0:00] Music.
[0:06] Podfeet.com a technology geek podcast with an ever so slight apple bias. Today is Sunday the 28th of January 2023 and this is show number 925. In this week's show you'll hear my third and so far
last installment of my Stream Deck series where I descend further into my madness plus a contribution from Stephen Getz on how he abandoned the Adobe subscription train and ended up on the
Adobe subscription train. But first, Bruce from Tennessee joins us again to talk Finder and Terminal and how to make them play well together.
Finder And Terminal In The Same Window – Fun With Scripts — By Bruce From Tennessee
[0:45] Hi, this is Bruce from Tennessee, also known as Use the Data, with a tip for working with the Finder and Terminal. The problem to be solved is that when working with files, I find some operations to be easier in the Finder,
and others to be easier in the terminal.
And there are times where I need a terminal window open to the same directory as my current finder window.
There are also times when working in an existing terminal window, where I want to either have a finder window open up in that same directory,
or get my terminal window into the same directory as an existing finder window.
[1:28] As Alison reminded me, we've seen some ways to do part of this from the Finder. As explained in an October 2021 tiny tip, like in the show notes, the path bar in Finder is powerful.
And you can use the option click on a folder in the path bar to open a terminal window in that particular directory.
So that's one way to solve one of the three cases.
But how can I deal with the other two cases?
The answer is a bit of shell script work that I'll describe in a minute, but let me first describe the results.
So when I'm in a terminal window on my Mac, I can simply type cdf, short for change directory to finder,
and that terminal session will now be in the same directory as the frontmost finder window.
Going the other way, I can type f here, short for finder here, and I get a new Finder window opened up in that same directory as my terminal session.
So if that's not useful for you, then feel free to fast forward to the next chapter in the podcast or move along to another blog entry.
Now, I've had this capability for a long time.
[2:47] But in Alison's call for some content, it occurred to me to share this with the Nusayla castaways. The answers come from Brett Terpstra in a blog post that is just under a decade old now,
and links to both Brett's site and that specific post. I was pretty sure that this had come from Brett and his site, like Alison's, has a great search feature, so finding that post wasn't that
hard once I went to go look for it. However, several things have changed about macOS since 2013,
and some of those changes affect what we need to do to make this work in a current version of macOS.
[3:30] When Brett wrote his article, macOS used something called bash as the default shell in the terminal. Starting in 2019 with macOS Catalina 10.15,
the default shell is now something called ZSH.
[3:47] For a large fraction of the things that a user might do in the terminal, there's no difference.
But if you want to customize your environment, the differences are significant. For more about Bash, ZSH, and other shells, go all the way back to taming the terminal part one of N.
[4:09] Blank in the show notes.
Bart and Allison also provide a lot of information about customizing your terminal environment in taming the terminal parts 13 and 14.
Again, blanks in the show notes. And over in programming by Stealth, the dynamic duo have also provided great information on these configuration files, managing them,
particularly in episodes 121 and 122.
[4:40] So if you've set up a new user account on a Mac at some point starting with macOS Catalina, you're most likely using ZSH and Brett's instructions won't work for you.
If you've carried forward a user account either with Migration Assistant on a new Mac because Macs last a long time.
And you're running a Mac that came out of the box with something before 10.15 Catalina.
You're probably using bash. You can use Brett's instructions to set up the commands, although I go into a bit more detail in the posting.
So how do you tell whether you're using the new zsh or bash? There's a few different ways to do this, but a simple way that's worked every place I've tried it is to type echo $number0 in terminal session.
[5:33] Followed by a return.
The results will tell you if you're running zsh or bash. If it says bash, just follow Brett's instructions and you're good, although like I said, I use a slightly different name than he does for
one of the commands. If you're running zsh, then you need to edit your.zprofile file rather than the.bash underscore profile file that Brett describes and the incantations for my cdf command
are slightly different. Bart and Allison describe editing text files like this.bash underscore profile and.z profile from the terminal in Taming the Terminal Part 11 event,
like in the show notes and they use the nano editor. Following that guide while working in the terminal you could type nano space tilde slash.bash underscore profile if you're running bash,
or you could type nano space tilde slash dot z profile if you're running zsh.
The tilde and slash are there to make sure that you're editing the file that's in your home directory regardless of what directory you happen to be running at the moment.
[6:47] For bash you can copy in the lines that I show in the show notes. They've used a slightly different abbreviation for open a finder window here than Brett did.
And so there's a slight difference from his blog post. If you're running ZSH, then it's a slightly different set of lines, again, shown in the show notes.
[7:09] If you're wondering where to put these lines in the file, just add them to the end, then save the file using Ctrl-O to quit, and then quit Nano with Ctrl-X. Quit the terminal app and then launch a new terminal window. The CDF and F here command should now work for you. The way,
to create my F here command is the same for the two shells, but the syntax to create that CDF command is a bit different.
For those who are interested, that CDF command is invoking a bit of Apple script to get the directory for the front-most file finder window.
It's also interesting to me as a command line aficionado as being an example of using all three types of quotes in one line.
Bart and Allison go into the two of the three types of quotes in Programming by Stealth, episode 143 of X, link in the shout outs.
The third type of quote, the so-called back tick, which is above the tab key on my US keyboard, is there to tell the shell to execute this command and give me the results as a string.
[8:19] I hope you found this to be a useful tip and my thanks to Brett Terpstra for figuring all of this out and posting it on the internet, and to Bart and Allison for their great work in both taming the terminal and programming by stealth.
Peace and may you find beauty in the world around you. Thanks for that contribution, Bruce.
I think I'm going to set up those commands for myself because when I develop scripts to solve a problem, I always end up using both finder and terminal.
It is certainly a pain point getting them both to be in the same place, particularly if I'm using multiple directories.
The only thing that's missing for me is something to remind me to use them. Now it's time for Stream Deck Down the Rabbit Hole, part 3.
Stream Deck — Down The Rabbit Hole, Part 3
[9:04] At the end of part two I had a really useful set of buttons, many with nice button faces, and I was looking into how to get live information to display on a button.
[9:13] I knew there were plugins that did this for their specific functions, but I could not figure out how I could get my own information shown.
[9:21] I posted a question on the MacPowerUser's forums, and was pointed to an application called BetterTouchTool, or BTT for short. I'd looked at this software before, and even and trialed it, but I didn't really see myself using custom gestures on my mouse or trackpad,
which were its flagship feature.
However, now I was being told it could handle Stream Deck buttons.
I checked it out and was amazed at the feature set included in this software.
At its core, BTT has many types of triggers and many types of actions, and you can wire these together in any way you can imagine.
The triggers include the aforementioned custom gestures, but also keyboard shortcuts, text snippets, Siri remotes, MIDI device controls, a BTT remote app on your phone, the MacBook,
Pro Touch Bar, and, as of a recent version, the Stream Deck.
Actions include, well, everything.
There are 15 different categories, with actions like sending a keypress to a specific application a requirement I mentioned in part 2.
Performing a mouse click, hiding an application, running a script, opening a URL, resizing a window and putting the computer to sleep.
In all there are over 150 defined actions, and while many are very specific, like press F19, some are very flexible, like run a script or send a key to an application.
[10:47] BTT addresses the Stream Deck in one of two ways. You can either install a native Stream Deck plugin, which BTT will then communicate with, or you can quit the Stream Deck software altogether,
and have BTT completely control the Stream Deck. I dipped my toes in the water with the plugin until I got an idea of what could be achieved, then very quickly went all in with full control.
Because I made this leap fairly early in my Stream Deck journey, there may be things I mentioned here in the context of BTT, which are in fact possible with the native Stream Deck software.
[11:22] The BTT interface is fairly straightforward. Where I disliked the clunkiness of the Stream Deck software, BTT is a lot more obvious to me, though it does have some quirky bugs you will almost
certainly have to work around. One is when deleting actions from a trigger. It doesn't seem to like deleting more than one at a time. I must get around to reporting that one.
[11:46] The application is hierarchical in the way it works. On the left is a list of applications. There is a special entry of all which contains triggers and actions that will apply regardless of the currently focused application.
Then you can set up triggers that only appear when the named application is focused. A good example of the usefulness of this is having buttons on my stream deck to set finder which only makes sense when Finder is the focused application.
On the other hand, my light controls make sense no matter which application has the focus.
[12:21] The next level is the trigger types. There are separate sections for stream deck, touch bar, keyboard, mouse, etc.
This makes a lot of sense as the different trigger types have quite different requirements. There is no need for example to have an icon for a keyboard shortcut like there is for a stream deck button.
[12:40] Next is the groups and top level triggers. I should preface here that I've mostly only worked with stream deck and touch bar triggers thus far.
[12:49] Groups on the stream deck manifest as a button which, when pressed, opens up a whole new set of buttons. I have all my light controls in a group for example.
[12:59] The first action to set up a stream deck button is to add a trigger which, broadly speaking, represents a single button. You then get to configure the button, including some rules for when it will appear,
such as based on modifier keys being held down or only on certain Stream Deck devices, if you have more than one.
[13:19] You can also position the button explicitly or leave it to BTT to flow into an available spot on the device.
[13:27] The other aspect to buttons is their appearance. Delightfully, BTT has built-in support for SCF symbols, so you can easily create decent looking buttons with very little work.
You can also put regular text on them and there are controls for colors and sizing and positioning of the symbol or text and color of the background. My preference is to create my own image and this
can be very simply dragged into the configuration. There is an oddity in how BTT handles custom button images. It seems like it wants a 96 pixel square image by default. However, I have conclusively
proven that my actual Stream Deck buttons are 72 pixels square. I just create my buttons at 96 pixels and drag them in and it all seems to work, so it's not a problem as such unless you're trying to be pixel perfect. With basic configuration and appearance set, the real fun begins, adding the actions.
[14:22] Unlike Stream Deck's clunky multi-action action, VTT expects you to add multiple actions. My longest one to date has 26 actions.
Adding actions is fairly straightforward, although another bug rears its head here.
When you add the first action, the application jumps back to the top level of its hierarchy, so you do not immediately get to edit your action.
If you're in a group, this is quite disconcerting as you're taken back out of the group. group. It's easy to just go back into the action but there are a few papercut bugs like this.
As soon as you have configured any triggers and actions they are live. Though with groups it seems you have to exit the group and return to see new buttons or new imagery on existing buttons.
[15:09] So I have described a greatly expanded, if somewhat buggy, version of the native Stream Deck software. Is that worth the price of BTT? I think so, because it has a much wider array of capabilities for the
Stream Deck and even with the bugs, it's easier to build up complex action sequences and also to have your buttons adapt to the current environment. Then you can add in all the other capabilities of
of the software. I have a touch bar equipped MacBook Pro. I've never been against the touch bar, but neither had I really made much use of it, until I got BTT. Now I have a battery percentage and charge time indication, the latest readings from my personal weather station,
which opens my weather underground webpage when tapped, a list of ejectable drives, which ejects those drives when tapped, and an indicator of current Bluetooth status, which toggles Bluetooth on or off when tapped. For me, the main thing BTT has enabled is total,
nerdery. In part one I described how I set the lights in my study for my nights on call. That process has changed a few times and currently does this. One, turn,
off the canvas light panels. Two, set all of the room lights to bright green for four seconds. Three, set all of the room lights to bright orange for four seconds.
4. Set all of the room lights to bright red for 4 seconds.
[16:37] 5. Drop the brightness of the room lights to 10%. 6. Set my Mac screen brightness to 10%.
[16:46] 7. Set the Stream Deck brightness to 10%. This takes a total of 26 steps, mostly calling a shell script I developed as a wrapper for very long home control URLs.
My current Stream Deck configurations include The Lighting group with 5 buttons for room light control, 5 to set scenes on the canvas, and 4 to set the canvas brightness to fixed levels, including off.
The Microsoft Teams group with 9 buttons.
A Laptop battery level indication. This button doesn't do anything, but its appearance is set by a shell script, so it shows me the current battery percentage.
7. Finder Tag Buttons, 6 colors and are clear, that appear only when Finder is focused. These run on Apple script, which in turn calls a shell script.
A group of 10 buttons that appear when DxO Photolab is focused, which give access to commonly used tools.
An additional group of 8 buttons for Photolab for its local adjustment mode.
[17:46] A button for the Citrix viewer application that presses a special key to invoke the Windows insert key, which is not present on Mac keyboards.
And a button for terminal that enters the SSH command to my web server.
That's 51 buttons in total, not counting the group buttons, using a variety of action types.
I think I've only just begun.
Steven Goetz On Returning To Adobe Lightroom (No Blog Post)
[18:10] Next, Allison sneaks in again for a chat with Stephen Getz about Stephen's journey through software for his photography.
Well, hey, I'd like to interrupt your regularly scheduled programming here. This is Allison, and I want to do this to introduce the NusillaCast audience to one of my best friends I have never met, Stephen Getz.
Welcome to the show, Stephen. Hello.
How are you today? I'm doing pretty good. So you have heard Stephen in a review or more than one that he has done over the years, but this is the first time he and I have taken the time out to actually have a conversation.
And if you've listened to this show for any length of time, you know that I get advice and help from Stephen all the time. He lives in Ontario, Canada, and I live in California, which is why we've never met.
But in a very odd turn of events, my daughter Lindsay and her husband Nolan were vacationing near where Stephen lives, so the three of them met up for a beer and I am still jealous that you got to meet them, Stephen.
[19:06] Yeah, that was seems like forever ago because it was the before times. Yeah. But hey, they got to meet you and I didn't. It doesn't seem fair.
Well, in any case, I asked Stephen come on the show to talk about his ongoing personal struggles with his relationship with Adobe for photography. He's a pretty serious photography guy shooting with a big girl Canon DSLR.
It's a funny conversation, I think, because it has to do with trying to divorce himself from Adobe and yet coming back over and over again. So can you start at the beginning of the story?
Like, why did you leave Adobe Lightroom? What is Adobe Lightroom? What is it used for? Start at the beginning of the story.
So I guess I'll start out with Lightroom. And Lightroom is a software for organizing and editing and tagging and sharing your digital photos.
[19:58] And it's been around for a very long time. I started out using iPhoto back in the G4 iMac day. And then I moved on to Aperture, which was a more pro tool.
And I loved Aperture because it would organize my library and it had the really good editing tools and it just works the way I work.
Work. Yeah, you could actually do like brush level editing, like you could brush in a burn or a color change and things, right? Yeah, and the tools worked how I like wanted them to work.
When I moved the adjustments, like the black and the highlights and shadows, they moved how I expected them to move, if that makes any sense. But Aperture abandoned that product, so I had to,
or Apple abandoned aperture.
So I had to find an alternative.
So back then, this is probably five years ago, maybe longer, I moved to Adobe Lightroom.
And it was a tool that worked really well. It organized photos very well and tagging worked the way you would expect it to work.
And the tools were at the time, state of the art tools for noise and editing and changing how your foot raw processing.
I mostly use Lightroom for almost entirely raw photos from my Canon DSLR.
[21:27] Anything like from my iPhone, I just use photos, Apple photos for. So interesting. I keep those two lives separate.
[21:35] Um, but, uh, so app or Lightroom didn't, I wasn't as happy with Lightroom as I was with Aperture, but Aperture was dead.
And I've always learned that once the product dies to move on from it, instead of trying to make, instead of trying to make it work for me longer than it is intended to, if that makes sense. Right. Right. Like Dan Morin said, quit it before it quits you.
Yeah. Well, especially with Apple, because once they abandoned things, they'll update the operating system and then you're like doing like hacks to try just to get it to work with the newest version of the operating system.
So the other problem is if you do it late, I found that you end up being one of those people asking the question about how to migrate when everybody's forgotten how to migrate.
Oh, exactly. And all the information you'll find is two years old and they've changed how it works were because they don't need to worry about that.
Cause, but, um, so I moved on to Lightroom and Lightroom met my needs, but the, the niggles with Lightroom for me are the subscription. They're, uh, a subscription model.
So you have to pay monthly for Lightroom.
And you pay for just Lightroom.
So you can, but it's actually, it's more, it makes more sense to pay for, they have packages for the Creative Cloud and it goes all the way up from every single piece of software they make in one subscription price to, uh, to like individual software programs, but I, I'm, I used the photography bundle.
[23:04] Which there's different versions of it that give you online storage, which I don't use. But the plan I have, you get what they call now Lightroom Classic,
and you get Lightroom, which works, which is on the iPad, and on Mac OS and Windows and all the operating systems you can think of.
I just use Lightroom Classic. I don't use what they would call Lightroom now.
[23:28] Interesting. So you have Lightroom, you get Lightroom Classic and Lightroom? Correct. Yeah and Lightroom works more. It's better. It's designed to use on the iPad So it works differently than Lightroom classic, which is more mouse oriented. I guess. Okay is how I would describe it,
Okay So you don't you don't rent Photoshop. Oh.
[23:48] So it does have Photoshop too. Yes. Oh, yeah. Okay. Sorry. I don't use it very often. I Use I use affinity photo if I'm going that nitty-gritty,
but Anyway, but yeah, it does light or so it's photo. It's lightroom Lightroom classic and Photoshop in a photography bundle and it's like.
[24:09] Twelve dollars Canadian among I think is what this option is right now and if you buy it the right time it can get a deal on it and be cheaper or more expensive if it's not the right time, but.
[24:21] So I I I don't know. I don't remember exactly how I found a a product, there's a company called DxO, which I've read their camera reviews for a very long time,
because they take cameras and they review the sensors and give them a score.
Wait a minute, that's not the same, that's not DP review. No, DP review is a website, but DxO does lab testing.
Although they're super pixel peepee people, right? Yes, exactly. So I've heard of DxO before, And they make software for... They make software for.
[24:59] Processing raw photographs. So Graham Shepard just talked to us about DXO something recently and Alistair's talked about DXO something.
I think what he uses is PureRAW, I think, and that is that is what, that is their engine for rendering raw files.
Okay. And the software that I use is Photolab, which is by DXO, and that matches their rendering with a library module. so you can organize and edit your photos at the same time. Okay, so it's a Lightroom equivalent.
Yeah, or photos, Apple Photos, the Mac app. Just think of it as a more, just like Aperture, a more pro version of that.
Okay, so the main reason that you looked at DxO, sorry, Photo Lab was because you were tired of paying the subscription.
Was there any other reason? I thought, I always felt that Lightroom, the editing was a little clunky on it.
And this was before they've added a lot of features since I had switched away a couple years ago. So we'll go back to that later.
But the editing was just a clucky feeling. It just felt more like a Windows piece of software that I was running on my Mac.
Because it's a walls multi-platform, right?
[26:17] Let me interrupt really quickly here because we haven't necessarily defined for non-photographers that raw photos basically contain more information.
They, I'm not going to get into depth and that sort of thing, but they contain more information that you can do more editing to get higher dynamic range within your photos.
And then you can compress them down into a JPEG. What you would standard see or like, like HEIC sort of on the, uh, on the iPhone, but it's basically just more information, big files.
You edit, you can do a lot more to edit them, bring out shadows, uh, bring down brightness and get a better picture.
I just want to interlude that. So I ran into DxO, it was Photolab 4 at the time.
And it was probably around, I want to say it was the fall. It was in the fall.
Because I tried the trial of Photolab 4, and I ended up finding Photolab 5 on sale, and I purchased Photolab 5.
Because if you wait until it's on sale, you can get it for $70 US dollars. And it's no subscription, so you can use it forever for that $70.
So that was less than a year of like, so I thought, you know what? I'll try it for a year and see how I like it.
[27:32] Oh, that's a good idea. Okay. Because I saw that it makes nicer looking, it renders the photos nicer. The more to me anyway, the with less work, if that makes sense.
Like you have to do, it's a lot less fiddly to get the pictures to look the way you want or the way I like them anyway.
Everyone has their own preferences, but it's got some advantages over Lightroom. Like it's no subscription.
They updated all the time.
[28:01] So they're doing bug fixes and adding features in the year after you've bought it. So a lot of software, once you buy it, they don't update it, but Photolab is very good at tweaking things that don't work properly.
So it looks like they do paid upgrades pretty often though. DxO Photolab 6 is out.
It comes out about once a year.
Okay. And so you get bug fixes, but maybe you're tempted by the next one? Correct.
Yes. Yeah. So you might end up with the same cost that you did if you did Lightroom. Exactly right. Especially if you don't, if you just, if you don't wait for when it's on sale.
Now they put it on sale quite often, but if you're like at the wrong time and then you don't know they do the sales, then you end up paying a lot more for it than you needed to.
Yeah, that's $139 for the essential edition right now. Yeah. And you don't want the essential, you want the other one because it's got Oh, good grief.
You want to hire the more expensive one? Yeah. Holy cow, that's $219. Yeah.
So if you buy it on sale though, you can get it that the you can get the the The non the what I forget what they call it now But you can get the full package for like 70 or 100 dollars, I think so elite. Yeah elite. That's what they call it,
Okay, so um but it's killer feature to me is it's um.
[29:17] It has very, very good lens correction. And that comes from their camera testing.
So they, because they test every, not just the camera body, they test the camera body with specific lenses.
And then they, I don't, I don't know exactly what the secret sauce, the how they do it, but they have profiles for body and lens together.
So this is a correcting like for lens distortion on the edges. Yeah.
Yeah, and it does sharpening in spots that it knows that lens is soft.
Because some lenses have like, they'll have a spot that at certain F stops and focal lengths are soft in certain spots in the frame.
And it will magically apply sharpening in just the spots that it needs it. So it doesn't over sharpen the other spots.
[30:07] That's cool. It's very smart. Their lens pressure is very good. And it's again, it's not just like, oh, it's cause it's a, it's a 80 D or whatever.
It's right down to that lens and the camera together.
So, um, and it, they also have very, very good, uh, noise reduction. They call it deep prime and they iterate it probably once a year or two. I think it's like deep prime plus or something now.
Okay.
Is that, so is that a separate package you can buy standalone? I think they have a standalone tool. Cause they, they bought Nick. I don't know if you remember Nick.
Yeah. the Nick plugins, they bought Nick.
And some of the Nick stuff shows up in there in...
[30:48] In PhotoLab, you just don't know that's where it's from. Okay.
I recognize controls from the Nick plugins that I used to use with Lightroom like forever ago.
Okay. But its noise reduction is very good. I think it uses AI, but everything uses AI.
Now it feels like... Steven's had me send him a couple of photos of my own where I know I've done everything I can to fix the noise, and he sends it back and I've just been blown away. That's pretty cool. So that's something to look at right now, $129 for pure raw.
Yeah. So pure rod gives you deep prime and the lens correction, but without the organizing bit, if that makes sense.
[31:27] Okay. And so you can use it if you are comfortable with photos, but aren't Apple photos, but aren't happy with the editing tools, which is I did try photos, but I don't like, I can't edit with it.
I tried. I gave it a really good shake because why buy software if I have, if I'm already paying for software, why not? Right.
But I just couldn't. Yeah. Sadly, they don't support Apple ProRAW and they're saying because ProRAW is not a true raw format, it's an Apple proprietary format.
So yeah, it has something to do with having to use Apple's software to do it and that they don't have that built into there or something.
Okay.
Lightroom does it, so I don't know. Adobe's also a lot bigger than DxO.
Right. Okay, so you're happy now you're in DxO Photo Lab, you've got this great organizing tool, you've got great software tools for editing your photos. But then you went back.
Yes.
So I wasn't happy with the...
I will say DxO still has a lot of work with the organizing tools, part of their tool. It just didn't...
It's really hard to explain. It just didn't...
[32:40] I just found myself always looking for photos when on Lightroom I could find them a lot easier. Even tagging. Tagging tools are not great in DXO. Again, they're getting better.
And they're a lot, at six apparently is a lot better than five. And five is a lot better than four.
But I just thought if I, before I bought six, I really thought I was going to give Lightroom another chance because they have a trial. So I thought, try the trial. I just find Lightroom's organization more natural to how I work.
Did you feel like you were coming home when you went back?
Yeah, it almost did. Yeah.
And again, DxO is not bad.
And I would definitely recommend it if someone wanted to try something other than Lightroom.
But it's just, again, it was like coming home to how it worked. And the same with the editing tool. Again, DxO's tools are very good.
They just, I don't know, it's hard to... It's just they work...
[33:32] Lightroom works the way I like it to work in the way I would expect it to work. And in the time I have available to sit down and work on my hobby, Lightroom let me do more in less time.
So are you nutty with your tagging the way Alistair is? No, I'm not.
Alistair is massive architecture. I'm not sure anyone else on earth is as nutty as Alistair is about the tagging.
[33:57] No, I generally just tag. I really hope this plays during Alistair's show so he can do the rebuttal.
I just tag, I usually tag like the event, like, like, uh, son's birthday or, and the people in it and the place because my camera doesn't have GPS on it.
So not all my photos are geo tagged.
So it might be like Walt Disney World, Jack, uh, uh, Dumbo or something like that. just so that if I'm looking for something like specific,
that I can find it just by typing out Magic Kingdom or Walt Disney World. And I don't worry about- Interesting. I just do that with in photos. I've started doing a little bit of tagging,
but for just a very specific couple of categories. But I just create an album for the event,
and I name it with that. And by the way, folders are not searchable, just so you know,
in photos, but album names are. So I create folders by quarter, by year. And then within that, I have albums and I just drag all the photos from, you know, Sienna's birthday go into a folder or into an album and then.
[35:05] Of course most my photos have have geotagging but you can now in Apple photos You can actually add the geotagging you could select a bunch of photos and say this was a Disney world Yeah, and I could do that in Lightroom to say don't.
[35:17] I don't I should I should take more time and do it because you can do it when you import them But I don't, I just import them. Maybe it's because I'm too impatient to look at them or something.
When you say tagging, is that the same as keywords? Yes. Yeah.
Okay. Okay. Yeah. Because I knew that's where Alistair had his... In fact, they probably even use them, call them keywords in here. I just call them tags.
I always get confused of the difference between the two. When you switched from Lightroom to DxO and back to Lightroom, did it retain all of your keywords?
Uh, it does because, uh, DxO and Lightroom store a lot of their information in what's called a sidecar file.
[35:56] So it'll be a little file of both of them. Leave your files on your, on their drive.
[36:05] Like they're not in a package, like photo, like photos. Okay. Not in a database.
No. So it's, it's like, you can move pictures and stuff in and out of them.
And so they store all the key words and both of them will store even edits in sidecar files.
[36:26] So you always have the original file. Yes. And in fact, I'm now running across since I moved back to Lightroom and I stopped using Lightroom for a couple of years,
there are older files that the edits are still there, even though I don't even have that old library.
Library, I like made a new library, but it's kept ratings and keywords and even the edits, like I can go in and see the, I, I redo edits a lot, but I, but, um, I could go in and see the old edit and I had done that and tweak it a little bit,
because it's all in the sidecar file, it's not in the library file.
[37:00] That's pretty cool. So this is kind of interesting. What I enjoyed about listening to you in, we text chat all the time.
We were actually looking at each other in video, which we're pretty sure we may never have done before. Maybe once. Yeah, maybe once. But we text chat eight times a day, I think. But what was funny was it was almost like you felt dirty going back to Adobe.
Well, yeah, cause everyone, like again, it's the subscription model. I really, like I like the subscription model that I don't like the subscription model.
I like the subscription model because it allows developers, big ones and small ones, to keep bringing updates to their software and know that they have a steady income to do that, right?
Like, and there's a lot of smaller people that have gone on their subscriptions and they explain why, like one password, for example, is a good one.
[37:52] And it makes sense to me, right? Because that steady income allows, makes it less of a risk to bring on staff and help you develop your software.
But I also like, it's also can be depending on the software, like for like, for me and a lot of other people, $13 a month is a lot of money to spend on their, like their hobby, right?
I guess what you've learned though by your experimental path was that it's a fair price.
Because DxO is doing much of the same kind of work and it's the same price in the end, Cause you have to, you essentially have to buy it once a year.
I can, yes. And that's what I've, that's what I've come up with. That's what I've found because it was when I was looking into buying, uh,
photo lab sick, I'm like, what's the difference if I'm going to spend a hundred dollars a year on photo lab six or on photo lab, or am I going to spend a hundred, $20 a year on Lightroom?
Like $20 is not a big difference over a whole year.
So, you know, like, so that's, and that's what I'm like, no, I'll try Lightroom again because like.
[38:56] I don't think PhotoLabs 6 progressed enough to be worth the, for the tools I use anyway, to be worth the extra hundred dollars.
I guess one of the nice things is now you have a little bit of the best of both worlds because you have the subscription for Lightroom where you're more comfortable with the library. But if you ever want to go over and use the noise reduction tools in DxO, you've still got DxO 5.
Well, what's really nice is DxO does have a plugin for Lightroom where you can round trip photo.
So I can, in Lightroom, I can choose a photo. Let's say it's a photo that's noisy, for example, or I used a less good lens. So it has like distortion or something.
I can send it to the DxO software and just use the lens correction and the noise reduction.
And then it will spit out a DNG file back into Lightroom where I can do all the other editing I like to do. so that I get the really good noise reduction,
and lens correction from PhotoLab, but then get the tools and the organization I like from Lightroom.
[39:58] Oh, that's great. That's really cool. Well, I don't think you should feel dirty going back to Lightroom. It sounds like you did a good experiment, you considered it, and I will try really hard to not mock you for paying them.
Wow, yeah. I appreciate that. Mocking is basically the central core of our relationship.
So that's a big statement I'm making there. And it goes both ways, right? Tell the people it goes both ways.
Sometimes, yeah. He's not. All right.
Well, for that, I'm going to wind you up. If people want to talk to you online now, what would the best way to do that be? Probably just my Twitter at Goatman.
I'm also on the Slack.
I don't remember what my name on the Slack is. I looked it up, you're Steven Getz. I'm Steven Getz on the Slack, there you go.
Look at that. Yeah, he's pretty active in there and like all the other lovely no silica way, so it's a lot of fun. Well, thanks for coming on. It was a treat for me to get to see you and talk to you in real life.
Well, as real life as nerds believe in anyway.
[41:05] Thanks for having me on. Thank you for that, Steven and Alison. I would just like to make a few clarifications.
DxO's two products share some DNA but serve very different purposes.
PureRAW is a raw converter. It does lens and camera corrections and noise reduction. These two features are DxO's secret source. PureRAW is a drag and drop application.
RAW files in and processed images in DNG, TIFF or JPEG format out.
[41:36] There are very few controls over the processing done.
Photolab is a full featured application like Lightroom Classic or Aperture. It has the same raw conversion engine as pure raw, but you get more control over how it works.
Then there are the library and usual processing features as Stephen described. It is worth reiterating that the more expensive elite edition is the one you want because the essential edition does not have the best noise reduction technology amongst other things.
[42:07] Also, Apple ProRAW isn't really RAW. It is synthesized from multiple lenses and already converted from the sensor data into a full RGB image. It does contain a
lot more information than the HEIC files, but DxO's secret source is decoding RAW sensor data, so even if it supported Apple ProRAW, it'd just be like using
Lightroom when it comes to sharpness and noise reduction. My journey in photo processing software has so far been Nothing, Lightroom, Aperture, Lightroom
again, Luminar, PhotoLab and most recently PhotoLab and Lightroom. Keywords are Lightroom's superpower. Stephen called me nuts for my keyword prowess and who am I
to disagree. As an example of why I use Lightroom for keywords I noted the stats of a recent session. I had 293 photos to which I applied 64 unique keywords, an.
[43:11] Average of 9 per image, and I did it in only 20 minutes, including defining 3 new keywords. It is worth noting that Lightroom Classic can be used as a
photo library manager, including keyword management, for free. If you have any questions about this hit me up in the pod feed slack.
Well that's going to wind things up for this week. If you like the content I created here, please consider checking out my photography and writing at zkarj.me. I'm an active participant
Outro
[43:43] in the Podfeet Slack, usually adding fun content to the Delete Me channel. And you can also follow me on Twitter at zkarj. Did you know you can email Alison at alison at podfeet.com anytime you like?
[43:58] If you have a question or suggestion just send it on over. You can follow her on twitter at podfeet and you can find her on mastadon at podfeet at chaos dot social.
If you want to join in the conversation you can join our slack community at podfeet dot com slash slack Where you can talk to me and all of the other lovely nocella castaways,
Remember everything good starts with pod feet dot com you can support the show at pod feet dot com slash patreon or with a one-time donation at podfete.com slash PayPal. And if you want to join in,
the fun of the live show you're going to have to wait until Sunday February 5th,
when you can head on over to podfete.com slash live at 5 p.m. Pacific time and join the friendly and enthusiastic Lucila Castaways. Thanks for listening and stay subscribe.
[44:49] Music.