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
Does LinVst support sendVstTimeInfo as both client and host? #172
Comments
No it doesn't. It's a bit of a rare one. I've made some changes for it in the file below but whether it works or not I don't know. If it does or doesn't work let me know, and I'll try to work it out or add it to the main code. |
Thanks for the quick response. :-) Will try to test tonight. |
Good news. Your patch worked :-) Bidule is now tracking the playback transport. Bidule's built in sequencer's transport follows fine. This may be TMI, but bidule has a module that extracts all of the time data into separate values. I verified that all of these are working as well. Here is the list of values (from the manual): Playing Output: sends 1 when playing and 0 when not Let me know if you need anything else tested. |
Thanks. I'll add the changes into the next LinVst release. |
Great! Thanks again for the quick and thorough turn around. :-) |
Running into a problem with running Plogue Bidule as a VST inside of Reaper (Linux) via LinVst. The plugin is loading fine and is processing audio and midi but the transport inside of Bidule isn't following Reaper's playback. I've also tested this same setup using Carla and the transport is syncing with out issue (however Carla has other issues as well).
I reached out to the developer at Plogue and he indicated that the Bidule VST plugin makes a "sendVstTimeInfo" request to the host so that Bidule can sync playback. It would seem to me that LinVST would have to forward the request to Reaper and then return Reaper's response back to Bidule VST. Is this supported? If so, any ideas on how to troubleshoot?
I'm running:
The text was updated successfully, but these errors were encountered: