I read the thread you posted. I thought the Drambo Wiki was created by Beepstreet. But in fact, it was created by the users themselves. I didn't know that.
Modular Garden Flow. The link didn't open for me for some reason.
I think screenshots of the modules and links to YouTube videos that exist could be added to the Drambo Wiki. Ideally, a description of the knobs and functions would be included.
I think this option is informative. These are my thoughts.
The thing that causes me the most headaches STILL is how clocks and timing relate to the transport. How to just get things working reliably and predictably. I,ve gotten to the point where I just make a custom clock module thing and try and bypass the main clock signal as much as possible. I must be missing something.
I always welcome new modules in Drambo - wonderful work @giku ! But I would love if the needed documentation (Module help) is released together with the module and not postponed to a later date. Make it a personal policy - I would appreciate this. I am writing this because of today's honestly frustrating experience:
I want to send sysex messages - wow there is the MIDI sysex generator module! Let's see: A text input field that accepts all kinds of characters? What do I need to enter? Hex? With spaces? With start and stop bytes? Can I enter multiple messages? OK - let's look in the module help: "No module help yet. Come back later :-(".
Yeah, I must admit, the “No module help yet. Come back later” is really frustrating. As @catherder suggests, just write it as the module is released; then it’s done and not a chore to add to the list of things that need doing at some point.
And, since the subject has been mentioned, a lot of modules with help text only have a very brief description of what they are and nothing more. They barely, I’m afraid, fit the definition of ‘Help’.
This would be the thing I feel is lacking from Drambo documentation in general: too much of it seems to be geared towards people who already have experience and knowledge of modular systems and the concepts behind the various modules - it too often assumes a level of understanding which may not already be present. True, it’s a big task to explain everything from scratch, assuming no previous knowledge, but it depends how accessible you want Drambo to be?
It occurs to me that with the release of Otoo, aimed at more novice users, maybe some documentation for Drambo that doesn’t assume any previous experience is all the more needed? I can easily imagine Otoo users taking the step up to Drambo (if that’s one of the hopes that Otoo will achieve?) and being utterly bewildered! Being able to open Otoo projects in Drambo in some way could be used as a way to get Otoo users started and help with this process perhaps?
Precise values can be calculated for a cheat sheet, but it depends on several numbers. Drambo’s normalized signal convention, buffer size, sample rate, tempo
But it’s totably doable though, with all data I’d figure it pretty quick in excel (not bragging)
True, and I missed some variables. But it’s worth figuring the math underlying, if only as a learning experience. It’s been a while since I went that rabbit hole, but it’s not magic science. The only wizard here in that regard is @rs2000 besides @giku of course
I’d say my biggest struggle was with understanding how polyphony worked in Drambo. I learned a lot from videos on YouTube but having clearly written documentation would be great.
Other things that flew past me included the pitch standard, how gates work and the morph and meta randomiser modules. Also how handy Flexi-sampler can be once you know all it can do.
Sometimes was made me lost was a bug, so although new features are very exciting, fixing bugs can make things much easier for newcomers. I generally have a talent for finding edge cases, it must be said.
Some of the naming of modules or other features are confusing. Quantise acts like a floor function rather than rounding (I think?). So a manual could include alternative names for certain modules or features for people that come from other domains.
"Other things that flew past me included the pitch standard, how gates work and the morph and meta randomiser modules. Also how handy Flexi-sampler can be once you know all it can do."
Some good points here especially the pitch standard.
Comments
Agreed and in regards to English we all speak japanese here. ;)
In regards to screenshots
I found these lurking on my computer.
TK32 did these quite awhile back.
I read the thread you posted. I thought the Drambo Wiki was created by Beepstreet. But in fact, it was created by the users themselves. I didn't know that.
Modular Garden Flow. The link didn't open for me for some reason.
I think screenshots of the modules and links to YouTube videos that exist could be added to the Drambo Wiki. Ideally, a description of the knobs and functions would be included.
I think this option is informative. These are my thoughts.
Half an hour isn't zero, so that's good.
By the way, I had a launchpad, and it didn't last long. But the APC40, in my opinion, is the best combination so far.
polyphony ...still kind of struggling ...
The thing that causes me the most headaches STILL is how clocks and timing relate to the transport. How to just get things working reliably and predictably. I,ve gotten to the point where I just make a custom clock module thing and try and bypass the main clock signal as much as possible. I must be missing something.
This! Especially when using the Signal modules
I always welcome new modules in Drambo - wonderful work @giku ! But I would love if the needed documentation (Module help) is released together with the module and not postponed to a later date. Make it a personal policy - I would appreciate this. I am writing this because of today's honestly frustrating experience:
I want to send sysex messages - wow there is the MIDI sysex generator module! Let's see: A text input field that accepts all kinds of characters? What do I need to enter? Hex? With spaces? With start and stop bytes? Can I enter multiple messages? OK - let's look in the module help: "No module help yet. Come back later :-(".
Yeah, I must admit, the “No module help yet. Come back later” is really frustrating. As @catherder suggests, just write it as the module is released; then it’s done and not a chore to add to the list of things that need doing at some point.
And, since the subject has been mentioned, a lot of modules with help text only have a very brief description of what they are and nothing more. They barely, I’m afraid, fit the definition of ‘Help’.
This would be the thing I feel is lacking from Drambo documentation in general: too much of it seems to be geared towards people who already have experience and knowledge of modular systems and the concepts behind the various modules - it too often assumes a level of understanding which may not already be present. True, it’s a big task to explain everything from scratch, assuming no previous knowledge, but it depends how accessible you want Drambo to be?
It occurs to me that with the release of Otoo, aimed at more novice users, maybe some documentation for Drambo that doesn’t assume any previous experience is all the more needed? I can easily imagine Otoo users taking the step up to Drambo (if that’s one of the hopes that Otoo will achieve?) and being utterly bewildered! Being able to open Otoo projects in Drambo in some way could be used as a way to get Otoo users started and help with this process perhaps?
I still have issues with LFO timing of the LFOs, Graphic Modulator and Graphic Env.
Any suggestions or cheat sheets on timing?
@snickast
It depends upon what you need to do.
For example;
If you want the LFO's in perfect sync or as near as then connect them with the Time signal (which I do most of the time)
and use the Scale time module to create multipliers or dividers of the tempo.
If you need the LFO's to be freewheeling yet have the tempo then you use them as is and set them to either Prog or Beat,
there's a sync input which you can use to reset the multiple LFO's to the begin at the same time.
There's many different ways.
What is your use case?
Precise values can be calculated for a cheat sheet, but it depends on several numbers. Drambo’s normalized signal convention, buffer size, sample rate, tempo
But it’s totably doable though, with all data I’d figure it pretty quick in excel (not bragging)
That's good to know.
A look up table for the LFO's and what dRambo CV values that the dRambo modules use was what I needed when I started.
Like many of us early dRambonauts I went ahead memorised the lot.
Not all of the modules react the same to cv modulation for instance when the ADSR, attack, decay and release sliders need
automation we have to use the SLider/Knob/ + Morph module combination and attack doesn't move linearly or even expotentially.
There are a few other quirks still a lot to play around with even the quirks.
True, and I missed some variables. But it’s worth figuring the math underlying, if only as a learning experience. It’s been a while since I went that rabbit hole, but it’s not magic science. The only wizard here in that regard is @rs2000 besides @giku of course
Agreed.
I can brute force a lot of stuff but the finesse for math definitely rs2000 and giku.
I’d say my biggest struggle was with understanding how polyphony worked in Drambo. I learned a lot from videos on YouTube but having clearly written documentation would be great.
Other things that flew past me included the pitch standard, how gates work and the morph and meta randomiser modules. Also how handy Flexi-sampler can be once you know all it can do.
Sometimes was made me lost was a bug, so although new features are very exciting, fixing bugs can make things much easier for newcomers. I generally have a talent for finding edge cases, it must be said.
Some of the naming of modules or other features are confusing. Quantise acts like a floor function rather than rounding (I think?). So a manual could include alternative names for certain modules or features for people that come from other domains.
@VinylDinosaur
"Other things that flew past me included the pitch standard, how gates work and the morph and meta randomiser modules. Also how handy Flexi-sampler can be once you know all it can do."
Some good points here especially the pitch standard.