Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Pre-Release Discussion

Reply
 
Thread Tools Display Modes
Old 08-08-2022, 08:21 AM   #1
musicbynumbers
Human being with feelings
 
musicbynumbers's Avatar
 
Join Date: Jun 2009
Location: South, UK
Posts: 14,218
Default v6.64+dev0808a - August 8 2022

v6.64+dev0808a - August 8 2022
  • # CLAP: ensure plugin size persists after user resizes parent window and then closes the plugin UI
  • # MIDI: retroactive record threshold is a single note during playback, 2 notes when stopped
  • # MIDI: retroactive record when looped and overdub is enabled will overdub all passes into item
  • # Track group manager: add context menu option to select tracks when selecting group
  • # Track group manager: add context menu, docking support
  • # Track group manager: fix opening window on startup
  • # Track grouping manager: fix enabling/disabling groups on selected rows [p=2584586]

v6.64+dev0808 - August 8 2022
  • * Includes feature branch: track grouping manager dialog
  • * Includes feature branch: .SD2/PCM/RAW file support
  • * Includes feature branch: CLAP plugin support
  • * Includes feature branch: track media/razor edit grouping
  • * Includes feature branch: pan law/function improvements
  • * Includes feature branch: improve experimental silent-track CPU reduction option to include FX tail length
  • * Includes feature branch: media item fixed lanes
  • * Includes feature branch: internal pin management overhaul for future extension
  • + Batch converter: add dropdown to choose how many CPU cores to use
  • + Region/Marker Manager: fix display glitch when resizing
  • + Track grouping: add Track Group Manager dialog
  • + WALTER: fix h variable in tcp.fxembed context [p=2584238]
  • # CLAP: for consistency, send only MIDI events, not CLAP events, to plugins, including note-on/note-off events
  • # CLAP: improve keyboard behavior on win32
  • # CLAP: support sending MIDI sysex to plugins
  • # FX: fix duplicate parameter label in generic UI for some plugins [p=2584487]
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
__________________
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.

Last edited by schwa; 08-08-2022 at 10:59 AM.
musicbynumbers is offline   Reply With Quote
Old 08-08-2022, 08:31 AM   #2
BPBaker
Human being with feelings
 
BPBaker's Avatar
 
Join Date: Oct 2013
Location: Brooklyn, NY
Posts: 209
Default

Quote:
Originally Posted by musicbynumbers View Post
[*]+ Track grouping: add Track Group Manager dialog
Woohoo! Thanks and looking forward to giving this a try!
BPBaker is offline   Reply With Quote
Old 08-08-2022, 08:32 AM   #3
Sexan
Human being with feelings
 
Sexan's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 4,689
Default

Thank you for grouping manager!

Is this supposed to happen?


When one group is selected, clicking enable on it toggles all groups on/off?

EDIT: One addition what I would find useful is when selecting group it selects all tracks in that group. Use case opening envelopes on all tracks in that group

Last edited by Sexan; 08-08-2022 at 08:37 AM.
Sexan is offline   Reply With Quote
Old 08-08-2022, 08:39 AM   #4
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,820
Default

Quote:
Originally Posted by Sexan View Post
When one group is selected, clicking enable on it toggles all groups on/off?
No, that's a bug, when enabling/disabling a selected group it should only affect other selected groups.
schwa is offline   Reply With Quote
Old 08-08-2022, 08:48 AM   #5
Klangfarben
Human being with feelings
 
Join Date: Jul 2016
Location: Los Angeles, CA
Posts: 1,701
Default

Thanks so much for a group manager!

Similar, on Linux, no individual group toggle is working. Clicking on the enabled button is also selecting the group, which then turns everything on/off.



Also, there doesn't seem to be a way to dock the window currently?

Agree with Sexan, if you click on the group name it would be really nice to also select the group tracks.
Klangfarben is offline   Reply With Quote
Old 08-08-2022, 08:56 AM   #6
vitalker
Human being with feelings
 
