- any headless Linux server
- Blender v2.79 or v2.80 - v2.93 (from package manager or blender.org)
- latest version of CrowdRender addon
- optional: GPU drivers for GPU-rendering
| import os | |
| import bpy | |
| import asyncio | |
| GLB = "/tmp/model.glb" | |
| def import_gltf(path): | |
| bpy.ops.object.select_all(action='SELECT') | |
| bpy.ops.object.delete() | |
| bpy.ops.import_scene.gltf(filepath=path) |
| # ##### BEGIN GPL LICENSE BLOCK ##### | |
| # | |
| # This program is free software; you can redistribute it and/or | |
| # modify it under the terms of the GNU General Public License | |
| # as published by the Free Software Foundation; either version 2 | |
| # of the License, or (at your option) any later version. | |
| # | |
| # This program is distributed in the hope that it will be useful, | |
| # but WITHOUT ANY WARRANTY; without even the implied warranty of | |
| # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
This was tested on a ThinkPad P70 laptop with an Intel integrated graphics and an NVIDIA GPU:
lspci | egrep 'VGA|3D'
00:02.0 VGA compatible controller: Intel Corporation Device 191b (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GM204GLM [Quadro M3000M] (rev a1)
A reason to use the integrated graphics for display is if installing the NVIDIA drivers causes the display to stop working properly.
In my case, Ubuntu would get stuck in a login loop after installing the NVIDIA drivers.
This happened regardless if I installed the drivers from the "Additional Drivers" tab in "System Settings" or the ppa:graphics-drivers/ppa in the command-line.
| import { join } from 'path' | |
| import { readdir, stat } from 'fs-promise' | |
| async function rreaddir (dir, allFiles = []) { | |
| const files = (await readdir(dir)).map(f => join(dir, f)) | |
| allFiles.push(...files) | |
| await Promise.all(files.map(async f => ( | |
| (await stat(f)).isDirectory() && rreaddir(f, allFiles) | |
| ))) | |
| return allFiles |
Updating to macOS Sierra is causing trouble with React Native due to some of the Node.js and system utilities it uses. Specifically the watch utility fails due to a limit on the number of files which can be opened at a time.
The following command shows the current limit.
launchctl limit maxfiles| #!/bin/bash -e | |
| ln -s /usr/lib/x86_64-linux-gnu/amdgpu-pro . | |
| ln -s /etc/OpenCL . | |
| tar -czvf libs.tar.gz amdgpu-pro/* | |
| tar -czvf conf.tar.gz OpenCL/* | |
| cat > .dockerignore << EOF | |
| OpenCL |
| //Look for other responsivevoice instances | |
| /*if (window.parent != null) { | |
| var iframes = window.parent.document.getElementsByTagName('iframe'); | |
| for (var i = 0; i < iframes.length; i++) { | |
| //iframes[i].style.width = "300px" | |
| } | |
| }*/ | |
| if (typeof responsiveVoice != 'undefined') { | |
| console.log('ResponsiveVoice already loaded'); |
Note: This is an older post that I did back when I thought I might have time to be a blogger. Oh I was oh so wrong. However, it has proven useful for some folks on stackoverflow. Thus I'm keeping it alive here on Gist.
One of my past projects dealt heavily with an open source Apple technology called HTTP Live Streaming. It’s an HTTP based streaming protocol that at its most fundamental level provides a way to stream video and audio from just about any server with nothing but a few free software tools provided by Apple**. However, it has a few additional features that I think make it a really exciting tool. Yet, I haven’t seen HTTP Live Streaming used very much. This is probably mainly due to the combination of a lack of good/clear documentation, and Apple’s Live Streaming Developer Tools being command line based also make the barrier to entry higher than many developers want to deal with.
The hope is to share my understanding of how to use this technology to: