Kore 1.0.3 Buglist

Hi Guys,

I will set the ball rolling.

1. Sounds still untitled when reloading projects.

2. Closeing Kore window in Live 5 now closes Live 5 as well, not good at all!

Is anyone else having problems with Live 5, it seems to work ok with the 6 beta for me?

Cheers


Andy

 

Copy/pasting some Reaktor Sounds loses their Easy Pages/mappings (sometimes and for some ensembles - can't work out any pattern as yet)

Closing Kore plugin in Live 5 then reopening leads to Freeze (with rewire enabled - deleting rewire fixes this)

Clicking on some Sounds just seems to open an empty channel

 

1) Untitled bug when reloading projects - All sounds are named 'Untitled'
One other thing I've noticed - on the KORE UI itself, 'Untitled' pretty much remain as such EVER, no matter what you do to the Sound (i.e, Save/Load)
I'm talking about the plugin here

2) Attributes are not loaded too when loading a project. Also, if a Sound is loaded manually, the Attribute 'Colour' is not reflected in the small circular light near the word 'Untitled'.

3) You can't get to User Pages when you load up your project in the DAW using the KORE controller only. You have to open your UI at least once, click on 'User' then the user page becomes available on the controller

V 1.0.3 and still the Untitled bug ............ *sigh*.
Would be funny if Logic or Ableton had a similar bug where they 'forgot' settings when reloading a project.

 

pisser will not even open up in live 5 or beta 6 for me. big surprise.
this sucks guess that i need to dl the older version and reinstall

 

I too am getting the reopen with untitled sounds in Logic 7.2

 

I don't get why NI 'Support' doesn't give this high priority to be fixed.
This is the first point of contact when using the controller to access the sounds used on various tracks of a song! d'uh!!!

I've posted a support query to Tech Support (once ****ing again on the matter) and will forward their reply to the forum.

Expect apologies, requests for patience and a statement saying the bug is tricky to fix.
I've been collecting them replies.

 

Yep,
same problems with the "untiteld" in live 5.2.2 on mac os x
I have an another problem no resolve: when the mac is shutdown
the kore controller make a terrible noise, like a storm, in headphones out...
interesting drone's musik ! Kore is the only interface/sound's card (usb or fw) who make this !! No truly response from NI support.

 

I didn't know there was this kind of thread, so I'll post these here:

After using Kore for a while through the controller headphones, the Kore controller output starts crackling and doesn't go back until I switch the output to built-in and back from audio settings or restart and disconnect. It sounds like the sounds crackles and has gaps in it. And sometimes it goes even mute after that. It's still unusable for a gig, so I should use the laptop output (with the built-in output this doesn't occur).

Here's another bug:
-create an empty performance.
-create two dummy presets with append-button
-create a new user page and assign any on/off-button of the Kore controller to Tap tempo
-the button taps tempo as it's supposed to do, but also switching presets from the controller back and forward taps the tempo
-also when the tempo tap is assigned to one of the on/off-buttons, I can't seem to change the fade-value at the preset manager, because trying to click these fields with a mouse button seems to tap tempo too, obviously clicking in quite many places when this tempo tap is assigned causes the tempo to tap.

 

thanks god! there´re other users out there who have the same problems that i have. i´m not nuts ))

i know this problem as well: the driver is just bullshit! i had telephone sessions with the NI "support". and after almost 3!!! weeks we realized this: if you use kore as audio hardware, it produces system requirement peaks up to 100 percent. you can check this with "dienstprogramme/ aktivitaetsanzeige"
this is also responsible for "sound stopps" during playing tracks (which happened 2 times in clubs we played!!!).
it´s time for NI to do something REAL!!!

 

ps: the support guys told me: "you´re the first one who reports this. must be a mac problem."

i visited my re-seller and we installed it on a audio-optimized pc. first thing was a deleted master boot record on the harddisk...

and these guys are whether studio nerds by themeselves or well experienced live musicians.. THEY called then NI "support" and - NO sorry - they just told some hillariuos things..

power book´s too slow.. you use cracks.. you must not use insert efx.. you must install latest updates..

HEY!

 

I had the "cant save soundfile" when Kore close.
Next time you can not open the sound again the sound and the performance is destroit.
Support told something like "maybe its because you are using traktor too..............but i just can say: "Its all NI Products"

The crackling sound changed, after changing USB to 2ms (before 4 ms) and Audio Buffer size to 5ms ( before 8 ms )
in the driver settings.

The crash is maybe coming when you change the Midi and Performance Path from Documents and Settings to the Path from your installation.
The next time the program writes himself the Documents and Settings Path again in the Application and leaves also the Application Path stay there.
I thought that the program dont know then where to write back.

 

I wish there was some USB settings we could experience with with a mac, but there are none. It's so sad because Kore has such a good idea and I really would like to use it but why doesn't it work!!!!!!!!!!

So is this "sound outputs turning into crackling output" someone else's problem too, or should I go change my controller and send it to service?

Powerbook 15" latest revision, 2gigs ram

 

So that's the reality:
Kore is a great concept but it's very very bad soundcard !!!
for any configurations.
It's like when the early ipods exists for Mac's users, with wrong battery and drivers etc, etc... it's like a pcommercial's private joke.
I don't like this.
I'm Mac's user, and i rest, and for the community we are Creators, not co(w)nsomators.
So please NI, change definitively your f*ck ing drivers and respect your users.
Money is not the end ! and fix yours bugs !!

 

Re: Kore 1.0.3 Buglist - Presets

Hey everyone-

I have installed the 1.0.3 Update and at this point I have 1 Major bug to report. I also found another bug that did not get fixed and will post that in a separate post. This bug is about PRESETS in 1.0.3 in stand-alone. Presets are probably one of the greatest features Kore has to offer. After spending many hours setting up my Presets in 1.0.2. and after installing the 1.0.3 update, all the hours I spent on setting up individual presets have been wasted. The pre-existing presets show up with the same name, however once I try to change to the next Preset, Kore strips-out all of the pages & parameters ("m" next to all parameters) on every channel insert and silences ever channel insert as well!!! So I experimented with creating new file in 1.0.3 with a couple new presets, saved it and re-opened the new file and the presets work. So this tells me that the new 1.0.3 update does not recognize the 1.0.2 presets??? This really really ticks me off. Updates are suppose help the user out not take 3 steps backwards... gezzzz!

ER... can you tell me whats up with this? Please don't tell me I have to re-create all my presets again. There must be something I am missing here. Come on NI... are you testing these things out?
_____________________
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)

 

Re: Kore 1.0.3 - Colorizing Channels in Mixer Mode

Another Bug: I reported this BUG very early in 1.0.2 and did not get fixed in 1.0.3. and its definetly a bug. In the Stand Alone version, I use 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 saving time. HERE IS THE BUG: After assigning different colors to different plugin channels in the "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 back 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. I was hoping this would have been fixed in this new 1.0.3 update but DID NOT! I work primarly in Mixer Mode........errrr!!!

Any reason this did not get fixed in this new update? Did it get reported to NI?
_______
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)

 

After upgrading to Kore 1.0.3, I noticed iTunes 7 all of a sudden had jumpy / crackly sound.

I tried playing with all the settings in QuickTime and in the and the Kore Controller Driver Control Panel and such but no dice.

NI-- can you make the Kore soundcard play nice with iTunes 7?

 

Oh, is that why iTunes is bugging out? I only get the crackles at under 100% volume in iTunes.

 

The KORG MDE-X GUI bug I reported in this post is still there...

 

A couple of major bugs with Kore when used as a plugin within Cubase SX3– one new and one old…

1) The old bug is that I still can’t type in the Kore window in Cubase – this makes it a real hassle when I want to search for a specific preset or rename anything in Kore. The only keys that can be used are those that are not assigned as key commands in Cubase. Kore is the only plugin I use that has this problem and no setting in Cubase seems to be able to alter this problem.

2) The new bug is that if I load any sequenced sound (like a drum loop in Reaktor), it no longer plays since the update to 1.0.3 – it doesn’t matter if I use the play button on the controller or in the Kore interface – nothing happens!

These are major problems that need to be sorted out asap – in my opinion, they make Kore almost unusable as a plugin.

I would be interested to know if anyone else is seeing these bugs or if they have found a way around them, as NI support has been so far unable to help me!

 

Replied to the bug request I sent to NI. Rico Baade apologized and said he would reiterate the urgency in getting my bug fixed for the next update. He said the next update is planned for mid-October.