v5.981+dev0801 - August 1 2019

[Edgemeal]

v5.981+dev0801 - August 1 2019
+ ARA: disable undo integration (should improve stability)
+ Jump to time: allow jumping to times relative to track/item by using tXiY prefix
+ Jump to time: mX and rX can be followed by whitespace and a time offset
+ Marquee: fix drawing glitches after interrupted marquee selection
+ Media items: actions to force (persistent) offline of item media, inactive take media
+ Modal windows: remember window positions (configurable option in preferences/general/advanced to tweak behavior)
+ Navigator: improve behavior when continuous scrolling is enabled
+ Preferences: add option in disk settings to periodically close excess open files
+ Tracks: complete overhaul of track/mixer panels for performance
+ macOS: improve memory use meter
# Fix possible crash when removing tracks with inactive sends [p=2163652]
# Media items: support displaying source time in H:M:S:F format

Full changelog / Latest pre-releases

[EvilDragon]

Originally Posted by Edgemeal

v5.981+dev0801 - August 1 2019+ Modal windows: remember window positions (configurable option in preferences/general/advanced to tweak behavior)

Thank you!

However, seems like ReaScript's GetUserInputs is still not following this preference.


MIDI editor Note Properties doesn't seem to follow "center on mouse cursor" preference at all, while "Event Properties" follows it just fine. Media Item Properties dialog doesn't follow "center on mouse cursor" preference either. Humanize just centers on screen, but not cursor. Display Quantization dialog doesn't follow any preference.

Snap/Grid Settings and Lock Settings don't seem to follow either of the centering preferences (doesn't matter if called through action list, keyboard shortcut, or right-click on toolbar button - even if I move their positions it is not stored and just goes back to top left-ish of the left (main) screen over here). Crossfade Editor only centers on screen, doesn't follow center on mouse cursor preference...

Transient Detection Sensitivity dialog just remembers last manually set position, it doesn't seem to follow any preference.

Parameter modulation/Link dialog saves position, but every separate instance open in the top left corner regardless of the modal dialogs preference, which is (extremely!) annoying.

Seems like many of the dialogs are not yet fully following the preference that is set. Can this please be remedied, so that we get consistent behavior according to the pref we chose, for all (and I mean ALL) dialogs?

[bFooz]

I am experiencing flashing of the whole UI when changing track selection. Win7 64bit

[Edgemeal]

reaper.JS_Window_GetScrollInfo no longer works, all return values are zero.
The UI now flickers when adding, selecting/unselcting tracks.
When bottom Docker (Performance) is first shown (or REAPER becomes the active app) it isn't getting painted correctly, image attached in post #7.

Win7 x64 / AMD Radeon HD6670

[EvilDragon]

For the record, there's no flickeering when doing track add/remove/select here. Either from TCP or from MCP.

[Edgemeal]

Originally Posted by EvilDragon

For the record, there's no flickeering when doing track add/remove/select here. Either from TCP or from MCP.

Maybe GPU related? Using an old AMD Radeon here, flickering is pretty bad and docker (Performance) painting is messed up too.


Win7 x64 / AMD Radeon HD6670

[Justin]

Originally Posted by Edgemeal

reaper.JS_Window_GetScrollInfo no longer works, all return values are zero.

What window are you passing it? That window is probably not valid.

[Edgemeal]

Originally Posted by Justin

What window are you passing it? That window is probably not valid.

Ya your right, SORRY!
I was getting handle to the horiz scrollbar in the Mixer, but seems you changed the Mixer window layout.

[Edgemeal]

Originally Posted by Edgemeal

The UI now flickers when adding, selecting/unselcting tracks.
When bottom Docker (Performance) is first shown (or REAPER becomes the active app) it isn't getting painted correctly, image attached in post #7.

Update: If the Mixer is open (floating or docked) the flickering goes away and Performance window redraws correctly when docked too.


Win7 x64 / AMD Radeon HD6670

[_Stevie_]

