KVR Audio is the Internet's number one news and information resource for open standard audio plugins. We report new releases, product announcements and product updates (major and minor) for all VST Plugins, DirectX Plugins and Audio Units Plugins. We manage a fully searchable audio plugin database (updated daily), and offer many free member services including user reviews, product update notifications and a very active discussion forum. We also host official support forums for many plugin developers plus the official Receptor support forum.
Plug-in Database: Virtual
Instruments, Effects & Hosts
Banks & Patches
Download & Upload
Plug-in Ratings
by KVR Members
Wiki: Tutorials,
Audio Lexicon, ...
Listen to Music
by KVR Members
Search
KVR

Google Powered Search:

in new window

KVR Powered Plug-in Search:

AuthorTopic: Developement of a sampler
helium
Posted: 15th November 2002 08:11
This is a question to all VST-coders
To build a sampler is easy, but how do you store the filename? Normaly I only have things, that can be stored as a number and I can use a VST-Parameter for that. So e.g. cubase will store the value with the song. But what about a path to a sample? how to store that?
jorgen
Posted: 15th November 2002 11:16
You should use chunks to save your data with the host (check out getCunk, setChunk). Whats inside the chunk is totally up to you (its just a stream of bytes), filename, sample data or whatever you want.

Since samplers usually don't have a fixed set of samples/programs, you never know how many VST params to have in yuor plug. So what you can do is expose a fixed set of params, lets say 32, and then let the user map VST params to sample params. Example: param 1 -> prog 1 sample 4 filter cutoff.

Doh! just told you the secret of Cyber 1.01. Razz

jorgen
Forum topics in the archive are read only. New posts should be made in the main KVR Forums.
Disclaimer:
All communications made available as part of this forum and any opinions, advice, statements, views or other information expressed in this forum are solely provided by, and the responsibility of, the person posting such communication and not of kvraudio.com (unless kvraudio.com is specifically identified as the author of the communication).