Rendering in T is not as perfect as I thought

[DWS]

you can see that its not just being clipped off but breaks up before the end....

Wow. I'm not sure what I looking at exactly, but it's disturbing. - s

[P.T.]

Is this happening at the end of each note or just at the end of the rendered file?

[semiquaver]

each note.

[headquest]

Nobody has ever claimed that T's dither is perfick.

"the ultimate in bleeding-edge digital audio"

[headquest]

this is going to delay the release of t2 i bet

Erm, I doubt it Ron

[braj]

I don't see what good it would do to delay T2 for this It definitely needs to be fixed, but you need to open your audio in a wave editor to see it, or turn your speakers to11 to hear it. I think I can live with that.

[headquest]

I'm just happy that it really doesn't affect me, since my music is crap anyway. This is the least of my problems I personally never would have noticed if it weren't pointed out.

Hey braj, I thought that you bounced down your MIDI clips to audio (rather than use the limited Freeze function)? If so, then this very much DOES affect you, because EVERY track you bounce down is introducing error, and that error is being summed cumulatively, and then further error is being introduced at export...

I started a thread here several months ago about problems with Tracktion's audio rendering, which was largely ignored at the time. There have been others who have reported problems too. I have noticed throughout the last several months that there were "issues" because I always analyse audio using Audition's high-calibre scientific analysis tools within the mastering process, which I always carry out in Audition.

I have also noted (and raised in that thread) the fact that audio that appears not to clip in Tracktion actuallu does clip when analysed with greater precision.

To say that there is a problem here is basically an understatement, but like the MIDI note-drop, Rewire issues, etc etc, nothing has yet been done. I did think that the "improved metering" and 64-bit summing might help, though...

[semiquaver]

It needs fixing now - there is no way to get audio out of T without screwing it up. should I bring it out at 32 and dither it down? DSP Quattro - $149 (I'm on mac). aaarg

[diverdee]

it's a problem isn't it, how serious? - I don't know, but I do know that Jules the creator & beno the mackie guy have both been on the forum recently & neither have commented, which would have been nice y'know just a 'hmmmm... we'll look into that'.
Oh well, let's see...

[braj]

I don't render to audio that much actually, the reason it was discussed really had to do with the limited freeze functionality. And I never would have noticed this error had it hnot been pointed out. But I see your point. I still don't think they should wait to ship though, I'm certain a downloadable patch will suffice.

One question: did this exist in T1 or get introduced with T2?

[headquest]

One question: did this exist in T1 or get introduced with T2?

Like various *others* it was in T1. (Bear in mind I didn't get far enough with T2 demo to render anything ).

[braj]

it's a problem isn't it, how serious? - I don't know, but I do know that Jules the creator & beno the mackie guy have both been on the forum recently & neither have commented, which would have been nice y'know just a 'hmmmm... we'll look into that'.
Oh well, let's see...

Yeah, that would be nice to know, but maybe they're busy working on a fix.

My point is this: if they are already pressing CDs and putting them in little boxes to ship off to vendors, I'd rather they just notify all users of the patch when it's released instead of pulling everything back. If it isn't pressed yet, then sure they should fix it before shipping it off. I'm guessing you'd have at least a weeks delay if that's the case, if not much more.

I have to imagine this is something that they were testing for. I wonder how long this has been a known issue. Maybe it's an incredibly complicated fix.

[IIRs]

I wonder how long this has been a known issue.

About 24 hours..

I'm sure Jules can get it sorted.

[gavriloP]

This thing happens with normal exported audio too. With 24bit export it is constant low-level noise at somewhere near -78db and this is not so very hifi. So if you for example have rendered your pristine and dynamic acoustic instrument recordings with plenty of headroom and then boost that rendered audio, it becomes audible during very low level parts. Of course you won't hear it during loud music but in these very low-level parts it might be very real issue. And even though using 32bit rendering is very good workaround, it should be addressed to users. Someone will be quite frustrated when he finds out that his mellow and dynamic rendered recordings have these digital noises.

And BTW I myself don't know how to set render Track option to 32bit, so for me exporting is only option (and this is limiting).

Just think what some specs loving people will say about this, you know I might not be so pretty, and this is sad for me. During my extended honeymoon with Tracktion I have become so in love with this host, I want best for it (her?)

Ok, the lab closes for now(I got to do something creative with her for awhile).

Mikko

<EDIT> I was fooling too long with my sentences, discussion went on behind my back .

And BTW I am working with T1.

[braj]

I wonder how long this has been a known issue.

About 24 hours..

I'm sure Jules can get it sorted.

headquest indicated it was in T1, that's why I asked. I'm not trying to inflame the situation.