Yeah but I'm barely a musician probably the Grateful Dead, Gong, and the Cure are my biggest influences. Not that it sounds like it really. Where's your stash of tunes?

Ha. . I'm no musician, but an engineer still swimming upstream. But as is the case these days most of us behind the glass are frustrated wannabe musicians and do a little music production. Some of it is on my web page linked in the sig. Nothing to be shouting from the roof tops about.

I do play a little keys and bass, very little of both and more "little" of the latter. I really enjoy mixing primarily but rarely find people willing to pay to do it right, so too much of it is compromised in some way, if just by time.

'Come Back' is cool I will try listening to more later.

That's not me doing any singing, rapping or anything, on any of that music (or anywhere else really). The performer on that track is a guy named Andre. I replaced his original music track, produced all new music for that song.

He submitted it for a "group mix" on the S1 forum and I wasn't really feeling the original music, so I just kept the vocals and did new music.

He's a pretty talented guy.

Grr... not Studio One's fault, but Melodyne is having some issue becoming registered. On my main machine I'm running a 30 day Editor trial, so it can't take the code there, but on my laptop when I run the licenser, it tells me Code28: license already upgraded. Anyone have any clue about this?

OK Celemony gave me a new code for V2, so no worries about Melodyne. And Pattern Arp Plus works now, the developer is really helpful and tracked it to a permissions issue on my computer, so no more rewiring Reaper for me

I'm still wondering about RAM memory usage, I thought CPU would be the limiting factor but it really seems memory usage is my biggest concern performance-wise. It seems if I leave S1 unattended (like overnight) eventually it will run out of memory, this is not with a huge memory load either, I think there probably is a memory leak somewhere. Closing/reopening resolves any memory issues so for a session it isn't really an issue, just an overall concern. I'm turning auto-save back on since that doesn't look to be an issue and I like the feature. If anyone has any tips about S1 and RAM please let me know.

Don't know if you got your answer - but open the 'marker track' and move the end marker to the end of your song. S1 automatically sets the song length at 5mins unless you change it.

Well after about a month with Studio One, I'm pretty happy I switched. I would say though that a couple weaknesses are like pebbles in my show:

1. an immature piano roll (but I'm sure it will mature, not a broken one either)

2. Some memory management issues that have workarounds and hopefully upcoming fixes, mostly an issue while I'm still on 32 bit.

It is an extremely nice DAW that it pretty coherent and easy to use, not exactly 'not needing a manual' like some claimed to me along the way but not brain surgery either.

I was initially concerned about CPU use since my very first demo on V2 was horrible in that regard were put to rest and from my experience CPU use is nice and low, near Reaper so anyone that heard CPU was an issue can scratch that off any 'con' list.

So to answer my own question now that I'm better oriented, to me the big strengths are:

Coherent attractive GUI
Stability
Nice included and integrated effects
Mastering system for Pro
Melodyne integration
Good preset system and browser
Sounds as good as any other host
Nothing that causes extreme frustration (yet!)

Hmmmmmm. I own studio one and I don't have that experience. Kontakt is still completely unusable and things like amp sims are brutal.

Maybe it has something to do with the audio interface being used, with my system Kontakt is fine, the included amp sim is fine, and Guitar Rig is fine. I use Line6's PodFarm though (well-matched to my soundcard) and my interface is a guitar-centric one, but everything has no noticeable difference in comparison to Reaper other than using more RAM than I would like). But that is more the way S1 manages RAM and it doesn't render any plugin unusable by any stretch from my experience.

We went through everything. It was widely reported. Presonus made some attempts at the time. NI made NONE. It wasn't long after it happened that the subject just disappeared......really have no idea if the issue was resolved.

Anyways, sorry to spam, I just get frustrated.

No worries I don't mind, Reaper has been crash-happy for me lately, software environments with lots of third-party plugins are bound to have some occasional hiccups.

That's why I hate all the hosts

Yeah 'what works for you' is literal, not figurative. Sometimes some issues may just get in the way of someone's system while a thousand others never have the same issue. It could come down to so many factors we would never even consider, like some peripheral software installed on our system that we would never guess is causing some conflict. Even switching systems may not resolve things. But with Reaper i think it is the AWS extension's groove implementation that is causing some issues for me, i tried to use it and got a couple crashes. I really want to see Reaper mature in certain areas, and same with Studio One. I'm not selling either anytime soon though, they are the only two I own currently and it is never good to put all your eggs in one basket.