vitalker's Avatar
 
Join Date: Dec 2012
Posts: 13,334
Default

Quote:
Originally Posted by musicbynumbers View Post
# FX: fix duplicate parameter label in generic UI for some plugins [p=2584487]
While we at FX generic UI, maybe it is possible to implement input boxes for parameters? For now the only way to set values is by mouse/mousewheel.
vitalker is offline   Reply With Quote
Old 08-08-2022, 08:57 AM   #7
Sexan
Human being with feelings
 
Sexan's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 4,689
Default

Yeah docking is not here on W10 either.

There is one more bug:
1. leave open group manager window
2. close reaper
3. start reaper
4. open group manager - it does not open on first try

Sexan is offline   Reply With Quote
Old 08-08-2022, 09:00 AM   #8
sockmonkey72
Human being with feelings
 
sockmonkey72's Avatar
 
Join Date: Sep 2021
Location: Berlin
Posts: 1,962
Default

Quote:
Originally Posted by vitalker View Post
While we at FX generic UI, maybe it is possible to implement input boxes for parameters? For now the only way to set values is by mouse/mousewheel.
+1.001
__________________
ReaPack Repository: right-click and copy index URL
sockmonkey72 is online now   Reply With Quote
Old 08-08-2022, 10:21 AM   #9
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 6,027
Default

The TGM text color seems to use a different font/Walter element than some other dialog boxes. This creates a problem on a dark theme I use in Windows where the TGM text is black on a dark background, versus say the Media Item Properties where the font is white. I think the TGM should use whatever font choices/logic that make the text white on Media Item Properties.

__________________
CSI v3 Wiki

Last edited by Funkybot; 08-23-2022 at 08:35 AM.
Funkybot is online now   Reply With Quote
Old 08-08-2022, 10:58 AM   #10
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,820
Default

Updated build just posted, should fix some of the reported issues.
schwa is offline   Reply With Quote
Old 08-08-2022, 11:50 AM   #11
Sexan
Human being with feelings
 
Sexan's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 4,689
Default

There is some lag when selecting tracks via group manager:

select track outside the the group then click on one group with tracks. It lags about 1-2 seconds

Sexan is offline   Reply With Quote
Old 08-08-2022, 12:02 PM   #12
nofish
Human being with feelings
 
nofish's Avatar
 
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,109
Default

Re: CLAP support

I've just added a new parameter to my plugin in v0.9.4 and there is the same issue as in p=2583166 (which was fixed intermediately) that the parameter isn't displayed in the generic GUI (though exposed as automatable parameter). VST3 version for comparison where it's fine.
Maybe this time it's because the parameter text is a string (rather than number)?

nofish is offline   Reply With Quote
Old 08-08-2022, 12:11 PM   #13
Klangfarben
Human being with feelings
 
Join Date: Jul 2016
Location: Los Angeles, CA
Posts: 1,701
Default

Quote:
Originally Posted by Sexan View Post
There is some lag when selecting tracks via group manager:

select track outside the the group then click on one group with tracks. It lags about 1-2 seconds
I'm not getting this lag on Linux, abeit this GIF is just a test project with minimal track count.

Klangfarben is offline   Reply With Quote
Old 08-08-2022, 12:11 PM   #14
Tale
Human being with feelings
 
Tale's Avatar
 
Join Date: Jul 2008
Location: The Netherlands
Posts: 3,653
Default

Quote:
  • # CLAP: for consistency, send only MIDI events, not CLAP events, to plugins, including note-on/note-off events
I had a quick go with this, removing CLAP Note On/Off from my test plugin, and it seems to be working.
Tale is offline   Reply With Quote
Old 08-08-2022, 12:15 PM   #15
Sexan
Human being with feelings
 
Sexan's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 4,689
Default

Quote:
Originally Posted by Klangfarben View Post
I'm not getting this lag on Linux, abeit this GIF is just a test project with minimal track count.
Happens with minimal track count (in that gif above there are about 15 tracks) but now I tested with 7 tracks also.

