Topic: sustain pedal problem

Hello,

I have Windows 10, my master keyboard is the "Keystation 61 mk3" from M-Audio and my DAW is Studio One 5 & Pianoteq 6 (x64)

The sustain pedal (PS-100) works in standalone but not in Studio One, anyone have a solution ?

Thanks.


https://m.media-amazon.com/images/W/WEBP_402378-T1/images/I/41ETsycVuGL._AC_.jpg

Re: sustain pedal problem

Hebus888 wrote:

Hello,

I have Windows 10, my master keyboard is the "Keystation 61 mk3" from M-Audio and my DAW is Studio One 5 & Pianoteq 6 (x64)

The sustain pedal (PS-100) works in standalone but not in Studio One, anyone have a solution ?

Thanks.


https://m.media-amazon.com/images/W/WEBP_402378-T1/images/I/41ETsycVuGL._AC_.jpg


https://support.presonus.com/hc/en-us/a...Studio-One

Re: sustain pedal problem

Thanks a lot, I'll try that tomorrow and let you know.

Re: sustain pedal problem

@Key Fumbler
Unfortunately it doesn't work and by searching the net I found that this problem has been recurring for a long time in Studio One despite user requests to Presonus support.
Thanks again to you.

Re: sustain pedal problem

Then I suggest having a look at the excellent Reaper DAW.

You said it worked normally with the stand alone version.
Normally with sustain pedals issues you would suggest checking polarity, plugging it in and out, checking it with other software. Perhaps getting a different sustain pedal off one of your old keyboards and trying that.

FWIW when I make layered sounds only two of the instrument layers can use the sustain pedal because the sustain pedal data is only linked to channels 1 and 2 in Pianoteq.

Last edited by Key Fumbler (09-09-2022 20:46)

Re: sustain pedal problem

Here's another possibility:

https://answers.presonus.com/12084/how-...edal-issue

Re: sustain pedal problem

I am gonna be the guy: switch to Reaper!!!

"And live to be the show and gaze o' the time."  (William Shakespeare)

Re: sustain pedal problem

It's possible that the DAW is rerouting or blocking your pedal data.  Within the DAW, you should be able to see the RAW midi data PTQ receives as a plug-in under PTQ's settings.  From there, you can check that the Midi CC that's supposed to be getting pedal events is indeed getting information and that PTQ is configured to interpret it.

Spotify: https://open.spotify.com/artist/2xHiPcCsm29R12HX4eXd4J
Pianoteq Studio & Organteq
Casio GP300 & Custom organ console

Re: sustain pedal problem

Chopin87 wrote:

I am gonna be the guy: switch to Reaper!!!


That's nice, thank you, but I really like Studio One.

Re: sustain pedal problem

Key Fumbler wrote:

Then I suggest having a look at the excellent Reaper DAW.

You said it worked normally with the stand alone version.
Normally with sustain pedals issues you would suggest checking polarity, plugging it in and out, checking it with other software. Perhaps getting a different sustain pedal off one of your old keyboards and trying that.

FWIW when I make layered sounds only two of the instrument layers can use the sustain pedal because the sustain pedal data is only linked to channels 1 and 2 in Pianoteq.


I have already checked the polarity and plug / reconnect the jack and after checking it is a known problem but not solved by the designers of Studio One.

I don't really want to try Reaper because I really like SO5

I'll try to contact support, you never know...

Re: sustain pedal problem

Hello everyone and thank you for your answers.

I forgot to specify that it does this for ALL VSTi and not just Pianoteq

Re: sustain pedal problem

Hebus888 wrote:
Key Fumbler wrote:

Then I suggest having a look at the excellent Reaper DAW.

You said it worked normally with the stand alone version.
Normally with sustain pedals issues you would suggest checking polarity, plugging it in and out, checking it with other software. Perhaps getting a different sustain pedal off one of your old keyboards and trying that.

FWIW when I make layered sounds only two of the instrument layers can use the sustain pedal because the sustain pedal data is only linked to channels 1 and 2 in Pianoteq.


I have already checked the polarity and plug / reconnect the jack and after checking it is a known problem but not solved by the designers of Studio One.

I don't really want to try Reaper because I really like SO5

I'll try to contact support, you never know...

If there is an option in studio One to clear out the record of all the midi devices that have ever been attached try that too.

Re: sustain pedal problem

brundlefly wrote:

Here's another possibility:

https://answers.presonus.com/12084/how-...edal-issue


Thanks but I already tried a similar method and it didn't change anything.
On the other hand, the midi monitor receives the signal

https://i.ibb.co/fpLDRn6/monitor-midi.jpg

Re: sustain pedal problem

Hebus888 wrote:

Hello everyone and thank you for your answers.

I forgot to specify that it does this for ALL VSTi and not just Pianoteq

It really is a question for these guys:

https://forums.presonus.com/viewforum.php?f=151

Re: sustain pedal problem

What about trying this:

https://youtu.be/wHWZg0V-kDY

Re: sustain pedal problem

It didn't work


Key Fumbler wrote:
Hebus888 wrote:
Key Fumbler wrote:

Then I suggest having a look at the excellent Reaper DAW.

You said it worked normally with the stand alone version.
Normally with sustain pedals issues you would suggest checking polarity, plugging it in and out, checking it with other software. Perhaps getting a different sustain pedal off one of your old keyboards and trying that.

FWIW when I make layered sounds only two of the instrument layers can use the sustain pedal because the sustain pedal data is only linked to channels 1 and 2 in Pianoteq.


I have already checked the polarity and plug / reconnect the jack and after checking it is a known problem but not solved by the designers of Studio One.

I don't really want to try Reaper because I really like SO5

I'll try to contact support, you never know...

If there is an option in studio One to clear out the record of all the midi devices that have ever been attached try that too.

Re: sustain pedal problem

This is a solution that concerns the reading of a recording.
My problem happens when I play the keyboard.

Key Fumbler wrote:

What about trying this:

https://youtu.be/wHWZg0V-kDY

Re: sustain pedal problem

Hebus888 wrote:

This is a solution that concerns the reading of a recording.
My problem happens when I play the keyboard.

Key Fumbler wrote:

What about trying this:

https://youtu.be/wHWZg0V-kDY

Okay - I had whizzed through to about 3:25 where he "add the MIDI controller" and thought it might also be a possible solution for you here. Nevermind.

If they can't even make something as absolutely fundamental or basic to work with every single working MIDI keyboard right out of the box they don't really deserve your business surely - assuming that's actually what's going on.

Assuming your MIDI keyboard is set on channel 1 or 2 here.
It's like having a car company have problems with getting the break pedals to work!!!

Test the keyboard with another DAW like Reaper - it's just a few MB and instantly downloads, no need to sign up to anything either. It's 100-percent usable out of the box. You could tell us what's happening in that. You could have that tested in minutes.

Re: sustain pedal problem

I installed Reaper and the sustain pedal works fine.
So the problem comes from SO5 !!



Key Fumbler wrote:
Hebus888 wrote:

This is a solution that concerns the reading of a recording.
My problem happens when I play the keyboard.

Key Fumbler wrote:

What about trying this:

https://youtu.be/wHWZg0V-kDY

Okay - I had whizzed through to about 3:25 where he "add the MIDI controller" and thought it might also be a possible solution for you here. Nevermind.

If they can't even make something as absolutely fundamental or basic to work with every single working MIDI keyboard right out of the box they don't really deserve your business surely - assuming that's actually what's going on.

Assuming your MIDI keyboard is set on channel 1 or 2 here.
It's like having a car company have problems with getting the break pedals to work!!!

Test the keyboard with another DAW like Reaper - it's just a few MB and instantly downloads, no need to sign up to anything either. It's 100-percent usable out of the box. You could tell us what's happening in that. You could have that tested in minutes.

Re: sustain pedal problem

Hebus888 wrote:

I installed Reaper and the sustain pedal works fine.
So the problem comes from SO5 !!

The time to switch has come !

Re: sustain pedal problem

Gaston wrote:
Hebus888 wrote:

I installed Reaper and the sustain pedal works fine.
So the problem comes from SO5 !!

The time to switch has come !

Indeed, a lot of these pedals are just a switch!

If a DAW developer can't even guarantee the absolute basics like a working sustain pedal..
That's not my judgement call though,  that's for the OP.

He wants to stick with Studio One for whatever reason so we should respect that. Certainly sets alarm bells off for me though. If they fall at the first hurdle..

In his position I would be pointing out on their forum that the sustain pedal works immediately in Reaper so Studio One has a major fundamental problem.

Last edited by Key Fumbler (15-09-2022 13:45)

Re: sustain pedal problem

Key Fumbler wrote:

If a DAW developer can't even guarantee the absolute basics like a working sustain pedal..

Every DAW has issues with some 'absolute basics' from time to time that are more or less persistent.

