Sorry to read about your issues. When everything these days are online these things do happen. It doesn't help that the manual is abbreviated somewhat. That is not an excuse or explanation just my own observation.

The good thing is you have this forum here to help in a pinch. It seems the only choice sometimes but fortunately the folks here try to help and not judge. In my experience they are also prompt.

Good luck on getting a better experience in using Studio One and if need be the help here in getting that experience better.

Would I be right back in assuming your background is Sonar?

Anyway I suggest you press F1 and read the manual from beginning to end.I'm over half way in the manual and overwhelmingly my experience has been positive. I'm taking my time to learn this and I'm in no rush, I also accept this is going to work differently from my previous DAW.

Installation was fine for me I didn't require any help, configuration happened via the manual.. no issues.

My only big issue is that downloading the right documentation, it is confusing but that's on another thread and logged with support.

If after all this you think improvements should be made then you need to state the details and specifics.

I recognise none of these issues (I switched from DP last year) and have found it a good experience - YouTube videos have helped greatly as has this forum. You need to persevere as this is a great DAW and the workflow is so easy. It's not perfect but you work out as you go along - it is not an alien experience if you are used to DAW's. The manual is so so - there is an unofficial one out there which is useful - and there are a few users who post helpful videos. So stick with it is my advice.

PreAl wroteWould I be right back in assuming your background is Sonar?

Anyway I suggest you press F1 and read the manual from beginning to end.I'm over half way in the manual and overwhelmingly my experience has been positive. I'm taking my time to learn this and I'm in no rush, I also accept this is going to work differently from my previous DAW.

Installation was fine for me I didn't require any help, configuration happened via the manual.. no issues.

My only big issue is that downloading the right documentation, it is confusing but that's on another thread and logged with support.

If after all this you think improvements should be made then you need to state the details and specifics.

Thank you for your reply. I imagine you did not read my post carefully as I mentioned that I had read the manual and watched the videos.

@johnadams

I too am sorry your experience has not been good.
For your midi instruments, what exactly was a problem that you had or continue to have?
If you can get specific, someone with the same instrument could help.

If you have been reading the posts in this forum, it is really important to be very detailed and clear on your issue(s).

Have you contacted Support for those issues you had?

Thanks much.

I had a very short stint with Cubase... which oddly enough came with my PreSonus Audio Interface. Studio One (S1) came out soon after so that's really all I know.

I did my first S1 install via CD's and since haven't had install issues with every subsequently provided online version.

So you watched videos. Maybe the PreSonus ones?
I'd also check out the many on YouTube. For me that really helped since you get different users perspectives and methods how to accomplish things - and there is typically more than one way to do the same thing.

Which ever DAW you came from, you can switch to that same DAW's keyboard shortcuts within Studio Ones' settings - but you may already know that if you've read the manual (see "Key Commands for Migrating Users")?

I too had a somewhat hard time understanding how to install midi keyboards.
This video helped me understand a lot:
https://www.youtube.com/watch?v=itWM3iY4sfw

johnadams38 wroteThank you for your reply. I imagine you did not read my post carefully as I mentioned that I had read the manual and watched the videos.

Right. Well if you've read the whole manual you should be way ahead of me??

Well we've had a very different experiences anyway. I've only read half the manual (still reading) and not seen the videos. There's also a thread here for ex Sonar users and I've been posting questions here occasionally.

It's all worked very well, I'm sorry it didn't work well for you, each to our own. I'm still learning. I too have used music software since the late 80's.

Not sure about your external hard drive, hard drive configuration is a function of the OS,so it could be an OS issue. But that's a guess I have no idea of the specifics. I'd create a new thread for this if you want it troubleshooted.

Good evening to all. I'm new here as well. I am a Sonar refugee and a hobbyist in recording and music technology, but a computer technician/network engineer/web designer/business owner for my real job, so I have no issue with learning new things, especially when it comes to technology.

All that said, I came to S1 with no previous experience with it. I loaded the demo, setup all of my external midi gear, configured a drum map for my Pearl Mimic Pro, and tested a lot of things. I have it all working just about the way I want, including a PCR-800 for both midi input and control surface purposes, a Contour Shuttle Pro for transport and other related controls - as well as a Frontier Designs Tranzport for the same functions when I'm across the room, and a BCF2000 for mixing and other "getting around".