Confirmed, on closed mixer the track selection is flickering and super laggy.

[Justin]

Originally Posted by Edgemeal

Update: If the Mixer is open (floating or docked) the flickering goes away and Performance window redraws correctly when docked too.


Win7 x64 / AMD Radeon HD6670

Can you give me your reaper.ini with the exact configuration that is flickery? Also make a licecap so I can see? Thanks

[Justin]

Originally Posted by EvilDragon

However, seems like ReaScript's GetUserInputs is still not following this preference.

Fixing

MIDI editor Note Properties / Media Item Properties dialog / Display Quantization dialog / Transient Detection Sensitivity /

These aren't modal.

Parameter modulation/Link dialog saves position, but every separate instance open in the top left corner regardless of the modal dialogs preference, which is (extremely!) annoying.

Yeah better defaults would probably be nice, maybe we can make it use that preference as a hint of where you'd like things.

[EvilDragon]

Originally Posted by Justin

These aren't modal.

Would still make sense to have those dialogs follow the preference, though? Or is there a complication between modal vs non-modal?

I mean, none of those dialogs are dockable or anything that would prevent them to show up according to that preference...

Originally Posted by Justin

Yeah better defaults would probably be nice, maybe we can make it use that preference as a hint of where you'd like things.

That'd be nice.

[Justin]

Originally Posted by EvilDragon

Would still make sense to have those dialogs follow the preference, though? Or is there a complication between modal vs non-modal?

I mean, none of those dialogs are dockable or anything that would prevent them to show up according to that preference...

It depends (some of them have existing logic to manage their position), I'll take a look and see if I can update some of them.

For now I'll accept three categories of feedback on this:

1) Modal windows that do not follow the pref
2) Modeless windows that do not remember their positions
3) Modeless windows that remember their positions but have poor default positioning that you'd like to follow that pref

[EvilDragon]

Originally Posted by Justin

It depends (some of them have existing logic to manage their position), I'll take a look and see if I can update some of them.

For now I'll accept three categories of feedback on this:

1) Modal windows that do not follow the pref
2) Modeless windows that do not remember their positions
3) Modeless windows that remember their positions but have poor default positioning that you'd like to follow that pref

Thanks - and fair points regarding feedback. I'll try to open all the possible dialogs, but might need help from other people here - everyone please chime in!


(By the way, how come Note Properties is modeless but Event Propeties isn't? Why this inconsistency?)

[xpander]

Originally Posted by Justin

For now I'll accept three categories of feedback on this:

1) Modal windows that do not follow the pref
2) Modeless windows that do not remember their positions
3) Modeless windows that remember their positions but have poor default positioning that you'd like to follow that pref

Added to what ED found earlier, I found these from the MIDI Editor. Only tested with the default Last window position.

1) Modal windows that do not follow the pref
Piano roll timebase - Timebase help
Notation - Edit Lyric

2) Modeless windows that do not remember their positions
Humanize

[lucor]

Originally Posted by Edgemeal

+ Tracks: complete overhaul of track/mixer panels for performance

Holy %&$#, thank you thank you thank you! Couldn't test for long, but large projects on my 4k screen have become EXTREMELY smooth with this latest update!
Only issue I found so far is this graphical bug when opening up a project. After clicking a track, everything is fine.
https://imgur.com/a/uehOccR

If you can apply whatever magic you worked here to the midi editor as well, Cubase will finally be forever dead to me.

[Klangfarben]

Originally Posted by Edgemeal

# Media items: support displaying source time in H:M:S:F format

Thanks so much for this addition. Unfortunately it doesn't actually work. It still displays start of item as 0:00:00:00 instead of the actual source time.

Currently in a 24 frame rate project. Will test other frame rates as well.

[_Stevie_]

Originally Posted by Klangfarben

Thanks so much for this addition. Unfortunately it doesn't actually work. It still displays start of item as 0:00:00:00 instead of the actual source time.

Currently in a 24 frame rate project. Will test other frame rates as well.

