21 postsPage 1 of 2
1, 2
Hi

I'm on Windows 10. Latest updates on all Software and Firmware. Using StudioLive Console 32. Computer wired via router.
I only can make DAW Mode working if I start Studio One first and after that power on the console.
In this case all functions are working.
If I start console first and start Studio One afterwards, only the Transport section responds.
This behavior is not very user friendly in a Studio Environment, where the console is running the whole day, but you maybe need to switch between DAW's.

Is this normal behaviour or something wrong on my side. Had this already with the Beta-Firmware. Universal Control always works as intended. No matter of the sequence.

Any thoughts?
Thanks, Ralph

Presonus Studio One Professional 4.0.1 | Steinberg Cubase Pro (9.5.30) | Workstation (i7 32GB RAM) & Microsoft Surface 4 Pro (i7 16GB RAM) both x64 w/ Windows 10 Pro (1709) | Motu 828mkII Hybrid | Komplete Kontrol S-88 | Behringer X-Touch | Arturia KeyLab 25 | Steinberg CMC Controllers | Presonus StudioLive 32 Series III Console | Presonus StudioLive 32 Series III Rack
User avatar
by matthewgorman on Thu Apr 19, 2018 2:04 pm
Not sure I am following you. Specifically:

If I start console first and start Studio One afterwards, only the Transport section responds


That part isn't making sense to me.

Matt

Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon
Lenovo Thinkpad E520, Windows 7 64bit, 8 GB RAM, Intel i5 Processor
StarTech EC13942 34mm Expresscard
S1Pro V2 , Melodyne Studio 4, Nomad Factory Studio Bundle, Waves , RM16, Studio 192, DP88, Faderport, Central Station Plus, Yamaha HS50 Monitors, Sceptre 6-8 Monitors, Temblor 10.
User avatar
by jpettit on Thu Apr 19, 2018 2:15 pm
Do you see Studio One under the Software Control dropdown list?
Do you have matching subnets for the control network and S1?

http://answers.presonus.com/24603/troub ... 603#q24603

1) For HELP Read the Manual.
2) Create a SUPPORT TICKET. "Select Submit a Request".
3) For Comunity Help add your specs to your SIGNATURE AND.
Include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce
Detailed how to HERE.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by ralphkersten on Thu Apr 19, 2018 2:26 pm
Thanks for taking care

matthewgorman wroteNot sure I am following you. Specifically:

If I start console first and start Studio One afterwards, only the Transport section responds


That part isn't making sense to me.

Does the other part make sense that I need to start Studio one first and then the console to have it fully working, or have you heard this the first time?

jpettit wroteDo you see Studio One under the Software Control dropdown list?
Do you have matching subnets for the control network and S1?

http://answers.presonus.com/24603/troub ... 603#q24603

Yes, I see S1 in the Dropdown list. On both sequences of starting up. When S1 is not started there is "None", but during start up it changes to "Studio One"

Can confirm that my subnets are matching

Presonus Studio One Professional 4.0.1 | Steinberg Cubase Pro (9.5.30) | Workstation (i7 32GB RAM) & Microsoft Surface 4 Pro (i7 16GB RAM) both x64 w/ Windows 10 Pro (1709) | Motu 828mkII Hybrid | Komplete Kontrol S-88 | Behringer X-Touch | Arturia KeyLab 25 | Steinberg CMC Controllers | Presonus StudioLive 32 Series III Console | Presonus StudioLive 32 Series III Rack
User avatar
by matthewgorman on Thu Apr 19, 2018 2:54 pm
Does the other part make sense that I need to start Studio one first and then the console to have it fully working, or have you heard this the first time?


I get the statement, just not grasping the behavior. My mixer is powered on all the time, and I am able to open, close S1 and connect. The part I didn't understand from a behavior perspective is the transport working, but nothing else working. Something sounds off.

Matt

Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon
Lenovo Thinkpad E520, Windows 7 64bit, 8 GB RAM, Intel i5 Processor
StarTech EC13942 34mm Expresscard
S1Pro V2 , Melodyne Studio 4, Nomad Factory Studio Bundle, Waves , RM16, Studio 192, DP88, Faderport, Central Station Plus, Yamaha HS50 Monitors, Sceptre 6-8 Monitors, Temblor 10.
User avatar
by jpettit on Thu Apr 19, 2018 3:01 pm
Go through answers article with fine tooth comb.

