::R5 Bug Reports here::

[Mercado_Negro]

Let's use this thread to collect bugs reports for REAPER 5 pre-releases. Please use announcement threads for discussion only.

Originally Posted by DarkStar

Please post:
-- one-line summary of the issue / problem
-- steps to create it
-- result
-- expected result (optional)
-- error messages, crash logs (faulting module, fault offset) (if any)

Originally Posted by schwa

Thanks for all the feedback! We will start plowing through all of the bug reports and suggestions. There will be a lot to do, so if you feel like your bug report was overlooked when the next build comes out, please don't hesitate to remind us.

As in the past, we will be tweaking, changing, and adding features for a while before officially releasing the new version.

[Sexan]

Redrawing jitter not present in 4.76:



Automation bypass on TCP has slow response if clicking fast

On first 2 seconds I click very slow,its ON and OFF,but on fast clicking there I think its triggering select all points action

Also (this happens on any version) in scenario with dual monitors, when you have Master track docked on the right side of the screen clicking on IO or Track Send opens IO window on secondary screen(Primary screen is Reaper,secondary is extend to the right side),it would be cool if there can be some kind of screen limit not to open it on secondary monitor

[Win Conway]

Tint item background strength does nothing in prefs now, if version 5 is tagged in rtconfig
Tried using itemtint in rtconfig, guessing it isn't implemented yet ?

Theme tweaker is completely borked as far as i can tell



As you can see the colors just change randomly

[White Tie]

Originally Posted by gpunk_w

Tint item background strength does nothing in prefs now, if version 5 is tagged in rtconfig

No a bug. Documentation will explain in due time.

Originally Posted by gpunk_w

Tried using itemtint in rtconfig, guessing it isn't implemented yet ?

I don't know what that is.

Originally Posted by gpunk_w

Theme tweaker is completely borked as far as i can tell

As you can see the colors just change randomly

Yes, confirmed.

[Win Conway]

i was trying itemtint to see if it tinted item background, ill wait till you doc it up

[Slick]

Show/Hide Track Envelope for last Touched FX Parametr not working...

[Nixon]

Draw labels over solid background for easier reading doesn't seem to work.
Volume, pan and width indications seem to get a little cut above in tcp.
Show/hide playrate control doesn't work either.

OSX 10.7.5 reaper 64 bit.

[gofer]

Originally Posted by Slick

Show/Hide Track Envelope for last Touched FX Parametr not working...

Confirmed for all "...last touched FX parameter" actions, (including "set alias...", "set MIDI learn" and "adjust...").
Working fine from the "Param" menu.

[schwa]

Originally Posted by Slick

Show/Hide Track Envelope for last Touched FX Parametr not working...

Fixed for the next build, thanks!

[Mercado_Negro]

PDC changes when audio channels are enabled/disabled during playback. It only happens with the VST3 version of several plug-ins (Softube TLA-100, Waves C-6, etc). Video here:

https://www.mediafire.com/?80zz4tpf7vckd9k

FIXED

[Argitoth]

ReaTune fx render as midi problem affects reaper 5, but not reaper-5-specific

[schwa]

Originally Posted by Mercado_Negro

PDC changes when audio channels are enabled/disabled during playback. It only happens with the VST3 version of several plug-ins (Softube TLA-100, Waves C-6, etc). Video here:

https://www.mediafire.com/?80zz4tpf7vckd9k

Thanks for the report. Weird bug! Are there any other plugins you know of that demonstrate this problem?

[semiquaver]

If I play a project with video past the end of the video the video window goes black and stays black until Reaper is restarted. Using the new decoder on osx 10.9.5.

[Mercado_Negro]

Originally Posted by schwa

Thanks for the report. Weird bug! Are there any other plugins you know of that demonstrate this problem?

Unfortunately no. Waves C6, Softube TLA-100 and CL1B are the only ones I have with VST3 and sidechain support.

[vicnest]

Got a few to report:
(1)Automation sliders or rotary button does not use the right range.
This bug even applied to track reapers build in track "Width". (+/- 100% in this case)

[vicnest]

(2) Automation parameter names are unclear when there are clearly space for one larger column text field (compared to the dark panel left unused).
The fader or rotary button could be in the 2nd row.
(I know there is a smaller text entry below showing current select envelope, but to view all at once would be quicker and more systematic)
(3) When automation lanes have various customized height, on one of the VST2 parameter automation lane, drag and UNDO, reset all the customized height. Only the customized height on track parameters (pre-vol, vol, pan, width, and etc.) persist when UNDO.
Usually kind of lost after UNDOing envelope drag in a parameter with customized height.

