MAJOR rendering problems with Kontakt 2 and absynth 3

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I'm exhausted after many hours of rendering a track with T1. Maybe some of you have some tips, but T1 still has some serious rendering issues which has to be adressed if it should be depended upon by professionals (I'm a semiprofessional)

I tried every thing I can think of: streaming samples using DFD (direct from disk), from ram, with and without fx, rendered at 1x speed, experimenting with latency time with kontakt AND tracktion. Rendering the whole track, and single tracks.

When exporting the whole edit as an audio file there seems to be some midi errors thrown in as well as the rendering errors, as bass notes are lagging, some are too long etc.

When trying to render a kontakt 2 rhodes part by itself, a lot of notes just cut off with a noticeable pop. The amount of notes that are cut of depends upon the tracktion latency, if I had very low latency almost all of the notes are cut, but raising the latence still doesn't make a useable render.

This problem really makes me consider a switch to logic. I save a lot of time working with a song in tracktion, but what does it matter when you can't render it? It's like MS Word without a printer function :help:

Considering how vital the rendering option is, it's important for Tracktion to sort this out in order for it to be usable for professionals, or even semipros... Right now it's useless for me, but I hope it will be adressed, and for T1 as well as T2.
Think before you think before you speak

Post

OK, we're talking about a final mixdown, aren't we? It's not a solution, but I wouldn't give up T because of this issue - especially when you're saying yourself that T is a timesaver to you. As a quick workaround I would propose to test one of the write-to-disk plugins, e.g.

Silverspike: Tape It (also there's a much improved v2.0 payware available)
Tobybear: Channelgrabber
(argh, there's a third one I can't remember...)

Put one of these plugs into the master output area and record the output to disk.

HTH

J.

Post

I saw a similar issue with Pro-53 a long time ago, I never resolved it though (I dodn't try that hard). Couls this be something with NI's plugs somehow, I never saw it with anything else.
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new

Post

Pro-53 has actually worked flawless for me as far as rendering concerned. I solved my current project by using Audio Hijack.

It just feels so 'insecure' to use 3-party software to get a usable mixdown. Has there been any word that the rendering capabilities in T2 will be enhanced? :?: This should anyway be regarded as a bugfix, so it should be fixed in T1 also.

It MAY be a Native Instruments problem, but I also tested the plugs with cubase sx and it worked great. Also, I haven't seen any complains about this on the Native Instruments user forums...
Think before you think before you speak

Post

I have had lots of weird issues with Kontakt 1.5; it produced internal errors and corrupt edits so I had to reinstall at one stage.

Only working with Kontakt 2 for one week now but I think I have to agree with you that something is not right with the rendering. Hopefully Jules will look into it.

I was wondering if other Kontakt users have (had) similar experiences?

Post

frankvg wrote:I have had lots of weird issues with Kontakt 1.5; it produced internal errors and corrupt edits so I had to reinstall at one stage.

Only working with Kontakt 2 for one week now but I think I have to agree with you that something is not right with the rendering. Hopefully Jules will look into it.

I was wondering if other Kontakt users have (had) similar experiences?
I havent had ANY Kontakt related problems. But I'm still on 1.5.

You should post some of your system specs/OS ect. That might be useful. Good luck.
Image

Post

Good idea:
win XP home
p4, 3.2 gh, 1 gig ram
echo indigo

Good to know you havent't had problems with Kontakt. I was thinking perhaps it has to do with the dfd settings. Time to do some experimenting.

Post

I've experimented with dfd settings in kontakt 2, but it didn't work either way
Think before you think before you speak

Post

I have had some problems with Kontakt 1.5.3. I had the dropout problem, but changing the instrument in Kontakt from "DFD" to "Sampler" seems to cure this. Another thing that i haven't been able to fix is that when rendering a Kontakt part the first note is always louder than the rest.

I'm running WinXP Home SP1, Tracktion 1 (latest version), M-Audio Ozone USB soundcard, Acer Aspire laptop with an AMD Athlon XP 2200+ processor, 640 mb RAM.

Edit: it's 1.5.3, not 1.5.3, and some bad spelling
Last edited by cellular on Wed May 04, 2005 2:17 pm, edited 1 time in total.
Beautiful and strange electronic music: http://www.cellular.se

Post

I may also add that this doesn't just apply to the final mixdown, but to rendering or freezing single/multiple tracks. None of these approaches work for me.
Think before you think before you speak

Post

I've been using a similar system with echo indigo, p4 3.2ghz on a laptop with 512 ram. Absynth 3 has always been stable and renders without issue, but I do have the occasional problem reaktor session. I usually have to render the individual track while keeping the orginal and that has worked well so far. But I am having ongoing problems with reaktor session.

Post Reply

Return to “Tracktion”