5 posts
Page 1 of 1
Hi, Studio one 5 pro song not loading when Atom SQ plugged in. Has anyone had or having this problem? as soon as I unplug Atom sq the song loads.
User avatar
by larsfrueauff on Fri Dec 18, 2020 5:31 am
Hi Lauren,

yes i have had the same issue, it was an older S1 V4... Song.
Saved as an V5 File - all fine.

After this, no problems with this at all.

Regards

Lars
User avatar
by Bbd on Fri Dec 18, 2020 7:56 am
laurentaylor2 wroteHi, Studio one 5 pro song not loading when Atom SQ plugged in. Has anyone had or having this problem? as soon as I unplug Atom sq the song loads.


You should post your specs.
Please contact Support about your issue.
Thanks.

Bbd

Please add your specs to your SIGNATURE.
Search the STUDIO ONE 5 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


OS: Win 10 x64 Home, Studio One Pro 5.x, Notion 6, Series III 24, Studio 192, Haswell CPU: i7 4790k @ 4.4GHz, RAM: 16GB, Faderport 8/16, Central Station +, PreSonus Sceptre S6, Eris 3.5, Temblor 10, ATOM, ATOM SQ
User avatar
by PreAl on Tue Dec 29, 2020 1:19 pm
Show a screenshot of your atom device inputs and outputs in studio one.

Studio One Pro 5, Faderport Classic (1.45), Atom Pad, Atom SQ, Presonus Studio 26c, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).

Intel i9 9900K, 32GB RAM,
EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
User avatar
by AlexTinsley on Thu Jan 14, 2021 10:59 am
We've gotten a few reports about this on Windows systems exclusively and are investigating. This comes down to system optimization. Making sure your system has all the correct device drivers for your chipset and embedded USB device controllers.

The Atom SQ is a class compliant device, we're not providing any device drivers to make this work with the OS, instead Atom SQ relies on the operating system to provide a method by which it communicates through standard USB connectivity. However Windows has it's own device drivers for the CPU and USB Chipsets that our device relies on to communicate.

We found a case where someone was using the Intel C230 chipset for an X79 CPU, an older INF driver that was installed with Windows 10 displayed this issue, when an updated the chipset INF driver from Intel was installed, the problem went away.

Make sure the chipset driver for your computer is up to date, it appears that the chipset driver that controls USB found in some Microsoft Windows 10 installations is older / out of date compared to newer chipset drivers provided by either Intel or AMD directly on their websites.

Depending on what system you're using. Windows update does not always update these drivers and the user must update these manually.

This is most likely to occur with systems that:
* Systems that did not originally come with Windows 10 as part of their original configuration
* Mobile / Laptops that originally shipped with Windows 7, 8 or 8.1 where Windows 10 was not part of the original install.
* * Even older Windows 10 systems from 2017 are seen to have this issue too.
* Custom built enthusiast systems, where Windows will install it's own drivers and the system builder may not load the drivers provided by the motherboard vendor's website (or from install disc that came with the motherboard).

To see what chipset your system is running, open up Device Manager.
The fastest is to hit Windows Key + X and hit the letter M
In the list of devices you'll see a list of + signs, click on the + sign where it says "System Devices"
Scroll down till you see something that says "Intel Series Chipset Controller" there will be some numbers after it. Should look something like this, your chipset may be different than in my example.

Win10_DevMgr_SystemDevices_Chipset.PNG
Windows 10 Device Manager System Devices Chipset Example


Then do a web search to find the updated driver for that chipset. If you right click and select update, it will only update what Microsoft has on file (which is not what you want), if you do a web search you may get a newer driver from Intel (or AMD) that is newer than what is in the Microsoft archive. (this is preferable)

That may resolve it, however you may also need to update your USB chipset driver. The next thing to check is to update your USB Device drivers. Same as before, Microsoft keeps older versions on file for Windows update, doing a web search manually may find you newer USB chipset drivers.

To see which USB chipsets you have in your system go back to Device manager and select in the list where it says Universal Serial Bus Controllers. It's not uncommon to find two different USB chipsets in the same system. Motherboards often have one brand chipset for the back panel riser and another for the front panel ports. In my case I have that and some expansion cards installed so my USB Series Controllers looks like this:

USB_Series_Devices-DeviceManager.PNG
Windows 10 Device Manager - Universal Serial Bus Series Controllers Example


This may not be exclusive to Intel, the same issue may occur for AMD. This does not appear to happen with any macOS systems.

Also see this article on USB 3.0 chipsets (while it was written for AudioBox USB), has info and links to vendor sites for chipset specific drivers. https://support.presonus.com/hc/en-us/a ... h-USB-3-0-

If you try all these things and still don't have any luck we've found in some cases where inserting a USB Hub between the computer and the Atom SQ will resolve the issue.

Using a powered USB-C to USB-A (x4) hub appeared to work, and it worked with or without the power cable attached, including having the Atom SQ go to sleep when the computer goes to sleep. We used the RSTech USB-C 4 Port Hub (Amazon Link) worked in our testing of this issue that provided a clean start up with Studio One each time.

While in other tests using a USB-A to USB-A hub worked only partially where one port worked but the others did not. Many passive hubs only replicate one port effectively and then just make copies of the first port (acting more like a splitter than a hub), your mileage may vary with unpowered hubs.

I know this was a lot, but if any of it helps, please let us know.

Knowledge Base Version of this post:
https://support.presonus.com/hc/en-us/a ... Windows-10

Forum Admin
Please add your specs to your SIGNATURE.
Search the STUDIO ONE 4 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.

5 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 1 guest