15 posts
Page 1 of 1
|
Hi there,
I am using: MacBook Pro (2017) - OSX (v10.12.5), 64 bit, 2.7 GHz i7, 16 Gb DDR3 // Studio One 3 Pro (Version: 3.5.1 build 43560) // Presonus Faderport 8 // Softube Console 1 Studio one (Pro) will not load two of my songs. When you try and load one, it gets through all of the plugin loading messages but as soon as it displays the “loading song” message it crashes. The Mac problem report displayed immediately afterwards mentions the Softube Console 1 plug in at the top: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_c.dylib 0x00007fff8f023b52 strlen + 18 1 com.softube.StripControlPI_VST_AU_Protect_VST3 0x000000013eb5da4e 0x13dfd7000 + 12085838 2 com.softube.StripControlPI_VST_AU_Protect_VST3 0x000000013eb5ed46 0x13dfd7000 + 12090694 3 com.presonus.vstservice 0x0000000129d90953 0x129d77000 + 104787 4 com.presonus.vstservice 0x0000000129dbd4de 0x129d77000 + 287966 5 com.presonus.studioone2 0x000000010bd09321 0x10b2d8000 + 10687265 6 com.presonus.studioone2 0x000000010b86a5d9 0x10b2d8000 + 5842393 I am using the VST3 version of the Softube plugin, there is a VST2 version but it doesn’t integrate well with S1. If I disable the VST3 plugin service in S1 the song loads and tells me that the 30+ Console 1 plugins (and the single instance of the Saturation Knob plugin) were not loaded - as you would expect. I can then edit the song as normal. If I save and reload the song (with the VST3 service active) it crashes again (I have tried re-saving the song with a new song namer before restarting the VST3 service but it made no difference). I have restarted the Mac several times, but no change. I have the most recent version of S1 Pro installed. On a tangent, SI crashes about 80% of the time after quitting normally. It seems to close normally but the Mac problem report opens (immediately) with a message, but not mentioning the Softube plugin: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.presonus.studioone2 0x000000010c7312a5 0x10c145000 + 6210213 1 com.presonus.studioone2 0x000000010c6a0b82 0x10c145000 + 5618562 2 com.presonus.studioone2 0x000000010c6b11b9 0x10c145000 + 5685689 3 com.presonus.studioone2 0x000000010c6c7742 0x10c145000 + 5777218 4 com.presonus.studioone2 0x000000010c6cdd43 0x10c145000 + 5803331 5 com.presonus.studioone2 0x000000010c6dd96e 0x10c145000 + 5867886 I am worried about using the Softube Console on more songs, and about the songs it is already on. It has been used heavily across all of my SI songs (about a dozen so far, I only started using S1 about a month ago) and I don’t want to lose the plugin settings if possible. I have only been using this Softube C1 for a couple of weeks and the crashes started then. But the random exit crashes have happened from day one using S1 (about four weeks). Do any other Console 1 users have a similar issue? And is there any way of salvaging the songs and plugin settings? I have contacted Softube support. Thanks, Darren |
|
Is there anyone out there using Stdio One and the Softube Console 1 successfully?
Are you using a Mac? Cheers, Darren |
|
Presonus have come back with a workaround which has worked for me so far:
Start Studio One, go to Preferences > Advanced > Services and turn off AU, VST, VST 3 support and then load those songs and turn off Low Latency Monitoring in those songs and save them. Then close the songs, turn the plugin services back on and restart Studio One. There is a known issue with SoftTube Console 1 and Studio One 3.5.x's new low latency monitoring and SoftTube is aware of it. Hopefully Softube are working on a permanent fix, but for the moment not using low latency mode has fixed it. |
|
I'm on Windows 10. I just setup Console One yesterday morning and did a mix with it last evening with no trouble. This morning I started another project and just about had the drums done and it locked up. Restarted the machine, loaded the project and it locked up again much faster, hence I'm looking for information on this also.
I do have Console One on a hub, and that's been reported as a potential problem, so that's going to be my first adjustment. It would be great if that's it. https://www.softube.com/index.php?id=co ... own-issues Donny |
|
I am using the Console 1 on both Mac and Windows and have no problems.
Only thing is the need to turn off low latency when I use a guitar amp plugin like the UAD Fender Tweed 55 after MIDI inputs and low latency to be able to hear the plugin...
Forum Moderator.
Please add your specs to your SIGNATURE. Search the STUDIO ONE 6 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. AMD Ryzen 7 3800X 8-Core 3.90 GHz Windows 10 64bit Home, MacBook Pro + Mini Big Sur, SO 5.5 Pro, SO 6.1.1 Pro, LUNA, Cubase 10.5 Pro, SLIII32, 24.4.2, 16.0.2 FW, Quantum 2626, Faderport 8, FaderPort 16, Atom, Atom SQ, Console 1+Fader 1, UA Apollo Twin TB/USB, Toontrack, NI Komplete 12, ++ |
|
I've been happily using C1 with S1 on Win7 for the last few months.
I've done half a dozen mixes with it and some larger sessions, 50+ tracks and have not had any issue at all. In fact, I could not be happier with the combination of the DAW and the plugin/controller. I use less plugins overall,the mixes sound great, actually comparable to mixes I've done on SSL's. I'm pretty impressed with S1 as a stable DAW. I've used Samplitude for years and really like the program but it does have some issues with 3rd party plugins, especially at high track counts. In Samplitude, VST3 is a no go for example. Maybe that is an issue happening in S1 as well. I read somewhere that some users feel that S1 works better on Windows fwiw. Cheers Hanuman |
|
Hey Donny, you solved your problem yet ?
Did you change from the hub and did that help ? Cheers
Forum Moderator.
Please add your specs to your SIGNATURE. Search the STUDIO ONE 6 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. AMD Ryzen 7 3800X 8-Core 3.90 GHz Windows 10 64bit Home, MacBook Pro + Mini Big Sur, SO 5.5 Pro, SO 6.1.1 Pro, LUNA, Cubase 10.5 Pro, SLIII32, 24.4.2, 16.0.2 FW, Quantum 2626, Faderport 8, FaderPort 16, Atom, Atom SQ, Console 1+Fader 1, UA Apollo Twin TB/USB, Toontrack, NI Komplete 12, ++ |
|
Hey,
Sorry for the delayed response. Yes, bypassing the hub fixed it. Absolutely LOVE Console One along with Studio One. Amazing combination. Donny |
doncolga wroteI'm on Windows 10. I just setup Console One yesterday morning and did a mix with it last evening with no trouble. This morning I started another project and just about had the drums done and it locked up. Restarted the machine, loaded the project and it locked up again much faster, hence I'm looking for information on this also. My problem is sort of similar. I registered my product yesterday and installed the software. I also used it through a powered hub and it worked fantastic. This morning I checked on it and it’s no longer communicating with the hardware. The plugin itself says “Attempting to connect to Console 1. if this message remains please make sure that the on screen display is running and that the Console 1 hardware is connected to your computer.” I plugged the usb cable directly into my computer but the result is the same.
Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7 Memory: 16 GB Presonus. Studio One Pro V6 Presonus Quantum Hardware DBX 160a Hardware DBX 160XT GA. LA2A (clone) GA. LA3A (clone) WA76 1176 (clone) WA EQP Pultec (clone) WA 73 Neve (clone) Softube. Console 1 MK3 (pending) Presonus. Faderport 8 (dual) "God's grace" 
|
|
You have to start the "Console 1 on screen display" in the Windows Start meny under Softube for the Console 1 controller to work in SO with the plugin if it is not on by default in the tray at the bottom right. (on Windows it is)
Forum Moderator.
Please add your specs to your SIGNATURE. Search the STUDIO ONE 6 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. AMD Ryzen 7 3800X 8-Core 3.90 GHz Windows 10 64bit Home, MacBook Pro + Mini Big Sur, SO 5.5 Pro, SO 6.1.1 Pro, LUNA, Cubase 10.5 Pro, SLIII32, 24.4.2, 16.0.2 FW, Quantum 2626, Faderport 8, FaderPort 16, Atom, Atom SQ, Console 1+Fader 1, UA Apollo Twin TB/USB, Toontrack, NI Komplete 12, ++ |
|
Thanks it’s a little bit different on a Mac but praise God I’m good to go now.
Thanks for the reply
Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7 Memory: 16 GB Presonus. Studio One Pro V6 Presonus Quantum Hardware DBX 160a Hardware DBX 160XT GA. LA2A (clone) GA. LA3A (clone) WA76 1176 (clone) WA EQP Pultec (clone) WA 73 Neve (clone) Softube. Console 1 MK3 (pending) Presonus. Faderport 8 (dual) "God's grace"
|
|
Yeah, I missed that one(Mac) but think that it is in Programs there (Mac)
Forum Moderator.
Please add your specs to your SIGNATURE. Search the STUDIO ONE 6 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. AMD Ryzen 7 3800X 8-Core 3.90 GHz Windows 10 64bit Home, MacBook Pro + Mini Big Sur, SO 5.5 Pro, SO 6.1.1 Pro, LUNA, Cubase 10.5 Pro, SLIII32, 24.4.2, 16.0.2 FW, Quantum 2626, Faderport 8, FaderPort 16, Atom, Atom SQ, Console 1+Fader 1, UA Apollo Twin TB/USB, Toontrack, NI Komplete 12, ++ |
|
I’ve been using Console 1 successfully for a while now but it appears there are issues with Studio One 5. If I start a brand new session then it works normally but if I load the VST 3 on a pre existing session then the hardware and software no longer communicate and I get the spinning beach ball and system lag.
And yes the pre existing sessions were started in version 5 as well.
Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7 Memory: 16 GB Presonus. Studio One Pro V6 Presonus Quantum Hardware DBX 160a Hardware DBX 160XT GA. LA2A (clone) GA. LA3A (clone) WA76 1176 (clone) WA EQP Pultec (clone) WA 73 Neve (clone) Softube. Console 1 MK3 (pending) Presonus. Faderport 8 (dual) "God's grace"
|
|
Hey Frank,
Did you ever get to solve this? I’m having a similar issue. It’s like the hardware can’t send commands to the software, however some levels info do work when I hit play. |
ricalv wroteHey Frank, I forgot about this😄 Yup I believe it was eventually solved with a Softube update if I’m not mistaken. I’d recommend contacting Softube Support. Those guys are pretty great Good Luck Frank Crow
Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7 Memory: 16 GB Presonus. Studio One Pro V6 Presonus Quantum Hardware DBX 160a Hardware DBX 160XT GA. LA2A (clone) GA. LA3A (clone) WA76 1176 (clone) WA EQP Pultec (clone) WA 73 Neve (clone) Softube. Console 1 MK3 (pending) Presonus. Faderport 8 (dual) "God's grace"
|
15 posts
Page 1 of 1
Who is online
Users browsing this forum: No registered users and 82 guests