v6.47+dev0205 - February 5 2022

[sockmonkey72]

v6.47+dev0205 - February 5 2022

• * Includes feature branch: improved peak building
• * Includes feature branch: batch converter improvements
• * Includes feature branch: improved zoomed-in peaks performance
• * Includes feature branch: FX chain oversampling
• * Includes feature branch: render internals simplification/cleanup
• * Includes feature branch: user-defined action overhaul
• * Includes feature branch: media explorer toolbar
• * Includes feature branch: media item fixed lanes
• + VST: fix various UI sizing quirks
• + macOS: fix Metal issue where an occluded window would end up stale on macOS 12
• # Batch converter: fix multiprocessing when FX instances are offline or bypassed
  

This thread is for pre-release features discussion. Use the Feature Requests forum for other requests.

Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

[Edison]

Originally Posted by sockmonkey72

v6.47+dev0205 - February 5 2022

• * Includes feature branch: improved peak building
• * Includes feature branch: batch converter improvements
• * Includes feature branch: improved zoomed-in peaks performance
• * Includes feature branch: FX chain oversampling
• * Includes feature branch: render internals simplification/cleanup
• * Includes feature branch: user-defined action overhaul
• * Includes feature branch: media explorer toolbar
• * Includes feature branch: media item fixed lanes
• + VST: fix various UI sizing quirks
• + macOS: fix Metal issue where an occluded window would end up stale on macOS 12
• # Batch converter: fix multiprocessing when FX instances are offline or bypassed
  

This thread is for pre-release features discussion. Use the Feature Requests forum for other requests.

Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

Hi Devs,

Why 6.47+dev0205 and not 6.46+dev0205?

Best regards

[Juca]

Originally Posted by Edison

Hi Devs,

Why 6.47+dev0205 and not 6.46+dev0205?

Best regards

6.47+Devs before of the final 6.47?
I second the Edison post.

[Justin]

oops typo

[Icchan]

Originally Posted by sockmonkey72

• + VST: fix various UI sizing quirks

Does this fix any issues with GÔN per following thread?
https://forum.cockos.com/showthread.php?t=256986?

[Funkybot]

Originally Posted by sockmonkey72

[*]+ VST: fix various UI sizing quirks

I'm not sure if anything can easily be done about this, but one of the nitpicky things I run into regularly is that when I'm resizing a plugin by dragging the lower-right corner of the GUI, I very frequently end up resizing the border of the floating FX window instead. Sometimes I'm dragging to resize the plugin AND the floating FX window simultaneously. I'm sure the same would apply for the FX Chain window.

Would be nice if Reaper could recognize the plugin was being resized and temporarily prevent the FX window frame resizing beyond the plugin bounds. Or maybe just prevent right corner drags on Reaper's fx window edge because so many plugins resize that way. I'm open to anything that improves that process, but it's a small nitpick.

[Funkybot]

Also, I'm not sure if it's a Reaper thing or a Softube thing (it works in my other DAWs) but if I resize a Softube VST2 plugin (VST3 works fine), save as default, then reopen said VST2 plugin, the size is recalled but there Softube header menu ends up underneath the Reaper plugin menu and there's a blank space at the bottom of the GUI. I have to drag again to get it to reset.

I did report to Softube support also but not sure if it's a Reaper resize quirk or something they're doing. Happens with all the Softube plugins I've tried, as long as it's VST2.

[Meo-Ada Mespotine]

I've made some more tests in regards of metadata output.

It seems like, that the export does only store 4096 bytes per TXXX-frame with ID3 in the media file.
However, the ID3-standard would allow up to 16 Mb for each frame.

I haven't checked yet for other metadata-schemes...

Edit:
Same goes for VORBIS, IXML and APE.

It seems like, GetMediaFileMetadata doesn't read APE-tags. It doesn't return a list of available fields from APE, despite being present in the file.
Have checked with mp3 and wavpack.

[schwa]

Reading APE tags seems to work as expected here, with wavpack files.

Regarding the 4k limit for TXXX tags, how are you adding the metadata?

[Meo-Ada Mespotine]

Ok, this is odd: ape seems to work now.

I have used
A,Filename=reaper.GetSetProjectInfo_String(0, "RENDER_TARGETS", "", false)
to get the to-be-rendered filename in my code, so there might be an issue in that regards.
Will check further on it, but right now, it works...
Strange.



