two details:
regarding 48 Volts - they should be switchable for every of the ( preferably 6 ) channels separately.
The ODAC link : http://nwavguy.blogspot.co.at/2012/04/odac-released.html ( btw: look ate THE REAL NUMBERS there )

Well - just demonstrating the new premises is also a good idea - not only by showing Pictures but by also giving sort of audible impression.

Did you already download the free Skin?

suggest using namespaces ( some lines in configuration file ), Lockdown extension if restricted access is needed ( don't know/cannot decide if needed), NSFileRepo extension if restricted access should be applicable for documents also ...

great, suggest a more detailed Description, e.g. zoom in/out is accomplished by two buttons, or some device where the zoom speed also can be controlled for soft start and end of zoom.

Hi Walter, using sociocratic measures in projects where numerous people are involved seems to be a very good idea!

consulting http://www.wikimatrix.org/compare/DokuWiki+MediaWiki some Questions:
Do you really want to switch from Database- to Text storage?

Sandisk - Specifications Line 2 says "(Preliminary specifications subject to change)" ;-))

just used some ( oil painting ) Gimp filter as alternative to recovering them

Do we have a raw Version ;-))?

Would select one ( or both ) of Workshop and talk

stress should be put on not overloading the sheet - btw. google spreadsheet is really great - I think exact dates would not be needed, IMHO week of year suffice.
Preview is even greater!!!

inviting backers to the lab is a very good idea, whishlist also. Polls - excellent idea, noticed only one ...

was not very clear about future - moving pages is ( even for only about one hundered of them ) not a good idea, but trying to put new ones into some sort of structure should be. The challenging question is indeed what to do with pages, that fit into more than one category, but that problem Philipe overcame with the New Main Page.

allan, listing the pages on the wiki is exactly no effort, because you have the all Pages. Using namespaces, you can "filter" these Pages, e.g. Project Pages - this one (Apertus Wiki) is built by default, and you can easily define additional namespaces, which can be queried quite intuitively by selecting one of them in the drop down selection.

https://www.sparkfun.com/search/results?term=rotary+encoder from http://irc.apertus.org/index.php?day=06&month=11&year=2014#64: great devices!!

even: I could not imagine an alternative to faders speaking in terms of volume control ( too many sound engineer jobs in the past )

• suggest 4 faders for 4 ( mono ) inputs. Advantage compared to wheels: faster travel speed to correct position ( tenth of seconds with a little practice ).
• suggest keeping the sound part as simple as possible - no pan, no mixing functionality ( use a sound mixing console if desired )

from http://irc.apertus.org/index.php?day=02&month=11&year=2014
00:53
Rebelj12a
Well yes, menu design and feature design go hand in hand with fixed buttons and the like. Ah ill just plan design for future easier that way.

[personal opinion]following decisions should be made:

having a problem with documenting the Discussion about sliders and rotary dials without bringing in my personal opinion, which I should not do as a documenter...
although extracting keywords would perhaps help not to go through the same discussions again and again.
extracting links would be a question of just setting up a simple script - if this could be of any use
[off topic] cannot imagine setting a camera value by using linear controls as e.g. sliders, although I appreciate faders when using a (sound)mixing console - compared to rotary knobs - on the other hand, it is very easy to distinguish about 16 different positions looking at a rotary knob ( or scale, imagine a wall clock or a compass ), whereas 10 positions are very hard to distinguish on a linear scale ( slider )
[very off topic]do we have something like user Interface from the Viewpoint of usability ( having intuitive handling in mind, and if so, which story should be behind it?)

What about some structure in/for the wiki? In the moment we have about hundred pages ( 106 to be precise ), as the numer of pages increase, it will be harder to find any information.
I propose to move e.g. ElphelVision pages to a separate namespace ( or something alike , as I am not "the MediaWiki expert" )

hi, just some sort of crawled through the irc logs of the past days to look at and bookmark all ( or some of ) the URLs, like

Tags & Taxonomies seems to be an interesting feature, especially when number of informative items increase, but I cannot find more Information on the website. Perhaps a separate knowledge base would be better