Then examine you Studio One.log file for hints.

1) For HELP Read the Manual.
2) Create a SUPPORT TICKET. "Select Submit a Request".
3) For Comunity Help add your specs to your SIGNATURE AND.
Include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce
Detailed how to HERE.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by ralphkersten on Thu Apr 19, 2018 3:08 pm
matthewgorman wrote
Does the other part make sense that I need to start Studio one first and then the console to have it fully working, or have you heard this the first time?


I get the statement, just not grasping the behavior. My mixer is powered on all the time, and I am able to open, close S1 and connect. The part I didn't understand from a behavior perspective is the transport working, but nothing else working. Something sounds off.

Shoot! So I think I need to do troubleshooting on my side. Also after it worked, if I close Studio One and restart it, Faders, Select, Mute & Solo Buttons are not working anymore. Fat Channel neither :-(
And indeed. Transport is still working. Even the Shift functions.

jpettit wroteGo through answers article with fine tooth comb.

Then examine you Studio One.log file for hints.

I'll do so

Thanks again guys

Presonus Studio One Professional 4.0.1 | Steinberg Cubase Pro (9.5.30) | Workstation (i7 32GB RAM) & Microsoft Surface 4 Pro (i7 16GB RAM) both x64 w/ Windows 10 Pro (1709) | Motu 828mkII Hybrid | Komplete Kontrol S-88 | Behringer X-Touch | Arturia KeyLab 25 | Steinberg CMC Controllers | Presonus StudioLive 32 Series III Console | Presonus StudioLive 32 Series III Rack
User avatar
by matthewgorman on Thu Apr 19, 2018 3:17 pm
Come back if you get Stuck.

Matt

Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon
Lenovo Thinkpad E520, Windows 7 64bit, 8 GB RAM, Intel i5 Processor
StarTech EC13942 34mm Expresscard
S1Pro V2 , Melodyne Studio 4, Nomad Factory Studio Bundle, Waves , RM16, Studio 192, DP88, Faderport, Central Station Plus, Yamaha HS50 Monitors, Sceptre 6-8 Monitors, Temblor 10.
User avatar
by ralphkersten on Sun Apr 22, 2018 8:07 am
I did some testing to further isolate my problem:

- Build a song from scratch (using the "Rock Band" template in S1)
- Started S1 and loaded that song
- Powered on console
-> Everything's fine. Can even switch between songs by closing the current and opening another (even those I exported from Cubase and imported to S1)

- Afterwards closed S1 and restarted while console kept powered on
-> with none of the songs I tried, the fader and other sections are working (except Transport)

- Powering off console and powering on again (while S1 kept on)
-> Everything works fine again

Studio One is always present in UCNet view of console as soon it got started

After the above, I did a factory reset of the console (holding FX-Button during start up and keeping current Firmware-Version 1.7.14047):
- After the reset and kept the console powered on, I started S1 and I needed to set again "Software Control" and "Studio One" in console's UCNET view
- Everything worked now as supposed to for first time in this sequence
- Then, I closed S1 and reopened again (with console still on)
-> Result: Same behavior as before :(

---> What I learned:
- Using DAW-Mode with sequence "starting S1 -> powering on Console" always works
- Using DAW-Mode with sequence "powering on Console -> starting S1" works only directly after a factory reset of the console
- The 4 transport buttons always work. No matter what sequence used

If anybody has an idea what to troubleshoot further, let me know. Any hint is appreciated

Presonus Studio One Professional 4.0.1 | Steinberg Cubase Pro (9.5.30) | Workstation (i7 32GB RAM) & Microsoft Surface 4 Pro (i7 16GB RAM) both x64 w/ Windows 10 Pro (1709) | Motu 828mkII Hybrid | Komplete Kontrol S-88 | Behringer X-Touch | Arturia KeyLab 25 | Steinberg CMC Controllers | Presonus StudioLive 32 Series III Console | Presonus StudioLive 32 Series III Rack
User avatar
by Bbd on Sun Apr 22, 2018 9:25 am
What version of UC and mixer firmware are you using?
Can you hear your PC sound in non-DAW mode before launching Studio One (using Tape In/Out)?
Is the mixer your default audio device for Windows?

I am using Win 10 64 with a SIII 24 and I can listen to YouTube and then launch Studio One w/o an issue, then I engage DAW mode on the mixer. I have my USB and Ethernet cables plugged in.
My song's audio output setup points to channels 37/38.

Bbd

1) For HELP Read the Manual.
2) Create a SUPPORT TICKET. "Select Submit a Request".
3) For Comunity Help add your specs to your SIGNATURE AND
Include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce
Detailed how to HERE.

