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

[concealed identity]

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

I'm trying to understand what you are actually trying to achieve by posting this.

They have an issue that seems irregular, and they were looking to find out why it's happening, whether it's a bug or setting or something else, and solve it.

[gentleclockdivider]

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.

Are you just being stubborn for the sake of it ?
We know that it's file specific , great ....next on the agenda , why exactly ? -
What I am actually trying to achieve is that once I know what the differences are in the files I can rectify the issue by changing it ( if possible )
Did you ever betatest anything (rhetoric question ) ?, because that is the procedure

[apoclypse]

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.

Are you just being stubborn for the sake of it ?
We know that it's file specific , great ....next on the agenda , why exactly ? -
What I am actually trying to achieve is that once I know what the differences are in the files I can rectify the issue by changing it ( if possible )
Did you ever betatest anything (rhetoric question ) ?, because that is the procedure

I'm not being stubborn. I'm asking what your next steps. If it's an issue with the files. What are you going to do to pinpoint that issue? Are you going to use a metadata editor to compare the files? Once you do have that data what are the next steps?

I have beta tested (I'm part of several betas actually) before but usually we are given a baseline. You weren't exactly clear about what the issue is so I tested as best I could given the information you gave. You didn't post that you were on 4.5. Which does matter. I don't know if the issues you are having is because of the version of S1 you are on. So if it doesn't happen on my install (6.6) I'm going to assume it's user error (like the Cold Sweat drag and drop issue).

For the other issue/behavior. You posted the same file twice so I couldn't test that properly. You didn't provide the Piano sample so I couldn't even check to see what issue you were having there. Again if you are talking about beta testing, usually accurate information is provided of what actually needs to be tested. I went out of my way to test with my own files to verify what was happening and found that it seems to be the files and most likely the metadata. I was going to look at the metadata of the files but I've wasted enough time here I think. I'm assuming you are more than willing to do that on your own.

[gentleclockdivider]

Ok , I found out
When slip editing +dropping a sample when the bitrate is too low , studio one will automatically increase the bitrate and thus making it destructive it then keeps a copy in the temp project folder ( right click a pad to see if it did ) .

Edit :cried victory too fast , I have two files that are both 1411 Kbps , one is affected the other is not but something tells me it's about the bitrate