6.1.3 Not Responding

I’m having a lot of issues with v6.1.3 on a PC running Windows 10.

Mainly I’m having trouble getting previews to render. The computer flashes a message that the App is not responding. DioneDV is not working at all, but that might be the same issue.

[If you are posting a new bug, please include the following]

  1. The bug / behavior you have encountered
  2. Your system profile
  3. Your log files (Help > Logging > Get Logs for Support)
  4. Any screenshots as necessary

[Please be sure to have searched for your bug before posting. Duplicate posts will be removed.]

Here are the logs
logsForSupport.zip (7.4 MB)

Hi Andy,

Thanks for the logs. Can you try changing the audio mode to convert when you have prores selected? Alternatively, can you try changing the codec to h264 or h265 before running a preview and let me know if it works?

Wow, changing the audio to convert worked! These crazy bugs! So until this is fixed, if I need ProRes I should keep audio on convert?

Also, while I’ve got you, is it possible to scale the width and height independently? I’m dealing with some anamorphic footage that requires a de-squeeze from 4:3 to 16:9 and it looks like there’s no way to do that in Topaz. Is that correct?

Is the CFR Fixed on apollo when output puts out VFR frame rate instead of Constant?

I’m happy to test this but I don’t understand what you’re asking. Are you talking about encoding settings? BTW, switching Codec Settings to H264 did fix the preview issue as you recommended.

1 Like

This bug has been fixed for most inputs in 6.0.4, however, we are still seeing some rare cases with specific input clips where this is still happening.

1 Like

That’s great, yes I’d recommend keeping the audio mode to convert when using prores until this is resolved.

You won’t be able to scale the scale the width and height independently, however, using the “pixel type” to square pixel might be what you are looking for.

1 Like

When I put a progressive CFR 25fps and use any model and apollo for 29.97 the frame output will be like 30.000 VFR or the frames may vary, Like other users have stated this started happened after 5.3.6. I had issues in all 6.x.x versions thus far. But have yet to try this new update.

I remember in one of the first versions of 6 we had to click keep CFR then the next version it was removed assuming didn’t have to choose CFR anymore. And then everything was VFR.

Can you send an example of the original and exported video where this is still occurring? Yes the button was removed because it was fixed (in most cases, not all)

  1. The original input file
  2. the exported file with VFR

You can securely submit your file(s) to our Dropbox using the link below. Please be sure to send me a note to let me know you sent something and include the file name.
Submit File to Dropbox

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.