Yes, confirmed here.

[schwa]

Originally Posted by Klangfarben

Thanks so much for this addition. Unfortunately it doesn't actually work. It still displays start of item as 0:00:00:00 instead of the actual source time.

Currently in a 24 frame rate project. Will test other frame rates as well.

Seems to work here, what are you seeing specifically?

[Klangfarben]

Originally Posted by schwa

Seems to work here, what are you seeing specifically?

1) Set project offset to something other than 0:00:00:00 - say 1:01:50:00
2) Create midi item starting at bar 1
3) Show item ruler and select source H:M:S:F
4) Item will show source as 0:00:00:00 not 1:01:50:00

Expected behavior would be item ruler would start at 1:01:50:00

The same thing happens when selecting time.

In the previous pres, selecting source - Time did work correctly. In this version neither time or H:M:S:F is working for source.

[schwa]

Originally Posted by Klangfarben

1) Set project offset to something other than 0:00:00:00 - say 1:01:50:00
2) Create midi item starting at bar 1
3) Show item ruler and select source H:M:S:F
4) Item will show source as 0:00:00:00 not 1:01:50:00

Expected behavior would be item ruler would start at 1:01:50:00

The same thing happens when selecting time.

In the previous pres, selecting source - Time did work correctly. In this version neither time or H:M:S:F is working for source.

Was what you're asking for ever supported? "Source time" means time in the source media. The start of the source media is always zero and is not affected by project start offset.

[Klangfarben]

Originally Posted by schwa

Was what you're asking for ever supported?

It was previously supported yes. Setting it to source time did respect Project Offset and would display current source time.

Originally Posted by schwa

"Source time" means time in the source media. The start of the source media is always zero and is not affected by project start offset.

Obviously I have a different understanding of source time than you but source time to me is where the item starts in reference to the project. If I recorded an item at 1:05:20:00, the source time of that item would be 1:05:20:00 not 0:00:00:00. Same for minutes-seconds.

If I set something to source preferred position, it wouldn't move the item to zero. So I wouldn't expect source time to always be zero either. I would expect it to refer to the items current position. Otherwise, item time and source time are pretty much the same thing, yes? (other than if an item is looped).

[_Stevie_]

It *could* be that we missunderstood the initial functionality.
I couldn't spot any diffence between item and source time.
So I assumed that source must be referring to the project time offset
Because in a previous pre it did exactly that

Anyway, if it was possible to add that, it would be marvelous!

Btw, the track/mixer improvements, are amazing. Thanks for that!

[mschnell]

Originally Posted by Edgemeal

+ Tracks: complete overhaul of track/mixer panels for performance

Unbelievable ! That was fast !!!
-Michael

[WyattRice]

Originally Posted by Edgemeal

v5.981+dev0801 - August 1 2019
+ Jump to time: allow jumping to times relative to track/item by using tXiY prefix
+ Jump to time: mX and rX can be followed by whitespace and a time offset

Nitpick.
In the jump window, the text for j's look like i's, and in some they are j's

e.g
"iump to minutes:seconds.fraction"
"iump to measurs.beats.fraction
"iump to hours:minutes:seconds:frames"

below that the j's look like j's on these next three lines.

"prefix with + or - for relative jump"

then the last two lines of text, goes back to i's
mN or m'name iump to marker by number or name"

[bwsd]

Originally Posted by Edgemeal

v5.981+dev0801 - August 1 2019
+ Tracks: complete overhaul of track/mixer panels for performance
Full changelog / Latest pre-releases

It is cool. I open around 8000 tracs without lag interface.
Thank You.

But now do not work mouse modifiers track control panel.

Ooops, I am not a first :-)

[Tale]

+ Tracks: complete overhaul of track/mixer panels for performance

FWIW: I can easily create 32768 empty tracks now (on Win10)!

[EvilDragon]

I can open around 8k tracks but RT CPU goes over 100% then... I wonder which settings affect this. What's your CPU, Tale?

