-
Hey David. Just type "BR" in angle-brackets to get carriage returns. No magic on Mac, I just do that all the time. Hopefully it will be fixed one day...
But more importantly, hopefully we'll figure out what's up with the disappearing memory. I don't have anywhere near as many licenses as you, just winds I and II Standard, Brass I Standard, Chamber Strings Extended, and Solo Strings Extended.
J.
-
...I don't suppose, David, that you've done an actual crash-test on how much memory is really available (or used)? That is, have you ever just loaded samples until it crashes? Just to see whether that 800 MB is _really_ gone, or if it's just the Task Manager messing up. Might be worth a try. I could try it on my machine, but I can't do it just this minute...
J.
-
The only thing I have looked at was to make sure that the VI was showing the same amount of available RAM as the Task Manager. It shows the same. I'll try to load presets until the system crashes, sound like fun. Will have to wait until I get home from work tonight. Will keep the Forum posted - pun intended :-) P.S. - trying to use the BR bracket suggestion but it not working - is it these {BR} or these [BR] ? neither work
-
test < > /< /> ...
david, i have not enough 64bit machines currently to check if this effect shows up in another configuration, but generally it doesn't make any sense to me ... is there a default fxp being loaded with the startup or something related to ASIO drivers or effects (samplitude involved)?
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
Hi Christian,
I agree. It makes no sense and I have never seen this before on WinXP Pro 32-bit.
Its very easy to test. Just boot-up WinXP 64 and don't launch anything just look at
how much RAM is being Committed in the Processes tab. Its usually around 200-300MB.
Then launch a blank VI stand-alone or VE stand-alone. Keep an eye on the Committed RAM
amount.
You should see the VI or VE RAM usage go up to around 100mb (I can't rememeber) but
the Committed RAM goes up much farther. Mine hits 1200mb!
I'm NOT using Samplitude, its not even installed.
Not loading a default fxp either, no effects. My interface is a FireFace800 by RME.
It would be fantastic if I could get some suggestions to try.
Thanks for your help!
David
-
mac pro. I've even tested my VI to the point to where I had no loaded patches, matrixes, or presets, and I had about 300mb left on a 3gb ram machine
-
This is my previous post that no one really responded to................ Maybe this will help!!............ Alright. First of all, I would like to say that I 'm not upset and I ABSOLUTELY LOVE VSL!!!! Ok, now that I got that out the way. I'm a new customer so I may be a lacking the expert knowledge. Ok, I've invested in a Mac Pro 2.66 Quad. I have 3gb so far. I am only running the Chamber Strings Collection. I am using Prottols as my Host. (ever since the new rtas). BUT I JUST CAN'T SEEM TO GET CONTROL OF FLOATING RAM. NOBODY RESPONDED TO MY FIRST BLOG SO I AM TYPING IN FULL TEXT DARNIT!!!!! I even tested it. My ram peaked at 2064mb. I loaded a simple matrix. Then I cleared it. When I cleared it, I never went back up to 2000mb. It peaked at 1664mb. Then I loaded a few patches and a matrix. After that I cleared it off. So when I checked my ram it showed 0 samples used and about 1400mb peak. I keep repeating the same steps with different combinations of patches and matrix files until I ended up with 300 mb WITH ABSOLUTELY ZERO SAMPLES LOADED. What am I doing wrong? eventually I couldn't even run my Protools because it had no space to work. Nothing could work in that matter. Even when I closed out VI and reopened it, the ram was still at the same spot. The only way that I could get my ram back was to restart my CPU. now thats not right is it? Am I not erasing the samples out of Ram correctly? Do I need to reload VSL. Whats the dealeo? Is it a Mac configuration issue? SOMEBODY PLEASE WRITE BACK THIS TIME!!!!!!!!!!!!!!!!!!! HELP! HELP!
-
I haven't experienced the behavior described in this thread but I have noticed an odd behavior that might be related and, if so, might help to nail down the source of the problem.
When I re-load all samples after optimizing, I very often wind up with MORE available RAM than before. My swap file is set to 0, so it's not that the OS is just dumping stuff to the swap file. The VI definitely does some strange things as far as memory goes...
This happens using the VI as a plug-in in Cubase 4 under WinXP 32-bit with the /3GB switch.
rgames
-
Hey cm,
Any luck looking into this RAM issue?
I know VSL is busy with a million other things but it would be nice to hear if this problem is being looked into.
Herb has a WinXP64 machine. It takes 2 minutes to confirm this issue on a computer. Maybe he could check his system?
In the meantime I have tested my RAM and complete system for defective conponents. Everything is running fine.
Not sure why almost a GB of RAM is disappearing on launching of VI or VE but its to big of an amount to overlook.
Oh, I also tried a suggestion by another member here to use the Learn/Optimize/Reset function but it did not have any impact.
Thanks for you help!
David
-
[quote=DM33]Hi DG,
Processor(s)
Number of processors 1
Number of cores 2 per processor
Number of threads 2 (max 2) per processor
Name Intel Core 2 Duo E6700
Code Name Conroe
Specification Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz
Package Socket 775 LGA
Family/Model/Stepping 6.F.6
Extended Family/Model 6.F
Core Stepping B2
Technology 65 nm
Core Speed 1600.0 MHz
Multiplier x Bus speed 6.0 x 266.7 MHz
Rated Bus speed 1066.7 MHz
Stock frequency 2666 MHz
Instruction sets MMX, SSE, SSE2, SSE3, SSSE3, EM64T
L1 Data cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 4096 KBytes, 16-way set associative, 64-byte line sizeChipset & Memory
Northbridge Intel i975X rev. A0
Southbridge Intel 82801GB (ICH7) rev. 01
Graphic Interface PCI-Express
PCI-E Link Width x16
PCI-E Max Link Width x16
Memory Type DDR2
Memory Size 8192 MBytes
Memory Frequency 333.3 MHz (4:5)
CAS# Latency (tCL) 5.0 clocks
RAS# to CAS# (tRDC) 5 clocks
RAS# Precharge (tRP) 5 clocks
Cycle Time (tRAS) 15 clocks
Bank Cycle Time (tRC) 21 clocksSystem
System Manufacturer
System Name
System S/N
Mainboard Vendor Intel Corporation
Mainboard Model D975XBX2
BIOS Vendor Intel Corp.
BIOS Version BX97520J.86A.2674.2007.0315.1546
BIOS Date 03/15/2007Memory SPD
Module 1 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston
Module 2 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston
Module 3 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston
Module 4 DDR2, PC2-5300 (333 MHz), 2048 MBytes, KingstonSoftware
Windows Version Microsoft Windows XP x64 Professional Service Pack 2 (Build 3790)
DirectX Version 9.0cDG
-
david it seems i managed to screw up the machine during some tests and am finally in the boat with you :-/
unfortunately i noticed this too late and can't reproduce the step where this issue happened now.
there is no time left for playing around this week so i have to ask you for some more patience ...
christian
edit: you won't beleive it .... it seems the issue is related to corrupt sample data (a sector from a harddisk fails or similar)
solution: open directory manager, remove all content, add some content
(you should notice the memory is increasing to 800 MB only opening the DM without having any VE opened before)
reboot - open VE ... back at 300 something ... (thx to george for the clever idea)
after adding the corrupt data the effect returns ... isn't that weired?
now we just need to find out what affects the taskmanager to show this amount of used memory even without any process listed ...
and remember: only a CRAY can run an endless loop in just three seconds.
Forum Statistics
196,068 users have contributed to 43,014 threads and 258,388 posts.
In the past 24 hours, we have 2 new thread(s), 16 new post(s) and 153 new user(s).