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

Memory duplicate #44

Open
WindowsNT opened this issue Mar 15, 2020 · 2 comments
Open

Memory duplicate #44

WindowsNT opened this issue Mar 15, 2020 · 2 comments

Comments

@WindowsNT
Copy link

It's really great, I use it for my sequencer. However I have an issue, for simultaneous processing.
Say I have two tracks that use the same channel and loaded SF file, then simultaneous processing cannot be with TSF.

  1. Is there a way to have simultaneous processing within the same TSF object?
  2. If not, is there a way to "mirror" the samples from another TSF object? Currently I use tsf_load_memory to load a SF, but although the memory is the same, TSF duplicates it in their own structures. Is there a way to avoid duplication of the same samples?

Best regards,

@schellingb
Copy link
Owner

Hey there

Can you check out pull request #1 and see if it fits your needs?
I have considered merging this at some point but wasn't sure if this solves many problems or just very specific ones and then forgot again about it.
If you could try it and give some feedback, I can look into merging this again.
This would be solution 2. which probably is far easier than a good clean API that solves it with an approach described in 1.

@WindowsNT
Copy link
Author

WindowsNT commented Mar 16, 2020

Thanks a lot, I will take a look. VST instruments do not support multi-processing so without such a mechanism I would need to duplicate the VST, which means that TSF would create the same presets twice in memory. If there is a copy mechanism then another instance of TSF, independent of the first, would be able to run on the same samples.

I will check it and notify you of the results. Here is my project.
Best,

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

No branches or pull requests

2 participants