OS: Win 10 x64 Home, Studio One Pro 4, Notion 6, Series III 24, Steinberg UR44, Haswell CPU: i7 4790k @ 4.4GHz, RAM: 16GB, Faderport 8/16, Cental Station Plus, Eris 3.5, ELAC Sub, Equator D5 monitors, Akai MPK261, Roland T6
User avatar
by ralphkersten on Mon Apr 23, 2018 5:17 am
Bbd wroteWhat version of UC and mixer firmware are you using?
Can you hear your PC sound in non-DAW mode before launching Studio One (using Tape In/Out)?
Is the mixer your default audio device for Windows?

I am using Win 10 64 with a SIII 24 and I can listen to YouTube and then launch Studio One w/o an issue, then I engage DAW mode on the mixer. I have my USB and Ethernet cables plugged in.
My song's audio output setup points to channels 37/38.

Both versions are latest.

No USB cable plugged in. I use my Motu Interface. That's my default audio device. Works well in all kind of circumstances.

Presonus Studio One Professional 4.0.1 | Steinberg Cubase Pro (9.5.30) | Workstation (i7 32GB RAM) & Microsoft Surface 4 Pro (i7 16GB RAM) both x64 w/ Windows 10 Pro (1709) | Motu 828mkII Hybrid | Komplete Kontrol S-88 | Behringer X-Touch | Arturia KeyLab 25 | Steinberg CMC Controllers | Presonus StudioLive 32 Series III Console | Presonus StudioLive 32 Series III Rack
User avatar
by ralphkersten on Thu Apr 26, 2018 11:07 am
Had the chance for further testing

I connected the console to my Mobile DAW, which consists of a Microsoft Surface 4 Pro (i7 16GB RAM) with Windows 10 (1709). From a software point of view it's a duplicate of my workstation.
There it works like a charm and how Matthew describes:

matthewgorman wrote
My mixer is powered on all the time, and I am able to open, close S1 and connect.

Further I excluded my Motu AI, the AMD Graphics Driver, the NI KK S88 and the Behringer X-Touch from causing the problems on my workstation.

One thing I noticed: After changing back from Mobile DAW to Workstation DAW, Studio One does not appear in UCNET Window on the console automatically. I have to reselect it. After selecting this and starting Studio One the first time (with Console already powered on of course), everything works as intended. Closing S1 and starting it once more, drops back to the old behavior.

Any thoughts are highly welcomed. Cheers

Presonus Studio One Professional 4.0.1 | Steinberg Cubase Pro (9.5.30) | Workstation (i7 32GB RAM) & Microsoft Surface 4 Pro (i7 16GB RAM) both x64 w/ Windows 10 Pro (1709) | Motu 828mkII Hybrid | Komplete Kontrol S-88 | Behringer X-Touch | Arturia KeyLab 25 | Steinberg CMC Controllers | Presonus StudioLive 32 Series III Console | Presonus StudioLive 32 Series III Rack
User avatar
by jpettit on Thu Apr 26, 2018 11:22 am
As I mentioned early it is usually in the extreme details of the UCNET connection.
The normal assumption is the mixer is on before S1 is started Incase S1 needs to attach to the audio driver.

On each test you need to record the actual IP address that works and does not work to compare.
Also look at the Studio One.log call out in the article and compare socket data.