[Tale]

Originally Posted by EvilDragon

I can open around 8k tracks but RT CPU goes over 100% then... I wonder which settings affect this. What's your CPU, Tale?

Intel Core i7-7700 3.60/4.20 GHz.

Note that with a 64 samples buffer at 44.1 kHz my RT CPU is also >100% (nearly 300% in fact). But with a larger buffer of e.g. 1024 samples, the RT CPU is only ~15%. Not bad for >8000 tracks!

[EvilDragon]

Ah yes, 128 samples buffer, i7-6700K at 4.5 GHz all cores here. Of course lower buffer size would demand more RT CPU.

I also noticed threading aggressiveness also takes up more CPU. Putting it on relaxed or automatic shaved off some more RT CPU.

[srdmusic]

Originally Posted by Edgemeal

v5.981+dev0801 - August 1 2019
+ Tracks: complete overhaul of track/mixer panels for performance

Thank you Devs for tackling this issue. I'm sure it quite difficult to streamline a DAW that is already already as efficient as Reaper is.

I have to run some further testing on an actual writing session to confirm real world number but so far there does seem to be an improvement of CPU consumption on larger track count session.

I did a little A/B test to see where the track limits can get to in each Dev version. Something interesting is still happening once track counts get higher than 1000 tracks.

I'd like to explore why Total CPU and RT CPU consumption seems to go up exponentially after 1000 tracks. Anything between 1-1000 tracks and my CPU is about 2%. At 2000 tracks it goes up to about 30% and at 2500 tracks My CPU hovers around 50%. This seems very odd to me since the tracks are not record enabled, there our no outputs set and the tracks are all muted. The tracks are not selected and there are no items on the track so there shouldn't be any anticipatory fx processing going on.

Is there a preference in Reaper that might be causing these sorts of numbers?

[lexaproductions]

Since this build, my custom configuration is not working. Crashes upon starting the program, It works on my standard configuration that I use daily. But I have a heavily custom version that I've used live for the last 3 years and This new build won't start with it. I don't know what's wrong. Here's the crash log:

Process:               REAPER [17864]
Path:                  /Applications/ReaLiveResources/REAPER64.app/Contents/MacOS/REAPER
Identifier:            com.cockos.reaper
Version:               5.97.111 (5.97.111)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           REAPER [17864]
User ID:               501

Date/Time:             2019-08-12 12:36:01.559 -0400
OS Version:            Mac OS X 10.11.6 (15G31)
Report Version:        11
Anonymous UUID:        48421833-45CE-0A6E-E670-0E640B1D81D1

Sleep/Wake UUID:       442414A8-2B3C-4F64-8251-1FDCF896FF99

Time Awake Since Boot: 360000 seconds
Time Since Wake:       320000 seconds

System Integrity Protection: disabled

