/3GB switch thread

[The Guru]

All questions answered here. I'd like to hear from those who've had issues with the switch whether they be boot issues or GUI display issues. Please enter all of your specs. :cool:

[Animus]

I use the switch and all works as expected. Mind you if plugins don't have large memory addressing they will ignore the switch and you are in the same boat as before.

[dcwave]

Use it with no issues

[Andrew J]

My machine used to have issues with /3GB, so I don't use it. Can't be more specific because it's a couple of years ago now!

AMD4400X2/A8N-SLI Deluxe/3GB Corsair TWINX
Seagate 80GB-160GB-320GB/GV-NX66T128VP/2x17"LCD

-Andrew

[kdm]

Nuendo works better here with than without in terms of memory handling. Nuendo would become sluggish when approaching 1.2G free, but I can run down to 600-700M free without problems.

The downside is that Spectrasonics products (RMX and Omnisphere) seem to have issues when the 1.2G free line is reached. Other VSTi's are fine.

Anyone know if LaaTiDo/setting up LAA for VSTi's would be of benefit?

[TAFKAT]

The downside is that Spectrasonics products (RMX and Omnisphere) seem to have issues when the 1.2G free line is reached. Other VSTi's are fine.

Hey Dedric,

One idea with the plugs that don't like running in the higher address space, where possible is to load them first so that they will be running in the lower memory address space. I am not sure whether that addressing assignment will be maintained when reloading the project , but maybe worth a try..

[psvennevig]

Hey Dedric,

One idea with the plugs that don't like running in the higher address space, where possible is to load them first so that they will be running in the lower memory address space. I am not sure whether that addressing assignment will be maintained when reloading the project , but maybe worth a try..

Will sadly not work. The whole memory situation in XP was crippled with SP2.
/3GB never had the power it once had.

I believe its better, and if you have the drivers, to run a 64 bit OS with 32 bit versions of Nuendo and plugs.
This way you get 4GB native memory space for Nuendo and plugins.
ReWired instruments and plugins all get their own 4GB memory space (if you have the RAM of course).

Maybe start a thread on how to really tune Vista x64 to run well with audio? :-)

P

[kdm]

Hey Vin - Pal is right. I tried running Stylus first in the list, but it seems to cause other problems with Nuendo, which is one reason I've maintained for a while that Nuendo has memory management issues (I've actually had Stylus report low memory when it was the first VSTi, with nothing load yet... lol).

Pal - I have been contemplating trying running everything in Vista 64, but I am guessing at least half of the sofware I would need wouldn't work, and doesn't that exclude the use of Quicktime completely?

Seems there are no simple solutions, and probably won't be for a while (I doubt we'll ever see QT 64 bit for Windows, or at least not before 2010...)

[TAFKAT]

Will sadly not work. The whole memory situation in XP was crippled with SP2.
/3GB never had the power it once had.

I believe its better, and if you have the drivers, to run a 64 bit OS with 32 bit versions of Nuendo and plugs.P

Hey Pal,

I hear you Bro, but x64 is not an option for all unfortunately due to hardware limitations, Midex anyone.. , and I have heard of some x86 plugs still havimng problems in the upper memory address spaces.. :-(


Maybe start a thread on how to really tune Vista x64 to run well with audio? :-)

You mean un-install it and install XP x64 instead... LOL

Sorry Mate, couldn't help it.. :-)

I am diving right into Vista optimisation as we speak, and not just the usual trim and tuck with settings and services, I am looking at a stripped back installation using VLite. Vista SP1 actually performs quite well on my dev systems that I have it installed on, I still can't see the benefit of Vista 32, and unless my hand is forced end of Jan, I'll be running with XPSP3 for 32 bit.

BTW: There are reports of another extension of the OEM life of XPSP3, so I think Microsoft are more than well aware that their is still life in it.

Peace

[TAFKAT]

Hey Vin - Pal is right. I tried running Stylus first in the list, but it seems to cause other problems with Nuendo, which is one reason I've maintained for a while that Nuendo has memory management issues (I've actually had Stylus report low memory when it was the first VSTi, with nothing load yet... lol)

Cool,

I was just thinking out loud... :-)

Stylus eh.., I'll be sure to keep a closer eye on that.


... and doesn't that exclude the use of Quicktime completely?

No, 32 Bit Quicktime works fine..., I have set up clients rigs with XPx64, Cubendo x86, Quicktime x86, Decklink.., its only Cubendo x64 Public Beta that you will have an issue with in regards to QT.. :-)

Peace

[psvennevig]

Yep to all (tired of quoting...)

Of course there is problems and obstacles going the x64 way. My point was only that it solves the memory issues.

And yes, Cubendo may have some small RAM issues. But I think that is very small. I think it is something they know very well at SB.
However, since every version of Cubendo uses more RAM, newer plugins use more RAM etc, the 32 bit limit is very close these days.

x64 will work when Microsoft drops 32bit, then Apple will release x64 QT at once, they have to for their iTunes :-)

Actually I think they way Apple is doing it by slowly transferring their users into a native 64 bit world is the way to do it.
It takes longer, but it doesn't render all old hardware obsolete in 4 hours.
Microsoft did the right in making a TRUE x64 bit OS from day one. But they do it wrong by not pushing it for what it is worth.

P

[TAFKAT]

Microsoft did the right in making a TRUE x64 bit OS from day one. But they do it wrong by not pushing it for what it is worth.

P

If only they hadn't been strong armed by AMD into accepting x86-64 on its first draft, we could easily have had a native 64 bit O.S, without needing to have required a complete rewrite of all of the drivers at the kernel level.. :-(

Imagine where we could have been now if that wasn't the case..

More in depth detail Here (http://emulators.com/docs/nx03_10fixes.htm)

Throw on the propeller cap first tho... LOL

[Bman]

For what it's worth I had mixed success with the 3GB switch, but overall the benefits far outweighed the negatives.

The problems were two-fold. First, a couple of plugins that I bought specifically for a project (Kong Audio VSTs) become a little more buggy than usual, particularly on program changes causing crashes. Far more problematic was my discovery that using the timewarp tool in the arrange window resulted in large cpu bursts that would briefly seize up SX3 (1 to 10 sec) when switching between windows (ie Project and Tempo) as soon as I used the time warp tool. Workflow ceased. If I rebooted everything was fine, that is until I used the time warp tool and then back came massive transient cpu spikes that would freeze things for a period of 1 to 10 seconds. Pretty annoying particularly when doing film work as I do. However, after much fiddling I discovered that by selecting and using timewarp in the key editor instead of the arrange window I didn't get this problem, so I had a workaround.

Overall though, being able to use the extra RAM has been a real boon, particularly for us film guys that use heaps of RAM with the larger orchestra libs.

Brett

[messianic]

Here's a link I thought might help:

http://support.microsoft.com/default.aspx/kb/929605