Hacker Newsnew | past | comments | ask | show | jobs | submit | domy's commentslogin

I'm very happy with the Infuse app connected to Jellyfin (also paying the $10/yr for the extra features).


Another Infuse user here, can confirm, it's very, very worth it. The official app with have to be entirely perfect to lure me away, even if it's free.


I have an AppleTV connected to my Samsung TV, and almost never use the Samsung remote. The AppleTV remote's on/off button switches everything together (through CEC I believe) so in everyday usage I only ever need a single remote.


Yep, I only ever use the LG remote for turning off the display when I want to listen to music with a blank screen.


I find that the experience of taking photos with an actual camera (be it mirrorless or DSLR) is vastly more engaging and enjoyable than with a phone.


I agree entirely. However the experience of lugging around a camera bag is vastly less enjoyable.


Look into something like a Fujifilm X100V or Leica Q2 (depending on your budget)

A camera should be nice and compact, then it won't be a hassle to have it with you.

The problem with modern cameras is they are heavy, bulky, junk build quality, have awful menu systems and don't play nice with your phone or your computer. What a wombo-combo of pain, just to get a nice photo!

If you can afford a Q2, all of those problems are addressed.

Modern cameras are like writing corporate software in Java. Leica Q2 is like writing short programs in Python. Phones are like using Squarespace to build a website.


Hm, I quite like your analogy! I actually just got into photography not too long ago with an R5. Thinking about it now, it really does feel some sorta "corporate." I also considered the fujifilm xt4, all the reviews make me feel as if that'd be a Pythonic kind of camera.

After falling in love with the whole photography universe, I hope one day I can experience the COBOL-like world of film. I did grow up when film was around, in the 90s and all that, but my family was too poor and I only ever messed around with disposable cameras and Polaroids. Polaroids themselves are a whole other insanely awesome universe to explore.


I find the experience of going trough 300 raw images and developing them the worst part of using DSLR and why I prefer modern phones with AI based image processing.

But you can’t argue with dslr results though. And when we talk about pro sport photography, well exactly same demands for large aperture, large and variable focal length, high iso with low noise, fast focusing and fast shooter speeds also apply to us amateurs taking pictures of our kids in poorly lit indoor sport events.


I had a huge backpack full of DSLR gear in the early 2000s. I still have a backlog of unprocessed RAW images I need to get through... =)


If I spent 10hrs a day for 365 days in a row I wouldn’t get through my backlog (easily way over 500k photos), but that’s not really the point. I don’t need to process and post every photo I take, many are either just for me or alternate takes that I might want someday. Looking through photos I took 10 years ago is one of my favorite activities and I often find hidden gems that I had dismissed before in the moment when originally gone through.


I do the same thing, I follow Johnny Harris' method[0] mostly. Basically I pick a random date (or an iOS provided "memory") and go through a bunch of photos related to that event. Then I delete all the useless ones, like the 99 takes I did of a sunset, and just keep the best ones.

[0] https://youtu.be/GLy4VKeYxD4


I find this argument nonsensical. Cameras don't force you to take 300 images, nor shoot RAW. As someone who shoots on film, I hear this all the time from people who try to justify why they shoot on film (...and then blow through ten rolls of Portra).


I should explained that I mostly shoot kids, birthdays and their sport and other events. Strictly on amateur level, but for this kind of occasions it's quite beneficial to take 300 shots since it all happens in the moment and you'll have a lot of misses to end up with 30 keepers.

Also, jpeg straight out of camera can be ok if you're controlling circumstances and have time to take test pictures and adjust parameters. And not change entire scene in a seconds. Once I went to RAW I could never come back. Now you don't have to worry about white balance or even exposure in the heat of moment. It allows you to really save a lot of these shots which would be lost in jpeg. Price you pay is staring in 300 raw images afterwards.

I must admit this affects my desire to use DSLR in the first place. I tend to use only if absolutely necessary.


I dropped to a micro 4/3rds setup for walking around for this very reason. The lightest body and 2-lens setup I could configure was about 5-6lb depending on how many spare batteries I wanted to carry as well.

My 4/3rds setup with flash, 5 lenses, and a few batteries was only 2.2lb. I don't even notice I'm wearing it.


I did this, 2013-2019ish. Unfortunately there has been so little development in m4/3 sensors over this time period that my iPhone has replaced it for all scenarios except occasional extreme-tele. The improvement in quality offered by even the best m43 camera and glass over the latest phones just isn't worth the effort to me anymore at focal lengths below 200mm-ish, or I want to do something that requires a traditional camera "hot shoe" like external lighting.

The latest and greatest m4/3 camera today doesn't really take still pictures any better than an Olympus EM-5 from 2013 (the increase from 16 to 20mp makes little "real world" difference), cellphones improved _enormously_ over the same period. With a modern iPhone, I get an extreme wide angle, "standard" and reasonable portrait focal length lens all in one device, with the files in Lightroom immediately after taking them. Yes you can argue for days about "fokeh" vs the real thing, but m4/3 isn't the platform you want to be on if rich bokeh was your primary objective in the first place. I've also yet to find a three lens kit that covers the range of a modern iPhone I can fit in my jeans pocket too, even in m4/3!

I think in some cases, many people just like the "ritual" of using an interchangeable lens camera as much as they practically get any better images than with a decent phone, which is fine! For some reason it's not fashionable in photograhy circles to admit this, I guess the fear of looking like a dilettante etc.


The 20mp 4/3 sensors have noticeable advantages in dynamic range and high-ISO noise compared to the 16mp sensors. It's not just more pixels. A new ~23mp sensor with further performance improvements should show up this year in the Panasonic GH6 and an unnamed camera from the company formerly known as Olympus, though it's not clear if or when it will make it to more pocket-friendly models.


Perhaps, but I have a Panasonic G9 (20mp) and a EM1 Mk1 (16mp from 2013) the differences, while measurable to some degree in benchmarks, in day to use are really not that noticeable at all. The m4/3 industry relies effectively just on Sony now for sensors as Olympus/Panasonic do not make them, and there is not that much commercial incentive for Sony to invest more - this is why we only get a sensor feature bump when the Sony sensor catalog finally gets a new installment in 17x13mm.


I noticed a big difference going from a Panasonic G7 to a GX9. It gave me a stop more usable ISO and a lot more ability to bring up the shadows when editing.


Obligatory Chase Jarvis quote: “The best camera is the one that you have with you.”


I think the problem here is general purpose phone design/cheap optional cases. I would absolutely love a camera-like industrial design and a real/artificial shutter "snap". I hope this improves


SLRs even more so


I love Matt Pharr's blog [0]. He's one of the authors of the Physically Based Rendering book [1] and his blog is mostly centered around that topic, with really well written and interesting articles.

[0] https://pharr.org/matt/blog/

[1] https://www.pbrt.org/


Infuse has support for Jellyfin.


Personally, I've grown very fond of ReactiveUI (https://github.com/reactiveui/ReactiveUI) over the time I've been using it. While the learning curve upfront is rather steep, I think it's absolutely worth it.


I've heard good things about Reactive but haven't invested the time in learning it. I have been using Caliburn for MVVM as it simplifies a lot of WPF oddities.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: