Welcome to www.esiq.org

ï»¿Copyright music Copyright Music in Order to Protect Future Profits If you are a budding artist seeking to copyright music that you have labored over, there is good news. Many people confuse copyrighting music with registering music and they are two different things. According to the law in the United States, once you have written or recorded your music in a permanent form, it is copyrighted. Of course, it might help to first understand what it means to copyright music in the first place. A copyright is a certain legal protection that is offered to those who compose creative works. Whether those works be art, music, or the written word. According to the U. S. constitution there are limits that can be placed on the amount of time that the work is exclusively protected. If you copyright music, this means that you and you alone have the right to use your work or allow others to use your work. You also have the right to distribute copies of your work. Whether those copies are in the form of written or sheet music or recorded music to the public as well as the right to perform your music for the public. There is something called fair use that despite your copyright; music written or recorded by you may be used for the purpose of research, news reporting, commentary, or criticism. In other words, there are times when the use of copyrighted material is deemed appropriate without the consent of the one holding the copyright. To copyright music alone is not enough in many cases to protect your music, at least not without going through a lot of hoops in order to do so. One of the things you can do in order to protect your copyright is provide notice of copyright. This is a simple step that includes writing a simple statement to the effect of the word "copyright", the date, and your name at the bottom of your sheet music or on the case for the recording or the actual recording itself. CD's are the most common means for recording devices today and a notice of copyright can easily be added to the exterior of your CD or on your label if you have one printed. In case you are wondering: why copyright music? The answer is rather simple, so others cannot take credit for your creative genius. For an added layer of protection you may want to consider registering your copyright as well. Registering your copyright will provide you with formal legal documentation of your ownership of your music should anyone else attempt to lay claim to your music or any other dispute about true ownership/authorship come about. You must have your copyright registered if you wish to file a copyright infringement suit and it is, in my humble opinion, better to not only copyright music early on but also to register your copyright before it could possibly become an issue. Registering while not entirely painless is not as difficult a process as you might think. Basically it involves filling out an application, paying a filing fee (check with the U. S. Copyright Office for the current amount), and a copy of the work being protected (this will not be returned). It's also important to remember that your music doesn't have to be published in order for you to obtain a copyright. Music should be copyrighted and registered long before the publication process in order to protect your rights as the creator of the music. Whether you are dabbling with cute little limericks or writing masterpieces and concertos or are rock and rolls next super star you want to make sure to copyright music earlier rather than later for the best possible outcome should problems arise.

Web Hosting - Bandwidth and Server Load, What's That? Two key performance metrics will impact every web site owner sooner or later: bandwidth and server load. Bandwidth is the amount of network capacity available, and the term actually covers two different aspects. 'Bandwidth' can mean the measure of network capacity for web traffic back and forth at a given time. Or, it sometimes is used to mean the amount that is allowed for some interval, such as one month. Both are important. As files are transferred, emails sent and received, and web pages accessed, network bandwidth is being used. If you want to send water through a pipe, you have to have a pipe. Those pipes can vary in size and the amount of water going through them at any time can also vary. Total monthly bandwidth is a cap that hosting companies place on sites in order to share fairly a limited resource. Companies monitor sites in order to keep one site from accidentally or deliberately consuming all the network capacity. Similar considerations apply to instantaneous bandwidth, though companies usually have such large network 'pipes' that it's much less common for heavy use by one user to be a problem. Server load is a more generic concept. It often refers, in more technical discussions, solely to CPU utilization. The CPU (central processing unit) is the component in a computer that processes instructions from programs, ordering memory to be used a certain way, moving files from one place to the next and more. Every function you perform consumes some CPU and its role is so central (hence the name) that it has come to be used as a synonym for the computer itself. People point to their case and say 'That is the CPU'. But, the computer actually has memory, disk drive(s) and several other features required in order to do its job. Server load refers, in more general circumstances, to the amount of use of each of those other components in total. Disk drives can be busy fetching files which they do in pieces, which are then assembled in memory and presented on the monitor, all controlled by instructions managed by the CPU. Memory capacity is limited. It's often the case that not all programs can use as much as they need at the same time. Special operating system routines control who gets how much, when and for how long, sharing the total 'pool' among competing processes. So, how 'loaded' the server is at any given time or over time is a matter of how heavily used any one, or all, of these components are. Why should you care? Because every web site owner will want to understand why a server becomes slow or unresponsive, and be able to optimize their use of it. When you share a server with other sites, which is extremely common, the traffic other sites receive creates load on the server that can affect your site. There's a limited amount you can do to influence that situation. But if you're aware of it, you can request the company move you to a less heavily loaded server. Or, if the other site (which you generally have no visibility to) is misbehaving, it's possible to get them moved or banned. But when you have a dedicated server, you have much more control over load issues. You can optimize your own site's HTML pages and programs, tune a database and carry out other activities that maximize throughput. Your users will see that as quicker page accesses and a more enjoyable user experience.

Web Hosting - Sharing A Server – Things To Think About You can often get a substantial discount off web hosting fees by sharing a server with other sites. Or, you may have multiple sites of your own on the same system. But, just as sharing a house can have benefits and drawbacks, so too with a server. The first consideration is availability. Shared servers get re-booted more often than stand alone systems. That can happen for multiple reasons. Another site's software may produce a problem or make a change that requires a re-boot. While that's less common on Unix-based systems than on Windows, it still happens. Be prepared for more scheduled and unplanned outages when you share a server. Load is the next, and more obvious, issue. A single pickup truck can only haul so much weight. If the truck is already half-loaded with someone else's rocks, it will not haul yours as easily. Most websites are fairly static. A reader hits a page, then spends some time skimming it before loading another. During that time, the server has capacity to satisfy other requests without affecting you. All the shared resources - CPU, memory, disks, network and other components - can easily handle multiple users (up to a point). But all servers have inherent capacity limitations. The component that processes software instructions (the CPU) can only do so much. Most large servers will have more than one (some as many as 16), but there are still limits to what they can do. The more requests they receive, the busier they are. At a certain point, your software request (such as accessing a website page) has to wait a bit. Memory on a server functions in a similar way. It's a shared resource on the server and there is only so much of it. As it gets used up, the system lets one process use some, then another, in turn. But sharing that resource causes delays. The more requests there are, the longer the delays. You may experience that as waiting for a page to appear in the browser or a file to download. Bottlenecks can appear in other places outside, but connected to, the server itself. Network components get shared among multiple users along with everything else. And, as with those others, the more requests there are (and the longer they tie them up) the longer the delays you notice. The only way to get an objective look at whether a server and the connected network have enough capacity is to measure and test. All systems are capable of reporting how much of what is being used. Most can compile that information into some form of statistical report. Reviewing that data allows for a rational assessment of how much capacity is being used and how much is still available. It also allows a knowledgeable person to make projections of how much more sharing is possible with what level of impact. Request that information and, if necessary, get help in interpreting it. Then you can make a cost-benefit decision based on fact.