Tracktion Software

D-Fusion · Post by **D-Fusion** » Fri May 27, 2005 10:56 am

Madness wrote:This thread allready has over 300 viewings.

There is obviously alot of people who are waiting on bugfixes before jumping on the T2 bandwagon.

Myself included...

Yep

I will continue to use my T1 NFR until the bugs are fixed, when the bugs are gone i am going to purchase the T2 Boxed.....

slkkrq · Post by **slkkrq** » Fri May 27, 2005 3:18 pm

I have T2 on the way. I was planning on recording and mixing in T2 and rendering in T1. Is this a good plan?

semiquaver · Post by **semiquaver** » Fri May 27, 2005 3:22 pm

no, both versions renders are the same.

djsubject · Post by **djsubject** » Fri May 27, 2005 4:35 pm

This is being worked on!

& how much is T2 in japan?

Subject

markmann · Post by **markmann** » Fri May 27, 2005 6:00 pm

Although I'm also frustrated that the render function doesn't work, T2 will "work" on a Mac if you use AudioHijack Pro to capture Tracktion's output at 24/96. I'd still like to have 32 bit renders available for archiving. Also, I haven't noticed any problems when I rendered one track at 32/96. I did notice that a render of an entire mix did not read the track automation correctly. So that's another issue they should be looking at as they fix this problem.

Mark Schleunes

Mr. Tingle · Post by **Mr. Tingle** » Fri May 27, 2005 6:10 pm

If T2 renders the same as T1 then this thread (and all like it) are a total load of PANTS!

I've been recording and rendering final projects for clients and my own work for a number of years with T1 and have got fantastic results.

This is just a red herring audiophile thread that has no useful purpose than to detract from T's excellent rep.

Mr. Tingle · Post by **Mr. Tingle** » Fri May 27, 2005 6:14 pm

The export function sometimes miss automation tracks, now that IS a problem worth talking about...

fake_fake · Post by **fake_fake** » Fri May 27, 2005 7:30 pm

I don't know what pants means... but it is very obvious to me. I have a track that doesn't have thick instrumentation, just a few sparse tracks, and I use reverb to provide a full pad like atmosphere... in the exported clip that full pad sound is stunted and rather than sounding like a big bushy tree it sounds closer to a stump.

Sure a passive listener wouldn't hear the difference, but that is why it sucks, because you can 'feel' the difference. One sounds beautiful and full, the other sounds the same except sounds boring. So it makes the track suck.

Maybe that's what the slogan in the video was about, if your music sucks it sucks because tracktion butchers it?

Windows has tapeit and voxengo recorder for free, neither of which has syncronization so exporting multiple files of identical length is very difficult without purchasing other software.

diverdee · Post by **diverdee** » Fri May 27, 2005 7:53 pm

fake_fake - just ignore people who say things like 'your problem is pants', they obviously aren't working with the same kind of material you are.
anyone who works with very sparse tracks, plenty of dynamics & space for reverbs etc. such as yourself will notice this problem, it is a problem - it is recognized that it exists & hopefully mackie/jules are working on it.
Let's just hope it isn't something deep seated in the code, like the various problems which seem to have some relation to the way tracktion handles graphics.

Mr. Tingle · Post by **Mr. Tingle** » Fri May 27, 2005 8:59 pm

Its been in Tracktion for 2 years or more, obviously its really noticable

Mr. Tingle · Post by **Mr. Tingle** » Fri May 27, 2005 9:10 pm

This thread is an insult to T as it gives a false impression.

Fact.

Joenco · Post by **Joenco** » Fri May 27, 2005 9:32 pm

Hey Tingle,

Do you mean no one noticed this before?
I hope this render problem will be fixed yesterday.
A host without render is like a pub without beer.

Joenco,

Mr. Tingle · Post by **Mr. Tingle** » Fri May 27, 2005 9:43 pm

There is nothing wrong with render. Use it.

gavriloP · Post by **gavriloP** » Fri May 27, 2005 9:54 pm

It was spotted before but "proven" only recently. It depends on material will it be noticeable, and if you don't increase the volume of rendered audio it isn't audible (for most of us, I think). But the fact remains that it makes Tracktion's 24bit output dynamic range worse than 16bit, maybe to 15bit or even less (at about -60db the noise began and it was muted at somewhere near -80db). But if you use 32bit rendering (you can only select if from export) this same trouble happens at so low levels it takes some inhuman creature to notice it. I can happily live with T1 now that I know this thing and use 32bit export. But it should be fixed because it is potentially pretty bad publicity.

-Mikko

Lunch Money · Post by **Lunch Money** » Fri May 27, 2005 9:56 pm

Agreed. It's one of those bits of exaggerated information... funny how everyone's been rendering with T for 2 years and it wasn't until one person notice that there's a 'problem', but as soon as it was pointed out, all of the sudden people are acting like it's a deal breaker or that the program is crippled.

Render your tracks. Enjoy your sequencer.

Greg

Tracktion Software

KVR Audio

Broken Render