12 posts
Page 1 of 1
When recording midi using Presence, the piano sounds great and the sustain pedal works as expected. But when I play back the recorded midi, the sustain pedal doesn't work properly. I see that the sustain pedal was recorded. But it has a value of 1 when the pedal is not engaged and a value of 0 when it is engaged. It seems that when the pedal is engaged, it is cutting off the sustain rather than sustaining the note. Any ideas on how to reverse the polarity of the recorded sustain? I cannot reverse the polarity of the sustain pedal itself because then when the keyboardist is playing, all of his notes sustain until he presses the sustain pedal.

Win 10 64-bit, 4 Core i7 @ 2.80GHz: 16Gb DDR4 SDRAM, Audiobox USB, Studio One 3.5 Pro 64-Bit (purchased Feb 18, 2018, 1 month before the grace period...)
StudioLogic numa compact 2 keyboard, Nektar sustain pedal.
User avatar
by Trucky on Thu Jun 14, 2018 2:24 pm
Please update your signature to include your keyboard & pedal information.

Check this video out to see how it compares to your settings:

https://youtu.be/DKgmfCFIBEY

For help with an issue, create a SUPPORT TICKET. Select "Submit A Request".
Please add your specs to your SIGNATURE.
How to get better, faster HELP.
Issues need to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce

Windows 10 (1803) Home 64-bit, Intel Core i5-4460S 2.90GHz, 40" HDMI Display (1920x1080), 8GB RAM, 1TB Samsung 850 EVO SSD
Studio One 3.5.6 & 4.0.1 Pro | Notion 6.4 | StudioLive 32 Series III v1.9.14636
User avatar
by donaldfincher on Sun Jun 17, 2018 10:38 am
Thanks for the reply Trucky. The filters are all turned off and the sustain pedal midi is being recorded. I tried using the "delete short notes" command, and it does help in some cases, but in other cases, the keyboardist is playing notes that are getting deleted by that delete short notes command. So rather than fixing the sustain issue in general, it only works if the keyboardist is playing notes longer than the threshold set for the delete short notes command. So, the sustain still isn't working.

Win 10 64-bit, 4 Core i7 @ 2.80GHz: 16Gb DDR4 SDRAM, Audiobox USB, Studio One 3.5 Pro 64-Bit (purchased Feb 18, 2018, 1 month before the grace period...)
StudioLogic numa compact 2 keyboard, Nektar sustain pedal.
User avatar
by iragoldstein on Thu Jul 05, 2018 11:36 pm
Hi donaldfincher,

Did you ever figure this one out? I'm in the same situation. I don't have any options checked and when I record the sustain pedal works fine, but on playback everything is the opposite.


Running the most current version of Studio One 4.

Computer: 2016 Macbook Pro 15" -- 2.9 GHz Intel Core i7 -- 16 GB 2133 MHz LPDDR3 -- 2TB SSD

DAC: UAD Arrow

Midi Keyboard: M-Audio Keystation 88es + Neewer sustain pedal with polarity switch
User avatar
by garyshepherd on Fri Jul 06, 2018 7:51 am
I ended up buying a new sustain pedal which gave you the option of reversing the "polarity" and that has worked - inexpensive if annoying.

Gary Shepherd

Please note that I may express opinions that are different from yours but I do not intend to cause offence.
____________
iMac 27" 3.3 GHz Intel Core i5, 32 GB Ram, High Sierra OS 10.13.6, 64 bit, Studio One 4 Professional 4.0.1 Build 48247, Melodyne 4 Editor, Digital Performer 9.51, Korg Legacy Wavestation and M1, Arturia minimoog V, Helix Native 1.60, Bias FX Pro 1.6.1.3174, Pod Farm 2.59, EZdrummer 2.1.4, Superior Drummer 3.1, EZkeys 1.2.4, Alesis Q49, Line 6 UX2, Gibson Les Paul Standard, James Tyler Variax JTV-59 and other guitars, synths and drum machines.
User avatar
by tezza on Fri Jul 06, 2018 8:01 am
I'm interested in this as well, just got a pedal for my Novation Launchkey, will try out tomorrow morning and report back findings.

Gary, I think your referring to a different problem, one that I also had. The issue of using the correct polarity pedal with the keyboard. If you use the wrong one, then when you put you foot down it won't sustain but when you take your foot off, it sustains. I too ended up getting a dual polarity switchable pedal to use with my current keyboard and to cover me for any other that I buy.

I think Iragoldstein is referring to a situation whereby the pedal is the correct polarity with the keyboard and works fine with that. It will also record ok but when the track is played back, studio one is somehow inverting the sustain info or recording different info to begin with that reverses the sustain information on the automation track during playback.

OS: Win 7, 64 bit. MB: ASUS P8Z77-V LE PLUS. CPU: Intel 3.4ghz, i5-3570, LGA1155. RAM: 8g DDR3 1333Mhz. 1 X SSD (OS) 2 X 7200 HDD (Recording/Samples). Steinberg UR44, Nektar Impact LX61. KRK Rokit 4 G3. S1 Pro V3.5.6. NI Komplete Ultimate 10.
User avatar
by garyshepherd on Fri Jul 06, 2018 11:56 am
Understood - not had that problem.

Gary Shepherd

