48 postsPage 1 of 3
1, 2, 3
Ever since installing 4.1.1, I've been having major issues with recording Midi Sustain Pedal during recording - it sounds right playing, but when recording I only get a quick jump from (0-127-0) each time I hold down the pedal. This of course results in no sustain during replay, with the exception of those quick blips.


Some of the past problems have apparently been fixed by removing and setting my keyboard up again. Others have suggested using the automation to make sure it works? Neither have solved the issue unfortunately.

The strange thing is, S1 says the pedal works as intended - just the recording doesn't reflect that. Here's a screenshot, showing midi files recorded PRE update and POST update.

Image

Windows 10 (17134) Pro 64-bit, Intel Xeon E5507 2.27 GHz, 1GB AMD Radeon 5450 Graphics (1920x1080), 16GB RAM, Intel SSD 180GB/2x HDD 1TB
Studio One 4.1.1.49941 | Arturia KeyLab Essential 49 | Maschine Jam
User avatar
by brettgoodkin on Sun Nov 11, 2018 4:55 pm
christopherharlan1 wroteEver since installing 4.1.1, I've been having major issues with recording Midi Sustain Pedal during recording - it sounds right playing, but when recording I only get a quick jump from (0-127-0) each time I hold down the pedal. This of course results in no sustain during replay, with the exception of those quick blips.


Some of the past problems have apparently been fixed by removing and setting my keyboard up again. Others have suggested using the automation to make sure it works? Neither have solved the issue unfortunately.

The strange thing is, S1 says the pedal works as intended - just the recording doesn't reflect that. Here's a screenshot, showing midi files recorded PRE update and POST update.

Image



Same exact behavior…. W T F?

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by brettgoodkin on Sun Nov 11, 2018 5:00 pm
I submitted a ticket... please do the same

Mine is Request #473003

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by brettgoodkin on Sun Nov 11, 2018 5:15 pm
*** Update ***

This bug exists on any Instrument that is directly triggering a 3rd party VST instrument (Toontrack, Kontakt). However, when an Instrument track has no VST instrument attached the sustain pedal data is recorded properly. The data is recorded only as momentary on/off.

The data will be properly recorded if Studio One's own Presence instrument is used... However, this is not an option for me.

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by brettgoodkin on Sun Nov 11, 2018 7:04 pm
I thought that maybe it had to do with the whole low latency monitoring, but, doesn't matter either way it still does the same behavior...

A behavior that has been present since version 2+ apparently with the same exact presentation, but, this is the first I've ever experienced it.

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by christopherharlan1 on Sun Nov 11, 2018 9:12 pm
It sucks that we both have this issue, but I'm glad I'm not alone in having it. My ticket is Request #473019.

Unfortunately this bug affects me severely, as I 95% of my time use VST instruments (Kontakt or VST3).

Windows 10 (17134) Pro 64-bit, Intel Xeon E5507 2.27 GHz, 1GB AMD Radeon 5450 Graphics (1920x1080), 16GB RAM, Intel SSD 180GB/2x HDD 1TB
Studio One 4.1.1.49941 | Arturia KeyLab Essential 49 | Maschine Jam
User avatar
by brettgoodkin on Sun Nov 11, 2018 9:47 pm
Glad you reported it, too

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by Robdp on Sun Nov 11, 2018 9:58 pm
I reported the same EXACT behavior 5 days ago and they asked me to delete my settings folder (apart from the license key)

I did that and it seems to have fixed it for now, but I know it will come back as I've done this before.

I'm glad that other people are having this as it shows it's definitely a bug. I even took a QT movie of my screen when playing and recording the sustain, but on play back it not being there..



So frustrating. Try the fix of deleting the settings folder. Worked for me, but only temporary I reckon.



Here's my original post about this..
viewtopic.php?f=151&t=28249&p=185854&hilit=sustain+pedal#p185854

Producer/writer
Mac Pro 5,1 - OSX 10.11.6 - Studio One v4 - Apogee Symphony - SSL Sigma - Cranesong Avocet - Faderport 1 - Console One
User avatar
by brettgoodkin on Mon Nov 12, 2018 12:03 am
My work around is to put a cat instrument of one instrument track... I don’t arm to record but I do click the monitor button so I can hear what I’m playing

I open a second instrument track that’s triggered by the same midi studio kwybkard... but I don’t load any instrument on the track mm

Arm the track to record... when you play you’re hearing your cat instrument... once you’re done, just drag the instrument track that you recorded on the blank channel up to the instrument track with the vst... it works perfectly

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by webhamster on Mon Nov 12, 2018 11:08 am
I am not at my computer but assume that this is the same issue that has been around for ages.

