all right
-
- Banned
- 1256 posts since 22 Feb, 2014
hi i am trying to make a 6db filter i dont really know how heres a picture of wot i have done i have mapped the freq of both filters to one knob
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Try to find out more about what you're trying to do. The tools are all there but you need to know what you're trying to do if you're going to achieve it.
Although never lose sight of happy accidents along the way
.
Although never lose sight of happy accidents along the way
.-
- Banned
- Topic Starter
- 1256 posts since 22 Feb, 2014
by default the filter is 12db but i want it down to 6db i trying to have a 6db high pass and low pass so i can add each of to each side of the eq i am so lost in all this
-
- Banned
- Topic Starter
- 1256 posts since 22 Feb, 2014
okay i found this picture see the fabfilters low cut is at 6db thats wot i want with mulabs eq
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Sorry, I have no idea what you are talking about. You need to provide context so other people understand you. We are not looking over your shoulder as you work, so you have to write a lot of clear explanation.runaudio wrote:by default the filter is 12db but i want it down to 6db i trying to have a 6db high pass and low pass so i can add each of to each side of the eq i am so lost in all this
MuX has a 1p Lowpass filter. This means it cuts 6dB per octave. The two are synonymous.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
-
- KVRian
- 1451 posts since 4 Oct, 2012 from Utah
runaudio,
What we are trying to tell you is to think it through yourself. Learn the tool set you have. Read the docs, learn about sound design and audio engineering, and figure out ways to achieve your desired wishes.
We're try to get you to learn how to solve your problems on your own so you don't have to depend on the community to answer your questions. Research and experimentation are things you will need to use and learn to solve your own problems.
Here's a list of modules MUX comes with: http://mutools.com/info/docs/mux/mutools-modules.html
Now, learn what each module does and is capable of doing. Once you've got a rough idea, start trying to build the desired product. This is called problem solving, or, in business terms, engineering. Using the tools you have to solve your problems. Asking for help, comes only after you have tried multiple ways to solve the problem, providing logic and workflow so we can view and check it, and by understanding that you are your own engineer. We are not here to work for you. We are here to help you when you get stuck.
If you need specialized modules that MUX may not (yet) supply, look into VST frameworks like reajs from Cockos, or even develop your own VST's from native languages such as c or c++.
Find ways to solve your problems instead of asking others to solve them for you. We can help you with logic and explanations, but won't make it for you. There's an old saying, "Give a man a fish, feed him for a day. Teach a man to fish, feed himself for a lifetime."
Dakkra
P.S This is not to be taken as offence. This is meant to explain what we do to get to where we are. This advice/method alone can not only make you a good audio engineer, but also a good person in general.
What we are trying to tell you is to think it through yourself. Learn the tool set you have. Read the docs, learn about sound design and audio engineering, and figure out ways to achieve your desired wishes.
We're try to get you to learn how to solve your problems on your own so you don't have to depend on the community to answer your questions. Research and experimentation are things you will need to use and learn to solve your own problems.
Here's a list of modules MUX comes with: http://mutools.com/info/docs/mux/mutools-modules.html
Now, learn what each module does and is capable of doing. Once you've got a rough idea, start trying to build the desired product. This is called problem solving, or, in business terms, engineering. Using the tools you have to solve your problems. Asking for help, comes only after you have tried multiple ways to solve the problem, providing logic and workflow so we can view and check it, and by understanding that you are your own engineer. We are not here to work for you. We are here to help you when you get stuck.
If you need specialized modules that MUX may not (yet) supply, look into VST frameworks like reajs from Cockos, or even develop your own VST's from native languages such as c or c++.
Find ways to solve your problems instead of asking others to solve them for you. We can help you with logic and explanations, but won't make it for you. There's an old saying, "Give a man a fish, feed him for a day. Teach a man to fish, feed himself for a lifetime."
Dakkra
P.S This is not to be taken as offence. This is meant to explain what we do to get to where we are. This advice/method alone can not only make you a good audio engineer, but also a good person in general.
Software portfolio
M.N.I.E - soon to be my musical portfolio
Hey, I'm Eurydice(Izzy for short) - she/her
M.N.I.E - soon to be my musical portfolio
Hey, I'm Eurydice(Izzy for short) - she/her
-
- KVRAF
- 3161 posts since 28 Mar, 2008 from a Galaxy S7 far far away
I agree to an extent, but...dakkra wrote:runaudio,
What we are trying to tell you is to think it through yourself. Learn the tool set you have. Read the docs, learn about sound design and audio engineering, and figure out ways to achieve your desired wishes.
We're try to get you to learn how to solve your problems on your own so you don't have to depend on the community to answer your questions. Research and experimentation are things you will need to use and learn to solve your own problems.
Whilst learning Rainmeter, I had absolutely no idea how to use it. As such the forum's were the place to go. They have the same philosophy as you, but that's no help when the basics aren't understood. Now I understand how Rainmeter code works, I can do most things with it, bar a few I haven't tried.
The same applies here. If you don't understand the basics of how modules work then trying to figure it out is like trying to figure out what's wrong with a program's source code with zero knowledge of the syntax. You gain a little info here and there, but because those pieces don't relate to each other it's difficult finding out what needs doing to achieve a desired result, as it was with Rainmeter.
So, yes, I agree to a certain extent, but for beginners, it's far easier to ask for help with basics than to spend days, weeks or sometimes months trying to figure stuff out when you have no reference point from which to learn from.
The docs are too sparse to be of any help for beginners. I don't know how to use many of the modules in mux and I also require help from time to time, that's surely the point of forums? To ask those with more experience than you for help. How would the human race have got where it is if we didn't share knowledge and help those in need? You have to give what you learnt so others may follow, not all of us have degrees in music tech, or spend all our time making music.
Beginners require guidance to get on the right path in any and every area of life, this is no exception. What may be a simple answer to one is another's nightmare, leaving people to fend for themselves is NOT the answer!
Anyway, no ill will intended here just my pov
@runaudio:
Please take the advice and explain better what you are trying to achieve and for god sake start using punctuation!
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
The module docs are not a guide to synthesis. Such resources are available, however, if you just go looking. Sound On Sound was a great resource when I was learning (I'd have provided a link but their website isn't that friendly).
I don't mind pointing to information sources if the questioner needs help in framing the question but I object to answering the same question repeatedly when an answer has been given. If the answer given wasn't understood then it should be referenced in the same thread and the point of shortcoming explained, so appropriate further assistance can be given. Starting a new thread for the same question is not useful to anyone.
I don't mind pointing to information sources if the questioner needs help in framing the question but I object to answering the same question repeatedly when an answer has been given. If the answer given wasn't understood then it should be referenced in the same thread and the point of shortcoming explained, so appropriate further assistance can be given. Starting a new thread for the same question is not useful to anyone.
-
- KVRAF
- 3161 posts since 28 Mar, 2008 from a Galaxy S7 far far away
I appreciate that comment fully. I thought it a bit 'off' myself to be honest!
I'm sure it was due to not getting an answer though?!
Personally, I haven't a clue what the purpose of this thread is!! The question has surely been answered:
Though it's good fun playing with mux in new ways sometimes, like with CS Piky, that was interesting and helpful in understanding certain parts. Like the MFO, didn't have a clue what the point of it was
But now I can see how it is used, at least in one aspect. But that aspect is very useful for adjusting waves from front panels.
This is all very much a hobby, just a mess about for me, nothing serious, just something to break the tedium from time to time, but it is great fun, even though my music's shit!
I'm sure it was due to not getting an answer though?!
Personally, I haven't a clue what the purpose of this thread is!! The question has surely been answered:
I admit I know virtually nothing about synthesis on a modular level! I simply look for sounds and edit thempljones wrote:MuX has a 1p Lowpass filter. This means it cuts 6dB per octave. The two are synonymous.
Though it's good fun playing with mux in new ways sometimes, like with CS Piky, that was interesting and helpful in understanding certain parts. Like the MFO, didn't have a clue what the point of it was
But now I can see how it is used, at least in one aspect. But that aspect is very useful for adjusting waves from front panels.
This is all very much a hobby, just a mess about for me, nothing serious, just something to break the tedium from time to time, but it is great fun, even though my music's shit!
-
- KVRian
- 877 posts since 28 Feb, 2015 from Interstella 5555
You've made my daysl23 wrote:This is all very much a hobby, just a mess about for me, nothing serious, just something to break the tedium from time to time, but it is great fun, even though my music's shit!
jokes apart the important thing is to have fun , nothing else matters