BUT when manager is docked then it does not update at all


BTW clicking on same group (and in gifs in previous post)

EDIT: Its not track outside the group, its any track just click on same group again (re-tested now)
Sexan is offline   Reply With Quote
Old 08-08-2022, 12:26 PM   #16
Freiin
Human being with feelings
 
Freiin's Avatar
 
Join Date: May 2020
Posts: 73
Default

[*]# MIDI: retroactive record threshold is a single note during playback, 2 notes when stopped
[*]# MIDI: retroactive record when looped and overdub is enabled will overdub all passes into item

If Reaper is not the best daw out there, then my name is not Gabriel.

Thanks, devs! This is huge!
__________________
Orchestral composer learning more and more.

https://www.youtube.com/BlackDollMurder
Freiin is offline   Reply With Quote
Old 08-08-2022, 12:42 PM   #17
EcBaPr
Human being with feelings
 
Join Date: Aug 2009
Posts: 402
Default

grouping manager looks good.. it would be great if other stuff could eventually be added.. markers would be awesome..
EcBaPr is offline   Reply With Quote
Old 08-08-2022, 01:00 PM   #18
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Posts: 3,672
Default

the quantize dialog is doing something weird in the MIDI editor that it isn't doing in 6.64

licecapped on portable install



1- record a loosely timed MIDI phrase
2- enter the MIDI editor
3- select all notes use the quantize dialog to quantize them to a visibly different grid value. OK out of quantize dialog
4- change your selection to just a few notes
5- open the quantize dialog box again
ISSUE: the unselected, previously quantized MIDI reverts to pre-quantized state.
7- quantize another selection and then hit commit
8- make a new selection and attempt to quantize.
ISSUE: selected content cannot be quantized.
__________________
mccrabney scripts: MIDI edits from the Arrange screen ala jjos/MPC sequencer
|sis - - - anacru| isn't what we performed: pls no extra noteons in loop recording
| - - - - - anacru|sis <==this is what we actually performed.
mccrabney is offline   Reply With Quote
Old 08-08-2022, 01:35 PM   #19
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 24,798
Default

Track group manager doesn't seem to follow theme colors here:

EvilDragon is offline   Reply With Quote
Old 08-08-2022, 01:53 PM   #20
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Posts: 3,672
Default

really digging into retroactive recording here. such a great way to input MIDI.

* in the MIDI editor, the "View: Hide unused and unnamed note rows" does not update to show new retroactively inserted note rows.

* question: when playback is stopped and "input quantize" is ON, retroactively recorded MIDI is quantized on input. since playback is stopped, are we quantizing to a free-running grid (essentially a silent metronome), or one that starts on first note input?
__________________
mccrabney scripts: MIDI edits from the Arrange screen ala jjos/MPC sequencer
|sis - - - anacru| isn't what we performed: pls no extra noteons in loop recording
| - - - - - anacru|sis <==this is what we actually performed.
mccrabney is offline   Reply With Quote
Old 08-08-2022, 01:55 PM   #21
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,745
Default

Quote:
Originally Posted by mccrabney View Post
really digging into retroactive recording here. such a great way to input MIDI.

* in the MIDI editor, the "View: Hide unused and unnamed note rows" does not update to show new retroactively inserted note rows.

* question: when playback is stopped and "input quantize" is ON, retroactively recorded MIDI is quantized on input. since playback is stopped, are we quantizing to a free-running grid (essentially a silent metronome), or one that starts on first note input?
hmm we should disable input quantize for events which occurred while the transport was stopped…
Justin is online now   Reply With Quote
Old 08-08-2022, 02:12 PM   #22
Sexan
Human being with feelings
 
Sexan's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 4,689
Default

I would like to bump two more things with group editing if possible:

1. Removing (alt click) razor removes just one part not whole group razor


