Despite being a very well thought tool, Composer has a main flaw that makes it unusable: rendering output (export feature) delivers innacurate results, such as extra samples rendering and main output bus asynchronism. At least in Nuendo v 11.0.41
@@SamHocking I don't know if Fiedler is aware. This occurred in the last project I worked on. The issue showed this way: First I rendered from within Composer (real time export) 3 different passes (stereo, binaural and 5.1 mono tracks). 5.1 tracks showed innacuracies compared to the other renders (a few extra samples past the 'out point', all tracks the same). Also, the stereo render had all the information 'moved' a few samples (this one didn't print extra samples), so that it lost sync with the original main output signal. I thought that maybe the issue was related to realtime rendering, as I noticed the computer was struggling during export process (cursor jumping in the project window). So I tried the same but this time from Nuendo's export window. It delivered inaccurate renders again (not exactly the same inconsistencies as before though). So after this, I turned off Composer and all the beams. Went back to Nuendo export window procedure and all went back to normal, no issues. So, if Nuendo's export works fine, I don't see any reason why Composer should fail, other than a problem within Composer.
Despite being a very well thought tool, Composer has a main flaw that makes it unusable: rendering output (export feature) delivers innacurate results, such as extra samples rendering and main output bus asynchronism. At least in Nuendo v 11.0.41
Hm, never ran into that issue. 🤔
Is this issue known by Fiedler? Is it happening for realtime and offline export or only one export type?
@@SamHocking I don't know if Fiedler is aware. This occurred in the last project I worked on. The issue showed this way: First I rendered from within Composer (real time export) 3 different passes (stereo, binaural and 5.1 mono tracks). 5.1 tracks showed innacuracies compared to the other renders (a few extra samples past the 'out point', all tracks the same). Also, the stereo render had all the information 'moved' a few samples (this one didn't print extra samples), so that it lost sync with the original main output signal.
I thought that maybe the issue was related to realtime rendering, as I noticed the computer was struggling during export process (cursor jumping in the project window). So I tried the same but this time from Nuendo's export window. It delivered inaccurate renders again (not exactly the same inconsistencies as before though).
So after this, I turned off Composer and all the beams. Went back to Nuendo export window procedure and all went back to normal, no issues.
So, if Nuendo's export works fine, I don't see any reason why Composer should fail, other than a problem within Composer.
@@michaelgwagner It could be a problem related to my PC, I can't rule that out.
Anyway, It could be a problem related to my PC, I can't rule that out.