Looking for Linux beta testers

[ggarra13]

This is your opportunity to get your hands on vmrv2 for free! I am currently looking for some Linux beta-testers (any flavor except Ubuntu) for vmrv2.
If this interest you, contact me privately at [email protected]

[RafaelLinux]

openSUSE TW user here, would like to help.
Operating System: openSUSE Tumbleweed 20251031
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: AMD Radeon RX 7600

First test:
Simply launching hdr-64 v1.4.4, not loading nothing, this is the aspect of the application window (a 4x black square overlapping application window).

[ggarra13]

Do you have any Desktop scaling factor? I am not familiar with Plasma, but on Gnome you can set the scaling factor of each of your screens.
Also, for testing purposes, can you do Ctrl + and Ctrl - to dynamically scale the windows?

[RafaelLinux]

yes, Plasma (Wayland) let user change scaling factor. In fact, mine it about 150% for my 4K monitor.
The usual Ctrl + {+|-} keyboard shortcuts are enabled and they work, albeit abnormally. Normally, the CONTENT of the window should increase or decrease, but with HDR application, EVERYTHING (including the container window and the black box) becomes proportionally larger or smaller.

[ggarra13]

Ctrl + {+|-} updates everything. If it is working fine. the Vulkan content (ie. the black content) and the menus should scale.
Try the mrv2 program (the OpenGL version -- not vmrv2) to see if it exhibits the same scaling issue. If it does, we can rule out a Vulkan problem and we will be left with either a Wayland / Kwin one.

To rule out a Wayland issue, try:

FLTK_BACKEND=x11 mrv2

or:

FLTK_BACKEND=x11 hdr

If it displays properly, that should point to a Wayland issue. If it does not, we are facing a Vulkan / Kwin one.

[RafaelLinux]

I'm only trying HDR, and it worked.

I will not try with mrv2, cause it shows constantly the modal window about licence.

[ggarra13]

I will not try with mrv2, cause it shows constantly the modal window about licence.

The whole point of this thread is to beta test vmrv2. I put my email at the top of this thread. Contact me at the email with your machine ID information and will give you a node-locked license for a year.

If you don't want to see the modal window about the license or become a beta tester, you can choose to install v1.4.0 of mrv2 which is free (not donationware) and does not ask for a license. However, it does not support Vulkan (ie. no HDR).

[ggarra13]

Congratulations! You found a really nasty bug in the Wayland scaling. I have now fixed it for both vmrv2 (which is donationware) and hdr (which is not). You can download the latest betas from:

https://mega.nz/folder/6O4RhaQT#PnrzFMdAkjK83iJOr-Dy0g

or wait until they are available at sourceforge.

Anyway, the offer for a license still stands, if you want it. You have qualified as a good beta tester.

[RafaelLinux]

I used version 1.0.5 of your program some time ago, and I still had it installed. By chance, I wanted to insert some text and geometric shapes into a video for a tutorial, and while looking for a new version, I came across the discussion thread where you mentioned needing a tester on Linux.

What I'm trying to say is that I'm not a regular mrv2 user, and I honestly don't think I'll ever use HDR, which is why I wouldn't make a donation—but I can help out while I have the time. Bear in mind I'd need to watch all the videos before continuing with tests, and that takes time, but it's the only way to avoid reporting bugs that might just be down to my lack of familiarity with the app.

For now, in my testing, simply playing a video in mrv2 v1.4.4, I've noticed some lag in certain parts, despite not having changed anything in the video, which was HD resolution. I found that performance issue odd. Anyway, didn't try more for mentioned annoying modal window.

I'm sorry, I didn't notice your text about writing you asking to be a beta tester ;)

[ggarra13]

Bear in mind I'd need to watch all the videos before continuing with tests, and that takes time, but it's the only way to avoid reporting bugs that might just be down to my lack of familiarity with the app.

Okay. Note that some videos are close to 2 to 3 years-old so many things have changed.

For now, in my testing, simply playing a video in mrv2 v1.4.4, I've noticed some lag in certain parts, despite not having changed anything in the video, which was HD resolution. I found that performance issue odd. Anyway, didn't try more for mentioned annoying modal window.