Also in the article try direct vs using router and auto IP.

1) For HELP Read the Manual.
2) Create a SUPPORT TICKET. "Select Submit a Request".
3) For Comunity Help add your specs to your SIGNATURE AND.
Include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce
Detailed how to HERE.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by ralphkersten on Thu Apr 26, 2018 11:28 am
Thanks jpettit. Was hoping to find an easy fix and tried this other stuff first. But now I think I have to dig deeper. As you mentioned.

Presonus Studio One Professional 4.0.1 | Steinberg Cubase Pro (9.5.30) | Workstation (i7 32GB RAM) & Microsoft Surface 4 Pro (i7 16GB RAM) both x64 w/ Windows 10 Pro (1709) | Motu 828mkII Hybrid | Komplete Kontrol S-88 | Behringer X-Touch | Arturia KeyLab 25 | Steinberg CMC Controllers | Presonus StudioLive 32 Series III Console | Presonus StudioLive 32 Series III Rack
User avatar
by marc-patricefelske1 on Thu Apr 26, 2018 3:50 pm
You are not alone. Same problem happens to me:

Powering on Mixer and Mac, Starting S1 -> DAW Mode not working
Powercycle Mixer while S1 is open -> Daw Mode is working

Sporadic Daw Mode stops working after switching Songs until a powecycle of the Mixer.
User avatar
by ralphkersten on Fri Apr 27, 2018 12:52 am
That's interesting. Also that you're on a Mac. Thanks for letting know. Hope we get rid of the problem some day.

Presonus Studio One Professional 4.0.1 | Steinberg Cubase Pro (9.5.30) | Workstation (i7 32GB RAM) & Microsoft Surface 4 Pro (i7 16GB RAM) both x64 w/ Windows 10 Pro (1709) | Motu 828mkII Hybrid | Komplete Kontrol S-88 | Behringer X-Touch | Arturia KeyLab 25 | Steinberg CMC Controllers | Presonus StudioLive 32 Series III Console | Presonus StudioLive 32 Series III Rack
User avatar
by ralphkersten on Sun Apr 29, 2018 8:35 am
Hi jpettit

Went thru another test according the link you provided above.

Test 1
Started Studio One first and then powered on the console (the case when all works ok)

The UCNET-Screen looks like this:
https://www.dropbox.com/s/no4fqvdwr9o5j ... n.jpg?dl=0

The Log-File has following content:
2018/04/29 15:39:45.837 [Warning] (cclsystem): UID conflict on class registration: Elastik 3 - 64bit (AudioSynth VST2) => used by: Elastik 3 (AudioSynth VST3/Synth)
2018/04/29 15:39:45.837 [Warning] (cclsystem): UID conflict on class registration: Helix Native (x64) (AudioEffect VST2) => used by: Helix Native (AudioEffect VST3)
2018/04/29 15:39:45.837 [Warning] (cclsystem): UID conflict on class registration: Movement_x64 (AudioEffect VST2) => used by: Movement (AudioEffect VST3)
2018/04/29 15:39:45.837 [Warning] (cclsystem): UID conflict on class registration: Gem EQ550-64 (AudioEffect VST2/Mastering) => used by: Gem EQ550 (AudioEffect VST3/EQ)
2018/04/29 15:39:46.297 [Warning] (Studio One): UCNET:Enabled UDP multicast on official port 47809 (1 sockets)
2018/04/29 15:39:46.297 [Warning] (Studio One): UCNET:Local UDP port bound to 57351 (1 sockets)
2018/04/29 15:39:48.797 [Warning] (Studio One): UCNET:Adding server via UDP discovery 192.168.0.137 : tcp 49679 udp 63434 (alive event)
2018/04/29 15:39:48.797 [Warning] (Studio One): UCNET:Server "PreSonus Hardware Access Service" (id = "") resolved at host "192.168.0.137", tcp 49679 udp 63434
2018/04/29 15:39:48.797 [Warning] (Studio One): UCNET:Adding server via UDP discovery 192.168.0.137 : tcp 49679 udp 63434 (alive event)
2018/04/29 15:39:48.797 [Warning] (Studio One): UCNET:Server "PreSonus Hardware Access Service" (id = "") resolved at host "192.168.0.137", tcp 49679 udp 63434
2018/04/29 15:39:49.108 [Warning] (araservice): ARA factory com.celemony.melodyne.arafactory.6825d81db92d3dd45fa2fb0e3104285c40bb0703 (com.celemony.ara.chunk.7) already exists!
2018/04/29 15:39:50.182 [Warning] (remoteservice): UCNET:Started listening on TCP port 52819 (1 sockets)
2018/04/29 15:39:50.184 [Warning] (remoteservice): UCNET:Server "Studio One/3.5.6.46910 Win x64" registration reply received.
2018/04/29 15:40:11.726 [Warning] (remoteservice): UCNET:Resolving hostname 192.168.0.137...
2018/04/29 15:40:11.726 [Warning] (remoteservice): UCNET:Connecting to 192.168.0.137...
2018/04/29 15:48:55.377 [Warning] (remoteservice): UCNET:Adding server via UDP discovery 192.168.0.52 : tcp 53000 udp 53000 (alive event)
2018/04/29 15:48:55.377 [Warning] (remoteservice): UCNET:Server "StudioLive 32" (id = "SD3E1XXXXXXX") resolved at host "192.168.0.52", tcp 53000 udp 53000
2018/04/29 15:49:17.413 [Warning] (remoteservice): UCNET:UDP mapping for 192.168.0.52 set to 53000
2018/04/29 15:49:17.422 [Warning] (remoteservice): UCNET:Client 106 attached to server 104
2018/04/29 15:50:44.997 [Warning] (remoteservice): UCNET:Extending client time out