I have not read any of the manual. I have watched a bunch of videos from numerous creators, both Presonus and not.

I found the midi device setup to be a bit obtuse, but "got there" with the many devices I have.

The drum maps are somewhat lacking compared to the Sonar equivalent (feel free to see my Sonar Drum Map video on my website to understand why I think this - and this is from the Sonar of about 2005 or so: https://www.blades.technology/music/son ... -drum-maps

And there are other things I do/will miss until (or if) they are included in S1, such as Sound On Sound recording and some others.

In general, however, I've found the program to feel largely more stable, more responsive, and mostly more intuitive than Sonar, especially in the post x1 era. I have also found that my devices work generally more like I expected them to rather than the kludgy way I've had to Make them work in Sonar.

I even went back to record a video on what "sound on sound" is in Sonar for folks here who have never seen it in action, and found myself staring blindly at the screen trying to figure out why I wasn't seeing the option I remembered and why I wasn't hearing what I was expecting to.

Long winded - and I apologize for that, but hopefully you and S1 will get along better in the future. So far, I'm enjoying the ride of learning something new and trying to look at the program with fresh eyes rather than "the old way was better" ones, even if in some cases it is absolutely true!

They made the process of installation and activation of Studio One so easy that, ironically, it confuses some people because it conflicts with their previous experiences and expectations. I'll explain...

1. Installation of soundesets is as easy as it gets anywhere. For any new user looking at Options (which one should do with any new software, look over Options), it's hard to miss Options > Locations > Sound Sets if you want to add that folder manually or set the default path. That's what you want, to set the default path there to your external drive. Anyone taking 5 minutes to explore Options would be hard pressed not to see this below...



I think if you put soundsets on an external drive and double click one it will automatically set or add that path to the list and install them.

2. Updating: Users are so accustomed to installing new versions they do it in Studio One even when they don't have to. like turning the demo into Artist or Pro, etc. It's their expectations and previous experiences that causes the issue, not the process. Studio One is literally all the same software, all versions, but people aren't accustomed to that so they make bad assumptions and do too much.

Honestly, they made it all so easy that it causes issues because most users aren't used to it being that easy to install and activate software.

Not the OP, but users are often so excited to get new software they never bother to just take a few minutes and look over the options and menus and they get frustrated.

I'm also curious as to what MIDI Devices the OP was trying to install. There's definitely some quirks in Studio One's MIDI Device implementation (I'm particularly thinking about how a single device can be a Controller or an Instrument but can't be both - which is arbitrary and doesn't reflect reality for many devices), but the overall device setup is a no-brainer IMO. Especially when it comes to mapping your Control Surface. I came from Sonar, keep Reaper around, and just got Cubase and when it comes to setting up something like a MIDI fader box or a synth for use as a Control Surface, there's nothing more intuitive than Studio One. Having just gone through it, Cubase is a nightmare in this regard and the functionality is insanely limited (8 quick link controls versus Studio One's which can map 127 MIDI CC's to unique controls if you want). However, the lack of multi-channel [MIDI] instrument tracks and no polyphonic aftertouch support can make working with some types of devices (MPE controllers, Drum Modules) very cumbersome in Studio One.

Anyway, my point is, specifics about what devices you're trying to setup and how would help. And maybe you're right and it's cumbersome. If you can think of a better way to setup MIDI Devices, maybe post your thoughts on it (or create a Feature Request).

johnadams38 wrote1) Sadly some very basic procedures were cumbersome and unintuitive.

2) The first experience a customer has with software is the installation. Be it a stock install or a custom one, most companies will make sure that it is as smooth and intuitive as possible for that reason. I hope I find the user interface to be more intuitive than the install process.

3) I had major problems pointing S1 to an external drive to store samples and loops. I finally accomplished it................or so I thought. Only to return the next day to find all the loops missing and some of the libraries. I simply gave up and installed them to the default folder.

4) The least intuitive install of midi devices I have ever experienced in any DAW I have tried.

If you are taking the time to talk to this forum please be specific on any one of these issues and work through them one at a time.

jpettit wrote

