When you speak to your attorney and accountant (if you don't have one of both, you should) look into the possibility of forming an LLC, S-Corp, or C-corp. Working as an independent contractor can cost you fortune come tax time.
Also, remember that as a corporation (not sure about LLC)the company is allowed to "loan" you up to $10,000, upon which you are not obliged to pay payroll taxes. This little loophole has saved my butt more than once.
Above all else, DO EVERYTHING BY THE BOOK, especially when it comes to taxes. Do not listen to those on this esteemed forum who would recommend that you not take care of zoning issues and the like--they have never been on the bad end of an inquiry. Granted, chances are, you won't get caught. If you do, THE RESULTS CAN BE CATASTROPHIC. It is so easy to take care of little issues like this that there is really no excuse for not doing so.
Good luck.
Hmmmm. At the studio that I run with my wife and two friends of ours, if everything is working, I'm "the computer guy." If something breaks and I manage to fix it quickly and without apparent effort, I'm "A Genius!". If something breaks and I have to spend the rest of the day futzing with it, I'm "a musician who fixes computers."
JSP I know nothing of, so I will not comment on it here. RE: PHP and ASP, unless you want to spend a huge amount of money that doesn't really have to be spent and lock yourself into the Microsoft Way, avoid ASP at all costs. PHP in combination with one of many fine open source databases (I'm fond of MYSQL, but these are other good options out there) is free, non-proprietary, and easy to work with. All you need is an old Linux box, a text editor (emacs for me, but pick your own flavor), and a week's worth of evenings to study and you'll be ready to rock, even if you're like me and are not an uberhacker by any stretch of the imagination. For MYSQL, a copy of PHPMyAdmin is useful too, as it makes administering your database a LOT easier.
mmmmmmm...this is a good point, especially from a legal/professional responsibility point of view. If my code is used to run a website that promotes my studio, no big deal; it does not have to live up the same expectation as the code that runs a water distribution system does. So, do we call code used in civil infrastructure design and implementation the work of engineers, while the (essentially) similar code that manages the function of my servers the work of a code monkey?
This question could also be applied to those of us that are A/V "engineers" as well as coders/software "engineers". Within A/V circles, if you know how to use the equipment in a studio environment to maximum effect and troubleshoot problems, you are known as an "engineer." Does the fact that we are able to implement, run and troubleshoot audio/video recording and editing systems make us "engineers" in the purest sense of the word? Certainly not. By the same token, is the fact that one is able to build boxen, integrate a server farm, write scripts, properly implement ipchains, or successfully install Slackware on siad boxen make us "engineers?" Once again, no. Most of the audio video engineers that I know (including myself) know very little about the low level workings of the equipment that we use and maintain. We are, in a sense, administrators: we know how to use the equipment to maximum artistic and technical effect and are able to resolve problems as they appear, but if asked to explain the nuts and bolts of the gear we know how to use so well, we are most often at a loss. The same thing applies to those of us that are highly able "users" of various boxen. We can manipulate these machines to do all sorts of nifty, useful stuff, which is great, but few of us could explain, let alone design, the inner workings of the machines we use so well.
To those that defy the above descriptions, I salute you. To the rest, we have to face up to the fact that we are users, albeit good ones.
Excellent point. If a word is so hard to spell that even after 6 years of higher education I can't spell it properly, I might as well avoid using it, as I shall do in the future.
Come on y'all--there's been more dicussion about this guy's rig than about the drivers. I'm sorry if you're bitter that your box is less than state of the art, but dems da breaks, kids.
In the meantime, kudos to NVidia for getting these out before anyone needed them.
This is exactly the sort of thing that will enable Linux to become a viable alternative for audio production. This statement may be anathema to many Linux masochists, but as a producer and musician I want a product that installs with a mouse click (or single, simple command line statement)and works. No hours of reseach and piling through newsgroups trying to find what little dependecies are unresolved. No having some uberuser tell me that all I need to do is write a device driver real quick and I'll be ready to go. Dealing with pro audio on Mac and Windows boxen is still troublesome now, even for those of use that know what the hell we're doing. On Linux, it simply is not an option unless you are highly skilled with the OS to begin with, and 99% of the musicians, producers, and audio engineers out there are not.
Whatever failures it might have, whatever it might lack right now, however much you might want to bitch about it, Eastman's work here is exactly what Linux Pro Audio needs if it is EVER going to be a viable alternative to M$ or Apple.
I'm looking forward to being able to type format c:. This brings me one step closer.
If there were adequate pro audio tools available for Linux that I could depend on for day to day production duties, I would take my Win 2000 lisences and chuck them in the garbage. Until Aurdour is really up and running (read as stable binaries that a musician, not a programmer, can install), no dice.
I think that we audio folks are going to have to wait for Ardour to finish 1.x development before we have a powerful, stable pro audio app on Linux. Aside from the cool factor/interesting challenge of getting Cubase to run under an emulator, I can't see it being up to the task of serious multichannel audio production, at least not for a looonnnnnngggggg time.
Slashdot Mirror
When you speak to your attorney and accountant (if you don't have one of both, you should) look into the possibility of forming an LLC, S-Corp, or C-corp. Working as an independent contractor can cost you fortune come tax time. Also, remember that as a corporation (not sure about LLC)the company is allowed to "loan" you up to $10,000, upon which you are not obliged to pay payroll taxes. This little loophole has saved my butt more than once. Above all else, DO EVERYTHING BY THE BOOK, especially when it comes to taxes. Do not listen to those on this esteemed forum who would recommend that you not take care of zoning issues and the like--they have never been on the bad end of an inquiry. Granted, chances are, you won't get caught. If you do, THE RESULTS CAN BE CATASTROPHIC. It is so easy to take care of little issues like this that there is really no excuse for not doing so. Good luck.
Hmmmm. At the studio that I run with my wife and two friends of ours, if everything is working, I'm "the computer guy." If something breaks and I manage to fix it quickly and without apparent effort, I'm "A Genius!". If something breaks and I have to spend the rest of the day futzing with it, I'm "a musician who fixes computers."
JSP I know nothing of, so I will not comment on it here. RE: PHP and ASP, unless you want to spend a huge amount of money that doesn't really have to be spent and lock yourself into the Microsoft Way, avoid ASP at all costs. PHP in combination with one of many fine open source databases (I'm fond of MYSQL, but these are other good options out there) is free, non-proprietary, and easy to work with. All you need is an old Linux box, a text editor (emacs for me, but pick your own flavor), and a week's worth of evenings to study and you'll be ready to rock, even if you're like me and are not an uberhacker by any stretch of the imagination. For MYSQL, a copy of PHPMyAdmin is useful too, as it makes administering your database a LOT easier.
mmmmmmm...this is a good point, especially from a legal/professional responsibility point of view. If my code is used to run a website that promotes my studio, no big deal; it does not have to live up the same expectation as the code that runs a water distribution system does. So, do we call code used in civil infrastructure design and implementation the work of engineers, while the (essentially) similar code that manages the function of my servers the work of a code monkey?
Not sure....processing......
This question could also be applied to those of us that are A/V "engineers" as well as coders/software "engineers". Within A/V circles, if you know how to use the equipment in a studio environment to maximum effect and troubleshoot problems, you are known as an "engineer." Does the fact that we are able to implement, run and troubleshoot audio/video recording and editing systems make us "engineers" in the purest sense of the word? Certainly not.
By the same token, is the fact that one is able to build boxen, integrate a server farm, write scripts, properly implement ipchains, or successfully install Slackware on siad boxen make us "engineers?" Once again, no.
Most of the audio video engineers that I know (including myself) know very little about the low level workings of the equipment that we use and maintain. We are, in a sense, administrators: we know how to use the equipment to maximum artistic and technical effect and are able to resolve problems as they appear, but if asked to explain the nuts and bolts of the gear we know how to use so well, we are most often at a loss. The same thing applies to those of us that are highly able "users" of various boxen. We can manipulate these machines to do all sorts of nifty, useful stuff, which is great, but few of us could explain, let alone design, the inner workings of the machines we use so well.
To those that defy the above descriptions, I salute you. To the rest, we have to face up to the fact that we are users, albeit good ones.
Sweet--thanks. Mom always said that admitting when you're wrong is good for your karma.
Excellent point. If a word is so hard to spell that even after 6 years of higher education I can't spell it properly, I might as well avoid using it, as I shall do in the future.
Berke Breathed actually used the color Chartruse.
touche....
Come on y'all--there's been more dicussion about this guy's rig than about the drivers. I'm sorry if you're bitter that your box is less than state of the art, but dems da breaks, kids. In the meantime, kudos to NVidia for getting these out before anyone needed them.
This is exactly the sort of thing that will enable Linux to become a viable alternative for audio production. This statement may be anathema to many Linux masochists, but as a producer and musician I want a product that installs with a mouse click (or single, simple command line statement)and works. No hours of reseach and piling through newsgroups trying to find what little dependecies are unresolved. No having some uberuser tell me that all I need to do is write a device driver real quick and I'll be ready to go. Dealing with pro audio on Mac and Windows boxen is still troublesome now, even for those of use that know what the hell we're doing. On Linux, it simply is not an option unless you are highly skilled with the OS to begin with, and 99% of the musicians, producers, and audio engineers out there are not. Whatever failures it might have, whatever it might lack right now, however much you might want to bitch about it, Eastman's work here is exactly what Linux Pro Audio needs if it is EVER going to be a viable alternative to M$ or Apple. I'm looking forward to being able to type format c:. This brings me one step closer.
If there were adequate pro audio tools available for Linux that I could depend on for day to day production duties, I would take my Win 2000 lisences and chuck them in the garbage. Until Aurdour is really up and running (read as stable binaries that a musician, not a programmer, can install), no dice.
I think that we audio folks are going to have to wait for Ardour to finish 1.x development before we have a powerful, stable pro audio app on Linux. Aside from the cool factor/interesting challenge of getting Cubase to run under an emulator, I can't see it being up to the task of serious multichannel audio production, at least not for a looonnnnnngggggg time.