42 postsPage 3 of 3
1, 2, 3
Hi Robert,

Yes, they are all the loops that are included with Studio One Pro.
In those, there's all the effects, chord progressions, and single shots.

PreSonus also offered some loops from a company called "Nine Volt Guitars" which were added a few years ago... in there.
I've only added some thunder and rain loops myself into my soundset folder.

So to be clear, I used to be able to just drag and drop loops from those soundsets located on my external USB 3.0 1TB Western Digital drive (via the S1 browser) into my song and they always worked. I usually left them 'as is' and only bounced a few but not in every song, so I cound transpose, etc..

I had a couple songs to finish in 3.5.6 so after that, I upgraded to 4.0.1 and that's when the issues immediately started. I found the only way I could keep using the soundset files from my externnal USB 3.0 drive was to always bounce them. But now that I've moved them all to my internal SSD drive, I can once again leave them in their most virgin state. This I do so that I can only manipulate them if needed - cuz if I bounce here and there and make edits weeks into a song, I'm commited. 8-)

And yes I understand that if I load a bunch of "Instruments" that could cause performance issues or audio dropouts but the songs that exhibited this when I first started using 4.0.1 were very simple and short arrangements. I've since removed the folder containing my test songs and files since I've resolved this issue for myself... but it doesn't answer the question as to what PreSonus changed in version 4 that now causes this?

Scott

Please add your System-Gear-Info to your Profile here.
-S1 Pro 5.5.2. Win11 Pro 22H2. Behringer UMC404HD. Melodyne Studio 5.3.1.018.
-MSI 12th Gen i7, 16GB, 1GB SSD x2, 7200rpm 2TB HD, NVIDIA RTX 3060.
-EZD3 & EZD2. Helix Native, Scuffham S-Gear. iZotope Ozone 5.
-Akai MPK249. 6 Guitars. Line 6 Helix LT, 2 POD's & an E-bow. 8-)
-Adam Audio T8V's. Dual 28" ViewSonic Displays. Rode NT1. SM58. Original Faderport.


-Just My Songs
-My Previous Band: 2GUYZINABASEMENT
User avatar
by snb1 on Tue Sep 04, 2018 11:22 am
snb1 wroteI've had the same problem for a while now dating back sometime in v3 and was one of the main reasons I couldn't dive into audio manipulation like I wanted to. Until today when I came across this post and seen you have the same issue so I was inspired to find a work around. I found that if you put Melodyne on your audio before any time stretching, everything will work fine. So pretty much treating Melodyne as the time stretching engine if that makes sense. Try it and let me know if it works for you.

Disregard this message, this is not a good workaround lol. Im going to tryn and reboot and see what happens because this is getting real annoying.

Studio One Pro 6.6 64 bit, macOS Monterey 12.6, 14" MacBook Pro M1 (2021),16gb ram, 512 SSD, 8-core CPU

SkipNo Beet

42 postsPage 3 of 3
1, 2, 3

Who is online

Users browsing this forum: jordanslator and 42 guests