• Hi and welcome to the Studio One User Forum!

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

Bug with Impact XT when using an audio clip for slicing samples

Crossinger

Active member
Hi there!

I think I found a bug while playing around with the Demo of Studio Pro 8.1.1. It's affecting Impact XT when slicing drums from audio

Steps to reproduce:

  1. Drag a stereo song file into the arranger of Studio Pro
    (Note: I had a YouTube stereo audio file in m4a AAC format, but I don't think it's important here)

  2. Trim the audio at the beginning, cut of the trailing part (I wanted to have the drum only intro)

  3. Drag an Impact XT to track 2 and open it

  4. Now the important part: Drag the trimmed event clip from the arranger window onto Pad 1 of Impact;
    Hold shift to slice it and drop it.

  5. You see the slices in the waveform pane - fine! Confirm with a click on the "Slice" button

  6. Now the drums are spread across the pads - OK!

  7. Click on Pad 1, listen, trim the slice with beginning, end, maybe also do a fade out

  8. Click on Pad 2
Here the bug happens: The Waveform display tells me "File not found"

1786041492306.png


But that's not true. The slices are still there and can be played via pads. I just no longer can edit them in the waveform pane.

My assumption: Impact somehow loses the connection the the trimmed event clip which is not a dedicated entry in the pool.

Workaround: First Bounce the trimmed event clip to a new track. Use the new copy for the steps above. Then it no longer happens.
But I see this as an unnecessary extra step. IMHO it should work as I described above.

Can anyone confirm this?

If yes, then I'll file a bug report within the next days. :)

Thanks for reading!
J.
 
I followed your str but I didn't get a "File not found" notice. I did butcher the sliced samples quite harsh up to sample 5, but I was able to switch back and forth between all of them, no issues, playback as per butchered modifications.
File was a 44.1 kHz 16 bit stereo mp3
 
Followed your Steps. Can`t confirm. I used a Stereo 44.1kHz 24-bit wav-file with a lenght of 24s. Hope this helps.
 
Hi there again!

Thanks to both of you for taking the time trying it by following my description. Today I took some time to do some further investigation. Here's what I can rule out so far:

1. File format (does also happen with e.g. wav files)
2. Filename (I suspected "special" characters, but nope - all good!)
3. Editing sliced samples (my step 7. in my first post) - no need to do so!

I could narrow down the issue a bit, but this causes a bit of a head scratch (and needs further investigation on my side):

It seems to work if the sample origin is a "known" folder. E.g.,

<username>/Music/Samples/Drumkits

This folder is a shortcut in the browser ("Files") --> then it works

My original file was located in a different folder that had nothing to to with my music and sample archive. --> bug occurs
I also tried it with my system "Downloads" folder, which is well known across my system. But again --> bug occurs

So it must have something to do with the file location. And that would explain, while the bounced copy never fails: it is placed in the project folder and this is also a "known" folder.
 
Last edited:
Just a thought: has SP access rights to the drive the original file lived on? Also, is this drive fast enough and not network / cloud accessed?
 
Just a thought: has SP access rights to the drive the original file lived on? Also, is this drive fast enough and not network / cloud accessed?
Good thought!

But no: This specific file is on the same (internal) SSD on my Mac as my other files and in direct "neighborhood" of my Music folder. And if I can drag my file into Studio Pro's arranger window, and it works, then I assume that Studio Pro has the necessary access rights.
 
Addendum: needless to say it works as expected (without bouncing) in Studio One 7.2.3. *sigh*
 
Have you tried other file formats to make sure this isn't isolated to m4a aac?
 
Have you tried other file formats to make sure this isn't isolated to m4a aac?
Yep, I converted my original file to wav (using Ocen Audio) and also tried it with another file that originally was a wav.
Unfortunately didn’t have time today for further investigation.
 
Last edited:
Yep, I converted my original file to wav (using Ocen Audio) and also tried it with another file that originally was a wav.
Unfortunately didn’t have time today for further investigation.
Bummer

So far, it's Win users reporting no problems. Maybe some Mac users will chime in
 
Back
Top