• Hi and welcome to the Studio One & Studio Pro User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!

Glitchy Impact slice behavior

freddiphin

Active member
I have (for as long as I've noticed - i.e. thru the versions) had this issue of not being able to slice samples to empty pads on Impact IF there are already populated pads in Impact. No matter what new slices (whether performed with the Shift-Drag method or Right-Click a pad and choose Slice) RE-populate the pads from the first position at C1 overwriting whatever was there to begin with. This can be seen in the video -
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Where you can see me Shift-Dragging a first sample to A bank, C1 and then slice it across banks A-C. I then choose a second sample and Shift-Drag to empty D bank and empty C5 and then slice. All those slices then overwrite my originals starting a A, C1. This is not what is supposed to happen, for sure.
 
...No one shares this issue or can reproduce??
 
...No one shares this issue or can reproduce??
Been messing around with impact today, not something I normally do. Don't ask me why I don't know...

However, I must admit I am a little confused by the pad note trigger assignments. In other similar drum sequencers the A to H pad bank grouping are contiguous with Impact they jump around.

In Bank F it Loops around from G 8 to C -2

However,
I experienced the same outcome, it defaults to writing the sliced loop to bank A B C etc., regardless of those pads already being inhabited by the previous slice operation. I am not familiar with impact, it would be interesting if someone more knowledgeable could comment.

Best of regards
 
Been messing around with impact today, not something I normally do. Don't ask me why I don't know...

However, I must admit I am a little confused by the pad note trigger assignments. In other similar drum sequencers the A to H pad bank grouping are contiguous with Impact they jump around.

In Bank F it Loops around from G 8 to C -2

However,
I experienced the same outcome, it defaults to writing the sliced loop to bank A B C etc., regardless of those pads already being inhabited by the previous slice operation. I am not familiar with impact, it would be interesting if someone more knowledgeable could comment.

Best of regards
OK then. I had reported it to Support as well, but so far no response. For sure this is not how it is meant to behave.
 
I wonder if Slice to pads is a one time thing ?
That would be odd and a restrictive move. I need to spend more time with Impact to be sure, but I had the result your Vid shows.

Best of regards.
 
Back
Top