Test 2
Have the console powered on and then starting Studio One (the case when DAW-Mode does not work)

The UCNET-Screen looks like this:
same as with Test 1

The Log-File has following content:
2018/04/29 15:51:47.538 [Warning] (cclsystem): UID conflict on class registration: Elastik 3 - 64bit (AudioSynth VST2) => used by: Elastik 3 (AudioSynth VST3/Synth)
2018/04/29 15:51:47.538 [Warning] (cclsystem): UID conflict on class registration: Helix Native (x64) (AudioEffect VST2) => used by: Helix Native (AudioEffect VST3)
2018/04/29 15:51:47.538 [Warning] (cclsystem): UID conflict on class registration: Movement_x64 (AudioEffect VST2) => used by: Movement (AudioEffect VST3)
2018/04/29 15:51:47.538 [Warning] (cclsystem): UID conflict on class registration: Gem EQ550-64 (AudioEffect VST2/Mastering) => used by: Gem EQ550 (AudioEffect VST3/EQ)
2018/04/29 15:51:47.938 [Warning] (Studio One): UCNET:Enabled UDP multicast on official port 47809 (1 sockets)
2018/04/29 15:51:47.938 [Warning] (Studio One): UCNET:Local UDP port bound to 50835 (1 sockets)
2018/04/29 15:51:48.186 [Warning] (Studio One): UCNET:Adding server via UDP discovery 192.168.0.52 : tcp 53000 udp 53000 (alive event)
2018/04/29 15:51:48.186 [Warning] (Studio One): UCNET:Server "StudioLive 32" (id = "SD3E1XXXXXXX") resolved at host "192.168.0.52", tcp 53000 udp 53000
2018/04/29 15:51:50.446 [Warning] (Studio One): UCNET:Adding server via UDP discovery 192.168.0.137 : tcp 49679 udp 63434 (alive event)
2018/04/29 15:51:50.446 [Warning] (Studio One): UCNET:Server "PreSonus Hardware Access Service" (id = "") resolved at host "192.168.0.137", tcp 49679 udp 63434
2018/04/29 15:51:50.446 [Warning] (Studio One): UCNET:Adding server via UDP discovery 192.168.0.137 : tcp 49679 udp 63434 (alive event)
2018/04/29 15:51:50.446 [Warning] (Studio One): UCNET:Server "PreSonus Hardware Access Service" (id = "") resolved at host "192.168.0.137", tcp 49679 udp 63434
2018/04/29 15:51:50.850 [Warning] (araservice): ARA factory com.celemony.melodyne.arafactory.6825d81db92d3dd45fa2fb0e3104285c40bb0703 (com.celemony.ara.chunk.7) already exists!
2018/04/29 15:51:50.989 [Warning] (remoteservice): UCNET:Started listening on TCP port 52859 (1 sockets)
2018/04/29 15:51:50.990 [Warning] (remoteservice): UCNET:Server "Studio One/3.5.6.46910 Win x64" registration reply received.
2018/04/29 15:51:51.065 [Warning] (remoteservice): UCNET:UDP mapping for 192.168.0.52 set to 53000
2018/04/29 15:51:51.272 [Warning] (remoteservice): UCNET:Client 106 attached to server 105
2018/04/29 15:53:07.183 [Warning] (remoteservice): UCNET:Extending client time out


