In Reply to: RE: Jriver Internal Volume transparency posted by fmak on September 26, 2015 at 22:02:08:
Fred,You are confusing two separate issues in computer architecture:
1. Data formats, e.g. 32 bit floating point vs. 64 bit floating point.
2. Memory addressing: 32 bit processor addresses vs. 64 bit processor addresses.These are different parts of the processor architecture. Large (e.g. 64 bit) data formats have been around for decades and work perfectly well with 32 bit memory addressing, providing that the file sizes involved are below 2 GB (or possibly 4 GB). People were using large floating point numbers back in the 1960's, but there was no need for 64 bit addressing until computers starting having more than 4 GB of RAM.
About the only connection between the two items comes with large audio files, where a high sampling rate and a long word length might make the file too large to be handled efficiently by a 32 bit program that was written to use memory mapped file access or to preload an entire track into RAM. You can tell if this is applicable to an audio program by looking at its memory utilization with a task monitor. If the 64 bit data path is just used for on the fly signal processing, then there will be no significant increase in memory utilization, and hence no connection to 32/64 application / OS question.
Tony Lauck
"Diversity is the law of nature; no two entities in this universe are uniform." - P.R. Sarkar
This post is made possible by the generous support of people like you and our sponsors:
Follow Ups
- RE: Jriver Internal Volume transparency - Tony Lauck 09/27/1510:06:21 09/27/15 (1)
- Good Clarification - fmak 11:03:49 09/27/15 (0)