v6.0rc1 - November 21 2019

[airon]

This jumped out. I am testing playback and mixing on some of my larger sessions too.

Small workflow tidbit on the MCP in the extended mixer.

A send whose volume is automated will have a small ring around the small secondary volume indicator on the right side. That ring is so small, it's harder to see than usual when that colour changes from GREEN to RED, which indicates a latched status.

That change of colour is the only indicator of the latched status.

The level indicator in that area is not coloured according to what status that send volume is in, i.e. trim-read/reading/latched.

So I'm looking at a miniscule ring surrounding a replicated level indicator. That could definitely be better. Fill the volume indicator with the status colour as well ? Or make a 7 o'clock to 5 o'clock solid indicator that carries the status colour with itself.


Second is the colour choice for the latched parameters that are indicated via parameter knobs on the MCP. I can hardly read them at a glance.

Here's a screenshot to illustrate both points.
https://stash.reaper.fm/37550/r60rc1...%20colours.png
The red send slots are muted.

[White Tie]

Originally Posted by Klangfarben

It's not even close to being done (which WT will be the first to admit).

No, its pretty much finished.

[Klangfarben]

Originally Posted by White Tie

No, its pretty much finished.

Yesterday it's Alpha and several issues being discussed and today RC1? Really??

[antti]

Resampling: optimize and greatly improve quality of resampling for convesion between common rates

Question for anyone who knows about this: Why does it matter for quality if you use common vs uncommon rates? A quick test in Octave confirmed that a 64 point sinc-interpolator (the default length in Reaper) can get 100+ dB stopband attenuation for fractional samplerate conversion and steep enough transition band for even over 50% downconversion (96 -> 44.1 kHz). Speed improvement is of course obvious and the filter cutoff can be slightly optimized for those cases but it shouldn't have much effect on the quality itself.

Related to that, why is there even an option for 768 point sinc called "Extreme HQ" when that much pre-ringing is more likely to cause issues than any improvement in transition band width?

[ovnis]

With the last version, there is an issue with toolbars text icons. There is no more relief.

[nofish]

Re: Track wiring diagram

I just tried it with one of my projects (~70 tracks) and to be honest, I'm not sure which useful info it could give me. It's basically mainly a lot of (currently cut off, as mentioned) wires. :P
Imo it would need some sort of filter function to be useful (or maybe option to only show selected tracks)?

edit:
Ok, some wire filtering options are in right click context, missed that at first..

[EvilDragon]

Originally Posted by nofish

edit:
Ok, some wire filtering options are in right click context, missed that at first..

Still not enough to make it useful, IMHO.



>>> No, its pretty much finished.


It looks far from finished. *shudders* Let's see what will the reviews say about the interface yet once again, when v6 is released... I expect general ridicule.

[_Stevie_]

Is the v6 to be considered feature complete? If so, I’m a bit speechless.

[nofish]

Originally Posted by EvilDragon

Still not enough to make it useful, IMHO.

Agreed.

[EvilDragon]

Originally Posted by _Stevie_

Is the v6 to be considered feature complete? If so, I’m a bit speechless.

With Reaper there's no such thing as feature complete. There'll be v6.0 and in two days you'll get v6.0.1

[_Stevie_]

Well, what's highly irritating me is that we went from a 5.9xx feature set to a v6 RC1. I think it would have made more sense, if the devs had switched to a v6 beta at some point. But this just doesn't make sense to me at all...

[EvilDragon]

Well if we consider how long we were in 5.9.x world, it could be considered as a concealed beta.

[Klangfarben]

Originally Posted by EvilDragon

With Reaper there's no such thing as feature complete. There'll be v6.0 and in two days you'll get v6.0.1

I think he meant more in terms of major features. Generally those get added during a major cycle release like this.

It really looks like all the 5.x dev versions should have just been named 6.0 alpha versions since it looks like those formed the basis for v6 without any real specific or new v6 features.

[ovnis]

I don't care about to know if we are going to switch to V6 or not.

V4, V5, V6... it's only marketing and business...

[MaCs]

Originally Posted by _Stevie_

Well, what's highly irritating me is that we went from a 5.9xx feature set to a v6 RC1. I think it would have made more sense, if the devs had switched to a v6 beta at some point. But this just doesn't make sense to me at all...