In addition, I can confirm that

Studio One checklist:
1.Options/General/Networking: Verify Allow remote control apps to discover the DAW is Enabled
2.Options/Advance/Service: Verify remote control support is Enabled

1. is enabled
2. is active

Router Check List:
1.Recommended routers. https://support.presonus.com/hc/en-us/a ... /210047813
2.DCHP is needed for this to work.
3.Check your hardware router is not blocking port 47809
4.Check that your Firewall is not blocking port 47809
5."If you are running Windows 10 Pro and having network issues, be sure to check if the Hyper V feature is installed on the PC running Studio One. If so, uninstall it or look for alternate solutions as virtual networking can be the root cause of your problem."

2. DHCP enabled
3. not blocking
4. not blocking
5. Hyper-V is not activated

Not done yet:
jpettit wroteAlso in the article try direct vs using router and auto IP.


Actually I can't read the S1-Logs in a way to identify a problem. Can you check if there's something suspicious.

Thanks and regards
Ralph

Presonus Studio One Professional 4.0.1 | Steinberg Cubase Pro (9.5.30) | Workstation (i7 32GB RAM) & Microsoft Surface 4 Pro (i7 16GB RAM) both x64 w/ Windows 10 Pro (1709) | Motu 828mkII Hybrid | Komplete Kontrol S-88 | Behringer X-Touch | Arturia KeyLab 25 | Steinberg CMC Controllers | Presonus StudioLive 32 Series III Console | Presonus StudioLive 32 Series III Rack
User avatar
by ralphkersten on Sat Jun 09, 2018 7:31 am
Hi Jeff

Wanted to let know that I could solve the problem with a workaround.
After changing to S1 4.0.0 and updating all firm- and software to the latest, the problem was still present.
What I did is changing the language in Studio One. When I switch to English, everything works as intended. When I use German (which was is my initial and preferred setting), the problem is present again.
I can live with that, but maybe it's a hint for the developers to look at.

Thx for all the help you gave.

Cheers
Ralph

Presonus Studio One Professional 4.0.1 | Steinberg Cubase Pro (9.5.30) | Workstation (i7 32GB RAM) & Microsoft Surface 4 Pro (i7 16GB RAM) both x64 w/ Windows 10 Pro (1709) | Motu 828mkII Hybrid | Komplete Kontrol S-88 | Behringer X-Touch | Arturia KeyLab 25 | Steinberg CMC Controllers | Presonus StudioLive 32 Series III Console | Presonus StudioLive 32 Series III Rack
User avatar
by jpettit on Sat Jun 09, 2018 7:57 am
Thanks Ralf
You will be happy to know they have fixed the issue and will have an update soon.

1) For HELP Read the Manual.
2) Create a SUPPORT TICKET. "Select Submit a Request".
3) For Comunity Help add your specs to your SIGNATURE AND.
Include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce
Detailed how to HERE.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by Andrew Hazzard on Tue Jun 12, 2018 5:04 am
Hi guys,

My DAW mode stopped working after I upgraded Studio One to version 3.5.6.48910!

It works with my Laptop running V3.5.5...??

Just thought I'd add this information to the thread.

Andrew

21 postsPage 1 of 2
1, 2

Who is online

Users browsing this forum: No registered users and 1 guest