I don't use Reaper but the list of MIDI bugs on their forum is long and I'm sure some of them would seem 'basic' to users of other DAWs that don't have that particular defect.

That said, the persistence of this issue in Studio One is a bit surprising. As common as it apparently is you would think it would be pretty easily reproduced for Dev to investigate and resolve.

Bottom line: So long as an issue isn't a chronic showstopper it makes sense to stick with a DAW that is working for you in most respects - more so if you have a great familiarity with it acquired over along period of time.

If the OP can't resolve this one with some permanence - or at all - and isn't 'married' to S1, then it would definitely be time to move on until it's reported fixed.

Personally, I'm pretty 'married' to Cakewalk and will likely never move on permanently unless they stop developing it and the licensing system breaks down!

Re: sustain pedal problem

brundlefly wrote:
Key Fumbler wrote:

If a DAW developer can't even guarantee the absolute basics like a working sustain pedal..

Every DAW has issues with some 'absolute basics' from time to time that are more or less persistent.

I don't use Reaper but the list of MIDI bugs on their forum is long and I'm sure some of them would seem 'basic' to users of other DAWs that don't have that particular defect.

That said, the persistence of this issue in Studio One is a bit surprising. As common as it apparently is you would think it would be pretty easily reproduced for Dev to investigate and resolve.

Bottom line: So long as an issue isn't a chronic showstopper it makes sense to stick with a DAW that is working for you in most respects - more so if you have a great familiarity with it acquired over along period of time.

If the OP can't resolve this one with some permanence - or at all - and isn't 'married' to S1, then it would definitely be time to move on until it's reported fixed.

Personally, I'm pretty 'married' to Cakewalk and will likely never move on permanently unless they stop developing it and the licensing system breaks down!

I already said as much in the last post.

Key Fumbler wrote:

..
That's not my judgement call though,  that's for the OP.

He wants to stick with Studio One for whatever reason so we should respect that. Certainly sets alarm bells off for me though. If they fall at the first hurdle..

In his position I would be pointing out on their forum that the sustain pedal works immediately in Reaper so Studio One has a major fundamental problem.

Reaper's MIDI has been pretty good for years - generally it's not really issues with things actually working  so much as people preferring different ways to work.  DAW users get used to say Ableton, Cubase, Pro Tools or whatever, then they try to "fix" Reaper with scripting to work the way they expect to work as they have become accustomed.

So this basic input pedal not working at all issue is in a completely different league!

I hope he can get it sorted and enjoys whatever DAW he wishes to use.

Last edited by Key Fumbler (15-09-2022 19:36)

Re: sustain pedal problem

Key Fumbler wrote:

I hope he can get it sorted and enjoys whatever DAW he wishes to use.

Agreed.

Re: sustain pedal problem

Kind of fun reading the Studio One tangent here - but this is a reason I tried Studio One some years back...


One of the founders of Studio One, Matthias Juwan, wrote the spec for VST 3.


I'd probably consider a fault with the pedal before S1. That pedal possibly fires a malformed, or proprietary signal to the dpiano, which the dpiano cannot translate correctly to spec for the remaining MIDI path. A new pedal might be a worthwhile expense.

Studio One is my choice of DAW for various reasons.

Here's the link to Studio One's Wikipedia page << there - I think many don't know just how amazing the founders of it are. It's a tool by early digital era Steinburg gurus who saw better ways for digital workflows within specs etc. From its inception from an original engine (KRYSTAL audio, which the 2 founders wrote), it's been incrementally becoming more useful in various ways. It really works for me.

They do have a free version - and in my experience, I would say it is easier for new users than Reaper.. but for sure we like the things we like for reasons of our own.

From the Studio One 5 Prime product page (the free version): wrote:

FREE after a full 30-day, all access demo of Studio One Professional. No credit card information required. After your demo period ends, you’ll have full access to Studio One Prime, no additional installation necessary.

Also the link to the relevant main Presonus Studio One page.. in case some Reaper-holics and others want a looksie.

Installing the thing is excellent, with its own maintenance app "Presonus Hub" if you choose - but you can update the DAW and other Presonus included plugins when they happen, from inside Studio One if you prefer.

If I was a plumber, I'd need a van full of good tools for the job etc. - and making music, Studio One gives enough tools for even high-end use cases.


