|
|
Jan 19, 2013 at 3:42pm
Sorry if this is the stupidest noob question, BUT.. !?
How do I use multiple ezadc objects and control them individually in the same patch, rather all of them turning on or off when I press one ?
I have checked help, but cant seem to work this seemingly tiny problem out :-(
|
|
|
Jan 19, 2013 at 3:57pm
I’m assuming you want to selectively send audio out to your output, but turning on/off ezdac is not the way to go about that. As you’ve seen, all ezdacs are connected together because you are literally turning on/off ALL audio processing when you press one. If you want to send audio out look at the gain~ or *~ objects, and you can connect whatever you want to those, then send all of them to ezdacs, or dacs, and have individual control over each section.
|
|
|
Jan 19, 2013 at 4:03pm
Hi, thanks
Sorry I didn’t explain myself too clearly. I want to control the ezadc separately from the ezdac. For example I want to be able to record through the mic but don/t want to the mic on all of the time and don’t want to have to turn the mic off itself as I am using the internal mic.
|
|
|
Jan 19, 2013 at 4:07pm
I guess adding the gain is the best bet then, and just work with the volume !.. thanks :-)
|
|
|
Jan 19, 2013 at 4:57pm
Yeah, use gain or *~ or anything else. The way you’ve been using ezdac/ezadc is not what they are meant to be used for. (ie they always stay on if you are processing audio). Just figure out the routing/levels another way.
|
|
|
Jan 19, 2013 at 6:57pm
As Rodrigo et. al. have pointed out, the ezdac~ object, by default, turns on audio processing globally. You *can* enable and disable audio in a patcher window, however – you might want to open the ezdac~ help file and look at the tab marked “local” for more on that. But the ezdac~ object isn’t intended to turn off audio – there are other alternatives to this, such as the gate~ object.
Have you considered using the “search” feature and then exploring what it gives you while you’re patching? It’s a good way to learn about using Max.
|
|
|
Jan 19, 2013 at 8:20pm
@Gregory
and my own favourite personal Max guru, called “See Also”
..but not in this specific context obviously
|
|
|
Jan 19, 2013 at 9:22pm
|
|
|
Jan 21, 2013 at 6:13pm
@n00b_meister
Spot on!
+ idly browsing the object explorer, pecking here & there at a help file !
Rooster_mode/off
|
|
|
Jan 22, 2013 at 9:53pm
Put a gate after the adc~. Connect its outlet to the right inlet of a gate~ object. Attach a toggle to the left inlet. When the toggle is X’ed, your adc~ signal will pass through. This works with dac~ as well.
|
