Page 2 of 2

Posted: Sat Apr 21, 2007 2:53 pm
by Dominik
a little secret:

the RAM button is a placebo
t
he first thing what i did was move all audio to the external SATA II drive connected through PCIe ESata card.

after that was better but not the best, so what i did next:

1. consolidate all clips (into individual audio files)
2. minimise the number of trax - from 17 - 8 (!!!)
3. all clips are 16 bit aiff
4. more RAM - now i have 2 gb
5. hi-q mode disabled in the clips

now it's ok but it's a BIG compromise!
That's probably your hard drive being too slow for this, quite simply. The seek time of the hard drive is the limiting factor here, and notebook hard drives are not very good in that respect. (To verify this, try a USB stick if you have one; you will probably be able to stream a lot more samples at a time off the stick than off the hard drive.

THIS IS A BIG JOKE.


first of all.
i wrote a topic about this....."issue"

http://www.ableton.com/forum/viewtopic.php?t=61998

...before i stumbled a lot of unanswered questions about the RAM confusion.

when you search about RAM problems ,the result shows about 1000's of threads.
in FACT.as more topics are in this forum as more complicated it became.

and i cannot believe that the RAM button is corrupt .
when i'm working with the RAM button my D LED is NOT flashing.
THAT simply means that the hard disc have not so much activity= longer living.
working with RAM is also FASTER when you have a modern motherboard with faster RAM dimms.

THE ABES ARE JUST JOKING.

this is not a little company anymore and don't believe that they are not exactly know what they do= just chicanery.

thanks for the ABES,i have a new motherboard now.....but it was not necessary......after two weeks thinking something is wrong with my computer and working everyday on this "non" existing problem....

a very professional computer expert found out this.

http://www.ableton.com/forum/viewtopic.php?t=60370
On Windows XP, Live can now address 3GB of memory in,
if the /3GB flag is set according to:
http://www.microsoft.com/whdc/system/pl ... AEmem.mspx
HAHHA...

the technician test it...he wrote something miracle in my xp boot .ini.

....a wonder. live 6 loads tons of files in the RAM.and when you put more than 3 gig of files win xp swap the files file out of the hard disc (that's normal!).
no errors anymore.

i was not listening if the files crackles (i test the demo version on another hard drive without speakers),but i guess RAM works with live 6 and this 3 gig mysteries, properly.

this is a topic about clips in RAM, right?
why some people try to change the title to...how fast is your fucking sata?
STAY ON TOPIC.

and....where is

ALEX........?

Posted: Sat Apr 21, 2007 5:39 pm
by Dominik
the RAM button is a placebo
after testing live 6 i recognise a difference btw. live 5 and 6.
live 6 seems to have a better handling of streaming from disc....still waiting for a answer from the headquarters.

Posted: Sun Apr 22, 2007 2:53 pm
by peeddrroo
thanks stefan for the feedback

it looks like it's a HD speed problem: i managed to play 27 audio tracks without a hicup with the files being streamed from a USB external HD.

Posted: Sun Apr 22, 2007 6:17 pm
by Dominik
well,for me the topic is not closed.there are still unanswered questions.

Posted: Mon Apr 23, 2007 9:12 am
by justin
Dominik wrote:well,for me the topic is not closed.there are still unanswered questions.
firstly, can i recommend you communicate less aggressively. i can understand ppl getting frustrated, but common courtesy goes a long way in my book. and i'm sure this would go a long way to getting your question answered... (i'm not quite sure what your unanswered question is?)

i would think knowing how your HD performed would be a reasonable question, considering the thread topic is using the RAM button to prevent glitches when streaming audio from disk... if your disk is fast enough you wont need to use the RAM, which would be best saved for real-time sound processing. effects and instrument plugins also need this RAM to work effeciently, and some of them can eat up a surprising amount of RAM.

j