18 posts
Page 1 of 1
I seem to be having a problem. When I had 16 GB RAM I had the same problem, now I have 32 GB RAM and I still have the same problem. Studio One takes ALL the RAM. For MIDI recordings with just a few actual instruments with a few fx plugins on each. I am in the 20-30 actual tracks range.

All the tracks in the recent example of this, were MIDI tracks (instruments on about 10-20% of the tracks). The sample libraries are not very big. There are no pianos for instance. Today the following instance happened during a Live Stream (over the network) while recording 74 minutes of 20 MIDI tracks from 7 controllers:
I looked up after recording for 20 minutes (all midi tracks) and the RAM/SWAP (seen in Rainmeter of the S1 recording computer, (not the streaming computer)) was at 20/27.
I looked up after recording for 74 minutes (all midi tracks) and that RAM/SWAP was at 99/93.

I don't know how to get this under control. It takes around 1/2 hour for such a recording to resolve. I checked resource monitor and the In Use of the physical memory was maxed. Studio one was using between 19 and 21 GB. The computer was using an additional 7-8 GB for its other operations. There was a reserve of 3-4GB. (see screenshots on the Google Drive link)

All this for 7 MIDI controllers, and no audio tracks whatsoever. About 20 MIDI tracks I estimate, were being recorded simultaneously, for a total of 74 minutes. This same type of thing was happening when I had 16 GB RAM (6 months ago I added an additional 16). I record at 1024, 48kHz.
You can see, it was a live stream on Periscope and I recorded the 20 MIDI tracks for 74 minutes of the live stream: https://www.periscope.tv/w/1RDGlQVQzkdJL

Here are some screenshots of the task manager, details of Studio One, performance monitor, RAM after the recording, before it finally resolved, and then again the open session, after the recording resolved, and then saved.

Interesting the last shots (you can see the time in the clocks of Rainmeter) here, (all screenshots) shows that Studio One was resolving as a shadow process for a few minutes after closing the program, and using something like 4.5 GB (greyed out in performance monitor Memory at top). https://drive.google.com/drive/folders/ ... sp=sharing.
The computer was never connected to the internet, only the LAN during this whole recording.

Are there some experts who can help me understand why the memory use jumped so high, and what I can do to keep it more under control?
Last edited by jebbyslonar on Mon Jun 07, 2021 4:14 am, edited 1 time in total.

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by Bbd on Fri Feb 07, 2020 7:37 am
You did not provide your specs as we always like to see.
For your issue, please contact Support.
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 jebbyslonar on Fri Feb 07, 2020 3:23 pm
8 core ryzen 7 1700 computer
32 GB RAM
Windows 10
Studio One, 4

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by scottyo7 on Fri Feb 07, 2020 6:20 pm
While you're waiting for more specific support, this previous post may help you understand a bit more about system resources. :roll:

The thing that jumps out at me is that it seemed you said you're 'streaming'.
Either you're recording while streaming or just doing playback of the tracks?

Either way, using Ethernet or WiFi while simultaneously running Studio One seems like a 'no-no'. All Audio optimization guides I've seen/read say to turn off WiFi and your NIC while running your DAW.

If I'm off tangent here, please forgive me for having you read this. 8-)

Please add your Signature/Info to your Profile here.
-ASUS i7 Laptop; 16GB; 2 Samsung SSD's; NVIDIA 670MX; Win 10 Home v20H2.
-S1 Pro 5.2.1; EZD2 2.1.8. A/I: USB Behringer UMC404HD.
-Synths: Camel Audio Alchemy, Air Tech Music Suite, UVI Digital Synsations & SONiVOX Twist.
-Melodyne Studio 4.2.4. Ozone 5, Scuffham S-Gear 2.97.
-Akai MPK249. 6 Guitars, two Line 6 POD's & an E-bow.
-Fluid Audio 'FX8' Monitors; Dual 28" Displays. Rode NT1; SM58. Original Faderport.

