v6.64+dev0804 - August 4 2022

[sockmonkey72]

v6.64+dev0804 - August 4 2022

• * 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
• + FX: improve syncing displayed value in generic UI [p=2583032]
• + MIDI: add action for retroactive record
• + PCM: support importing .pcm, drag-importing .raw audio files
• + SD2: support reading/playing back/converting .sd2 and other raw audio files, with limited support for specifying audio attributes (see .sd2 source properties)
• # CLAP: add %CLAP_PATH% support for path list, default
• # CLAP: always show menu when clicking re-scan button, to allow clear cache+rescan
• # CLAP: apply path changes when re-scanning plug-ins
• # CLAP: fix display of parameters in generic UI [p=2583166]
• # CLAP: if vst_scan=1 (or =3) in reaper.ini, use in-process scanning
• # CLAP: properly handle MIDI note-offs encoded as note-on with velocity zero
• # CLAP: support category and developer listing in Add FX dialog (requires re-scan, also the first exported "feature" is used as the category)
• # CLAP: update generic UI in response to parameter change events [p=2583184]
• # CLAP: use separate persistent configuration state for renamed 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

[sockmonkey72]

• + MIDI: add action for retroactive record

!!!

[STOP]

Originally Posted by sockmonkey72

v6.64+dev0804 - August 4 2022


# CLAP: properly handle MIDI note-offs encoded as note-on with velocity zero

CLAP version of Surge XT work fine now. Thanx

[mike@overtonedsp]

# CLAP: update generic UI in response to parameter change events [p=2583184]

That seems to have fixed the issues I was having with parameter max / min values in the generic UI too.

[tonalstates]

Originally Posted by sockmonkey72

v6.64+dev0804 - August 4 2022[*]+ MIDI: add action for retroactive record

Yeeeeeeesssss! Thank you devs! Long awaited


Edit:

Trying out Surge XT on CLAP I get crackels whenever I move any parameter slider, while this doesn't happen with the AU or VST3, this while playing a midi item. Anyone to confirm with other CLAP plugins or the same? Idk if it's on REAPER's CLAP integration or on the synth

[Paul Eye]

Originally Posted by tonalstates

Trying out Surge XT on CLAP I get crackels whenever I move any parameter slider, while this doesn't happen with the AU or VST3, this while playing a midi item. Anyone to confirm with other CLAP plugins or the same? Idk if it's on REAPER's CLAP integration or on the synth

Yep, same here with Surge XT 1.1.0. The CLAP version crackles, VST3 doesn't.
Other CLAP synths I tried (Odin, Fluctus, a few Full Bucket synths) don't have this crackling.

[PitchSlap]

Originally Posted by sockmonkey72

• + FX: improve syncing displayed value in generic UI [p=2583032]
• + MIDI: add action for retroactive record

Thanks! I've been hoping for native retrospective record since switching from Cubase 10+ years ago. Hopefully we could get for audio at some point too.

As for generic UIs, I've always wished we could enter precise values.

[baconpaul]

Originally Posted by Paul Eye

Yep, same here with Surge XT 1.1.0. The CLAP version crackles, VST3 doesn't.
Other CLAP synths I tried (Odin, Fluctus, a few Full Bucket synths) don't have this crackling.

Yeah confirmed this and we know why. Talking with the team about whether this is a surge or reaper problem or both but have a fix if we decide it is a surge problem. (There's a point in the API where it's unclear whether the host can do X; and surge assumes non-defensively that it won't do X; and reaper does X. So I can merge the defense against X, or reaper can stop doing X, or both )

[Paul Eye]

Originally Posted by baconpaul

Yeah confirmed this and we know why. Talking with the team about whether this is a surge or reaper problem or both but have a fix if we decide it is a surge problem. (There's a point in the API where it's unclear whether the host can do X; and surge assumes non-defensively that it won't do X; and reaper does X. So I can merge the defense against X, or reaper can stop doing X, or both )

This is both suitably vague and reassuring enough. Hopefully whatever solution (API/Reaper/Surge) you come up with is most beneficial

[STOP]

Originally Posted by tonalstates

Trying out Surge XT on CLAP I get crackels whenever I move any parameter slider

Confirm.

-No crackle when parameter are assign to midi learn > potentiometer.

[Funkybot]

Originally Posted by sockmonkey72

v6.64+dev0804 - August 4 2022[*]# CLAP: support category and developer listing in Add FX dialog (requires re-scan, also the first exported "feature" is used as the category)

When I went to Preferences -> Plugins -> LV2/CLAP and did a "Clear cache and rescan" none of these items appeared in the FX Browser (Developer or Category). Even restarted Reaper and did it again.

When I did a "scan for new plugins" in the FX Browser itself, then I saw the changes.

I would expect the results to be the same regardless of where the scan occurred. Not a high priority item.

[Arthur McArthur]

Originally Posted by sockmonkey72

v6.64+dev0804 - August 4 2022
[*]+ MIDI: add action for retroactive record

Great stuff, devs!

It would be great if this feature was extended to support loop recording. If you're jamming along to a looped section, it currently only inserts the data from the last loop, which isn't I expected. Ideally, it would insert all of the data played since the transport was started into takes in an item, matching the normal record functionality.

[srdmusic]

Originally Posted by sockmonkey72

v6.64+dev0804 - August 4 2022
[*]+ MIDI: add action for retroactive record

Fantastic!!!! Thank you DEVs

[Kundalinguist]

Schwa

.sd2 file conversion is working as intended.

I located my source file; set the desired parameters, and then out came a .wav file that played the audio content in its new format.

Perfect. Thank you very much. The only thing I have not tested yet is how this conversion will work in aligning files in an old DP project, meaning: if there is something stored in the way of alignment information within the transformed audio file. I'll try that tomorrow.

Thanks again.

[Daodan]

Originally Posted by sockmonkey72

v6.64+dev0804 - August 4 2022
+ MIDI: add action for retroactive record

Thanks!!!

Tested with vkb. If you play too fast you can get this

[hans]

Hi devs! Sorry for repeating myself here, but the following fix for 0803 wasn't fixed even though it was addressed in the 0803 changelog.

# Track grouping: handle mouse modifier to adjust item contents and right edge [p=2582906]

[AZpercussion]

Originally Posted by hans

Hi devs! Sorry for repeating myself here, but the following fix for 0803 wasn't fixed even though it was addressed in the 0803 changelog.

# Track grouping: handle mouse modifier to adjust item contents and right edge [p=2582906]

Moreover, all these actions don't work properly with auto grouping:

[doofered]

Hi Devs! I've tested CLAP plugin compability and found that PDC is not working for CLAP plugins. Thank you for your diligence! <3

[schwa]

Originally Posted by hans

Hi devs! Sorry for repeating myself here, but the following fix for 0803 wasn't fixed even though it was addressed in the 0803 changelog.

# Track grouping: handle mouse modifier to adjust item contents and right edge [p=2582906]

When doing edits that affect an edge, only grouped items that align with that edge will be edited. This is the way grouped edge editing works in general, although I could see an argument that this particular edit is a kind of a special case.

[AZpercussion]

Originally Posted by schwa

When doing edits that affect an edge, only grouped items that align with that edge will be edited. This is the way grouped edge editing works in general, although I could see an argument that this particular edit is a kind of a special case.

Align edges don't work properly too.

[hans]

Originally Posted by schwa

When doing edits that affect an edge, only grouped items that align with that edge will be edited. This is the way grouped edge editing works in general, although I could see an argument that this particular edit is a kind of a special case.

Alright! Hope you'll find the argument good enough to implement it for the grouped tracks! Thanks!



Track group editing. All tracks set both to follow and lead.
Edges are being affected on the same track and above items, but not under.
On the last track, I can adjust all items right edge and contents using the "move contents and right edge" modifier.

[Justin]

Originally Posted by Daodan

Thanks!!!

Tested with vkb. If you play too fast you can get this

ah thanks, fixing!

[mike@overtonedsp]

I currently have a parameter flagged CLAP_PARAM_IS_BYPASS which the CLAP SDK implies should be used for merging host and plug-in bypass functions if necessary.

I'm using it to 'grey out' the plugin UI, when set - as an indication to the user that the plugin has been disabled in the host e.g. with the checkbox unticked.

Reaper doesn't appear to support this - could it be added?

e.g.

Plugin disabled (checkbox unchecked) host_bypass (CLAP_PARAM_IS_BYPASS) = 1.0 or Max value

Plugin enabled (checkbox checked) host_bypass (CLAP_PARAM_IS_BYPASS) = 0.0 or Min value

[BartR]

Originally Posted by sockmonkey72

v6.64+dev0804 - August 4 2022

• + MIDI: add action for retroactive record]

That's a great improvement!
I wish it will be also for Audio Files not only MIDI, in the future.

Thank you also for this beauty.

[airon]

Little test on three plugins from two different devs.

SurgeXT is ok.

Surge FX Plugin is ok, except for the GUI on the plugin not changing when parameters are automated and the automation is played back.
FX Parameter knobs on TCP/MCP display the changes and are completely fine. The GUI of the plugin is not.


Chowd BYOD
The plugins GUI is fine. Processing fine.
Reapers GUI responds to commands, but GUI drawing stops after I hit play for some audio on the timeline. The audio is fine, but Reaper just stops drawing anything really. Yet the GUI still works. I could drag a fader on the MCP around and a little box popped up for the changing track volume, but other than that nothing was drawn.

[Tale]

• + PCM: support importing .pcm, drag-importing .raw audio files

I don't suppose we can import raw floating-point audio, right?

[schwa]

Originally Posted by Tale

I don't suppose we can import raw floating-point audio, right?

We could support that, do you know of some application that generates it?

[BrokenTriplet]

Originally Posted by schwa

We could support that, do you know of some application that generates it?

Sound Forge is at least one that has supported 32 and 64bit float formats in the .RAW custom format menu, since v11 at least.

[schwa]

Is it easy for you (anyone) to link to one?

[BrokenTriplet]

Originally Posted by schwa

Is it easy for you (anyone) to link to one?

Here you go:

https://we.tl/t-gfILxrxYff

It's a 909 kick, 44.1KHz, 32-bit IEEE stereo

[Tale]

Originally Posted by schwa

We could support that, do you know of some application that generates it?

Audacity, but only because I explicitly tell it to do so. Also, I don't have a lot of raw floating-point audio files, and I don't use them all that much.

Currently I will import them into Audacity, and then export them to WAV format, so I can import them into REAPER, but if it's very little trouble to add something like BITSPERSAMPLE 32F or FORMAT FLOAT to the raw source properties, then that would be nice to have.

[schwa]

Originally Posted by Tale

Audacity, but only because I explicitly tell it to do so. Also, I don't have a lot of raw floating-point audio files, and I don't use them all that much.

Link to a file (or send it to us) and we'll add support for it!

[Tale]

Originally Posted by schwa

Link to a file (or send it to us) and we'll add support for it!

Okidoki! Here's a ZIP containing 2 seconds of 220 Hz sine wave at 44.1 kHz in 32-bit and 64-bit floating-point, both little-endian.

[Meo-Ada Mespotine]

Originally Posted by sockmonkey72

[*]+ MIDI: add action for retroactive record

Nice addition!

[Tale]

In the generic UI REAPER displays the unit string twice, but only after you've touched the slider.

Steps to reproduce:

1. Launch REAPER.
2. Create track.
3. Add a VST plugin e.g. ReaEQ to track.
4. Switch to generic UI.
5. Notice Freq or Gain parameter value, e.g. "100.0 Hz" or "0.0 dB".
6. Drag a Freq or Gain parameter, value changes to e.g. "96.6 Hz Hz" or "0.0 dB dB".

It works fine with v6.64+dev0803 and older (including v6.64), so I was thinking that it might be related to this change:

• + FX: improve syncing displayed value in generic UI [p=2583032]

Tested using REAPER v6.64+dev0804 x64 on Windows 10.

[Tale]

Originally Posted by Tale

In the generic UI REAPER displays the unit string twice, but only after you've touched the slider.

Fixed in v6.64+dev0808, thanks!