 |
|
|
01-24-2021, 05:55 AM
|
#1
|
Human being with feelings
Join Date: Apr 2019
Posts: 258
|
too many cuts makes reaper slow
If I work on a track with too many cuts (and I mean lot of cuts, think like every beat etc for 30 tracks etc) Reaper really slows down and playback create glitches... am I doing something wrong here?
|
|
|
01-24-2021, 12:52 PM
|
#2
|
Human being with feelings
Join Date: Apr 2020
Location: Leipzig
Posts: 2,255
|
How many of them are there? 30? 3000? 3000000?
The thing is, that the more items you have, the more Reaper has to shuffle memory around. This is basically like, if you have one big piece of paper on your desktop. You can move it around very easily.
Now cut it into 30.000 pieces and try to move them around. It'll take a lot of time.
There are some things you can try to improve:
1) restart Reaper, as memory could become defragmented over time, so reopening the project could lead to better organisation of the memory. This could make things faster a little.
2) restart computer, as sometimes all programs currently running defragment the computer's memory to an extend, that everything becomes slower
3) use subprojects/stems for project-tracks, of which you already finished cuts. Render them out, and replace the tracks with the rendered one, so reduce the amount of individual items in the track.
For instance: if track one holds the drumline and you are finished editing it, render it out and replace the items on track 1 with the rendered out version of it.
It's probably a good idea to save the project under a new name, so you still have access to the drumtrack with all edits, in case you need to work on them a little more.
You can also try to glue the items, also to reduce the number of items used in your project.
There are probably more tips possible, but for that, we would need to know more about the project.
Do you use computing-intensive plugins/instruments? Which ones?
Is your computer fast enough? How fast is it?
Is the harddrive/SSD from which you load audio-files(if you use something else than MIDI) fast enough?
etc etc
|
|
|
01-27-2021, 07:11 AM
|
#3
|
Human being with feelings
Join Date: Apr 2019
Posts: 258
|
I believe it was due to the fact that I used fill up gaps and it created lot of tracks for each track - it made a mess! Plus I had some heavy plugin,
The combination of these two was too much rightly so
Love reaper!
|
|
|
01-27-2021, 07:44 AM
|
#4
|
Human being with feelings
Join Date: Jul 2007
Posts: 460
|
If you actually hear crackles, increase media pre-buffer size. But it's very very rare that this is happening.
If Reaper takes too long to pre-buffer media (press play - a few seconds pass - playback starts), get a faster SSD where you're reading the media files from.
Reaper handles huge sessions with millions of cuts exceptionally well, so whichever of the 2 mentioned above might be your problem, there is a solution :-)
|
|
|
02-01-2021, 10:04 PM
|
#5
|
Human being with feelings
Join Date: Apr 2019
Posts: 258
|
Quote:
Originally Posted by fuseburn
If you actually hear crackles, increase media pre-buffer size. But it's very very rare that this is happening.
If Reaper takes too long to pre-buffer media (press play - a few seconds pass - playback starts), get a faster SSD where you're reading the media files from.
Reaper handles huge sessions with millions of cuts exceptionally well, so whichever of the 2 mentioned above might be your problem, there is a solution :-)
|
my buffer is high enough (1024 0r 2048) so it can't be that. I realised that because I chopped lot of parts and used "fill gaps" function, it created sometimes hundereds overlapped media item on each track, and the project had already lot of tracks.
I would need a function like only play one audio file per track, or delete overlapped items...
|
|
|
Thread Tools |
|
Display Modes |
Hybrid Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 02:01 PM.
|