[vicnest]

(4)VST3 plug-in automation value looks very buggy. The parameter is the SSL Duende X-EQ gain with +/-20dB.
Also it would be nice if the display value on the envelope could be persist rather than actual dB value on current time and equal points but numeric ratios on other points.

At least make it optional for current selected envelope if such processing takes too much power for all envelopes.

Thank you

[Shootkin]

Waves again:



The behaviour even worse now.

Faulting application name: reaper.exe, version: 4.9.9.11, time stamp: 0x54977e0e
Faulting module name: WaveShell-VST3 9.3_x64.vst3, version: 9.3.30.1, time stamp: 0x546027f0
Exception code: 0xc0000005
Fault offset: 0x000000000002c9e7
Faulting process id: 0x538
Faulting application start time: 0x01d01f2bcfa7f892
Faulting application path: C:\Program Files\REAPER5\reaper.exe
Faulting module path: C:\Program Files\Common Files\VST3\WaveShell-VST3 9.3_x64.vst3
Report Id: 6b981789-8b1f-11e4-82a3-28d244831729
Faulting package full name:
Faulting package-relative application ID:

[PitchSlap]

Not sure how useful this is, but I had Reaper hang when doing basic tasks on the arrange page (don't remember exactly what, I think I might've been editing an automation envelope). I got the same crash doing something totally different as well. This is a (fairly complex) track started in 4.76. I have both R4 and R5 installed on the same machine but in different directories. I'm going to go back to 4 for the time being.

Problem signature:
  Problem Event Name:	AppHangB1
  Application Name:	reaper.exe
  Application Version:	4.9.9.11
  Application Timestamp:	54977e0e
  Hang Signature:	f2fc
  Hang Type:	769
  OS Version:	6.1.7600.2.0.0.256.1
  Locale ID:	1033
  Additional Hang Signature 1:	f2fcceff8c738d86e628cec002b02ac4
  Additional Hang Signature 2:	6110
  Additional Hang Signature 3:	6110881b5d536287afd5d73308b48138
  Additional Hang Signature 4:	f2fc
  Additional Hang Signature 5:	f2fcceff8c738d86e628cec002b02ac4
  Additional Hang Signature 6:	6110
  Additional Hang Signature 7:	6110881b5d536287afd5d73308b48138

Here's another crash I got when closing a project (crash happened after the tracks were removed)

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	reaper.exe
  Application Version:	4.9.9.11
  Application Timestamp:	54977e0e
  Fault Module Name:	reaper.exe
  Fault Module Version:	4.9.9.11
  Fault Module Timestamp:	54977e0e
  Exception Code:	c0000005
  Exception Offset:	00000000002bef85
  OS Version:	6.1.7600.2.0.0.256.1
  Locale ID:	1033

[mete0r]

Sending to a reaverb causes pops/clicks, but only if rendering from File menu or from a group (and not both tracks separately at the same time).

Steps to recreate: http://puu.sh/dHzQW/20d38ec108.gz
Results: Included in above link.
Expected results: Included in above link (in the separate renders).

EDIT: Please note I'm using linux.

[Lazarus]

I don't know if this is all ReaScript GetUserInputs or just v5/Lua, but there is a trailing whitespace char in the return value from Lua.

[DarkStar]

When I start Reaper, the title bar and some of my toolbar icons are not refreshed fully. In the following the top screenshot is after starting Reaper and the lower one is after clicking (e;g Play then Stop, or adding an FX):



(This also also happened in v4.75 but I do not now have that installed)

[hwhalen]

http://forum.cockos.com/showthread.php?t=140835

[schwa]

Originally Posted by Mercado_Negro

PDC changes when audio channels are enabled/disabled during playback. It only happens with the VST3 version of several plug-ins (Softube TLA-100, Waves C-6, etc). Video here:

https://www.mediafire.com/?80zz4tpf7vckd9k

Haha, this is actually a very old and not VST3 specific bug. It will be fixed for pre3 (and fixed for the next 4.x release, too).

[vitalker]

From version 4...

[Mercado_Negro]

Originally Posted by schwa

Haha, this is actually a very old and not VST3 specific bug. It will be fixed for pre3 (and fixed for the next 4.x release, too).

Thanks, schwa. I tried it with their VST2 versions and I couldn't reproduce it, that's why I thought it was VST3 specific (and I never saw that in 4.x hehe). Anyways, I'm glad it's gonna be fixed. Merry Xmas, mate!

[Mercado_Negro]

VST3 Scanning issues:

Originally Posted by aMUSEd

Getting lots of crashes on scanning my VST3 folder

