Realistically, you start getting diminishing returns at around (IIRC) 1/4 the sampling rate.
That's not true. The whole point is that if a signal is sampled at frequency f, then it can be reconstructed perfectly if its bandwidth is less than f/2. Go learn the maths instead of making vague statements that you think must be right intuitively, but which you actually don't know about.
equidistant 44kHz sampling just drops anything that does not fit into this sampling
but unless you first oversample and then selectively reduce the sample rate you do not know which are the "detailed" parts, which warrant a higher sampling frequency and which aren't. Secondly, since you refer to music, human hearing is bandlimited anyhow, so there is no point reconstructing freequencies outside of our perceptual range.
sampling is not guessing. The Nyquist sampling theorem shows that a signal that is sampled at twice the frequency of the highest frequency component in the signal can be reconstructed perfectly. With music this doesn't matter though, because humans have bandlimited hearing, so all we have to do is sample at twice the maximum frequency we can hear.
For example, if my source material didn't "need" 44kHz througout a song, could the sample rate be trimmed back in places while the sample size was increased?
interesting idea. The reason that we use 44kHz as the standard sampling rate is that most people's hearing ferequency cutoff is at about 20kHz, and hence the Nyquist sampling theorem shows that we need to sample at 40kHz. add a little bit to account for the fact that anti-aliasing filters aren't infinitely steep and we get 44kHz. So the real question is, in music are there blocks in which the highest frequency is below 20kHz? Then ask whether the reduced quantization brought by using higher sample sizes audible?
and audiophiles care to comment?
Re:Hyperchip Technology FAQ
on
Is Hyperchip Hype?
·
· Score: 2, Insightful
The site that was done by IBM for the last games was built strictly ro a specification delivered by the IOC. The spec didn't mention alt tags, and since it would cost a significant amount of cash to put them in on a site of that size, they didn't. Put the blame where you think it rests, but like many many large IT projects that have problems, I put it at the feet of those who wrote the spec.
To me it makes perfect sense for the spec to be developed in partnership with the experts, as well as the deliverable since most people who write specs for large IT projects don't really know what they want.
I would have thought that lossless compression of random data is impossible since compression schemes make use of the non randomness of data. Doesn't information theory prohibit this?
And it wasn't the judge that ordered the whole system be disconnected if you read the article. She ordered that systems with access to the private information be disconnected. If the DoI are not able to isolate the affected machines or subnets, but have to rely on yanking their whole network than that's their fault. I suspect that they didn't actually have to do this, but they are "making a point" to the judge about her ruling. a point that merely proves their incompetance further.
actually yes. quite frequently. It also explains why the last cashpoint I saw rebooting itself had 64Mb of RAM on board according to the startup stats. 64Mb!!! to run a bloody cashpoint.
By the way, this is not to diminish the quality of MS embedded solutions. I have no idea how solid they are, and I guess that most of the people here don't know either. That won't stop them having a rant and making some funny funny ha ha jokes about crashing jukeboxes/ATM/whatever.
Show me the RPM on their website. I agree with what you are saying: they are not technically comparable operations, but as far as the average user is concerned they are identical. "What do I have to do to be able to play the game?" Most uesrs don't care about the route. They care about the destination.
yes. just downloaded. played for about 20 minutes. about to delete. It's tedious, but pretty. BTW, appreciate you sticking your neck out on this forum.
Obtain the tuxracer-win32-.zip file from the Downloads page.
Unzip this file to your hard drive. You will need a program like Winzip to do this.
You're done!
installation for Linux
Make sure you have (and have correctly installed) the following libraries:
An implementation of the OpenGL API version 1.1 or greater (Mesa versions >= 3.2 work; see http://mesa3d.sourceforge.net). Note that you will need a hardware-accelerated implementation of OpenGL in order for Tux Racer to be playable.
The GLUT library, version 3.7 beta or greater. This is distributed in the MesaDemos package, so if you have installed Mesa you probably also have GLUT. Otherwise, see http://www.opengl.org.
Tcl Version 8.0 or greater.
(Optional) Simple DirectMedia Layer (SDL) Version 1.1.1 or greater. This is required for joystick support.
(Optional) SDL_mixer Version 1.0 or greater. This is required for sound and music support.
Obtain the tuxracer-.tar.gz and tuxracer-data-.tar.gz files from the Downloads page.
Unpack the code tarball:
shell$ tar xvfz tuxracer-.tar.gz
shell$ cd tuxracer-
Configure for your system:
shell$./configure
Many people will be able to run configure without passing any options. The more commonly-used configure options are:
--prefix=DIR: Specify where to install tuxracer. (The tuxracer binary will be placed in DIR/bin)
--with-tcl-libs=DIR: Specify Tcl library location
--with-tcl-inc=DIR: Specify Tcl header file location
--with-tcl-lib-name=NAME: Specify Tcl library base name
--with-gl-libs=DIR: Specify OpenGL library location
--with-gl-inc=DIR: Specify OpenGL header file location
--with-glut-libs=DIR: Specify GLUT library location
--with-glut-inc=DIR: Specify GLUT header file location
--enable-stencil-buffer: Use if your hardware has a stencil buffer
--with-data-dir=PATH: Location of tuxracer data directory (can be also configured in options file later)
Run./configure --help for a complete list of options.
Compile:
shell$ make
Tux Racer should compile cleanly, with few (if any) warnings. Please see the FAQ or our Support page if Tux Racer fails to compile.
Install the tuxracer binary:
shell$ make install
Unless you specified the --prefix option when you ran configure, this command will install the tuxracer binary in/usr/local/bin
Install the data files:
shell$ cd/usr/local/share
shell$ tar xvfz/path/to/tuxracer-data-.tar.gz
shell$ mv tuxracer-data- tuxracer
You may install the data files anywhere you wish, but tuxracer looks in/usr/local/share/tuxracer by default.
In fact it seems to me that the current spate of chart rubbish is mainly due to the fact that there is now _more_ music than ever being publsihed. allow me to explain.
Nowadays the variety of music that is available on CD is greater than it ever has been before. This means that I can go into a record store and buy exactly what I want to hear. The problem is that what I like is quite specialised and other people prefer other stuff that is similar, but not the same. In the past the quantity of records produced was smaller, so if it was in the ballpark of your taste then you bought it. Now you only buy a record if it is exactly what you want.
The upshot of this is that there are fewer large homogenous markets where everyone buys the same thing. But there is one massive market with growing disposable income and fairly predictable uniform tastes... Girls aged between 8 and 16. Consequently most of the stuff in the charts is produced specifically with this demographic in mind, and consequently is crap.
fortunately the charts mean little these days and I can still get hold of topnotchtuneage.
Having a heart-monitor would have probably prevented these deaths.
Actually it probably wouldn't. Over a million people take ecstacy each weekend in the UK, and the number of deaths related to the drug is approximately 50 in total. These deaths are mostly due to overheating. A few were due to excessive consumptioon of water which is exacerbated by inhibited kidney function, so water doesn't leave the body making it difficult to maintain homeostasis. A few were caused by an allergic reaction to the drug, but as a proportion of users ecstacy is "safer" in this regard than most over the counter pharmceuticals. Death due to heart failure is very rarely if ever recorded.
There is plenty of information about the risks associated with MDMA usage on the web, as well as steps that can be taken to reduce the physical risk. A far greater worry is the psychological damage caused by repeated usage. Minds are fragile things and the effect of these drugs on them is mostly unknown. Have a look at Alexander Shulgin's book on the subject, or kick off at google.
I did that and have read all about this before in new scientist and others. What I was challenging was that Loughborough uni got lots of money for it. Nowhere in the articles I read does it mention them.
actually it wasn't. What I mentioned here was taking three orthogonal synchronised images and using the data to attempt to construct a 3D model of the image.
In "the Matrix" and numerous other films and shows since many cameras were fired simultaneously and then motion video interpolation hardware from Snell and Willcox used to generate interpolated frames. Thus the special effect was created. This has absolutely nothing to do with the bird thing other than the fact that they both use more than one camera.
see http://www.snellwilcox.com/internet/press/releases/sep99/matrix.shtml
Instead, I would focus on speed (Can the MRI slices be taken fast enough to image an entire bird multiple times a second? Seems unlikely with the current generation of equipment)
I wasn't very clear. This was what I was assuming when I made the points above. The cell size of MRI is small (order of mm cubed) and in the time taken to make a measurement, the bird will move substantially. This is what I meant by "not being in the exact centre"
Using high speed cameras you have three or more synchronised shots of the bird taken from known viewpoints. Hence manipulation is simple as the images can be "alligned" easily. An MRI is essentially a set of data about a series of points in space rather than a projection onto 2D (as is a camera shot). Alligning these with each other for a moving object would be very non-trivial as you would have no "reference".
If they could fix up an MRI (Magnetic Resonance Imaging) machine they could also get information on muscle use and blood flow.
No they couldn't. An MRI scan requires that the part to be scanned is in the exact centre of the magnet that surrounds the bore. It also requires that the sftware that combines all of the sectional images into a 2-D slice and then a 3-D image know exactly where each image was taken from. For a flying bird exact position is variable and unpredictable. In orther words you are talking rubbish.
p>
2. It wouldn't really matter if it weren't because your average army camp isn't pointing an IR canera at everything that moves to see whether it is hot or not.
3. The most probably use of this kind of thing would be to set it off from a position fairly close to the target. ait for it to have a quick look around and feed video back etc. Then return to SAS type people who set it off. They then know what's going on and are better prepared to make their move.
Slashdot Mirror
mu-law and a-law are companding schemes, and have nothing to do with the sampling rate.
Realistically, you start getting diminishing returns at around (IIRC) 1/4 the sampling rate.
That's not true. The whole point is that if a signal is sampled at frequency f, then it can be reconstructed perfectly if its bandwidth is less than f/2. Go learn the maths instead of making vague statements that you think must be right intuitively, but which you actually don't know about.
equidistant 44kHz sampling just drops anything that does not fit into this sampling
but unless you first oversample and then selectively reduce the sample rate you do not know which are the "detailed" parts, which warrant a higher sampling frequency and which aren't. Secondly, since you refer to music, human hearing is bandlimited anyhow, so there is no point reconstructing freequencies outside of our perceptual range.
interesting idea. The reason that we use 44kHz as the standard sampling rate is that most people's hearing ferequency cutoff is at about 20kHz, and hence the Nyquist sampling theorem shows that we need to sample at 40kHz. add a little bit to account for the fact that anti-aliasing filters aren't infinitely steep and we get 44kHz. So the real question is, in music are there blocks in which the highest frequency is below 20kHz? Then ask whether the reduced quantization brought by using higher sample sizes audible?
and audiophiles care to comment?
To me it makes perfect sense for the spec to be developed in partnership with the experts, as well as the deliverable since most people who write specs for large IT projects don't really know what they want.
That's CICS.
actually that has more to do with the maturity of the CICS client for OS/2 than anything else.
actually yes. quite frequently. It also explains why the last cashpoint I saw rebooting itself had 64Mb of RAM on board according to the startup stats. 64Mb!!! to run a bloody cashpoint.
By the way, this is not to diminish the quality of MS embedded solutions. I have no idea how solid they are, and I guess that most of the people here don't know either. That won't stop them having a rant and making some funny funny ha ha jokes about crashing jukeboxes/ATM/whatever.
Show me the RPM on their website. I agree with what you are saying: they are not technically comparable operations, but as far as the average user is concerned they are identical. "What do I have to do to be able to play the game?" Most uesrs don't care about the route. They care about the destination.
installation for Windows 95/98/ME/NT/2000
Obtain the tuxracer-win32-.zip file from the Downloads page.
Unzip this file to your hard drive. You will need a program like Winzip to do this.
You're done!
installation for Linux
Make sure you have (and have correctly installed) the following libraries:
An implementation of the OpenGL API version 1.1 or greater (Mesa versions >= 3.2 work; see http://mesa3d.sourceforge.net). Note that you will need a hardware-accelerated implementation of OpenGL in order for Tux Racer to be playable.
The GLUT library, version 3.7 beta or greater. This is distributed in the MesaDemos package, so if you have installed Mesa you probably also have GLUT. Otherwise, see http://www.opengl.org.
Tcl Version 8.0 or greater.
(Optional) Simple DirectMedia Layer (SDL) Version 1.1.1 or greater. This is required for joystick support.
(Optional) SDL_mixer Version 1.0 or greater. This is required for sound and music support.
Obtain the tuxracer-.tar.gz and tuxracer-data-.tar.gz files from the Downloads page.
Unpack the code tarball:
shell$ tar xvfz tuxracer-.tar.gz
shell$ cd tuxracer-
Configure for your system:
shell$
Many people will be able to run configure without passing any options. The more commonly-used configure options are:
--prefix=DIR: Specify where to install tuxracer. (The tuxracer binary will be placed in DIR/bin)
--with-tcl-libs=DIR: Specify Tcl library location
--with-tcl-inc=DIR: Specify Tcl header file location
--with-tcl-lib-name=NAME: Specify Tcl library base name
--with-gl-libs=DIR: Specify OpenGL library location
--with-gl-inc=DIR: Specify OpenGL header file location
--with-glut-libs=DIR: Specify GLUT library location
--with-glut-inc=DIR: Specify GLUT header file location
--enable-stencil-buffer: Use if your hardware has a stencil buffer
--with-data-dir=PATH: Location of tuxracer data directory (can be also configured in options file later)
Run
Compile:
shell$ make
Tux Racer should compile cleanly, with few (if any) warnings. Please see the FAQ or our Support page if Tux Racer fails to compile.
Install the tuxracer binary:
shell$ make install
Unless you specified the --prefix option when you ran configure, this command will install the tuxracer binary in
Install the data files:
shell$ cd
shell$ tar xvfz
shell$ mv tuxracer-data- tuxracer
You may install the data files anywhere you wish, but tuxracer looks in
You're done!
300dB? you'd be dead.
no, really. You _would_ die.
Nowadays the variety of music that is available on CD is greater than it ever has been before. This means that I can go into a record store and buy exactly what I want to hear. The problem is that what I like is quite specialised and other people prefer other stuff that is similar, but not the same. In the past the quantity of records produced was smaller, so if it was in the ballpark of your taste then you bought it. Now you only buy a record if it is exactly what you want.
The upshot of this is that there are fewer large homogenous markets where everyone buys the same thing. But there is one massive market with growing disposable income and fairly predictable uniform tastes... Girls aged between 8 and 16. Consequently most of the stuff in the charts is produced specifically with this demographic in mind, and consequently is crap.
fortunately the charts mean little these days and I can still get hold of top notch tuneage.
Actually it probably wouldn't. Over a million people take ecstacy each weekend in the UK, and the number of deaths related to the drug is approximately 50 in total. These deaths are mostly due to overheating. A few were due to excessive consumptioon of water which is exacerbated by inhibited kidney function, so water doesn't leave the body making it difficult to maintain homeostasis. A few were caused by an allergic reaction to the drug, but as a proportion of users ecstacy is "safer" in this regard than most over the counter pharmceuticals. Death due to heart failure is very rarely if ever recorded.
There is plenty of information about the risks associated with MDMA usage on the web, as well as steps that can be taken to reduce the physical risk. A far greater worry is the psychological damage caused by repeated usage. Minds are fragile things and the effect of these drugs on them is mostly unknown. Have a look at Alexander Shulgin's book on the subject, or kick off at google.
In "the Matrix" and numerous other films and shows since many cameras were fired simultaneously and then motion video interpolation hardware from Snell and Willcox used to generate interpolated frames. Thus the special effect was created. This has absolutely nothing to do with the bird thing other than the fact that they both use more than one camera.
see http://www.snellwilcox.com/internet/press/release
I wasn't very clear. This was what I was assuming when I made the points above. The cell size of MRI is small (order of mm cubed) and in the time taken to make a measurement, the bird will move substantially. This is what I meant by "not being in the exact centre"
Using high speed cameras you have three or more synchronised shots of the bird taken from known viewpoints. Hence manipulation is simple as the images can be "alligned" easily. An MRI is essentially a set of data about a series of points in space rather than a projection onto 2D (as is a camera shot). Alligning these with each other for a moving object would be very non-trivial as you would have no "reference".
If they could fix up an MRI (Magnetic Resonance Imaging) machine they could also get information on muscle use and blood flow.
No they couldn't. An MRI scan requires that the part to be scanned is in the exact centre of the magnet that surrounds the bore. It also requires that the sftware that combines all of the sectional images into a 2-D slice and then a 3-D image know exactly where each image was taken from. For a flying bird exact position is variable and unpredictable. In orther words you are talking rubbish.
p>
2. It wouldn't really matter if it weren't because your average army camp isn't pointing an IR canera at everything that moves to see whether it is hot or not.
3. The most probably use of this kind of thing would be to set it off from a position fairly close to the target. ait for it to have a quick look around and feed video back etc. Then return to SAS type people who set it off. They then know what's going on and are better prepared to make their move.