The help docs I shared from Obsidian are made with their Publish tool. Same idea is what I was thinking. You can also look up Digital Gardens as a whole and you’ll find a ton of different examples around the web. That’s the main takeaway I want from it. Something that can grow and isn’t ever really done.
As for a graph usefulness, It’s very subjective but if we are utilizing just basic wikilinks then it’ll be used by some and not by others. I find it more than just aesthetically pleasing. It’s a nice way to navigate. If it was something that would take a ton of time to make I wouldn’t bother too much but it’ll be automatic.
@parkerfrost - one of us one us! I just looked it up I will be hitting two years on Obsidian this December. Great tool!
Obsidian is great. I used to use it, but stopped a while ago because it wasn't worth it for me to pay the monthly subscription fee. Their current pricing page says that the Publish add-on for Obsidian costs $8USD "per site, per month, billed annually," which sounds like a good deal. But before we commit to that, we should make sure each individual user who would want to participate in the Drambo wiki would be able to do so free of charge. It would significantly hinder participation in the wiki if everybody who wanted to make an edit had to pay a monthly subscription fee.
If this is considered "commercial use," then there's also a "$50 USD Per user, per year" fee. Not sure how this compares to costs of other hosting platforms. Also unsure about whether each user is billed individually, or the owner pays for all the licensed users.
EDIT: Here's official docs from Obsidian that seems to offer clarification: "Only the site owner needs an active subscription for Obsidian Publish. Collaborators only need an Obsidian account." Great! And afaik, the regular Obsidian account is free to set up. But here is the catch: it seems like wiki editors will either need to a) use git to publish edits to the public wiki, or b) pay for the Obsidian sync add-on, which costs $4-$5 USD per month, depending on whether it is billed monthly or annually. And git is not exactly known for being user-friendly....
I have decent amount of experience with obsidian sharing/collaboration. It’s true git would be no go for most so we can just toss that. The simplest is sync, which as you said does require payment. However if there was a maintainer system, as in a few people actually manage the obsidian and then collect and publish snippets from others that would be very simple and low cost. It could easily be done with one obsidian account shared by all the maintainers that pays for one publish and sync a month. There would just need to be contribution system made. You could collect snippet here in the forum or with a google form or any number of ways. The maintainers then find the best way to add it to the knowledge base. Also anyone who wants to contribute who already has an obsidian sync account could do so easily.
Commercial use - I don’t think this idea fits that definition as it’s a community project made and payed for by the community as a resource for others without seeking compensation. I can’t think of anything less commercial. If it were to be sanctioned and or overseen directly by beepstreet in the future then the fee would want to be payed.
I’d also add that if down the road it’s found that obsidian is not the platform of choice, it’s Markdown based and thus extremely portable. The whole wiki could be easily moved to many other platforms
These are my thoughts! Just wanted to share what I know.
Thanks for the explanation, @parkerfrost. Obsidian sounds like a suboptimal solution to me. The fact that non-paying users wouldn't be able to directly make edits seems like it raises too many complications. It creates unnecessary work for the group of middle managers who would need to facilitate the transfer of content from other users into the wiki. Alternatively, if we used a dedicated wiki platform instead of hacking a solution together in Obsidian, we could avoid that type of managerial busywork. That said, a suboptimally-designed wiki is still better than no wiki! So the ease of launching the system in Obsidian is a plus, especially considering the fact that it wouldn't be too complicated to export the content and reformat it later if we decide to change to a better wiki platform in the future.
I was merely sharing a template. I wouldn’t expect anyone to use a specific tool for writing which is why I went with the file type in my plan - Markdown.
While I use Obsidian, it’s Markdown files. I’m not sure when Git was taken out of the equation, but I think it’s probably most necessary. On Git, Markdown is standard.
I’m more than willing to look into a Wiki/Mediawiki if that’s what we all think is best.
On Obsidian there’s several plugins / platforms that use Git as a way to host and share local files was my thought process. Nothing paid.
@offbrands GitHub makes tones of sense as a host. I think I just heard someone say Obsidian so I thought that was the plan. I think Git as in push/pull requests as a means of collaboration would only allow a certain type of person to contribute. That’s all I was saying. GitHub as a markdown wiki host makes a lot sense.
if everyone interested in contributing wants to use Git that totally works for me! I just know that it can be complicated to get used to if you’ve never used it
Okay! It was me that mentioned Obsidian I just wanted to clarify what I should have earlier that it was for markdown sense not so much the app itself!
Yeah I mean Git can get pretty difficult but I’m wondering if realistically only several people use the editing features then it should be a workable solution. I only say that cause I know it’ll be like several people who contribute in the end no matter how easy we make it for people to contribute
That being said the straight forward approach might be the wiki one’s shared by @rs2000 - I’ll look into it.
I want to make sure it’s as cost efficient as possible so I don’t know anything about media wiki or the like but I know git is free is another reason I was at first thinking of it.
Another Obsidian (and Github) user here, who likes to write. I would contribute once established.
[edit] Oh. I should have read further before posting. I'm not interested if there's a cost involved. Also, I believe this would fall under Commercial Use if any of the work ends up in the in-app help, which ideally it should.
MediaWiki isn't particularly hard to set up. Hosting is where the costs can come in. If it can live on whatever infrastructure this forum is running on then that would be ideal. MediaWiki is low overhead. I have my own wiki running along with several other web services on a Raspberry Pi 4 in my home and it doesn't even break a sweat.
Loopy Pro forum member espiegel123 set up the Loopy Pro Wiki. He may be able to provide some insight if anyone would like to PM him over there.
I'm totally up for just plain 'ol Github and markdown, but I'm not a typical user. I think participation might suffer with that route. The control would be great though.
OK, @giku and me have picked DokuWiki now because of its simplicity and the fact that you can work with plain text markup.
The formatting rules are fairly simple, and there's some help documentation available in the Wiki to assist you in editing.
Giku was quick to set everything up!
Now I'll create a basic hierarchical structure and let you know when I'm done. I'll also grab some of the content that people on the former audiobus forum had added to the audiobus wiki. It might need some editing as a few Drambo things have changed over the years.
Giku and me are friends of organizing content by tagging information. I'll start with what I think could work but that will certainly need to be honed and extended over time.
For a start, I'll include everyone who has posted in this thread as editors but I'm happy to add more writers, it's easy 😊
Anyone who would like to contribute is very welcome to participate, just let us know here what you'd like to add so we can keep it somewhat organized in the beginning.
After the first major steps are done, we might open editing to everyone here, as the Wiki is not limited to Drambo only.
Sorry ahead about the lack of formatting… maybe some things are still useful and/or relevant…
GENERATOR
Audio Unit instrument (AUi)
Description:
A container module for AUi plugins with up to 16 parameters available for integration of a familiar instrument into a modular environment, thus enabling advanced, Drambo specific functionality, such as Parameter Locking or modulation from the vast variety of sources.
User Interface:
By default this module loads as a single AUi slot, without any user controls.
Tap + to access the list of available AUi plugins. (Alternatively use hamburger menu from module library to load plugins or saved user presets directly)
Tap AUi icon to access the GUI of the plugin.
On the right side of the plugin, use up/down arrow button to extend the GUI to full screen or shrink it back.
MAP button allows you to map up to 16 parameters, making them accessible from native modules view and available for further modulation. Nudge parameters while MAP button is flashing to map or unmap them. (Not all the parameters that are available on the plugin GUI can be mapped. This is plugin specific - request availability from AU developer)
While MAP button is flashing a number in brackets appears underneath, indicating the number of mapped parameters. Tap the number to see all available parameters, or select them from the list directly.
I/O:
Like any digital instrument, AUi expects MIDI signal and outputs audio generated by the plugin.
From native modules view tap MIDI connector at the bottom of the module to reveal available MIDI sources, such as Track Sequencer, MIDI effects or AUv3 MIDI generators.
AUi will AutoConnect to the nearest MIDI source left of the module.
Instrument rack
Description:
A container module which allows you to create customised interfaces, thus filtering out unwanted visual noise which is common byproduct of any modular environment. A focused approach with the benefits of modular under the hood, as well as convenient way to save and share your creations.
User Interface:
This module loads as an empty shell that you can facilitate with any number of modules by tapping + button inside the container. Once your creation is complete along with all the necessary routings and/or internal signal processing, it’s time to clean up your custom UI. Find and enable ‘Hidden in compact view’ option in module preferences (tap header of any module inside your rack to access its preferences) for all of the modules you wish to exclude. (Many low level modules have this option enabled by default) Using the arrows in the top right corner of the rack, you can lock your creation for reduced, unified view. (Alternatively, you can enable Compact view from rack preferences, as well as further reduce UI to I/O only by enabling Fold option)
Being the most convenient way to save your creations, while in Compact view, two arrows will appear in the top left corner for quick preset switching.
I/O:
To accommodate various scenarios, Instrument rack is equipped with wide range of inputs. You can switch between CV (default) and MIDI modes in module preferences. Choose CV mode if you plan to integrate your creation into a typical modular environment, where an instrument is driven by Control Voltages or choose MIDI if you want to take advantage of many excellent third party MIDI sequencers, MIDI generators, and let Drambo take care of the necessary signal handling.
Additionally, Instrument rack is equipped with an audio input (which can come handy if your rack contains samplers you want to record into), Time signal input (which is crucial to keep e.g. LFOs in sync) and an audio output.
AN Kick
Description:
Digital recreation of the famous TR808 kick drum circuit, heard on countless records and loved to these days across numerous genres.
User Interface:
Two knobs, Tune and Decay is all you need to recreate everything that made the original so popular.
Wanna play bass line with a kick drum like a pro?
Just turn up the Decay, tap triangle left to the Tune knob, assign Pitch CV as a modulation source and turn the modulation amount all the way up.
Done! Use the keyboard to play your kick chromatically.
Additionally, Boost switch will enhance the contour, just like the accent does on the original box, altering the decay and the pitch slightly, which you can Parameter lock on the step basis or simply enable for maximum punch... I mean kick.
AN Kick will accept Gate or Trig signals to generate audio and will AutoConnect to the nearest Gate or Trig source to its left when added.
Staying true to the original design, AN Kick does not respond to velocity by default when added.To achieve velocity sensitivity tap V at the bottom of the module and connect it to V source on MIDI to CV module.
Digital recreation of the famous TR808 kick drum circuit, heard on countless records and loved to these days across numerous genres.
User Interface:
Two knobs, Tune and Decay is all you need to recreate everything that made the original so popular.
Wanna play bass line with a kick drum like a pro?
Just turn up the Decay, tap triangle left to the Tune knob, assign Pitch CV as a modulation source and turn the modulation amount all the way up.
Done! Use the keyboard to play your kick chromatically.
Additionally, Boost switch will enhance the contour, just like the accent does on the original box, altering the decay and the pitch slightly, which you can Parameter lock on the step basis or simply enable for maximum punch... I mean kick.
AN Kick will accept Gate or Trig signals to generate audio and will AutoConnect to the nearest Gate or Trig source to its left when added.
Staying true to the original design, AN Kick does not respond to velocity by default when added.To achieve velocity sensitivity tap V at the bottom of the module and connect it to V source on MIDI to CV module.
Oscillator (mini)
Description:
Essential building block for most types of synthesis.
Oscillator (mini) is nearly identical to Oscillator module in terms of functionality.
In terms of features, this oscillator is tailored towards various - typically digital - types of wave shaping, such as FM (Frequency Modulation), PM (Phase Modulation), PD (Phase Distortion).
Apart from the most common waveforms this oscillator features some unique ones as well such as Sine nine or Sine PD to support these synthesis methods.
User Interface:
Wave Shape: tap the field to reveal the list, or drag up and down to scroll through available shapes. Sine, Sine nine, Saw, Pulse, Triangle, Sine PD
Tune: use this knob to tune your oscillator continuously (free from chromatic scaling)
PW: Pulse Width control, applicable in the context of Pulse shape - where width can be reduced to 0 (inaudible) - and Sine PD shape - where the knob is used to adjust Phase Distortion amount.
I/O:
In most cases you would expect an oscillator to be playable from the keyboard, therefore when added, its Pitch CV input will AutoConnect to the nearest Pitch CV source (typically the Pitch CV output on the MIDI to CV module) to its left. Occasionally, you may want some of your oscillators to disregard pitch information from the keyboard. To do so, disconnect Pitch CV input by double tapping Pitch CV connector and choose Disconnect option.
Underneath, you can find an input that allows you to Hard Sync your oscillator to another oscillator. To do so, tap the Gate connector on the oscillator ‘to be synced’ and connect it to the Audio output of the oscillator ‘to be synced to’.
In this configuration the Tune knob no longer determines the pitch - pitch is controlled by the sync source - instead, it generates often asymmetrical, harmonically rich shapes when modulated (e.g. by an ADSR envelope).
Antialiasing:
Wavetable oscillator
Description:
An ultra-clean wavetable oscillator, supporting Serum wavetables. Up to 256 waves in a single oscillator, up to seven voices stereo unison with an internal rack for advanced wavetable effects (PROCESSOR / SPECTRUM).
Comes with 41 wavetables by Echo Sound Works.
User Interface:
I/O:
Oscillator
Description:
Essential building block for most types of synthesis.
A standard subtractive-style oscillator with a variety of wave shapes and modulation inputs for Tune and PW parameters.
User Interface:
Easy to operate layout, where all available shapes are quickly accessible, along with the quantized tuning and dedicated Fine tune knob. Although Tune knob is quantized to chromatic scale via touch input, continuous modulation is supported via its modulation input, therefore can be utilised for FM or Hard Sync type of sounds.
I/O:
In most cases you would expect an oscillator to be playable from the keyboard, therefore when added, its Pitch CV input will AutoConnect to the nearest Pitch CV source (typically the Pitch CV output on the MIDI to CV module) to its left.
Additionally, you can Hard Sync it to another oscillator using Sync connector.
A perfect emulation of the famous JP8K supersaw oscillator with 7 detuned saw waves.
User Interface:
You can tune the oscillator using Tune (quantized) and Fine knobs. Width determines the amount of detuning applied to all voices. Use Mix knob to create the perfect balance between the core oscillator and the detuned voices and Stereo knob to spread those voices across the stereo field.
I/O:
FM operator
Description:
The basic element of FM synthesis.
Internal oscillator’s frequency or phase is linearly modulated by FM input. Internal feedback changes the shape of the oscillator from Square through Sine to Saw. Frequency ratio may be set to 0. In this case FM operator is ‘stopped’ and acts like a sophisticated wave shaper / through-zero oscillator.
User Interface:
FM Amount: Controls the amount of modulation applied by the source that is connected to its FM input.
Ratio: Base frequency ratio. Quantized via touch input, but allows other values as well via double tap pop-up menu.
Detune: Base frequency detune.
Phase / Freq: Switch between phase modulation and linear frequency modulation.
Feedback: Controls the amount of output signal that is fed back to FM input. Changes the wave shape from Square through Sine to Saw.
Attack, Decay: Controls the attack an d decay length of the internal amp envelope, which you can extend with sustain portion with Sustain switch.
Velocity: Amount of velocity influence on amp envelope level.
End level: Controls the bottom level of amp envelope.
I/O:
FM operator is a fully featured synth voice on its own, relying on number of connections. All these connections handled automatically. When added, it will AutoConnect to the nearest Gate, Pitch and Velocity CV sources to its left (usually from MIDI to CV module) as well as the nearest audio source to its left as a FM modulator.
A sophisticated sampler with a multitude of operating modes for various use cases.
It is tailored towards loop mangling, therefore a single sample can be loaded. (below are some examples for practical applications)
For more conventional sampler duties, such as using multilayered sample libraries please find Sampler module.
User Interface:
By default the module loads without any pre-loaded sample content.
You can either load a sample from your library or record audio directly into the module.
To load a sample, tap the waveform screen and pick a sample - typically a longer loop. Once a sample is loaded, by tapping the waveform screen you can enter the editor.
Here you can Normalize and Trim your sample, as well as Set slices, automatically from the available submenu or manually by tapping the waveform to add/remove a slice and drag the header left/right to adjust it.
Alternatively, you can sample directly into the module. Please find Rec drop down menu at the top right corner of the module with additional controls for sampling.
Source: Switch between the module input and all available audio inputs of your audio interface.
Sync: Switch betweenthree recording sync modes. Instant will start recording as soon as REC button pressed, Pattern will start recording on the next pattern cycle and Threshold will start recording once signal is present at the input.
Clear: Will clear the waveform, but maintain the sample length and slices, so you can re-record audio into a pre-sliced buffer.
Remove: Will remove the sample along with the slices.
Monitor, REC: Buttons to monitor and sample from selected input.
With a sample loaded or recorded, it’s time to look into playback.
As mentioned above, Flexisampler is aimed mainly at loop playback and mangling.
It does not support time stretching, therefore changing Pitch will change playback Speed and vice versa. Playback Speed ranges from +1 (full speed), through 0 (playhead stopped), to -1 (reverse playback). When loading perfect loops, you can use Sync drop down menu right to the waveform screen to determine the length of your loop in beats, so it can be stretched to fit your current project tempo. To avoid clicks at loop or slice points use Fade in / out controls. Use Velocity controlto determine the velocity influence on playback volume.
Offset, Loop start and Loop end controls work in the context of the following playback modes:
1-Shot: Playback starts from Offset locator and plays once until Loop end locator.
Loop: Playback starts from Offset locator and loops forward between Loop start and Loop end locators.
Loop p-pong: Playback starts from Offset locator and loops back and forth between Loop start and Loop end locators.
(In these modes Start slice parameteroptions can be ignored as they only apply to 1-Slice mode)
1-Slice: Slices are played once. Start slice options will determine how these slices are being triggered. When Random is selected, a random slice will be played. Note option will play a slice for each note, starting from C2 (C2 - Slice1, C#2 - Slice2, D2 - Slice3 etc). Velocity option will play a slice depending on velocity, starting from low velocity (first Slice) up to full velocity (last Slice), as well as allowing transposition of the slices across the keyboard. Offset option allows Offset knob to select a slice. Finally Off option will disregard slices altogether, playing back the whole sample as 1-Shot.
Scratch: Playhead is stopped and controlled by Offset parameter, that can also be modulated.
To accommodate all these playback methods, there are four Launch modes available. Trigger and Gate modes are generally useful when manual triggering is desired from keyboard or sequencer, while Transport and Pattern modes are available for convenient playback of longer loops synced to main sequencer.
I/O:
On top of the CV inputs (Pitch, Gate, Velocity), an additional audio input is available. Route any audio signal to this input, select Module input as source and start sampling.
A simple one shot sampler. Samples containing markers are chopped and slices are played randomly (round-robin). An ideal building block for a drum sampler.
User Interface:
Minimalistic, self explanatory interface. Tap waveform screen to access sample editor, where you can Normalize, Trim yoursample as well as Set slices for random playback.
I/O:
A single Trig input to trigger loaded sample or random slice.
Sampler
Description:
A multi zone sampler.
User Interface:
I/O:
Noise
Description:
Essential building block for most types of synthesis with two types of noises and stereo operation available. Although all frequencies are produced in equal intensity, White noise sounds brighter due to the nature of our hearing, which doesn't sense all frequencies equally. Therefore, people often prefer to listen to Pink noise, that boosts the lower frequency range or Brown noise, that puts even more emphasis on the lower frequencies.
User Interface:
Switch between White and Pink noises at the top of the module. Enable stereo for uncorrelated stereo noise. Additionally you can create Brown noise by adding an Integrator module (MATH / 1 OP / Integrator) after White noise.
For polyphonic operation, connect gate input to a polyphonic gate output, such as MIDI to CV module gate output with Voice count greater than one.
Impulse
Description:
Create a short impulse from Gate and Velocity inputs. Useful but not limited to creating excitation impulses for the Modal Resonator, Comb Filter, Waveguide modules.
User Interface:
Impulse shape depends on the Shape setting and the impulse Length can be adjusted between super-narrow and up to 50ms. Noise allows you to add noise with the same envelope as the impulse and Tone is a simple 6dB low pass filter to further shape the signal.
I/O:
Will AutoConnect to the nearest Gate/Trig and Velocity source to its left when added.
This hasn’t been touched for quite some time so things definitely need adjusting, also this was meant to be a sort of beginners guide, with some basic tips and a lot of repetition so it sticks :D
with this new context a lot of bs can be edited out.
you dont learn how to cook tasty food by reading the handbook of the stove and the pan ... ;)
this needs to work differently
I explain the basics to you while we are on the way (if I need to) of creating *something* makes way more sense to me 🤔
kind of like the tutorial projects in drambo are?
ppl are supposed to have fun and not feel "lectured" by reading a mind numbing dokumentation to door 101
if you dont know that need to use these 3 modules together to get it to do whatever ... it doesn't really help if you know what each of them does ... 🤷🏻♂️
@rec, as a counterpoint to @lala’s comments, i think the stuff you’ve posted here would be extremely useful to beginners and i don’t think most new users have the time - initially at least - to learn through creative exercises in the way @lala suggests and that could just as easily feel like being lectured to anyway, just different approaches to teaching.
Surely the proposed wiki could encompass both approaches anyway? A catalogue of definitions for users who need that and a ‘cookbook’ for users who already understand the basics.
Your definitions would also work well in the module ‘?’ sections in app.
Perhaps stating the obvious, but in the ‘How to get started’ section (or somewhere), i would make sure to cover the ‘basics’ that users might wonder about if they’re coming from other audio software…e.g. setting up external equipment, sequencer/piano roll, export options, setting up patterns to play in sequence with repeats, automation, MIDI connections etc. Imagine a new user coming from their DAW of choice to Drambo and wanting to know how to do the everyday things every DAW does, i think it should cover this too as a reference guide even if only briefly.
@rs2000 I like this structure a lot! I think it’s great to get started. In my experience building similar knowledge banks, you’ll find out what needs more or less structure after you filled it out more, and this seems like the perfect amount of organization without being to rigid.
This isn’t related to the structure, but rather some ideas from a new user perspective. Drambo can be many things. The current manual touches on this, but I think it can be elaborated on and more friendly to new comers at the same time. What I mean by this is in the getting started section have guides thatnscrictly treat Drambo as one thing. ie Drambo the drum machine, Drambo the modular synth, Drambo the Midi arranger, Drambo the Sampler, etc. So instead of trying to give holistic overview it’s more like a series of different ways you could use it in your music workflow.
I bring this up because I’ve owned Drambo for many years but only recently got into it. For me that took minimizing its use to arranging for a while. But for others it may be something else. Drambo is a DAW in sheep’s clothing and like any daw it can be a lot to take in on first use. I’d be happy to try and write one of these as an example.
Really excited to dive into the wiki. Thanks for setting it up!
Comments
The help docs I shared from Obsidian are made with their Publish tool. Same idea is what I was thinking. You can also look up Digital Gardens as a whole and you’ll find a ton of different examples around the web. That’s the main takeaway I want from it. Something that can grow and isn’t ever really done.
As for a graph usefulness, It’s very subjective but if we are utilizing just basic wikilinks then it’ll be used by some and not by others. I find it more than just aesthetically pleasing. It’s a nice way to navigate. If it was something that would take a ton of time to make I wouldn’t bother too much but it’ll be automatic.
@parkerfrost - one of us one us! I just looked it up I will be hitting two years on Obsidian this December. Great tool!
Obsidian is great. I used to use it, but stopped a while ago because it wasn't worth it for me to pay the monthly subscription fee. Their current pricing page says that the Publish add-on for Obsidian costs $8USD "per site, per month, billed annually," which sounds like a good deal. But before we commit to that, we should make sure each individual user who would want to participate in the Drambo wiki would be able to do so free of charge. It would significantly hinder participation in the wiki if everybody who wanted to make an edit had to pay a monthly subscription fee.
If this is considered "commercial use," then there's also a "$50 USD Per user, per year" fee. Not sure how this compares to costs of other hosting platforms. Also unsure about whether each user is billed individually, or the owner pays for all the licensed users.
EDIT: Here's official docs from Obsidian that seems to offer clarification: "Only the site owner needs an active subscription for Obsidian Publish. Collaborators only need an Obsidian account." Great! And afaik, the regular Obsidian account is free to set up. But here is the catch: it seems like wiki editors will either need to a) use git to publish edits to the public wiki, or b) pay for the Obsidian sync add-on, which costs $4-$5 USD per month, depending on whether it is billed monthly or annually. And git is not exactly known for being user-friendly....
I have decent amount of experience with obsidian sharing/collaboration. It’s true git would be no go for most so we can just toss that. The simplest is sync, which as you said does require payment. However if there was a maintainer system, as in a few people actually manage the obsidian and then collect and publish snippets from others that would be very simple and low cost. It could easily be done with one obsidian account shared by all the maintainers that pays for one publish and sync a month. There would just need to be contribution system made. You could collect snippet here in the forum or with a google form or any number of ways. The maintainers then find the best way to add it to the knowledge base. Also anyone who wants to contribute who already has an obsidian sync account could do so easily.
Commercial use - I don’t think this idea fits that definition as it’s a community project made and payed for by the community as a resource for others without seeking compensation. I can’t think of anything less commercial. If it were to be sanctioned and or overseen directly by beepstreet in the future then the fee would want to be payed.
I’d also add that if down the road it’s found that obsidian is not the platform of choice, it’s Markdown based and thus extremely portable. The whole wiki could be easily moved to many other platforms
These are my thoughts! Just wanted to share what I know.
Thanks for the explanation, @parkerfrost. Obsidian sounds like a suboptimal solution to me. The fact that non-paying users wouldn't be able to directly make edits seems like it raises too many complications. It creates unnecessary work for the group of middle managers who would need to facilitate the transfer of content from other users into the wiki. Alternatively, if we used a dedicated wiki platform instead of hacking a solution together in Obsidian, we could avoid that type of managerial busywork. That said, a suboptimally-designed wiki is still better than no wiki! So the ease of launching the system in Obsidian is a plus, especially considering the fact that it wouldn't be too complicated to export the content and reformat it later if we decide to change to a better wiki platform in the future.
I was merely sharing a template. I wouldn’t expect anyone to use a specific tool for writing which is why I went with the file type in my plan - Markdown.
While I use Obsidian, it’s Markdown files. I’m not sure when Git was taken out of the equation, but I think it’s probably most necessary. On Git, Markdown is standard.
I’m more than willing to look into a Wiki/Mediawiki if that’s what we all think is best.
On Obsidian there’s several plugins / platforms that use Git as a way to host and share local files was my thought process. Nothing paid.
@aaa @parkerfrost - ^^^
@offbrands GitHub makes tones of sense as a host. I think I just heard someone say Obsidian so I thought that was the plan. I think Git as in push/pull requests as a means of collaboration would only allow a certain type of person to contribute. That’s all I was saying. GitHub as a markdown wiki host makes a lot sense.
if everyone interested in contributing wants to use Git that totally works for me! I just know that it can be complicated to get used to if you’ve never used it
I agree that Git might not be the best "mainstream choice".
I used to contribute content to
and
And I found editing very straightforward.
Also, edits and old revisions could be viewed easily so not much can be destroyed even if literally anyone with a login can contribute.
Okay! It was me that mentioned Obsidian I just wanted to clarify what I should have earlier that it was for markdown sense not so much the app itself!
Yeah I mean Git can get pretty difficult but I’m wondering if realistically only several people use the editing features then it should be a workable solution. I only say that cause I know it’ll be like several people who contribute in the end no matter how easy we make it for people to contribute
That being said the straight forward approach might be the wiki one’s shared by @rs2000 - I’ll look into it.
I want to make sure it’s as cost efficient as possible so I don’t know anything about media wiki or the like but I know git is free is another reason I was at first thinking of it.
Another Obsidian (and Github) user here, who likes to write. I would contribute once established.
[edit] Oh. I should have read further before posting. I'm not interested if there's a cost involved. Also, I believe this would fall under Commercial Use if any of the work ends up in the in-app help, which ideally it should.
MediaWiki isn't particularly hard to set up. Hosting is where the costs can come in. If it can live on whatever infrastructure this forum is running on then that would be ideal. MediaWiki is low overhead. I have my own wiki running along with several other web services on a Raspberry Pi 4 in my home and it doesn't even break a sweat.
Loopy Pro forum member espiegel123 set up the Loopy Pro Wiki. He may be able to provide some insight if anyone would like to PM him over there.
I'm totally up for just plain 'ol Github and markdown, but I'm not a typical user. I think participation might suffer with that route. The control would be great though.
Wow, thanks a lot @number37!
Looking into it.
@aaa
I noticed that you took the initiative in creating threads for individual modules.
Awesome.
Cheers @number37 - i’ll look into this
@aaa
I'm leaving my messages here as I don't want to mess with your flow in regards to the modules etc.
Agreed, keeping the one thread going rather than creating multiple threads makes much more sense.
Much less phaff.
OK, @giku and me have picked DokuWiki now because of its simplicity and the fact that you can work with plain text markup.
The formatting rules are fairly simple, and there's some help documentation available in the Wiki to assist you in editing.
Giku was quick to set everything up!
Now I'll create a basic hierarchical structure and let you know when I'm done. I'll also grab some of the content that people on the former audiobus forum had added to the audiobus wiki. It might need some editing as a few Drambo things have changed over the years.
Giku and me are friends of organizing content by tagging information. I'll start with what I think could work but that will certainly need to be honed and extended over time.
For a start, I'll include everyone who has posted in this thread as editors but I'm happy to add more writers, it's easy 😊
Anyone who would like to contribute is very welcome to participate, just let us know here what you'd like to add so we can keep it somewhat organized in the beginning.
After the first major steps are done, we might open editing to everyone here, as the Wiki is not limited to Drambo only.
Sorry ahead about the lack of formatting… maybe some things are still useful and/or relevant…
GENERATOR
Audio Unit instrument (AUi)
Description:
A container module for AUi plugins with up to 16 parameters available for integration of a familiar instrument into a modular environment, thus enabling advanced, Drambo specific functionality, such as Parameter Locking or modulation from the vast variety of sources.
User Interface:
By default this module loads as a single AUi slot, without any user controls.
Tap + to access the list of available AUi plugins. (Alternatively use hamburger menu from module library to load plugins or saved user presets directly)
Tap AUi icon to access the GUI of the plugin.
On the right side of the plugin, use up/down arrow button to extend the GUI to full screen or shrink it back.
MAP button allows you to map up to 16 parameters, making them accessible from native modules view and available for further modulation. Nudge parameters while MAP button is flashing to map or unmap them. (Not all the parameters that are available on the plugin GUI can be mapped. This is plugin specific - request availability from AU developer)
While MAP button is flashing a number in brackets appears underneath, indicating the number of mapped parameters. Tap the number to see all available parameters, or select them from the list directly.
I/O:
Like any digital instrument, AUi expects MIDI signal and outputs audio generated by the plugin.
From native modules view tap MIDI connector at the bottom of the module to reveal available MIDI sources, such as Track Sequencer, MIDI effects or AUv3 MIDI generators.
AUi will AutoConnect to the nearest MIDI source left of the module.
Instrument rack
Description:
A container module which allows you to create customised interfaces, thus filtering out unwanted visual noise which is common byproduct of any modular environment. A focused approach with the benefits of modular under the hood, as well as convenient way to save and share your creations.
User Interface:
This module loads as an empty shell that you can facilitate with any number of modules by tapping + button inside the container. Once your creation is complete along with all the necessary routings and/or internal signal processing, it’s time to clean up your custom UI. Find and enable ‘Hidden in compact view’ option in module preferences (tap header of any module inside your rack to access its preferences) for all of the modules you wish to exclude. (Many low level modules have this option enabled by default) Using the arrows in the top right corner of the rack, you can lock your creation for reduced, unified view. (Alternatively, you can enable Compact view from rack preferences, as well as further reduce UI to I/O only by enabling Fold option)
Being the most convenient way to save your creations, while in Compact view, two arrows will appear in the top left corner for quick preset switching.
I/O:
To accommodate various scenarios, Instrument rack is equipped with wide range of inputs. You can switch between CV (default) and MIDI modes in module preferences. Choose CV mode if you plan to integrate your creation into a typical modular environment, where an instrument is driven by Control Voltages or choose MIDI if you want to take advantage of many excellent third party MIDI sequencers, MIDI generators, and let Drambo take care of the necessary signal handling.
Additionally, Instrument rack is equipped with an audio input (which can come handy if your rack contains samplers you want to record into), Time signal input (which is crucial to keep e.g. LFOs in sync) and an audio output.
AN Kick
Description:
Digital recreation of the famous TR808 kick drum circuit, heard on countless records and loved to these days across numerous genres.
User Interface:
Two knobs, Tune and Decay is all you need to recreate everything that made the original so popular.
Wanna play bass line with a kick drum like a pro?
Just turn up the Decay, tap triangle left to the Tune knob, assign Pitch CV as a modulation source and turn the modulation amount all the way up.
Done! Use the keyboard to play your kick chromatically.
Additionally, Boost switch will enhance the contour, just like the accent does on the original box, altering the decay and the pitch slightly, which you can Parameter lock on the step basis or simply enable for maximum punch... I mean kick.
blob:https://forum.beepstreet.com/ac28985a-6bc0-4032-a412-9dea47ac4f81I/O:
AN Kick will accept Gate or Trig signals to generate audio and will AutoConnect to the nearest Gate or Trig source to its left when added.
Staying true to the original design, AN Kick does not respond to velocity by default when added. To achieve velocity sensitivity tap V at the bottom of the module and connect it to V source on MIDI to CV module.
AN Kick
Description:
Digital recreation of the famous TR808 kick drum circuit, heard on countless records and loved to these days across numerous genres.
User Interface:
Two knobs, Tune and Decay is all you need to recreate everything that made the original so popular.
Wanna play bass line with a kick drum like a pro?
Just turn up the Decay, tap triangle left to the Tune knob, assign Pitch CV as a modulation source and turn the modulation amount all the way up.
Done! Use the keyboard to play your kick chromatically.
Additionally, Boost switch will enhance the contour, just like the accent does on the original box, altering the decay and the pitch slightly, which you can Parameter lock on the step basis or simply enable for maximum punch... I mean kick.
blob:https://forum.beepstreet.com/ce62bb86-f1f1-48d9-9a0f-cbd348769eddI/O:
AN Kick will accept Gate or Trig signals to generate audio and will AutoConnect to the nearest Gate or Trig source to its left when added.
Staying true to the original design, AN Kick does not respond to velocity by default when added. To achieve velocity sensitivity tap V at the bottom of the module and connect it to V source on MIDI to CV module.
Oscillator (mini)
Description:
Essential building block for most types of synthesis.
Oscillator (mini) is nearly identical to Oscillator module in terms of functionality.
In terms of features, this oscillator is tailored towards various - typically digital - types of wave shaping, such as FM (Frequency Modulation), PM (Phase Modulation), PD (Phase Distortion).
Apart from the most common waveforms this oscillator features some unique ones as well such as Sine nine or Sine PD to support these synthesis methods.
User Interface:
Wave Shape: tap the field to reveal the list, or drag up and down to scroll through available shapes. Sine, Sine nine, Saw, Pulse, Triangle, Sine PD
Tune: use this knob to tune your oscillator continuously (free from chromatic scaling)
PW: Pulse Width control, applicable in the context of Pulse shape - where width can be reduced to 0 (inaudible) - and Sine PD shape - where the knob is used to adjust Phase Distortion amount.
I/O:
In most cases you would expect an oscillator to be playable from the keyboard, therefore when added, its Pitch CV input will AutoConnect to the nearest Pitch CV source (typically the Pitch CV output on the MIDI to CV module) to its left. Occasionally, you may want some of your oscillators to disregard pitch information from the keyboard. To do so, disconnect Pitch CV input by double tapping Pitch CV connector and choose Disconnect option.
Underneath, you can find an input that allows you to Hard Sync your oscillator to another oscillator. To do so, tap the Gate connector on the oscillator ‘to be synced’ and connect it to the Audio output of the oscillator ‘to be synced to’.
blob:https://forum.beepstreet.com/1fd6bada-63b3-4e20-b266-7316bcc2652dIn this configuration the Tune knob no longer determines the pitch - pitch is controlled by the sync source - instead, it generates often asymmetrical, harmonically rich shapes when modulated (e.g. by an ADSR envelope).
Antialiasing:
Wavetable oscillator
Description:
An ultra-clean wavetable oscillator, supporting Serum wavetables. Up to 256 waves in a single oscillator, up to seven voices stereo unison with an internal rack for advanced wavetable effects (PROCESSOR / SPECTRUM).
Comes with 41 wavetables by Echo Sound Works.
User Interface:
I/O:
Oscillator
Description:
Essential building block for most types of synthesis.
A standard subtractive-style oscillator with a variety of wave shapes and modulation inputs for Tune and PW parameters.
User Interface:
Easy to operate layout, where all available shapes are quickly accessible, along with the quantized tuning and dedicated Fine tune knob. Although Tune knob is quantized to chromatic scale via touch input, continuous modulation is supported via its modulation input, therefore can be utilised for FM or Hard Sync type of sounds.
I/O:
In most cases you would expect an oscillator to be playable from the keyboard, therefore when added, its Pitch CV input will AutoConnect to the nearest Pitch CV source (typically the Pitch CV output on the MIDI to CV module) to its left.
Additionally, you can Hard Sync it to another oscillator using Sync connector.
Antialiasing:
Oscillator: Supersaw
Description:
A perfect emulation of the famous JP8K supersaw oscillator with 7 detuned saw waves.
User Interface:
You can tune the oscillator using Tune (quantized) and Fine knobs. Width determines the amount of detuning applied to all voices. Use Mix knob to create the perfect balance between the core oscillator and the detuned voices and Stereo knob to spread those voices across the stereo field.
I/O:
FM operator
Description:
The basic element of FM synthesis.
Internal oscillator’s frequency or phase is linearly modulated by FM input. Internal feedback changes the shape of the oscillator from Square through Sine to Saw. Frequency ratio may be set to 0. In this case FM operator is ‘stopped’ and acts like a sophisticated wave shaper / through-zero oscillator.
User Interface:
FM Amount: Controls the amount of modulation applied by the source that is connected to its FM input.
Ratio: Base frequency ratio. Quantized via touch input, but allows other values as well via double tap pop-up menu.
Detune: Base frequency detune.
Phase / Freq: Switch between phase modulation and linear frequency modulation.
Feedback: Controls the amount of output signal that is fed back to FM input. Changes the wave shape from Square through Sine to Saw.
Attack, Decay: Controls the attack an d decay length of the internal amp envelope, which you can extend with sustain portion with Sustain switch.
Velocity: Amount of velocity influence on amp envelope level.
End level: Controls the bottom level of amp envelope.
I/O:
FM operator is a fully featured synth voice on its own, relying on number of connections. All these connections handled automatically. When added, it will AutoConnect to the nearest Gate, Pitch and Velocity CV sources to its left (usually from MIDI to CV module) as well as the nearest audio source to its left as a FM modulator.
Flexi sampler
Description:
A sophisticated sampler with a multitude of operating modes for various use cases.
It is tailored towards loop mangling, therefore a single sample can be loaded. (below are some examples for practical applications)
For more conventional sampler duties, such as using multilayered sample libraries please find Sampler module.
User Interface:
By default the module loads without any pre-loaded sample content.
You can either load a sample from your library or record audio directly into the module.
To load a sample, tap the waveform screen and pick a sample - typically a longer loop. Once a sample is loaded, by tapping the waveform screen you can enter the editor.
blob:https://forum.beepstreet.com/c47f42a6-cb9c-42e5-b0f3-d63c348c6f92Here you can Normalize and Trim your sample, as well as Set slices, automatically from the available submenu or manually by tapping the waveform to add/remove a slice and drag the header left/right to adjust it.
Alternatively, you can sample directly into the module. Please find Rec drop down menu at the top right corner of the module with additional controls for sampling.
blob:https://forum.beepstreet.com/0638f79a-ba15-49bb-8894-be6971bb21f3Source: Switch between the module input and all available audio inputs of your audio interface.
Sync: Switch between three recording sync modes. Instant will start recording as soon as REC button pressed, Pattern will start recording on the next pattern cycle and Threshold will start recording once signal is present at the input.
Clear: Will clear the waveform, but maintain the sample length and slices, so you can re-record audio into a pre-sliced buffer.
Remove: Will remove the sample along with the slices.
Monitor, REC: Buttons to monitor and sample from selected input.
With a sample loaded or recorded, it’s time to look into playback.
As mentioned above, Flexi sampler is aimed mainly at loop playback and mangling.
It does not support time stretching, therefore changing Pitch will change playback Speed and vice versa. Playback Speed ranges from +1 (full speed), through 0 (playhead stopped), to -1 (reverse playback). When loading perfect loops, you can use Sync drop down menu right to the waveform screen to determine the length of your loop in beats, so it can be stretched to fit your current project tempo. To avoid clicks at loop or slice points use Fade in / out controls. Use Velocity control to determine the velocity influence on playback volume.
Offset, Loop start and Loop end controls work in the context of the following playback modes:
(In these modes Start slice parameter options can be ignored as they only apply to 1-Slice mode)
Examples:
To accommodate all these playback methods, there are four Launch modes available. Trigger and Gate modes are generally useful when manual triggering is desired from keyboard or sequencer, while Transport and Pattern modes are available for convenient playback of longer loops synced to main sequencer.
I/O:
On top of the CV inputs (Pitch, Gate, Velocity), an additional audio input is available. Route any audio signal to this input, select Module input as source and start sampling.
Shot sampler
Description:
A simple one shot sampler. Samples containing markers are chopped and slices are played randomly (round-robin). An ideal building block for a drum sampler.
User Interface:
Minimalistic, self explanatory interface. Tap waveform screen to access sample editor, where you can Normalize, Trim your sample as well as Set slices for random playback.
I/O:
A single Trig input to trigger loaded sample or random slice.
Sampler
Description:
A multi zone sampler.
User Interface:
I/O:
Noise
Description:
Essential building block for most types of synthesis with two types of noises and stereo operation available. Although all frequencies are produced in equal intensity, White noise sounds brighter due to the nature of our hearing, which doesn't sense all frequencies equally. Therefore, people often prefer to listen to Pink noise, that boosts the lower frequency range or Brown noise, that puts even more emphasis on the lower frequencies.
User Interface:
Switch between White and Pink noises at the top of the module. Enable stereo for uncorrelated stereo noise. Additionally you can create Brown noise by adding an Integrator module (MATH / 1 OP / Integrator) after White noise.
blob:https://forum.beepstreet.com/c130d2c7-666f-485f-8945-693460438737I/O:
For polyphonic operation, connect gate input to a polyphonic gate output, such as MIDI to CV module gate output with Voice count greater than one.
Impulse
Description:
Create a short impulse from Gate and Velocity inputs. Useful but not limited to creating excitation impulses for the Modal Resonator, Comb Filter, Waveguide modules.
User Interface:
Impulse shape depends on the Shape setting and the impulse Length can be adjusted between super-narrow and up to 50ms. Noise allows you to add noise with the same envelope as the impulse and Tone is a simple 6dB low pass filter to further shape the signal.
I/O:
Will AutoConnect to the nearest Gate/Trig and Velocity source to its left when added.
This hasn’t been touched for quite some time so things definitely need adjusting, also this was meant to be a sort of beginners guide, with some basic tips and a lot of repetition so it sticks :D
with this new context a lot of bs can be edited out.
That's great to hear @rs2000. Thanks so much to you and @giku for taking the steps to get this rolling! I'm looking forward to contributing.
@rec
sorry to say, I would not find this helpful, its just basic stuff ...
what I would find useful are cookbook like tool tips
like this
(lala grabs a bunch of modules and runs away with it)
the other stuff is just basic lesson 101 stuff - what does this module do ...
how to combine stuff in interesting ways is much more inspirational, me thinks
(reading about the basic functions does not make you come up with stuff like this ;) )
btw. "brown noise" isnt named after the color ...
its about mr. browns discovery of molecular movements (nobel prize in the 20s) - this is a very strong hint - use me for modulation ... ;)
just understanding the basics doesn't get you very far, you need to understand how to combine basic things to make something amazing 🤔
you dont learn how to cook tasty food by reading the handbook of the stove and the pan ... ;)
this needs to work differently
I explain the basics to you while we are on the way (if I need to) of creating *something* makes way more sense to me 🤔
kind of like the tutorial projects in drambo are?
ppl are supposed to have fun and not feel "lectured" by reading a mind numbing dokumentation to door 101
if you dont know that need to use these 3 modules together to get it to do whatever ... it doesn't really help if you know what each of them does ... 🤷🏻♂️
"brown noise"
discontinuous structure of matter
this random process is so deeply embedded in the universe, its crazy 🤯
@rec, as a counterpoint to @lala’s comments, i think the stuff you’ve posted here would be extremely useful to beginners and i don’t think most new users have the time - initially at least - to learn through creative exercises in the way @lala suggests and that could just as easily feel like being lectured to anyway, just different approaches to teaching.
Surely the proposed wiki could encompass both approaches anyway? A catalogue of definitions for users who need that and a ‘cookbook’ for users who already understand the basics.
Your definitions would also work well in the module ‘?’ sections in app.
Good points @Robin.
I'm still thinking about the basic structure.
It looks like this now:
Drambo sections
Intro
.
How to get started
Building a basic synthesizer
Adding effects
Polyphony
...
Recipes, tips and tricks: How do I ... ?
.
Showcase: Projects and presets made by Drambo users
.
Modules
.
.
.
Block diagram
.
Integrating Drambo with your existing gear
.
Also, I'm planning to add a set of predefined tags for modules (like in Drambo's Add menu) and a separate set of tags for recipes and projects.
I'm leaning towards tags that focus on the result rather than on the theory behind it.
Opinions?
Sounds good to me @rs2000.
Perhaps stating the obvious, but in the ‘How to get started’ section (or somewhere), i would make sure to cover the ‘basics’ that users might wonder about if they’re coming from other audio software…e.g. setting up external equipment, sequencer/piano roll, export options, setting up patterns to play in sequence with repeats, automation, MIDI connections etc. Imagine a new user coming from their DAW of choice to Drambo and wanting to know how to do the everyday things every DAW does, i think it should cover this too as a reference guide even if only briefly.
@rs2000 I like this structure a lot! I think it’s great to get started. In my experience building similar knowledge banks, you’ll find out what needs more or less structure after you filled it out more, and this seems like the perfect amount of organization without being to rigid.
This isn’t related to the structure, but rather some ideas from a new user perspective. Drambo can be many things. The current manual touches on this, but I think it can be elaborated on and more friendly to new comers at the same time. What I mean by this is in the getting started section have guides thatnscrictly treat Drambo as one thing. ie Drambo the drum machine, Drambo the modular synth, Drambo the Midi arranger, Drambo the Sampler, etc. So instead of trying to give holistic overview it’s more like a series of different ways you could use it in your music workflow.
I bring this up because I’ve owned Drambo for many years but only recently got into it. For me that took minimizing its use to arranging for a while. But for others it may be something else. Drambo is a DAW in sheep’s clothing and like any daw it can be a lot to take in on first use. I’d be happy to try and write one of these as an example.
Really excited to dive into the wiki. Thanks for setting it up!