But - re the pedal prob?.. I'd first check in Studio One settings.. things like filters (you can filter out input such as pitch bend etc.).. and setting send "All" instead of just channel 1 or 2 and so on.. these things can be changed in any DAW and users can mistakenly alter these thinking "still works, I'll leave that change", then come back 3 months later and forgot what was changed - but I have my doubts that Studio One would be at fault, other than saying "Nope" to incorrect incoming pedal data (for which fault would lie with the pedal  - OR maybe the dpiano can't translate the pedal's signal to standard MIDI - so a bad combo of dpiano and pedal perhaps?).

Check in the advanced settings processes, like "Allow Win MIDI" is ON. (that and other settings are from memory - so may not be exact wording sorry.. time)

But - if it works in Reaper or another DAW maybe that works out for you. I'd send the situation to Presonus and see if they can help though, if wanting to solve in Studio One.

Hope it works out for you.

Pianoteq Studio Bundle (Pro plus all instruments)  - Kawai MP11 digital piano - Yamaha HS8 monitors

Re: sustain pedal problem

Qexl wrote:

Kind of fun reading the Studio One tangent here - but this is a reason I tried Studio One some years back...


One of the founders of Studio One, Matthias Juwan, wrote the spec for VST 3.
..
Studio One is my choice of DAW for various reasons.

Here's the link to [
They do have a free version - and in my experience, I would say it is easier for new users than Reaper.. but for sure we like the things we like for reasons of our own.


Also the link to the relevant main Presonus Studio One page.. in case some Reaper-holics and others want a looksie.

Installing the thing is excellent, with its own maintenance app "Presonus Hub" if you choose - but you can update the DAW and other Presonus included plugins when they happen, from inside Studio One if you prefer.

If I was a plumber, I'd need a van full of good tools for the job etc. - and making music, Studio One gives enough tools for even high-end use cases.

But - if it works in Reaper or another DAW maybe that works out for you. I'd send the situation to Presonus and see if they can help though, if wanting to solve in Studio One.
Hope it works out for you.

The OP did make it clear that he wants to stick with Studio One.
Studio One fans might have recoiled in horror at this article:
https://www.musicradar.com/news/fender-...one-future

It would be like saying - Pianoteq is too complex. Why not just have a single intro page and one piano?!!!

If I can talk about us as a collective (in The thread) REAPER users aren't trying to alienate people, we just tend to be highly enthusiastic after finding Reaper. For me it was the easiest to use and most intuitive, and it came with no clutter and it's so efficient. The tiny footprint. Complete lack of need for anything like a maintenance hub, yikes!
Downloading all of Reaper is click on Reaper download- download Reaper- oh, it's done before I could complete the sentence!

Never mind any conversion or recruitment This simplicity is why I suggest testing with Reaper with any problems at all. No need to sign up, no hundreds or thousands of MB of data, no hub malarkey.
No crippled versions. There is only one version you typically need - 64 or 32-bit, Windows,  Mac or Linux.

Re: sustain pedal problem

Yeah I'm totally cool with all that Keys

Keys wrote:

The OP did make it clear that he wants to stick with Studio One.

Yeh but you told him it didn't deserve a purchase

NP - Just dropping my view, since I've seen a few threads where people are rightly loving Reaper yet sadly.. Studio One in this thread kind of got whacked hard, you'd have to agree

This is just some detail some might like to take in - but tangential to the pedal issue - still hoping to hear back as to whether it's solved.

Even if I never update another plugin - I could keep this install of Studio One (and everything) as it is, and it would probably suit me for another 10 years, which may be all I would want. Some pretty huge reasons would now need to come my way to jump ship. I'll update/upgrade - but if they ruined the offering.. I'll be fine to unplug from updates and keep the installs working as is. I think too many professional systems using the platform would mean, no new CEO is going to be allowed to just shipwreck their competitive pro DAW.

BTW - some readers could think we're maybe upset about all this - assuring you, this topic is one I'm fine with.. and am genuinely interested in reading things said about this stuff - I know we add this info to be useful, not annoying hopefully (and Key Fumbler is in a conversational era which I really do love to see).

Like we probably all have said - no hassle, everyone will like whatever they like - and it's great to read how others think about these tools.. I was interested to read Key's dislike for 'hub' management apps for example.. and I hope I can give some notion to him and others, why those things can be useful - esp. with more than a few tools installed.

Re - simplicity - There have been users saying Pianoteq should be simpler in various ways - some I agree with - and I've agreed with some tool ideas, like a new extra front-end simplified total EQ (slider, left for more bass, right for more treble). But.. egad, I love both ways~! Simple and complex where it matters.

