Page 1 of 1

bug: Instrument tab not working great on macOS

Posted: 13 Dec 2020 01:40
by fxt
Radium is working quit good now on macOS, the only thing that seems buggy is navigating and dragging instruments in the modular patch window around. Sometims navigating the space with the navigation bar doesn't work and sometimes dragging instances around does not work.

Re: bug: Instrument tab not working great on macOS

Posted: 13 Dec 2020 09:48
by kjetil
Thanks for reporting. I don't have access to a mac right now, but I'll look at it soon. Which version of macOS are you using?

(BTW. I guess you meant the modular mixer and not the instrument tab?)

Re: bug: Instrument tab not working great on macOS

Posted: 23 Dec 2020 16:12
by fxt
i mean the modular patch tab where you connect instruments, fx and do audio routing. I'll do a video as soon as I find some time.

Re: bug: Instrument tab not working great on macOS

Posted: 29 Dec 2020 10:26
by kjetil
Oh, sorry, I misunderstood, "patch" is the word meaning instrument in the source code of Radium. :-)

I think the issue you're describing the same as this one: https://github.com/kmatheussen/radium/issues/1291

Re: bug: Instrument tab not working great on macOS

Posted: 06 Feb 2021 22:11
by fxt
hello, the found out that the bug only applies when using the trackpad on my macbook, using a mouse works perfectly.

I'm talking about the modular mixing area where one is patching instruments, and doing audio routing :)

and just to specify, I don't man the snapping, but the scrollbar is jumping around erratic when scrolling up/down in the area.

Re: bug: Instrument tab not working great on macOS

Posted: 07 Feb 2021 16:08
by kjetil
Hmm, it's a little bit difficult developing for mac in these times since I don't have a mac at home, and I'm not at Notam very often because of the virus restrictions. But I'll try to remember testing this when I get the chance.

But have you checked if the behavior has been better in Radium 6.7.68 or later? At least the snapping behavior magically got fixed in that release, probably because the build environment and all 3rd party libraries were updated in that release.