El Capitan recording issues

[Wouter1]

IMPORTANT please comment on this ticket only if you have something new to report regarding recording with my driver on El Capitan

In #64 @vitalibondar reported

Recorded sound is distorted (Reaper, Logic, Quicktime).
https://cloudup.com/ihcV-dV6lWL

[Wouter1]

@vitalibondar do you see any problem reports in the log files while recording?

[vitalibondar]

@Wouter1 Yes. http://pastebin.com/gyAkjkNp

And another video with clean driver installation (update after installation native original driver). I see error after while: https://cloudup.com/iV7M_CWCNpU

Just for information: original EMU driver installed without errors, but don't work (no playback, no recording, no messages in kernel log).

[vitalibondar]

Many users are reporting problems with different usb-audio interfaces in El Capitan

[Wouter1]

ok thanks vitalbondar for the log contents.

Basically the log contains this

Oct 3, 2015, 12:13:42 kernel[0]: RingBufferDefault<USBInputRing>::push warning. Ignoring overrun
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples err reading ring: e00002e7
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples err reading ring: e00002e7
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples err reading ring: e00002e7
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: RingBufferDefault<USBInputRing>::push warning. Ignoring overrun
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples err reading ring: e00002e7
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples err reading ring: e00002e7
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples err reading ring: e00002e7
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP
Oct 3, 2015, 12:13:42 kernel[0]: EMUUSBAudioEngine::convertInputSamples READ HICKUP

[Wouter1]

It seems that the driver works fine for some but not for others. Normally, recording has to work first, after that playback (which is sync'ed to the recording channel).

@djohayn you reported playback works fine on your machine for playback. What machine do you have (hardware)?

@vitalibondar what is your machine?

[Wouter1]

0x2e7 = data underrun. We are not receiving the expected amount of data from the EMU.

@vitalibondar do you have the EMU directly connected to your computer or is there a hub in between?

[Wouter1]

Just for information: original EMU driver installed without errors, but don't work (no playback, no recording, no messages in kernel log).

Thanks.

Not sure what to make of that. But it suggests that something important in the USB or audio system has changed.

The original driver has the original code signature from creative so that explains why it loads without the extra hacks.

[Wouter1]

My first impression is that the USB system calls back my code with a signal that the data is ready, but that the data is not there.

[Wouter1]

@vitalibondar I opened your linked audio sample https://cloudup.com/ihcV-dV6lWL with audacity and I see you have four channels sampled.

Can you try what it does if you sample only 2 channels, eg with audacity?

[Wouter1]

Checked the code that generates the reported error messages.

This happens when CoreAudio (the mac kernel) calls our code to fetch audio samples but too early, when the samples are not available.

This can mean that the coreaudio is out of sync, or that there is not enough data coming in from the USB. Or maybe something does not initialize properly.

[vitalibondar]

@Wouter1 3 files: mono (reaper), stereo (audacity), 4 channels (quicktime) https://cloudup.com/cAPCLc1UF-Y
Something else: after turning off/turning on EMU, driver cannot loaded. I must reinstall it.

[vitalibondar]

@Wouter1 I have MacBook Pro (Retina, 13-inch, Late 2013) 8 GB RAM.
upd.: the EMU directly connected to my computer.

[Wouter1]

Thanks for the update. This should all work fine on a late 2013 rMBP, I even can use the rMBP with a hub between the compu and the EMU.

I hear 'one two' very soft, with loads of echo in the reaper mono.
The stereo has just loads of clicking.
The 4 channels has same 'one two', again very soft and only on channel 1.

There are repeated blocks of silense in the recording, and duplicate blocks of data.

[Wouter1]

As you mentioned, there seem lots of troubles with audio in El Capitan.

Maybe we should wait a bit and see how this develops after the first update of El Capitan?

[vitalibondar]

@Wouter1 I agree, that it makes sense.

[Wouter1]

EmptyFruit also has a rMBP, just a bit newer.

Some things have changed on the audio side : dual microphones, and support for digital out through the headphone port (I suppose). But on first thought, that would only complicate matters on the NEW rMBP, not on the old one where the drivers were written for.

I will wait till El Capitan 2 is out before digging deeper into this.

[Wouter1]

@vitalibondar just a small shot in the dark, but can you confirm that your /System/Library/Extensions/EMUUSBAudio.kext (and all files inside) have mode 755 (drwxr-xr-x), and are owned by "root", group "wheel"?

[Wouter1]

And, what does this give you

kextutil -tn /System/Library/Extensions/EMUUSBAudio.kext/

[vitalibondar]

@vitalibondar just a small shot in the dark, but can you confirm that your /System/Library/Extensions/EMUUSBAudio.kext (and all files inside) have mode 755 (drwxr-xr-x), and are owned by "root", group "wheel"?

@Wouter1 Sorry, but i can't check this. I have installed Yosemite.

[Wouter1]

ok thanks, I hoped you had El Capitan installed on a separate partition.

[vitalibondar]

@Wouter1 I'm sorry, but I just updated my computer when El Capitan has appeared in App Store.

[Philipondio]

Hi Wouter & Vitali,
so I'm wondering: If I don't use the interface to record, but solely to listen to music, will that work on El Capitan?
I have the Emu Tracker Pre USB btw., and no problems with my other interfaces (RME Babyface, Geekout 1000).
Thanks! Phil

[Wouter1]

Thanks for your interest in my driver.

I received mixed reports about how it works in El Capitan. For most users it seems fine (there were 135 visitors last week and I assume most were here to download it). Vitalibondar however never got it working and had to go back to Yosemite.

I did not yet switch to El Capitan (I wait at least till version 2 I think) so I have no first hand feedback.

If you try, can you please report back here if it works for you.

[Wouter1]

I got a thank-you message from Joachim from Germany for a nicely working EMU tracker pre under mac os el capitan.

Just mentioning as this is another indication that for most users the driver still works ok.

[lofiatunes]

Record audio (EMU-0404 USB) not work on OS X El Capitan.
Direct Monitor works fine!
Midi IN/OUT without complaints!
S/PDIF not tested.

MacBook Pro Retina, 15-inch, Mid 2014

[Wouter1]

@digdelu thanks for reporting! You're also the first to report that midi is working, great to hear that.

[Wouter1]

I created an external drive with a comletely fresh install of El Capitan to test this issue.

Unfortunately El Capitan was completely crashing every time I plugged in the network cable. This ate up all my time. Filed a bug report with Apple 23132686. Also posted https://discussions.apple.com/message/29125446#29125446

[Wouter1]

@roddy20 @Laximus Sorry for the late response, I am on holidays and mostly without internet. Yes you can change the plist manually and re-install, or just re-download and install the driver from github.

I am not aware of the issue with sleeping for longer periods.

[Laximus]

@Wouter1 Thank you the answer. =) Yes it's strange , but its only happen when the high latency workaround installed, not everytime, but sometimes happens. When I revert to the original latency, there is no this sleeping issue. Thank you anyway. =)