2. If fade behavior could be same as current item edges behavior (when fades overlap)

Smaller items fades get influenced much if item edges start at same time, or not at all if edges start at different time.


You can see here one scenario when fade is greater than the item, it is influenced immediately.
And there is another case here https://forum.cockos.com/showpost.ph...8&postcount=16

Thank you for all the hard work (seems V7 to me !
Sexan is offline   Reply With Quote
Old 08-08-2022, 02:33 PM   #23
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Posts: 3,672
Default

Quote:
Originally Posted by Justin
hmm we should disable input quantize for events which occurred while the transport was stopped…
agreed.

Quote:
# MIDI: retroactive record threshold is a single note during playback, 2 notes when stopped
an argument against this: a single note threshold can serve as a step-input. i tried downgrading to 0807 to make a demo gif, but it looks like the threshold is 2 notes while stopped there too, as well.

in the MPC sequencers, users can have OVERDUB on while playback was stopped, and enter notes (with as-played duration) while stepping around the grid. very handy for quick sketches. in REAPER, you could do the same using "Navigate: Move edit cursor left/right by grid" - then clear buffer, tap your intended note, retroactively insert it, and repeat.

if you'd consider changing this to 1 note while stopped for a pre, i'd love to test this
__________________
mccrabney scripts: MIDI edits from the Arrange screen ala jjos/MPC sequencer
|sis - - - anacru| isn't what we performed: pls no extra noteons in loop recording
| - - - - - anacru|sis <==this is what we actually performed.
mccrabney is offline   Reply With Quote
Old 08-08-2022, 03:02 PM   #24
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Posts: 3,672
Default

* while project is playing, single notes held over loop reset are not retroactively inserted. if you play 2 or more notes, they are entered. however, notes held over loop reset do not retrigger at loop beginning ala active record:



i do think that retriggering held notes on loop playback is problematic, but retriggered notes are better than truncation.
__________________
mccrabney scripts: MIDI edits from the Arrange screen ala jjos/MPC sequencer
|sis - - - anacru| isn't what we performed: pls no extra noteons in loop recording
| - - - - - anacru|sis <==this is what we actually performed.
mccrabney is offline   Reply With Quote
Old 08-08-2022, 03:22 PM   #25
Gass n Klang
Human being with feelings
 
Gass n Klang's Avatar
 
Join Date: Nov 2015
Location: Cologne
Posts: 1,640
Default

Quote:
Originally Posted by Sexan View Post
I would like to bump two more things with group editing if possible:
1. Removing (alt click) razor removes just one part not whole group razor
2. If fade behavior could be same as current item edges behavior (when fades overlap)
+1

but thanks one more time again: working with track groups is such a relief. In combination with razor edits it speeds up my editing workflow by 20% at least. There are some aspects where razor edits don't work hand in hand with track edit groups but we are getting there. Thanks again, the time where I don't have a look at pro tools at all has come way closer.
__________________
https://juliusgass.de
Gass n Klang is offline   Reply With Quote
Old 08-08-2022, 03:27 PM   #26
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Posts: 3,672
Default

Quote:
# MIDI: retroactive record overdubs into existing items if in replace/touch-replace modes
could this be extended to retroactive MIDI recorded while playback is stopped? current stopped behavior is that new MIDI items are created in-lane on top of existing items, even in overdub mode.

__________________
mccrabney scripts: MIDI edits from the Arrange screen ala jjos/MPC sequencer
|sis - - - anacru| isn't what we performed: pls no extra noteons in loop recording
| - - - - - anacru|sis <==this is what we actually performed.
mccrabney is offline   Reply With Quote
Old 08-08-2022, 04:20 PM   #27
nofish
Human being with feelings
 
nofish's Avatar
 
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,109
Default

Quote:
Originally Posted by Sexan View Post
1. Removing (alt click) razor removes just one part not whole group razor
I find this functionality (partially removing RE) quite handy actually.
nofish is offline   Reply With Quote
Old 08-08-2022, 05:34 PM   #28
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,820
Default

Quote:
Originally Posted by Sexan View Post
1. Removing (alt click) razor removes just one part not whole group razor
I understand the inconsistency may be bothersome, but the existing behavior is useful, so we're thinking it's probably fine as is.


Quote:
Originally Posted by Sexan View Post
2. If fade behavior could be same as current item edges behavior (when fades overlap)
This is a more bothersome inconsistency, but unfortunately it's been the behavior forever. We may change (fix) this in the +dev builds but it would need to remain in +dev for a long time since it changes existing workflow.
schwa is offline   Reply With Quote
Old 08-09-2022, 12:22 AM   #29
Gass n Klang
Human being with feelings
 
Gass n Klang's Avatar
 
Join Date: Nov 2015
Location: Cologne
Posts: 1,640
Default

Quote:
Originally Posted by schwa View Post
I understand the inconsistency may be bothersome, but the existing behavior is useful, so we're thinking it's probably fine as is.
It's getting especially bothersome if you've got multiple razor areas selected in track edit group mode. Why not make a "remove one razor edit area (ignoring edit group)" mouse modifier instead, so we can have both. Besides that can easily be reached by temporarily deactivating group (alt + g)
__________________
https://juliusgass.de
Gass n Klang is offline   Reply With Quote
Old 08-09-2022, 01:08 AM   #30
mike@overtonedsp
Human being with feelings
 
mike@overtonedsp's Avatar
 
Join Date: Sep 2018
Location: Oxford, England
Posts: 219
Default

#CLAP

@nofish

Quote:
Re: CLAP support

I've just added a new parameter to my plugin in v0.9.4 and there is the same issue as in p=2583166 (which was fixed intermediately) that the parameter isn't displayed in the generic GUI (though exposed as automatable parameter). VST3 version for comparison where it's fine.
Maybe this time it's because the parameter text is a string (rather than number)?
You need to be sure that you implement value_to_text properly (even if this isn't the issue here) because the host will use this to query the plugin, and the plug-in returns a human readable string of the parameter value.

So

parameter.get_value: You always return a double representing the (RAW) parameter value.

parameter.value_to_text: You return a (UTF8) string representing the human readable form of the parameter.

Whether the parameter is 'a string' rather than a number should be irrelevant, because you are responsible for putting it in the correct form the host is asking for. For example I have parameters which are displayed as a number with units, so its just a generic C string representing the text even though internally the raw value is 0.0f to 1.0f and Reaper has no issues with it as far as I can tell

EDIT: Since +dev808a I'm now missing the second to last parameter (or the last displayable e.g. not marked as CLAP_PARAM_IS_HIDDEN parameter) in the generic UI - so something broke between 808 and 808a. Window resizing is now remembered correctly - could this be related to that fix?

Last edited by mike@overtonedsp; 08-09-2022 at 03:19 AM.
mike@overtonedsp is offline   Reply With Quote
Old 08-09-2022, 02:31 AM   #31
Sexan
Human being with feelings
 
Sexan's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 4,689
Default

Quote:
Originally Posted by schwa View Post
I understand the inconsistency may be bothersome, but the existing behavior is useful, so we're thinking it's probably fine as is.


This is a more bothersome inconsistency, but unfortunately it's been the behavior forever. We may change (fix) this in the +dev builds but it would need to remain in +dev for a long time since it changes existing workflow.
Understandable. Regarding fades could it be done as separate modifier so the existing behavior is not disrupted (just thinking out loud since only you know whats actually under the hood)?

Anyway very grateful for everything you guys done!
Sexan is offline   Reply With Quote
Old 08-09-2022, 03:21 AM   #32
Sexan
Human being with feelings
 
Sexan's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 4,689
Default

Swipe bug:



If you go under last group things get lil funky

This box flickers for some reason:

Last edited by Sexan; 08-09-2022 at 03:26 AM.
Sexan is offline   Reply With Quote
Old 08-09-2022, 03:33 AM   #33
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,820
Default

Quote:
Originally Posted by Sexan View Post
Regarding fades could it be done as separate modifier
Yes, we'll try that.
schwa is offline   Reply With Quote
Old 08-09-2022, 04:49 AM   #34
AZpercussion
Human being with feelings
 
Join Date: Oct 2019
Location: Moscow / Tbilisi
Posts: 912
Default

It would be useful to have mouse action to draw razor edit area ignoring grouping. The same for excluding from razor area too.


Regarding group manager, I think it would be better to have track list in dropdown view, not just one string.
For now there are all tracks in drop down menu. It's inconvenient for big projects.

In the dropdown view tracks could be shown as in a folder and we could enable/disable one track in group and go to grouping properties for editing their flags.
For adding other tracks there may be + icon near group name with two choices: choose track from list or just add selected track in the group.
Yeah, it requires some internal changes in grouping logic...
AZpercussion is offline   Reply With Quote
Old 08-09-2022, 07:53 AM   #35
nofish
Human being with feelings
 
nofish's Avatar
 
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,109
Default

Quote:
Originally Posted by mike@overtonedsp View Post
#CLAP
@nofish

You need to be sure that you implement value_to_text properly (even if this isn't the issue here) because the host will use this to query the plugin, and the plug-in returns a human readable string of the parameter value.
(...)
Thanks.
I think the host (REAPER) can deal with the param fine as I can tweak/automate it and it does what it should (I think), it's just that it's not displayed in the genreic UI.



Quote:
EDIT: Since +dev808a I'm now missing the second to last parameter (or the last displayable e.g. not marked as CLAP_PARAM_IS_HIDDEN parameter) in the generic UI - so something broke between 808 and 808a. Window resizing is now remembered correctly - could this be related to that fix?
Interesting, I just checked with +dev808, for me the param isn't displayed either unfortunately.
nofish is offline   Reply With Quote
Old 08-09-2022, 08:00 AM   #36
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,820
Default

Quote:
Originally Posted by mike@overtonedsp View Post
EDIT: Since +dev808a I'm now missing the second to last parameter (or the last displayable e.g. not marked as CLAP_PARAM_IS_HIDDEN parameter) in the generic UI - so something broke between 808 and 808a. Window resizing is now remembered correctly - could this be related to that fix?
Can you link to a plugin that demonstrates this please? I'm sure it's somewhere up-thread or in a previous thread but I'm not finding it.
schwa is offline   Reply With Quote
Old 08-09-2022, 08:23 AM   #37
mike@overtonedsp
Human being with feelings
 
mike@overtonedsp's Avatar
 
Join Date: Sep 2018
Location: Oxford, England
Posts: 219
Default

@schwa

Quote:
Can you link to a plugin that demonstrates this please? I'm sure it's somewhere up-thread or in a previous thread but I'm not finding it.
There's one I made here:

https://www.acmt.co.uk/products/down...3sa/index.html

In the generic UI it only shows

HPFreq
LPFreq
Bypass
Trim

Its missing the Polarity (Phase) parameter which is the last displayable parameter.

EDIT: (The plug-in also has a CLAP_PARAM_IS HIDDEN | CLAP_PARAM_IS_BYPASS parameter called 'host bypass' which is intended to be set (by the host) when the plugin is bypassed by the host but this doesn't seem to work in Reaper - according to the CLAP SDK it should be 'Bypass On' = 1.0 (max) 'Bypass Off' = 0.0 (Min). This would then allow me to 'grey out' the UI if / when the plug-in is disabled in Reaper. It would be great if this worked - but would require checking that it doesn't break functionality with other plug-ins)

Last edited by mike@overtonedsp; 08-09-2022 at 09:10 AM.
mike@overtonedsp is offline   Reply With Quote
Old 08-09-2022, 09:13 AM   #38
mike@overtonedsp
Human being with feelings
 
mike@overtonedsp's Avatar
 
Join Date: Sep 2018
Location: Oxford, England
Posts: 219
Default

Quote:
Originally Posted by mike@overtonedsp View Post
@schwa



There's one I made here:

https://www.acmt.co.uk/products/down...3sa/index.html

In the generic UI it only shows

HPFreq
LPFreq
Bypass
Trim

Its missing the Polarity (Phase) parameter which is the last displayable parameter.

EDIT: (The plug-in also has a CLAP_PARAM_IS HIDDEN | CLAP_PARAM_IS_BYPASS parameter called 'host bypass' which is intended to be set (by the host) when the plugin is bypassed by the host but this doesn't seem to work in Reaper - according to the CLAP SDK it should be 'Bypass On' = 1.0 (max) 'Bypass Off' = 0.0 (Min). This would then allow me to 'grey out' the UI if / when the plug-in is disabled in Reaper. It would be great if this worked - but would require checking that it doesn't break functionality with other plug-ins)
Just realised you won't see the issue with that release of the plug-in. Could be something my end - but it actually seems like if I mark the last parameter as CLAP_PARAM_IS_HIDDEN (because this is my 'host bypass' parameter which I don't want the user to see) then both it and the previous parameter are hidden in the generic UI. Marking any other parameter in the list as hidden works as expected. Parameters are displayed (or hidden) correctly in Bitwig, so this does look like a Reaper issue.

Last edited by mike@overtonedsp; 08-09-2022 at 09:29 AM.
mike@overtonedsp is offline   Reply With Quote
Old 08-09-2022, 09:49 AM   #39
I hate ac/dc so much
Human being with feelings
 
I hate ac/dc so much's Avatar
 
Join Date: Aug 2022
Posts: 4
Default

[*] * Includes feature branch: internal pin management overhaul for future extension


What is this one about? Is there any additional info about it?
I hate ac/dc so much is offline   Reply With Quote
Old 08-26-2022, 08:19 AM   #40
sonicartist
Human being with feelings
 
Join Date: Dec 2014
Posts: 21
Default Core use control for Batch Processing

I am unable to use some of my more CPU intensive UAD plugins with Reaper's Batch Processing, or ANY Batch Processor for that matter. The problem is that the Batch Processors attempt to process more files than the UAD hardware can handle simultaneously. The hardware quickly reaches its limit and Reaper sends back errors telling me some of the files were not processed properly. There are thousands of files being processed in any given batch. I was hoping the new Core use control in Batch Processing would help but thinking a Wait State or something like it would need to be implemented to solve this. I have the latest pre-release but I am not seeing the drop-down menu. Please help, I am at a dead stop in production at this point.

I've been posting on another thread so here is my original post.

Long time casual user of Reaper but testing now for a move from Pro Tools and really loving so much here as I dig deeper. Currently working on an expansion pack for Slate Drums and the developers at Slate recommended Reaper as the development DAW.

A showstopper here, however, is using some of my UAD plugins with Reaper Batch Processing. With many UAD plugins, their hardware is required and there are limitations on how many plugins you can run concurrently depending on how many cores your UAD hardware provides. Some of their more intensive plugins, the HELIOS EQ plugin for example, are not playing well with Reaper's Batch Processor. The Batch Processor runs full speed ahead and quickly fills my UAD resources resulting in errors and files not being processed properly. There are thousands of files in the cue at any given time. It is true that Reaper BP provides a single thread option which technically would do the job if I had several hours to wait for each instance, but there are far too many batches during mastering for such a long wait.

What I am proposing and hoping you can do is to offer some kind of throttling or limit on how many files can be Batch Processed at the same time so that it won't CPU/Core intensity of the plugin won't matter and Reaper BP will work for ANY of the amazing UAD plugins.

Thank you so much for an amazing DAW! Loving the community and certainly the genius of Cockos.
sonicartist 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 02:09 PM.


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