XK-System (community project) > Software Development
(RFD) OS X or Windows? (CLOSED)
Artur D'Assumpção:
Hi guys,
I think there might be some confusion.
This is just for the Desktop client (desktop environment). The actual computer is running on Linux on a separated machine that's inside the I/O computer rack. This is running with a realtime kernel so it's very very reactive and as near zero-latency has it's possible in a Linux realtime dedicated system.
All the rest will connect to the computer through TCP/IP, this includes the desktop client (GUI stuff). We are also planing other interconnections through the network such as displays (as many as you want) and remote controllers.
Regarding the desktop client (main application) you can install it wherever you want, each configuration with its advantages/disadvantages.
As I see it, one of the main advantages of installing the desktop client exactly on the same machine where you run your Protools (or other DAW) installation is the following:
- One less computer to have (one less keyboard, one less mouse, one less monitor)
- Everything's integrated in one place
- Time Code slaving/Transport integration can be achieved without use of any cables:
- This means you'll be able to slave the SSLMixed Computer to TimeCode support without using any SMPTE or MTC/MIDI cable in the scenarios where your DAW is Time Code master (most of them I imagine). This is possible because we'll develop a virtual midi MTC IN where you can send your TC reference directly from DAW to the client inside the same system without having to get the signal out through a cable and back in.
- This is exactly the same approach for the Transport integration support.
- Of course if you still use a different system/appliance other than your DAW to provide TC reference on your studio you'll still be able to use SMPTE or MTC through a cable to sync the system. This will be possible through a special purpose I/O card we'll design and that you'll slot in the computer. In this scenario the desktop client application will get TC reference through TCP/IP.
Regarding the OS X/Windows debate I think we need to be cautious with a decision in here. Not all userbase is OS X, although I agree the great majority of it is.
You have the example of Apogee that ditched the support of Windows and I hated that because I really can't use their gear and hate to be forced to use a specific system, specially when I don't use it. For this reason I would prefer to support both systems, even if that means a bigger workload in the future. This is still under consideration at this stage of course...
Also regarding the application code maintenance for the future, that is something that will be always necessary. An application written for OS X 10.8 with certain framework dependencies will NOT work on OS X 10.3 or 10.10. Look at what happens with Protools, everytime a new major version of OS X is released they have to do something in the code to make it 100% stable and supported. So there's no such thing as having an app that will work forever without any maintenance, unless you're doing only POSIX compliant C applications and with shell command line look and feel... I bet you guys would hate that and kill me! ;)
I have to be honest I am currently having a big big dilema. I am not a OS X user and I was willing the start developing the systems for OS X, using a virtual machine as my developing base. But the Yosemite (OS X 10.10) really is coming as a big show stopper to me due to SWIFT, the future new developing language by Apple.
Apple is killing Objectve-C (which SUCKS!!!) and slowly giving place to SWIFT. It is foreseeable that in a near future Apple kills the Objective-C support. Should we invest lots of time and effort developing on a language that has its future condemned?
I was thinking that we should take the plunge and wait for Yosemite (I can apply for the beta to get it earlier) and look into the SWIFT thing. We could start the development directly on this language with the upside that we would be investing in the future and downside that users pre-Yosemite can't use it.
This is my dilema and what at the same time pushes me to start the development on a Windows system, while waiting to see what's the big deal with the Yosemite+SWIFT.
Let me know your thoughts.
Cheers,
Artur
Artur D'Assumpção:
Good news, you can start developing in SWIFT on OS X 10.9.3 if you install XCODE 6 Beta.
This is good news since I could tackle the SWIFT language right now without having to wait for Yosemite (october I think).
Cheers,
Artur
waltzingbear:
in that case, Mac as most of the clients i have that use SSL and PT are Mac based.
Alan
Artur D'Assumpção:
Alan,
Yes, I am now 95% inclined to start the development with Mac, I am already studying and prepping the environment on a virtual machine (I don't have an apple computer)
Cheers,
Artur
jimlfixit:
Hi Artur
Over the years, I have visited loads of studios and practically all of them have Mac computers, even non SSL ones. The last one I saw which had a PC was in 2002 (Enya's studio in Ireland).
Surely Mac is the way to go and, as someone once said to me, a Mac is built as an aircraft but a PC is built as a car with wings! Macs are arguably less liable to crash and have have viruses, easier to learn and are much more affordable these days. They used to be associated with graphic design many years ago but, with the arrival of the old colourful iMac, much later followed by the iPad and iPhone, their use has increased dramatically today.
At SSL, the mix software was complied on a PC but Colin Sanders always had a Mac handy in the background (Classic SE I think?) and preferred that system ideally even though it couldn't handle the SSL requirements at the time (1980 ish).
Like others on here, I would strongly suggest going with the Mac operating system. Hope this helps get the vote up to beyond 97 - 98%? Regards from Jim.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version