-Just Me
-Previous Band: 2GUYZINABASEMENT
User avatar
by robertgray3 on Fri Feb 07, 2020 6:36 pm
scottyo7 wroteusing Ethernet or WiFi while simultaneously running Studio One seems like a 'no-no'


I've done video conferences and stuff while working in my DAW all the time. Works OK, as well as streaming does these days I guess. It makes it harder to troubleshoot the RAM leak but the solution doesn't have to be "never stream ever."

Mac OS X Catalina 10.15.7
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2
User avatar
by jebbyslonar on Sat Feb 08, 2020 5:32 pm
Pro Tools rose from 16 or 17 % to 22 or so.. Today. I was meaning to go for a similar test run and a 74 minute record. It couldn't happen cause every little thing I had to do in Pro Tools required a stop and start of the recording. Like, Pro Tools required a stop of the play for changing track visibility and bringing up a different memory location. And Pro Tools required stop of the play for introducing new plugins to the session. Nothing like Studio One.
Well I got the Pro Tools set up and tomorrow or soon I will do the comparison over the similar 75 minute stretch.

I continue to stream. It is no no no. It is just a different world now than in the earlier times. Things are much different. I have no issues whatsoever with uploading the 6-8 MB of a 2500 kbps video stream and 192-320 kbps audio to the network (I stack the graphics up and stream from the other computer to the internet).

With an AMD computer anything is possible. My i7 still staggers under just a few graphics being thrown at it but the AMD doesn't blink no matter what I throw on a session.

I will check your post about RAM but I doubt there is anyone with any info about the current thing I've been dealing with. It used 10-11 GB when I had 16 GB RAM, now it uses 20 as I have 32. Just hogging all the ram...just for MIDI only recordings. Makes no sense to me. The photos I showed via the Google Drive link indicate that it is Studio One using the 20 GB and not something like OBS.

Even If I used all 10 fingers to record poly aftertouch say, half the time, MIDI alone shouldn't push it much above 1 solitary GB.

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by jebbyslonar on Sat May 01, 2021 4:14 pm
I believe I have finally located the problem. I recently picked up on using S1 again after about a year of non use, at least 8 or 9 months using other daws.

Also Recently I found a massive 13 GB hiberfil file in my c drive. I used a registry change to stop Windows creating the hiberfil, and a command to turn off hiberfil while in safe mode. The key trick is to run the command in safe mode. The Reg Edit you can do while running Windows normally. There.

