The video component of Digital Cinema Packages (DCP) for commercial movie theatres (digital cinemas, as opposed to the "traditional" 35mm film cinemas) is a stream of JPEG 2000 images.
If you're allergic to compiling (sadly, so many people are), most authors have a RPM version available.
If you're talking about compiling a tarball and installing it (configure;make;make install) that's generally a bad idea on something like Red Hat, Fedora, or Centos. You're almost always better off to create a rpm or compile a srpm if it's available. A lot of srpms for Fedora can be compiled for Centos with little or no modification.
Of course, if you're talking about compiling one single executable that can live in your own personal ~/bin directory, that's a horse of a different colour.
There are good and valid reasons why Centos is currently falling behind RHEL in doing updates. Red Hat is making it more difficult for Centos to keep up. This may not be intended to target Centos, but rather Oracle who has been using Red Hat's own work to sell a competing tech support service.
However, Centos gets caught in the crossfire. This email from Johnny Hughes lays out some of the issues that Centos now has to deal with that were never an issue before.
Here is what he has to say:
QUOTE: Yes, and NOW the release process is MUCH harder.
Red Hat used to have an AS release that contained everything... we build that and we get everything. Nice and simple. Build all the packages, look at it against the AS iso set... done. Two weeks was about as long as it took.
Now, for version 6, they have:
Red Hat Enterprise Linux Server (v. 6) Red Hat Enterprise Linux Workstation (v. 6) Red Hat Enterprise Linux Desktop (v. 6) Red Hat Enterprise Linux HPC Node (v. 6) Red Hat Enterprise Linux Workstation FasTrack (v. 6) Red Hat Enterprise Linux Server FasTrack (v. 6) Red Hat Enterprise Linux Desktop FasTrack (v. 6) Red Hat Enterprise Linux Scalable File System (v. 6) Red Hat Enterprise Linux Resilient Storage (v. 6) Red Hat Enterprise Linux Load Balancer (v. 6) Red Hat Enterprise Linux HPC Node FasTrack (v. 6) Red Hat Enterprise Linux High Performance Network (v. 6) Red Hat Enterprise Virtualization
They have the same install groups with different packages based on the above groupings, so we have to do some kind of custom generation of the comps files to things work.
They have created an optional channel in several of those groupings that is only accessible via RHN and they do not put those RPMS on any ISOs... and they have completely changed their "Authorized Use Policy" so that we can NOT login to RHN and use anything that is not on a public FTP server or on an ISO set... effectively cutting us off from the ability to check anything on the optional channel.
Now we have to engineer a compilation of all those groupings, we have to figure out what parts of the optional channels go at the point release and which ones do not (the ones that are upgrades). Sometimes the only way to tell is when something does not build correctly and you have reverse an optional package to a previous version for the build, etc.
We have to use anaconda to build our ISOs and upstream is using "something else" to build theirs.. so anaconda NEVER works anymore out of the box. We get ISOs (or usb images) that do not work and have to basically redesign anaconda.
We can't look at upstream build logs, we can't get all the binary RPMs for testing and be within the Terms of Service.
And with the new release, it seems that they have purposely broken the rpmmacros, and do not care to fix it:
So, trust me, it is MUCH more complicated now than it was with previous releases to build.
With the 5.7 release, there were several SRPMS that did not make it to the public FTP server without much prompting from us. And with the Authorized Use Policy, I can not just go to RHN and grab that SRPM and use it. If it is not public, we can no longer release it.
So, the short answer is, it now takes longer. END OF QUOTE
I own and operate a movie theatre, and I had my 35mm film equipment removed and replaced with a digital cinema setup earlier this year. In place of my film projector, lamphouse and platter I now have a rackmount cinema server and a digital projector. It takes up a lot less space in the projection room.
The movie studios are pushing for theatres to convert to digital due to the cost savings from not having to create all of those prints on film.
Digital movies and trailers are currently distributed on CRU hard drives. There is talk of going to satellite distribution instead, but at the moment I get hard drives couriered to me in Pelican cases. I copy the movie from the CRU drive onto a raid in my cinema server. Once the CRU drive is copied onto the server I'm done with it and can put it back in the case it came in; the movie actually plays directly from the server.
My picture is brighter and crisper than it ever was with film, it's rock-steady with absolutely no jitter, and scratches and dust are a non-issue. The sound is also vastly better than what I had with film.
My customers don't really seem to notice the picture quality, but I have had a lot of comments and compliments on the digital cinema sound.
From the point of view of the guy who operates this stuff (I'm a projectionist, of course) digital is a lot easier and less time consuming than playing movies on film. The cinema server works like a giant ipod -- I copy the movie onto the server (which takes a half-hour or so but I just go away and come back when it's done), then set up a playlist with all of the trailers and whatever else I want to show with it, and insert cues to do things like turn the lights up and down in the auditorium. The playlist takes about ten minutes to set up. That's it. I press Play to start each show, and at the end of the week I spent two minutes hitting Delete to erase the old movie.
Compare that to film, where I would spend an hour or so getting the movie off of the shipping reels and onto the platter, then spend a half-hour per day cleaning and oiling the projector, plus five minutes threading up each movie on the projector. And another 40 minutes or so tearing the movie down and putting it back on the shipping reels when I've finished playing that movie.
The negative side of the digital versus film is that a fault is less obvious. If the film is buggered up or a gear on the projector is stripped it's usually pretty easy to see the fault and possibly fix it or take steps to deal with it somehow before there is an actual problem that keeps the movie off-screen. (I've actually hand cranked my platter to keep the movie going when one of the motors quit in the middle of a show.) A fault in the digital is both less obvious and more likely to be impossible for the projectionist (me) to fix and deal with.
But digital cinema is sure nice. Having spent my life working with film to this point I wasn't really sure that I would like it, but having had the digital cinema setup for a number of months now I won't say that I miss film. As far as I'm concerned it's all about the results and I'm providing a better presentation for the customers now than I ever could before, so what's not to like?
In some ways digital is probably more idiot-proof than film.
I got my own grant money so it should be between me and my funders how I spend it (and how I assign my own copyright).
If your grant money is funded, in whole or in part, by the taxpayer then the taxpayer has a right to the fruits of the money he has spent on your research.
If it's a privately funded grant, then by all means do as you wish.
What about some of the modern structured BASIC languages? Though I haven't really paid much attention to BASIC for some years now, BASIC has most of the features that you list in your question.
I don't think it's ever taken more then 5 minutes for me to renew my drivers license or license plates or do anything else in regard to that stuff.
Of course, I live in a small town and the local "motor license issuer" is a small office just down the street. They are also sell insurance and package tours....
My first computer was a Commodore 64 and I learned programming and general computer use on that, and most stuff was either Basic or Machine Language on that. When I got an XT and wanted to learn programming, I looked at both Turbo C and Turbo Basic in the local Radio Shack store (they were side by side on the shelf and exactly the same price, as I recall) and bought Turbo Basic because I figured I knew a bit more about Basic and it would be easier to get started doing things.
In hindsight I should have bought and learned Turbo C instead. I got to be pretty darn good with Basic programming and wrote some cool stuff with Turbo Basic (including some "shareware" that made a pretty decent buck for a while), but some years later I discovered two things:
1. C wasn't very hard to learn; in fact it took me less time to "get started" with C than it did when I started learning Basic programming on the XT.
2. I could do some cool stuff with Basic but similar stuff could be done more easily and directly with C. In other words, stuff that required a lot of "bending" in Basic could just be done in C without much fuss at all.
So in hindsight, I wish I had read the Turbo C Reference Manual when I first got my XT.
Even though I did well in typing class, somehow I never really got good at typing numbers. I don't think we spent enough time on that.
However, today I can type numbers very well. I never use the numeric keypad to do it, though. I always type the numbers using the top keys. Why? Because I learned to type numbers by typing programs from Compute! magazine into my Commodore 64. This was many years after I learned to type in school, but I spent many hours typing in line after line of numbers with Compute!'s MLX program and now I can type numbers as well as I can type text.
When I was in high school I learned to type on big manual Underwood typewriters in typing class. I also learned some other skills in that class that seem to be going the way of a lost art, such as how to properly fold a letter to fit into an envelope.
In my opinion, typing class was the most useful class that I took in high school. I learned skills that I use literally every day.
On two occasions I have had courier drivers post a "you weren't here" card on the front door exactly two inches away from the "For Deliveries Ring Bell at the Back Door" sign.
I would be extremely interested in this if it could create and save digital cinema files for professional digital projector/servers for movie theatres. For creating custom policy trailers and pre-show ads.
Your employees have no business sticking USB drives into process control computers.
Until the software, firmware, what-have-you needs to be updated or changed. "We now need to change the rotation speed from X to Y in sub-vector Z". Would you like to do that all by keyboarding each one of the 25,000 or so machines?
Electronics repair techs are a dying (or dead) breed. Everyone I know who used to do that stuff has either died or moved on to other things. Few folks even know what a capacitor is, and even fewer know how to determine its size or even whether it's actually working.
I watched the end credits of the Justin Bieber movie. Many of the songs were written by someone else, and a few of the songs were "Written By Justin Bieber,..... " and a list of about 5 or 6 other people.
So I really doubt that he can write his own music.
I do some work for a radio station that puts out "Fifty Thousand Watts!". Their transmitter tower is really really high (I never asked exactly how high) and it's on top of a hill about a mile away from the studio. I always figured that was just because those locations were convenient places to put the studio and the tower, but perhaps it's a safety thing?
Your tax rebate idea still wouldn't work. Instead of a reasoned vote you would simply get a "lemme check the box and I'll get out of here" vote, which would quite likely be worse.
The quorum idea, on the other hand, would be workable if you had an interested voters list. If everyone who "cares" signed up for that list, and a minority of those on the list voted, that would signal that the choices offered were unsatisfactory and a do-over would be required.
Slashdot Mirror
The video component of Digital Cinema Packages (DCP) for commercial movie theatres (digital cinemas, as opposed to the "traditional" 35mm film cinemas) is a stream of JPEG 2000 images.
This isn't reading, but for entertainment he should look at old time radio. Old Time Radio
Thousands of marvellous radio plays as mp3's, no reading required.
Just the thing for long trips in a car or commuting, too.
Westerns, detective stories, comedies, it's all there. And it's free and legal, too.
It's my understanding that, unlike Centos, SL isn't as concerned with exact binary compatibility with RHEL. So, if it compiles and runs, ship it.
If you're allergic to compiling (sadly, so many people are), most authors have a RPM version available.
If you're talking about compiling a tarball and installing it (configure;make;make install) that's generally a bad idea on something like Red Hat, Fedora, or Centos. You're almost always better off to create a rpm or compile a srpm if it's available. A lot of srpms for Fedora can be compiled for Centos with little or no modification.
Of course, if you're talking about compiling one single executable that can live in your own personal ~/bin directory, that's a horse of a different colour.
There are good and valid reasons why Centos is currently falling behind RHEL in doing updates. Red Hat is making it more difficult for Centos to keep up. This may not be intended to target Centos, but rather Oracle who has been using Red Hat's own work to sell a competing tech support service.
However, Centos gets caught in the crossfire. This email from Johnny Hughes lays out some of the issues that Centos now has to deal with that were never an issue before.
Here is what he has to say:
QUOTE:
Yes, and NOW the release process is MUCH harder.
Red Hat used to have an AS release that contained everything ... we build that and we get everything. Nice and simple. Build all the packages, look at it against the AS iso set ... done. Two weeks was about as long as it took.
Now, for version 6, they have:
Red Hat Enterprise Linux Server (v. 6)
Red Hat Enterprise Linux Workstation (v. 6)
Red Hat Enterprise Linux Desktop (v. 6)
Red Hat Enterprise Linux HPC Node (v. 6)
Red Hat Enterprise Linux Workstation FasTrack (v. 6)
Red Hat Enterprise Linux Server FasTrack (v. 6)
Red Hat Enterprise Linux Desktop FasTrack (v. 6)
Red Hat Enterprise Linux Scalable File System (v. 6)
Red Hat Enterprise Linux Resilient Storage (v. 6)
Red Hat Enterprise Linux Load Balancer (v. 6)
Red Hat Enterprise Linux HPC Node FasTrack (v. 6)
Red Hat Enterprise Linux High Performance Network (v. 6)
Red Hat Enterprise Virtualization
They have the same install groups with different packages based on the above groupings, so we have to do some kind of custom generation of the comps files to things work.
They have created an optional channel in several of those groupings that is only accessible via RHN and they do not put those RPMS on any ISOs ... and they have completely changed their "Authorized Use Policy" so that we can NOT login to RHN and use anything that is not on a public ... effectively cutting us off from the ability to check anything on the optional channel.
FTP server or on an ISO set
Now we have to engineer a compilation of all those groupings, we have to figure out what parts of the optional channels go at the point release and which ones do not (the ones that are upgrades). Sometimes the only way to tell is when something does not build correctly and you have reverse an optional package to a previous version for the build, etc.
We have to use anaconda to build our ISOs and upstream is using "something else" to build theirs .. so anaconda NEVER works anymore out of the box. We get ISOs (or usb images) that do not work and have to basically redesign anaconda.
We can't look at upstream build logs, we can't get all the binary RPMs for testing and be within the Terms of Service.
And with the new release, it seems that they have purposely broken the rpmmacros, and do not care to fix it:
https://bugzilla.redhat.com/show_bug.cgi?id=743229
So, trust me, it is MUCH more complicated now than it was with previous releases to build.
With the 5.7 release, there were several SRPMS that did not make it to the public FTP server without much prompting from us. And with the Authorized Use Policy, I can not just go to RHN and grab that SRPM and use it. If it is not public, we can no longer release it.
So, the short answer is, it now takes longer.
END OF QUOTE
I own and operate a movie theatre, and I had my 35mm film equipment removed and replaced with a digital cinema setup earlier this year. In place of my film projector, lamphouse and platter I now have a rackmount cinema server and a digital projector. It takes up a lot less space in the projection room.
The movie studios are pushing for theatres to convert to digital due to the cost savings from not having to create all of those prints on film.
Digital movies and trailers are currently distributed on CRU hard drives. There is talk of going to satellite distribution instead, but at the moment I get hard drives couriered to me in Pelican cases. I copy the movie from the CRU drive onto a raid in my cinema server. Once the CRU drive is copied onto the server I'm done with it and can put it back in the case it came in; the movie actually plays directly from the server.
My picture is brighter and crisper than it ever was with film, it's rock-steady with absolutely no jitter, and scratches and dust are a non-issue. The sound is also vastly better than what I had with film.
My customers don't really seem to notice the picture quality, but I have had a lot of comments and compliments on the digital cinema sound.
There is an official specification for digtal cinema.
From the point of view of the guy who operates this stuff (I'm a projectionist, of course) digital is a lot easier and less time consuming than playing movies on film. The cinema server works like a giant ipod -- I copy the movie onto the server (which takes a half-hour or so but I just go away and come back when it's done), then set up a playlist with all of the trailers and whatever else I want to show with it, and insert cues to do things like turn the lights up and down in the auditorium. The playlist takes about ten minutes to set up. That's it. I press Play to start each show, and at the end of the week I spent two minutes hitting Delete to erase the old movie.
Compare that to film, where I would spend an hour or so getting the movie off of the shipping reels and onto the platter, then spend a half-hour per day cleaning and oiling the projector, plus five minutes threading up each movie on the projector. And another 40 minutes or so tearing the movie down and putting it back on the shipping reels when I've finished playing that movie.
The negative side of the digital versus film is that a fault is less obvious. If the film is buggered up or a gear on the projector is stripped it's usually pretty easy to see the fault and possibly fix it or take steps to deal with it somehow before there is an actual problem that keeps the movie off-screen. (I've actually hand cranked my platter to keep the movie going when one of the motors quit in the middle of a show.) A fault in the digital is both less obvious and more likely to be impossible for the projectionist (me) to fix and deal with.
But digital cinema is sure nice. Having spent my life working with film to this point I wasn't really sure that I would like it, but having had the digital cinema setup for a number of months now I won't say that I miss film. As far as I'm concerned it's all about the results and I'm providing a better presentation for the customers now than I ever could before, so what's not to like?
In some ways digital is probably more idiot-proof than film.
I got my own grant money so it should be between me and my funders how I spend it (and how I assign my own copyright).
If your grant money is funded, in whole or in part, by the taxpayer then the taxpayer has a right to the fruits of the money he has spent on your research.
If it's a privately funded grant, then by all means do as you wish.
What about some of the modern structured BASIC languages? Though I haven't really paid much attention to BASIC for some years now, BASIC has most of the features that you list in your question.
I doubt many arcade games from last century even had copy protection.
Many arcade PCB's had components that were embedded in epoxy to prevent anyone from tampering with them.
I don't think it's ever taken more then 5 minutes for me to renew my drivers license or license plates or do anything else in regard to that stuff.
Of course, I live in a small town and the local "motor license issuer" is a small office just down the street. They are also sell insurance and package tours....
My first computer was a Commodore 64 and I learned programming and general computer use on that, and most stuff was either Basic or Machine Language on that. When I got an XT and wanted to learn programming, I looked at both Turbo C and Turbo Basic in the local Radio Shack store (they were side by side on the shelf and exactly the same price, as I recall) and bought Turbo Basic because I figured I knew a bit more about Basic and it would be easier to get started doing things.
In hindsight I should have bought and learned Turbo C instead. I got to be pretty darn good with Basic programming and wrote some cool stuff with Turbo Basic (including some "shareware" that made a pretty decent buck for a while), but some years later I discovered two things:
1. C wasn't very hard to learn; in fact it took me less time to "get started" with C than it did when I started learning Basic programming on the XT.
2. I could do some cool stuff with Basic but similar stuff could be done more easily and directly with C. In other words, stuff that required a lot of "bending" in Basic could just be done in C without much fuss at all.
So in hindsight, I wish I had read the Turbo C Reference Manual when I first got my XT.
Even though I did well in typing class, somehow I never really got good at typing numbers. I don't think we spent enough time on that.
However, today I can type numbers very well. I never use the numeric keypad to do it, though. I always type the numbers using the top keys. Why? Because I learned to type numbers by typing programs from Compute! magazine into my Commodore 64. This was many years after I learned to type in school, but I spent many hours typing in line after line of numbers with Compute!'s MLX program and now I can type numbers as well as I can type text.
When I was in high school I learned to type on big manual Underwood typewriters in typing class. I also learned some other skills in that class that seem to be going the way of a lost art, such as how to properly fold a letter to fit into an envelope.
In my opinion, typing class was the most useful class that I took in high school. I learned skills that I use literally every day.
Just use a question mark in place of the unknown character.
Privoxy. Does more than adblock plus and works with any web browser
On two occasions I have had courier drivers post a "you weren't here" card on the front door exactly two inches away from the "For Deliveries Ring Bell at the Back Door" sign.
Many places have a residency requirement (or at least a preference), and many more charge a higher tuition for foreign students.
I would be extremely interested in this if it could create and save digital cinema files for professional digital projector/servers for movie theatres. For creating custom policy trailers and pre-show ads.
Your employees have no business sticking USB drives into process control computers.
Until the software, firmware, what-have-you needs to be updated or changed. "We now need to change the rotation speed from X to Y in sub-vector Z". Would you like to do that all by keyboarding each one of the 25,000 or so machines?
Electronics repair techs are a dying (or dead) breed. Everyone I know who used to do that stuff has either died or moved on to other things. Few folks even know what a capacitor is, and even fewer know how to determine its size or even whether it's actually working.
I watched the end credits of the Justin Bieber movie. Many of the songs were written by someone else, and a few of the songs were "Written By Justin Bieber, ..... " and a list of about 5 or 6 other people.
So I really doubt that he can write his own music.
Why do they need your SSN to process a damages claim?
Should be: http://techie-buzz.com/tech-news/mysql-com-database-compromised-sql-injection.html
(There is an extra l in the summary's link.)
I do some work for a radio station that puts out "Fifty Thousand Watts!". Their transmitter tower is really really high (I never asked exactly how high) and it's on top of a hill about a mile away from the studio. I always figured that was just because those locations were convenient places to put the studio and the tower, but perhaps it's a safety thing?
Your tax rebate idea still wouldn't work. Instead of a reasoned vote you would simply get a "lemme check the box and I'll get out of here" vote, which would quite likely be worse.
The quorum idea, on the other hand, would be workable if you had an interested voters list. If everyone who "cares" signed up for that list, and a minority of those on the list voted, that would signal that the choices offered were unsatisfactory and a do-over would be required.