memory
Date | 2017-03-11 18:52 |
From | Menno Knevel |
Subject | memory |
I am using Blue, but i think this is more a Csound thing. I have this instrument: flooper and diskin2 both load in 4 samples into memory, as i notice when i look at the Memory and Swap History of my Linux Mint system with 4G of memory. I was using 4 rather big files with flooper/diskin2 and 30 notes to play the files at different speeds, skipping some samples etc.. With every note the same 4 files are read back in, and after a few seconds i am out of memory and my system is trying to use the swap disk. At one point the swap is full - end of story. I'd like to understand why Csound is not just loading the 4 samples just once and use the notes to read those samples? Is there a more memory economic way possible? -- View this message in context: http://csound.1045644.n5.nabble.com/memory-tp5755014.html Sent from the Csound - General mailing list archive at Nabble.com. Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here |
Date | 2017-03-11 19:22 |
From | Michael Gogins |
Subject | Re: memory |
Could you please enter an issue in GitHub? Best, Mike On Mar 12, 2017 5:52 AM, "Menno Knevel" <magknevel@gmail.com> wrote: I am using Blue, but i think this is more a Csound thing. |
Date | 2017-03-11 20:24 |
From | Victor Lazzarini |
Subject | Re: memory |
Flooper (by design) loads all samples into memory, and does not share it. If you use flooper2 instead, you’ll see a difference. It just reads from the shared function table, with little extra memory use. Diskin2 does not load much into memory, it reads from disk as required. ======================== Prof. Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy, Maynooth University, Maynooth, Co Kildare, Ireland Tel: 00 353 7086936 Fax: 00 353 1 7086952 > On 11 Mar 2017, at 18:52, Menno Knevel |
Date | 2017-03-12 12:50 |
From | Menno Knevel |
Subject | Re: memory |
Good to know, thanks! this week i will do a test with flooper, flooper2 and diskin2, using 30 notes with the same 4 soundfiles, and monitor the memory usage. I will report back so the developers can decide if all is according to expectations. -- View this message in context: http://csound.1045644.n5.nabble.com/memory-tp5755014p5755025.html Sent from the Csound - General mailing list archive at Nabble.com. Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here |
Date | 2017-03-12 13:39 |
From | Victor Lazzarini |
Subject | Re: memory |
flooper will have a high memory usage, that’s a fact and it is what it is. Not designed for the type of thing you are trying to do. ======================== Prof. Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy, Maynooth University, Maynooth, Co Kildare, Ireland Tel: 00 353 7086936 Fax: 00 353 1 7086952 > On 12 Mar 2017, at 12:50, Menno Knevel |
Date | 2017-03-19 13:21 |
From | Menno Knevel |
Subject | Re: memory |
This issue has been solved and was entirely my fault. I had the loading of the (big) samples inside the local instrument. So for every note the same samples were loaded in again and again for every new note. Until i ran out of memory and the swap file kicked in... Loading samples in the Global Orchestra solved the memory problem as the samples are loaded in only once. It works nicely now. -- View this message in context: http://csound.1045644.n5.nabble.com/memory-tp5755014p5755158.html Sent from the Csound - General mailing list archive at Nabble.com. Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here |