Forum Post

Re-Render export Error
Hi there,

I recently exported a number of Re-renders from a master file and found an issue with the created re-renders. The master file plays the section where the problem occurs without any problems so I think it's safe to assume the issue came from the exporting process.

The problem was consistent in all re-renders at this same section for roughly 100 seconds. There were a number of re-renders exported at once (7.1, 5.1, stereo as well DME stems for each format) and there were constant pops in audio on each channel of the re-renders.

Running Dolby v5.0.0 on a macOS Monterey v12.6

  • AdamP (Dolby Labs)

    Hi,

    Sorry to hear about this. Is this repeatable with the same master or did this only happen once? Were there any other applications open while the re-renders were being exported? Can you zip up and send the logs so we can see if there are any errors? Were the re-renders multi-mono or interleaved files? If this is repeatable would you be able to share the master file?

    Thanks,
    Adam
    Expand Post
  • I've been having the same issue but with the latest Renderer. This has happened with the external and internal Renderer
    Running Dolby v5.2 on a macOS Ventura v13.6 PT 20223.12
  • AdamP (Dolby Labs)

    Hi,

    Thanks for letting us know. Same questions as above and some additional ones:

    Is this repeatable with the same master and/or across multiple masters?
    Were there any other applications open while the re-renders were being exported?
    What are the specs of the workstation?
    Can you zip up and send the logs so we can see if there are any errors?
    Were the re-renders multi-mono or interleaved files? If this is repeatable would you be able to share the master file?
    Are these re-renders using all beds/object or custom re-renders with groups? Standard groups or use defined? If custom can you share a screen grab of the input configuration and re-render ?
    Also what is being used to playback the re-render? Are these being imported into the DAW? Into session/projects with the same sample rate, bit depth etc?
    Are these pops as reported by the other user or dropouts?

    Sorry for all the questions but providing as many details as possible will help narrow this down.

    Best,
    Adam
    Expand Post
    • Would it be possible to do a team viewer to expedite this process? Seems more efficient .
    • Is this repeatable with the same master and/or across multiple masters? *Yes, *

      Were there any other applications open while the re-renders were being
      exported? *Chrome Browser*

      What are the specs of the workstation? *Ultimate Pro Tools Ultimate, MTRX*,

      Can you zip up and send the logs so we can see if there are any errors? *How
      do I access the logs?*

      Were the re-renders multi-mono or interleaved files? If this is repeatable
      would you be able to share the master file? *Re-Renders were interleaved,
      but I tried multi-mono as well for good measure and the same issue
      happened.*

      Are these re-renders using all beds/object or custom re-renders with
      groups? Standard groups or use defined? If custom can you share a screen
      grab of the input configuration and re-render ?* They are you using custom
      -Re-renders with objects/beds/Said group selected. *

      Also what is being used to playback the re-render? Are these being imported
      into the DAW? Into session/projects with the same sample rate, bit depth
      etc?* Offline bouncing the re-renders and importing them back into session
      after bounce. 24bit 48Khz *

      Are these pops as reported by the other user or dropouts? *They are drop
      outs + click and pops*
      Expand Post
  • AdamP (Dolby Labs)

    Hi,

    Not at this point. Answers and the logs would be a better place to start in determining how to proceed. An additional one. Has this issue only surfaced after upgrading to v5.2 did this happen with previous versions? If so, which versions?

    Thanks,
    Adam
    • Ok, thanks for the clarification. I will be able to give this attention tomorrow. Thanks again
    • Also adding that this issue only happened with the 2023.12 update in both the internal/external issue and with the v5 and v5.2 versions of the Dolby Renderer. When I install the 2023.9 the offline bounces seem to work fine.
  • AdamP (Dolby Labs)

    Thanks. The logs are accessible from the Renderer v5.2 menu bar "help" dropdown.
10 of 17