Studio one ..drag-drop sliced sample into sample one

[gentleclockdivider]

I've got an issue here >
I slice up a drumloop (transient detection method ) followed by the slice action >.
Selecting all the samples and drag dropping them into sample one neatly places each sample on a separate key (screenshot 1)

But on someother samples following the exact same method , each slice is spread out across the whole keyrange (screenshot 2 )
Weird

[apoclypse]

I'm not sure what you are doing exactly here but why not use the Send to Sample One function instead. (Right click on the selected audio, Audio > Send to Sample One, or Send to Impulse). It will automatically create a Sample One XT instrument for you and the audio will be mapped out.

[gentleclockdivider]

I'm not sure what you are doing exactly here but why not use the Send to Sample One function instead. (Right click on the selected audio, Audio > Send to Sample One, or Send to Impulse). It will automatically create a Sample One XT instrument for you and the audio will be mapped out.

I just do the basic procedure for transient detection and slicing


Hah , I get the same result when righ click and sending to sample one , at least with one sample
I use two samples , first James Brown's funky drummer ...each slice gets it's own key .
Second loop is James Brown's cold sweat , this puts all slices across the whole keyrange .
I has to be something about that sample

[gentleclockdivider]

If you right click a brand new loaded sample ( no transient detection whatsoever ) and choose send to new impact , it will automatically slice it for you in impact
I really dislike when a program decides things for me

[gentleclockdivider]

CORRECTION : when holding shift+ dragging a loop into sample xt , it automatically slices it , without enabling any transient detection
I just guess it does that under the hood

[gentleclockdivider]

There is def something weird going in the way Impact xt treats different samples <
Take the first screenshot , the orange clip sample when slip editing (in arrangee view )and drag droing in sample one , the sample start -end adress is still adjustable in sample one editor and thus non destructive .


When doing slip editing on the green sample and then drag dropping onto sample Impact xt , the sample start end adress markers are non adjustable outside their boundaries (start defaults to 0) , iow it has become destructive .


This depends from sample to sample and I have no idea why it treats certain samples differently

[gentleclockdivider]

These are two samples that when slip editing them in the arrange and drag dropping in impact , you can't adjust the start -end adress in impact xt >
The arrange slip editing was destructive
Can anyone test this , and why exactly these samples exhibit this behaviour
(Barry White and James brown drumloop )
https://app.box.com/s/r3axhzyyduyv8l6zrd2d2qq9ilzrqc8c
https://app.box.com/s/r3axhzyyduyv8l6zrd2d2qq9ilzrqc8c

[gentleclockdivider]

