Corrupted Sounds

I don't see it here...

ew

 

No, I did not read your post entirely. Sorry, yes do report this please via the support form.

As mentioned, our QA could not repoduce this, neither could Eric. So we need to find the special condition under whihc this issue occurs.

Best,

Henning

 

This is exactly the same issue I reported. It works every time with the Biolabs/Camel Sounds I mentioned and example I posted if you want a way to reproduce it.

I notice Matt is on a Mac and I am on PC so if you're looking for a "special condition" the fact that we are on such different systems makes it less likely it's system specific and more likely there's a problem with the way KORE 2 handles some types of KORE 1 multisound.

 

bump - progress report please? Still not heard from tech support.

 

Right I have made a file on KORE 1 using just freeware so anyone can test this out. It just uses 1 instance of REFX Claw and one instance of SmartElectronix SupaPhaser loaded into the slot below in the same channel. This is the critical condition for replicating this bug. The other thing is you need to load and edit it from the browser, not the "Load Sound" command.

To replicate the bug place the SOUND in your shared folder and once it's in your KORE 2 database do a search for it (might be best to test it once to make sure it's working for you).

Start with a fresh performance, select the SOUND and before trying to load it click the edit button in the browser and just change the star rating and click save. Nothing else. This is sufficient to create a corrupted SOUND next time I try and load it on my system (though changing colour also does it). Works every time.

http://www.fingermarks.co.uk/music/supaclaw.zip

I've also included a corrupted version for comparison:

http://www.fingermarks.co.uk/music/corrupted_supaclaw.zip

anyone that understands HEX code might want to see what the differences are in a HEX editor.

 

Also I've found that if I so load this file (or similar ones) from the "Load SOUND" dialogue and then immediately resave it in KORE 2 without making any changes it seems to "immunise" it against this corruption - I can change all sorts of attributes this way and so far, touch wood, they don't damage the file. Doesn't help me with the ones I've already lost though and a bit of a pain with big folders full of SOUNDS made in KORE 1 like all my CamelKORE SOUNDS.

Probably useful to know though in looking for the cause - it seems to be using the EDIT button with a selected SOUND made in KORE 1 with an instrument and 1 or more fx in the same channel (maybe with third party VSTs or a mix of NI and 3rd party?) in the browser itself that corrupts the SOUND.

 

Thanks for the additional info; that should help.

ew

 

Support seem to have been having difficulty replicating this but it turned out they were not following the same procedure (they keep saving the performance as a sound, not the sound itself) so to make it simple I have attached some instructions with screenshots - anyone want to try and replicate this?

http://www.fingermarks.co.uk/gifs/instructions.pdf

 

Hi Kymeia,

thanks for the info, I just forwarded this post, but I can't tell you by when we'll have a result.

Best, Henning

 

Well you won't get a result as long as technical support seem unable to follow my instructions properly. I have tried spelling it out to them and they keep saying they can't replicate it but when they describe what they are doing they are not following the exact procedure I have specified, or taken into account the fact that Multivac is also having the same problem but on a Mac. It's becoming very frustrating. I know there's a serious problem and it's corrupted all my personal Multisounds and a few from third parties like Biolabs and it's 100% reproducible on my system but they keep acting like I'm imagining it or something. Can someone else please try this.

 

dont have kore2 so can't verify, but if there is anything i (or camel audio) can do to help, just let me know.

col

 

I definitely will, Col =)

Happy holidays to you, and tell Ben the same.

ew

 

cheers eric...right back atcha.

just been trying to pm you, but cant see where to switch them on.

anyway, if NFRs of phat-space would help you or anyone at NI support pin this down, i'm sure tim can sort you out. let me know and i'll drop him a email.

 

It's in my profile, Col- click on my name.
To turn it on at your end, go to your control panel here at the top of the forum and click on options.

ew

 

Thanks Col. Luckily at least your sounds I had backups of but stupidly, since I thought all I was doing was some minor tagging, I hadn't thought to back up my own.

 

Hi,

fyi: the issue has now been reproduced and will be investigated by the developers.

I'll let you know once there's more info available.

Best, Henning

 

Whoopee

I hope they can also find a way to rescue my corrupted Sounds.

 

Hi, I just wanted to say I am also having this issue in a big way - I have customised most of my library in such a way that makes it susceptible to this problem.

The only option for the moment seems to be to open and re-save most of my 10,000 plus sounds individually, and in the meantime it's impossible to batch edit or even change colour/rating of any sounds until this is resolved as there is no way to tell which sounds are at risk/already corrupted and which are 'immunised' as Kymeia described above.

Kore 2: Find, Play, Tweak, Save, BACKUP, Edit, Lose, Restore Backup, Open, Resave, Curse Gods

 

Have you sent in a report to support? - I think the more voices raised on this very serious problem the better - took quite a while for them to identify the problem.

 

Good point. I will, indeed.