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

Forbid output update after EOS #833

Merged
merged 5 commits into from
Oct 21, 2024
Merged

Conversation

noituri
Copy link
Member

@noituri noituri commented Oct 18, 2024

Fixes #552

@noituri noituri requested a review from wkozyra95 October 18, 2024 09:57
@noituri noituri changed the title @noituri/fix render after eos Forbid output update after EOS Oct 18, 2024
@noituri noituri force-pushed the @noituri/fix-render-after-eos branch from 8d01d72 to 4802750 Compare October 19, 2024 12:50
@noituri noituri force-pushed the @noituri/fix-render-after-eos branch from 4802750 to cfcada4 Compare October 19, 2024 12:52
compositor_pipeline/src/pipeline.rs Outdated Show resolved Hide resolved
@noituri noituri enabled auto-merge (squash) October 21, 2024 10:02
@noituri noituri force-pushed the @noituri/fix-render-after-eos branch from c76bb6c to fca2060 Compare October 21, 2024 10:20
@noituri noituri force-pushed the @noituri/fix-render-after-eos branch from 233a705 to 7493837 Compare October 21, 2024 13:23
@noituri noituri merged commit abf9e95 into master Oct 21, 2024
4 checks passed
@noituri noituri deleted the @noituri/fix-render-after-eos branch October 21, 2024 13:38
@@ -123,7 +123,7 @@ pub fn offline_processing() -> Result<()> {
if !(1.9..=2.1).contains(&duration) {
return Err(anyhow!("Invalid duration: {}", duration));
}
if !(930_000..=1_000_000).contains(&bit_rate) {
if !(930_000..=1_008_200).contains(&bit_rate) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • if something changed in the compositor that affected this test then adjust lower bounds too.
  • if you are doing something like this make sure to communicate it clearly. You added that change after getting PR approved and I only noticed this by accident.

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

Successfully merging this pull request may close these issues.

Scene update after EOS should be ignored
2 participants