This took me a while to figure out!
I'm on the latest version osx using a line6 ux8. On the first load of Audiomulch I can set up a sound in contraption and connect it, but no sound will come out until I double click on it to open it. If I start a new scene everything works as expected.
Line6 was terrible drivers so it's probably their fault and it's not a huge issue. I'm just posting in case it helps someone else.
You shouldn't need to double-click SoundIn (I assume you mean open it's property editor), but you do need to make sure audio is enabled on the toolbar (speaker icon).
Yeah, I have to open it's property editor. Since updating to 10.6.5 audiomulch crashes while using the line 6 toneport ux8 as soon as I double click on the sound in.
The Line 6 issue sounds like it might be something else. Please could you email the crash report to me at rossb@audiomulch.com
I need to understand what you're doing before I can suggest a remedy. I don't think I'm understanding your explanation of what you're doing.
If you just open one of the example files that doesn't use SoundIn and press play on the transport toolbar does it work?
When you say "double click on sound in" do you mean in the contraptions list at the left of the patcher, or on the contraption node in the patcher itself once you've created the soundin contraption.
Thanks!
Ross.
Well, I figured out why it was crashing. Somehow under Audio Driver the sound out had been set to built in output. Changing both the in and out to the UX8 fixed it, but still it would nice to use both. Maybe I have to make an aggregate device? Although I am pretty sure I use both in other programs.
Sorry about not being clear about the steps. I add a sound in device into the patcher either by right clicking or going to the side bar. Once it's added if I double click to open the properties audiomulch crashes. Hope that makes sense. It doesn't have to be wired to the sound out. I still have to open the properties to get sound in to turn on though.
Is the crash report just all the info in the "Problem report for Audiomulch" ?
it starts with :
Process: AudioMulch [1291]
Path: /Applications/AudioMulch 2.1.1/AudioMulch.app/Contents/MacOS/AudioMulch
Identifier: com.audiomulch.AudioMulch
And goes on and on and on. I don't want to fill your email up if it's the wrong thing :)
Thanks.
Using an aggregate device is probably the best option for now. But I'd still like to resolve the underlying issue so please do send the crash report . The crash report will go on and on, that's ok. Here's the easiest way to get it:
- Run the Console app. You can find it at: Applications/Utilities/Console
- In the tree in the left column navigate to:
LOG FILES > ~/Library/Logs > CrashReporter
You should see some AudioMulch crash logs there.
- You can right-click or control-click on them and choose "Mail" to email them to me at rossb@audiomulch.com
But back to your original issue, let me get this straight:
1. You launch AudioMulch.
2. Open an example patch (for example Examples/Applied/PondLife.amh)
3. You press the Play or toggle the Enable Audio button on the transport toolbar
4. You hear nothing
5. You create a SoundIn contraption. Still no sound.
6. You double click on the SoundIn contraption in the patcher to show its editor and now, finally you hear sound.
Is that what's happening for you?
Thanks
Ross.
Internal sounds work fine. Pondlife will start playing immediately. If I make a SoundIn and connect it sound will not come in until I open the properties.
A new detail I've noticed is that if I start a new patch after opening the properties of SoundIn it works as soon as it is patched into SoundOut, I no longer have to open the properties.
I can also make a SoundIn, open the properties without patching it to sound out and then make a new file and again the SoundIn works as soon as it's connected without opening the properties.
I just sent the crashlog. Hope it helps.
Thanks for sending the crash report. I'm afraid i'm still not sure what that problem is but I'll try to sort out out.
As far as the SoundIn issue goes, I think I misunderstood you before. My current understanding is that It's not that sound doesn't work without SoundIn -- I imagine you could plug a TestGen into SoundOut and you would hear it as soon as you turned up the volume. What you're seeing is that SoundIn input from an external source isn't working until you open the SoundIn properties editor, is that correct? (that would still be quite strange but it gives me something to look in to).
Ross
Yes, that's it, the actual line in on my Line6 UX8 usb sound card won't activate until I open the properties panel of SoundIn.
I think it might have something to do with the UX8's "tone direct monitoring" function that allows me to monitor the inputs on ports 1+2 with very low latency.
I can also hear inputs 1+2 without wiring them to SoundOut as soon as I open the SoundIn properties.
I'll do some testing on ports 3-8 to see if they operate differently.
Thanks.
Try going to AudioMuclh > Preferences > Audio Driver and make sure the Open all channels checkbox is checked.
Let me know if that makes a difference.
Thanks