Old 10-25-2023, 06:04 AM   #1
sockmonkey72
Human being with feelings
 
sockmonkey72's Avatar
 
Join Date: Sep 2021
Location: Berlin
Posts: 1,935
Default FR: MIDI_GetRecentInputEvent() multithreading

I realize this might be a big ask, but would it be possible to improve the concurrency protection on MIDI_GetRecentInputEvent()? It looks like it's currently using a global critical region which can cause deadlocks.

My use case is this -- I am trying to develop a "smart thru" feature to prevent a MIDI hardware device from looping back to itself (I'm recording from the device and the track is also playing back to it). For whatever reason, the device freaks out when this happens. I am using the process()ing thread of a VST3 plugin to do this (since this is where I can compare incoming MIDI events to the recent input events to determine whether to block the output).

Anyway, it works great, except when it deadlocks. :-) Maybe you have a better suggestion, or maybe, just maybe, this isn't so hard to improve.

Thanks for considering it!
__________________
ReaPack Repository: right-click and copy index URL
sockmonkey72 is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 02:11 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.