Crashed Thread:        0  reaper  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
/Library/Caches/com.apple.xbs/Sources/Metal/Metal-56.6.1/Framework/MTLTexture.m:643: failed assertion `MTLTextureDescriptor has one or more dimensions set that are zero or greater than the maximum allowed size.'
 

Thread 0 Crashed:: reaper  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff97d76f06 __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff9e8f64ec pthread_kill + 90
2   libsystem_c.dylib             	0x00007fff9006f6df abort + 129
3   libsystem_c.dylib             	0x00007fff90036dd8 __assert_rtn + 321
4   com.apple.Metal               	0x00007fff94f9e7ad MTLReportFailure + 600
5   com.apple.Metal               	0x00007fff94f82ab5 -[MTLTextureDescriptorInternal validateWithDevice:] + 606
6   com.nvidia.web.GeForceMTLDriverWeb	0x0000000118501ae3 0x11833c000 + 1858275
7   com.nvidia.web.GeForceMTLDriverWeb	0x0000000118481d4b 0x11833c000 + 1334603
8   com.apple.QuartzCore          	0x00007fff9cae6e56 allocate_drawable_private(unsigned int, unsigned int, id<MTLDevice>, MTLPixelFormat, bool, bool, unsigned int, CGColorSpace*, _CAImageQueue*) + 893
9   com.apple.QuartzCore          	0x00007fff9cae68c8 -[CAMetalLayer nextDrawable] + 1408
10  com.cockos.reaper             	0x000000010fa26927 -[REAPERSwell_hwnd swellDrawMetal:] + 2359
11  com.cockos.reaper             	0x000000010fa2d89a swell_updateAllMetalDirty() + 282
12  com.cockos.reaper             	0x000000010f85f0b8 -[REAPERapp sendEvent:] + 5176
13  com.apple.AppKit              	0x00007fff981efae4 -[NSApplication _doModalLoop:peek:] + 751
14  com.apple.AppKit              	0x00007fff983d06fb __35-[NSApplication runModalForWindow:]_block_invoke + 126
15  com.apple.AppKit              	0x00007fff981ed375 -[NSApplication runModalForWindow:] + 156
16  com.apple.AppKit              	0x00007fff98604ebe -[NSSavePanel runModal] + 627
17  com.cockos.reaper             	0x000000010fa3ae86 BrowseForFiles(char const*, char const*, char const*, bool, char const*) + 662
18  reaper_sws_extension.dylib    	0x000000011f82f6de OpenProjectsFromList(COMMAND_T*) + 110
19  reaper_sws_extension.dylib    	0x000000011f78308b hookCommandProc(int, int) + 731
20  com.cockos.reaper             	0x000000010f55cf8f Main_OnCommandEx2(int, int, ReaProject*) + 111
21  com.cockos.reaper             	0x000000010f55ce97 Main_OnCommand(int, int) + 39
22  com.cockos.reaper             	0x000000010f7fe192 lua_Main_OnCommand(lua_State*) + 66
23  com.cockos.reaper             	0x000000010f84e624 luaD_precall + 2132
24  com.cockos.reaper             	0x000000010f96992e luaV_execute + 1982
25  com.cockos.reaper             	0x000000010f84f026 luaD_callnoyield + 70
26  com.cockos.reaper             	0x000000010f850e1b luaD_rawrunprotected + 107
27  com.cockos.reaper             	0x000000010f850b70 luaD_pcall + 64
28  com.cockos.reaper             	0x000000010fc28bf8 lua_pcallk + 152
29  com.cockos.reaper             	0x000000010fbf6d83 LuaAPI::InterpretScript(char const*, char const*) + 403
30  com.cockos.reaper             	0x000000010fc489bc RunReaScript(char const*, int, KbdSectionInfo*, int, bool, int) + 1548
31  com.cockos.reaper             	0x000000010fb84acf MainProc(HWND__*, unsigned int, unsigned long, long) + 10783

[Justin]

Originally Posted by lexaproductions

Since this build, my custom configuration is not working. Crashes upon starting the program, It works on my standard configuration that I use daily. But I have a heavily custom version that I've used live for the last 3 years and This new build won't start with it. I don't know what's wrong. Here's the crash log:

Process:               REAPER [17864]
Path:                  /Applications/ReaLiveResources/REAPER64.app/Contents/MacOS/REAPER
Identifier:            com.cockos.reaper
Version:               5.97.111 (5.97.111)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           REAPER [17864]
User ID:               501

Date/Time:             2019-08-12 12:36:01.559 -0400
OS Version:            Mac OS X 10.11.6 (15G31)
Report Version:        11
Anonymous UUID:        48421833-45CE-0A6E-E670-0E640B1D81D1

Sleep/Wake UUID:       442414A8-2B3C-4F64-8251-1FDCF896FF99

Time Awake Since Boot: 360000 seconds
Time Since Wake:       320000 seconds

System Integrity Protection: disabled

Crashed Thread:        0  reaper  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
/Library/Caches/com.apple.xbs/Sources/Metal/Metal-56.6.1/Framework/MTLTexture.m:643: failed assertion `MTLTextureDescriptor has one or more dimensions set that are zero or greater than the maximum allowed size.'
 

