Just to let you know: I'd be very interested in a Windows version. I use a lot of devices that are (sadly) not compatible with Linux. I would even be happy to pay to support the project.
Anyway, if you need beta-testers on Windows, I'd be more than happy to help.
Alright. I know I'm bumping up a dead thread. I'm also new to this program.
And you know what? I've found myself snobbed. I realize a.) That Linux and Mac OS's are much closer, therefore easier to port.... and b.) The goal of this program is to make people rely less on Windows.
Then I get into an issue here: Windows users tend to not help small developers?
That's a hasty generalization, a clear logical fallacy.
I switched my netbook from XP to Ubuntu Netbook Remix, 9.04; however, being on a gaming rig such as my main computer, it is set up with a better sound system for recording. It isn't that I don't like Linux (I think Ubuntu is one of the best operating systems made. I love it. It's just, right now, it'd be a bad investment for me to throw money into it). Secondly, I enjoy smaller groups. Do you know why? Because they listen to the words of their users and actually care about what we think.
What you have done is snob the voices of windows users for petty social views. Correct, you cannot port windows without violating those views; but, I find them flawed to begin with.
Opening it to windows, while opening it to a larger audience, would, as the article stated, risk the support people becoming overwhelmed by mindless complaints. I have an answer to this problem: You're a small-time publisher to begin with. It doesn't matter if you port it to windows. One cannot become overwhelmed, because you're not big enough to become as such. As a linux lover, of course it'd be nice to go full linux, but not giving any support and snobbing windows users is just a low blow that will alienate and cause hate between possible users of your finely-made software.
I ask that you reconsider your position on a windows port. I do because I just don't feel windows is that bad. I even bought vista, and while it's a terrible OS, I stick with it. Why? I'm a gamer, too.
Thank you for your time reading this,
You're a small-time publisher to begin with. It doesn't matter if you port it to windows. One cannot become overwhelmed, because you're not big enough to become as such.
I am afraid this is what your entire post is based on, and is false, thus invalidating your entire post.
Take a look at Mantis. I am helping out the project with trying to organize in there, but it has overflown due to a lack of availiable time for developers to work on, and update issues when they do work on them. Take a look at the Manual, same story. There isn't enough time for the develoeprs to work on it. They are ALREADY overwhelmed.
As I have said in the past, the port to Windows would require a developer working on it and dedicating their time to supporting it and building it as a distribution. At the very least that requires a developer that uses Windows on a regular basis, which is a rarity in the community supporting Ardour at the moment, and noone has come forward wishing to take that load and proven themselves consistent enough to do so that I know of. (Could be wrong, but I haven't heard of anyone)
windows is shit. this is my very subject point of view to this topic, but still think its worth mentioning it here.
Hello people, as a user of Mac, Windows, and Linux all the time, and a developer on all as well, I felt compelled to throw my 2c in on this. Each of these operating systems have their inherent strengths and weaknesses.
Windows is easy to setup and everyone and their brother knows exactly how to use it. It's embedded in everything. It's really the best value for a casual computer user. However, it's proprietary code base and closed source curtail your options as a developer to the point where you have to use MS tools to develop. I like VB.NET, but not for everything. I also like C, but not for everything. In fact, I think I'd pick PERL for most things I have to accomplish....haha.
The Mac is a great multimedia OS, and has good support for most things UNIX. I use a Mac as my primary system, since it gives me everything, bash, Apple software, Office software, and a slew of pretty good dev tools. I have to agree though, that when you get into Apple's innards, they are fairly protective of it like Microsoft. This is the price of commercial OS software.
Linux is possibly the most amazingly extensible and customizable environment the world has ever seen. It's development tools are second to none, especially for C and C++. Not to mention it's all (well, mostly) open source, and free. With the developments from you guys with software like Ardour, JACK, Jamin, etc, it really showcases the efficiencies of the Linux OS and it's viability as a multimedia workstation OS. It is not without it's drawbacks though, just like any OS. For your basic user, it's NOT going to be easy to understand how to do some things. Think of trying to walk your mom through ./configure and sudo make install! And we think of these things as simple. Commercial OS software takes these "techy" processes out of view of the average user, who has no internal computing know-how, and probably doesn't want any. Although, with the newest Ubuntu releases I've been checking out, this is starting to go the other way too. (good for the average user!)
Moreover, no OS is superior to another. They just have different intended focal points. The best practice (IMO and experience) is to leverage the power of each for their intended purpose. Given recent advances in virtualization technology, you can have a real powerhouse multi-OS system all in one box.
Paul, I totally understand not wanting to release a Windows version. But I do understand why many people would want it. If your basing your development and fiscal model depending on people that want new development to be willing to pay for it, your going to see a much more informed and willing community in which to do business if you don't release a Windows version.
On a side note, a quick thank you to the Ardour/JACK development team. You guys have really done a stellar job on Ardour and JACK.
Hi. I have been using Linux on my desktop for about 5 years now so I am definitely a Linux only user. Lately I have been searching for software that would allow me and my friend (a windows user) to collaborate on some music projects.
Point 1. As I have been a commercial software developer I get all to well the point about all the work supporting a new platform especially when that platform is not the one you use for your daily life.
Point 2. It seems to me that the Ardour project has some financial problems and that the new "chose to pay" approche has been some what successful. Would the bigger user base for Ardour on windows generate more money for the project?
Point 3. I am following some other open source projects too and I cant see that a bigger community can be a problem.
What are your thoughts?
Read the link that Paul posted, I believe that sums up his views on 2 and 3 of your post rather well.
@tryken: i'd appreciate it if you would read the article that i linked to, and then show some signs of tackling the experience it reports and the argument it makes.
I am sorry. I forgot to mention that I did read the article and that my point is that I disagree with some of the things said in the article. I do not agree that a bigger community is bad for an open source project. I do agree that supporting an extra Os is a lot of unwanted work. Creating install packages and distribution is some of the most boring things a developer can do. And I do agree that your average windows user is less interested in helping a project or even understand why he should help a project but still I do not agree that excluding them will help the project.
However. Ardour is without at doubt open source and it is without a doubt cross platform. So following the open source philosophy. Anyone who is willing to do the relatively "easy" task of updating the existing port for windows and put in the enormous amount of time required to support it can.
Since Ardour is an open source project anyone can port it to windows or any other Os not currently supported and help support it.
I fully and totally understand that the current developers has enough to do already and do not want the huge amount of extra boring work of supporting another Os. And that asking them to do so is almost an insult.
I got an idea last night about creating an unofficial windows build and putting it on another web page just to see if it catches on and if we could attract some windows developers who was willing to put in the time of supporting it. If we cant and it doesn't work then we just drop it. What do you guys think about this idea?
One last word is that I am sorry if it seemed like I attacked anyone. It was not my intention.
Cinmay - please forgive me if you're already an Ardour developer. You mentioned being a developer but I don't recognise your name so I assume you must mean for some other projects.
It would help if you could clarify who you mean by "we". Are you offering to take on this extra work or are you implying that the existing dev team should undertake it? Because I think that is really at the heart of Paul's argument.
Towards the end of your last post you acknowledged that this would be a burdensome extra load. You also stated that it shouldn't be piled onto the (already overworked) dev team. So do you have someone else in mind when referring to "we"?
No. I am not a Ardour developer. When I was talking about we I was talking about the community in general. I don't like to front ideas without being ready to put my money where my mouth is and do the actual work too but I would much rather spend my time sending in patches on the new Ardour3 midi system witch is what I am really interested in.
That being said I do understand the value of community for the good of the software, support and even financial. So I would be willing to dig up some windows pc and putting a beta version on a newly created web page. But only if the rest of us (The community) and the main developers thought it was a good idea and maby someone would be willing to help me? :) It's been many years since I last did any sort of programing on windows and I dread having to learn a lot of stuff that I really don't want to know.
What's becoming clear here is that a lot of people seem to be reading Bryce's article but failing to understand it. And I don't really blame them. IMHO it isn't a well-written article. So here, in a nutshell, is the point that I think Bryce is trying (unsuccessfully) to make:-
The main thrust of Bryce's argument is that porting a small project to Windows has the effect of exposing it to a much wider audience. More eyes looking at the software results in a big increase in bug reports. But it doesn't necessarily bring in more developers to fix the bugs. Therefore it increases the burden of support for the existing developers. I suspect this is what Paul means when he refers to the social issues of porting Ardour to Windows. Unfortunately, Bryce's article is cluttered with too many (more spurious) arguments and one has to read the article very carefully (and several times) before that message crystalizes. To the casual reader, he simply seems to be arguing that it's better to sacrifice popularity and remain in blissful ignorance of the bugs. Or perhaps (to put it more charitably) it's better to hope that the bugs won't affect (or won't get noticed by) a smaller audience. To my mind that sounds like a bad case of wishful thinking so I can fully understand why people aren't persuaded by Bryce's article.
However, as one of the few people who HAS successfully ported Ardour to Windows I think I can speak authoritatively about the likely problems - and lack of POSIX compatibility is NOT one of them. In point of fact, Microsoft offers an implementation of POSIX (for Windows) that's reputedly every bit as good as anything you'll find from Apple. Furthermore there's a well-established open source project called Cygwin. Not only does it offer an exceptionally good POSIX environment for Windows but (with the sole exception of ALSA) everything needed to build Ardour is readily available both in source code and in binary form. I personally have compiled Ardour under Cygwin with almost no major changes needed. MIDI was my only significant area of concern as (I assume) it must also have been for the OS-X port.
But at the end of the day, Ardour is NOT a Windows program and therefore a Windows port wouldn't offer the things that Windows users take for granted (such as simple installation). This is where my experience differs from Bryce's. I agree with him that a Windows port would bring an increased burden of support but I saw no evidence that Ardour was any more buggy under Windows than under Linux or OS-X.
In my view the most likely issues would be installation issues. Ardour's dev team would inevitably find itself swamped with questions about Cygwin (or MinGW, or whatever). I support the view that this isn't (and shouldn't be) in their remit. In fact, to give just one example, I never found a way that Ardour could be reliably launched from a desktop icon. Can you imagine the uproar that'd be created in the Windows community by that problem alone?
Paul is right to say (at this point in time) that a wholesale launch of "Ardour for Windows" would be counter productive. There aren't enough developers to support it and there's no obvious reason to believe that new devs would come forward. Having said that Cinmay, I personally agree with you that a small scale "trial" could only be instructive. Nonetheless, the key to success would depend on finding the developers FIRST and starting the project SECOND. I don't think you'll get very far if you want to start a project, then simply "hope" that developers will join it.
John - the issues with a Windows port are far from limited to bug reports about Ardour. Every project I know that creates software for Windows, whether proprietary or open source, inevitably faces a large number of support issues that ultimately resolve to something entirely unrelated to the software in question. Given the current nature of the Ardour community, we have the expertise and even (in general) the willingness to try to tackle such questions when they arise on Linux, in part because we don't believe they will arise to the same extent and/or in quite the same way. However, I seriously doubt that our community would be capable of handling the myriad of Windows-naive user questions that we would face, and I equally doubt that our community would expand fast enough with Windows-centered knowledgeable and helpful members. I read quite a few audio tech related forums, and they almost as full as the same kind of "basic machine setup" issues as the ardour.org forums. I do not want myself or any potential Ardour developers (of any level, from design through extensive coding) to be spending time on issues like this. Its bad enough that distributions' mistakes and unwillingness to provide for our use cases means that we have to do this on Linux. Adding Windows to the mix would just be a disaster.
That certainly ties in with my experience Paul. I found nothing to indicate that Ardour might be flaky or less reliable under Windows. In fact on my PC (which houses both Windows and Linux) Ardour ran exactly the same under them both. The issues were more peripheral and mostly to do with the fact that Ardour didn't "behave like" a Windows program. For example, Ardour wouldn't run at all until I'd launched this dastardly thing called 'X' (of course, I understood this but I think it would have puzzled most Windows users). Furthermore, I could only launch Ardour reliably from a command line. And it only "looked good" on my left-hand monitor. Dragging it to my right-hand monitor made the fonts look very "fuzzy". None of these problems were in any way due to Ardour but I'm quite sure they'd generate a barrage of questions from confused Windows users.
Given enough developer time, I've no doubt these issues could be overcome (e.g. changing the menu font might have solved the font problem). But as you say, this kind of thing isn't within the remit of Ardour's development team.
So, to come full circle, my advice to Cinmay is that if he still wants to press forward, he needs to accept that "we" shouldn't be assumed to include the existing developers.
I definitely agree with you both.
I think windows support needs to fit in to the long term strategy of the development team. I think the core developers need to find out amongst them selves what should be Ardours stands on windows. Should windows be supported in 3.0 or 3.1 or 3.4 or should Ardour never support windows.
If a long term strategy is implemented then we can gradually start to work on windows support. Perhaps by attracting developers to a closed alpha or beta version so that all the installation and other windows specific issues can be solved before we get a flood of "Ardour wouldn't run at all until I'd launched this dastardly thing called 'X'" questions.
A solution might be to start very soft by creating a forum under Installation & Configuration called "windows development & beta testing" (or something better) to start attracting windows developers and give them a chance to communicate.
Sorry if my replies seem a little inconsistent. I'm just trying to get a feel for what peoples opinions are.
forart.it, please stop talking bullshit. i don't understand why you have to whine about POSIX. FYI, windows is posix-compliant too, and then what? posix (not) compliance is not what makes an OS a different platform. supporting windows is NOT a condition for being multiplatform. if some software supports more than 1 (one) platform then it's multiplatform, even if your platform is not supported.
and then, oh well... start lame arguments about why they won't make tremendous amount of work for you for free!
Windows users have Logic, Cubase, ProTools, Audition, and all the rest. Ardour at the moment is the biggest DAW fish in the Linux DAW pond. It would be a small fish in the Windows pond, and ANYTHING that distracts the Ardour developers from making Ardour the best Linux DAW out there is BAD for Ardour and BAD for Ardour's users, potential increased income for Paul from Windows users notwithstanding (and, Paul has been more than clear enough about his stance on this).
If I wanted to run Windows I'd use my Adobe Audition license on Windows. I choose to use Linux, and Ardour on Linux bests Audition (1.5 is what I own and used for quite a while) on Windows up one side and down the other.
And Bryce's article is spot-on. There are a few opensoure Unix-centric projects with enough developers to make a Windows port worthwhile (PostgreSQL, for instance, works quite well with little issue on Windows, but getting the developers to agree to do it and getting dedicated developers to support it was a multiyear rigamarole; I was there, packaging PostgreSQL RPMs at the time), but Ardour is duplication of effort in the Windows space since there are plenty of Windows DAW's out there. There is a paucity of really good DAWs in the Linux space; let's not dilute the development effort any more than it already is! And if you're looking for free-of-cost you shouldn't really be looking at Ardour anyway, IMHO.
You want to use Windows? Fine, but please leave the best (IMHO) Linux DAW out of it. Or port and support it yourself.
*mode rant=false musician/producer/Ardour subscriber=true*
Sorry, but speaking as a producer/engineer/musician (and someone who puts in a monthly donation via subscription to Ardour development), I get tired of the idea that everything should work on Windows. Windows is not the be-all end-all, and it is OK if the developer of a program chooses to not port that program to Windows; there are certainly plenty of Windows developers who are unwilling to support Linux for many of the same reasons Paul won't support Windows (support nightmare, few developers, low developer time, etc)!
*mode rant=false musician/producer/Ardour subscriber=true*
Hrmph, perhaps when we can get MOTU, Cubase, ProTools, and Logic support on Linux, then I might change my tune....
But Paul likely won't. And that's his call anyway.
For the record, Audition 1.5 and Ardour really are apples and oranges;)
Yes, apples and oranges.
Both are great sources of vitamin C, even if the 'user interfaces' in the manner of consuming them are different.
I can be just about as productive for the types of multitrack and touchup work I do in Audition as I can in Ardour; I can peel and eat an apple just about as quickly as I can peel and eat an orange, even though different tools and techniques are required. Both give me vitamin C... uh... good multitrack editing and touchup capabilities for song production from multiple, layered, sources. Even though the taste, texture, and varieties are different. I could comment on the details, but those aren't really important, except that with Ardour I have to add a good soundfile editor in the mix, where with Audition it's integrated.
Yes, apples and oranges. But both produce the same desired end result for my use cases.
I personally don't think there is much comparison of the multitrack capabilities of Audition 1.5(Haven't used the newer ones) and Ardour. That is what I was referring to. Audition, and before it Cool Edit was an amazing standalone destructive file editor(To be honest probably the best, and certainly my favorite), but the multitrack capabilities were a bit lacking to be honest when it comes to real time non-destructive mixing.
This is drifting off topic for this thread, but I'd be happy to comment in a thread about comparisons between Ardour and the others. Might even start one. Always good to have a comparison chart to see what different packages support, and how to do the same 'things' using different programs' various methodologies. Something like the Unix Rosetta Stone, but for DAW's.
If those who want a windows port are just looking for something free of cost there are options, apparently even an opensource option.
The closed source option is well known, reaper.
I only recently stumbled upon the open source option: http://www.experimentalscene.com/software/darkwave-studio/
I don't know anything about the quality of this software and I strongly suspect that this project does have legal problems, mainly due to it's use of Steinberg technologies and the resulting license issues.
Since ardour tries to stay in the legal area I suspect that it wouldn't provide what windows users expect, which would be mainly VST and maybe even rewire or ASIO support (whereas jack is superior to the later two, afaik).
I suspect a lack of VST support alone would be reason enough for lots of windows users not to use ardour.
It seems that in contrast to VST, AU support is legally possible, which might have been another reason why ardour was ported to that platform.
This is just another argument that hasn't been made yet, I added it for completeness's sake, feel free to correct me if I'm wrong on any of this.
The requested URL /drupal/foss-win-paradox was not found on this server.
I am a brand new subscriber today. From what I can tell I am the exact problem that is keeping development Ardour for Windows.
I didn't realize that I would not be given access on my current OS. I didn't read everything about Ardour. I just wanted it for what looks like it is excellent in the areas I wanted to address. I will go back to Audacity and make it and Avidemux work do the work I wanted Ardour to do for me. I will subscribe here while I wait for the windows version to come out.
Please help me.
Your subscriptions & donations are critical help that make it possible for full-time development of Ardour to continue. Your support is critical and much appreciated.
July goal US$6200 (US$74.4k/yr)
Subscribers 3069 US$7893.00/month
Support Ardour, get free upgrades: pay $1, $4, $10 or $50/month: