Tracktion Software

aMUSEd · Post by **aMUSEd** » Tue Sep 06, 2005 5:31 pm

Well I brought up very similar problems with Reaktor 4 and Tracktion 1. They were fixed but maybe these apps all share some code or methods of communicating with the host that Tracktion doesn't like.

koolkeys · Post by **koolkeys** » Tue Sep 06, 2005 7:01 pm

This is a known problem with NI products. I have the same problems with Kontakt 2 and EWQLSO. And it used to be thought to be related to the DFD mode, but it's common no matter what. It's definately an NI issue. I don't think Tracktion is at fault here, really. I could be wrong. But I know it's been discussed a few times before, and I don't know if anyone ever got it sorted out. Sad, too, because there is some good stuff there and it's a hastle to do it with a workaround.

Koolkeys

ceenda · Post by **ceenda** » Tue Sep 06, 2005 7:04 pm

To be honest, I'm a bit worried about embarking on large GPO/EWQLSO orchestrations as I imagine that it begins to affect realtime playing at high CPU loads as well. Given that you don't have the option of freezing or rendering, it's a bit of a problem.

experimental.crow · Post by **experimental.crow** » Tue Sep 06, 2005 7:33 pm

koolkeys wrote:This is a known problem with NI products. I have the same problems with Kontakt 2 and EWQLSO. And it used to be thought to be related to the DFD mode, but it's common no matter what. It's definately an NI issue. I don't think Tracktion is at fault here, really. I could be wrong. But I know it's been discussed a few times before, and I don't know if anyone ever got it sorted out. Sad, too, because there is some good stuff there and it's a hastle to do it with a workaround.

Koolkeys

errm ...
never had this problem in FLS ...

never heard ew mention this problem in Sonar ...

i'm only hearing about this problem in tracktion ...

unless i've missed something ...
can you provide a link to this complaint in other hosts ?...

koolkeys · Post by **koolkeys** » Tue Sep 06, 2005 11:56 pm

I never said that it was a problem in other hosts. I even suggested that I could be wrong about it not being Tracktion. What I meant by saying that it's common to NI products, I meant INSIDE TRACKTION. That's where the complaints have been, in this forum. My ONLY reason to say it's not Tracktion is because in my mind, if it was a problem with Tracktion's rendering engine, it would happen with random synths, not just NI stuff. Obviously, SOMETHING is different in the NI stuff. Maybe it's something that Tracktion interprets differently than other hosts. For instance, with the first note missing bug, it was said that it's become common practice to code a certain way, and T tried to handle it properly, but it wasn't really Tracktion. It was just the way T handled it.

Same here. Whatever it is, I highly doubt that Jules will be able to find the problem without seeing the code for NI, or doing some serious investigating. This is because NI codes something differently than other plugs, or it would happen with others.

It would be easy to blame this totally on Tracktion, but it just can't be the case. I think it may be a combination. Yes, I'd like it fixed also. But to say that it's all Tracktion is being unfair without any real way of knowing. I believe it's been noted, and hopefully either Jules or NI will fix whatever is wrong.

Koolkeys

experimental.crow · Post by **experimental.crow** » Wed Sep 07, 2005 4:10 am

koolkeys wrote:I never said that it was a problem in other hosts. I even suggested that I could be wrong about it not being Tracktion. What I meant by saying that it's common to NI products, I meant INSIDE TRACKTION. That's where the complaints have been, in this forum. My ONLY reason to say it's not Tracktion is because in my mind, if it was a problem with Tracktion's rendering engine, it would happen with random synths, not just NI stuff. Obviously, SOMETHING is different in the NI stuff. Maybe it's something that Tracktion interprets differently than other hosts. For instance, with the first note missing bug, it was said that it's become common practice to code a certain way, and T tried to handle it properly, but it wasn't really Tracktion. It was just the way T handled it.

Same here. Whatever it is, I highly doubt that Jules will be able to find the problem without seeing the code for NI, or doing some serious investigating. This is because NI codes something differently than other plugs, or it would happen with others.

It would be easy to blame this totally on Tracktion, but it just can't be the case. I think it may be a combination. Yes, I'd like it fixed also. But to say that it's all Tracktion is being unfair without any real way of knowing. I believe it's been noted, and hopefully either Jules or NI will fix whatever is wrong.

Koolkeys

noted ...
i wasn't quite sure how to interpret your statement ...

couldn't agree more ...
it's a problem only co-operation will solve ...

and i'm not blaming anyone ...

as i've heard of this problem w/ absynth , kontakt , and battery ... it seems fairly evident that there is some core problem that NI and Mackie need to address ...

hopefully soon ...
it is in both their interests to do so ...

aMUSEd · Post by **aMUSEd** » Wed Sep 07, 2005 6:11 pm

normal wrote: it's a problem only co-operation will solve ...

and i'm not blaming anyone ...

as i've heard of this problem w/ absynth , kontakt , and battery ... it seems fairly evident that there is some core problem that NI and Mackie need to address ...

hopefully soon ...
it is in both their interests to do so ...

Agreed - which is why I have posted it on this forum and the NI forum. Now if only someone from Mackie would show some interest.....

aMUSEd · Post by **aMUSEd** » Thu Sep 08, 2005 6:13 pm

el bumpo

aMUSEd · Post by **aMUSEd** » Fri Sep 09, 2005 5:39 pm

Oh ffs. No wonder Mackie and NI can't resolve these problems if they can't even respond to their customers let alone talk to each other

SuitcaseOfLizards · Post by **SuitcaseOfLizards** » Fri Sep 09, 2005 8:17 pm

Have you tried to see if it works properly in eXT?

aMUSEd · Post by **aMUSEd** » Fri Sep 09, 2005 8:29 pm

Works properly in everything else. The problem seems to be the way Tracktion and certain NI plugins interact (or don't).

ceenda · Post by **ceenda** » Fri Sep 09, 2005 8:49 pm

On that note, have you tried running Absynth from inside eXT. Just the eXT VSTi with absynth inside?

Just wondered whether having it 'wrapped' in eXT made any difference?

I'm currently installing on a new PC, so I can't test that at the moment.

aMUSEd · Post by **aMUSEd** » Fri Sep 09, 2005 9:01 pm

Unfortunately the automation I recorded using Abs 3 doesn't work when it's wrapped in ExT so I can't really save my track or get a good comparison.

aMUSEd · Post by **aMUSEd** » Sat Sep 17, 2005 12:32 pm

Bump - still waiting for a response from Mackie or NI

pHz · Post by **pHz** » Thu Sep 22, 2005 9:08 pm

you posted on the mackie forum too ???

(no NI plugs at all here so i cant test)

slainte

rob

Tracktion Software

KVR Audio

Very annoying Absynth 3 rendering problem