Thread 0 Crashed:: reaper  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff97d76f06 __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff9e8f64ec pthread_kill + 90
2   libsystem_c.dylib             	0x00007fff9006f6df abort + 129
3   libsystem_c.dylib             	0x00007fff90036dd8 __assert_rtn + 321
4   com.apple.Metal               	0x00007fff94f9e7ad MTLReportFailure + 600
5   com.apple.Metal               	0x00007fff94f82ab5 -[MTLTextureDescriptorInternal validateWithDevice:] + 606
6   com.nvidia.web.GeForceMTLDriverWeb	0x0000000118501ae3 0x11833c000 + 1858275
7   com.nvidia.web.GeForceMTLDriverWeb	0x0000000118481d4b 0x11833c000 + 1334603
8   com.apple.QuartzCore          	0x00007fff9cae6e56 allocate_drawable_private(unsigned int, unsigned int, id<MTLDevice>, MTLPixelFormat, bool, bool, unsigned int, CGColorSpace*, _CAImageQueue*) + 893
9   com.apple.QuartzCore          	0x00007fff9cae68c8 -[CAMetalLayer nextDrawable] + 1408
10  com.cockos.reaper             	0x000000010fa26927 -[REAPERSwell_hwnd swellDrawMetal:] + 2359
11  com.cockos.reaper             	0x000000010fa2d89a swell_updateAllMetalDirty() + 282
12  com.cockos.reaper             	0x000000010f85f0b8 -[REAPERapp sendEvent:] + 5176
13  com.apple.AppKit              	0x00007fff981efae4 -[NSApplication _doModalLoop:peek:] + 751
14  com.apple.AppKit              	0x00007fff983d06fb __35-[NSApplication runModalForWindow:]_block_invoke + 126
15  com.apple.AppKit              	0x00007fff981ed375 -[NSApplication runModalForWindow:] + 156
16  com.apple.AppKit              	0x00007fff98604ebe -[NSSavePanel runModal] + 627
17  com.cockos.reaper             	0x000000010fa3ae86 BrowseForFiles(char const*, char const*, char const*, bool, char const*) + 662
18  reaper_sws_extension.dylib    	0x000000011f82f6de OpenProjectsFromList(COMMAND_T*) + 110
19  reaper_sws_extension.dylib    	0x000000011f78308b hookCommandProc(int, int) + 731
20  com.cockos.reaper             	0x000000010f55cf8f Main_OnCommandEx2(int, int, ReaProject*) + 111
21  com.cockos.reaper             	0x000000010f55ce97 Main_OnCommand(int, int) + 39
22  com.cockos.reaper             	0x000000010f7fe192 lua_Main_OnCommand(lua_State*) + 66
23  com.cockos.reaper             	0x000000010f84e624 luaD_precall + 2132
24  com.cockos.reaper             	0x000000010f96992e luaV_execute + 1982
25  com.cockos.reaper             	0x000000010f84f026 luaD_callnoyield + 70
26  com.cockos.reaper             	0x000000010f850e1b luaD_rawrunprotected + 107
27  com.cockos.reaper             	0x000000010f850b70 luaD_pcall + 64
28  com.cockos.reaper             	0x000000010fc28bf8 lua_pcallk + 152
29  com.cockos.reaper             	0x000000010fbf6d83 LuaAPI::InterpretScript(char const*, char const*) + 403
30  com.cockos.reaper             	0x000000010fc489bc RunReaScript(char const*, int, KbdSectionInfo*, int, bool, int) + 1548
31  com.cockos.reaper             	0x000000010fb84acf MainProc(HWND__*, unsigned int, unsigned long, long) + 10783

Thanks, the next build (coming soon) should fix, hopefully!

[lexaproductions]

Thanks Boss

[Justin]

Originally Posted by lexaproductions

Thanks Boss

There, let me know if this happens in 0812 too.