Thread: [Audacity-devel] SMDI support (SCSI sample transfer)
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Jelle H. <je...@de...> - 2005-02-26 18:05:41
|
Hello developers, SMDI is a SCSI based protocol to transfer samples to/from a hardware sampler. This is implemented in for example Sony Soundforge. Samples are transferred from the sampler, edited and uploaded again. Meta data such as loop points and amplification envelopes can also be edited. A opensource library and frontend is available for linux, see http://nolv.free.fr/SMDITools/ My question ofcourse is, if you are planning on supporting this in Audacity. If not, could I implement this as a plugin or something? Thanks, Jelle. |
From: Dominic M. <do...@au...> - 2005-02-27 10:57:56
|
Jelle, It's not a high priority for us; the number of users who have SCSI hardware samplers and would like to use them directly from Audacity is pretty small. Especially if the library we'd be using only supports Linux. Of course, if you wanted to add support and the code is clean, we'd be happy to include it! If you could describe what the user interface would look like, and what operations would need to be supported, I might be able to help you figure out how to implement this feature within Audacity. For example: user selects "XXX" menu item, chooses "YYY" from dialog box, then Audacity reads ZZZ samples from a hardware device and inserts them WWW. - Dominic On Feb 26, 2005, at 10:04 AM, Jelle Herold wrote: > Hello developers, > > SMDI is a SCSI based protocol to transfer samples to/from a hardware > sampler. This is implemented in for example Sony Soundforge. Samples > are > transferred from the sampler, edited and uploaded again. Meta data such > as loop points and amplification envelopes can also be edited. > > A opensource library and frontend is available for linux, see > http://nolv.free.fr/SMDITools/ > > My question ofcourse is, if you are planning on supporting this in > Audacity. If not, could I implement this as a plugin or something? > > Thanks, > Jelle. |
From: Jelle H. <je...@de...> - 2005-02-27 13:50:33
|
Hey Dominic, Quoting Dominic Mazzoni (do...@au...): > It's not a high priority for us; the number of users who have SCSI > hardware samplers and would like to use them directly from Audacity is > pretty small. Especially if the library we'd be using only supports > Linux. Of course, if you wanted to add support and the code is clean, > we'd be happy to include it! I guess I'll have to do that then ;-) > If you could describe what the user interface would look like, and > what operations would need to be supported, I might be able to help > you figure out how to implement this feature within Audacity. >=20 > For example: user selects "XXX" menu item, chooses "YYY" from dialog > box, then Audacity reads ZZZ samples from a hardware device and > inserts them WWW. It's really basic: A setup screen is needed: The user selects an availiable scsi device=20 and then selecteds a sampler model. User clicks OK; these settings are stored somewhere. 1. The user selects "Retrieve sample (from sampler)" menu item. A dialog appears, listing all available samples on the sampler in the form "[#sample nr.] [name] [size]". The user selects one (or more) sample(s) and Adacity reads the sample(s) from the sampler. The samples are displayed in audacity. 2. The users selects "Transfer sample to sampler" menu item. A dialog appears again, listing all samples, with the currently retrieved sample selected (if any: a sample could also be loaded from disk for example). The users clicks OK (hit return) and Audacity transfers the data back to the sampler. Obviously, this should be accesible via keyboard shortcuts and/or toolbar items. Thanks, Jelle. |
From: Dominic M. <do...@au...> - 2005-03-02 05:01:29
|
On Feb 27, 2005, at 5:50 AM, Jelle Herold wrote: > A setup screen is needed: The user selects an availiable scsi device > and then selecteds a sampler model. User clicks OK; these settings > are stored somewhere. > > 1. The user selects "Retrieve sample (from sampler)" menu item. A > dialog appears, listing all available samples on the sampler in the > form > "[#sample nr.] [name] [size]". The user selects one (or more) sample(s) > and Adacity reads the sample(s) from the sampler. The samples are > displayed in audacity. > > 2. The users selects "Transfer sample to sampler" menu item. A dialog > appears again, listing all samples, with the currently retrieved sample > selected (if any: a sample could also be loaded from disk for example). > The users clicks OK (hit return) and Audacity transfers the data back > to the sampler. > > Obviously, this should be accesible via keyboard shortcuts and/or > toolbar items. Cool. To add new menu items, you just need to edit Menus.h and Menus.cpp. Search for some item already in the menu and copy and paste the relevant code. Keyboard shortcuts are easy, they're specified in the string that contains the menu item text. You can make the dialogs directly using wxWidgets function calls like ::wxGetSingleChoice. The trickier part will be retrieving and transfering the audio. I think you should build these functions as importers and exporters, so use import/ImportPCM.cpp or import/ImportOGG.cpp as examples for retrieving samples into Audacity, and export/ExportPCM.cpp, for example, as an example for transfering samples to the sampler. - Dominic |
From: Axel S. <as...@as...> - 2006-06-17 09:50:12
|
Dominic Mazzoni <dominic <at> audacityteam.org> writes: > The trickier part will be retrieving and transfering the audio. I > think you should build these functions as importers and exporters, so > use import/ImportPCM.cpp or import/ImportOGG.cpp as examples for > retrieving samples into Audacity, and export/ExportPCM.cpp, for > example, as an example for transfering samples to the sampler. > > - Dominic Hello Dominic, I found this article while I'm searching for an SMDI Tool (no matter weather linux or windows I'm using both for making music). Has anyone done this work? If not, I can try to write some classes for import and export (Windows and Linux). My main job is software developer and I've written some small C++ apps using wxwidgets. So I think that I'm able to do that job. - Axel |
From: Alexandre P. <ale...@gm...> - 2006-06-17 10:02:14
|
On 6/17/06, Axel Schmidt wrote: > Hello Dominic, > I found this article while I'm searching for an SMDI Tool > (no matter weather linux or windows I'm using both for making music). > > Has anyone done this work? > If not, I can try to write some classes for import and export > (Windows and Linux). > My main job is software developer and I've written some small > C++ apps using wxwidgets. So I think that I'm able to do that job. Which makes me think about plug-in architecture for import/export... Alexandre |
From: Anthony A. O. <ai...@gm...> - 2006-06-17 20:40:05
|
On Sat, 17 Jun 2006 13:54:51 +0400, Alexandre Prokoudine wrote: >On 6/17/06, Axel Schmidt wrote: > >> Hello Dominic, >> I found this article while I'm searching for an SMDI Tool >> (no matter weather linux or windows I'm using both for making music). >> >> Has anyone done this work? >> If not, I can try to write some classes for import and export >> (Windows and Linux). >> My main job is software developer and I've written some small >> C++ apps using wxwidgets. So I think that I'm able to do that job. > >Which makes me think about plug-in architecture for import/export... I can only second this idea. A plugin that can be kept open. Select, send.... Select, send. No fuss. Tony |