Hang on loading Padshop Pro - then crash trying it a second time

Same with Halion 5

So far only been able to open Largo VST3i and PPGWave 2

but can't access PPG Wave 2 presets!

[WyattRice]

Download the latest 5 pre2.

The external editor set in the prefs (e.g. notepad++) for reascripts is not working as it did.

[PitchSlap]

Crash with 5.0pre2 on startup while scanning plugins (initial VST3 scan). After the crash Reaper eventually started however.

Also the version # seems off in the crash report (5.0pre1 said 4.9.9.x), unless this was a lingering R4 process that crashed when R5 tried to start.

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	reaper.exe
  Application Version:	4.7.5.61
  Application Timestamp:	548cd657
  Fault Module Name:	vorbis.acm
  Fault Module Version:	0.0.3.6
  Fault Module Timestamp:	50a51541
  Exception Code:	c0000005
  Exception Offset:	0000000000001f4f
  OS Version:	6.1.7600.2.0.0.256.1
  Locale ID:	1033
  Additional Information 1:	3d8e
  Additional Information 2:	3d8ec6c8639549a9bc622ff3d1c2eeba
  Additional Information 3:	cecc
  Additional Information 4:	cecc689019567a9b0bbea1ab13a00560

After this Reaper crashed when I tried to load the Schaak Transient Shaper plugin (one of the only VST3s I had installed) and Windows said it applied some compatibility settings to Reaper, which is something that has never happened with any previous versions...

[Gates of Horn & Ivory]

I'm getting lots of black flickering over the entire Reaper window when I resize the TCP sidebar or any dockers. In both pre1 and pre2. Using OSX, both 32 and 64 versions.

Edit: horizontal zooming by left-dragging on the ruler marker/region lanes area is now very jerky and unresponsive.

[aMUSEd]

Originally Posted by Mercado_Negro

VST3 Scanning issues:

It's not just scanning issues, there seems to be no support for loading and saving vstpresets so far.

[Justin]

Originally Posted by Gates of Horn & Ivory

I'm getting lots of black flickering over the entire Reaper window when I resize the TCP sidebar or any dockers. In both pre1 and pre2. Using OSX, both 32 and 64 versions.

Edit: horizontal zooming by left-dragging on the ruler marker/region lanes area is now very jerky and unresponsive.

What OSX version?

[Gates of Horn & Ivory]

10.10

Would updating to 10.10.1 fix it?

[SmajjL]

Bug detected in the preset list system of the ReaPlugs. (ReaEQ, ReaComp for sure)

Pick any preset and the preset name will not follow\update correctly, blank.
The preset itself will change, i assume correct..
Then try to mouse scroll in the list from there, good luck.
This is a R5 bug since pre1, both 32\64bit (checked)
The latest official work as before, but..
I have never as far as i can remember been able to mouse scroll from (no preset) as a start point.
Had to select something down the list and then it works.

Note: Non Reaplugs seems to work "as before"

Im on Windows7 64bit.

Merry Christmas devs & Co >*

[bluzkat]

My VST3 FabFilter and Voxengo plugins don't show up in the FX browser.

(pre 2)

[vitalker]

Originally Posted by bluzkat

My VST3 FabFilter and Voxengo plugins don't show up in the FX browser.

Open reaper-vstplugins64.ini/reaper-vstplugins.ini in Reaper's root, find notes about these plugins and delete these strings. Open Reaper and Have fun!

[Tale]

As already reported in the pre1 thread, but now tested against pre2:

If I save a project with the VST3 version of one of the newer Arturia synths (tested Matrix-12 V, Solina V, VOX V), and load it back, then all settings are lost and there is no sound. If I then select a preset everything is fine again, so it would look like settings aren't recalled when loading the project. VirtualCZ does seem to recall its settings [in pre1], so I am not sure if this is a REAPER 5 or an Arturia issue (although I think the Arturia synths work fine in other VST3 hosts).

EDIT: Arturia Oberheim SEM V VST3i also doesn't recall its setting properly.

EDIT: Using v5.0pre5 I have compared VOX V data chunks in the RPP file, and it would seem that the VST3 data chunk is corrupted (see attached RPPs). However, I still can't say if this is REAPER's or Arturia's fault.

[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 flicker 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 unuseable.
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.

Merry christmas all

[pepe44]

Mixer and track Panel shows weird if not in default layout mode! Anyone experiencing problems as well ?
Macbook Pro core i5 4 G RAM
Yosemite 10.10.1
Reaper V5 pre2

[swiiscompos]

The theme tweaker is still broken: when you click on a color setting the color window won't appear if another one is already open. It is open, just not visible.