32bit apps in window xp VS 32bit apps in 64bit window xp

bluesj · 21st February 2006, 05:50 AM

operating 32bit apps in window xp VS operating 32bit apps in 64bit window xp through 32bit emulation wow

what is more good?

thank you

digitaldrummer · 21st February 2006, 06:26 AM

32-bit on ia64 is in emulation. 32-bit on x64 (or AMD64, or EM64T...) is native (not emulation), however, you don't necessarily get the true benefits an x64 app would get (such as the linear memory model). You may realize better performance if you run multiple instances of 32-bit apps and have lots of RAM (i.e., way more that 4GB)... or maybe not. the sticky point for many is that 32-bit drivers (kernel mode) don't work on x64 and must be recompiled to work.

Mike

bluesj · 21st February 2006, 10:29 AM

Quote:

Originally Posted by digitaldrummer

32-bit on ia64 is in emulation. 32-bit on x64 (or AMD64, or EM64T...) is native (not emulation), however, you don't necessarily get the true benefits an x64 app would get (such as the linear memory model). You may realize better performance if you run multiple instances of 32-bit apps and have lots of RAM (i.e., way more that 4GB)... or maybe not. the sticky point for many is that 32-bit drivers (kernel mode) don't work on x64 and must be recompiled to work.

Mike

thank you
i got critical info from u.
i also got similar answer from other people
have a nice day

neilwilkes · 22nd February 2006, 04:22 PM

There are other, more serious implications too.
According to Joe Bryant of Universal Audio, the following also applies.

Win64 supports two application modes: 32-bit (for compatability), and 64-bit. If an app is compiled to run in 64-bit mode, it can't load 32-bit plugins or add-ons. Also, since there's no x87 FPU in 64-bit mode, all the floating point code must be reworked to run on the vector units. So for example, if a plugin has optimized assembly code (like most good native plugs), these have to be completely rewritten to work in 64-bit mode on the new floating point hardware! Some plugins may already have been written to use the vector units (like some synths and impulse 'verbs), so these would port more easily assuming the vector code is the only low-level assembly code.

As appealing as 64-bit mode is, the sonic benefits simply aren't there. In fact, the internal precision of the vector units is lower than the x87 FPU! The vector units can process 32- and 64-bit floats, but their internal resolution is fixed at the same precision. The x87 FPU on the other hand, always retains 80- or 160-bit internal prescion, and only drops the precision when results are saved to memory. Also, when 64-bit precision is used in the vector unit, performance is cut in half, so intensive 64-bit float code will be slower than 32-bit code.

The bottom line is that because of the availability of this more efficient, but lower resolution 32-bit float mode in Win64, some plugin vendors may opt to drop precision when supporting 64-bit application mode, and sound quality will be lower than what's currently available in the current 32-bit mode.

More can sometimes be less!

theblue1 · 22nd February 2006, 10:19 PM

Darned if you do... danged if you don't.

Damn.

manning1 · 23rd February 2006, 01:45 AM

i wont be moving to 64 bit OS any time soon.
i find it amusing that some folks feel they have to have a 64 bit OS.
its just an OS...focus on the things that matter. input sig chain and convertors etc etc.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Converting 32bit > 24bit (What program?)	dreamaudio	So much gear, so little time!	2	14th December 2005 10:50 PM
Is this the future of audio apps?	Hammer v2	Music computers	3	22nd February 2005 08:19 AM
Linux audio apps	natpub	Music computers	26	16th September 2004 04:35 PM

21st February 2006, 05:50 AM	#1
bluesj Gear Head Join Date: Aug 2005 Posts: 39	32bit apps in window xp VS 32bit apps in 64bit window xp operating 32bit apps in window xp VS operating 32bit apps in 64bit window xp through 32bit emulation wow what is more good? thank you

22nd February 2006, 10:19 PM	#5
theblue1 Lives for gear Join Date: Mar 2005 Location: Long Beach, CA Posts: 5,761	Darned if you do... danged if you don't. Damn. __________________ biz \| profile \| songblog \| acoustic \| mutant roots pop

23rd February 2006, 01:45 AM	#6
manning1 Lives for gear Join Date: May 2004 Location: canada Posts: 3,186	i wont be moving to 64 bit OS any time soon. i find it amusing that some folks feel they have to have a 64 bit OS. its just an OS...focus on the things that matter. input sig chain and convertors etc etc. __________________ i'm just a dumb computer engr (ret'd)...."quantum computing is the future" running a native software studio daw...Powertracks and Reaper on amd. my little songs www.motagator.com/bmanning (saving up for pristine ADA convertors i cant afford...lol)

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

21st February 2006, 06:26 AM	#2
digitaldrummer Gear nut Join Date: Jan 2006 Location: Texas Posts: 93	32-bit on ia64 is in emulation. 32-bit on x64 (or AMD64, or EM64T...) is native (not emulation), however, you don't necessarily get the true benefits an x64 app would get (such as the linear memory model). You may realize better performance if you run multiple instances of 32-bit apps and have lots of RAM (i.e., way more that 4GB)... or maybe not. the sticky point for many is that 32-bit drivers (kernel mode) don't work on x64 and must be recompiled to work. Mike

22nd February 2006, 04:22 PM	#4
neilwilkes Gear maniac Join Date: Sep 2005 Location: London, England Posts: 166	There are other, more serious implications too. According to Joe Bryant of Universal Audio, the following also applies. Win64 supports two application modes: 32-bit (for compatability), and 64-bit. If an app is compiled to run in 64-bit mode, it can't load 32-bit plugins or add-ons. Also, since there's no x87 FPU in 64-bit mode, all the floating point code must be reworked to run on the vector units. So for example, if a plugin has optimized assembly code (like most good native plugs), these have to be completely rewritten to work in 64-bit mode on the new floating point hardware! Some plugins may already have been written to use the vector units (like some synths and impulse 'verbs), so these would port more easily assuming the vector code is the only low-level assembly code. As appealing as 64-bit mode is, the sonic benefits simply aren't there. In fact, the internal precision of the vector units is lower than the x87 FPU! The vector units can process 32- and 64-bit floats, but their internal resolution is fixed at the same precision. The x87 FPU on the other hand, always retains 80- or 160-bit internal prescion, and only drops the precision when results are saved to memory. Also, when 64-bit precision is used in the vector unit, performance is cut in half, so intensive 64-bit float code will be slower than 32-bit code. The bottom line is that because of the availability of this more efficient, but lower resolution 32-bit float mode in Win64, some plugin vendors may opt to drop precision when supporting 64-bit application mode, and sound quality will be lower than what's currently available in the current 32-bit mode. More can sometimes be less!