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. krugger

    krugger Forum Member

    Messages:
    230
    New bug for me:
    I load up a new sound (say Albino 3) and the problem isn't the plugin but rather the control assignment on the User Page.

    I've got only 1 user page and i can't get to it via the hardware buttons.
    I've tried combos of pressing SOUND and/or CONTROL, left/right cursor buttons etc, no go.
    I'm sure how I used to get to the user page on v1.0.1 so I'm also sure I'm not doing anything wrong.

    If, however, I open KORE UI in my DAW and click on the User tab, then the User tab does open and on the hardware controller too.

    From then on, I can navigate from User to the auto-assigned ones (+ the main area) on the hardware freely.

    Summary:
    Cannot access User Page using the controller only.
    This bug is 'unlocked' once the User Page is selected at least once in the UI

    Platform: Mac Intel
    Version: 1.0.2

    Kr.
     
  2. Loopster

    Loopster NI Product Owner

    Messages:
    7
    Kore driver sets out

    I have a problem with the new audio driver. by playing songs and samples in wavelab 5, live etc... the sound suspends very often. I tried a reinstall of the driver but it didn´t fix it.

    Any ideas for that?
     
  3. ew

    ew Moderator Moderator

    Messages:
    21,328
    Re: Kore driver sets out

    Yep. If you're running at 16 bit resolution, change to 24. If you're already running at 24 bits, change to 16 and then back to 24.

    http://www.nativeinstruments.de/forum_us/showthread.php?t=38134

    ew
     
  4. Loopster

    Loopster NI Product Owner

    Messages:
    7
  5. andreuz

    andreuz Forum Member

    Messages:
    76
    Re: KORE 1.0.2 bug list (2 NEW BUGS)

    ew: comments on these?

    Couple of BUGS that I have found using the new 1.0.2 update:

    BUG 1) In the Stand Alone version, I like using the "Attributes" to Color-Code each type of plugin (sound) using the same, respective color. This way, at a quick glance in the mixer view, I can quickly identify plugins/sounds by their assigned COLOR and is good for organizing, visually. BUG: After assigning different colors to different plugins "Sound Attributes", and then save the file, close it out, and reopen it - In the MIXER MODE VIEW (|||), all the colors are now defaulted to "White". Here is the weird thing - go to just one of the attributes for one of the assigned colorized plugin and the color name is still correct, then select the "same or different color" and go back to the MIXER VIEW and now ALL THE COLORS ON ALL PLUGINS are back to the way they were when last saved !!! The other 2 Mode colors work fine (only Mixer view has the bug), but I use the mixer mode all the time and I can't do this procedure evertime I open a file... lol. I certainly hope this can be fixed in NI's next update.

    BUG 2) In Stand Alone version, I have been working on a master template file for me to use and slowly improve it for my "Live Performance". After spending many hours getting it close to a usable template (I should have backed it up), BUG: One night I decided to experiment with "Group Channels". I added 2 new group channels assigned them each a different plugin. Then, in the performance view, I selected the "Solo" button on both group channels and for some dumb reason saved the file. When I reopend the file to work in it further, the solo buttons on each group channel were still on (saved), then I went to turn them off and KORE crashes. I open the file again and it opens and can select any other plugin and work with them but the second I select any part of either of the 2 group channels, to delete them KORE crashes. There must be a BUG somewhere in the group channels. I lost my template file alone with many hours of setting it up. I will be backing up my templates from here on. NI, please look into this for the next update. I think I can benefit using the group channes, but wont touch them until there is a fix.

    _______
    My setup: WinXP/SP2; Hard - P4, 2.8 Ghz, 2 Gig Ram, Dedicated HD, Delta 66, Midiman USB 4x4, Hammond XK2 (using as contoller) & Roland Piano (using as a contoller) & MAudio Controller Pedal. Soft - NI Plugins; 3rd party UVI Plugins

    Andreuz- (Registered Native Instruments & KORE owner)
     
  6. Steffen Fuerst

    Steffen Fuerst NI Product Owner

    Messages:
    427
    Re: AAS Lounge Lizard still doesn't work

    I (and AAS) know that the au-version doesn't produce any sound, we didn't find the cause till know, but did you also try the vst-version? That should work.

    Best regards,
    Steffen
     
  7. Loopster

    Loopster NI Product Owner

    Messages:
    7
    Re: Kore driver sets out

    Hey thanks ewistrand it worked fine with 24 bits ;)

    Let´s make some really fine music, have a nice day

    loopster

    #
     
  8. ew

    ew Moderator Moderator

    Messages:
    21,328
    Re: KORE 1.0.2 bug list (2 NEW BUGS)

    I haven't noticed the first one, but I don't work in mixer view very often. I'll look into it.

    As to the second, I use group channels a lot myself and haven't run into that problem. I'll try to replicate it.

    ew
     
  9. andreuz

    andreuz Forum Member

    Messages:
    76
    Re: KORE 1.0.2 bug list (2 NEW BUGS)

    Thanks ew... thats all I can ask for. Hopefully there is a fix for both.
     
  10. Kymeia

    Kymeia NI Product Owner

    Messages:
    6,268
    I've tried an earlier version of rewire now (1.61) but it still crashed/hung Ableton Live. Any news on the fix?
     
  11. theoryzero

    theoryzero NI Product Owner

    Messages:
    234
    I'm using the MDE-X effects plug-in from the Korg Legacy Collection - Digital Edition in Kore 1.02. When I try to bring up the panel for the MDE-X it comes up as a blank window. This happens when using Kore as a plug-in in Cubase SX3 or in standalone mode. The panel for the plug-in works fine in Kore 1.01.

    I've tried this on two different Windows machines with the same result. I do not have this problem with the WAVESTATION or M1 plug-ins. Known issue?

    TZ
     

    Attached Files:

  12. BobTheDog

    BobTheDog NI Product Owner

    Messages:
    1,339

    I get the same here, so it looks like a bug.

    Cheers

    Andy
     
  13. WillBarnett

    WillBarnett Forum Member

    Messages:
    339
    Live 5.0.3 running several instances of Kore I can add a new Kore instance and I get the message "NI Kore couldn’t find the Sound database. Your Kore Sounds will be analysed to create a new database". Sounds library is then empty.
     
  14. andreuz

    andreuz Forum Member

    Messages:
    76
    Re: KORE 1.0.2 bug list (2 NEW BUGS)

    Hello EW:

    I am just doing a follow-up on this as this very important to me. Just verifying that you reported the 1st bug I mentioned above about colorizing plugin channels to NI for the next update? I MAINLY WORK IN MIXER MODE (III) (I use colors to organize my plugins) and every time I open up a previously saved file that I have assigned various colors to plugins channels in "Attributes", I have to go to one of the plugin channels and select that color and only then do all the other color re-estabish their assigned colors in MIXER MODE... and its driving me crazy! Did you try it yourself?

    I would appreciate some assurance that you tried it (even though you don't work in mixer mode, many of us probably do) and reported it. Please let me know.

    As far as the 2nd bug... I have not gone back to using any Group Channels since my major file crash.... and wont until I hear anything back about it.

    Thanks in advance!! Andreuz
     
Thread Status:
Not open for further replies.