Mac OS simple sound mixer
Ever wanted to play sound through multiple audio devices on your Mac OS X system? It cannot be done with the normal Mac controls, but to my surprise there is a decent sound mixer built into the base Mac OS.
Step by step instructions: Play sound on multiple devices, including Internal Speakers, on OS X | Best Mac Tips
I have this setup for my 90 year old mother, so we can all watch TV at once:
- HDMI from Mac to our Panasonic TV
- Headphones plugged into the earphone jack on the Mac
- Closed captions turned on for TV
The result is that we can turn her volume way up, while we listen over the TV’s internal speakers. The headphones, even at maximum volume, may not be quite loud enough for her. In that case, I will add a $25 earphone amplifier into the system.
Still missing: I cannot find Bluetooth headphones that are loud enough for her.
Second, I don’t know of anything similar for her phone.
This is how home IoT ought to work. But overall, this service is going to figure in a lot of divorce lawsuits! Excerpts from the article: Continue reading
Hardware and software list for new PhD students. It’s a good starting place. (I guess February is the start of the new academic year “Down Under.”) Source: Going back to school again – a shopping list | The Thesis Whisperer
My additional suggestions:
1. Reference manager software is essential. EndNote is radically overpriced and behind in terms of features, but unfortunately is standard in certain fields. There are open source alternatives (Zotero). I use Bibdesk, which is only about $50.
2. A document manager is also essential. And I disagree with her comment about using a different manager for each source (PDF, web pages, etc.) To start with, Evernote is an OK but very lightweight document manager – it is not easy to find things once your library gets large (I have > 10,000 documents, but that is after years in academia). Better alternatives are:
- Devonthink (much more complex and correspondingly harder to learn, but also more powerful. For example, you can link to specific locations inside documents).
- Both of these allow you to store ALL kinds of documents and to easily display, search, reorganize, and annotate them while still in the main application. For web pages, you have the option of storing as HTML, or converting to PDF.
- A third option, which went through years of bugs but is apparently now OK, is Papers (papersapp.com). But it only has native support for PDF – everything else has to be stored as PDF. Still, if I were starting over I would give it a serious look.
- Finally, Bibdesk or other reference managers may be OK for managing documents, although I’ve never tried it.
Scrivener and its ilk for writing you have discussed elsewhere.
TL;DR It will take 5+ years for standards to get sorted out in home automation. Until they are, devices from different companies will not be compatible. Anything that you buy and install now will be inconvenient (you will need multiple interfaces) and become obsolete in a few years.
Now that there are many genuinely useful and modestly priced home automation devices (and I don’t mean smart refrigerators), we are ready to enter the rising portion of “the S curve” where penetration increases. Most of the devices can be retrofit, which will make uptake much easier.
But right now, most vendors have their own protocols. Common protocols are needed at 3 layers: the user interface, such as a mobile phone/computer app (or web site), physical communication such as Bluetooth, Zigbee, or Wi-Fi, and data protocols (API’s, essentially). Most vendors appear to be moving toward a hub and spokes arrangement, where the hub handles communication to the user and outside the home, so there will also be competition for whose hub customers buy. Finally, I would add security as its own “layer,” since it is so important and currently completely neglected.
The research on this seems pretty overwhelming: laptops and cell phones in class hurt learning. Related issue: learning to listen.
Unfortunately in my more quant courses, they can be necessary at times. But if I had a way to turn off the Internet, I certainly would. (FCC makes wireless jamming illegal – for good reason.)
The odds of dying in a car wreck are twice as high as this thing “exploding.” I’m keeping it.
Source: My Galaxy Note7 is still safer than my car. I’m keeping it
This author does an interesting calculation, but he does it wrong. The 100 Note7s that have exploded, out of 2.5M sold, were all used for 2 months or less since the phone has only been on the market that long. When you correct for this, the rate of fires over a 2 year ownership period is roughly 1 in 1000. (Probably higher, for several reasons.)
Second, lithium battery fires are nasty, smelly, and dangerous because they can set other things on fire. I speak from personal experience. Do you want to leave a device plugged in at night that may have a .1% chance of burning your house down over the period that you own it? I hope not.
His car wreck odds calculation (1 in 12000), by the way, may be per-year, but again he does not realize that it matters. But he is right that cars are plenty dangerous. I once estimate that at birth an American has a 50% chance of being hospitalized due to a car accident during their lifetime.
There are many other TOM issues to do with this Samsung Note7 recall. Clearly they have internal problems, and problems somewhere in management.
Proving self-driving cars are safe could take up to hundreds of years under the current testing regime, a new Rand Corporation study claims. Source: Self-driving cars may not be proven safe for decades: report The statistical analysis in this paper looks fine, but the problem is even worse for aircraft (since they are far safer per mile than autos.) Yet new aircraft are sold after approx 3 years of testing, and less than 1 million miles flown. How?
From the report:
we will show that fully autonomous vehicles would have to be driven hundreds of millions of miles and sometimes hundreds of billions of miles to demonstrate their reliability in terms of fatalities and injuries. Under even aggressive testing assumptions, existing fleets would take tens and sometimes hundreds of years to drive these miles.
How does the airline industry get around the analogous statistics? By understanding how aircraft fail, and designing/testing for those specific issues, with carefully calculated specification limits. They don’t just fly around, waiting for the autopilot to fail!