Page 1 of 1

Your experience after COMPRESSING samples?

Posted: Sat Sep 15, 2012 2:47 pm
by fResH_
Hi guys, just want to hear from you that have use the sample compression. What do you think of it? Did you experience some issues?

It did compress it from 132mb to 80mb but so that worked. buuut...
I did notice a deffekt in samples after the compression. take a look at my video showing what happend to some of the DRUM KICKS.


The problem and TIME CONSUMING of finding the "peep" sounds in the compressed samples.
http://www.youtube.com/watch?v=QZCOf7az ... e=youtu.be

I noticed that after I compressed, some of my samples have been mixed with eachother.. take a look at this clip that ilustrates a roller snare and a turkish daff into each other.
http://www.youtube.com/watch?v=0yFhgEPV ... e=youtu.be


Watch the video to hear and belive:
http://www.youtube.com/watch?v=RndHV9yhymY

part 2
http://www.youtube.com/watch?v=DWA0pejZ ... e=youtu.be

part 3
http://www.youtube.com/watch?v=6EvoSsK_ ... e=youtu.be

I can keep all they finding deffekts whit the samples. :O
Is there a solution for this? Why did this happend?

Posted: Sat Sep 15, 2012 7:53 pm
by gempk5
I also do have this problem .not work after compressing 265 mb .and compressing take entire one day and is not end until I click cancel.and then after will show the ram available 223 mb !!!! :?: :idea: :!:

Posted: Sat Sep 15, 2012 10:30 pm
by AntonySharmman
fResH_
This whistling effect is just loop !!!
Go to the specific samples , edit them and you will discover in second page
that loop square box is active !
Un-check it and save it back with compression box checked.

Never use loop mode to percussion & drum samples , because then you have to
re-edit every simple sample !
Pa2X was insensitive to that issue but when you transfer samples to Pa3X all
these issues will be revealed , especially after compression !

I've compressed Gb of samples for my commercial resources and I ensure you that
512 Mb of samples need just 4 Hours , when procedure is canceled or power shut
down happens , stops at an average point that will be continued when function
is recalled.
The only malfunction in compression that I'm afraid is still there , is that
in some samples ,loop point is slightly removed in MS reproduction only , and
can be fixed in most of times with just re-saving these samples (compressed).

I hope that helps you.

Posted: Sun Sep 16, 2012 12:42 pm
by garabed02
I had the same problem. I have a 256 mb set, I compressed all my samples and it takes an entire day (I have more than 5 000 samples, I guess that's the reason) but fResH is right, it's the loop problem. I talked to Paolo about this and you have to find all bugging samples and unloop them, and save them again.

This problem is producing because sometimes, when we load a drumkit or multisample by another set, we didn't pay attention on the samples. So now, we have to resave allllll samples which are looped.

Regards

Posted: Mon Sep 17, 2012 6:17 pm
by fResH_
Antony, I will say yes and no to your input.. the looping is true thank you for that.. BUUUT here is the thing I noticed.. after the compression the compressing have mixed ihop samples into each other with some of them.. here is a clip that will show you.. you know how a roller snare sounds like.

http://www.youtube.com/watch?v=0yFhgEPV ... e=youtu.be


AntonySharmman wrote:fResH_
This whistling effect is just loop !!!
Go to the specific samples , edit them and you will discover in second page
that loop square box is active !
Un-check it and save it back with compression box checked.

Never use loop mode to percussion & drum samples , because then you have to
re-edit every simple sample !
Pa2X was insensitive to that issue but when you transfer samples to Pa3X all
these issues will be revealed , especially after compression !

I've compressed Gb of samples for my commercial resources and I ensure you that
512 Mb of samples need just 4 Hours , when procedure is canceled or power shut
down happens , stops at an average point that will be continued when function
is recalled.
The only malfunction in compression that I'm afraid is still there , is that
in some samples ,loop point is slightly removed in MS reproduction only , and
can be fixed in most of times with just re-saving these samples (compressed).

I hope that helps you.

Posted: Tue Sep 18, 2012 12:20 am
by musicrazy
i experienced the same thing with os 1.11. After re-install os and recompressing samples all went ok. not happen again after several compressions.

Posted: Tue Sep 18, 2012 1:19 am
by fResH_
aha nice to hear. thanks
musicrazy wrote:i experienced the same thing with os 1.11. After re-install os and recompressing samples all went ok. not happen again after several compressions.

Posted: Tue Sep 18, 2012 2:16 am
by AntonySharmman
fResH_
I'm also aware of this malfunction , I didn't notice it earlier !!!
This is a different issue and concerns only Ram failure , in case you see merged samples
( there you have roll Sd merged with Rim) , and was an accidental issue.
This can be solved
wiping ram mode in older to reload samples from System HD , or turning of Ram ST-By in order to force
reloading , but all the others are looped percussion and must be corrected regardless to any OPS !

Posted: Wed Sep 19, 2012 1:44 pm
by Paolo@Korg
Matthew,

You have a personal message.

Best regards,
Paolo

Posted: Wed Sep 19, 2012 3:33 pm
by Asena
I HEAVE THE SAME PROBLEMS; PAOLO !!! Mail me to please.

Posted: Wed Sep 19, 2012 3:34 pm
by Asena
BY THE WAT this is great to explore , whit video proof. And Its maybe better to undarstand for KORG, We are their beta testers. :wink:

Posted: Wed Sep 19, 2012 8:42 pm
by fResH_
The problem and TIME CONSUMING of finding the "peep" sounds in the compressed samples.
http://www.youtube.com/watch?v=QZCOf7az ... e=youtu.be

Posted: Fri Sep 21, 2012 3:35 pm
by Paolo@Korg
Matthew,

As for mixed samples, have you tried with the Media > Preferences > Force PCM Reload? While this issue should happen rarely, this command usually solves problems of missing or corrupted samples.

The whistle depends, as Antony points out, on loops. There is too short a loop, that causes troubles when compressing (too little data on which to work). If it is a percussive sound, please turn the loop off. If it is a long sample, make a longer sample. (Please remember to save the sample).

Best regards,
Paolo

Posted: Tue Sep 25, 2012 12:55 am
by fResH_
Paolo, Yea I noticed the loop whistle thing as Antony pointed out.. Its just a pain in the ass to resave almost every sample. :(

Accualy I have never tryed "Force PCM Reload", what will this do? Make the samples as they were before the compress? no? what?

Have you found any reasons of why this mix up of samples in samples occurs?



Paolo@Korg wrote:Matthew,

As for mixed samples, have you tried with the Media > Preferences > Force PCM Reload? While this issue should happen rarely, this command usually solves problems of missing or corrupted samples.

The whistle depends, as Antony points out, on loops. There is too short a loop, that causes troubles when compressing (too little data on which to work). If it is a percussive sound, please turn the loop off. If it is a long sample, make a longer sample. (Please remember to save the sample).

Best regards,
Paolo

Posted: Tue Sep 25, 2012 12:57 am
by fResH_
In the end of this story,
Would it not have just been better if KORG inplanted a 512mb in the first place. instead of playing around with this RAM limits for us users and fooling around with compressing techonlegy nonsense that are bugging. They would have saved some souls.

2012 with 256mb limit + worthless compressing option on a proffesionall arranger like this, 2012? :lol: :lol: :lol: yeah right