I attribute my recent absolute success to my removing that hiberfil successfully. I have attatched a picture of the detail how to remove the hiberfil in case anyone else is seeing swap (you can see this in the default rainmeter skin that comes with Rainmeter) going above 85 to 90 or so, evidenced by massive freezing of Studio One at the end of a 1 hour recording of many midi tracks. (this is what I was doing, MIDI mostly but the program would stall for 1 to 5 minutes at the end of the long recording and I would have to wait. (Reading above it says a half hour to resolve...I had forgotten it took sooo long, but I must have been stating my observations of the time)

Now my swap stays in the mid 20s percent wise, even on those long sessions an hour or more.
Still doing everything else the same as I was before still use network, still using 2 interfaces on the computer, many midi devices. Etc. Now using the most recent Studio One.

Still can only guess that this hiberfil was what the problem was, since I am now using more updated Windows probably, and also more updated Studio One. Even possibly a smaller session, though I have not experienced any swelling of that SWAP (again anyone who wants to see "SWAP" should get rainmeter and install just the default skin that it comes up with the first time you use it) Not a well controlled experiment but it is completely ok with me because that studio one just works a lot smoother than it was a year or more ago.

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by jebbyslonar on Thu May 20, 2021 6:49 am
a week or 2 later. Just can't say it's been great. Still experiencing problems, but now instead of getting to the end and freezing for a half hour, it is just freezing forever and never coming back so I now gotta just task manager it.

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by Vocalpoint on Fri May 21, 2021 3:41 pm
jebbyslonar wrotea week or 2 later. Just can't say it's been great. Still experiencing problems, but now instead of getting to the end and freezing for a half hour, it is just freezing forever and never coming back so I now gotta just task manager it.


Took a look at a few of your screencaps from 2020 - to me - it's looks as if your RAM is completely exhausted and hence a lockup etc.

Regardless of machine, CPU (Ryzen) or power - if you let a herd of VSTi's run rampant - they will use all the RAM - and this has little to do with S1.

Would love to see what "7 MIDI controllers" you are running and what VSTis are connected to them to get a sense of where all the memory is going. And don't let Task Manager make you think it's all S1 stealing the RAM - I believe all the processes (like say Kontakt with a larger library or two) appear as being part of the S1 memory footprint under Task Manager - when in actual fact it's Kontakt taking as much memory as it can.

You need to get specific about how many tracks you have, what's on them and what VSTis are actually in use here. Any song with 20 or 30 or 40 tracks full of VSTi's is going to have some resource issues - eventually.

VP

Studio One: Professional v5.3.0
DAW : Custom Built | Intel i5 10600k | ASUS ProArt z490-Creator | 32 GB RAM | Windows 10 Professional 20H2 (March 2021)
Interface : RME Multiface 2 (with Driver/TotalMix v4.26)
User avatar
by jebbyslonar on Mon Jun 07, 2021 3:28 am
Vocalpoint wrote
You need to get specific about how many tracks you have, what's on them and what VSTis are actually in use here. Any song with 20 or 30 or 40 tracks full of VSTi's is going to have some resource issues - eventually.

VP


I have got kontakt installed but i haven't used it in a while. It's definitely not in these sessions. On the other hand I have got a lot of midi controllers and they have aftertouch which has a lot of points of midi. Also recording some CC MIDI from some. Now I am getting quite a few BSODs, lately. Also running OBS of course, and 3 interfaces now instead of the 2 from before as I've over the weekend attached my Audiobox 96 (2 in 2 out lowest minimal interface from the Presonus line) Of course I'm only using 1 interface for audio (no ASIO4All) and the other 2 are just MIDI ins or outs. It's probably the resources, but still My rainmeter skin lists Swap around 50% and I did ditch that hyberfil file. It's a pain to lose the sessions. Not a huge deal, a half hour I have always got the audio and session recording from the OBS in the network attached computer. I use a few VSTs, One thing I have noticed is that it seems to be the (synergy program derived) network mouse that causes problems. I have a video where I can see myself cutting back across the divide and the swap on the computer with Studio One goes cut in half when the mouse lands on the other computer with a click. Also I have had the BSOD directly on mousing into the other computer after STOPPING the recording while it is still finishing (during the freeze). The mouse lands in the other computer and BANG a BSOD in the Ryzen ASUS. But this is possibly a coincidence as there are times when I don't do it with the mouse (like today) and still get a sudden BSOD shortly after the freeze sets in.

I have to save more often, less than a half hour, or it will BSOD, this is just the last few weeks. Using a few Presonus reverb plugins and 7 or 8 from other sources are the FX I guess I should try to cut back but it's just a sound I made about a week ago anyways, and only 3 tracks of interface input external audio (which is 5 total tracks, 1x mono + 2x stereo) but more than 10 tracks of MIDI. 4 VSTis I used during today's BSOD were black noh snare and Dark VX Bass Drum (both by same maker KVR chokehold), and 7 FX on 2 seperate percussion/hats (both from Beatstep Pro sequences) (BSP Channel 2 and 10)) are both Eight Voice from Cherry Audio x2 But I did not record those 4 vsts as any audio only just the midi. Mosts of these plugins are visible in one pane on the MIX and it shows over 10 plugins. I will put a screenshot there's nothing off screen vst-wise.

