I tried to make a stand alone synth with both effects and simple voices patche.
I tried to make a stand alone synth with both effects and simple voices patche.
We don't have much discussions going on here, so I am not sure if it is a good idea to add even more sections.
How about you post in Modular Discussions? If we get more activity about related gear we will add a new section an move the posts.
Beep, Bopp, Bleep: info@modulargrid.net
I would recommend to buy a Math and a VCA next.
and ohh.. say goodbye to your savings ;)
-
ringhof.bandcamp.com
I went for the MI Veils, nothing to complain here. I choosed it because of its layout, each channel on a horizontal line.
-
ringhof.bandcamp.com
Absolutely awesome module for bass, I find the 2 and 4 density saws (when used with low spread and a put through any low-pass filter) to me feels very reminiscent of the Korg MS-20's dual VCO's.
While I don't use the 8 density often it has a nice thick sound to it that works well for stabs or ambient drones.
A wee bit harder to chew than the two latest tracks that I posted. Some dissonance, a bit off beat in places and "creatively" mixed.
I hope you like it anyway! I do. But all comments, positive or negative, are highly appreciated.
The generated melody comes from my 0-coast, the hand chased melody comes from my Minilogue, the background ambience and the plucky bell sound comes from Rings (of course ).
But who's the drummer? The first correct answer will be rewarded with a pineapple owl.
I was wondering the same. I went for the intelijel and it seems great I've never used the others listed here. Other options are the Tangle Quartet or that Zlob one which is 6 vca in 8hp I believe?
recently bought a few modules from great and awesome fellow wigglers here on modulargrid:
@El_Miguel
@mindmachines33
@qleonetti
@Delabelle
@Jinx
@mac6mal
@phineas
@theartstrip
@tans
thanks!
I have improved the search function. If you search for a user in this thread only the posts containing the username are shown. The old behaviour showed every post and just highlighted the search term. It's easier now to find out if a user is mentioned.
-- modulargrid
Would it be nice to have a section for gear related to modular music, but that is not a module by itself?
I am thinking of the Organelle, OP-1, Korg SQ-1 but maybe also eurorack cases.
Hi I am new to Eurorack, I have been using softsynths for a few years and wanted to get into Eurorack, I use Reaktor as will as a Omnisphere and other Spectrasonics software, I want to incorporate Eurorack with my DAW and use it standalone also , I have a Beastsetpro and a Kordbot for sequencing . Any suggestions would be helpful. I tend do a lot of ambient stuff.
Bought a module from @gummyboy - great communication, great packaging. Buy with confidence!
thx for the feedback. i used the rampage all five central outputs, as well as some of the gates. vcdlfo sine, tri and the lfo out from the mother32. along with turing machine and volts breakout
Bought a module from @lenni and picked it up personally. Great guy and the module is in excellent condition.
Thank you.
I just cleaned up.
-- ParanormalPatroler
Just wow and thank you!
Beep, Bopp, Bleep: info@modulargrid.net
Thoroughly enjoyed your lfo patch. Sounded very much like someone playing a harp. How many lfo did you use
These are my thoughts for a first eurorack – I'd love any feedback on the modules chosen or if there's anything I'm really overlooking.
In addition to this rack, I also have a Make Noise 0-Coast and a Korg SQ1. Will the SQ1 be sufficient as a starter sequencer for this rack? Eventually I'd like to add the Rene or Stillson Hammer MKII, and perhaps a Volca Beats for drum rhythm.
Thanks much in advance.
hello :) i created a nice patch using all my lfo's controlling each other, the result went thru a quantizer into rings and clouds. turned out quite interesting self running thing:
hope you like it, too ...
cheers, ello
I just cleaned up. The only untagged modules on the Grid are the ones locked by manufacturers etc. I contacted them via the Contact Manufacturer button asking if they can tag their modules appropriately. Here's hoping they'll do it.
Anyway, it's just a few. Did the rest myself!
Hi folks,
A first batch of the 3340-based Aemit VCO II is produced, 7 have been shipped, 3 more are available at the introductory price of 199 Euro (not including shipping).
Feature highlights :
Audio and low range from 45 sec. to 40 kHz.
Span, coarse and fine tune.
Exponential response, 1V/octave.
4 FM inputs, 1 linear FM.
Rising and falling sawtooth, PWM "pulsaw", PWM pulse, triangle and sine outputs.
Soft and hard sync.
See : https://www.modulargrid.net/e/aemit-vco-ii
Check it out !
Aemit Eurorack modules
Had a great experience doing business with @dombles. Thanks!
I already DELETED 30+ tags of some notorious modules ;)
-- modulargrid
Holy crap! LOL.
BTW, I meant to say Atlantis showed up before Batumi, not first. The ordering is working fine for me per the spec you mentioned.
I already DELETED 30+ tags of some notorious modules ;)
Beep, Bopp, Bleep: info@modulargrid.net
Did not see your first message: The order you have is "Newest". The default order wasn't switched when clicking on a tag. That should be fixed by now.
However you can still change the sort orders any time, if people want the old representation with "most popular first" it is possible.
-- modulargrid
Looks good to me! I think it's an elegant solution ... but now I feel compelled to go tag those 10-15 modules that have no tags whatsoever
I'm using Firefox 56.0.1 (64-bit). I just clicked on the "Frequency Divider" tag (no other search options) and I got (in order of appearance): Compare 2 (Comparator, Dual/Stereo, Frequency Divider, Logic), Divide & Conquer ..
-- ParanormalPatroler
Did not see your first message: The order you have is "Newest". The default order wasn't switched when clicking on a tag. That should be fixed by now.
However you can still change the sort orders any time, if people want the old representation with "most popular first" it is possible.
Beep, Bopp, Bleep: info@modulargrid.net
Followup: ok, it works when using the drop-down. Just checked with Frequency Divider again and it works just fine. It does not work when clicking on a tag though, just so you know. My offer still stands if you need to test.
-- ParanormalPatroler
Ah, those little blue tag links in the module short description box? They should work now too.
Beep, Bopp, Bleep: info@modulargrid.net
Ok, this is interesting. A few thoughts. I think the penalty could work, but it may take some time. For example, I sorted by LFO. Batumi, which is clearly an LFO has 4 tags and shows up way, way down on the page (Atlantis showed up first until I removed all tags but Synth Voice). This could prompt manufacturers to use less tags so that placement is higher on the page. The solution implemented sort of works, but not for items that are tagged heavily.
Atlantis showed up first, when you selected LFO? This is wrong, maybe there is a bug in the code :(
The PRIMARY FUNCTION could be the new database field. It would mean that many modules would not have that particular field filled out for a while, but eventually we'd get there.
I see. I am not totally against it, but I know there would be a lot to change with the version system ...
Side note: I am not pushing this agenda, I am just having a conversation. I work in a filed where we bounce ideas off each other all day long, so I am not married to any of my ideas, just trying to spur creative thinking.
-- dysonant
It's completely fine, we need ideas to improve.
Beep, Bopp, Bleep: info@modulargrid.net
Followup: ok, it works when using the drop-down. Just checked with Frequency Divider again and it works just fine. It does not work when clicking on a tag though, just so you know. My offer still stands if you need to test.
PP.
It should work. Which browser are you using, which function/tag are you looking for?
Yes, that is the idea.
-- modulargrid
I'm using Firefox 56.0.1 (64-bit). I just clicked on the "Frequency Divider" tag (no other search options) and I got (in order of appearance): Compare 2 (Comparator, Dual/Stereo, Frequency Divider, Logic), Divide & Conquer (Clock Modulator, Frequency Divider), DIV (Clock Modulator Frequency Divider), Burst (Clock Generator, Clock Modulator, Frequency Divider, Random), ... , 4046 Shaper (Frequency Divider).
Can't upload a screenshot it seems but hit me up via PM if you want to Skype this out; I can share my screen there and you'd have a different system to demo this.
Is it working though? 'Cause I'm searching based on tag only and I get mixed number of tags on the results.
It should work. Which browser are you using, which function/tag are you looking for?
I would assume the ones with just that one tag would appear first, no?
Yes, that is the idea.
Beep, Bopp, Bleep: info@modulargrid.net
We have that update now. What do you think?
-- modulargrid
Is it working though? 'Cause I'm searching based on tag only and I get mixed number of tags on the results. I would assume the ones with just that one tag would appear first, no? Anyway, I think it's a great idea to be honest. We should definitely go with that one.
Side note: I am not pushing this agenda, I am just having a conversation. I work in a filed where we bounce ideas off each other all day long, so I am not married to any of my ideas, just trying to spur creative thinking.
-- dysonant
Don't worry man, I don't think anyone is in love with their ideas here. We're all pushing for a better user experience when it comes to using MG; that's the end goal! Personally, I really enjoy these types of conversations anyway.
Hey everyone I've recently fallen into the clutches of eurorack and decided to use (almost) all DIY modules. This is my first rack; what do you all think?
Ok, this is interesting. A few thoughts. I think the penalty could work, but it may take some time. For example, I sorted by LFO. Batumi, which is clearly an LFO has 4 tags and shows up way, way down on the page (Atlantis showed up first until I removed all tags but Synth Voice). This could prompt manufacturers to use less tags so that placement is higher on the page. The solution implemented sort of works, but not for items that are tagged heavily.
I know what I had suggested previously may have been too complex, but this is why I suggested it. If there are two lists from which to tag. Where the first list is PRIMARY FUNCTION and users are only allowed to select a single primary function but as many SECONDARY FUNCTIONS as they like, then you could easily sort by PRIMARY FUNCTION.
In the ADD/EDIT portion of the site you could have a dropdown for primary function, so you would not have to have duplicative checklists.
The PRIMARY FUNCTION could be the new database field. It would mean that many modules would not have that particular field filled out for a while, but eventually we'd get there.
Side note: I am not pushing this agenda, I am just having a conversation. I work in a filed where we bounce ideas off each other all day long, so I am not married to any of my ideas, just trying to spur creative thinking.
I am experimenting to implement a ranking for the results. If someone is explicitly searching by function the modules with less attached functions will be prioritized in the ranking. That means there will be a penalty in the listing position for the swiss army knife and overtagged modules.
We have that update now. What do you think?
Beep, Bopp, Bleep: info@modulargrid.net
Sorry for the confusion. You cannot add new modules to a large rack with expired unicorn account.
I will change that in the description.
Beep, Bopp, Bleep: info@modulargrid.net
From the Unicorn FAQ:
"And my big Racks?
They stay big. But you can not enlarge them anymore and you can not create new ones if this would hit the limits."
This was my understanding when I paid for a Unicorn account: that I would not be able to create or enlarge racks that were over the size limit if the I allowed the Unicorn account to expire. I did expect that I'd still be able to change modules on the existing large rack, however--which isn't the case.
The FAQ should be updated to reflect this.
There was a time when one could select a module function, such as "VCA", and be presented with list of modules that served that function.
It's hard to get this right, because it is not only a technical problem but also a question of definition.
I think we have 2 problems here:
We have a best practice for that @ParanormalPatroler already explained:
the question that tagging needs to answer to is whether a module can be used as X or not. If the answer is yes, then the tag should/could be applied.
e.g. if a module is labeled as a VCA it has to have input and output jacks to be used as a VCA in conjunction with other modules. If there is somewhere a VCA burried in the module you cannot access it is not right to tag it as a VCA. It is a community effort to get the tags right.
If you have a synthvoice with accessible patchpoints it is o.k. to tag that module as VCA.
Still people looking for just a VCA don't want to have a synthvoice listed at the first places in their result.
One easy and immediate solution to this problem would be to limit the tag option down to 2-3 tags at maximum
Sure that would work too, it would be the easiest and quickest solution, but it would feel almost like cheating ;)
Btw. we already have a max limit.
Damn, I had a detailed and great response queued and clicked submit to be presented with a login.
Sorry!
I wonder if a broader category like "Modulation" with sub feature filters that one could select multiple feature from would work?
I understand the idea but I am not very much into the category/subcategory topographies. It gets academic and inconsistent very quick. Beginners will be overwhelmed, the UI will be difficult and the SQL queries will be slow/complex. If it is possible to keep it flat and simple I am in for that.
I am experimenting to implement a ranking for the results. If someone is explicitly searching by function the modules with less attached functions will be prioritized in the ranking. That means there will be a penalty in the listing position for the swiss army knife and overtagged modules.
So searching for VCA will get you the simple building blocks first.
I think that might be a good thing because manufacturers have to think about the main function of their module.
The main idea is to not add any new functionality but to just magically get better results.
Beep, Bopp, Bleep: info@modulargrid.net
Absolutely. I do this all the time, but it's a lot of stuff and my time is limited. Also, manufacturer lock :)
True, but so is everybody else's, including the people who mod the site. This is a community effort, we all pitch in somewhat.
Sorry if that came off dismissive, didn't mean it that way. Just meant that even with all the people doing this right now, it is a difficult and time consuming process.
[...] I wonder if a broader category like "Modulation" with sub feature filters that one could select multiple feature from would work? For example the user could select the FUNCTION Modulation and then select 1 or more multiple FEATURES like Attenuator, Envelope Generator, Mixer.
I am not sure adding a multifuntional tag would solve the problem. Though the idea is right in that broader categories to encapsulate modules main function might be beneficial. This is provided more detailed sub-tagging could be applied and the method for searches allowed one to select multiple features. It could mimc ecommerce product listing page filters. For example, if one is looking at a product listing page for the t-shirts category then could then select the colors black, red and blue from a filter list and not have to see white, yellow and orange.
I think you're simplifying the problem to a degree which is not realistic. Color is an attribute and can easily be defines as a subgroup of a product category. It is a rather obvious one and makes for an easy UX choice, whereas functionality VS features are interchangeable attributes. To extend your example, where does Mixing fit in terms of Utility? Is it a subcategory of Utility or a different function entirely? This is all subjective as we try to define usage in an area which by definition tries to avoid it. Modulation, right, what about all the oscillators that can go to LFO speeds? It's a can of worms.
You are correct, I am over-simplifying the problem. Mostly so that I can wrap my head around it abstractly without actually doing any real work. To really dig in to it someone would have to look at all that data and begin t structure it. I do this all the time for work and it can be a nightmare. I am actually running into an issue with this right now where products are both categories and attributes. Though in my case, there is a hell of lot less that what exists on MG. And yeah, maybe modulation is not a good idea, but trying to start somewhere.
Again, in my most humble opinion, the problem we're facing is having too many disparate modules on the grid. If we get the option to merge, categorize as one-off creations or manufactured (because not all manufacturers are properly listed) and then allow for a maximum of 3 tags per module, that could make things far more easier to navigate. What if a module can do more than those three things? Well, you know what, that's what manuals and demo videos are for. We also have a huge database of info on MW FB and MW forum and that's what the internet is here for.
Yeah, I can see how having multiples is a problem. Not including the micro-Braids, there are 9 distinct Braids modules on the grid. Merging those into one using the multiple panel feature would be a huge start towards cleaning things up.
And I totally agree on the manual/video/forum point about getting more detailed descriptions. Maybe you are on to something with limiting the tags.
Absolutely. I do this all the time, but it's a lot of stuff and my time is limited. Also, manufacturer lock :)
True, but so is everybody else's, including the people who mod the site. This is a community effort, we all pitch in somewhat.
[...] I wonder if a broader category like "Modulation" with sub feature filters that one could select multiple feature from would work? For example the user could select the FUNCTION Modulation and then select 1 or more multiple FEATURES like Attenuator, Envelope Generator, Mixer.
I am not sure adding a multifuntional tag would solve the problem. Though the idea is right in that broader categories to encapsulate modules main function might be beneficial. This is provided more detailed sub-tagging could be applied and the method for searches allowed one to select multiple features. It could mimc ecommerce product listing page filters. For example, if one is looking at a product listing page for the t-shirts category then could then select the colors black, red and blue from a filter list and not have to see white, yellow and orange.
I think you're simplifying the problem to a degree which is not realistic. Color is an attribute and can easily be defines as a subgroup of a product category. It is a rather obvious one and makes for an easy UX choice, whereas functionality VS features are interchangeable attributes. To extend your example, where does Mixing fit in terms of Utility? Is it a subcategory of Utility or a different function entirely? This is all subjective as we try to define usage in an area which by definition tries to avoid it. Modulation, right, what about all the oscillators that can go to LFO speeds? It's a can of worms.
Again, in my most humble opinion, the problem we're facing is having too many disparate modules on the grid. If we get the option to merge, categorize as one-off creations or manufactured (because not all manufacturers are properly listed) and then allow for a maximum of 3 tags per module, that could make things far more easier to navigate. What if a module can do more than those three things? Well, you know what, that's what manuals and demo videos are for. We also have a huge database of info on MW FB and MW forum and that's what the internet is here for.
Personally I don't have much of a problem with the tagging system as it is; I don't even mind being able to give all the tags for all I care. I would only make the question more apparent when someone uploads a module "Can it provide this functionality to other modules?" and have the uploader tag the module as such. It's easier for users to have to answer a question than not, it helps to focus. But you raise a fair point as we do see tags being misused.
Damn, I had a detailed and great response queued and clicked submit to be presented with a login. Ugh. I'll try to respond again, but it's gonna be much simpler.
Why not edit the modules you deem as tagged inappropriately with what you think is the correct tag and serve the community while helping yourself?
Absolutely. I do this all the time, but it's a lot of stuff and my time is limited. Also, manufacturer lock :)
For instance, I find that Maths is primarily an Envelope Generator and not a Utility module, so you can clearly see that our points of view on what the main Function of a module is might differ.
True that, I wonder if a broader category like "Modulation" with sub feature filters that one could select multiple feature from would work? For example the user could select the FUNCTION Modulation and then select 1 or more multiple FEATURES like Attenuator, Envelope Generator, Mixer.
That being said, as I replied on your FB post, the question that tagging needs to answer to is whether a module can be used as X or not. If the answer is yes, then the tag should/could be applied.
I would definitely not want to limit the amount of information or anyones ability to cross-list items. I just think there may be abetter solution. Totally agree with you that if a module can be used as X it should state that.
Do not forget that some manufacturers tend to overstate what their modules contain and might also overtag just for marketing purposes; I have no concrete examples of their MO but I have seen some examples of overtagging when a module cannot actually offer such functionality. I simple edit on my part solved that but it's not always possible, especially if a Manufacturer decides to lock the module's description, as is their prerogative.
I think this could be solved with the suggestion I am proposing.
One easy and immediate solution to this problem would be to limit the tag option down to 2-3 tags at maximum. No exceptions. That would force uploaders/manufacturers to really have to decide what type of Function each module serves and by which tag it is best described. Does that mean that some modules would be underserved or underrepresented in particular categories? By all means, yes, that would be the case, especially for modules that have a million functions (I'm thinking Maths or Sports Modulator as good examples of that), but in my opinion that is a small price to pay to make MG cleaner.
It would certainly help get the ball rolling on cleaning up the data. Then maybe creating a FUNCTION drop down and a FEATURE attribute based filter might be easier.
We could add a multifuntional tag as a representative of that particular category. A "well, it does more than that" type of thing.
I am not sure adding a multifuntional tag would solve the problem. Though the idea is right in that broader categories to encapsulate modules main function might be beneficial. This is provided more detailed sub-tagging could be applied and the method for searches allowed one to select multiple features. It could mimc ecommerce product listing page filters. For example, if one is looking at a product listing page for the t-shirts category then could then select the colors black, red and blue from a filter list and not have to see white, yellow and orange.
But then again, I prefer clarity. Someone might disagree. r
To me, this is all about clarity.
Why not edit the modules you deem as tagged inappropriately with what you think is the correct tag and serve the community while helping yourself? For instance, I find that Maths is primarily an Envelope Generator and not a Utility module, so you can clearly see that our points of view on what the main Function of a module is might differ.
That being said, as I replied on your FB post, the question that tagging needs to answer to is whether a module can be used as X or not. If the answer is yes, then the tag should/could be applied. Do not forget that some manufacturers tend to overstate what their modules contain and might also overtag just for marketing purposes; I have no concrete examples of their MO but I have seen some examples of overtagging when a module cannot actually offer such functionality. I simple edit on my part solved that but it's not always possible, especially if a Manufacturer decides to lock the module's description, as is their prerogative.
One easy and immediate solution to this problem would be to limit the tag option down to 2-3 tags at maximum. No exceptions. That would force uploaders/manufacturers to really have to decide what type of Function each module serves and by which tag it is best described. Does that mean that some modules would be underserved or underrepresented in particular categories? By all means, yes, that would be the case, especially for modules that have a million functions (I'm thinking Maths or Sports Modulator as good examples of that), but in my opinion that is a small price to pay to make MG cleaner.
We could add a multifuntional tag as a representative of that particular category. A "well, it does more than that" type of thing.
But then again, I prefer clarity. Someone might disagree.
Hi MG folks,
I posted a mini-rant about this (i'm in no way upset or angry, just a little frustrated) on the Facebook MW group about module function tagging . There was a time when one could select a module function, such as "VCA", and be presented with list of modules that served that function. Now when a user selects "VCA" they get result that include modules like "Percussa Super Signal Processor " which kind of defeats the purpose of categorization.
I understand that many modules have multiple functions and there is a benefit to cross-listing. I question the usefulness when that modules extra functions do not really meet the criteria of the function filter. The example above is extreme, because it illustrates how a user looking for a VCA will be presented with something utterly ridiculous for that function. Other cases like a drum module being cross listed as an Envelope Generator, because it has an EG, but that EG is not accessible for use with other modules, begs the question of it's intended function.
I do not have a solution, I wish I did. It was mentioned on Facebook that maybe there should be a logical separation of Function and Feature. For example, MATHS is many things and should by all means be cross-listed. However, it is at it's core a Utility module. If I could select the Function of Utility then further refine my filter by Feature tags, that would solve both the need for users and people listing modules with many uses. So basically, all modules could have a single main function and then have an unlimited number of features. The Function categories could be a little more broad to encapsulate the wide range of features many modules have.
I understand that, if implemented, it would require a large amount of data normalization and refinement. I am not totally sure how to handle something like that as I have not given it any thought beyond this sentence :)
I hope this all makes sense and it's not coming off sounding like nonsense or a complaint. I care about this site and use it daily.
(@kmacinski) Thanks to @lenni and @mnpzn for fast shipping and good packaging!
Thanks for the reply/tips.
I think I'm going to focus on the VCO/effects side of things to start with as I can use the Deluge for sequences and beats at the start then as I get further down the line I can decide to expand.
Plenty of research to do in the meantime which is exciting!
Hello, this is my current setup, minus the Beast-Tek Rich Glitch I have which I couldn't find on ModularGrid.
I am enjoying where I'm at, after about 5 months of wriggling - however I feel a little lost as to how to make my rig more like an instrument that a single sound source generator (if that makes any sense).
Also I can't for the life of me work out what I am doing with the Erica ADSR :/ ! ..and the Recti-Combi is slightly confusing.
I'd like to be able to have my set-up be able to play as a self contained unit, for rhythmic & ambient styles, and also in conjunction with Ableton which is why I added the CV Pal.. considering getting a Beatstep pro too.
Anyway, just thought I'd throw it all out there and see if anyone had suggestions or advice for me - much appreciated!