I am getting closer and I think it's a bug but not sure .
When slip editing + some fade in-out applied to the sample , the process has become destructive when dropped in sample xt ( sample start -end adress can't be adjusted outside the boudnaries )
The weird thing is that is also happpens to certain samples that have no fade in fade out .

[gentleclockdivider]

exact same issue with sample one
Here are two samples , adjust them in arrange view by moving start-end adress and drop them into sample one
The funky drummer sample is still adjustable , while the piano sample is not .
https://app.box.com/s/ek7rgqzk42zr7z8hr4kv25e2sptap6k3
https://app.box.com/s/wzoiei5ie26lrcgwt2jgvj2v9htezghr

[apoclypse]

These are two samples that when slip editing them in the arrange and drag dropping in impact , you can't adjust the start -end adress in impact xt >
The arrange slip editing was destructive
Can anyone test this , and why exactly these samples exhibit this behaviour
(Barry White and James brown drumloop )
https://app.box.com/s/r3axhzyyduyv8l6zrd2d2qq9ilzrqc8c
https://app.box.com/s/r3axhzyyduyv8l6zrd2d2qq9ilzrqc8c

I tried the files and sliced them and mapped them just fine in Sample One XT using the send to Sample One command. Btw, the files are both the same file. I don't know if you mean to use another sample there.

What version of S1 are you on? I'm not seeing this bug on my end.

Edit: I also tried dragging and dropping it into Sample One. No issue there either. Works as intended.

[apoclypse]

I am getting closer and I think it's a bug but not sure .
When slip editing + some fade in-out applied to the sample , the process has become destructive when dropped in sample xt ( sample start -end adress can't be adjusted outside the boudnaries )
The weird thing is that is also happpens to certain samples that have no fade in fade out .

If you think about it logically it makes sense. S1 is bouncing the file into a new file before it adds it to Impulse or Sample One because it assumes that if you processed the file (added fades, etc) that's what you would want to play back from the sampler. So if you just drag an unedited file into Impulse it will load the full loop. If you just add a fade to the file (even if you remove it) it's considered an edit and it will just load that sample slice destructively because it will bounce it before loading it in.

Logic Pro behaves the exact same way btw if you drag and drop an edited file into Drum Machine Designer. Bitwig does this as well but gives you the option of just using the raw file as well. Live just ignores all edits. Which is probably not what I'd want. I guess since Live doesn't have a bounce in place function it kind of makes sense.

[gentleclockdivider]

I am getting closer and I think it's a bug but not sure .
When slip editing + some fade in-out applied to the sample , the process has become destructive when dropped in sample xt ( sample start -end adress can't be adjusted outside the boudnaries )
The weird thing is that is also happpens to certain samples that have no fade in fade out .

If you think about it logically it makes sense. S1 is bouncing the file into a new file before it adds it to Impulse or Sample One because it assumes that if you processed the file (added fades, etc) that's what you would want to play back from the sampler. So if you just drag an unedited file into Impulse it will load the full loop. If you just add a fade to the file (even if you remove it) it's considered an edit and it will just load that sample slice destructively because it will bounce it before loading it in.

Logic Pro behaves the exact same way btw if you drag and drop an edited file into Drum Machine Designer. Bitwig does this as well but gives you the option of just using the raw file as well. Live just ignores all edits. Which is probably not what I'd want. I guess since Live doesn't have a bounce in place function it kind of makes sense.

no , you're doing it wrong
Don't slice anything , just download the two files and import them both into studio one
Adjust the start and the end position ( of the clip ) of both audio files , this is a NON destructive process ..like this

Now drop them both on a pad ( don't hold shift while droppping becasue this will automatically slice it when dropped ) .
The result is that slip edit data of the drumloop ( is still there once dropped , but the piano sample data is gone .


Somehow , the piano sample has undergone a destructive process will dropping it onto impact and or sample one , but there is NO new sample data in the pool
Result is that both samples are treated differently once dropped and is imho a bug

It has already been confirmed by at least 1 user who is on ethe latest version of studio one , I am still on 4.5

[apoclypse]

I don't know what to tell you I'm on the latest version. I don't consider it a bug as I think it works as intended.

From my testing it seems to be based on the metadata of the file. For example all of the newer files I used for testing worked non-destructively (Loops from Loopmasters or Splice). I could change the start end and points just fine and when I dropped it into Impact it had the loop points as you mentioned.

However when I dropped an older drum loop non-splice file it destructively copied the file. I'm not sure why but maybe some conversion needs to happen on S1's part to import it into Impact. When I did that no new sample data is created in the Pool but the sample does show up in Finder in the project folder (right click on the pad in Impact and choose show in Finder).

I verified this with 5 splice/loopmasters files (which work as you want it to) and 5 older non-splice files. All WAV 24-bit 44.1khz.

I don't know what exactly you are trying to get out of posting this as you are two versions behind. You can't even test if they fixed these issues you keep posting about. What is your goal exactly?

[gentleclockdivider]

I don't know what to tell you I'm on the latest version. I don't consider it a bug as I think it works as intended.

From my testing it seems to be based on the metadata of the file. For example all of the newer files I used for testing worked non-destructively (Loops from Loopmasters or Splice). I could change the start end and points just fine and when I dropped it into Impact it had the loop points as you mentioned.

However when I dropped an older drum loop non-splice file it destructively copied the file. I'm not sure why but maybe some conversion needs to happen on S1's part to import it into Impact. When I did that no new sample data is created in the Pool but the sample does show up in Finder in the project folder (right click on the pad in Impact and choose show in Finder).

I verified this with 5 splice/loopmasters files (which work as you want it to) and 5 older non-splice files. All WAV 24-bit 44.1khz.

I don't know what exactly you are trying to get out of posting this as you are two versions behind. You can't even test if they fixed these issues you keep posting about. What is your goal exactly?

Does it matter if i am two versions behind , and the goal is clear isn't it ?
I post it so users with later versions can verify or not , simple stuff really .
Like you said , it behaves different on certain samples even on the latest version .
If it's metadata that is responsible or not , probably

[apoclypse]

I don't know what to tell you I'm on the latest version. I don't consider it a bug as I think it works as intended.

From my testing it seems to be based on the metadata of the file. For example all of the newer files I used for testing worked non-destructively (Loops from Loopmasters or Splice). I could change the start end and points just fine and when I dropped it into Impact it had the loop points as you mentioned.

However when I dropped an older drum loop non-splice file it destructively copied the file. I'm not sure why but maybe some conversion needs to happen on S1's part to import it into Impact. When I did that no new sample data is created in the Pool but the sample does show up in Finder in the project folder (right click on the pad in Impact and choose show in Finder).

I verified this with 5 splice/loopmasters files (which work as you want it to) and 5 older non-splice files. All WAV 24-bit 44.1khz.

I don't know what exactly you are trying to get out of posting this as you are two versions behind. You can't even test if they fixed these issues you keep posting about. What is your goal exactly?

Does it matter if i am two versions behind , and the goal is clear isn't it ?
I post it so users with later versions can verify or not , simple stuff really .
Like you said , it behaves different on certain samples even on the latest version .
If it's metadata that is responsible or not , probably

It does matter because you are posting issues that could have been addressed already in later versions. Even if they weren't what's the point of having someone on a new version verify this for you? That's not going to change anything for you. Why not just download the S1 demo of the latest version and verify yourself (or buy an upgrade license)?

We've established that the "issue" is file specific. Great! So now that you know that what exactly does that change for you? I'm trying to understand what you are actually trying to achieve by posting this.