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

"scene range" doesnt show just the "scene range" #2

Open
lucianomunoz opened this issue Nov 4, 2022 · 2 comments
Open

"scene range" doesnt show just the "scene range" #2

lucianomunoz opened this issue Nov 4, 2022 · 2 comments

Comments

@lucianomunoz
Copy link

I've been making a video about your nice addon, and while testing the features this one which to me should be the default to set, doesnt seem to be working correctly:

image

as you can see the audio waveform shown goes beyond the scene range.

@Pullusb
Copy link
Owner

Pullusb commented Nov 5, 2022

Hi Luciano!

I cannot reproduce the bug. But as long as the sound is still synchronized (is that the case ?) it's not a big deal for me ;)
This might be related to the source. What is the file type and format ? How long is it ?
This might affect the wave creation in some ways (you can try re-encoding the source and see if the behavior is still the same)

About default settings
I agree that scene range should be the default target for most people.
It's on selected strips because I made this first for integration in a studio pipeline where everything is shot based.
In our pipeline at ADV studio, we have a voice strip separated from the music strip in the shot sequencer.
So upon auto-building, we would select only the voice one to have clear wave display for lip-sync.

Now that the addon is more and more used elsewhere, I'll think about changing that to scene range if I can adapt things at the studio, but no time to work on that at the moment...

Unrelated, but I see that you have the waveform it in white color, is it intentional ?
I know that selecting a highly bright or dark color gives white (can't do anything about it ^^)

@lucianomunoz
Copy link
Author

lucianomunoz commented Nov 14, 2022

That makes total sense, I'll give you some extra details on the bug whe it appears again, thanks for clarifying and looking into it!

I was just playing with the colons and ended up there

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

No branches or pull requests

2 participants