Changing presets (using plugin's native preset system) in FabFilter Twin2 VST3 results in loss of audio.
This is still an issue with pre3
This seems fixed in pre4, however...whenever presets are changed in Twin2, audio information will start to flicker.
I also noticed this (but I can't replicate anymore): sometimes, when changing presets you can see how GUI becomes sluggish (I was able to observe it by playing MIDI keyboard while changing presets - upon each preset change, plugin's MIDI keyboard felt sluggish for half a second or so)
I witnessed none of this issues in Studio One which I've been testing for the last few days...
In any case, it seems something is not right here...
REAPER was truly awesome when dealing with third-party VST2.4 plugins...I hope it continues to be so with VST3 too.
It's not a bug, but a sidechain dropdown for plugins, in the pin connector dialog, adds midi send besides audio send. Is it real to avoid this behaviour and make only an audio send?
Actually, they all do, see example 2 below. I'm relatively sure these AVI's are raw "screenstream" avi exports from Camtasia captures, but they show everywhere else correctly.
when audio if first take and midi is second take of a media item, midi does not show up consistently in second take lane.
I'm trying to use midi as a sort of pitch graph view of my audio.
basically the bug is that midi "peaks" are rendered based on what midi is enabled (midi is enabled when selected as the active take)... but I need midi to be rendered regardless of whether it's the active take or not.
__________________ Soundemote - Home of the chaosfly and pretty oscilloscope. MyReaperPlugin - Easy-to-use cross-platform C++ REAPER extension template
Did also the stable VST2.4 engine of Reaper 4.76 change in V5pre x versions?
I ask because there are many plugins that work perfect in 4.76 but not as they should in V5pre´s with VST2.
Sometimes result in graf. flickering on the top of the main reaper window when loading a preset.
That seems so that
memory areas -when loading presets inside the plugins- overlap with the graphic frame buffer or whatever.
And it doesn´t happen with the same plugins on the same machine with Reaper 4.76
Quote:
ELP:
There are now a lot of problems with melda plugins and Reaper 5 preX.
Both versions VST2 and VST3.
For example MMultibandconvolution and loading main presets inside the plugin. Produce a lot of flickering on the top of the main reaper window,
cpu hooks, long preset changing/loading time etc.pp.
32 Bit and 64 Bit systems, V5x both VST2 and VST3 unusable.
The same plugins with Reaper 4.76 VST2 works perfect and in other VST3 hosts the VST3 versions works also perfect,
but not with reaper 5.Xpre. As I said both VST2 and VST3.
PitchSlap:
I can confirm this. Those plugins all have weird non-standard interfaces which is probably a factor, but I do also seem to get issues with some VST2.4 plugins. Basically when editing settings, the GUI will become unresponsive and Reaper will hang, but if I wait 3-5 minutes, it works.
still happens pre4, melda plugins and other not really usable Vst2 and Vst3
__________________
I hope you can understand me? Without german beer my written english is always very bad, with beer it becomes unbearable!.
Less is more! To much limited the own creativity.
I was working on a project and accidentally removed an instance of Kontakt 5 from the mixer, I used undo and although Reaper brought Kontakt back it was blank and I lost all my loaded instruments.
I was working on a project and accidentally removed an instance of Kontakt 5 from the mixer, I used undo and although Reaper brought Kontakt back it was blank and I lost all my loaded instruments.
Maybe it's just me, but still... Using Reaper v5.0pre5b (portable install) :
1) let's say you have several tracks in your project, each of them having a height of something between 25 and 60 pixels.
2) arm any track for record : the height of the track involved suddenly jumps to something around 70 pixels (73 for both 'default' and 'default_4.0' themes, 72 for the 'Classic_1.x' one and strangely only 65 for my own 'Piolit' theme). And you are no longer able to reduce its height, this, until you 'unarm' it...
This doesn't happen on Reaper 4.75 with the same project, no matter the theme used. Could someone confirm or tell me what I am missing ?
EDIT : the same issue occurs when you select a track with the 'Automatic record-arm when track selected' option enabled, this, until you unselect it...
pre5c x64
Opening Volume envelope and closing causes fader volume to go to 60db,on any track not VCA related
I can also confirm this, but there are a couple of conditions neccesary to reproduce the bug:
-the envelope must be set to fader scaling mode.
-There can't be any automation points on the envelope aside from the intial zero point at the start of the timeline
The actions "move cursor right/left to grid division" are broken in V5 if I have my grid division set to frames. Rather than moving the cursor one frame at a time, it moves different amounts depending on how far I'm zoomed in/out. In v4 it always moves the cursor by a single frame no matter what my zoom level is.
I can also confirm this, but there are a couple of conditions neccesary to reproduce the bug:
-the envelope must be set to fader scaling mode.
-There can't be any automation points on the envelope aside from the intial zero point at the start of the timeline
Confirmed here also with the above mentioned conditions.
Maybe to do with Preferences -> Audio -> Recording -> Always show full track control panel on armed tracks ?
You're right... Completely forgot that this one was even existing. With pre1, I didn't have to check it, as it was working as expected as with 4.xx. Guess that installing pre5b over it changed the setting in a way or an other. But I'm the only culprit, honestly...
Since you're fixing weirdness on the timeline could you please take a look at this long-standing bug when unfreezing edited tracks?
Steps to reproduce:
1) Select a few tracks and freeze them
2) Unlock items on frozen tracks and edit/move them around
3) Unfreeze these tracks now
Result: items aren't placed correctly again (since REAPER warns the user that all edits will be discarded it should drop all changes and move items back accordingly).
Here you can see two examples of this problem:
Example 1:
Example 2:
__________________ Pressure is what turns coal into diamonds - Michael a.k.a. Runaway
Trying to export almost 13,000 media items for a sample library via export dialog "Selected Media Items" and the speed of the dialog box was extremely slow. Please stop the dialog from unecessary updating! PLZZZZZZZZ. Whether it's changing the ouput filename or the output format, the dialog insisted on re-calculating 13,000 file names for every character typed or any small change made. Suggestion: Update the file names only after clicking on the [###### files] button (the button that reveals file names via rudimentary scrolling list)
__________________ Soundemote - Home of the chaosfly and pretty oscilloscope. MyReaperPlugin - Easy-to-use cross-platform C++ REAPER extension template
TrackFX_FormatParamValue() unselects currently selected envelope (tested only when TrackFX_FormatParamValue() formats the value for currently selected track envelope)
Set active takes to ... color commands are broken.
1. Create two or three takes on a track.
2. Slice it up and make active take selection
3. Right click, Item and take colors, Set active takes to custom color or random color.
Expected behavior: Only the active take selection to be colored accordingly.
seems broken (it seems to be broken when using volume envelope fader scaling) In test project (see attachment) use GetEnvelopePoint() to get value of the first point in envelope. GetEnvelopePoint() says it's 545.22, but .rpp says it's 0.38. If you need my REAPER.ini, I'll send it to support mail. (using pre8)
Add some item FX automation, leave Reaper / shift focus to another editor or workstation, come back to Reaper, it's non-responsive and has to be forced quit.
seems broken (it seems to be broken when using volume envelope fader scaling) In test project (see attachment) use GetEnvelopePoint() to get value of the first point in envelope. GetEnvelopePoint() says it's 545.22, but .rpp says it's 0.38. If you need my REAPER.ini, I'll send it to support mail. (using pre8)
I think we have to use SLIDER2DB/DB2SLIDER when "volume envelope fader scaling" is selected: