Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VST pitch automation not working #4625

Closed
Cangle50 opened this issue Sep 27, 2018 · 17 comments · Fixed by #4692
Closed

VST pitch automation not working #4625

Cangle50 opened this issue Sep 27, 2018 · 17 comments · Fixed by #4692
Assignees
Milestone

Comments

@Cangle50
Copy link

If you try to automate the pitch in vestige with a Automation track, it makes a nasty unacceptable crackling/static noise

this is on a Windows 10 OS PC.

@SecondFlight
Copy link
Member

What VSTs have you tested this with?

@Cangle50
Copy link
Author

Take your pick of vst it doesn't appear to matter but you could try it on synth1.

@DomClark
Copy link
Member

I've experienced this too. I haven't investigated too far, but I think it's caused by #4460. VST automation is currently sent to the plugin from the main thread, and if it's still holding the mutex to send the pitch event, audio processing is skipped for the plugin. I think my fix for #4543 should also fix this, as it changes VST automation to be sent from the processing thread.

@SecondFlight
Copy link
Member

Thanks for the report, @Cangle50!

@Cangle50
Copy link
Author

Your Welcome SecondFlight

@PhysSong
Copy link
Member

I think it's caused by #4460.

I think so. However, I thought it wouldn't matter. See #4460 (comment)
If I can reproduce it, I'll probably investigate the noise part.

@musikBear
Copy link

If you by PITCH mean the marked one. I can automate that fine in win32 rc7
instrumentdefaults
I also threw one dial from the matrix in a AUT-block. Automates perfectly

@Cangle50
Copy link
Author

To musikBear if you can, try it in the 64 bit ver. that's the ver. I use.

@DomClark
Copy link
Member

I think the issue is that the automation doesn't always block the processing; sometimes it gets sent in time, sometimes it doesn't. The result is a stuttering sound where sometimes the buffer contains audio and sometimes it is cleared to zero. Here's the waveform of some recorded playback - the left hand side had pitch automation, the right hand side didn't.
image

@musikBear
Copy link

@Cangle50
I cant run x64

@Cangle50
Copy link
Author

@musikBear
So your saying you can't hear a unacceptable crackling/static noise when automating the pitch on a continuous note in VeSTige with any vst's run on win x32 rc7?

@musikBear
Copy link

musikBear commented Sep 29, 2018

@Cangle50

on a continuous note

Ohhh so on a continuous note
thats new..
Yes it cracles

@Cangle50
Copy link
Author

@musikBear
Thank you for the response.

On a side note to the Dev's. The crackling noise may not be limited to the automation of the pitch.
If you scrub the keyboard keys up and down in quick sequence you can hear crackling noise, just not as
prevalently as automating the Pitch knob.

@tresf tresf changed the title The Automation of the Pitch in VeSTige appears broken in RC7 VST pitch automation not working Sep 29, 2018
@tresf
Copy link
Member

tresf commented Sep 29, 2018

@DomClark is this worth milestoning for the 1.2.0 branch, or is this a regression we'll have to live with on 1.2.0? Please classify and milestone appropriately.

@DomClark
Copy link
Member

The automation can be fixed quite easily I think, I'll make a PR sometime soon. The keyboard scrubbing might be trickier. I'd like to make some changes to the IPC code on the master branch, outlined in #4540 (comment), which would probably fix it, but that's a future thing.

@DomClark DomClark added this to the 1.2.0 milestone Sep 29, 2018
@PhysSong
Copy link
Member

PhysSong commented Oct 4, 2018

Should we revert #4460? It seems like the change introduced some tricky bugs. I'm not sure it's worth reverting #4460 because it has some positive effects.

@PhysSong
Copy link
Member

PhysSong commented Oct 7, 2018

After some thinking, now I think reverting #4460 is an overkill. I was able to hear the noise with manual changes as well, but it was quite slight.
I think the timeout in #4460 which is zero for playbacks can be increased a bit. 1~2 ms should be fine since most changes don't take too long. My concern was long-blocking jobs such as reloading external plugins.
@DomClark Anyway, I think #4543 (comment) should be a part of the next RC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants