Old 03-19-2019, 02:39 PM   #1
mabian
Moderator
 
mabian's Avatar
 
Join Date: Aug 2007
Location: Italy
Posts: 4,326
Default v5.973+dev0319 - March 19 2019

v5.973+dev0319 - March 19 2019
  • + ARA: improve alignment of various interfaces/objects
  • + Notation editor: improve behavior when moving notation between tracks [t=209875]
  • + Render dialog: fix persistence of render tail setting in certain cases [t=218639]
  • # VST3: fix incorrect behavior relating to Waves CLA issue with recent dev builds [p=2110195]
Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

Last edited by mabian; 03-19-2019 at 02:40 PM. Reason: Formatting
mabian is offline   Reply With Quote
Old 03-20-2019, 03:54 AM   #2
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

Quote:
Originally Posted by mabian View Post
+ Notation editor: [/COLOR][/b]improve behavior when moving notation between tracks [t=209875]
It's on a good way. Still problems:

1)
- select notation with a note
- drag up
BUG - everything moves down at first



2)
- select notation in the first and second measure
- drag left
BUG - the item is extended but the notation is misplaces

Regarding item extension - note editing does extend items. The old behaviour is that notation events editing does not extend it. Maybe it would be appropriate that also notation editing would extend it.

bFooz is offline   Reply With Quote
Old 03-20-2019, 09:10 AM   #3
Valle
Human being with feelings
 
Valle's Avatar
 
Join Date: Nov 2007
Location: Sweden
Posts: 808
Default

Quote:
# VST3: fix incorrect behavior relating to Waves CLA issue with recent dev builds [p=2110195]


I think *maybe* the CLA MH issue is gone. Here's how it went:
  • I installed v5.973+dev0319, ran it and loaded the test file. It worked!!!

  • Loaded another (real) project containing CLA MH. Worked!

  • Closed v5.973+dev0319 to do some tests with other REAPER versions. All OK.

  • Then I ran v5.973+dev0319 again, loaded the test file, and ... *POOF* ... REAPER completely – now even without the Runtime Error message – disappears from the face of the screen. Retrying to execute v5.973+dev0319, loading the file ... again: *POOF* ... (AARGH! Not the *POOF*, I hate *POOFs*!)

  • So, I re-installed v5.973+dev0319, then restarted Windows. Ran v5.973+dev0319, loaded the test file again. It worked!

  • Since, I've tested back and forth, deliberately trying to crash REAPER. But everything reads and loads as expected. Not one *POOF*.

So, hopefully the issue is gone, and the *POOFs* may have had to do with old "rest files" that required a Windows reboot or something. I don't know.

Allow me to add just one more thing (nothing to do with the issue itself):

I’ve been a REAPER-only user since 2008. And it’s times like this when you feel that the developers did this “for me” (OK, not “for me” literally speaking , rather for all of us) – and within such small time range – that you know that you are dealing with a top, first class company/developer/support/software. Cockos rock!
__________________
Valenzia Vision
Valle is offline   Reply With Quote
Old 03-20-2019, 10:41 AM   #4
emwhy
Human being with feelings
 
Join Date: Apr 2018
Posts: 270
Default

Probably don't have to go to my extreme, but whenever I update Reaper for a new release or pre release I always delete the current reaper.ini file (or just rename it) and let the program rebuild itself over. Then I import my preferences file and it's back to normal. Seems to work well and will hopefully avoid any POOF....I hate that too.
emwhy is offline   Reply With Quote
Old 03-20-2019, 11:21 AM   #5
Valle
Human being with feelings
 
Valle's Avatar
 
Join Date: Nov 2007
Location: Sweden
Posts: 808
Default

Quote:
Originally Posted by emwhy View Post
whenever I update Reaper for a new release or pre release I always delete the current reaper.ini file (or just rename it) and let the program rebuild itself over. Then I import my preferences file and it's back to normal. Seems to work well and will hopefully avoid any POOF....I hate that too.
Good tip. Althogh, I honestly can't remember ever having any POOFs and/or crashes with REAPER with my setup. This was the first time since my "first" REAPER version (v2.001). I never delete, move or modify any files. I just install over it all. And I always install and use newest version for all my works (public, pre- or dev, whichever is the latest).
__________________
Valenzia Vision
Valle is offline   Reply With Quote
Old 03-21-2019, 04:03 AM   #6
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
Default

The VCA stacking works fine.
Could it be that every VCA level adds another buffer block of latency ? It feels like it with two levels VCAs. Not tried more levels yet.
This is all pushing faders while playback is engaged.
__________________
Using Latch Preview (Video) - Faderport 16 setup for CSI 1.1 , CSI 3.10
Website
"My ego comes pre-shrunk" - Randy Thom
airon is offline   Reply With Quote
Old 03-21-2019, 06:50 AM   #7
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,721
Default

Quote:
Originally Posted by airon View Post
The VCA stacking works fine.
Could it be that every VCA level adds another buffer block of latency ? It feels like it with two levels VCAs. Not tried more levels yet.
This is all pushing faders while playback is engaged.
VCAs are all zero latency...
Justin 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:15 PM.


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