64 bit D-Day

What statistics do you base that on? Can't say it has been my experience.

Presumably there will come a day when it will no longer be necessary to update OSs.

Presumably both Microsoft and Apple think that day is a long way off.

 

Well that is for sure a detailed technical answer.

Microsoft must love customers like you.

 

lol

 

a good percentage of users actually reported worse performance using 64bit. most never used more than 4G of ram in their audio apps so any benefit from that was negated in the higher processor and resource demands.

i have seen absolutely no benefit in using 64bit over 32 bit for audio in producing audio for 4 - 9 minute songs. if i was doing soundtrack work where the files and samples are considerably larger, i would likely see a benefit. at the same time, i have not noticed, on the mac side, a decrease in performance with OS 10.11 or above. earlier versions of the prior to 10.11, my performance was worse with 64bit, currently, it is the same and i see neither benefit, nor detriment in using 64bit, and the limitations for me are the same, either i can or cannot run certain plug-ins respectively.

IMO, bigger number not always better, let your workflow define your needs. if you have to use 32bit, then use it. if if does not matter, then use 64bit.
if you need to use both, i recommend using live and installing both the 32 and 64 bit versions or cubase 8.5 and rendering the effects tracks or sounds to samples and then using them in the 64 bit only programs. the reality is, you will eventually have to use 64 bit only for newer plug-ins, but that does not mean you cannot find ways to use legacy ones in your mixes.

 

Not sure where you got that info...
You might be undermining how much ram things take these days.
Machine with only 3 instruments takes 1.6GB away, for some reason a single gmail safari tab is using 1.3GB, another youtube tab 500MB... To that add on the OS and many other background stuff... and bye-bye ram and hello slow page file.
Now imagine if i open maschine in Ableton, while watching a tutorial on youtube and do a complicated project ... 4Gb is nothing...

 

I don’t think this has anything to do with an imminent 3.0 release. Both Apple and MS have already started to give developers warnings about dropping 32bit Support at the OS level. NI is just being proactive since all of their software except older stuff like Pro53 already have 64-bit versions of all the software and that has been the case for years. At least since Logic released the 64-bit version of 9.

Apple will drop 32bit Support very soon. MS is already letting developers know that They have theirs eyes set on Win32 and are going to get rid of the 32bit version of Windows 10 altogether.

Welcome to the future.




Sent from my iPhone using Tapatalk

 

i thought high sierra dropped 32 bit mode from apps already...

 

it is 4G per app, so in 32bit mode, live would get 4g ram max, safari is 64 bit so it can grab more than 4g already, the 64bit os can use as much as it needs... in 64 bit mode, it just lets each app grab more than 4g ram, so live could grab 5G ram .... kontakt can be set to grab quite a bit of ram... so if you needed to load a large sample sets in ram and had like 32 tracks, then, yes, you are going to need more than 4G for the audio app hosting it all.. ..but, you can set kontakt to use a ram servers, so that is a way around the 4G limit.. me... i rarely ever do that to that extent or ii use two computers in sync.... so if i run cubase or live on one computer and maschine on another.. 64bit is just a bigger number to me... or if i use rewire on one single computer, each audio app still gets the 4G ram each in 32bit mode... i use 64 bit now because i know that soon those audio apps are going to demand more ram as the standard for minimum required ram increases as more computer have 16G or above.... for now, we still have laptops being sold that max out at 4G ram, so it is time to convert all the projects to handle that and accept 64 bit as the standard, and 32 bit the legacy.

 

Ultimately if you are using 32 bit DLL's in 64 bit app a sandbox needs be written around it and in a lot of cases that's where the reliability fails and performance is reduced (thunking is not a great scenario in DAWs). It's an extra code that isn't needed (and often unreliable). Not only that 32 bit plugins have no been tested in these environments, and old plugins often don't integrate well with new software.

If you ring up tech support for most DAW manufacturers I suspect problems with 32 bit plugins comes very high on the list. Go back in time 5 years or so and visit DAW forums and observe the endless complaints in forums are from people running 32 bit in 64 bit environments.

Lack of resources is the other issue.

Just say no! (Can't believe I'm saying this in 2018).

 

Yeh think I'm going to keep an old school 32 bit environment and have a 64 bit version I can update overtime..Otherwise it's too much downtime which is not what I want ..First world problems eh

 

Well hopefully they have no intention of preventing 32 bit programs running inside their 64 bit OSs.

 

Obviously I don't know if my projects are reasonably typical however, until recently, I did run both 32 and 64 bit versions of Live on my PC.

I never experienced an issue opening a 64 bit created project in 32 bit Live and there was absolutely no performance difference in how it ran.

You have to push it a bit to exceed the 4GB limit, plus many sample based VSTs will stream from disc. When using SSDs, streaming from disc is less of a bottleneck.

I only deleted 32 bit Live from my system to regain disc space as I have reluctantly decided to retire Vanguard, which was my only 32 bit VST.

 

I see, so... a global limit 4GB for all applications only happens if the OS itself is 32bit, if the OS is 64bit and some apps are 32 each app has a 4GB limit. I wouldn't have any peace of mind knowing my ram is capped regardless, then again I'm not really the average user, I use a desktop computer in a laptop age exactly because i want the best performance i can get inside my budget, this includes overclocking my system which is not very common for Audio.
I also see a lot of people using 32bit apps have lots of random issues, probably because of what Cake explained in post 31.

 

No I think Cake is talking about using 32 bit VSTs inside a 64 bit app, in which case you do have to use a wrapper like for example jbridge.

Running 32 bit apps in a 64 bit OS is extremely common and generally trouble free. Think of apps like Acrobat and even Microsoft Office.