Bug 422931

Summary:	Visualisation Tools Levels plugin histogram should not be rendered
Product:	[Applications] kdenlive	Reporter:	gdiffey
Component:	User Interface & Miscellaneous	Assignee:	Jean-Baptiste Mardelle <jb>
Status:	RESOLVED NOT A BUG
Severity:	minor	CC:	fritzibaby, julius.kuenzel
Priority:	NOR	Flags:	fritzibaby: Backport+
Version First Reported In:	20.04.1
Target Milestone:	---
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description gdiffey 2020-06-13 18:15:20 UTC

SUMMARY

Plugins and effects that produce video output for information and correction purposes should have a way to draw output that's not in the main video window

I'm currently re-rendering a 2hr render at 4am  because I left the histogram's on when doing some level adjustments to clips and didn't realise they'd be in the output

I think that any tools that produce visual output should not be in final output unless confirmed or a option is ticked

It might be useful for tutorials but in general you never want the output to contain this video at all

STEPS TO REPRODUCE
1. Place a video on the timeline
2. add the levels plugin turn on the histogram
3. Render the video

OBSERVED RESULT

Video is rendered with the histogram in the output file.


EXPECTED RESULT

Video should not include histogram as it's a editing tool

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
Operating System: Debian GNU/Linux 
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.5
Kernel Version: 5.6.0-2-rt-amd64
OS Type: 64-bit
Processors: 4 × Intel® Core™ i3-4150 CPU @ 3.50GHz
Memory: 15.6 GiB of RAM


ADDITIONAL INFORMATION

Just a thought. but should these be moved to a different drawing surface  completely this might be an opportunity to further support lv2 plugins ui etc
(I'd really like to not have to take my audio to ardour just to get a fft scope and a nice ui on a parametric EQ)

Comment 1 emohr 2021-05-12 15:39:37 UTC

I can confirm. We shouldn't render scope effect until the user wants it to render.

Comment 2 Julius Künzel 2023-11-07 14:19:47 UTC

Thanks for your report!

I think the current behavior is fine. It is how effects work and the scope effects are still effects. If we add extra logic to keep it of by default, it just gets in-transparent and breaks the logic of "what you see is what you get".

I recommend you to also take a look at the scope widgets https://docs.kdenlive.org/de/tips_and_tricks/scopes/index.html which do not suffer from this problem.

Closing as won't change.