Old 03-13-2017, 01:10 PM   #1
Arnar
Human being with feelings
 
Arnar's Avatar
 
Join Date: Jan 2007
Location: Smokie Bay.
Posts: 796
Default Memory Issue - MIDI.

I am editing MIDI files , I import say 90 .mid files as native Reaper midi format. When I start cutting them up , editing and have maybe reached 180 midi files it takes about 10-13 gig in ram and Reaper gets very slow.

I am only using Geist as kick , and Sylenth as a synth, very basic midi editing session and yet its suuuper slow.
Feels like this should be a breeze and not a problem.

At 8 gig , if i open the action list it just hangs.
Also it will eventually crash and takes forever to load.


Any ideas ?
__________________
In Music We Trust.
http://soundcloud.com/hazar
http://soundcloud.com/ifthenrun

Last edited by Arnar; 03-13-2017 at 01:19 PM.
Arnar is offline   Reply With Quote
Old 03-13-2017, 01:24 PM   #2
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,814
Default

Feel free to post the .RPP here, or email it to support at cockos.
schwa is offline   Reply With Quote
Old 03-13-2017, 01:46 PM   #3
Arnar
Human being with feelings
 
Arnar's Avatar
 
Join Date: Jan 2007
Location: Smokie Bay.
Posts: 796
Default

The .rpp's are from 740mb to 2 gig ?
Which is weird , just a bunch of tiny midi files ?
__________________
In Music We Trust.
http://soundcloud.com/hazar
http://soundcloud.com/ifthenrun
Arnar is offline   Reply With Quote
Old 03-13-2017, 01:51 PM   #4
Arnar
Human being with feelings
 
Arnar's Avatar
 
Join Date: Jan 2007
Location: Smokie Bay.
Posts: 796
Default

Its very simple to reproduce.

Import ca 90 one measure midi files.
Implode all files into one - (90 takes) ,duplicate to next measure and switch takes.

Keep doing this until you reach around take 30 and its starts to eat up memory ...60 and I am at almost 4 gig.
At take 30 it starts to take a few seconds to duplicate and switch takes.

At this point , if I search action list, it hangs.
And when it crashes , its stuck in task manager at 7 gig.
Needs a restart.
__________________
In Music We Trust.
http://soundcloud.com/hazar
http://soundcloud.com/ifthenrun

Last edited by Arnar; 03-13-2017 at 05:27 PM.
Arnar is offline   Reply With Quote
Old 03-13-2017, 02:53 PM   #5
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 24,798
Default

Quote:
Originally Posted by Arnar View Post
The .rpp's are from 740mb to 2 gig ?
Which is weird , just a bunch of tiny midi files ?
Pack them to RAR, they should compress much better since RPPs are just text mostly.
EvilDragon is offline   Reply With Quote
Old 03-13-2017, 04:53 PM   #6
Arnar
Human being with feelings
 
Arnar's Avatar
 
Join Date: Jan 2007
Location: Smokie Bay.
Posts: 796
Default

OK, will do
__________________
In Music We Trust.
http://soundcloud.com/hazar
http://soundcloud.com/ifthenrun
Arnar is offline   Reply With Quote
Old 03-13-2017, 05:17 PM   #7
Arnar
Human being with feelings
 
Arnar's Avatar
 
Join Date: Jan 2007
Location: Smokie Bay.
Posts: 796
Default

Here's a dropbox link 34mb.
This one sits at almost 12 gig in memory.
https://dl.dropboxusercontent.com/u/...xtract%203.rar
__________________
In Music We Trust.
http://soundcloud.com/hazar
http://soundcloud.com/ifthenrun
Arnar is offline   Reply With Quote
Old 03-14-2017, 06:49 AM   #8
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,814
Default

Thanks for posting the project. The RPP contains about 159 million lines so it's difficult to even analyze. I can say that it contains 8660 separate MIDI takes, many of which are copies of the same MIDI source data which itself contains about 18000 MIDI events. 8660*18000 = about 155 million.

18000 MIDI events for a song-length MIDI file is on the high side but not unreasonable. Having 8660 instances of the full-length MIDI data is probably unnecessary. You could reduce this various ways. If you are making many copies of a long MIDI file in order to use different, small parts of it in different places, you could use pooled copies (so that only one copy of the full-length item is stored in the RPP), or you could glue the smaller pieces (so that each small piece does not store a full copy of the full-length item). If you absolutely need thousands of copies of a full-length MIDI file, you should import the MIDI as file reference rather than in-project items.

Last edited by schwa; 03-14-2017 at 07:01 AM.
schwa is offline   Reply With Quote
Old 03-14-2017, 08:29 AM   #9
Arnar
Human being with feelings
 
Arnar's Avatar
 
Join Date: Jan 2007
Location: Smokie Bay.
Posts: 796
Default

155 million ! Thats nothing :P

Ok, will try some things to make this easier.
__________________
In Music We Trust.
http://soundcloud.com/hazar
http://soundcloud.com/ifthenrun
Arnar is offline   Reply With Quote
Old 03-14-2017, 09:15 AM   #10
ivansc
Human being with feelings
 
Join Date: Aug 2007
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
Default

Quote:
Originally Posted by Arnar View Post
I am editing MIDI files , I import say 90 .mid files as native Reaper midi format. When I start cutting them up , editing and have maybe reached 180 midi files it takes about 10-13 gig in ram and Reaper gets very slow.

I am only using Geist as kick , and Sylenth as a synth, very basic midi editing session and yet its suuuper slow.
Feels like this should be a breeze and not a problem.

At 8 gig , if i open the action list it just hangs.
Also it will eventually crash and takes forever to load.


Any ideas ?
Just being nosey here, but have you done this successfully in any other DAW?
__________________
Ici on parles Franglais
ivansc is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 12:05 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.