Attachments
Screenshot (456).png

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by robertgray3 on Mon Jun 07, 2021 7:46 am
This is simpler to solve than you're making it. Every time I had a plugin doing this it was just a case of opening Task Manager and removing plugins/instruments/devices one at a time until I saw all the RAM get freed up. If the RAM *doesn't* get freed up then usually closing the program will freeze or crash. On macOS we can do a spindump to show why a program is freezing or look at the crash report and usually in one of those two it will show what isn't giving up the memory. I think Windows has an equivalent but it's a little more complicated, same principle though.

Mac OS X Catalina 10.15.7
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2
User avatar
by jebbyslonar on Sat Jun 12, 2021 5:30 am
I don't have the Mac. I can't solve this problem. It happened again today. I was able to record an early 27 minute live recording then the 2nd recording stopped and BSOD. I don't see anyplace in taskmanager for plugins. Sounds like something you might find in Studio One..IF s1 wasn't frozen.

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by jebbyslonar on Sat Jun 12, 2021 6:33 am
Ok, I just did another recording in the same session as that earlier I had the BSOD on, and this time, after a 10 minute recording, I did a 15 minute recording, and both stopped well instantly with no freeze.
Only 2 things different one is I was still here on the internet after my last post less than an hour ago, the other being that after the earlier recording of over 20 minutes, and BSOD, I went in safe mode and ran device cleanup, which completely removed every device on my system (not in use by safe mode, obviously). That may be what got me back to the pleasant state of full stop on a dime after recording.

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by jebbyslonar on Tue Jun 15, 2021 12:12 am
Reminder to remove all devices in safe mode with device cleanup, as it (recording) worked again yesterday to record over 20 minutes and full stop after about 5 second count from pushing the stop button to green and red lights going off and blue square lighting showing the recording was resolved. Seems like the thing to do at this time is to delete those devices in safe mode. Just select all then delete. Yesterday's record was on the same cycle so to speak after the initial remove of devices I mentioned 2-3 days ago. Perhaps something that needs to be done when it starts acting up, but not before then.

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by jebbyslonar on Sat Jun 19, 2021 8:35 am
After this much time about 2 weeks now, yesterday upon recording a 20 minute recording, it went almost a full 30 seconds before resolving and blue stop button light coming on after pushing stop to end the 20 minute recording. Recording basically the same amount of tracks + or - an external instrument recording in every case, this time having selected a track and moved it from a lower slot to an upper one in the sequence. That could be the reason for the 20 extra seconds to get from Green+Red Record play lights to the Blue stop light. Thinking it is time to do the device delete again.

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by jebbyslonar on Thu Jul 01, 2021 3:08 am
2 weeks more of testing I do a recording session every day almost, and I got up to a 56 minute session 2 days ago. This did not BSOD, and resolved after a half minute to a minute, which I thought was too long. I had deleted devices as stated in the previous post, so it looks like I did several sessions without deleting devices, and had no problems stopping the recordings. Working from same template in all. Was up to a recording of 40 minutes, a few of 30 minutes, several 20 minutes and finally this 56 minute recording, all since that most recent device delete in safe mode I mentioned in my previous post.

The USB device deletinon has caused more problems, almost than it's worth, it would be good if there was a way around this problem without it, but it's good it works. The other things that get deleted are things such as USB Devices, which you should remember afterwards to go in device manager and re disable windows power management setting which is a real nuisance (anyone who works in AUDIO in Windows for any amount of time knows about Windows stupid and unchangable POWER MANAGEMENT, an UTTERLY USELESS function that keeps turning on no matter what you set your POWER PLAN to do, and ALSO keeps turning on despite REMOVAL of BATTERY from a laptop, which begs the question "WHY would I want to SHUT OFF MY OWN USB DEVICE MID SESSION by DEFAULT?"). I have had MIDI devices shut off mid recording which often causes problems with Presonus Studio One software freezing. You will also have to rediscover all audio ins and outs in OBS, and any USB cameras there after a device delete.

