Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vokoscreen freezes - build from source - GST_MESSAGE_ERROR #330

Open
4 tasks done
claudio4j opened this issue Sep 19, 2024 · 3 comments
Open
4 tasks done

vokoscreen freezes - build from source - GST_MESSAGE_ERROR #330

claudio4j opened this issue Sep 19, 2024 · 3 comments
Labels

Comments

@claudio4j
Copy link

Bug report checklist

  • Always send the vokoscreenNG log, after a "Start" and "Stop"
  • Have you searched the existing issues to see if this report is a duplicate?
  • Are you using the latest version of vokoscreenNG?
  • Are you familiar with https://www.mediawiki.org/wiki/How_to_report_a_bug ?

Cloned the git repo as of today to get access to the recently audio support.
Build successful.
My system:
Fedora 40, kernel 6.10.6-200.fc40.x86_64, KDE, wayland
2 monitors - main monitor from laptop, secondary monitor 4k via hdmi

Describe the bug
Trying to record a window open in the secondary monitor, click the "start" button, the countdown is displayed and the recording icon is displayed in the taskbar, then when I want to end the recording, I click the stop button, vokoscreenNG freezes, nothing happens, try clicking the close button from the vokoscreen window (top right corner) gives nothing, then kde window system asks to force kill vokoscreen.

Log messages
See attached.
vokoscreenNG-error.log

Additional context
If I set the target window to record in the monitor 1 (the monitor from the laptop) then it works, recording either the desktop or a selected window. I suspect the freeze is related to the 4k monitor, it has a different resolution compared to the monitor 1.

Using the monitor from the laptop is just ok.
Reporting here in case someone else has the same problem.

Thanks for providing such a great recording tool.

@vkohaupt
Copy link
Owner

To make sure that the high resolution is the cause, please make a recording without audio and without countdown and report here.

@claudio4j
Copy link
Author

claudio4j commented Sep 20, 2024

All tentatives are in the secondary 4K monitor.

. mic + countdown + window: QT apps (krusader, konsole app) = works
. no mic + countdown + window: QT apps (krusader, konsole app) = works
. no mic + no countdown + window: QT apps (krusader, konsole app) = works

I did more testing with these combinations
. mic + countdown + full screen
. mic + no countdown + full screen
. mic + no countdown + full screen + 17 frames/s
stops button works, video records is ok / audio is breaking up, no intelligible sound. Other tentatives, the audio is correctly recorded for ~30s, then mute, then recorded for a couple of seconds and then no audio. The video is ok. ~ 2 min recording time. Switched to mkv/VP8, same results.

. no mic + countdown + full screen = works
. no mic + no countdown + full screen = works

. mic + countdown + firefox window = as reported, click stop button, freezes and kill the process. The video file is zero bytes.
. no mic + countdown + firefox window = stops button works, no freeze. The video file is zero bytes.
. no mic + no countdown + firefox window = stops button works, no freeze. The video file is zero bytes.

The following logs are printed, even when it works:

(vokoscreenNG:2985146): GStreamer-CRITICAL **: 10:38:22.609: gst_value_collect_int_range: assertion 'collect_values[0].v_int < collect_values[1].v_int' failed
(vokoscreenNG:2985146): GStreamer-CRITICAL **: 10:38:22.609: range start is not smaller than end for `GstIntRange'

@claudio4j
Copy link
Author

I did some recording, with the full screen to the primary laptop screen + mic + countdown and have experienced mic audio not recorded for a random time, ranging from10s to 40s then it either resumed mic recording or finished recording with no audio, see attached voko-nomic.log.
Is there any additional debugging flags I can add to the build or running process to help diagnose this issue ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants