S1 Developement is tooo fast...........

Begin sarcastic rant:

Can't you folks in Hamburg slow down a bit. This seemingly constant cycle of bug fixes, feature adds, new versions, etc is really starting to give me a headache. For cryin out loud, take a vacation, long smoke break, whatever. This over infatuation with getting it right and pleasing your customers is trying my patience.

If I have to learn ONE MORE FEATURE, I may forget how to drive.

End sarcastic rant.

Haha.

Yeah, I think they should intentionally delay 2.5 (or whatever may be next) for Spring '13, or at least until after Dec 22 to make sure the planet is really still here and they won't need those 500 crates of bottled water and batteries and spam to survive.

Besides... the Mayans don't need step sequencing so much anyway.

haaaaaa...

seriously though man.... if I get one more seamlessly awesome feature that melts into the GUI, makes sense, and makes you say "damn, I don't remember what it was like without that feature being right there... that wasn't in the previous version?"... i'm gonna slap someone.

S1 devs are out of control. Too much power and too god of a workflow are hindering my music

+ 1,000,000

I'm actually overwhelmed with options because I have a DAW that quite simply actually works, and now ... I've got too many songs to work on. Instead of tweaking the DAW, I'm tweaking the music. Something isn't right here, and I'm becoming over-productive.

It's been getting a little cranky in here, so I felt the need to inject some levity to the equation. There was a thread that served as inspiration, any idea which one?

This message was edited 1 time. Last update was at 21/08/2012 17:31:51

There's something to be said about tact when bringing up feature requests, or feature modifications. Given that Presonus is a company made up of people (yes...actual humans!) who respond to things in human ways, the liklihood that of getting a positive response from a developer goes up if the request isn't phrased as a demand, or a threat, or an insult. Derisive implications that the develpers don't know when they're doing, don't care, or aren't doing things the right way is a guaranteed way to get a negative response or no response at all.

The Presonus folks who work on S1 are just that: "folks". They respond to negativity and insult about their work (and by proxy their jobs) in the same way that ANYONE would. To assume that being forceful and demanding (and in many cases outright insulting) will get things accomplished is exactly opposite of what would be expected in a real world situation. But because the comments can be made from behind the veil of a screen name people feel as though you can get away with it here.

Try politeness first...sprinkle it with a bit of well thought out prose about the issue or request (good grammar and sentence structure does matter in this world of text folks, but no, being a native English speaker isn't a requirement and in fact there's probably someone here that speaks whichever language is needed). 900 exclamation points!!!??!!??##$$#@@@ and USING bIg LeTTeRS doesn't make things more effective to read, nor does it get the point across better. And a quick thanks at the end of a post can mean the difference between a misunderstanding and a recognition of a friendly fellow user who's just trying to improve the program and the place.

- Deep thoughts by Gizzmo the Mogwai

Well said Gizzmo.

I think the actual interaction that we have with the developers here makes it what it is.

It seems as though the internet has killed common decency.....hmmm....internet killed our decency skills.........maybe to the tune of the Buggles? I feel like Dewey Cox now. Off to the Beat Lab.

This message was edited 1 time. Last update was at 21/08/2012 21:27:58

Context: (noun) The conditions and circumstances that are relevant to an event, fact, current state of being, etc.

There is very little (if any) of that, only personal fast food wishes for things to magically appear out of thin air because, well, darn it, we want them.

If it was all really that easy, evwryone would be doing it, dropping major "blow your socks off" features every 3 months.

Curiously, nobody is actually doing that and subjectively greater need (unfortunatley), actually doesn't come with it's own time machine.

Makes you wonder how many people have ever spent 5+ years building anything.

This message was edited 1 time. Last update was at 21/08/2012 23:05:40

LMike wrote:Makes you wonder how many people have ever spent 5+ years building anything.

I liken it to something probably a LOT of us are very familar with: The "construction" or "building" of a studio. Whether that be for home, personal, or hobby use or for a business. Rarely does anyone ever go out and simply buy a studio, in total all at once. And if they did, the liklihood that they'd be 100% perfectly happy with it is slim. Additionally the liklihood that they'd know how to use it all is even slimmer.

It takes a lot of time, years, to get the money to either put together all of the pieces you want, or the time to build that perfect piece of studio furniture, or the time to learn to use that piece of gear. Putting all of those things together to actually make a song sound good, or to record a song is something that isn't just done...poof. Research needs to be done...money needs to be calculated...budgets flexed and massaged, resources divied out, decisions need to be made on which part to be bought for what purpose and for what amount and how much time can be spent on this piece over that piece...etc.