Haven't done any testing to see what device is causing a build up in what I will call the Studio 1 cache because I can't say why it's happening any other way. It could be an incorrect term but that's what it acts like a real big cache. it's a pretty long list. I guess I would start with interfaces and MIDI but who knows which device is causing it. Suffice to say that you will have to redo your settings for Power Management of USB devices, and also input any wifi password again (deleted network device) Aside from those problems it's an ok solution. Pretty much not having a BSOD outweighs a few things to re enable or redefine every 12 days or so.

computer1:
ASUS ROG GL702ZC
AMD Ryzen 7 1700 (8/16 cores)
32 GB RAM
Studio One Artist 5.2 May 2021

USB ARRAY 4 ports:
1 C: M Track 8x4 interface (Default for S1) MIDI i/o is System 1m;
2 A: FTU8R MIDI in fr P10 out
3 A: 4 hub, -Presonus AB96 MIDI fr P10 thru, -Cam, -MPK MINI, -Xk25
4 A: 7 hub -MsftLCamStudio, -PSATOM, -Xk37, -Pr10, -ABSPro, +2 idle


Network:
NDI, Mouse, MIDI


computer 2:
Razer 4/8 i7 7700 32RAM
USB ARRAY 4 ports:
1 TB: 4 hub: -Xk25, -??, -MsftLCam3000
2 A: -FTU8R MIDI i/o BSP
3 A: 4 hub: -MseKbd, -SDXL -JP08, -Mk3
4 A -FTU MIDI in is Oxygen 8 v2
User avatar
by Vocalpoint on Fri Jul 02, 2021 9:48 am
jebbyslonar wrote2 weeks more of testing I do a recording session every day almost, and I got up to a 56 minute session 2 days ago. This did not BSOD, and resolved after a half minute to a minute, which I thought was too long.


Must admit - have been keeping this thread in my scope for about a month now - and I still do not know what exactly the issue is. Is it constant BSOD? Is it S1 dying after 50+ minutes of recording? Is it too many MIDI devices? If you could boil this down to one sentence it would help.

For the record - and to ensure clarity is paramount - if you ever see a BSOD in WIndows - it is 100% guaranteed - with zero exceptions - to be a hardware issue.

Every BSOD will post a problematic (but very often) cryptic message when a BSOD occurs. All BSOD's are recorded to mini dump files and all can be examined with tools like BlueScreenView:

http://www.nirsoft.net/utils/blue_screen_view.html

Suggest you download this small tool and examine all the mini dump files that have been created since this thing started for you and see what it tells you.

In all my experience - all BSODs I have encountered have a logically and traceable hardware specific driver that is interacting with the OS in a negative fashion. It is never the fault of the source application (like Studio One).

Now - S1 may very well be calling this idiotic driver within your sessions - simply because this device driver needs a very specific action to occur before it then interacts with Windows and sets off the BSOD.

But do not blame S1 - it is simply the messenger here for (what I believe) is a much lower level issue occurring with some driver component on your machine.

For further fun and games - and trust me - this one was truly bizarre - a few years ago just when I switched from Win 7 to Win 10 - I suddenly started getting a crap load of BSODs (on my DAW) that naturally I blamed on the apps in use or the hardware on the machine - it took me about 5 days to analyze this and I still could not come up with the actual issue.

After some super obscure last resource digging - it turned out to be the power supply of the actual PC that needed replacing. Once a new one was brought in - have not a had even the hint of a problem.

The bottom line - EVERYTHING is in play when dealing with weird BSODs. It is never obvious and in all cases I have ever seen - it's a 99.99% certainty that your issue lies elsewhere - far away from S1.

Cheers

VP

Studio One: Professional v5.3.0
DAW : Custom Built | Intel i5 10600k | ASUS ProArt z490-Creator | 32 GB RAM | Windows 10 Professional 20H2 (March 2021)
Interface : RME Multiface 2 (with Driver/TotalMix v4.26)
User avatar
by PreAl on Fri Jul 02, 2021 10:21 am
Indeed. What exactly is the BSOD error message, and what is happening within the windows event viewer?

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.

18 posts
Page 1 of 1

Who is online

Users browsing this forum: fmaestas and 18 guests