Re: [fluid-dev] Thread safety long-term thoughts

2009-11-26 Thread josh
Quoting David Henningsson : j...@resonance.org wrote: I don't think there is an issue with this. Since the new value isn't actually passed through the queue, the queued event is essentially just an update request. The latest value will always be the value assigned to the variable and the

Re: [fluid-dev] Thread safety long-term thoughts

2009-11-26 Thread David Henningsson
j...@resonance.org wrote: Quoting David Henningsson : If someone is playing along with the midi track, they can't have high latency. On the other hand, I think it is only between songs there is a problem, the rest should not be very time-consuming. True, hadn't really thought of that scenario.

[fluid-dev] Re: Revert program change return event stuff

2009-11-26 Thread josh
Quoting David Henningsson : j...@resonance.org wrote: I think I will just revert the changes in regards to processing program change events in the helper thread. The problems with program changes occurring in the synth thread (possible mutex contention and memory allocation) seem less

[fluid-dev] Re: Revert program change return event stuff

2009-11-26 Thread David Henningsson
j...@resonance.org wrote: I think I will just revert the changes in regards to processing program change events in the helper thread. The problems with program changes occurring in the synth thread (possible mutex contention and memory allocation) seem less of an issue in comparison and will on

[fluid-dev] Revert program change return event stuff

2009-11-26 Thread josh
I think I will just revert the changes in regards to processing program change events in the helper thread. The problems with program changes occurring in the synth thread (possible mutex contention and memory allocation) seem less of an issue in comparison and will only happen in the case