Most of us here are probably familiar with the difficulty of putting together a studio...programming software isn't that much different. Research, time spent learning, time spent developing, time spent fleshing out major decisions, time spent tweaking, time spent testing...etc...etc...people who haven't worked as member of a project team can't understand this and so they lose track of everything that actually has to go into the development of something that might seem simple...but is in fact complex.

If that time isn't put in, then neither of these two endeavours will be successful...and certainly not pretty.

Gizzmo0815 wrote:There's something to be said about tact when bringing up feature requests, or feature modifications. Given that Presonus is a company made up of people (yes...actual humans!) who respond to things in human ways, the liklihood that of getting a positive response from a developer goes up if the request isn't phrased as a demand, or a threat, or an insult. Derisive implications that the develpers don't know when they're doing, don't care, or aren't doing things the right way is a guaranteed way to get a negative response or no response at all.

The Presonus folks who work on S1 are just that: "folks". They respond to negativity and insult about their work (and by proxy their jobs) in the same way that ANYONE would. To assume that being forceful and demanding (and in many cases outright insulting) will get things accomplished is exactly opposite of what would be expected in a real world situation. But because the comments can be made from behind the veil of a screen name people feel as though you can get away with it here.

Try politeness first...sprinkle it with a bit of well thought out prose about the issue or request (good grammar and sentence structure does matter in this world of text folks, but no, being a native English speaker isn't a requirement and in fact there's probably someone here that speaks whichever language is needed). 900 exclamation points!!!??!!??##$$#@@@ and USING bIg LeTTeRS doesn't make things more effective to read, nor does it get the point across better. And a quick thanks at the end of a post can mean the difference between a misunderstanding and a recognition of a friendly fellow user who's just trying to improve the program and the place.

- Deep thoughts by Gizzmo the Mogwai

Dang, in this case I'm afraid poor thread-starter Matt won't have a chance with this one ...

personally I am happy with S1 and the 2.06 update, it's stable and has not crashed on me since a looong time ago,
the only thing that is making me frustrated, and I would like it to be the next feature added, is some sort of nonlinear workflow for arrangement
it's been asked for a lot of times and I am asking for it again.
right now I work on creating and composing and I have lots of tracks, and when it's time to try out ideas, it's a pain in the ass having to manually copy/move everything and make sure it is all ok

Kahlbert wrote:

Gizzmo0815 wrote:There's something to be said about tact when bringing up feature requests, or feature modifications. Given that Presonus is a company made up of people (yes...actual humans!) who respond to things in human ways, the liklihood that of getting a positive response from a developer goes up if the request isn't phrased as a demand, or a threat, or an insult. Derisive implications that the develpers don't know when they're doing, don't care, or aren't doing things the right way is a guaranteed way to get a negative response or no response at all.

The Presonus folks who work on S1 are just that: "folks". They respond to negativity and insult about their work (and by proxy their jobs) in the same way that ANYONE would. To assume that being forceful and demanding (and in many cases outright insulting) will get things accomplished is exactly opposite of what would be expected in a real world situation. But because the comments can be made from behind the veil of a screen name people feel as though you can get away with it here.

Try politeness first...sprinkle it with a bit of well thought out prose about the issue or request (good grammar and sentence structure does matter in this world of text folks, but no, being a native English speaker isn't a requirement and in fact there's probably someone here that speaks whichever language is needed). 900 exclamation points!!!??!!??##$$#@@@ and USING bIg LeTTeRS doesn't make things more effective to read, nor does it get the point across better. And a quick thanks at the end of a post can mean the difference between a misunderstanding and a recognition of a friendly fellow user who's just trying to improve the program and the place.

- Deep thoughts by Gizzmo the Mogwai

Dang, in this case I'm afraid poor thread-starter Matt won't have a chance with this one ...

Yes

This "development speed" chapter of the book is turning into an Internet version of the 3 little bears.

Baby Bear: Development is too slow. I want it now!
Mama Bear: Development is too fast, I can't keep up!
Papa Bear: Development is juuuuust right.

Don't worry about Matt folks, he's doing just fine.

The whole purpose of starting the thread was to bring a little levity into everyone's day. Too much negativity lately, so it was a veiled "atta boy" to the developement team.

It's all good, now back to making music everybody. Enjoy the day.