Please test vmrv2 (ie. the Vulkan version of mrv2), now at v1.4.5:

https://mega.nz/folder/6O4RhaQT#PnrzFMdAkjK83iJOr-Dy0g

or mrv2 (ie. the OpenGL version of mrv2), now at v1.4.5:

https://mega.nz/folder/OXwS0TaQ#25ZQzUOt9C4Z7PxlJYQUeg

If you still see a slow down with v1.4.5, please post which backend you are using (mrv2 or vmrv2).

[RafaelLinux]

VMRV

The Vulkan version crashes when loading videos that I can open with the OpenGL version (I've left you what comes up in the console, which is different depending on whether it's an AVI or MKV video).

Opening an AVI file

vmrv2
ERROR:  [lic.] "No valid license found for machine=293ef77dec0d45069ad30059ebd24e90"
        [main] mrv2 v1.4.5 Vulkan - Built Nov  5 2025 20:29:08 - Release
        [main] Set Language to en_US.UTF-8, Numbers to C
        [main] Build Environment:
        [main]  Distribution: Rocky Linux release 8.10 (Green Obsidian) 
        [main]  Desktop Environment: gnome-classic
        [main]  Kernel Info: 4.18.0-553.47.1.el8_10.x86_64
        [main] Running Environment:
        [main]  Distribution: openSUSE Tumbleweed
        [main]  Desktop Environment: Wayland KDE kwin 6.5.1
        [main]  Kernel Info: 6.17.6-1-default
        [main] Install Location: 
        [main]  /usr/local/vmrv2-v1.4.5-Linux-64
        [main] Preferences Location: 
        [main]  /home/myuser/.filmaura/
        [main] Temp Location: 
        [main]  /tmp
        [ocio] Setting OCIO config to default:
        [ocio]  ocio://default
        [pref] Loading hotkeys from "/home/myuser/.filmaura/mrv2.keys.prefs".
        [view] HDR monitor found.
        [view] Vulkan color space is VK_COLOR_SPACE_HDR10_ST2084_EXT
        [view] Vulkan format is VK_FORMAT_R16G16B16A16_UNORM
Failed to initialize vkSetHDRMetadataEXT - no HDR extension will be used.
GOT SIGNAL 11
Stack trace (most recent call first):
#0  0x0000000000b29661 in printStackTrace() at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#1  0x0000000000b29583 in mrv::signal_callback(int) at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#2  0x00007efcd564290f at /usr/lib64/libc.so.6
#3  0x00007efcbb1dc424 at /usr/lib64/libvulkan_radeon.so
#4  0x00007efcbb11c9ba at /usr/lib64/libvulkan_radeon.so
#5  0x0000000000974cb3 in tl::timeline_vlk::Render::begin(tl::math::Size2<int> const&, tl::timeline::RenderOptions const&) at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#6  0x00000000008f8db0 in mrv::vulkan::TimelineWidget::draw() at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#7  0x00007efcdd7412f1 in Fl_Vk_Window::flush() at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk_vk.so.1.5
#8  0x00007efcde352f05 in Fl_Wayland_Window_Driver::flush() at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#9  0x00007efcde2aaa41 in Fl::flush() at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#10 0x00007efcde354459 in Fl_Unix_System_Driver::wait(double) at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#11 0x00007efcde2aa81c in Fl::run() at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#12 0x00000000005bfdaf in main at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#13 0x00007efcd562b2fa in __libc_start_call_main at /usr/lib64/libc.so.6
#14 0x00007efcd562b3ca in __libc_start_main@GLIBC_2.2.5 at /usr/lib64/libc.so.6
#15 0x00000000005e094d in _start at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2

Openin a MKV file

