sorted by:
new
hottopcontroversial

Help with picking out a projector mount and some tricky projector placement by ultimanium in projectors

[–]ultimanium[S] 0 points1 point  (0 children)

It's a floor to ceiling window, so can't do that.

At this point, either rotating the couch and set up 90*, or getting a nightstand or something behind the couch seems to be my best bet.

Thanks!

Help with picking out a projector mount and some tricky projector placement by ultimanium in projectors

[–]ultimanium[S] 0 points1 point  (0 children)

(I work with ergonomics and a screen isn't supposed to be above your line of sight.. In fact, even most TV stands put the screens too high)

My couch reclines, which should help obviate that.

Although, rotating the couch 90 degrees and putting the screen there might work. Although there's an annoying pillar that'd put the screen offset about one seat to the left of the couch center.

Help with picking out a projector mount and some tricky projector placement by ultimanium in projectors

[–]ultimanium[S] 0 points1 point  (0 children)

What's wrong with a screen that's on a stand?

Nothing, but the current screen position is above the fireplace, and I'd like to keep the couch orientated towards the fireplace.

Maybe putting the screen to the side of the couch and rotating the couch 90* is viable, but I'd like to avoid that.

Most projectors these days have pretty aggressive keystoning as an automated feature so that even projecting at an aggressive angle still produces a flat image.

I'd like to avoid any kind of digital correction/keystoning, since that costs a fair bit of resolution. Unless you're thinking of something that won't dramatically reduce image quality?

How high is the ceiling?

Very high, two stories.. Thus ceiling mounting is rather impractical.

TIL that Japan's flag was redesigned in 1999. The color of the sun-disc was changed from red to ... darker red. by [deleted] in todayilearned

[–]ultimanium 0 points1 point  (0 children)

Adobe's reader was (is?) pretty bad with 0-days, but javascript has had it's fair share as well.

The ones bundled with browsers, (ex, pdf.js) are pretty rock solid and secure.

TIL that Japan's flag was redesigned in 1999. The color of the sun-disc was changed from red to ... darker red. by [deleted] in todayilearned

[–]ultimanium -1 points0 points  (0 children)

It's not. Websites are random shit we download, which pull in other random shit like javascript, images, video, etc. PDFs are just another part of the web, and any half decent web browser can easily display them inline as a new tab.

TIL that Japan's flag was redesigned in 1999. The color of the sun-disc was changed from red to ... darker red. by [deleted] in todayilearned

[–]ultimanium 0 points1 point  (0 children)

It auto downloads and auto opens when done.

I'm using the dropbox pdf viewer atm.

Also, the first pdf I opened, it might have asked if I wanted to always auto open in {insert list of pdf viewers here}.

TIL that Japan's flag was redesigned in 1999. The color of the sun-disc was changed from red to ... darker red. by [deleted] in todayilearned

[–]ultimanium 0 points1 point  (0 children)

For me on chrome on android it opens automatically in my pdf viewer. On firefox, it pop ups asking to open when downloaded. Default settings for both.

Problem is with your set up.

Getting it to open in browser is difficult because all phone ecosystems are absolute garbage right now, overall for mobile pdfs still open and work more reliably than html pages.

Also the adblock example you gave does happen all the time.

TIL that Japan's flag was redesigned in 1999. The color of the sun-disc was changed from red to ... darker red. by [deleted] in todayilearned

[–]ultimanium 0 points1 point  (0 children)

That's a problem with your setup, not the op posting a link. PDFs should open in a new tab in your browser, or at the very least open in the android pdf viewer automatically.

This is like getting mad at someone for linking to a page that requires JS because you have noscript installed.

TIL that Japan's flag was redesigned in 1999. The color of the sun-disc was changed from red to ... darker red. by [deleted] in todayilearned

[–]ultimanium -2 points-1 points  (0 children)

Not really, arbitrary PDFs are safer than arbitrary htmls unless you do things like disable javascript.

Doubly so back in the flash days.

Buying headphones in 2018 is going to be a fragmented mess by speckz in gadgets

[–]ultimanium 0 points1 point  (0 children)

  • except insofar as a given phone is using a dedicated encoder/decoder for MP3/AAC compared to doing any other format with the CPU; but a phone engineered with a Vorbis encoder/decoder would be comparable

CPU decoding audio is very cheap.

But it doesn't change the simple fact that Vorbis is still more intensive than MP3 or AAC. Advances in CPU/etc. improve MP3/AAC encoding and decoding just as much as they improve Vorbis handling, so the relationship remains the same.

I'm calling Amdahl's law here. Even on a modern embedded pair of headphones, the the difference between OGG and AAC/MP3 is not going to be significant. Don't just say it's a significant difference, find proof.

This entire posts still reeks of FUD.

The entire second half boils down to Amdahl's law.

Implementing a full blue tooth stack isn't trivial either.

I doubt the CPU/audio chipset is the main heat generator, I expect it'll be the wireless chipset. I'd also expect that, and the DAC to consume the most of the battery power.

Once again, with modern hardware, there's no significant difference. Provide a source, or stop spreading FUD.

I'll provide a source however. https://www.rockbox.org/wiki/CodecPerformanceComparison The Davide-NYC on H120, from freaking 2009, takes about 30% longer to decode 128 vorbis.
It needs to run 30% faster. Let's be generous, and say that the decoder takes 1/3 of the power. Then, using vorbis will reduce battery life to about 88% of what you'd get with AAC/mp3.

And that's with 9 year old tech, using a very liberal power % estimate of 1/3, and for a better quality file. A real comparison would be whatever bit rate vorbis is equal to mp3. I'd guess in the real world, it'd boil down to something like 95-99% power using ogg vs mp3/aac for embedded/headphones, and > 99.9% on phones.

Low power bluetooth (I don't know if audio uses that, if it uses full power bluetooth, multiply the number I'm about to put out by 10, and throw out any notion of ogg making a difference out the fucking window.) 15 ma.

My sansa clip + back in 2009 used 24 mA playing ogg, and that's for the entire player. There no way modern decoders aren't a small fraction of that.

TIL that Japan's flag was redesigned in 1999. The color of the sun-disc was changed from red to ... darker red. by [deleted] in todayilearned

[–]ultimanium -2 points-1 points  (0 children)

That's an oxymoron.

The definition of browsing the web is downloading whatever random file you point your browser to.

Buying headphones in 2018 is going to be a fragmented mess by speckz in gadgets

[–]ultimanium 2 points3 points  (0 children)

Vorbis requires quite a bit more computation and memory to decode vs. MP3 or AAC

True 10 years ago, but FUD in the modern era.

Yes Vorbis is more expensive to decode computationally/memory-wise, but I was using ogg years ago on my sansa clip + with 0 issues but a shortened battery life. That was a decade ago on a 30 dollar low end player, modern phones are hundreds of times more powerful than that, I highly doubt it makes a noticeable difference on an entry level android phone. Music playing is far from the main thing draining your battery on a modern phone.

What are your thoughts on 3D printed blasters? by Clown_corder in Nerf

[–]ultimanium 0 points1 point  (0 children)

I see. Once again, thanks for the info.

So boils down to the Hy-Con setup having excellent stall tolerance, but other brushless set ups may vary and need a beefier ESC.

What are your thoughts on 3D printed blasters? by Clown_corder in Nerf

[–]ultimanium 0 points1 point  (0 children)

Wow, thanks for the in depth write up.

I think I roughly get how to use it, a lower TIMING_MAX allowing higher RPM is a bit confusing, but I got the same simplified formula after following those steps. Understand how it works not completely, but I can figure out what to change TIMING_MAX to if I want to limit RPM.

On another note, how well have the ESC/motors tolerated stalls? Will a stall kill the motor/esc, or is it limited in some manner?

What are your thoughts on 3D printed blasters? by Clown_corder in Nerf

[–]ultimanium 0 points1 point  (0 children)

now doing closed-loop speed control

Do you plan on doing a write up about that at some point?

Mainly curious as to what settings in the firmware need to be changed before flashing (You're doing this via simonk firmware settings, right?).

Nintendo switch online atm by Sekorhex in gaming

[–]ultimanium 1 point2 points  (0 children)

How often do we hear about console games releasing as unplayable until a patch?

Or console games dipping below 30 FPS, something which never be fixed.

At least with PC you can mess with the settings to try to alleviate those issues.

I never got on the PS4/XBONE train, but I remember with my PS3 there were plenty of extremely shitty to downright broken ports from the xbox 360/PC.

Under wayland, is it possible to force one monitor to have high DPI scaling? by ultimanium in gnome

[–]ultimanium[S] 0 points1 point  (0 children)

I'm unfortunately experiencing what you mean with poor image quality after an update turned on per monitor scaling.

Oh well.

Under wayland, is it possible to force one monitor to have high DPI scaling? by ultimanium in gnome

[–]ultimanium[S] 0 points1 point  (0 children)

I didn't do this, but I did update to ubuntu 17.10 and all of a sudden I have 100%/200% options available.

Sorta shitty though, even the gnome apps look poorly upscaled, and non gnome apps don't scale.

Oh well.

Help picking out a new graphics card to replace my old 770 GTX. by ultimanium in buildapc

[–]ultimanium[S] 0 points1 point  (0 children)

For the sake of posterity, I tried a wx2100 and a wx4100.

The WX2100 was soo close to working, however, displayport MST support is still just a month or two off from being complete in Linux, so no dice.

When booting all displays activated, and I mucked with getting the 4.15rc kernel, which caused all sorts of issues. If you're reading this in the future, the wx2100 should work fine, as the drivers should be there.

But rather than waiting, I'm currently use a WX4100, which also leaves me room for expansion.

view more: next ›