reasurround prerelease discussion - Page 16

AZpercussion · 03-11-2021, 02:13 AM

Angle values are cool, but there is a troubles to enter values below zero. The same for xyz positions.

Berg · 03-11-2021, 02:22 AM

Quote:

Originally Posted by schwa

I do get exactly equal panning in that scenario. I would guess your center rear speaker is not positioned exactly in the center, or maybe the right rear speaker influence is set higher than the center rear? Or maybe the input puck is fractionally to the right of +50 ... I'd expect to see atan(0.5)=+153(.435..) degrees at +50,-100 but I see +154 in your screenshot.

Well, I checked it but I still have this strange behavior here for this 6.1 setup, could not fix it.
Thanks for the other corrections, now user setups are more friendly !

schwa · 03-11-2021, 05:14 AM

Quote:

Originally Posted by AZpercussion

Angle values are cool, but there is a troubles to enter values below zero. The same for xyz positions.

I'm not seeing this problem?

schwa · 03-11-2021, 05:15 AM

Quote:

Originally Posted by Berg

Well, I checked it but I still have this strange behavior here for this 6.1 setup, could not fix it.
Thanks for the other corrections, now user setups are more friendly !

Want to post the project with just that one track?

Berg · 03-11-2021, 05:21 AM

Quote:

Originally Posted by schwa

Want to post the project with just that one track?

Please find the session, OS X here.

schwa · 03-11-2021, 05:43 AM

I suppose we should show more digits!

svijayrathinam · 03-11-2021, 04:17 PM

Quote:

Originally Posted by svijayrathinam

Hi Schwa,

I have another issue which is very much related to this. I have made a little video to show that issue and also showed how protools handles the same issue. Pls take a look at this. The protools way could be a possible solution. But Pls think of a suitable solution for this..Pls...

Here is a video link

https://youtu.be/UEz0qD4rmqg

thank you very much..

Hi schwa,

Can you pls make a better way to handle this issue please? Perhaps with the new media item channel mapper ? Pls.. I am still struggling with this issue when it comes to plugins

junh1024 · 03-11-2021, 09:57 PM

Quote:

Originally Posted by svijayrathinam

Hi schwa,

Can you pls make a better way to handle this issue please? Perhaps with the new media item channel mapper ? Pls.. I am still struggling with this issue when it comes to plugins

SO in the video it looks like PT is doing auto multi-mono (or multi-stereo) for non-surround FX instantiation & maybe (auto) parameter linking.

For 20>91 compression (but not multi-band compression), I can think of a few workarounds for now. eg, Compress in 20 BEFORE panning to 91, or using surround compressors (there are a few available). Do you still need "auto multi-mono for non-surround FX" ?

Berg · 03-12-2021, 01:30 AM

Quote:

Originally Posted by schwa

I suppose we should show more digits!

Please see what I have, equal level is obtained for +41 XYZ source position.

Berg · 03-12-2021, 01:30 AM

Quote:

Originally Posted by svijayrathinam

Hi schwa,

Can you pls make a better way to handle this issue please? Perhaps with the new media item channel mapper ? Pls.. I am still struggling with this issue when it comes to plugins

Yes, it would be very useful.

svijayrathinam · 03-12-2021, 01:52 AM

Quote:

Originally Posted by junh1024

SO in the video it looks like PT is doing auto multi-mono (or multi-stereo) for non-surround FX instantiation & maybe (auto) parameter linking.

I already spoke about this. Some Plugins have 100s of parameters. Like fab EQs and fab Pro Rs. Linking parameters will take hours..Unless there is a way to just put two plugins and hit one button to link all parameters of selected plugins..

Quote:

Originally Posted by junh1024

For 20>91 compression (but not multi-band compression), I can think of a few workarounds for now. eg, Compress in 20 BEFORE panning to 91, or using surround compressors (there are a few available). Do you still need "auto multi-mono for non-surround FX" ?

