Losing transients on truncate and cut

After cutting or truncating samples I recognize a serious loss of transient. Sounds just like the sample gets a fade-in after being cutted. Feels like a serious bug.

Doesn't matter if I truncate for example the first half of a sample or cut the second half. In all cases when using truncate and cut the initial transients decrease. See attached screen.

Any experiences on this?

 

I think this is due to some "unacuracy" if you zoom out on waveforms and how to present them, but it is nothing you should hear.
try to zoom totally in until you see stairs then it should look the same if you really just have cut something away.

Uwe

 

Nope, I definitely hear it. The kicks do have way less punch, sound much more muddy than before truncating or cutting.

 

Have you a sample from maschine libary that I can try again - I tried with some clicks but it had no effect on my side.

Uwe

 

could this problem have something to do with "zero crossing"? isn't there somewhere on machine sampling tab a function to switch "zero crossing editing" on/off?....

 

Not from the Library, as I'm using my own samples, but sure, here you go:
https://www.dropbox.com/s/ratzfcwqxd33rb2/GT Wimmer A2.wav?dl=0
https://www.dropbox.com/s/urd27nuavdmtyf6/GT Wind Of Change G2.wav?dl=0
https://www.dropbox.com/s/dcvcbbsxjtgizjq/GT Wobble I G#2.wav?dl=0

As you see in the attached images, these samples show perfect loops in my audio editor, but Maschine just ignores them.

 

Maschine just ignores the loops, so there's no zero crossing in effect.

 

here i just played with the zoom but really gentle in small steps, i also truncated after setting end marker to front but the sound was always the same. Absolutely no change to transients.

Uwe

And normally wav files does not contain loop point information as standard. But some programs write it somwhere in the metadata? like wavosaur, acid and whatnot. But like I said not a standard.

Uwe

 

Thanks for trying. Strangely I tried the same in a new project where it worked. So it seems it was kind of a random bug. Similar to the fact that some loop points are read and others are ignored. I created all loops in the same app, so I don't see any specific reason why some of the loop points are imported and some are not.

Even if loops are not standard, for a sample-based DAW like Maschine it should be self-evident to read these loops. Other DAWs and samplers do it, too. Can't imagine that it's a big deal for NI.