That's their way of doing. And I think users get a lot of value compared with what they are paying for.

[tusitala]

Originally Posted by Justin

Edit: thanks (retina displays), fixing!

Thank you very much Justin!


Is there any news about a possible articulation management feature for version 6 ?


All the best

-t

[Klangfarben]

Originally Posted by ovnis

I don't care about to know if we are going to switch to V6 or not.

V4, V5, V6... it's only marketing and business...

In terms of Reaper, yes I agree. However, there were a LOT of V6 threads floating around with many great suggestions and requests. Releasing it this way is sort of ignoring all those requests and saying, hey sorry, maybe next time when V7 rolls around. Not only is the 5.x dev versions forming the basis for V6 unorthodox, but I think doing it this way makes some users feel like their suggestions and input wasn't valued or even considered. Because generally a major cycle release will have at least a FEW of those feature requests.

[heda]

6.0 could be this and then 6.01 could have a big new surprise feature. You never know. I remember v5.0 didn't come with notation editor which would have been a good feature alone to just change from v4 to v5 in other companies.. Then notation editor came a few updates later.

Then you have other examples... like Blender... the change from Blender 2.79 to 2.80 was so huge that it should have been Blender 3.0 instead... Blender and REAPER are my favourite softwares... I'm fine with it. note.. I'm very bad giving version numbers to my scripts

[pepe44]

Testing v6 Rc1
when reaeq is embeded on TCP / MCp the mousewheel doesnt change the bandwidth
Dirac LE , NICE

[Jae.Thomas]

totally fiending for reatune to embed

[Funkybot]

Originally Posted by heda

6.0 could be this and then 6.01 could have a big new surprise feature. You never know. I remember v5.0 didn't come with notation editor which would have been a good feature alone to just change from v4 to v5 in other companies.. Then notation editor came a few updates later.

That's how I feel. Both notation and ARA came in the v5 lifecyle. Big additions on top of everything else. HiDPi support probably isn't a small thing either. Reaper's frequent update approach has always meant it's in a near-constant state of flux/improvement. The major version numbers are less important with Reaper compared to other DAWs for this reason.

[robgb]

Originally Posted by schwa

Also, JS plugin UIs can be embedded.

Hmm. The option is greyed out for me with JS plugins.

[EvilDragon]

Originally Posted by robgb

Hmm. The option is greyed out for me with JS plugins.

Not all JS FX, only those that use gfx. If they just have the generic sliderse, they can't be embedded.

[pepe44]

Just open the same project on 5.987 and 6 rc1

RT on 6 is 0.9%
RT on 5.987 is 3.9%

Total CPU is the same 29%

Nice.

[Xenakios]

Originally Posted by robgb

Hmm. The option is greyed out for me with JS plugins.

It needs to be a JS plugin with a custom GUI. The ones with only the sliders won't work.

[HighVoltage]

Not sure where to put this bug, but it only happens in pre-releases since around 5.97.
Happens in this one too, but not in the official releases.

When i move my mouse over a floating window, be it an open VST window, the media explorer, or a Midi take's window, and there is something under those windows that would display a tooltip, the tooltip shows through the middle of the window, like the mouse is not over the topmost window, but under it.

This screen shows that i moved my mouse over the media explorer (quickly), but a tooltip was triggered from the mixer below it:
https://prnt.sc/q0q9fg
https://prntscr.com/q0pzdl

The worst part is that the tooltip stays there as long as im inside the window, and it even blocks the mouse hit area.


Win 10 (1909)
Reaper x64

[HighVoltage]

Action: Set default CC shape to Square no longer works

[nofish]

Originally Posted by _Stevie_

Well, what's highly irritating me is that we went from a 5.9xx feature set to a v6 RC1. I think it would have made more sense, if the devs had switched to a v6 beta at some point. But this just doesn't make sense to me at all...

Answered quite on point (imo) here:
https://www.askjf.com/index.php?q=4542s

edit:
To add, having read this answer some time ago I'm not really surprised that v6 went straight to rc, considering that the +dev releases were regarded as the v6 alpha/beta phases.

[asai]

