They are supported! I'm writing this comment on a hackintosh running a GTX 1060. Nvidia released Pascal-compatible Mac drivers 2 weeks ago (April 11).

Interesting but unverified side story, the drivers were apparently released because of an email from a redditor: https://www.reddit.com/r/apple/comments/65hpc8/funny_story_a...

> Windows + Linux subystem is pretty great, or just booting directly into Linux.

I built this new computer recently and gave Windows 10 and Ubuntu 16.04 both a shot. I decided I didn't want to relearn how to be productive with them and turned it into a hackintosh, and I'm very happy with it so far.

Same! I was waiting for the pascal drivers to take the 1080 Ti plunge, and I am super happy I did (literally installed it 48h ago, upgrading from a 980). I have a 6700k "mac" that flips to a top of the line gaming pc if I am in the mood for that.

Glorious: http://fred.d.pr/FQLuV

It doesn't take a ton of time. I did keep great notes about all the process in hopes I'd have time to write an extensive guide, but still haven't quite been able to come up with the time to write it.

[0] https://www.tonymacx86.com/threads/unibeast-install-macos-si...

2018 is still a long way from here and who knows how that new Mac Pro will be.

The only solution to me would be running OS X on my own desktop hardware. I'd gladly pay Apple a nice premium for this.

Recently I went to a projection mapping seminar (its kinda like DJing but using video loops), everyone who attended had older macbook Pros (with hdmi to power the projectors). The production machines they use to do the projections live are all microsoft windows machines, as its the only way to get enough video horsepower to run the multiple displays.

The artists running the seminar said they couldn't recommend macs anymore, excepting for some backend asset creation. Since most software is mac/windows right now its not a bid deal, I worry if the mac demand goes south, the software won't be ported.

I'm hoping linux starts being more viable solution for content creation. Seems like its heading that way.

Edit: low res demo from 2008: https://vimeo.com/2577056

I continually experimented with automating sound-reactive video, but it was unpredictable and difficult to get a pleasing, "fluid" result which didn't cause seizures, so we always did it by hand using hardware such as EDIROL V-4 or the MX50. It was also a lot more fun to punch buttons and slam sliders to the beat of the music ;)

Do you mean current or previous pipeline? Unfortunately most projects are somewhat unique and require at least some variation, if not a complete overhaul in workflow, depending on what the customer wants. I never got a chance to use VVVV in a commercial capacity, although there is an upcoming project where we are seriously considering it. Generally we used custom in-house software (e.g. for 360 projections using 2x 4-channel MPEG-2 decoder cards) or VJ software such as ArKaos and Resolume. Like I said before, these days it's purely content production, so the pipeline is relatively similar to a game studio. We still encode everything into various QT formats and we rent hardware for shows because as you said, it's hard to keep up with ever-changing hardware demands.

If you are interested in our projects, check out http://www.motionlab.at (go the old site for now, the new site is WIP).

The V4s still sell quite well for some reason, some of the other analog gear is still in demand for circuit bending.

If the projectors are decent they can still hire pretty well too.

Keijiro Takahashi at Unity Japan has a great github repository full of relevant libraries.

https://github.com/keijiro

Using a hackintosh for mapping/vj'ing as the off the shelf hardware isn't at all practical and I want to keep using OSX only software.

Honestly it's a nightmare.

I want as many video outputs as possible, enough power to run multiple layers of video, be running game engines at the same time, transcode a video in a pinch and more.

Switching to windows is probably the only option going forward.

We all need ECC. It should be a standard feature by now.

ECC also thwarts Rowhammer and similar attacks, if that matters to you.

Note that it isn't enough for AMD to restore ECC support in consumer kit; you also need motherboard support, and the MB makers are also complicit in raising ECC costs.

But for whatever reason, AMD never seems to put ECC in the bullet lists for why you should buy their parts. I guess as someone else mentioned its because the motherboard manufactures don't enable/qualify it even though its likely just a matter of firmware tweaks ever since the DRAM controller moved on chip. I got it working on a cheap phenom II/gigabyte motherboard (IIRC) some time ago as well. In that case I don't think the motherboard even advertised it, but I had some unbuffered ECC DIMMs lying around and I plugged them in, and they worked. Of course the only real indication besides booting the machine that it was actually working was a kernel blurb during boot about it. I don't think I got the EDAC reporting to give me soft error rates at the time.