[Laximus]

@Wouter1 One more question please.: first when I installed your driver I had to enter this command: csrutil enable --without kext in terminel in recovery mode. Do I have to do it every time when I am changing the latency time or revert to the origonal latency or not? Or do I have to do anything in recovery to change this line back to the original state? Hope you understand what I mean. Thank you!

[Wouter1]

@Laximus the csrutil setting is remembered so doing it once is sufficient. Maybe iyou need to re-run if you upgrade to a higher version of the OS.

It has nothing to do with the latency of the driver.

To recover to original state, just re-download the driver. The low-latency script changes values in the original file and can be used only once.

[Laximus]

@Wouter1 Thank you =) I mean the original state of the csrutil.

[Wouter1]

@Laximus
oh, for the original state of csrutil, you have to re-run csrutil I assume. Never tried that. You will need to check the csrutil to disable the option. I expect something like csrutil disable

Notice that you must leave it enabled (so --without kext) if you want to continue using the driver.

[Laximus]

@Wouter1 Thank you the quick response. There was an Os update, and after the driver works like charm, I wouldnt have to do it again. =) But I did. =DDDD It works.

[Emptyfruit]

@Laximus , hi. Can you, please, be more specific, what update and what you mean by "works like a charm" ?

[Laximus]

@Emptyfruit Hi! Of course. There was an OSX update around a week ago: 10.11.4 and after this update the EMU-driver from here and the EMU device works great, and the high latency workaround works too for audio recording. Sorry for not to be clear. =) My device is an EMU USB 0202.

[Emptyfruit]

