1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

reaktor + protools = crash + no help from NI

Discussion in 'REAKTOR' started by stabba, Jan 8, 2004.

Thread Status:
Not open for further replies.
  1. stabba

    stabba NI Product Owner

    Messages:
    3
    PLEASE HELP!!

    anytime i attempt to open reaktor 4 as a plugin in protools 6.2.2 under mac os x (10.3) on my g5 dual 2ghz, it results in an immediate crash of protools - even under the most simplified conditions. the native instruments support team hasn't responded in almost a month now - maybe someone here knows a solution?

    - cp -
     
  2. John Nowak

    John Nowak Account Suspended

    Messages:
    3,493
    I think it would be more like:

    ((((reaktor + protools) && crash) && no help from NI) == Anger ) = TRUE

    I mean let's face it, the crashing and the lack of communication are not involved in any cause/effect relationship!

    That being said, NI is working on getting Reaktor to work better with Protools. I know its probably very annoying for you, but making a complex program like Reaktor work as a plugin is especially difficult, and frustrating for the programmers as well as the users. They're making every effort to straight out plugin issues that they can.
     
  3. stabba

    stabba NI Product Owner

    Messages:
    3
    that still doesn't tell me anything.
     
  4. n311

    n311 New Member

    Messages:
    7
    I feel your pain and frustration. I'm having problems with DP4 in even getting it to recongnize the AU components so it just skips the loading of R4 completely. Oddly enough it loads FM7 and Absynth fine an without any crashes. Reaktor seems to run fine as a stand alone but that's not why I bought the program. So with all these problems that I'm hearing from other users. Are they all using it as a stand alone to avoid the crashes and other technical problems? How are others getting around this? Any suggestions? I'm all ears. Cheers and lets hope they fix this sometime soon.
     
  5. stabba

    stabba NI Product Owner

    Messages:
    3
    yeah, it works fine as a standalone for me too. thats great for building synths and samplers, but it takes away the ability to use it as an effects processor which is the main reason i bought it. native instruments claims that it's been extremely difficult to make reaktor work as a plug-in, yet they don't have any problem advertising it as one. its always a shame when potentially good software companies take shortcuts for the sake of profit. kontakt works great with protools... native instruments needs to get off their asses and deliver what they've already claimed to be true in reaktor. i understand that it may be difficult, but they've already pursueded us to buy their product under false pretenses and i say its time they fixed the problem. there are organizations available dedicated to dealing with unethical business tactics, but it shouldn't have to come to that. NI - we're waiting.

    -cp-
     
  6. linpaws

    linpaws NI Product Owner

    Messages:
    323
    Hello cp,
    I use PT and R4 as well. I understand how you feel, I felt the same when R4 came out without RTAS, and waiting for it took ages and made me feel mislead.
    In the end NI lived up to their promisses and now all works fine. *AHEM*
    It was worth the wait.

    Here are some suggestions for enjoying PT&R4 (while you wait for the update) anyhow:

    - If possible, work under 10.2.8, that is the config the NI promisses are based on.

    _ if you want to build effects yourself, it's better to do that in standalone mode, you can test your .ens by puting a sampler macro before your effect and load it with some audio region from PT.
     
Thread Status:
Not open for further replies.