The article linked (thanks! - had seen it - but not worried.. yet). Really seemed like it was a new CEO bustling with personal enthusiasm, quoted to make it seem possible they'll ditch S1 for a Garage Band-like even simpler DAW. Putting that down to first run "I have a vision for the company" kind of statement stuff than anything set in stone. Anything the boardroom says is going to be taken to mean something bad is going down. At least in good deals, that doesn't always happen though.

I'd like to try their new cheaper entry product if it came along (there are some great tools for garage band-like quick songwriting - but maybe not for final productions.. probably one could export stems and have them all line up in the main product.. all valid stuff and can be fun).. but def would like to keep S1 on its evolutionary course. Probability is high, that the thing won't be declawed - but a parallel product may instead emerge to maybe 'compete' (cola wars style!) the free version of S1.. but that's just from watching this happen over and again in similar prod/serv plays.

The reference to 'too many pages of documentation' which seems a criticism in the article, I think is just to say the new boss understands people's desire for a usable product with less requirement to dig into any technical manuals too deeply. A new user who kind of knows what a DAW is will probably never look at the manual.. unless trying to get too clever, too soon, with routing/sends/FX/busses (a lot of the time not a good idea unless knowing why you'd want to do those things anyway - and in that case, you prob also don't need the manual hehe). That stuff can be more spaghetti-like madness in the old big-name pro DAWs because they really make that stuff comply to old real-world analogous workflows.. this is something S1 simplified well.

Frankly - a lot of people like to look at every statement these kinds of execs make as a portent of doom - take their position on it and post "oh noes!". As a media play, the looming controversy works.. mostly for click-baiting their web readers on some music news sites, more than knowing what's going to happen. I'll def wait - before feeling like it's all downhill for S1

Should say - I'm someone who would also love to use Reaper if I didn't already fully integrate with Studio One over the last half dozen years or more, because I needed some of its features which I couldn't get elsewhere (for much greater expense I should add). And it is truly simple to use - and you can hide clutter etc. too if you want. The 'views' in S1 are brilliant IMHO.

But, I guess Atari and tools it ran gave me the impression that "Well digital might be OK before I get too old" (roughly true) in the early 90s (bees knees at the time), all kinds of DAWs including the typical big industry ones (which I loath - why bring all that old-school studio nomenclature into what could be better workflows, like S1 tackled at least to my satisfaction without losing ability to work in complex ways) - and can honestly say nothing can do more better for me than S1. I can choose to use it like I used my old Tascam 4 track.. or I can use it to make albums, to mastering etc.

I know I couldn't do both, or all that I do in Reaper in the same way. But others may surely feel this the other way around

Totally - Not putting anyone down for their DAW choice - just adding some sizzle to the convo because it's been a few times I've seen negative S1 vibes here and other places online go without mentioning how I think "hang on.. it's actually better than being made out here" To me it deserves to get a look at too. Just my 2c about this. Not telling anyone what to do - just giving what I hope is useful info to some readers passing by.


Maintenance hub is actually fab. Truly, I get people (like I used to be like) not wanting that kind of thing. But now, my setup has some 400+ plugins (or I can't work how I used to in physical studio times.. like a plumber, my van is full of things for any type of job etc.).

Very few free versions of anything really do cut it - and keeping a swathe of those tools up to date in one place beats tripping over multiple websites/logins at all kinds of random times, downloading one by one, and all the separate activations, inputting those codes.. keeping a record of it in case it falls over.. support! - that's too much work.

Also use central management tools for other plugin ecosystems (waves/plugin alliance etc.. I'd hand-on-heart rather scroll all the plugins in their list and tick "update all these", one more click and boom, done all working and installed.. no hoops).

It's not that I'm some mislead consumer who needs protection from the corporate behemoths.. or that I got duped into signing up The spin didn't spin me in.. it's maybe not intuitive to understand in what ways some of us really do prefer, if not rely upon those systems (for time saving at least).

Definitely don't think like it's about having to put up with 'em. It's never been easier to fully stock your audio setup and keep it all running.. in the past, one by one, plugin by plugin, download update, install, activate - then think of doing that at least 400 times, then a hundred more maybe twice a year on top?

Not to mention the old compatibility issues for each one.. 32 bit vs. 64 bit.. finally I'm all 64 and VST 3 hallelujah!

Or just open a hub (a few times a year maybe) and do a bunch in one hit. For example.. I hate getting update notifications for most software (it would be fine if I didn't use many - but I do). When I have to update 1 item, it's a drag - and probably over 100 plugins are 'free-range' bought/downloaded individually from vendors - so for those.. it's still mildly annoying.. and I rejoice whenever one of those gets into the plugin alliance deal. Then it's 1 less 10 minute hassle. (10x400 = 4000 or 66hours). Hubs probably save me a week per year of trivial monkeying with logins/dl/inst/activations.


[Edit to add below] ...


Could it be that someone at UJAM had their Pianoteq forum reading goggles on?

Which DAW Is Best for Music Production?

The list they write about:

Studio One
Ableton Live
FL Studio
Logic Pro
Reaper

- I think they did a fine simple wrap of the most basic info.

Gotta say, most of the positive points re Reaper apply also to Studio One from my exp of both.

Cheers!

Last edited by Qexl (18-09-2022 18:15)
Pianoteq Studio Bundle (Pro plus all instruments)  - Kawai MP11 digital piano - Yamaha HS8 monitors

Re: sustain pedal problem

Qexl wrote:

Could it be that someone at UJAM had their Pianoteq forum reading goggles on?

Which DAW Is Best for Music Production?

The list they write about:

Studio One
Ableton Live
FL Studio
Logic Pro
Reaper

The Studio One section could be re-labeled Cakewalk by Bandlab with no modifications and be completely accurate. I will never understand why CW is so consistently omitted from such round-ups. I thought for a long time that the name just didn't sound serious enough, but when 'Fruity Loops' started getting recognition, I had to abandon that hypothesis. ;^)

Re: sustain pedal problem

Ah Yes! Agreed.

I've really adored Cakewalk I'd like to see it keep going and be listed as well. Fond memories of the 90s-2002-ish era with that DAW. Deserves some love.

IIRC (maybe others remember this).. it may have been one of the first to do an actual great job of exporting whole projects to other pro DAW formats (stems/track&channel layouts at least).. but I didn't tend to do that often enough to be sure it was Cakewalk - but rings a bell. I do remember them having quite a few early ideas which are now common to a lot of DAWs.

Cakewalk was certainly my go-to for some years.

Pianoteq Studio Bundle (Pro plus all instruments)  - Kawai MP11 digital piano - Yamaha HS8 monitors

Re: sustain pedal problem

Hebus888 wrote:

Hello,

I have Windows 10, my master keyboard is the "Keystation 61 mk3" from M-Audio and my DAW is Studio One 5 & Pianoteq 6 (x64)

The sustain pedal (PS-100) works in standalone but not in Studio One, anyone have a solution ?

Thanks.


https://m.media-amazon.com/images/W/WEBP_402378-T1/images/I/41ETsycVuGL._AC_.jpg

Any joy with this yet?

Another tool you could check all sorts of Midi activity with is MIDI-ox.
http://www.midiox.com/

Last edited by Key Fumbler (19-09-2022 09:39)

Re: sustain pedal problem

Qexl wrote:

I've really adored Cakewalk I'd like to see it keep going and be listed as well. Fond memories of the 90s-2002-ish era with that DAW.

Cakewalk 2.0a for DOS came bundled with an MPU-401 interface I bought for my first PC in 1988. I picked up Studio One on a cross-grade offer from Presonus when CW went AWOL for a while in 2017 before being picked up by Bandlab (with long-time CTO, Noel Borthwick, still heading up the Dev team). I keep S1 updated but have never really used it in anger. CW is just too familiar and works too well for me to invest the time in developing the necessary muscle memory for S1 or Reaper which I also looked into briefly. CW has always been an innovation leader and has also adopted new features from other DAWs on a regular basis to maintain parity. So long is it continues to do that, I'll have no reason to consider switching. Highly recommended for anyone who doesn't feel the same way about their current DAW.

Re: sustain pedal problem

Wowowo Cakewalk on DOS in 1988 !! Home PC users could near-affordably get their own workstation happening and we all had access to a new cool tool cornucopia. Hard to really describe the sense of possibility in music making back then.

That's a fab write-up for Cakewalk brundlefly! from an early adapter.. I dips me lid!

Wholeheartedly agree with your assessment and believe indeed Cakewalk should be on any list of DAWs.

I installed the Bandlab Cakewalk iteration at the time and appreciated Noel's heart in keeping it buzzing (should be more like that in music tech).


....

BTW - I mentioned Atari in my prior post but of course meant "Amiga". Can't edit the post - but that should be put right.. apologies to Amiga! or any readers who might have wanted to go searching for "Amiga DAW 1990s" but instead ended up doing some kind of "Atari DAW 1990s"

Pianoteq Studio Bundle (Pro plus all instruments)  - Kawai MP11 digital piano - Yamaha HS8 monitors