4 ms·
there’s quite a few people here replying to you letting you know how there are indeed situations where A/V professionals have and are continuing to use built-in
by palimpsests 5y ago
there’s quite a few people here replying to you letting you know how there are indeed situations where A/V professionals have and are continuing to use built-in I/O. I have seen the same. A properly prepared machine is immune to the issues I’ve heard you describe in this thread (notifications, etc).
It sounds like there’s something about all of these responses that isn’t resonating with you because I see a pattern of responding and letting us know our experiences are essentially invalid, for some reason. Are you able to speak to why that’s important to you? Why does this seem so far-fetched / unbelievable to you?
- unethical_ban 5y agoYeah, I'm watching this unfold and I don't see how the other person can't see the problem. Someone spends a thousand, or two thousand dollars on a high-end device with state-of-the-art ports and graphics and processing, and because "OS notifications sometimes pop up if you don't disable them", real pros buy a piece of middleware hardware that does nothing but filter out a software issue?
- dkonofalski 5y agoYes, exactly. If you need to be able to control what goes to the display and take that away from the OS, you need a hardware I/O device. OS notifications and alerts are just examples of any number of things that could be displayed that are unwanted. In situations where something like that makes the setup "unusable", you have to have a hardware I/O device. There's not another option.
- dkonofalski 5y agoI think you're misreading what I'm saying. I have only been responding to people that are saying that the dot makes this setup "unusable". The machine you're describing is not possible without a dedicated hardware I/O device because the OS always has access to display devices and apps cannot override that. If the dot makes their setup unusable, then the situation prior to Monterey should also have made their setup unusable because the OS could have popped up an alert dialog at any time (or any kind of OS chrome). Using built-in I/O is absolutely fine in professional settings but not for settings where you need complete control of what's being displayed and that's precisely what they're complaining about. They never had completely control of what was being displayed. They were just OK with it because it either didn't bother them often or it wasn't a dealbreaker for whatever they were doing. If you need to know that you're only going to see what you want to see, you have to use hardware I/O. I've never said anyone's experiences are invalid. Stop talking down to me like a child and making things up.
- dang 5y agoYou posted a ton of comments to this thread (over 60 of them!) perpetuating a massive flamewar, and broke the site guidelines in a whole bunch of places, including outright personal attacks. We ban accounts that carry on this way, and we've had to warn you about breaking the site guidelines more than once in the past. We don't want flamewars here. Please make your substantive points thoughtfully and without swipes in the future—regardless of how wrong other people are or you feel they are. Btw, when discussion degenerates to the level of people arguing about what each other did or didn't say, that's a sure sign that the conversation has become tedious and uninteresting to those not involved in the spat, and that it's time to step away from the comment box. You weren't the only person in the thread doing these things, but (from the subset I've seen), your account was behaving the worst, both qualitatively (in terms of how badly you were breaking the site guidelines) and quantitatively (in terms of how many posts you made and how much fuel you added to the flames). Could you please review https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and take the intended spirit of this site more to heart from now on? I don't want to ban you, but if this keeps happening, we'll end up having to, because it's not what this site is for and it destroys what it is for.
- dkonofalski 5y agoI'm sorry. I didn't mean to start a flamewar and I didn't think that posting comments was frowned upon. It's just something I'm passionate about and felt was being misconstrued by people. Can you clarify where I broke the site guidelines? I don't believe that I've personally attacked anyone but that feels like a subjective measure so I'd like to be clear on what you consider a personal attack (in this thread specifically). I don't feel like calling someone out for mischaracterizing what I'm saying or flat-out being dishonest about what I've said is a personal attack but, if it is considered that by the admins, then I'll stop doing that. If it's something else, then I'd like to be aware of it so I can check myself in the future. I'm reading the guidelines now and will try to take the intended spirit. I don't want to get banned but I also don't want discussion to be surface-level and I get that there's a fine line there. Sorry again. I'll do better in the future.
- dkonofalski 5y ago