-
Notifications
You must be signed in to change notification settings - Fork 10
Improve Player File Callback Handling #83
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -485,7 +485,6 @@ FileExportScreen::FileExportScreen(MainEditor& editor, | |
| return; | ||
| } | ||
| config.setManualExport(!config.getManualExport()); | ||
| repository_->update(config); | ||
| if (config.getManualExport()) { | ||
| startTimer_.setEnabled(false); | ||
| endTimer_.setEnabled(false); | ||
|
|
@@ -501,7 +500,7 @@ FileExportScreen::FileExportScreen(MainEditor& editor, | |
| exportVideoFolder_.setEnabled(false); | ||
| browseVideoButton_.setEnabled(false); | ||
| browseVideoSourceButton_.setEnabled(false); | ||
|
|
||
| config.setExportCompleted(false); | ||
| } else { | ||
| startTimer_.setEnabled(true); | ||
| endTimer_.setEnabled(true); | ||
|
|
@@ -517,15 +516,9 @@ FileExportScreen::FileExportScreen(MainEditor& editor, | |
| exportVideoFolder_.setEnabled(true); | ||
| browseVideoButton_.setEnabled(true); | ||
| browseVideoSourceButton_.setEnabled(true); | ||
|
|
||
| if (!config.getExportCompleted()) { | ||
|
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I removed this to be consistent with how we update the
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is specifically needed for Premiere Pro. It looks like this change may be fine, but it should be tested on Premiere Pro to verify that it's okay to just update to true without checking the exportCompleted flag has been set. |
||
| // Normally this is handled by the file export processor | ||
| // But in manual button cases where the processor is destroyed we need | ||
| // to flag it here | ||
| config.setExportCompleted(true); | ||
| repository_->update(config); | ||
| } | ||
| config.setExportCompleted(true); | ||
| } | ||
| repository_->update(config); | ||
| repaint(); | ||
| }; | ||
| LOG_ANALYTICS(RendererProcessor::instanceId_, "FileExportScreen initiated."); | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand how this is checking for a "new" file. Do you mean an empty file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the path to the given output file does not exist, export must be to a new file not rewriting an existing file.
How would an empty iamf file exist here besides maybe a crash during export?