32 vs 64 bit, Someone school me!
- Thread starter iJackPot
- Start date
Wallengard
Manipulator of energy
32 bit will only allow you to use up to 4gb of memory while 64 bit will allow you to use as much as you could possibly need for a long time.
For the most part, and I'm not a very very technical guy, 64 bit is faster and allows for more resources to be used.
I'd suggest to go with 64 bit wherever you can. 32 bit will probably eventually stop being made all together.
I'm sure if you wait around or actually search the Internet yourself, you'll get a much more detailed response than I can provide.
For the most part, and I'm not a very very technical guy, 64 bit is faster and allows for more resources to be used.
I'd suggest to go with 64 bit wherever you can. 32 bit will probably eventually stop being made all together.
I'm sure if you wait around or actually search the Internet yourself, you'll get a much more detailed response than I can provide.
Last edited:
KonKossKang
Ozagas
Recently found out even if you have ram left over, some progs don't use more of it on 32bit apps.
64bit can use up to 128gb of ram but more than 8 is farfetched. 4gb can get filled up with effort though.
For S1/reason I stick on 32bit because of rewire with reason 5/I am not fond of jbridge yet.
If you have 64bit plugins for everything, use 64 bit version.
64bit can use up to 128gb of ram but more than 8 is farfetched. 4gb can get filled up with effort though.
For S1/reason I stick on 32bit because of rewire with reason 5/I am not fond of jbridge yet.
If you have 64bit plugins for everything, use 64 bit version.
bandcoach
Zukatoku - Mod Scientist
32 bit vs 64 bit in a daw and vsts/plug-ins is not only about ram but about precision of the audio engine and its calculations/mathematics: 32 bit floating point vs 64 bit floating point; see this for further disambiguation
https://www.izotope.com/support/kb/...bit_and_64-bit_in_software_plug-ins_and_audio
the ram argument is for operating systems i.e. x86 vs x64 in win terms and the equivalent in mac os and linux and variants.
ps
64 bit systems can access more than 16 exabytes of RAM/hard disk storage space - that is more than 16 x 10[sup]18[sup] (16 000 000 000 000 000 000 +) bytes (actually 2[sup]64[/sup] which is 18 446 744 073 709 551 616 bytes which is exactly 16 exabytes: this is equivalent to 16 million terabytes of RAM
some operating systems limit how much ram can be accessed: 128gb is one such limitation, however, one of the os's for server infrastructure (on HP's os's) allows up to 1 yottabyte of hard disk space to be accessed (that is 10[sup]24[/sup] bytes of storage space, 1 million exabytes and therefore 1 trillion terabytes)
to garner some measure of the scale
https://www.izotope.com/support/kb/...bit_and_64-bit_in_software_plug-ins_and_audio
the ram argument is for operating systems i.e. x86 vs x64 in win terms and the equivalent in mac os and linux and variants.
ps
64 bit systems can access more than 16 exabytes of RAM/hard disk storage space - that is more than 16 x 10[sup]18[sup] (16 000 000 000 000 000 000 +) bytes (actually 2[sup]64[/sup] which is 18 446 744 073 709 551 616 bytes which is exactly 16 exabytes: this is equivalent to 16 million terabytes of RAM
some operating systems limit how much ram can be accessed: 128gb is one such limitation, however, one of the os's for server infrastructure (on HP's os's) allows up to 1 yottabyte of hard disk space to be accessed (that is 10[sup]24[/sup] bytes of storage space, 1 million exabytes and therefore 1 trillion terabytes)
to garner some measure of the scale
| unit | expressed in kilobytes | bytes |
| kilo | 1000[sup]1[/sup] | 10[sup]3[/sup] |
| mega | 1000[sup]2[/sup] | 10[sup]6[/sup] |
| giga | 1000[sup]3[/sup] | 10[sup]9[/sup] |
| tera | 1000[sup]4[/sup] | 10[sup]12[/sup] |
| peta | 1000[sup]5[/sup] | 10[sup]15[/sup] |
| exa | 1000[sup]6[/sup] | 10[sup]18[/sup] |
| zetta | 1000[sup]7[/sup] | 10[sup]21[/sup] |
| yotta | 1000[sup]8[/sup] | 10[sup]24[/sup] |
Last edited: