Behringer U-Control UCA202 not recognised on Mac OSX
-
- F7 - Goldenseal
- Posts: 19
- Joined: Fri Jul 28, 2017 2:28 pm
Behringer U-Control UCA202 not recognised on Mac OSX
Anyone able to help fixing this? Maybe it's because there's no driver installation for the soundcard??
[soundcloud]https://soundcloud.com/boimesa/dive-perspecticals[/soundcloud]
- Duchamp
- Site Admin
- Posts: 41
- Joined: Thu Mar 08, 2012 6:42 pm
Re: Behringer U-Control UCA202 not recognised on Mac OSX
Does the UCA202 work with other audio apps? If not, there's something wrong at the OS level (and we have zero control over it).
-
- F7 - Goldenseal
- Posts: 19
- Joined: Fri Jul 28, 2017 2:28 pm
Re: Behringer U-Control UCA202 not recognised on Mac OSX
Yes! I've tried it in garageband and it works fine there.. :S?Duchamp wrote:Does the UCA202 work with other audio apps? If not, there's something wrong at the OS level (and we have zero control over it).
[soundcloud]https://soundcloud.com/boimesa/dive-perspecticals[/soundcloud]
- Duchamp
- Site Admin
- Posts: 41
- Joined: Thu Mar 08, 2012 6:42 pm
Re: Behringer U-Control UCA202 not recognised on Mac OSX
Ok, so please paste here the log file/output. Remember to enable debug messages in Configuration -> Misc -> Debug messages. Thanks!
-
- F7 - Goldenseal
- Posts: 19
- Joined: Fri Jul 28, 2017 2:28 pm
Re: Behringer U-Control UCA202 not recognised on Mac OSX
I'm not getting any debug messages eventhough i've activated it :S
Everything is connected: the ins and outs but when arming the master it just won't give off any sound eventhough i do see certain peaks and spikes in the db meter..??
Everything is connected: the ins and outs but when arming the master it just won't give off any sound eventhough i do see certain peaks and spikes in the db meter..??
[soundcloud]https://soundcloud.com/boimesa/dive-perspecticals[/soundcloud]
-
- F7 - Goldenseal
- Posts: 19
- Joined: Fri Jul 28, 2017 2:28 pm
Re: Behringer U-Control UCA202 not recognised on Mac OSX
Can i send a video showing whats happening??
[soundcloud]https://soundcloud.com/boimesa/dive-perspecticals[/soundcloud]
- Duchamp
- Site Admin
- Posts: 41
- Joined: Thu Mar 08, 2012 6:42 pm
Re: Behringer U-Control UCA202 not recognised on Mac OSX
Back from a long vacation.
A video won't help much now: we need to figure out the debug messages first. Go to the configuration window, select "Misc" tab, enable debug messages "to file". Since you are on OS X, you'll find a giada.log file in [your_home]/Library/Application Support/Giada/. Then please paste here the output.Boi_social wrote:Can i send a video showing whats happening??
-
- F1 - Bilberry
- Posts: 1
- Joined: Sun Dec 03, 2017 5:04 pm
Re: Behringer U-Control UCA202 not recognised on Mac OSX
I'm having similar issues and have a whole development system setup with debugger etc. and have posted a couple of similar-ish bugs on Github.
I will have some time over the holiday break and hope we can make some progress over the next couple of weeks.
I'm currently stuck, not being particularly familiar with the codebase and a couple of quick pointers could really get me in a position to at least find the exact failure points for more Giada-experienced code-hands to work out if I can't figure it out myself.
ssteinerX
I will have some time over the holiday break and hope we can make some progress over the next couple of weeks.
I'm currently stuck, not being particularly familiar with the codebase and a couple of quick pointers could really get me in a position to at least find the exact failure points for more Giada-experienced code-hands to work out if I can't figure it out myself.
ssteinerX
- Duchamp
- Site Admin
- Posts: 41
- Joined: Thu Mar 08, 2012 6:42 pm
Re: Behringer U-Control UCA202 not recognised on Mac OSX
Excellent, I know our wise @monocasual on GitHub is already working with you on the problem. Let's continue there, since it's a more development-oriented issue. Thanks for your time!steve.steiner wrote: ↑Wed Dec 20, 2017 4:18 pmI'm having similar issues and have a whole development system setup with debugger etc. and have posted a couple of similar-ish bugs on Github.