> vmrv2
ERROR:  [lic.] "No valid license found for machine=293ef77dec0d45069ad30059ebd24e90"
        [main] mrv2 v1.4.5 Vulkan - Built Nov  5 2025 20:29:08 - Release
        [main] Set Language to en_US.UTF-8, Numbers to C
        [main] Build Environment:
        [main]  Distribution: Rocky Linux release 8.10 (Green Obsidian) 
        [main]  Desktop Environment: gnome-classic
        [main]  Kernel Info: 4.18.0-553.47.1.el8_10.x86_64
        [main] Running Environment:
        [main]  Distribution: openSUSE Tumbleweed
        [main]  Desktop Environment: Wayland KDE kwin 6.5.1
        [main]  Kernel Info: 6.17.6-1-default
        [main] Install Location: 
        [main]  /usr/local/vmrv2-v1.4.5-Linux-64
        [main] Preferences Location: 
        [main]  /home/myuser/.filmaura/
        [main] Temp Location: 
        [main]  /tmp
        [ocio] Setting OCIO config to default:
        [ocio]  ocio://default
        [pref] Loading hotkeys from "/home/myuser/.filmaura/mrv2.keys.prefs".
        [view] HDR monitor found.
        [view] Vulkan color space is VK_COLOR_SPACE_HDR10_ST2084_EXT
        [view] Vulkan format is VK_FORMAT_R16G16B16A16_UNORM
Failed to initialize vkSetHDRMetadataEXT - no HDR extension will be used.
GOT SIGNAL 11
Stack trace (most recent call first):
#0  0x0000000000b29661 in printStackTrace() at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#1  0x0000000000b29583 in mrv::signal_callback(int) at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#2  0x00007f23a904290f at /usr/lib64/libc.so.6
#3  0x00007f23931dc424 at /usr/lib64/libvulkan_radeon.so
#4  0x00007f239311c9ba at /usr/lib64/libvulkan_radeon.so
#5  0x0000000000974cb3 in tl::timeline_vlk::Render::begin(tl::math::Size2<int> const&, tl::timeline::RenderOptions const&) at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#6  0x00000000008f8db0 in mrv::vulkan::TimelineWidget::draw() at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#7  0x00007f23b11412f1 in Fl_Vk_Window::flush() at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk_vk.so.1.5
#8  0x00007f23b1d52f05 in Fl_Wayland_Window_Driver::flush() at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#9  0x00007f23b1caaa41 in Fl::flush() at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#10 0x00007f23b1d544a6 in Fl_Unix_System_Driver::wait(double) at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#11 0x00007f23b1caa86c in Fl::check() at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#12 0x0000000000b29394 in mrv::wait::milliseconds(float) at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#13 0x00000000009cf9c4 in mrv::vulkan::TimelineViewport::resizeWindow() at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#14 0x00000000009d2ee4 in mrv::vulkan::TimelineViewport::currentVideoCallback(std::vector<tl::timeline::VideoData, std::allocator<tl::timeline::VideoData> > const&) at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#15 0x0000000000e58bb0 in tl::timeline::Player::tick() at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#16 0x000000000081e46f in mrv::TimelinePlayer::timerEvent_cb(void*) at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#17 0x00007f23b1d1c74d in Fl_Timeout::do_timeouts() at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#18 0x00007f23b1cfe5bf in Fl_System_Driver::wait(double) at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#19 0x00007f23b1d54444 in Fl_Unix_System_Driver::wait(double) at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#20 0x00007f23b1caa81c in Fl::run() at /usr/local/vmrv2-v1.4.5-Linux-64/lib/libfltk.so.1.5
#21 0x00000000005bfdaf in main at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2
#22 0x00007f23a902b2fa in __libc_start_call_main at /usr/lib64/libc.so.6
#23 0x00007f23a902b3ca in __libc_start_main@GLIBC_2.2.5 at /usr/lib64/libc.so.6
#24 0x00000000005e094d in _start at /usr/local/vmrv2-v1.4.5-Linux-64/bin/vmrv2

MRV2

In the OpenGL version, floating panels, when they extend beyond the main window, don't allow the usual mouse pointer operations: the pointer changes to the one for "resizing the window" and so the green and red buttons become unreachable.

I believe the interface has become less intuitive. With the old version, I had no trouble inserting graphic elements (circles, arrows, ...) and in this version I haven't managed it. In fact, the "Demo" usage time has expired (something I didn't know would happen) and I haven't succeeded.