When latency is set high this problem happens. Does this always happen or only with a larger auto buffer? Maybe enabling or disabling low latency for software instruments makes a difference.

In S1 all controller data is recorded with incorrect timing. For most controllers like volume you hardly notice this, but the controller timing issue is related to the sound card buffer. Higher buffer = worse control data timing.

S1 4 - Windows 10 1803 - i9 7900x 32mb - interface: Studio 192 + Quantum 2 - CS18ai
User avatar
by brettgoodkin on Mon Nov 12, 2018 11:19 am
Not related to buffer

Set at 32 or 2048 same problem

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by brettgoodkin on Mon Nov 12, 2018 8:53 pm
Here’s the response to my CS ticket... I’m in the middle of session so I can’t try it yet

Please reset your Studio One settings and reconfigure your MIDI devices.

Go to Help>Open Settings folder.

Copy the contents of the folder over to a folder on your desktop.

Close S1 and delete the contents of the settings folder with the exception of the user.license file as well as the "Extensions" folder.

Open S1 and go to Studio One>Options (Preferences on a Mac) to reconfigure your settings.

Test to see if the problem is resolved. If it is not, please feel free to copy your settings files back over from the backup that you created in step 2.


*If you are missing presets or Sound Sets after doing this, simply double-click one of your Sound Sets under Documents>Studio One>Sound Sets.

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by toddjenkins on Tue Nov 13, 2018 6:58 am
I haven't been able to get my sustain pedal to work either. I'm using it to play MODO Bass, and want to use the pedal for slides. When I play the two notes with the pedal it sounds fine. But when I play back the recording, it recorded two distinct notes instead of a slide between the two.

I will try this out and see if it works.

Thanks.
User avatar
by brettgoodkin on Tue Nov 13, 2018 9:56 pm
toddjenkins wroteI haven't been able to get my sustain pedal to work either. I'm using it to play MODO Bass, and want to use the pedal for slides. When I play the two notes with the pedal it sounds fine. But when I play back the recording, it recorded two distinct notes instead of a slide between the two.

I will try this out and see if it works.

Thanks.

Report back!

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by bradch00 on Wed Nov 14, 2018 2:19 pm
Just back from a road trip. Same issue with my Nectar LX88. At least I know it's not my gear. Will submit a trouble ticket as well.
Cheers

2015 iMac 5K Retina (i7 4Ghz, 32GB RAM, 1TB Flash Drive)
Interface: Antelope Audio Zen-Studio, Black Lion (Red) Sparrow A/D
Control Surface: Faderport & Faderport 8
User avatar
by brettgoodkin on Wed Nov 14, 2018 3:24 pm
So, I did this and I have a mixed report...

Still doesn't work on my current session... Or the last three sessions that i've been working on it the same bug is present. Again, this is only a problem recording... in my existing projects where the sustain had been properly recorded, playback is fine


If I start a new song, the sustain is recorded properly.

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by kevladd on Wed Nov 14, 2018 7:30 pm
brettgoodkin wroteSo, I did this and I have a mixed report...

Still doesn't work on my current session... Or the last three sessions that i've been working on it the same bug is present. Again, this is only a problem recording... in my existing projects where the sustain had been properly recorded, playback is fine


If I start a new song, the sustain is recorded properly.


I posted about this some time ago. It has (had) to do with your overall latency. If you're recording with a bunch of plugins that add latency, this sustain problem occurs. That's why when you start a new song, you don't see it.I haven't tried it lately though.
It was a bug that was apparently fixed but might have crept back in.
User avatar
by brettgoodkin on Wed Nov 14, 2018 7:57 pm
Crazy

That makes sense... but, dang, these sessions are tracking versions, so, hardly any plugins all

Interesting that Modo Bass works perfectly in the same session and records proper sustain length...

Everything else? Same bug

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...
User avatar
by kevladd on Wed Nov 14, 2018 8:15 pm
viewtopic.php?f=151&t=21505

Here's the thread I started when I found this bug initially. You might read through it and see if it's the same.
User avatar
by brettgoodkin on Thu Nov 15, 2018 12:14 pm
I disabled all plugins on the session (other than 3rd party VSTis) and can report that this "fixed" the issue....


Hardly a true fix....

https://soundcloud.com/brotherbrim/sets ... ernational

Win10... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i7 monster...

48 postsPage 1 of 3
1, 2, 3

Who is online

Users browsing this forum: TheUntalentedOne and 15 guests