|
|
|
10-03-2020, 11:47 AM
|
#1
|
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
v6.14+dev1003 - October 3 2020
v6.14+dev1003 - October 3 2020
- * Includes branch: separate process VST/VST3 scanning
- * Includes feature branch: per-chain PDC mode and overhaul/optimization
- * Includes feature branch: media explorer and metadata improvements
- * Includes feature branch: razor editing
- + Control Surfaces: run MCU/01X peak meters when stopped [Twitter]
- + VST3: improve compatibility with plug-ins that fail during initialize()
- + VST: if a plug-in hangs during scanning, allow terminating via button
- + VST: use separate process when scanning plug-ins, fixes various TLS/FLS issues and improves startup stability when scanning large numbers of plug-ins
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
Last edited by vitalker; 10-04-2020 at 02:19 AM.
|
|
|
10-03-2020, 11:48 AM
|
#2
|
Human being with feelings
Join Date: Oct 2010
Location: Charleston, SC
Posts: 12,769
|
VST: if a plug-in hangs during scanning, allow terminating via button
Great idea!
|
|
|
10-03-2020, 11:51 AM
|
#3
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,749
|
Quote:
Originally Posted by vitalker
- * Includes branch: separate process VST/VST3 scanning
* Includes feature branch: per-chain PDC mode and overhaul/optimization
* Includes feature branch: media explorer and metadata improvements
* Includes feature branch: razor editing
|
We added a new whatsnew line category that confuses the changelog formatting script, sorry!
|
|
|
10-03-2020, 11:58 AM
|
#4
|
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Quote:
Originally Posted by schwa
We added a new whatsnew line category that confuses the changelog formatting script, sorry!
|
That's okay, I can change it.
|
|
|
10-03-2020, 12:22 PM
|
#5
|
Human being with feelings
Join Date: May 2018
Location: Moscow, Russia
Posts: 612
|
Quote:
Originally Posted by vitalker
Includes feature branch: per-chain PDC mode and overhaul/optimization
|
This is probably difficult to explain clearly and concisely, but I would like a little more detail
|
|
|
10-03-2020, 12:23 PM
|
#6
|
Human being with feelings
Join Date: Apr 2016
Location: ASU`ogacihC
Posts: 3,913
|
PDC values shown in Performance Meter are still not the same as what the fx chain is showing when PDC is set to 'classic 1.0-6.0' mode'.
Last edited by Edgemeal; 10-03-2020 at 12:32 PM.
|
|
|
10-03-2020, 12:42 PM
|
#7
|
Human being with feelings
Join Date: May 2018
Location: Moscow, Russia
Posts: 612
|
It seems found
Last edited by Yanick; 10-03-2020 at 12:57 PM.
|
|
|
10-03-2020, 03:11 PM
|
#8
|
Human being with feelings
Join Date: Jun 2017
Posts: 24
|
Love the tool! Just a small bug.
I love how the razor edit tool works. Such an amazing addition!
There was a bug I found however that occurs after selection across a track and its envelopes. It happens when a track has automation clips ending right before the razor edit selection starts. Duplicating the razor edit area results in a tiny little remnant of the end of the automation item that was outside the area. The process is illustrated in the gif here: https://imgur.com/2C4ITnQ
The "Move envelopes with media items and razor edits" switch does not affect this in any way.
What happens that shouldn't?
There are remnants of automation items that were outside of the razor edit selection that duplicate with it.
Intended result?
There is no automation clips outside the razor edit are that are duplicated.
Love the new addition very much though!
|
|
|
10-03-2020, 03:35 PM
|
#9
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,096
|
Being able to see at a glance which branches are included is nice, thanks.
|
|
|
10-03-2020, 03:40 PM
|
#10
|
Human being with feelings
Join Date: Jan 2008
Location: Vancouver, BC
Posts: 3,793
|
Quote:
Originally Posted by vitalker
v6.14+dev1003 - October 3 2020
- Includes branch: separate process VST/VST3 scanning
- + VST3: improve compatibility with plug-ins that fail during initialize()
- + VST: if a plug-in hangs during scanning, allow terminating via button
- + VST: use separate process when scanning plug-ins, fixes various TLS/FLS issues and improves startup stability when scanning large numbers of plug-ins
|
This seems like a great idea.
Related to that, I often have projects that crash on startup and it would be helpful to have more information as to which plugin is responsible.
The project loading window says "Project: loading effect: VSTx plugin name". The words 'project' and 'effect' seem superfluous and something like: "Loading: VSTx plugin name (track)" would be more helpful if we need to open a project in recovery mode to remove a problem plugin.
I also wonder about a recovery option which loads all plugins as a dedicated process. That way problem projects could be loaded as completely as possible while making it easy to know which plugins crashed.
__________________
FRs: v5 Media Explorer Requests, Global Quantization, Session View
Win10 Pro 64-bit, Reaper 6(x64), AMD 3950x, Aorus X570 Master, 64GB DDR4 3600, PowerColor Red Devil 5700XT, EVO 970 2TB, 10TB HD, Define R6
Last edited by PitchSlap; 10-03-2020 at 04:38 PM.
|
|
|
10-03-2020, 05:20 PM
|
#11
|
Human being with feelings
Join Date: Apr 2013
Location: France
Posts: 9,875
|
Quote:
We added a new whatsnew line category that confuses the changelog formatting script, sorry!
|
Corrected. It should be more flexible now.
Also added links to twitter status.
|
|
|
10-04-2020, 12:02 AM
|
#12
|
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,687
|
Quote:
Originally Posted by vitalker
v6.14+dev1003 - October 3 2020
- + VST: if a plug-in hangs during scanning, allow terminating via button
|
As this might be a related issue:
In my setup Kontakt is prone to hang, either when loading the project or what unmuting or muting the track it is loaded in.
This seems to be related to stopping the track activity when muting (which I definitively need in this (live setup) project).
It heavily seems to depend on the Version of Kontakt used. (Of course I corresponded with NI on this issue multiple times)
I can elaborate on this issue, if you want me to.
Maybe the devs might want to take a look at this on the fly ...
-Michael
Last edited by mschnell; 10-04-2020 at 05:23 AM.
|
|
|
10-04-2020, 03:13 AM
|
#13
|
Moderator
Join Date: Aug 2007
Location: Italy
Posts: 4,326
|
Quote:
Originally Posted by PitchSlap
This seems like a great idea.
I also wonder about a recovery option which loads all plugins as a dedicated process. That way problem projects could be loaded as completely as possible while making it easy to know which plugins crashed.
|
I'd like to join the bandwagon by reminding my recovery option FR: now, all plugins in recovery mode are loaded offlined, and that's fine. But... then there's no way to know which plugins were actually offline and which ones have been set offline due to recovery mode.
It would be great to have a different offline mode for plugins that are such because of recovery to distinguish the ones that were offlined even in the project opened normally.
Thanks,
Mario
|
|
|
10-04-2020, 04:25 AM
|
#14
|
Human being with feelings
Join Date: Mar 2007
Posts: 3,978
|
Yes, what mabian wrote ^^^^^^^ makes great sense.
In my projects I have plugins in offline state lot of time so they do not eat up memory, you know, until I am in need to really use them.
After finishing the project, they can be removed if not used, but while in progress it can bring a hard times when analyzing which plugs were already offline in project and which were "offlined" by recovery option.
EDIT: mabian, can you post link to that FR, please? I would like to add my +1
EDIT2: OK, I already found your FR thread here:
Recovery mode enhancements requests
Last edited by akademie; 10-04-2020 at 04:40 AM.
|
|
|
10-04-2020, 04:42 AM
|
#15
|
Human being with feelings
Join Date: Aug 2015
Posts: 3,669
|
Quote:
Originally Posted by Night
[ai remnant bug report]
|
hey Night, i'm unable to reproduce that bug with my config.
i wonder if it has to do with snap settings. try disabling "snap razor edits to media items / automation items" in snap preferences? maybe you're grabbing a little something unintentionally
|
|
|
10-04-2020, 04:55 AM
|
#16
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,749
|
Quote:
Originally Posted by Night
Duplicating the razor edit area results in a tiny little remnant of the end of the automation item that was outside the area.
|
Could you share a simple project that demonstrates this behavior please? It may depend on a specific tempo or other project settings.
|
|
|
10-04-2020, 05:34 AM
|
#17
|
Human being with feelings
Join Date: Dec 2009
Location: United Kingdom
Posts: 668
|
Just wanted to offer my experience with Reaper loading times and VST scanning.
On my desktop, Reaper starts in 4.230 seconds.
VST folder metrics: 225424 files, 16843 folders, of which 4164 are *.dll;*.vst3
This is subsequent runs so most probably there is a lot cached in memory. File allocation table for sure. Will post new benchmark once I get to restart the machine.
The machine is: windows 10 x64, Intel i9-9900T on Z370, 64GiB RAM, Sabrent RocketNVMe 4.0 SSD.
|
|
|
10-04-2020, 05:49 AM
|
#18
|
Moderator
Join Date: Aug 2007
Location: Italy
Posts: 4,326
|
Quote:
Originally Posted by akademie
Yes, what mabian wrote ^^^^^^^ makes great sense.
In my projects I have plugins in offline state lot of time so they do not eat up memory, you know, until I am in need to really use them.
After finishing the project, they can be removed if not used, but while in progress it can bring a hard times when analyzing which plugs were already offline in project and which were "offlined" by recovery option.
EDIT: mabian, can you post link to that FR, please? I would like to add my +1
EDIT2: OK, I already found your FR thread here:
Recovery mode enhancements requests
|
Yes thanks, glad to see it's not only me to wish it was there
- Mario
|
|
|
10-04-2020, 06:22 AM
|
#19
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,294
|
wasn't this fixed before?
please improve the visual to give more correct information regarding what's inside the midi item.
Thanks
|
|
|
10-04-2020, 10:07 AM
|
#20
|
Human being with feelings
Join Date: Oct 2013
Location: Argentina
Posts: 1,303
|
Hi devs!
I know that Linux is not officially supported, but this is serious. I'm working with Linux Mint on a project with approx. 30 instances of Synth1 loaded with Wine and bridged with Yabridge, which is working just fine here. Up to dev0925, the project was rock-solid in terms of stability. As soon as I tried dev1003, it crashed badly, and then on a subsequent try, Reaper did some crazy thing on startup, firing up another Reaper instance and freezing while initializing. It looks pretty bad for a Wine user, I think.
Please, I hope you can take this into account. I try not to bother with Linux things outside of its dedicated thread, but this seems rather fearsome for my taste. Needless to say, I can pm whatever you need to test it.
Thanks so much in advance!
|
|
|
10-04-2020, 01:42 PM
|
#21
|
Human being with feelings
Join Date: Jun 2017
Posts: 24
|
Quote:
Originally Posted by schwa
Could you share a simple project that demonstrates this behavior please? It may depend on a specific tempo or other project settings.
|
Weirdly enough I can't seem to replicate it outside of the project either! However, attached is the project in which I experienced the bug. I stripped out a bunch to suit the upload limit and focus on the main part where it happens. Start the razor edit selection from bar 9 to 13 across the 808 track and the envelope tracks and then duplicate to see the effect.
|
|
|
10-04-2020, 02:14 PM
|
#22
|
Human being with feelings
Join Date: Aug 2015
Posts: 3,669
|
looks like your AI are looping right there at the end, and the loop point is right on the grid line. i was able to get rid of the ghost splits by REing blank space and using it to truncate the existing AI.
"over the line, smokey."
OT, but REAPER should pad probably pre-project timespace with "negative time" so that zooming to edit cursor doesn't de-center when contents are close to project start. i had to drag Night's AI to way later in the project so that i could licecap zooming in on it properly.
Last edited by mccrabney; 10-04-2020 at 02:48 PM.
|
|
|
10-04-2020, 02:38 PM
|
#23
|
Human being with feelings
Join Date: Aug 2015
Posts: 3,669
|
those ghostly envelope points definitely come back somewhat unpredictably, though - if you make an AI that goes from 100% to 0% and loop it, and then zoom way in, you can see the end point at 0 spike back up to 100% as it attempts to make a smooth loop. the result is a point that exists in the grid line, but also doesn't. when it does, it gets picked up by RE. when it doesn't, it doesn't.
in my workflow, i have forgone looping AI. if i want the AI to repeat i just duplicate it adjacent to itself, and utilize the "default edge transition time" param in Preferences.
Last edited by mccrabney; 10-04-2020 at 02:49 PM.
|
|
|
10-04-2020, 09:43 PM
|
#24
|
Human being with feelings
Join Date: Dec 2015
Posts: 2,100
|
RE: Embedded FX GUI
--------------------
There are backgrounds for the other Embedded FX elements, but there isn't one for the actual GUI for the FX.
tcp_fxembed_header_bg_h
tcp_fxembed_header_bg_v
tcp_fxembed_header_float
tcp_fxembed_header_minimize
While this can look OK in in some themes, the inabilty to at least create a stylized border around the embedded area can really clash with the rest of the theme.
apologies if this is the wrong thread.
I wasn't sure where to put it.
::
|
|
|
10-05-2020, 12:29 AM
|
#25
|
Human being with feelings
Join Date: Jun 2017
Posts: 24
|
Quote:
Originally Posted by mccrabney
those ghostly envelope points definitely come back somewhat unpredictably, though - if you make an AI that goes from 100% to 0% and loop it, and then zoom way in, you can see the end point at 0 spike back up to 100% as it attempts to make a smooth loop. the result is a point that exists in the grid line, but also doesn't. when it does, it gets picked up by RE. when it doesn't, it doesn't.
in my workflow, i have forgone looping AI. if i want the AI to repeat i just duplicate it adjacent to itself, and utilize the "default edge transition time" param in Preferences.
|
Interesting that that's what causes it! Not sure if it is still a bug seeing as I'm pretty sure automation items are looping by default but thankyou for the hack in the meantime.
|
|
|
10-05-2020, 12:35 AM
|
#26
|
Human being with feelings
Join Date: Jul 2009
Posts: 1,231
|
"+ VST3: improve compatibility with plug-ins that fail during initialize()"
Thanks for this, working well so far!
|
|
|
10-05-2020, 02:41 AM
|
#27
|
Human being with feelings
Join Date: Jun 2010
Location: Berlin
Posts: 563
|
The latencies reported in the FX Chain window don't correspond with the latencies from the Performance Meter:
Both chains are in "Per-chain compensation" mode.
|
|
|
10-05-2020, 04:36 AM
|
#28
|
Human being with feelings
Join Date: Aug 2015
Posts: 3,669
|
Quote:
Originally Posted by Night
Not sure if it is still a bug seeing as I'm pretty sure automation items are looping by default
|
it is and they are - now, unless schwa beats us to the punch, the trick is figuring out how to make those schrodinger's points appear reliably so that we have a better report.
you found a valuable bug!
|
|
|
10-05-2020, 07:10 AM
|
#29
|
Human being with feelings
Join Date: May 2011
Location: Colombes
Posts: 749
|
Quote:
Originally Posted by vitalker
v6.14+dev1003 - October 3 2020[*]+ VST3: improve compatibility with plug-ins that fail during initialize()[*]+ VST: if a plug-in hangs during scanning, allow terminating via button[*]+ VST: use separate process when scanning plug-ins, fixes various TLS/FLS issues and improves startup stability when scanning large numbers of plug-ins
|
Hi,
i've had to rescan my waves plugins today and most of VST3 versions were not recognized during Reaper loading with error messages that i had to close ("terminate" button) on each waveshell.
I went back to v6.14 and all was fine again
|
|
|
10-05-2020, 07:24 AM
|
#30
|
Human being with feelings
Join Date: Dec 2010
Posts: 3,826
|
Quote:
media explorer and metadata improvements
|
Any hints on what you want tested here, I couldn't find anything different to test ?
For reference, issues I noticed that still remain.
Text and controls either not rendered properly or cut off if the media browser is at its smallest width in vertical dock.
Adding media explorer actions to non media explorer toolbars just adds a random non media explorer action.
Any chance we can try a few more Media explorer toolbars in that branch?
In this gif you will see....
1 No media item selected - Not rendered correctly
2 Start on bar checkbox - Not rendering correctly (Plenty of room to stack above or under autoplay at smallest width docked)
3 BPM display - Not rendered correctly (Renders when sample is not previewing, but doesn't render when sample is previewing, does wonky stuff at different dock widths)
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
Last edited by Win Conway; 10-05-2020 at 07:36 AM.
|
|
|
10-05-2020, 07:44 AM
|
#31
|
Human being with feelings
Join Date: Dec 2010
Posts: 3,826
|
Insert in to sampler on new track is broken.
Reuse active sampler is broken.
See gif.
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
|
|
|
10-05-2020, 07:51 AM
|
#32
|
Human being with feelings
Join Date: Dec 2010
Posts: 3,826
|
The 'Key' metadata tag has no real usage in Reaper, BPM sets BPM and works with syncing, so has usage, but if you set the Key tag it doesn't really do anything, if it autoset the root key in reasampler that would be a workflow boon, especially for people expecting to set a root note and not some random number (Anti RS5K nerdgasm parameter guesswork police)
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
|
|
|
10-05-2020, 08:27 AM
|
#33
|
Human being with feelings
Join Date: Mar 2011
Location: London
Posts: 1,211
|
Quote:
Originally Posted by Win Conway
The 'Key' metadata tag has no real usage in Reaper, BPM sets BPM and works with syncing, so has usage, but if you set the Key tag it doesn't really do anything, if it autoset the root key in reasampler that would be a workflow boon, especially for people expecting to set a root note and not some random number (Anti RS5K nerdgasm parameter guesswork police)
|
It has a very real usage, it let you know in which key is the file you've selected.
|
|
|
10-05-2020, 09:00 AM
|
#34
|
Human being with feelings
Join Date: Dec 2010
Posts: 3,826
|
Quote:
Originally Posted by swiiscompos
It has a very real usage, it let you know in which key is the file you've selected.
|
Which is generally in the file name
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
|
|
|
10-05-2020, 11:00 AM
|
#35
|
Human being with feelings
Join Date: Feb 2017
Posts: 4,812
|
Quote:
Originally Posted by Reflected
wasn't this fixed before?
please improve the visual to give more correct information regarding what's inside the midi item.
Thanks
|
Yes please
__________________
🙏🏻
|
|
|
10-05-2020, 08:44 PM
|
#36
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by vitalker
v6.14+dev1003 - October 3 2020[*]+ VST: if a plug-in hangs during scanning, allow terminating via button
|
I'd probably add another 30 more seconds before this window appears. It's not getting along nicely with some of the Arturia VST3's. AnalogLab and Melotron V both fired this. Analog Lab eventually continued after a few more seconds, but the Melotron V just refused to go any further. Don't remember ever having a problem with Melotron V before.
Also, similar deal, but way worse, with the Roland Cloud plugins which take a while to load. Each of them fires the Terminate window. These don't hang entirely; they'll eventually process, but it's just annoying to see the window pop up for a few seconds with every new plugin scan. And you get it for both VST2 and VST3 versions of their plugins so when I say the number of times the window popped up was in the neighborhood of 40, that's not an exaggeration.
I think an extra 20 or 30 seconds added to the time before the window pops up would be ideal. Some plugins, such as those with massive GUI resources and/or stupid cloud activation schemes that need to phone home will trigger the Terminate VST window way too quickly.
Last edited by Funkybot; 10-05-2020 at 08:54 PM.
|
|
|
10-06-2020, 01:36 AM
|
#37
|
Human being with feelings
Join Date: Mar 2011
Location: On my arse in Glasgow, Scotland
Posts: 2,032
|
Different MIDI editor behaviour on second screen
This only started happening on dev1003.
The good news: Gluing a MIDI item with the MIDI editor open on a second screen doesn't hide the editor while the gluing is being done - previously the editor area went blank, which was a bit worrying. The editor also seems a lot more stable, comparatively. A GUI memory improvement, I guess.
The minor bad news: Can't seem to disable the MIDI editor being docked at the bottom of my main screen on first opening a MIDI item in a large project. I have to close the docker to get it on the second screen, which didn't used to happen.
Once a MIDI item has been opened and undocked, subsequent behaviour is as expected, on subsequent project opens too - (though on a new blank project, new MIDI items open undocked).
(edit) And if I glue a midi item with the undocked editor open, it immediately docks, unbidden.
Thanks.
Last edited by bolgwrad; 10-08-2020 at 04:05 AM.
Reason: Just one more thing
|
|
|
10-06-2020, 03:34 AM
|
#38
|
Human being with feelings
Join Date: Dec 2019
Posts: 214
|
Can we get wildcards for fast export, or are they already hidden somewhere?
----------------------------------------------
Last edited by Odys; 10-06-2020 at 04:00 AM.
|
|
|
10-06-2020, 08:59 AM
|
#39
|
Human being with feelings
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
|
Odys
That would be great!
Maybe an option for this to use the normal render window settings would work.
We do have wildcards for a few things but not this as far as I know.
Devs. If you did this. Please consider it also working for arrange page stuff so we can get rid of the "untitled midi" label (unless I missed a place to already do that)?
__________________
subproject FRs click here
note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
|
|
|
10-06-2020, 09:08 AM
|
#40
|
Human being with feelings
Join Date: Dec 2019
Posts: 214
|
Quote:
Originally Posted by musicbynumbers
Devs. If you did this. Please consider it also working for arrange page stuff so we can get rid of the "untitled midi" label (unless I missed a place to already do that)?
|
Its in language pack, removed it few months ago so don't remember exactly what line, annoyed me too
|
|
|
Thread Tools |
|
Display Modes |
Linear 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 12:39 PM.
|