There are plenty of people out there running a JACK setup with a far more customizable digital audio workflow, sure the combinations aren't standardized and you can mix and match sequencers/synths/mixers etc, but this flexibilitty is a feature not a bug.
Of the relatively few people i know that use pro tools, most have never ending trouble with having it actually function (at least on windows). Extra cost, plsus lock in, and lack of flexibility (comparatively) in workflow. I can see why people take issue with releasing something as 'open source' in a format that is hindering to the cause.
You don't need another spin, since kde/xfce etc come on the install dvd.
Aside from emergency recovery situations, there is no reason to use livecds any more. If you are going to install an os do a full install, not an extermely gimped install just so your install media is the size of an old school cd.
With developer tools and a whole lot more stuff than most sane people need my fedora installs tend to hit 6-8gb max, this is nothing for hard disks/ssd today.
I find whether you like gnome3 is highly dependent on how many applications you typically have open at once, with the fewer you have open the more usable gnome being.
The eeepc I'm on at present has (counts) 43 windows open, and on my desktop I can be using 100+ depending upon task. Quickly accessing the window I want under gnome3 is a real pain compared to say, kde. So I just use kde.
The grandparents get by with gnome3 just fine though, they rarely have more than 4-5 things open at a time.
It's the Actel ProAsic3, it fits the redacted portions that only show the first letters and in the scanned nda doc and some quotes about claims from the manufacturer exactly match it.
I never would have have quit Linux due to its tavlet UI in March 2011 if I knew what was in store for Win 8.
There are more desktop environments than what ubuntu ships with you know, hell if you install a non-gimped version of linux (like the fedora dvd installer) you can install multiple at the same time and select them when you log in.
I too dislike gnome3 and unity etc, that's why I use kde. There are other options also if you like.
It just re-establishes the fact that frankly, Microsoft's developer tools are one of the best ones out there
Moreso, it just establishse that windows is the primary target of microsoft developer tools (no surprise), whereas with open source tools it tends to be the afterthought after linux.
I'd personally take emacs over visual studio, but I'm an odd linux user/developer, I'm sure I'm not the only one though.
What do you classify as "Low latency" for audio(in milliseconds)?
I tend to run about 4 or 8 msec with jack, this is with a multitude of programs being able to use it unlike windows. Some people run lower (you can set it as low as you want.. if your hardware can take it is another matter) but there isn't much need and I think pcie bus latency + other factors might start to kick in.
The best windows setups I've seen still tend to hit around 10-12msec with it more typically being 20-30. Although here seems to say 3 might be possible with asio, with 11-12 being more typical minimum. Mac systems I've seen never tend to go below 6, which is fine.
For things that don't require low latency, and have issue with a callback interface that wants specific numbers of samples etc, what is stopping them just making a small fifo buffer to emulate the behaviour they are doing now with pulse? Just feed jack from the buffer.
The developer of pulseaudio admitted it was made for low power consumption, a few ease of use things were mentioned, but they were for the user not developers (and all of which weren't really a problem with jack by then anyway, like hot plugging etc)
aside from the extra resource consumption (there is no need to run low latency if you don't want to) Jack handles any case pulse can, and then some.
They have, pulse for end users and Jack for people who care about their audio.
Why not one interface? Because the low latency goals of jack conflict with the low power goals of pulseaudio (designed for use on netbooks and tablets etc) why desktop users had to suffer so much into the pulse transition just to cater to that crowd I have no idea.
At present there are two systems people use for audio, pulseaudio comes with most distributions these days standard (for end users, rather limited and full of latency) and JACK (for professional audio usage, uses a callback interface though)
low latency and low power tend to be at odds with each other, what with low latency frequently waking up the cpu etc. The only reason pulseaudio was went with on the desktop is for some reason they seem to think we care about a fraction of a percent more cpu usage on my plugged in desktop machine over a more useful audio subsystem. (Their reasoning being TABLETS ARE THE FUTURE!, or something along those lines)
Alsa is where the drivers are, having separation of drivers from audio server makes sense, and alsa -> jack can achieve far lower workable latencies than coreaudio by itself can (which itself would have driver and audio server separation internally, too).
Linux is as bloated or as thin as you want it to be, just because the average person seems to want a bunch of whiz bang features doesn't mean you have to have them.
Hardware support for one. Not even talking about computers, if you plug in a random pcie card to a mac pro what are the odds of success? on linux it tends to be a case of "has the chipset been out for more than 3-6 months"
You are also limited in the updates you receive, I have a g4 mac I'm quite fond of and it can still function using a 3.3 kernel and the latest of packages (with a lightweight DE of course). Mac os X support died for it quite some time ago.
Mac os X is very much a second class citizen in OSS world, for instance if you run JACK on os x coreaudio midi doesn't interact with the jack midi system, still worthwhile for the extra functionality it provides over coreaudio but problematic when using professional audio programs designed for JACK.
Little things like that, everywhere. Hell even it's use of semaphores/mutex's is slightly different than that of linux (one uses named the other doesn't). One of my friends runs os x and loves some of the software i use on linux, if it's close enough to functioning I'll help him port it but it really can be a pain.
But instead, you distributed the song to thousands of people.
You seed every download until you hit the thousands of uploads mark? Must have a lot of upload capacity. Even small downloads won't hit that because the smaller the download the more seeders there tends to be so less likelihood of your machine distributing.
Hardware must allow 3rd party software to run on it. That was the Atari thing.
Now turn that 180 degrees around with: Software must allow installation on 3rd party hardware. That was the Pystar thing.
So they couldn't be more opposite issues if they tried. The Atari issue has no relevance whatsoever here.
I see it as an interoperability thing, so it is the same.
X must not have any artificial hinderences to work with random Y, this is what is being argued in both the case of hardware and software. For some reason they let it slide with hardware, but not software? this is inconsistent.
And I am making a copy of your comment in my mind when I read it, there are exceptions so these things can be used you know, just like how copying a program to ram so it can run is 'copyright infringement'
Actually, nigger meant negro which is literally the word for 'black' in Spanish and Portuguese, it stems from the latin word 'niger' which also means 'black'
There is a solution to this.. just start out with gimp and the interface will be natural to you.
Most photoshop users aren't professional and haven't paid for their versions of photoshop, the first time anyone complains of gimp not being like photoshop I try to ascertain if it was pirated, if so, they have no reason to bitch. If not, why should it matter to them? They already own photoshop.
It was the same deal with people complaining about blenders old interface, to those who were used to it it was most efficient. And the results were hard to argue with.
Slashdot Mirror
We no longer have crucifiction or burning at the stake, for example.
Why would you do that when shooting people in the head is so much less effort?
There are plenty of people out there running a JACK setup with a far more customizable digital audio workflow, sure the combinations aren't standardized and you can mix and match sequencers/synths/mixers etc, but this flexibilitty is a feature not a bug.
Of the relatively few people i know that use pro tools, most have never ending trouble with having it actually function (at least on windows). Extra cost, plsus lock in, and lack of flexibility (comparatively) in workflow. I can see why people take issue with releasing something as 'open source' in a format that is hindering to the cause.
militarized -past participle, past tense of militarize (Verb) Verb:
1. Give (something, esp. an organization) a military character or style: "militarized police forces". 2. Equip or supply with military resources.
No, something tells me you don't know what militarized means.
You don't need another spin, since kde/xfce etc come on the install dvd.
Aside from emergency recovery situations, there is no reason to use livecds any more. If you are going to install an os do a full install, not an extermely gimped install just so your install media is the size of an old school cd.
With developer tools and a whole lot more stuff than most sane people need my fedora installs tend to hit 6-8gb max, this is nothing for hard disks/ssd today.
I find whether you like gnome3 is highly dependent on how many applications you typically have open at once, with the fewer you have open the more usable gnome being.
The eeepc I'm on at present has (counts) 43 windows open, and on my desktop I can be using 100+ depending upon task. Quickly accessing the window I want under gnome3 is a real pain compared to say, kde. So I just use kde.
The grandparents get by with gnome3 just fine though, they rarely have more than 4-5 things open at a time.
Someone actually likes unity? I'm amazed.
Gnome3 is dodgy, but that is what we have kde/xfce/etc for.
It's the Actel ProAsic3, it fits the redacted portions that only show the first letters and in the scanned nda doc and some quotes about claims from the manufacturer exactly match it.
I never would have have quit Linux due to its tavlet UI in March 2011 if I knew what was in store for Win 8.
There are more desktop environments than what ubuntu ships with you know, hell if you install a non-gimped version of linux (like the fedora dvd installer) you can install multiple at the same time and select them when you log in.
I too dislike gnome3 and unity etc, that's why I use kde. There are other options also if you like.
It just re-establishes the fact that frankly, Microsoft's developer tools are one of the best ones out there
Moreso, it just establishse that windows is the primary target of microsoft developer tools (no surprise), whereas with open source tools it tends to be the afterthought after linux.
I'd personally take emacs over visual studio, but I'm an odd linux user/developer, I'm sure I'm not the only one though.
Wireshark can do this.
What do you classify as "Low latency" for audio(in milliseconds)?
I tend to run about 4 or 8 msec with jack, this is with a multitude of programs being able to use it unlike windows. Some people run lower (you can set it as low as you want.. if your hardware can take it is another matter) but there isn't much need and I think pcie bus latency + other factors might start to kick in.
The best windows setups I've seen still tend to hit around 10-12msec with it more typically being 20-30. Although here seems to say 3 might be possible with asio, with 11-12 being more typical minimum. Mac systems I've seen never tend to go below 6, which is fine.
For things that don't require low latency, and have issue with a callback interface that wants specific numbers of samples etc, what is stopping them just making a small fifo buffer to emulate the behaviour they are doing now with pulse? Just feed jack from the buffer.
The developer of pulseaudio admitted it was made for low power consumption, a few ease of use things were mentioned, but they were for the user not developers (and all of which weren't really a problem with jack by then anyway, like hot plugging etc)
aside from the extra resource consumption (there is no need to run low latency if you don't want to) Jack handles any case pulse can, and then some.
They have, pulse for end users and Jack for people who care about their audio.
Why not one interface? Because the low latency goals of jack conflict with the low power goals of pulseaudio (designed for use on netbooks and tablets etc) why desktop users had to suffer so much into the pulse transition just to cater to that crowd I have no idea.
At present there are two systems people use for audio, pulseaudio comes with most distributions these days standard (for end users, rather limited and full of latency) and JACK (for professional audio usage, uses a callback interface though)
low latency and low power tend to be at odds with each other, what with low latency frequently waking up the cpu etc. The only reason pulseaudio was went with on the desktop is for some reason they seem to think we care about a fraction of a percent more cpu usage on my plugged in desktop machine over a more useful audio subsystem. (Their reasoning being TABLETS ARE THE FUTURE!, or something along those lines)
Alsa is where the drivers are, having separation of drivers from audio server makes sense, and alsa -> jack can achieve far lower workable latencies than coreaudio by itself can (which itself would have driver and audio server separation internally, too).
Linux is as bloated or as thin as you want it to be, just because the average person seems to want a bunch of whiz bang features doesn't mean you have to have them.
So, how am I limited by using Mac OS?
Hardware support for one. Not even talking about computers, if you plug in a random pcie card to a mac pro what are the odds of success? on linux it tends to be a case of "has the chipset been out for more than 3-6 months"
You are also limited in the updates you receive, I have a g4 mac I'm quite fond of and it can still function using a 3.3 kernel and the latest of packages (with a lightweight DE of course). Mac os X support died for it quite some time ago.
Mac os X is very much a second class citizen in OSS world, for instance if you run JACK on os x coreaudio midi doesn't interact with the jack midi system, still worthwhile for the extra functionality it provides over coreaudio but problematic when using professional audio programs designed for JACK.
Little things like that, everywhere. Hell even it's use of semaphores/mutex's is slightly different than that of linux (one uses named the other doesn't). One of my friends runs os x and loves some of the software i use on linux, if it's close enough to functioning I'll help him port it but it really can be a pain.
But instead, you distributed the song to thousands of people.
You seed every download until you hit the thousands of uploads mark? Must have a lot of upload capacity. Even small downloads won't hit that because the smaller the download the more seeders there tends to be so less likelihood of your machine distributing.
Hardware must allow 3rd party software to run on it. That was the Atari thing. Now turn that 180 degrees around with: Software must allow installation on 3rd party hardware. That was the Pystar thing. So they couldn't be more opposite issues if they tried. The Atari issue has no relevance whatsoever here.
I see it as an interoperability thing, so it is the same.
X must not have any artificial hinderences to work with random Y, this is what is being argued in both the case of hardware and software. For some reason they let it slide with hardware, but not software? this is inconsistent.
Agree with the rest though
And I am making a copy of your comment in my mind when I read it, there are exceptions so these things can be used you know, just like how copying a program to ram so it can run is 'copyright infringement'
No one buys Macs just for the hardware,
Tell that to all those people running linux on their mac mini.
would you be able to link to that? I'm interested in reading about it.
Actually, nigger meant negro which is literally the word for 'black' in Spanish and Portuguese, it stems from the latin word 'niger' which also means 'black'
Different products suit different needs, the same in regards to workflows. Everything being the same is actually a bad thing.
There is a solution to this.. just start out with gimp and the interface will be natural to you.
Most photoshop users aren't professional and haven't paid for their versions of photoshop, the first time anyone complains of gimp not being like photoshop I try to ascertain if it was pirated, if so, they have no reason to bitch. If not, why should it matter to them? They already own photoshop.
It was the same deal with people complaining about blenders old interface, to those who were used to it it was most efficient. And the results were hard to argue with.
Other people have done this before.. it's not like you'd be the first to block google's tracking