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

OSX Reaktor is sick?

Discussion in 'REAKTOR' started by claudek, Jun 19, 2003.

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

    burgessa23 NI Product Owner

    Messages:
    73
    is the issue still happeneing, I just had to re-format my desktop for other issues and now r4 won't run standalone.

    I'm going to try the first 2 lines thing tonight

    any other tips??

    -andrw
     
  2. claudek

    claudek Forum Member

    Messages:
    896
    PANTHER GM

    Panther is being worked on as we speak.."DP"..Developer Preview is where it is now..
    Meaning a preview for software companies like NI,Motu etc...... so programmers can be working on new drivers ,updates etc to work with it (at least supposed to be testing and developing on the DP of 10.3)..So don't start the crying until the GM is shipped..
    I know so many changes and my fear is next update of 4.03 may be ok..but then Panther will screw it up..Will it ever work right??
     
  3. claudek

    claudek Forum Member

    Messages:
    896
    Weird but good news

    I do not know what happened but now when I open my audio/midi settings in 4.02 all is acting normal..Cannot complain..weird..keep my fingers crossed..Seems ever since I ran the midi pipe app, it has worked..but maybe coincidental.
     
  4. burgessa23

    burgessa23 NI Product Owner

    Messages:
    73
    I still can't run in standalone

    here's a log file exerpt:

    Date/Time: 2003-07-17 08:09:29 -0700
    OS Version: 10.2.6 (Build 6L60)
    Host: Andrew-Burgesss-Computer.local.

    Command: Reaktor 4
    PID: 500

    Exception: EXC_BAD_ACCESS (0x0001)
    Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

    Thread 0 Crashed:
    #0 0x9068ba54 in objc_msgSend
    #1 0x90131f64 in CFRelease
    #2 0x003ce8a8 in MacOSXMidi::getInPortName(char*, long)
    #3 0x003cdc5c in MacOSXMidi::getPortDescription(void*, long*)
    #4 0x003cd9cc in MacOSXMidi::getProperty(char const*, void*, long*)
    #5 0x003c4698 in NSAudioEngine::getDeviceProperty(char const*, long, void*, long*)
    #6 0x003c3b64 in NSAGetDeviceProperty
    #7 0x0038a22c in NI::AB::InterfaceNSA::getNumPorts(long, bool)
    #8 0x0038ac04 in NI::AB::ImpNSAMidiForm::updateLists()
    #9 0x0038aa08 in NI::AB::ImpNSAMidiForm::setData()
    #10 0x0038c200 in NI::AB::ImpNSASetupDialog::doDialog(NI::UIA::Dialog::CreateData const&)
    #11 0x00385af0 in NI::AB::ImpNSA::eek:penDefaultConfigurationDialog(NI::UIA::WindowBase*)
    #12 0x0027e204 in TReaktor::Init()
    #13 0x001d2f28 in ReaktorApp::init()
    #14 0x003d1c40 in NI::UIA::AppModule::attachApplication(NI::UIA::Application*)
    #15 0x001d2b50 in MainModule::init()
    #16 0x003d1b64 in NI::UIA::AppModule::create()
    #17 0x003d1fb8 in NI::UIA::DETAIL::AppModuleStartup::init()
    #18 0x003d1f5c in NI::UIA::DETAIL::AppModuleStartup::run()
    #19 0x001c974c in main
    #20 0x000044a4 in _start
    #21 0x00004324 in start



    any ideas???


    -andrew
     
  5. claudek

    claudek Forum Member

    Messages:
    896
    You had a kernal panic..
    This is not a good thing..
    Exception: EXC_BAD_ACCESS (0x0001)
    Codes: KERN_PROTECTION_FAIL
    URE (0x0002) at 0x00000000
    Did you register your R4?
     
  6. burgessa23

    burgessa23 NI Product Owner

    Messages:
    73
    yes, it's registered and fully legal

    I emailed support, this morning.


    we shall see, at least it works as an AU


    -andrew
     
  7. claudek

    claudek Forum Member

    Messages:
    896
    Spoke to soon

    I noticed pops and cracks in the audio from time to time as standalone..even as Au sometimes..Then I noticed today 3 system freezes, which happen only while running Reaktor..
     
Thread Status:
Not open for further replies.