I Cant compress before panning. For example..I have a bunch of tracks and all of them have surround panner on them and they are routed to A folder. I want to have a multi band compressor there. Also I do have the TB reverb and I know it supports 16 channels. But Ideally I would like to have the freedom we have in protools where we can use any plugin as multichannel.

We are looking for a simple way to change plugin mapping and easy linking of plugin parameters. One button and link all parameters. And Another idea suggested here earlier was plugin folders..

schwa · 03-12-2021, 05:12 AM

Quote:

Originally Posted by Berg

Please see what I have, equal level is obtained for +41 XYZ source position.

If you can post the project it's a lot more useful than a screenshot!

Berg · 03-12-2021, 05:46 AM

Quote:

Originally Posted by schwa

If you can post the project it's a lot more useful than a screenshot!

Sorry, I thought you could open the session .rpp.
Here is a link to my session which is very simple.

https://www.dropbox.com/s/5n4q1ido3h...ound2.RPP?dl=0

schwa · 03-12-2021, 06:44 AM

Ah, ok, that's a bug that affects custom speaker setups. It should fix your project if you select the center rear speaker and type in 0 for the X position, even though it already displays 0. We'll fix the bug for the next build.

Rodulf · 03-12-2021, 10:07 AM

Does anybody have any idea when RS2 will be released? It sounds so interesting.

junh1024 · 03-12-2021, 04:51 PM

Quote:

Originally Posted by Rodulf

Does anybody have any idea when RS2 will be released? It sounds so interesting.

See https://forum.cockos.com/showthread.php?t=22836

Quote:

Originally Posted by svijayrathinam

I already spoke about this. Some Plugins have 100s of parameters. Like fab EQs and fab Pro Rs. Linking parameters will take hours..Unless there is a way to just put two plugins and hit one button to link all parameters of selected plugins..
...
We are looking for a simple way to change plugin mapping and easy linking of plugin parameters. One button and link all parameters. And Another idea suggested here earlier was plugin folders..

OK then.

If RPR would do auto multi-stereo it might save more CPU compared to auto multi-mono. Also, a native surround FX might save CPU vs multi-X, or not (depends per-case). Since Fabfilter tends to be high-CPU & toneboosters medium, and ReaXComp low.

AZpercussion · 03-13-2021, 08:26 AM

Quote:

Originally Posted by schwa

I'm not seeing this problem?

I found what exactly the problem is.
The values are applied automatically. And if nothing is typed, the value becomes +0.
When I type "-" and ponder a little, for example, something distracts me or I am in transport with a laptop and the typing speed is lower than usual (this is how I tested it), the typed minus is applied as +0. The following numbers give a positive value.
So "-" should be applied like -0.

svijayrathinam · 03-13-2021, 08:37 AM

Quote:

Originally Posted by junh1024

OK then.

If RPR would do auto multi-stereo it might save more CPU compared to auto multi-mono. Also, a native surround FX might save CPU vs multi-X, or not (depends per-case). Since Fabfilter tends to be high-CPU & toneboosters medium, and ReaXComp low.

Actually in my experience I found fab filter less cpu intensive than tone boosters. Normally in my project I tend to have 100s of fab filter plugins as take FX and reaper handles them with ease !

Berg · 03-14-2021, 02:28 AM

Quote:

Originally Posted by schwa

Ah, ok, that's a bug that affects custom speaker setups. It should fix your project if you select the center rear speaker and type in 0 for the X position, even though it already displays 0. We'll fix the bug for the next build.

Thanks, works now perfectly for 6.1 film.
BUG : I tested a 7.1 SDDS Film (or Dolby Atmos for large screen) which gives us the same behavior, for +-25 or +- 75 X source position.

AZpercussion · 03-14-2021, 11:52 AM

Track channels count doesn't update when plugin preset loading.
But it does if you change output setup separately.

Also option to pass through or zero out unmapped output channels doesn't saved in presets.