In regards of TXXX in the MP3, I used this code-snippet.
It renders the file with metadata and checks, whether the data stored in TXXX is equal to the original test-data.
The results will be shown in various variables, beginning with A_

-- set to mp3
local A,B=reaper.GetSetProjectInfo_String(0, "RENDER_FORMAT", "bDNwbYAAAAAAAAAAAgAAAP////8EAAAAgAAAAAAAAAA=", true)
local retval

-- create test-metadata, that has only ABCD time and again in it
A_TestMetaData=""
for i=1, 1024*32 do A_TestMetaData=A_TestMetaData.."ABCDABCDABCDABCDABCDABCDABCDABCD" end

-- add metadata to Reaper's metadata-storage
reaper.GetSetProjectInfo_String(0, "RENDER_METADATA", "ID3:TXXX:TUCH|"..A_TestMetaData, true)

-- get current export-file-name
A,Filename=reaper.GetSetProjectInfo_String(0, "RENDER_TARGETS", "", false)

-- render the file
reaper.Main_OnCommand(41824,0)

-- get the TXXX-metadata-frame for TUCH from recently rendered file
PCM_source=reaper.PCM_Source_CreateFromFile(Filename)
Aretval, A_TestMetaData_FromFile = reaper.GetMediaFileMetadata(PCM_source, "ID3:TXXX:TUCH")

-- Check, if original data is equal to the one I got from the file(which it isn't)
A_TestMetaData_FromFile_Same_Or_Not=A_TestMetaData_FromFile==A_TestMetaData

-- the length of the original metadata versus the length of the metadata read from the mp3
A_TestMetadata_Length=A_TestMetaData:len()                           -- 1048576 Bytes
A_TestMetadata_Length_FromFile_Length=A_TestMetaData_FromFile:len()  -- 4095 bytes

The rendered file has only 4k of metadata stored with TXXX.

This resulted in this file: https://mespotin.uber.space/stuf/metadata-test.mp3
When I open it in a text-viewer, the TXXX-metadata is truncated after 4096 bytes.

Edit: Oh, tested on Windows 7...

Edit2:
Ahh, I got the problem with APE, which wasn't a problem with APE at all.

A,Filename=reaper.GetSetProjectInfo_String(0, "RENDER_TARGETS", "", false)

doesn't take into account if a file already exists AND silently increment filenames to avoid overwriting is activated.
So I basically didn't read from the most recently created filename, but rather the first one I created(that had no metadata in it).
I think, RENDER_TARGETS should add the incrementation-number of the filename when this checkbox is activated.

Means:
"metadata-test.wv" when checkbox is off and file already exists
"metadata-test-001.wv" when checkbox is on and file already exists.

[daxliniere]

Importing markers from a CSV seems to have developed a glitch. The last 2 characters in the marker name are repeated.



(P.S. would you reeconsider removing the 800x600 image size for attachments, please? I always have to uplaod them to Stash separately.)


All the best!

[Mercado_Negro]

I've seen this recurrent problem with AU versions of any plug-in:

https://u.pcloud.link/publink/show?c...QttnRKJjM682i7

I have it so all windows appear on center of screen and this works for VST2 and VST3 but when it comes to AU the plugin tends to move to the bottom each time I close and open the UI.

This is on REAPER ARM.

[schwa]

Originally Posted by daxliniere

Importing markers from a CSV seems to have developed a glitch. The last 2 characters in the marker name are repeated.

Fixing, but making sure: that csv was not created by REAPER, right? Or was edited afterwards?

[daxliniere]

Originally Posted by schwa

Fixing, but making sure: that csv was not created by REAPER, right? Or was edited afterwards?

Thanks Schwa. Correct, this was made by Stacktune (project management for audio). It's worked flawlessly for a long time (1+ yrs) and only recently has this issue. (First time it's happened.)


Unrelated: can we get an indication in the MCP when a plugin is in Delta-Solo mode, please? I just got caught scratching my head over why one track sounded like sh¡t. XD
Perhaps FX name text colour becomes yellow? Or we get a yellow dot on the FX name? Or the text flashes between online and offline colours?

All the best,
D.

[schwa]

Originally Posted by daxliniere

