PlanetZ forums - scopeusers.com

Hi

I'm new here at Planet Z and this is my first
Post.

I have a problem with my STS3000. Sometimes,
when I try to do normalize to on of my samples, I get a "click" noize that distroy
my sample. Is it a bug?
Here is my system:
Pulsar II
PIII 866 cpu
512 Ram

Thank you.

Hi there - welcome aboad...

What software are you using to normalise the sample(s)?

Are they one-shot samples, or looped? If looped, are they 'perfectly' looped (both ends of loop at a crossing point/in phase with each other)?

When you say your samples are destroyed, is the whole sample affected, or just a single point in the sample?

Royston

I think Royston figured it out.
Be sure that you have a smooth start and end point of your sample.
You can solve this, when you use a wave editor like cool edit, sound forge, wave lab or whatever and fade in and out your sample for only few milli seconds.

Hi

I don't have normalize problem with my
soft (I'm using wavelab), the problem
is with the normalize function that is in
the STS3000 sample editor.
And it's happen with any kind of wav file,
loop or not loop.

Thank you.

Does this happen with every (all) samples that you normalise, or just particular ones?

If you normalise a sample in Wavelab and normalise a copy of the same sample in STS 3000, then play both back using STS 3000, is only the sample which was normalised in the sampler 'corrupted'?

Royston

It's happen from time to time.
And yes, it only happen on the STS
Sample Editor.
Maybe it's a ram problem...?


Thank You.

Me - Di wrote:

It's happen from time to time.
And yes, it only happen on the STS
Sample Editor.
Maybe it's a ram problem...?

Can't be, from what you've said, else why would a sample edited (normalised) in Wavelab play perfectly but a sample edited in STS have glitches?

I would suggest to only normalise in Wavelab in future, and forget about using STS 5000 for this purpose.

This all sounds very odd, though - a normalise algorithm isn't exactly rocket science ...

Royston

I guess you right...
I'll use wavelab instad of the STS.
Thank anyway.


Thank you.

Me - Di wrote:

I guess you right...
I'll use wavelab instad of the STS.
Thank anyway.

No worries - perhaps you could send me an example sample which exhibits this behaviour?

(You can use my private email address which is in my profile information).

Royston

On 2004-03-30 04:46, Counterparts wrote:

Me - Di wrote:

I guess you right...
I'll use wavelab instad of the STS.
Thank anyway.

No worries - perhaps you could send me an example sample which exhibits this behaviour?

(You can use my private email address which is in my profile information).

Royston

Thank you for trying to help, but since
I'm using the libary pc for internet
I can't send you anything...

Thank you.

Hi,

i got the same problems. That was the reason that i only normalize my samples in cubase sx.

On 2004-05-03 07:44, stephan_trance wrote:
Hi,

i got the same problems. That was the reason that i only normalize my samples in cubase sx.

Now I know i'm not the only one...
So maybe my RAM is OK... I Hope...

Thank You.

Me - Di wrote:

Now I know i'm not the only one...
So maybe my RAM is OK... I Hope...

Probably is OK - this site has a very good memory test utility:

http://www.memtest86.com/

IIRC you pop the code onto the floppy and boot from that to run the tests.

Royston

Thank you.
I'll check it.

i've also had this happen - spike at the very end of sample.

the sts sample editor is a bit half-arsed.