T2 - Wave-Wave Render Problem

[IndiQa]

I have found that when I render a T2 project to a single wave file that the output (wav file) sounds off...way off.

I have 3 wave tracks which are set up in T in 3 tracks. These tracks have various processing functions applied to them. Reverb/EQ etc.

The output is still messed up no matter what processing I use or if I use NO processing. Just render the 3 tracks to one.

The levels are reduced, there is a pulsing "hiss" type noise. And just general degradation of the audio. I have checked the rendered audio in both SoundForge 8 and Audition. Same problem.

Playing the project inside T2 sounds exactly the way I want it to. No problems.

The input waves are 24/96 and the output wave is set to render to 24/96. Also tried rendering down to 16/44 same thing. The input waves are clean and nice so it's not a matter of garbage in/garbage out.

Recording a project using VSTis only with effects and such then rendering has no problems what so ever.

Am I missing something here?

btw This happened in both 2.0.13 and the newest update.

Scratching my head and nether parts over this here.

Thanks,

Curt

[aMUSEd]

I washoping rendering was fixed but couldn't see it in the list of fixes and it sounds like not. I've had lots of problems with renders being gappy or having bits missing/off.

[audiobot202]

It's an ongoing issue with Tracktion I have found. There are some VSTs it does not like and while they play fine, they do not render correctly. For example, the Superwave P8 with Chordworx in front is a problem for me...the rendered notes bleed into one another.
I just use a recorder like Tapeit on the masyer output to record exactly what plays. Shouldn't have to I know, but it's a useful workaround and the renders sound great.
I don't know when any of it will be fixed, but Tracktion does not play nice with certain combinations of VSt fx and instruments on bounce down or render. It remains a very annoying problem. How do I explain to my friend who is just getting into it that he'll have to use Tapeit to record because T2 doesn't like Superwave8 or more than one instance of JX10 ? Why can Ableton Live render instruments well every single time where Tracktion just fails? 'tis a mystery for sure...

[ModuLR]

It remains a very annoying problem. How do I explain to my friend who is just getting into it that he'll have to use Tapeit to record because T2 doesn't like Superwave8 or more than one instance of JX10 ? Why can Ableton Live render instruments well every single time where Tracktion just fails? 'tis a mystery for sure...

http://www.ableton.com/forum/viewtopic. ... ght=render

I'm sure it's just as odd for these Live 5.0.2 users with rendering problems who might have to suggest Tapeit. There are always two sides to a coin, software is just not that simple.

[audiobot202]

Indeed not. Of course, I was only speaking from my own experience. Very few problems with Live, more problems with Tracktion in the same area.
It is refreshing though to see the other side of the coin

[IndiQa]

Many thanks to all for showing me my sanity (at least in this instance) is intact. I knew I read some time back about some render problems but wasn't sure if it related here.

Again many thanks and I will join you in pounding on RMS and Mackies door to CORRECT THIS PEOPLE !!

Curt
(aka IndiQa)

[mandolarian]

Hey, Curt, could you list the specific VSTs used in each track. Us simpletons could try to duplicate the issue using our complex software.

Did you try disabling a single VST at a time until T renders correctly?

[Lunch Money]

<shrug>

The render bug that was fixed was related to a different problem. I never said there couldn't be new ones.

I've never had a render problem, even when it WAS a "bug". I just never noticed that my reverb tails were turning to noise at -90dB. Sometimes I set -90dB as my silence threshold for trimming silence at the beginnings and ends. <grin>

Not sure about this latest one... without knowing the exact plug-ins and a clearer vision of what's going on (not that you weren't clear... just that I'm not quite following... my concentration has been crap lately) I can't replicate and confirm/deny. FWIW, if there IS a bug, I'd rather know that it's a bug so that it can get sorted... it's not like I'm saying that just because I don't notice it, it doesn't exist.

Greg

[IndiQa]

Hey, Curt, could you list the specific VSTs used in each track. Us simpletons could try to duplicate the issue using our complex software.

Did you try disabling a single VST at a time until T renders correctly?

I tried it with and without any VSTs at all. Same results.

Just 3 wav tracks that I tried to render to one.

I will have to say that the TapeIt plug in works fine...Like T ought too.

Curt

[Lunch Money]

Your project is 3 audio tracks.

When you render the entire project (ie. the 3 audio tracks), the resultant file is hissy and the levels get screwed.

If you play the project, it sounds fine. If you put TapeIt on the master bus and record it, the resultant file is fine.

Is that correct? I'm sure you've stated it fine, but as I mentioned, I'm having concentration issues, so I'm just trying to be perfectly clear what's going on before I try to replicate.

[IndiQa]

LM Thats correct. And I also am familiar with "concentration" issues
As I said if the piece is ALL done using VSTis and whatever effects I need (VST) the renders have always been fine. Excepting the FinalMix problem a while back. Which with the newest release of FM is now fine. Thanks to RMS and Mackie/Loud Tech.

Oh just for the record my system is:
3.6GHz P4 Dual Core (560j)
1Gb Dual Channel Ram
Audigy 2 zs (24/96)
160 Gb HDD

Curt

[jplanet]

Just out of curiosity, try this, it was my workaround before they fixed the pdc render bug, which djsubject discovered:

- Select all three tracks
- Freeze them
- render and see if the problem is still there

[IIRs]

It seems to work ok here..