musicbynumbers · 03-14-2021, 02:11 PM

Quote:

Originally Posted by AZpercussion

Track channels count doesn't update when plugin preset loading.
But it does if you change output setup separately.

Also option to pass through or zero out unmapped output channels doesn't saved in presets.

Nice catch! Bug 2 especially!

plush2 · 03-14-2021, 07:52 PM

The UI seems to be freezing again while writing automation with ReaSurroundPan and other VST3 plugins (Dear VR Pro) as described in this previous post. musicbynumbers, you had this problem before also. Are you seeing it again?

musicbynumbers · 03-15-2021, 01:18 AM

Quote:

Originally Posted by plush2

The UI seems to be freezing again while writing automation with ReaSurroundPan and other VST3 plugins (Dear VR Pro) as described in this previous post. musicbynumbers, you had this problem before also. Are you seeing it again?

Not been working with automation much last week or so. I'll try and test it later today and get back to you.

musicbynumbers · 03-15-2021, 03:09 AM

Quote:

Originally Posted by plush2

The UI seems to be freezing again while writing automation with ReaSurroundPan and other VST3 plugins (Dear VR Pro) as described in this previous post. musicbynumbers, you had this problem before also. Are you seeing it again?

Just tested and it's pretty broken for me too. Very intermittent and erm "janky" again

Especially touch automation as it's not able to record a few seconds without dropping out of an automation item and then back in again leaving bits of AI everywhere.

Maybe the cpu change that fixed it got removed?

schwa · 03-15-2021, 05:09 AM

Writing automation via what method?

musicbynumbers · 03-15-2021, 09:18 AM

Quote:

Originally Posted by schwa

Writing automation via what method?

For that quick test it was with a normal mouse on the actual reasurround pan GUI, moving around input 1's XY in touch mode.

I can test other methods if that helps?

That was super smooth after the fix you guys put it in but is now broken again.

plush2 · 03-15-2021, 09:48 AM

Quote:

Originally Posted by schwa

Writing automation via what method?

I was using touch mode as well. I can go back a few versions if you like and see exactly when the regression happened.

plush2 · 03-15-2021, 10:10 AM

Quote:

Originally Posted by schwa

Writing automation via what method?

The problem reasserts itself at build v6.25+dev0309. The previous several builds work (back to when we first submitted the bug) up until that point and every build since exhibits the same problem.

Because the UI of the underlying Reaper freezes completely when attempting to write automation in the plugin UI it doesn't seem to matter which automation mode we are in. The automation is not captured accurately.

musicbynumbers · 03-15-2021, 05:42 PM

I'm still seeing the automation/gui issue here.

It's not as bad maybe with one input being moved (although still get ai dropouts) but if I link say 4 inputs together and move one for 8 lanes at once then it gets very stuck.

schwa · 03-15-2021, 06:02 PM

I'm really not seeing any issue with automation in the 0315 build, either on windows on mac. There was an issue with the 0309 and later builds on windows, but that was corrected in 0315.

musicbynumbers · 03-15-2021, 06:12 PM

Quote:

Originally Posted by schwa

I'm really not seeing any issue with automation in the 0315 build, either on windows on mac.

It might be something specific to my settings then. See if Plush still has any issues I guess

A few settings that might be different to others here could be me having a 64 samples buffer and 20 cores (well 10 real ones).

Here's an image of my buffer settings if that helps.

fakemaxwell · 03-15-2021, 08:55 PM

I'm not getting any GUI lag but definitely some strange behavior with automation in 6.25+dev0315.

When in touch mode, panning by using the puck on the VST, automation drops in and out. Write mode seems to work normally:

When undoing the animation laid in like this, each little block is a separate undo point:

Using the pan pot on the automation track works, but it's reversed. Guessing this has to do with matching the regular track pan direction with ReaSurroundPan. Also, when you hit Ctrl-Z to undo, the automation lane crunches down in size:

Tested in 6.25 and the automation lane crunch happens there too, so that isn't just for ReaSurroundPan. I guess I never noticed the automation undo points chunking up like that, it happens in Write mode as well.

plush2 · 03-15-2021, 09:02 PM

Quote:

Originally Posted by schwa

I'm really not seeing any issue with automation in the 0315 build, either on windows on mac. There was an issue with the 0309 and later builds on windows, but that was corrected in 0315.

I am definitely still seeing the issues with 0315. It's like the whole Reaper program UI under the plugin UI freezes for decent stretches of time while manipulating the pucks. This happens however the track is set to automate anything or even when I'm just moving the panner around in regular playback. As before, it does not behave this way in the embedded UI.

It is very odd as it works perfectly in 0308 and then not again in any version after that. I should reiterate that I'm seeing the same behaviour with the Dear VR Pro panner as well (as I was the case the first time we noticed this bug). I also notice it with Toneboosters Equalizer 4.

musicbynumbers · 03-16-2021, 12:58 AM

One difference too could be that I have 6 monitors spread over two nvidia graphics cards. And reaper's various windows are spread over 5 of them.

Maybe plush2 has multi monitors too?

Could it be this?

Berg · 03-16-2021, 02:17 AM

Same type as previous bug with 7.1 SDDS Film, I noticed another bug with the 7.1.4 Dolby Atmos preset, when panning the source on the sides at equal distance from left side and left front, Y=+50, we don't have equal level. We have 2,5 dB difference. Please have a look at the jpeg below. Same thing on the rear part between left side and left rear.

schwa · 03-16-2021, 07:05 AM

Quote:

Originally Posted by Berg

I noticed another bug with the 7.1.4 Dolby Atmos preset, when panning the source on the sides at equal distance from left side and left front, Y=+50, we don't have equal level

Ah, sorry, fixing!

schwa · 03-16-2021, 07:11 AM

Regarding the automation issues, is there a difference in the behavior when using the regular overhead view vs the 3D view? Also, are you on a hidpi display?

schwa · 03-16-2021, 07:13 AM

Quote:

Originally Posted by plush2

This happens however the track is set to automate anything or even when I'm just moving the panner around in regular playback.

So I understand, you're seeing this issue even when not automating anything?

schwa · 03-16-2021, 08:55 AM

Quote:

Originally Posted by plush2

it works perfectly in 0308

Frustratingly, I am able to reproduce the plugin drawing updates blocking the REAPER UI from updating on windows, with a busy scene in 3D view, but I can't see any difference in the behavior in 0308 vs later builds. And the report of other plugins having the same issue seems like a complete red herring as far as I can tell.

Would you mind verifying that you are seeing different view updating behavior in *other* plugins in the 0308 build vs later builds?

plush2 · 03-16-2021, 09:17 AM

Quote:

Originally Posted by schwa

Regarding the automation issues, is there a difference in the behavior when using the regular overhead view vs the 3D view? Also, are you on a hidpi display?

Interesting, the problem happens in the overhead view and the 3d view but not in the triple view (with the three boxes from axial perspectives) found on the middle view button. In that view I can select in any of the three perspectives and the UI of Reaper does not lock up. Using an assignable knob (eg. Left/Right) with the overhead view does not lock up the UI. It would seem using mouse or touch to manipulate that canvas is the thing causing the freeze.

I am on an hidpi display and I do have multiple monitors (but only 2

).

It seems interesting to me that those other 2 VST3 plugins lock up the UI in the exact same way yet other VST3 plugins (like melda mautoequalizer) which do a very similar top-down canvas UI do not. In all cases, it is just on the canvas (the speaker layout or the eq nodes display) that the freezing is caused. Any of the knobs, sliders or other controls do not cause the freeze up.

In my case the UI freezes while the transport is playing back regardless of whether I'm automating or not. As soon as I grab a puck (or a canvas control in the other VST3 plugins) and start moving the UI in Reaper starts to freeze up.