johnadams38 wrote1) Sadly some very basic procedures were cumbersome and unintuitive.

2) The first experience a customer has with software is the installation. Be it a stock install or a custom one, most companies will make sure that it is as smooth and intuitive as possible for that reason. I hope I find the user interface to be more intuitive than the install process.

3) I had major problems pointing S1 to an external drive to store samples and loops. I finally accomplished it................or so I thought. Only to return the next day to find all the loops missing and some of the libraries. I simply gave up and installed them to the default folder.

4) The least intuitive install of midi devices I have ever experienced in any DAW I have tried.

If you are taking the time to talk to this forum please be specific on any one of these issues and work through them one at a time.

Hi and thanks for the reply. I actually had everything working before I made my original post. My post was simply my feelings on the process of installation as I experienced it. I am glad to know that others had a positive experience.

Funkybot wroteI'm also curious as to what MIDI Devices the OP was trying to install. There's definitely some quirks in Studio One's MIDI Device implementation (I'm particularly thinking about how a single device can be a Controller or an Instrument but can't be both - which is arbitrary and doesn't reflect reality for many devices), but the overall device setup is a no-brainer IMO. Especially when it comes to mapping your Control Surface. I came from Sonar, keep Reaper around, and just got Cubase and when it comes to setting up something like a MIDI fader box or a synth for use as a Control Surface, there's nothing more intuitive than Studio One. Having just gone through it, Cubase is a nightmare in this regard and the functionality is insanely limited (8 quick link controls versus Studio One's which can map 127 MIDI CC's to unique controls if you want). However, the lack of multi-channel [MIDI] instrument tracks and no polyphonic aftertouch support can make working with some types of devices (MPE controllers, Drum Modules) very cumbersome in Studio One.

Anyway, my point is, specifics about what devices you're trying to setup and how would help. And maybe you're right and it's cumbersome. If you can think of a better way to setup MIDI Devices, maybe post your thoughts on it (or create a Feature Request).

Thanks for your reply. I was setting up a Keyboard controller, a Midi Guitar Module, and a Roland Handsonic Drum module. You hit the nail on the head. It was the Handsonic that gave me the most problems.

What were problems with the Handsonic?
Do you still have problems with the Handsonic?

I had a few glitches with a Roland A300 Pro control surface for instance, not an easy ride .. turned out to be how the keyboard was set up not Studio ONE. The forums helped me:

viewtopic.php?f=151&t=27865

.

That's what I understood, you were not asking for help just stating your observation. But as you can see the User's here will try to help.

One thing to mention, I've been using Studio One since 2011 and still learn new things as the need arises. Apart from that I found it fast to get up to speed on more than any other DAW that I use.

Welcome to the forum.

Thanks to everyone who took the time to reply. I really appreciate the constructive feedback which makes me feel more positive about learning how to use S1.

PreAl wroteWhat were problems with the Handsonic?
Do you still have problems with the Handsonic?

I had a few glitches with a Roland A300 Pro control surface for instance, not an easy ride .. turned out to be how the keyboard was set up not Studio ONE. The forums helped me:

viewtopic.php?f=151&t=27865

.

Hi, The problems with the Handsonic was having S1 recognize it. S1 asks you to disconnect and then reconnect your midi device. I did that but it did not work.

The GI-20 and my Keyboard are USB connected. The Handsonic is pure midi and I use the Midi-in connection on my Audio Interface.

It eventually occurred to me that I should try reconnecting the audio interface while the Handsonic was connected to it.........and that worked.

Johnadams38 wrote: The GI-20 and my Keyboard are USB connected. The Handsonic is pure midi and I use the Midi-in connection on my Audio Interface.

It eventually occurred to me that I should try reconnecting the audio interface while the Handsonic was connected to it.........and that worked.

Hi John, Glad it worked out. If you encounter the problem again for any reason, its probably worth running the Handsonic via USB. I have a load of outboard MIDI gear, but I have an 8 In/Out MIDI interface. But where I can, I'll run USB. Just an option to consider. Things like my Roland Octapad, I cant, since there's no USB.

I really appreciate the constructive feedback which makes me feel more positive about learning how to use S1.

So I guest the poor experience is deemed a bit better. A good thing.