Please note that I may express opinions that are different from yours but I do not intend to cause offence.
____________
iMac 27" 3.3 GHz Intel Core i5, 32 GB Ram, High Sierra OS 10.13.6, 64 bit, Studio One 4 Professional 4.0.1 Build 48247, Melodyne 4 Editor, Digital Performer 9.51, Korg Legacy Wavestation and M1, Arturia minimoog V, Helix Native 1.60, Bias FX Pro 1.6.1.3174, Pod Farm 2.59, EZdrummer 2.1.4, Superior Drummer 3.1, EZkeys 1.2.4, Alesis Q49, Line 6 UX2, Gibson Les Paul Standard, James Tyler Variax JTV-59 and other guitars, synths and drum machines.
User avatar
by tezza on Fri Jul 06, 2018 10:27 pm
I had a look at this today.

I started up and used a stand alone VST piano to test the new sustain pedal with my keyboard, everything ok, the pedal sustains when pushed down and ceases when returning to up position, no need to switch polarity on the pedal. Had a bit of a jam, everything working ok.

Start up Mixcraft pro 8.

Recorded and played back an Acoustica piano instrument, everything worked as expected, sustain pedal records and plays back as expected. Did the same with a Kontakt piano, Alicias keys, again no problems, everything works as expected.

My Novation Launchkey keyboard and the generic sustain pedal are working as expected with standalone VST instruments and also inside a DAW (Mixcraft) when playing, recording and playing back recorded content.

Started up Studio One and opened a small project I am working on. Inserted Instrument track, put a Kontakt instrument (Alecia's keys) on the track and had a quick jam with the other instruments.

Keyboard and sustain pedal works as expected. Recorded a passage using the sustain pedal. Passage recorded and played back as expected, sustain pedal working as expected.

Everything recorded and played back without issue, unable to replicate the sustain pedal problem indicated in this thread with version 3.5.2.44603.

Thought I would update my version of Studio One and retest.

Now on version 3.5.6.46910

Everything working as expected, tried some presence instruments as well. All record and playback sustain as supposed to.

Unable to replicate the sustain problem indicated in this thread. Everything worked as it should straight away without any changing of settings.

Unable to test version 4 as I don't have that version.

OS: Win 7, 64 bit. MB: ASUS P8Z77-V LE PLUS. CPU: Intel 3.4ghz, i5-3570, LGA1155. RAM: 8g DDR3 1333Mhz. 1 X SSD (OS) 2 X 7200 HDD (Recording/Samples). Steinberg UR44, Nektar Impact LX61. KRK Rokit 4 G3. S1 Pro V3.5.6. NI Komplete Ultimate 10.
User avatar
by Jemusic on Sat Jul 07, 2018 3:37 pm
Just out of interest I am connected to my computer via a 5 pin MIDI OUT signal being generated from my controller and feeding into a midi interface on its own private USB port. (PCI Based)

With USB only in the case of the Novation controller can you check to see what else is going on with the USB port. What else is connected there. This may be a USB port related issue only as well. The sustain message is being flipped for some reason. It never happens over midi.

Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4
iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface and Scarlett 18i20

Poor minds talk about people, average minds talk about events, great minds talk about ideas - Eleanor Roosevelt
User avatar
by tezza on Sat Jul 07, 2018 10:41 pm
Are you referring to my novation Jemusic? I don't have a problem with the sustain issue, just trying to replicate the problem unsuccessfully. Regarding which USB input I use with the keyboard, it gets whatever is available wherever on the computer, USB 3.0 or 2.0 back or front. I find it always works without problem regardless of which USB port I use and whatever is on that same bus.

OS: Win 7, 64 bit. MB: ASUS P8Z77-V LE PLUS. CPU: Intel 3.4ghz, i5-3570, LGA1155. RAM: 8g DDR3 1333Mhz. 1 X SSD (OS) 2 X 7200 HDD (Recording/Samples). Steinberg UR44, Nektar Impact LX61. KRK Rokit 4 G3. S1 Pro V3.5.6. NI Komplete Ultimate 10.
User avatar
by SwitchBack on Sun Jul 08, 2018 5:59 am
Here’s something to try:

Some keyboards revert their pedal input on/off response depending on if the pedal is plugged in before or after the keyboard is powered up. So try flipping the pedal’s on/off switch and change your pedal plug-in/power up routine. That may get the pedal to work OK both for S1 and for the keyboard.
User avatar
by Jemusic on Sun Jul 08, 2018 7:26 pm
SwitchBack wroteHere’s something to try:

Some keyboards revert their pedal input on/off response depending on if the pedal is plugged in before or after the keyboard is powered up. So try flipping the pedal’s on/off switch and change your pedal plug-in/power up routine. That may get the pedal to work OK both for S1 and for the keyboard.


This is very good advice. I have seen some very strange behaviour in terms of plugging in sustain pedals either before or after powering up. In terms of their own behaviour and what is being sent to a DAW. (with Yamaha and Nord synths especially) Although I would imagine in many cases the sustain pedal has not been removed for some time.

If the sustain pedal has been plugged in for a while, it might be good to pull it out, power up and down and then repatch pedal back in. Maybe clean plug and spray some contact cleaner in the socket etc.. Sometimes when plugs are not touched for a long time, a form of corrosion builds between the contacts and could send misleading information.

The internal sound engine of a keyboard may be getting the right message but the message being sent over USB may be different and corrupted for some reason.

Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4
iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface and Scarlett 18i20

Poor minds talk about people, average minds talk about events, great minds talk about ideas - Eleanor Roosevelt

12 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 7 guests