[0] https://en.wikipedia.org/wiki/ECC_memory

RDP will give better results and there are tons of implementations.

NoMachine is probably the best documented and supported. However is proprietary but they have a free version. I believe it can do streaming video.

Spice is poorly documented and seems to not be maintained however it is very efficient and can stream janky video.

Have a look at XRDP with libfxcodec for streaming video (need lots of bandwith) otherwise without libfxcodec for decent low bandwidth

https://encrypted.google.com/search?q=xrdp+libfxcodec

Shortest Googlewhack(-ish) I've ever accidentally stumbled upon myself, for sure!

try: https://github.com/neutrinolabs/librfxcodec

It would be a nice protocol if there were functional clients, but I fear that train has sailed.

As someone who does front end graphic work to mockup apps before building them as part of my workflow I couldn't see myself switching off Mac OS unless Microsoft drops the registry, replaces NTFS, stops with the spyware being built in, disables the forced updates and finally goes with one UI/UX for everything.

Why do you care about the registry and NTFS?

Desktop developer could care, but a web one?

I've opened up Regedit in the past year, but I work with a piece of benighted software that supports a weird but useful feature designed fifteen years ago when doing unfathomable things with the registry was something people did.

I'd argue that's preferable to a complicated hierarchy of obscurely named keys.

Also, the registry is used for a lot of stuff besides configs. So my experience on Windows is that you have to run the installers (=slow), rather than simply copying all the files to clone a system.

Plus, it tends to fragment all across the disk, or something like that, and your Windows system inevitably slows down over time. Maybe SSDs eliminate that problem; I (fortunately) haven't had to use Windows in quite a few years.

You can't copy full software installs like that, but it's not the fault of the registry. Installing typical software means affecting dozens of system settings all in different places. You can't easily copy linux software along with every setting it affects either. You're best off either reinstalling or copying the entire drive, both of which work on Windows.

No, that's not true--I did once in 2015 to make a game written in 1998 work.

I think we can lay this one to rest.

Copying putty settings from one host to another? That's a regedit.

(Semi-) permanently disabling live scans from Windows Defender? That's a regedit.

https://github.com/randyrants/sharpkeys

One of the first things I install on any new system. Gotta have my Caps Lock->Escape.

That means you can do a Hackintosh build with their latest video cards (GTX1080 or Titan) with full driver support.

[1]: https://9to5mac.com/2017/04/11/nvidia-releases-pascal-web-dr...

[1] https://www.jinx.de/JollysFastVNC.html

That's to be defined. I for example use a MBP with an E-GPU Setup (Sonnet Echo Express-III with a Pascal GPU inside). Put the MBP in my Docking station and I have a decently powerful desktop Mac. I love it, I hope that is the future.

Any real world issues or hiccups, or has it been as good as you make it sound?

But there are unfortunately other things to consider. In my case the Echo express enclosure is not made for Graphic cards and you have to modify it to make it work - done in about one hour when you are really careful. The wait for Pascal drivers was sad. Other than that the only other thing that comes to my mind is that you cannot remove the MBP from the docking station before shutting it down. (I have read that sleep should also work but it does not for me)

Edit: If things work really depends on the exact setup. I have just seen the video posted in another comment (https://www.youtube.com/watch?v=yho3rCNfzGE) and it looks like I have just been really lucky with my setup.

You can use them right now but the driver is still in beta. See https://arstechnica.com/apple/2017/04/nvidia-releases-beta-g...

I see that folks are putting nvme cards into their older mac pros:

https://forums.macrumors.com/threads/pcie-m-2-nvme-on-macpro...

Is there a recipe that allows one to boot from an nvme add-in card on an older mac pro ? (in my case, early 2009)

I would suggest this card, it should work, it is SATA based as opposed to NVMe. I have installed a few of these in on several older systems (x58 based and others) and saw a very large performance bump, even versus SSDs connected via aftermarket PCIE SATA-3 controller (running at 500-550mbs). YMMV if attempting to clone an existing drive - I have had this problem with add-in PCIE cards, older motherboards, and various operating systems - a fresh install to one of these drives will likely be easier.

Sorry to be a name nazi, but some people may not be aware of the difference. Its hard to tell online if people don't notice the error or don't know they've made an error.

[1] https://en.wikipedia.org/wiki/Xenon_(processor)

...but you might not like the results under MacOS

(Edited for typos)