As a software developer myself I've learned that version numbers are almost entirely non-standard and there are a lot of factors that go into it.

When a project such as Reaper is ongoing so consistently for so many years, with as much user participation as it has (and actually welcomes,) I think we need to be a little less critical of Cockos and their decision to release an RC rather than a beta.

Now I know that everyone on this forum is an active participant and enthusiastically supports Reaper development, so we all know that it's not so important that they've released an RC considering how long we were in 5.9.x which was basically a beta for 6 the whole time.

These guys, more than any other DAW developer I've experienced, are ON IT. And the features keep on rolling out between just the two of them, and they are gracious and humble enough about sharing their work and receiving feedback. So let's be generous in our appreciation.

[juliansader]

The new auto-stretch timebase still doesn't work if the item contains user-inserted stretch markers, and the item is copy/pasted using actions, as shown in the top right item in this image (as reported in the BOO version):




BTW, since MIDI items don't follow track and project default timebases if these are set to "Time", it may avoid confusion if Project settings and Action names refer to "Timebase for non-MIDI items/envelopes/markers"

[Justin]

Originally Posted by EvilDragon

Well if we consider how long we were in 5.9.x world, it could be considered as a concealed beta.

5.98x+devXXYY was more or less a 6 beta, yep.

There is enough major new stuff in there that it would be irresponsible for us to put it in 5.9xy. People don't expect major major (potentially disruptive) changes in .0xy releases. We do too much of it already. :/ With a x.0 we can get away with more significant changes.

[pepe44]

Is the Dirac algorithm only available on the 32 bits version ? Just installed the 64 bits and no Dirac LE there!

[Tale]

Originally Posted by antti

Why does it matter for quality if you use common vs uncommon rates?

Because for integer rates that have a common divisor (e.g. 44100 <-> 48000 or 96000) you can use higher oversampling without interpolation (see WDL_Resampler changes from April/May for the dirty details).

[Garrick]

Originally Posted by Jason Brian Merrill

totally fiending for reatune to embed

Good call!

[Klangfarben]

Originally Posted by nofish

Answered quite on point (imo) here:
https://www.askjf.com/index.php?q=4542s

edit:
To add, having read this answer some time ago I'm not really surprised that v6 went straight to rc, considering that the +dev releases were regarded as the v6 alpha/beta phases.

The problem with this is that there are a whole lot of users who don't use or test the pre release, probably the largest amount of users, so doing it this way means they didn't really have a voice in the development of V6. If it was named 6.0 beta/pre/dev etc. I think there would have been a lot more users jumping in and testing and giving feedback.

[Xasman]

Originally Posted by pepe44

Is the Dirac algorithm only available on the 32 bits version ? Just installed the 64 bits and no Dirac LE there!

See https://forum.cockos.com/showpost.ph...54&postcount=6

[pepe44]

Originally Posted by Xasman

See https://forum.cockos.com/showpost.ph...54&postcount=6

Thanks!
i swear i saw it there on the 32 bits version! ehheh

[antti]

Originally Posted by Tale

Because for integer rates that have a common divisor (e.g. 44100 <-> 48000 or 96000) you can use higher oversampling without interpolation (see WDL_Resampler changes from April/May for the dirty details).

That helps for cpu (roughly halves it) but doesn't have any effect on quality with properly implemented fractional samplerate converter (assuming the same filter specifications are used for both).

[musicbynumbers]

Originally Posted by tusitala

Is there any news about a possible articulation management feature for version 6 ?
-t

I can't lie.. I'm really hoping this comes at some point soon too. It would be a massive help

[pbognar]

Originally Posted by heda

6.0 could be this and then 6.01 could have a big new surprise feature. You never know. I remember v5.0 didn't come with notation editor which would have been a good feature alone to just change from v4 to v5 in other companies.. Then notation editor came a few updates later.

Then you have other examples... like Blender... the change from Blender 2.79 to 2.80 was so huge that it should have been Blender 3.0 instead... Blender and REAPER are my favourite softwares... I'm fine with it. note.. I'm very bad giving version numbers to my scripts

Exactly - I was going to post the same thing. Notation arrived in 5.20...

So I calculate that the chord track should arrive in 6.30 - Bwahahaha!!!