XK-System (community project) > General Discussion
Prerequisites specification list for the SSLMixed computer
Artur D'Assumpção:
Guys,
It's a good a idea to start the discussion on the prerequisites for the new SSLMixed computer. This is important to discuss at this stage because there might be certain requisites that will later have influence on hardware and software design decisions.
Some of the major-topics I think are important to be discussed at this stage (among others) are:
LIST LAST UPDATED: 10/11/2013
* Overall solution requisites (macro features)
- 100% open solution (hardware + software) - MANDATORY
- Low manufacturing costs - MANDATORY
- Support for SSL 4000/5000/6000 consoles (E, G and G+) - MANDATORY
- Support non-moving (vca) and moving fader (ultimation) consoles - MANDATORY
- Keep fader automation status button support - MANDATORY
- Replace completely the old SSL computer - MANDATORY
- Based on 100% new hardware (don't use old parts) - MANDATORY
- Full/partial SSL keyboard support (besides transport)- UNSUPPORTED
- Support legacy monitor- UNSUPPORTED
- Support 100% autonomous system - MANDATORY
- Support client assisted system (ex: DAW support, etc.) - MANDATORY
- Windows and OS X Support - MANDATORY
- IOS Support (tablet support) - SHOULD
- Android Support (tablet support) - SHOULD
* Hardware specific requisites:
- Low power consumption - MANDATORY
- Noiseless (no fans) - MANDATORY
- Small form factor - SHOULD
- No need to preform console modifications/customizing - MANDATORY
* I/O connections specific requisites
- Interface with the SSL through the same flat cables - MANDATORY
- Network support (TCP/IP) - MANDATORY
- Support for external monitor - SHOULD
- Support MTC MANDATORY
* Software specific requisites
- Comprehensive VCA + automation support - MANDATORY
- Comprehensive total recall support - MANDATORY
- Transport support - MANDATORY
- Console surface status support - MANDATORY
- Console modes support (MIX, RECORD, REPLAY, etc.) - MANDATORY
- DAW Integration - MANDATORY
- DAW Transport support - MANDATORY
- DAW Automation support - OPTIONAL
- DAW Control (VCA to DAW / DAW to VCA) - OPTIONAL
- Client side (laptop/desktop) configuration and management - MANDATORY
- Client side (laptop/desktop) live session management support - MANDATORY
- Comprehensive Project management - MANDATORY
- Console live debugging and calibration features - MANDATORY
- Multi-client support - MANDATORY
- Channel live monitor and VCA control support via remote devide (ex: tablet device) - OPTIONAL
- Support multi-display (over TCP/IP) - OPTIONAL
This is totally open for discussion, so lets discuss and define what we really want to do for this project. I will be filling the requisites while these are becoming defined in the next days. :D
Cheers,
Artur
marcmozart:
Guess I just posted on this already :-)
http://forum.sslmixed.com/index.php?topic=442.msg2495#msg2495
Artur D'Assumpção:
I'll go ahead and post some ideas I have to start the discussion:
* It should replace totally the current computer
The old computer hardware is getting very old and very difficult to find and EXPENSIVE!!! So any solution that uses any piece of the old hardware will be limited from the start, it wouldn't be a solution for all SSL users (there are users which don't even have a computer today), could pose challenges to integrate with a modern platform, specially if we're aiming to a low power consumption and small form factor solution and could also prevent the development of new features.
* Should connect trough existent flat cables and without needing any console modifications
This would be nice to have, a 100% plug and play solution.
* Should be small form factor
A small solution would be totally pervasive in the studio and wouldn't need to occupy rack spaces.
* Should be small low consumption and zero noise
* Should fully support automation
* Should fully support total recall like feature
* Should fully support the transport
* Should support moving and non-moving faders
* Should provide DAW integration
* Should be remotely controllable (via desktop application or tablet)
All SSLMixed computer features would be controllable via a controller application.
* Should be multi-client (several simultaneous clients can connect to the computer)
This feature would allow for scenarios were the laptop is the main controller station but you could also interact (only view or view and control) at the same time with one or more tablets/desktops.
More ideas to come...
Artur D'Assumpção:
--- Quote from: marcmozart on November 06, 2013, 09:39:15 PM ---Guess I just posted on this already :-)
http://forum.sslmixed.com/index.php?topic=442.msg2495#msg2495
--- End quote ---
Could you repost it here please?
perfectsnd:
>>
You guys are really picking my brains here! A couple of thoughts…
These are the components/products/features I think we need to come up with:
VCA TO DAW and DAW to VCA
- turning VCA-Fader Voltages into data that ANY DAW can read, preferable via TCIP
and vice versa of course:
- turning DAW controller data into VCA Voltages
TOTAL RECALL to DAW
- sending Total Recall Data into a DAW by using a Control Surface Protocol
- designing a AU / VST / AAX GUI that receives the total recall data and allows us to use the PlugIn Library Functions of a DAW to store full channels as plug-in patches, so the user can build a library of his favorite channel settings.
Obviously with these features we DO NOT NEED to invent any recorder for the automation as everybody is using their favorite DAW for this purpose. It would also allow people to control their DAW tracks with the VCA Faders, pretty much like on a Duality. My point is, why invent another recorder, when there are thousands out there and everybody already has their favorite one. Same for the Total Recall Data. Let us just NOT write another library software - Logic Pro, for example, is excellent at this, and all we need to do is write a DAW plug-in (with no audio functions or audio passing thru) that receives the controller data. The DAW user could also put our Plug-in at the end of his DAW plug-in chain and store the Recall at EXACTLY the place where the Console Channel is in his audio chain.
These would be an essential "extra" to keep the "feel" of the console:
- Interface for the build in Computer Keyboards, Funtion Keys, Transport etc. (both E and G-Series compatible) which - again - translates to a Control Surface Protocol.
I guess my main point is, let's ONLY develop what is needed and not come up with any redundant stuff.
« Last Edit: Today at 10:19:24 PM by marcmozart »
Report to moderator Logged
www.mozartandfriends.com - A song can change your life
1992 SSL 4048 G-Series
See you at www.facebook.com/mixedbymarcmozart
Konnektor
Newbie
*
Posts: 17
Karma: +7/-0
[applaud] [smite]
London
View Profile
SSL 4k automation to DAW interface
Personal Message (Offline)
Re: the e/g computer - actually a direct to disc recording system
« Reply #3 on: Today at 10:37:56 PM »
Quote
anything can be done :)
it's just a matter of time
due to the footprint of the ribbons the box will have a certain size anyway
if there's a way to output voltages with a beagle board or sthg similar without the need of sample&hold circuits that would be awesome!
maybe we could use an lcd controller? i think these use s&h on every dot
i totally agree Marc!
Quote from: marcmozart on Today at 10:16:22 PM
I guess my main point is, let's ONLY develop what is needed and not come up with any redundant stuff.
TOTAL RECALL to DAW:
i did some packet sniffing on digidesigns pro control (ethernet) which would be ideal for pro tools
it would make already large sessions into extremely large ones, though
« Last Edit: Today at 10:42:19 PM by Konnektor »
Navigation
[0] Message Index
[#] Next page
Go to full version