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

KORE 1.0.2 bug list

Discussion in 'Technical Issues' started by silikon, Jul 21, 2006.

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

    silikon NI Product Owner

    Messages:
    6
    All,

    Just downloaded the 1.0.2 Kore update, along with the 1.7.0 driver update, and I'm still getting crashes when Kore starts up. In the interest of better illumination, I cleared out the kore.crash.log, and re-ran the plugin scan. Each time a crash occured, I moved the log out and saved it off.

    What's the quickest way to find out if the plugin is Carbon based, or Mach-O based? Tried looking at the various .plist files, found nothing useful, ran a strings against the plug itself... Nothing.

    I've included the log files (one for each crash)...

    Thanks for everything!
     

    Attached Files:

  2. silikon

    silikon NI Product Owner

    Messages:
    6
    Re: KORE bug list

    I almost forgot... if it helps, I've also captured a directory listing of all the plugins in the VST and Components directories.....

    (see above message)

    Thanks!
     

    Attached Files:

  3. TechLo

    TechLo NI Product Owner

    Messages:
    187
    Is this a bug the size of Texas?

    ...or just me?

    Before I give the detailed explaination, here's the problem. The User Page knobs that I've assigned to Battery2 controls always reset to 12 o'clock when I open and reload the KoreSound whether as a plugin (Sonar5, Project5V2, Live 5.2) or standalone. Not fun to have your attacks, decays, cutoffs and resonances all at the mid position everytime you load up yoiur song! However, when I save the KoreSound in a standalone performance and reload the performance, the User Page knobs positions are where I'd saved them at previously.

    The knob assignments that correlate to Kore mixer elements i.e. the volume and pan of each channel restore just fine, it's ONLY the User Page knobs assigned to Battery2 controls that point straight to the sky when reloading, a great phallic salute saying "Up yours, pal!" LOL

    Is this by design, or a bug?
     
  4. truman

    truman Forum Member

    Messages:
    279
    Re: KORE 1.02 update

    i finally can say:

    using kore in cubases first vst instrument slot i get the best results, when battery is loaded before kore i get the worst. i know this is not a very good description, but i cannot sort it out better. and by "significantly often" i mean, it happens nearly every time i save and load my project, what leads to i cannot use 1.02 as plugin.
     
  5. BobTheDog

    BobTheDog NI Product Owner

    Messages:
    1,339
    Re: KORE 1.02 update

    Sounds still load as "Untitled", come on guys this was surely one that should have been fixed!

    Cheers

    Andy
     
  6. BobTheDog

    BobTheDog NI Product Owner

    Messages:
    1,339
    Re: KORE 1.02 update

    User pages not available from Kore unit after reloading.

    This is in Live 5.

    Create new project, add kore instance, add sound to Kore. Left and right buttons now change between channel pages and user pages.

    Now save project, exit live, start live and reload project.

    Now left and right buttons do not switch between channel pages and user pages you are stuck on channel pages.

    If you now use the mouse to open up the Kore screen and select a user page the controller then starts working again. Left and right switch between channel and user pages again.


    Cheers

    Andy
     
  7. BobTheDog

    BobTheDog NI Product Owner

    Messages:
    1,339
    Re: KORE 1.02 update

    Have had Cubase sx 3 hange twice trying to load koreFX at startup.

    The second time this happed I left it for a few minutes, it then bluescreened with a 0x0000007f

    After reboot it seems to be loading ok now.

    Cheers

    Andy
     
  8. BobTheDog

    BobTheDog NI Product Owner

    Messages:
    1,339
    Re: KORE 1.02 update

    Keyboard entry still not working in Cubase SX3.

    Cheers

    Andy
     
  9. ew

    ew Moderator Moderator

    Messages:
    21,328
    KORE 1.02 bug list

    I've moved some threads to start this off. Please post your 1.02 bugs here.

    ew
     
  10. BobTheDog

    BobTheDog NI Product Owner

    Messages:
    1,339
    Re: KORE 1.02 bug list

    Hi,

    I just had another bluescreen stop 0x0000007f. This is the second one today. I cannot remember the last time I saw one on this machine before today!

    This happened as followed:

    I Start Kore standalone.
    I clicked the Bass selector in the browser.
    I Double clicked 3step 908 in the browser.

    Now Kore just sat there useing 100% of one of my cpus. I left it a minute or so and then tried to close the app but it was unresponsive.

    I then started task manager, it was strange as there where two "Native Instruments Kore" entries in the Application tab, I could only see one running but maybe one had not closed down properly from before.

    I tried "end Task" on each of them a few times and they did not end.

    I then went to the Processes tab, there was only one Kore.exe listed here. I selected it and clicked "End Process", then got the bluescreen Stop 0x0000007f.

    After a reboot I tried loading 3step908 and it worked perfectly.

    Cheers

    Andy
     
  11. zamyen

    zamyen NI Product Owner

    Messages:
    8
    Re: KORE 1.02 bug list

    Kore still crashing at startup in standalone and vst.

    Says "Kore starting...." on splashscreen, and goes no further.

    AMD 4600 X2
    3gb Ram
    SB Audigy 2 ZS
    XP SP2

    ..Tested reinstall of driver and software
    ..Tested with only Kore dlls in VST plugin folder
    ..USB power saving disabled and Kore plugged in directly (usb2.0)
    ..Crashes my PC with BSOD - "DRIVER_IRQ_NOT_LESS_OR_EQUAL" --> driver Koreusb.sys

    So far despite owning this for almost 2 months have not had a moment's use out of Kore and none of Tech support suggestions have helped...

    Hugely disappointed this patch does not solve the problem, but at least feel it should give some kind of message or indication why it is stalling!

    (NB. Noticed a few other people had this similar loading up problem...as far as I can tell no one has ever posted that they have got Kore to work once they get in this situation..)
     
  12. BobTheDog

    BobTheDog NI Product Owner

    Messages:
    1,339
    Re: KORE 1.02 bug list

    Hi,

    Changeing ASIO settings for my Mlan driver caused Kore to crash with the old favorite:

    "Kore.exe has encountered a problem and needs to close We are sorry for the inconvenience.".

    When I restart Kore I have the correct values.

    I see this problem with not only Kore but most NI apps useing MLan asio or Echo asio on my laptop.

    Cheers

    Andy
     
  13. truman

    truman Forum Member

    Messages:
    279
    Re: KORE 1.02 bug list

    this sounds very similar to the problem i had, and here is the solution i found (worked for me):

    http://www.native-instruments.com/forum_de/showthread.php?t=37534
     
  14. BobTheDog

    BobTheDog NI Product Owner

    Messages:
    1,339
    Re: KORE 1.02 bug list

    Blue Screens.

    Since installing the new version and driver I have now had 4 bluescreens, this is on a machine that I rarely ever see bluescreens so I believe it must be the new driver.

    This time I was working in Live for about an hour with 4 instances of Kore loading. On one instance I was useing the browser to try out different sounds which was working really well and when I clicked on a new sound live just disapeared with no error message.

    I restarted live and let it recover the project and it bluescreened with a Stop 0x0000007f.

    I am going to log a call with support.

    Cheers

    Andy
     
  15. fermuscolo

    fermuscolo Forum Member

    Messages:
    26
    Re: KORE 1.02 bug list

    Hello, after I create some presets with different plugins, when I switch presets lots of notes get stuck. It also happenned with version 1.01. Its unuseable. I don't even start to use the controller pages or touching the controller, only layers with differnt FXs and mixes. I can't do anything more after at least I can play something with this thing.
     
  16. jigglypuff2

    jigglypuff2 NI Product Owner

    Messages:
    88
    Re: KORE 1.02 bug list

    1.02 works much better for me - but if I load a preset that needs around 30-40% CPU , I start to get spikes after a while when the CPU meter starts racing up to 80-90% then back down to 30-40%.

    So the spike issue has only been partially fixed.

    I certainly would not use this program live yet- it's just too unstable at the moment

    It is encourarging that it is working better now.
     
  17. Nishioka

    Nishioka NI Product Owner

    Messages:
    10
    Re: KORE 1.02 update

    I´ve similar problems. At a system with Nuendo 3 it´s only possible to use Kore, if you load it at first VSTi in the first VSTi Slot. If you load another VSTi before Kore the system chrashes. I don´t know if it appears generally after loading of any VSTi or only special VSTis.

    Another sad bug: Kore can´t switch presets on most of the VSTis.
     
  18. BobTheDog

    BobTheDog NI Product Owner

    Messages:
    1,339
    Re: KORE 1.02 bug list

    I am getting these spikes also useing Kore as a plugin in Live 5.

    Cheers

    Andy
     
  19. truman

    truman Forum Member

    Messages:
    279
    Re: KORE 1.02 update

    most of my cubase projects (from times before kore) have battery on the first vst slot. so when i consider using kore, i have to rearrange all of them? no thanks, ill stay on 1.01 (wich i can load into what ever slot i want).
     
  20. BobTheDog

    BobTheDog NI Product Owner

    Messages:
    1,339
    Re: KORE 1.02 update


    Hi

    I have just done a test with SX and 1.02, loading battery into slot 1 and then Kore into slot 2 and everything works fine here.

    Not alot of help but it may give you hope :)

    Cheers

    Andy
     
Thread Status:
Not open for further replies.