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

[Feature Request] RGB Vectorscope #979

Closed
ItsJustTee opened this issue May 27, 2019 · 6 comments
Closed

[Feature Request] RGB Vectorscope #979

ItsJustTee opened this issue May 27, 2019 · 6 comments
Labels
Legacy (Unsupported) Issue pertains to version 0.1 which is no longer supported Medium Priority

Comments

@ItsJustTee
Copy link

Is your feature request related to a problem? Please describe.
Sometimes we never know how RGB Correct our videos are and thats where this feature comes in

Describe the solution you'd like
This feature allows the user to monitor the RGB of the video and therefor using Effects to correctly balance the colors of the video to perfection.

Describe alternatives you've considered
Now you could go and use the Project Monitor to look at the colors but this should be useful

Do you know any libraries or sources that can help the Olive Team include the feature?
None that i know

Additional context
This is what a RGB Vectorscope looks like :
rgb

@sobotka
Copy link
Collaborator

sobotka commented May 27, 2019

  1. This isn’t a vectorscope. This is a waveform.
  2. Vectorscopes are extremely challenging to handle properly in a managed pipeline.
  3. “Balancing” is also a little tricky, given that proper pixel handling on your input imagery, from something such as a GH5, an X-T3, an A6500 etc. is handled via the proper colour transform at ingestion.

It’s a kettle of fish to handle properly and correctly.

RGB waveform is the easiest target here. The rest require a little more flexible development and options.

@ItsJustTee
Copy link
Author

Alright Understood

@davej453
Copy link

davej453 commented May 27, 2019 via email

@sobotka
Copy link
Collaborator

sobotka commented May 27, 2019

Go to B&H and buy an RGB Parade monitor. Or would you be buying a waveform monitor? Or wait, is a waveform capable of displaying both RGB and luma off the SDI and displaying it as a literal waveform? Asking for a friend.

Kdenlive currently has the main ones implemented. Could this be used as a
source for something in Olive?

Wait, you come to correct a post that a waveform isn’t a waveform, then you barf up KDEnlive with no pixel management at all. 🤯

@davej453
Copy link

davej453 commented May 28, 2019 via email

@sobotka
Copy link
Collaborator

sobotka commented May 28, 2019

Please do go on...

I’d be very interested in the software you are using that you handled your colour appropriately the whole pixel chain, and as such, could rely on your waveforms.

Also, nice work on avoiding the answer “They are rendered as waveforms, hence they are a waveform.” It makes your sealioning all the more relevant. Also thanks for the education that different waveform modes have different purposes. What else would you like to teach the ignorant masses? Do go on...

@olive-editor olive-editor locked as off-topic and limited conversation to collaborators May 28, 2019
@olive-editor olive-editor unlocked this conversation May 28, 2019
@olive-editor olive-editor locked as off-topic and limited conversation to collaborators May 28, 2019
@itsmattkc itsmattkc added Legacy (Unsupported) Issue pertains to version 0.1 which is no longer supported and removed Core Infrastructure labels Sep 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Legacy (Unsupported) Issue pertains to version 0.1 which is no longer supported Medium Priority
Projects
None yet
Development

No branches or pull requests

4 participants