Thanks Schwa. Correct, this was made by Stacktune (project management for audio). It's worked flawlessly for a long time (1+ yrs) and only recently has this issue. (First time it's happened.)

It's because of the quotation marks within the marker name fwiw.

[tonalstates]

Originally Posted by daxliniere

can we get a yellow dot on the FX name? Or the text flashes between online and offline colours?
D.

Yeah, that would be nice! +1

[gapalil001]

Originally Posted by Funkybot

Also, I'm not sure if it's a Reaper thing or a Softube thing (it works in my other DAWs) but if I resize a Softube VST2 plugin (VST3 works fine), save as default, then reopen said VST2 plugin, the size is recalled but there Softube header menu ends up underneath the Reaper plugin menu and there's a blank space at the bottom of the GUI. I have to drag again to get it to reset.

I did report to Softube support also but not sure if it's a Reaper resize quirk or something they're doing. Happens with all the Softube plugins I've tried, as long as it's VST2.

the same happens to Arturia plugins. i also have weird square around dry/wet knob everywhwere


[EDITED]
also, all these frames around sliders looks weird too

[ramses]

I've seen the same issue with VST3 softube plugins, on win 11.

[srdmusic]

I have been tested the last few Dev Releases on Windows 11 and I'm experiencing extremely long load times with Native Instruments Kontakt 6.6.1 vst2 and vst3. This is the latest version of Kontakt available.

It does not seem to happen on every instrument mostly orchestral instruments with larger memory foot prints like Cine Samples Strings Core and Cinebrass. Also some older libraries like Project Sam Symphobia.

Reaper eventually loads the sessions but it takes about 10-15mins for a session that normally loads in less than a min.

I have made sure there are no anti virus software install including Windows Defender.

Is it possible there is an incompatibility between Reaper and Kontakt on Windows 11?

[daxliniere]

Originally Posted by gapalil001

the same happens to Arturia plugins.

I'd be fairly certain Softube and Arturia plugins use the same framework.

[ramses]

Originally Posted by srdmusic

I have been tested the last few Dev Releases on Windows 11 and I'm experiencing extremely long load times with Native Instruments Kontakt 6.6.1 vst2 and vst3. This is the latest version of Kontakt available.

It does not seem to happen on every instrument mostly orchestral instruments with larger memory foot prints like Cine Samples Strings Core and Cinebrass. Also some older libraries like Project Sam Symphobia.

Reaper eventually loads the sessions but it takes about 10-15mins for a session that normally loads in less than a min.

I have made sure there are no anti virus software install including Windows Defender.

Is it possible there is an incompatibility between Reaper and Kontakt on Windows 11?

Kontakt 6 works well for me in Win 11. Loading times are fine.

[srdmusic]

Originally Posted by srdmusic

I have been tested the last few Dev Releases on Windows 11 and I'm experiencing extremely long load times with Native Instruments Kontakt 6.6.1 vst2 and vst3.

I figured out the issue. I had disabled windows defender but Microsoft somehow re-enabled it without asking me when I updated to Windows 11.

Defender needs to be disabled or samples need to be exclude from kontakt to load quickly.

[srdmusic]

Originally Posted by ramses

Kontakt 6 works well for me in Win 11. Loading times are fine.

Windows defender has re-enaled itself without asking me.

[ramses]

Originally Posted by srdmusic

I figured out the issue. I had disabled windows defender but Microsoft somehow re-enabled it without asking me when I updated to Windows 11.

Defender needs to be disabled or samples need to be exclude from kontakt to load quickly.

Good to know.

[Joe90]

Ever since this update, melodyne opens with a truncated GUI. Resizing it fixes the problem, but it literally happens every time you open the editor. I run melodyne docked in the FX chain below the arrange view, so it's even more frustrating as I have to undock it every time to resize it. It doesn't only happen when you first open the plugin, it happens every time you reopen it to make an edit.

I'm on PC, Win 10, latest VST3 version of Melodyne. I'm using it as item FX but the same thing happens when I run it as track FX.

I'm assuming it's something to do with this fix - "VST: fix various UI sizing quirks"

The dev version before this doesn't have this issue. I'm hoping it can be fixed - I'm concerned that it looks like it's made it into a release version (Edit - just double checked and I don't think it has - sorry) as I won't be able to update.

If the devs need me to test anything at my end I'm happy do so, just let me know.

Cheers!

[Justin]

Originally Posted by Joe90

Ever since this update, melodyne opens with a truncated GUI. Resizing it fixes the problem, but it literally happens every time you open the editor. I run melodyne docked in the FX chain below the arrange view, so it's even more frustrating as I have to undock it every time to resize it. It doesn't only happen when you first open the plugin, it happens every time you reopen it to make an edit.

I'm on PC, Win 10, latest VST3 version of Melodyne. I'm using it as item FX but the same thing happens when I run it as track FX.

I'm assuming it's something to do with this fix - "VST: fix various UI sizing quirks"

The dev version before this doesn't have this issue. I'm hoping it can be fixed - I'm concerned that it looks like it's made it into a release version (Edit - just double checked and I don't think it has - sorry) as I won't be able to update.

If the devs need me to test anything at my end I'm happy do so, just let me know.

Cheers!

I just tested with melodyne 5.1.003 and couldn't reproduce your issue.

1) What happens if you try to resize the window (does Melodyne resize to fit it, or does it stay the same size)?

2) Is your display at 100% DPI or some other setting? If not 100%, which hidpi awareness mode is REAPER in?

3) Can you post a copy of your reaper.ini so we can test against those settings?

[Joe90]

Cheers Justin.

I've attached a gif to show what happens -

https://stash.reaper.fm/43805/Melo%20Issue.gif

In the first part of the gif I'm opening melodyne as item FX, opening the FX chain and docking it in the bottom half. The GUI corrects itself as soon as I resize the FX chain. I realised I can just drag the boundary to resize it, rather than undocking it, so that's easier at least.

In the second part of the gif I'm loading melodyne as track FX and floating the GUI. You can see the same issue occurs. You can also see the issues occurs every time the plugin is closed and reopened, whether item FX in FX chain or track FX and floating.

Resizing the FX chain/floating window causes the melodyne GUI to correct itself and fill the space correctly.

I am running multimonitor aware V2 (a lot of elements looks blurry and oversized on the 1080 screen otherwise). However I tested with the other modes, and the only one in which I didn't get this issue was 'unaware'.

I'm running one 4K monitor at 200% scaling and one at 1080p set to 100%. This gif was recorded on the 4k monitor as that's my main one, but the issue occurs if melodyne is opened on either monitor.

I just set the 4k monitor to 100% scaling to test, and it didn't help. I will say on lower scaling settings and/or lower resolutions the issue is less obvious, the GUI is not as truncated, but you can still see it 'correcting itself' when you resize the FX chain window, or the floating melodyne window.

My Reaper.ini is attached.

Thanks for checking on this, much appreciated. If there's any other info you need then let me know.

[Justin]

Originally Posted by Joe90

Cheers Justin.

I've attached a gif to show what happens -

https://stash.reaper.fm/43805/Melo%20Issue.gif

In the first part of the gif I'm opening melodyne as item FX, opening the FX chain and docking it in the bottom half. The GUI corrects itself as soon as I resize the FX chain. I realised I can just drag the boundary to resize it, rather than undocking it, so that's easier at least.

In the second part of the gif I'm loading melodyne as track FX and floating the GUI. You can see the same issue occurs. You can also see the issues occurs every time the plugin is closed and reopened, whether item FX in FX chain or track FX and floating.

Resizing the FX chain/floating window causes the melodyne GUI to correct itself and fill the space correctly.

I am running multimonitor aware V2 (a lot of elements looks blurry and oversized on the 1080 screen otherwise). However I tested with the other modes, and the only one in which I didn't get this issue was 'unaware'.

I'm running one 4K monitor at 200% scaling and one at 1080p set to 100%. This gif was recorded on the 4k monitor as that's my main one, but the issue occurs if melodyne is opened on either monitor.

I just set the 4k monitor to 100% scaling to test, and it didn't help. I will say on lower scaling settings and/or lower resolutions the issue is less obvious, the GUI is not as truncated, but you can still see it 'correcting itself' when you resize the FX chain window, or the floating melodyne window.

My Reaper.ini is attached.

Thanks for checking on this, much appreciated. If there's any other info you need then let me know.

Thanks, I think I have a workaround for this on the next build!

[Joe90]

Originally Posted by Justin

Thanks, I think I have a workaround for this on the next build!

Amazing. Great to hear.