Moreover, it is highly unusual for the key to close the application; I think that's a major mistake.

Finally, something that strikes me and worries me regarding security. After doing an upgrade or downgrade, it downloads the corresponding RPM. So far, so good. However, it is not right that it asks for the root password to proceed with the installation. The proper thing would be to ask where to perform the download and let the user carry out the installation. I understand you do it this way because that's how the Windows version works, but it is not the appropriate approach for security reasons.

[ggarra13]

Thanks for the feedback!

Here's my comments:

VMRV2:

In your log, you have:

Failed to initialize vkSetHDRMetadataEXT - no HDR extension will be used.

This extension is the one that allows HDR, so without it, you might as well just use the OpenGL version.
This points to a serious problem in your Vulkan installation or to really outdated Vulkan drivers for your card. I've checked and it seems the Radeon drivers are still not HDR ready.
Try starting VMRV2 with:

$ FLTK_BACKEND=x11 vmrv2

to run it under XWayland instead of Wayland and see if that also crashes.

The difference in the logs between AVI and MKV is just due the different size of your videos, with one fitting inside your monitor, while the other having to be rescaled.

MRV2

In the OpenGL version, floating panels, when they extend beyond the main window, don't allow the usual mouse pointer operations: the pointer changes to the one for "resizing the window" and so the green and red buttons become unreachable.

This is likely a bug in the Wayland implementation of the panels. Will look into it.

With the old version, I had no trouble inserting graphic elements (circles, arrows, ...) and in this version I haven't managed it.

That's because the demo/donationware version (ie. from v1.4.1 on) turns off the action tools except for scrubbing. If you become a beta tester (I have your machine id now, so I can register you if you want), you will have access to: Action Tools, Drawing, NDI, and OpenEXR Layers and no expiration time all of which are turned off in the donationware version.

[ggarra13]

In the OpenGL version, floating panels, when they extend beyond the main window, don't allow the usual mouse pointer operations: the pointer changes to the one for "resizing the window" and so the green and red buttons become unreachable.

I cannot reproduce this with v1.4.5 OpenGL on my Ubuntu 25.04 box. Can you create a small screengrab movie showing the issue?

[RafaelLinux]

Videocaptura.de.pantalla_20251108_054829.webm

[ggarra13]

I see. It is a bug in Kwin I am afraid. Here's what happens in GNOME 48:

Grabacion.de.pantalla.desde.2025-11-08.04-24-09.webm

[RafaelLinux]

But I use applications having floating panels under Wayland and all them manage correctly panels outside main window.

[ggarra13]

But I use applications having floating panels under Wayland and all them manage correctly panels outside main window.

If that's the case, you have a point. However, most likely they are all Qt applications or X11 applications running under XWayland. So there's something in FLTK that is not setting under Kwin. I'll raise the issue with FLTK's Wayland expert.

[ggarra13]

Can you try if panels work fine under XWayland? Run:

FLTK_BACKEND=x11 mrv2

[ggarra13]

Here's the response from FLTK's Wayland guy.

That is a "feature" of how KWin, plasma's Wayland compositor, decorates its windows. KWin sends no event to the client app when a subwindow extends outside from its parent and the pointer enters that part of the subwindow. Therefore FLTK is completely unaware that the user attempts to drag the subwindow. The same occurs when the cursor enters the window titlebar: the client receives no event from the compositor; everything happens inside the compositor process, out of reach fom the Wayland client process.

That is very visible when the app is run with WAYLAND_DEBUG=1. Place the subwindow half outside and half above the main window. When the cursor enters the subwindow part above the main window, Wayland sends information to the client. When the cursor is moved away and then made to enter the subwindow part outside the main window, nothing is sent by the compositor to the client who remains unaware of what's happening on the display.

One way out of this: run the app with environment variable LIBDECOR_FORCE_CSD=1. This forces KWin to decorate its windows with libdecor, and subwindows can be dragged anywhere.

[RafaelLinux]

Can you try if panels work fine under XWayland? Run:

FLTK_BACKEND=x11 mrv2

Yes, it fixes the issue!!! ;)