Thanks. So the recording issue is still present. :(
On 8 Apr 2016 11:50, "Laximus" notifications@github.com wrote:

@Emptyfruit https://github.com/Emptyfruit Hi! Of course. There was an
OSX update around a week ago: 10.11.4 and after this update the EMU-driver
from here and the EMU device works great, and the high latency workaround
works too for audio recording. Sorry for not to be clear. =) My device is
an EMU USB 0202.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#65 (comment)

[eabarth]

This driver worked well for me the first time I used it. I plugged in a mic and it sounded totally normal. Went to use it today, and the recording is all garbled. Weird that it just stopped working all of a sudden. I haven't updated anything.

[Wouter1]

@eabarth are you on El Capitan and did you apply the high latency setting?

[eabarth]

Thanks for responding so fast! I'm on El Capitan (latest update) but haven't messed around with latency settings. Since it just worked the first time I tried it, I thought I'd be good with the defaults.

I don't see instructions on how to apply a high latency setting, just the article on how to make it low latency. If there's a common fix I should be trying, can you link me to instructions? Sorry to bother you with my noobishness.

[Wouter1]

@eabarth I updated the installation pages and added an extra script to simplify installation on El Capitan.
Can you give it a try?

[eabarth]

Yes, I got it to work! Thanks for that!

[eabarth]

Hmm. It worked for a while, but then it suddenly became all garbed again. Not sure what triggered the change.

Resetting the interface and reopening the control panel seemed to fix it (whereas yesterday, it didn't). Now it's working. So for now, I'm good—don't mind having to reset once in a while, I guess. I'll keep you updated if I notice any patterns or anything that fixes it.

[Wouter1]

@eabarth glad you got it working. Yes sometimes the interface needs to be resete with the control panel. My guess is that the EMU settings sometimes get garbled.

[Laximus]

@Wouter1 Hello, I would like to write a report, that the wake up issues on El Capitan/iMac somehow is related to this driver or to the hardware itself. Or the Apple didnt write properly something in the USB drivers. I used your driver, and was lot of wake up issues with EMU USB 0202 - kernel panics, and have to restart the iMac almost from every second sleep state. Around a week ago I dont use the EMU USB 0202 at all, it's not even pluged to the iMac by usb, and no wake up issues at all. I really apreciate your work of course, I just want to report this. Thank you.

[Wouter1]

@Laximus thanks for reporting. I madee separate ticket as this is not a recording issue.

[Wouter1]

ANYONE please comment on this ticket only if you have something new to report regarding recording with my driver on El Capitan

[Laximus]

Oh, it's true. Sorry for the OFF!

[Wouter1]

@vitalibondar @Philipondio @digdelu @eabarth @Emptyfruit @adrian-polglase @boredomisacrime @maxflex @Laximus @roddy20

Good news!

New version of the EMU driver! The latency and recording issues seem to be resolved.
Can you please check if it works for you?

Sorry for the long time this took. It took a huge amount of work to adapt all the changes that Apple made to the USB drivers.

[Emptyfruit]

Wow, that's very good news. I hope I'll be able to try shortly. Also let's
hope apple won't kill it again in Sierra.. :)
On 12 Jul 2016 00:25, "Wouter1" notifications@github.com wrote:

@vitalibondar https://github.com/vitalibondar @Philipondio
https://github.com/Philipondio @digdelu https://github.com/digdelu
@eabarth https://github.com/eabarth @Emptyfruit
https://github.com/Emptyfruit @adrian-polglase
https://github.com/adrian-polglase @boredomisacrime
https://github.com/boredomisacrime @maxflex https://github.com/maxflex
@Laximus https://github.com/Laximus @roddy20
https://github.com/roddy20

Good news!

New version of the EMU driver! The latency and recording issues seem to be
resolved.
Can you please check if it works for you?

Sorry for the long time this took. It took a huge amount of work to adapt
all the changes that Apple made to the USB drivers.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#65 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AORnz7gSzsbEIWqAUKZzt8fTYCd1L1i2ks5qUrS5gaJpZM4GIYM2
.

[Laximus]

WORKS! WORKS! Thank you so much! =) I tried it with the low latency version, audio record is perfect. I will try later with normal latency as well! Yeehaaa! Thank you!!!!

[Wouter1]

Great to hear! Glad that it all works :)

[sookiesookie6]

This works for me except that a lot of plugins no longer work, when I switch back to built in audio they start working again. Just talking about built in plugins like the Pitch plugins etc.

Is there a setting I need to change perhaps?