Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Bug Reports

Reply
 
Thread Tools Display Modes
Old 02-07-2020, 03:34 AM   #1
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 10,605
Default Estimated Remaining render time for Render Matrix can be grossly incorrect (FIXED)

Premise
  • 2 Regions(more than 1) , both of some length. Longer with heavier processing makes this easier to spot.
  • Render matrix set to render one of the regions at the master output(or track, that doesn't matter).

Problem
Estimated time to render always shows the time based on the assumption that ALL regions are marked for render.

One hint is the title bar of the render window during the render. It shows "Rendering region 2/2" as an example, even if just one region is marked for render.

It has been this way for years. That makes the estimated time worthless, unless I'm willing to calculate what percentage of the length of all regions the actually marked regions are, and devide by estimated+lapsed tim to get my render time. Gee thanks for stuffing the render window full of useful information/puzzles. I actually calculate the time judging by the realtime factor of the render.
Please, with cherries on top, fix this gosh darn problem or just boot the estimated time indicator out of the render window alltogether.
__________________
Dialogue/FX Editor & Re-Recording Mixer
(Video)Using Latch Preview - Faderport16 CSI
"My ego comes pre-shrunk" - Randy Thom

Last edited by airon; 02-08-2020 at 07:20 AM.
airon is offline   Reply With Quote
Old 02-10-2020, 05:38 AM   #2
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 10,605
Default

This is really easy to verify. I suppose that's why nobody's posting here as they might consider it a waste of time.

So here's a really simple session you can render from. A tone generator, which is why the track is armed, and a stack of ReaXComps to produce some load.

The render is set to Render Matrix.

There are two things to do for the test.

Mark all regions to be rendered in the Render Matrix and execute the render. Take note of the estimated render time. Then mark only one region for render and execute the render.

It'll be the same estimated render time, and that's the bullshit.
Attached Files
File Type: rpp RenderTest.rpp (24.1 KB, 28 views)
__________________
Dialogue/FX Editor & Re-Recording Mixer
(Video)Using Latch Preview - Faderport16 CSI
"My ego comes pre-shrunk" - Randy Thom
airon is offline   Reply With Quote
Old 02-12-2020, 08:35 AM   #3
Thonex
Human being with feelings
 
Join Date: May 2018
Location: Los Angeles
Posts: 1,096
Default

Yeah. There are various scenarios where the estimated render time is totally wrong. I can confirm the matrix bug. That’s been there since I started using Reaper 18 months ago.

Another one is if you are rending tons of tiny edits. The kind where they are so short the render VU meter doesn’t even register them (offline max speed). In many cases it will show a render time of infinite. LOL.
__________________
Cheers,
Andrew K
v6.03+dev0114 - January 14 2020 • Mac 10.12.+ • i7 Quad 2.9GHz • 24GB
Thonex 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 10:11 PM.


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