search

ms0547212 / soundflower

Automatically exported from code.google.com/p/soundflower
GNU General Public License v2.0
0 stars 1 forks source link

Weird Sound Artefacts #24

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

1. Install Soundflower 1.4.3 with Soundflowerbed
2. Use (2ch) as Main Output, so I can use the Volume controls on my Audio DJ 8
3. In Audio Setup, I use 96kHz and 32 Bit (well actually the Soundcard does
only 24 bits, but there is only this choice) It does not seem to matter
which channel is used on the Audio Hardware.

What is the expected output? What do you see instead?

After a while, the Sound is completely muted or I can hear some strange
humming distorted nois which sound like a Buffer Overrun. In fact, with a
smaller Buffer, the Artifacts can be heard sooner and generally with a
higher pitch. For example, with a Buffer Size of "2048" it takes about one
hour before the Artefacts appear (seems to be a fixed amount of time), with
a buffer size of "64" its only a matter of minutes.

All in all, this Bug reminds me of "Issue 21" - so this might not be
related to my Audio Hardware

I can "fix" the Bug by just selecting any Buffer Size when the error
appears, but of course it will reappear a certain amount of time (depending
again on Buffersize).

What version of the product are you using? On what operating system?

I use Soundflower 1.4.3 in Mac OS X 10.5 

Please provide any additional information below.

Audio Hardware: Audio DJ 8 from Native Instruments

Original issue reported on code.google.com by kuderm...@alphanull.de on 18 May 2009 at 4:27

GoogleCodeExporter commented 8 years ago 
I have the exact same problem, but my Interface is a Native Instruments Audio 4 
DJ.

Original comment by felip...@gmail.com on 15 Jun 2009 at 2:53

GoogleCodeExporter commented 8 years ago 
I've also tried the latest drivers from Native Instruments, without success.

Original comment by felip...@gmail.com on 15 Jun 2009 at 3:02

GoogleCodeExporter commented 8 years ago 
I have the same issue with a MOTU Ultralite on 10.5.7

Original comment by coreykai...@me.com on 4 Jul 2009 at 5:03

GoogleCodeExporter commented 8 years ago 
I'm using Mac OS-X Leopard 10.5.{6,7} also.

Original comment by felip...@gmail.com on 4 Jul 2009 at 7:48

GoogleCodeExporter commented 8 years ago 
Any hints on how to solve this bug?!

I'm running the latest version of Soundflower on Snow Leopard (MacBook 3.1), 
with
latest drivers.

It appears to be some kind of buffer overflow. When the artifacts occurs, 
clicking on
Soundflower menu item and reselecting the interface temporarily solves the 
problem.

Original comment by felip...@gmail.com on 4 Oct 2009 at 6:41

GoogleCodeExporter commented 8 years ago 
I also have an issue just like thi.

SF/SFB worked perfect on Leopard, I am wondering whether to go back until a fix 
is found? As this seems to 
have happened sine i upgraded to SL. Although I have not confirmed that yet...?

Ableton 8.0.05 into SF 1.5.1 then into Audacity 1.2.5 // AH Pro 2.9.4

Have also tried through Audio HiJack, but, because the trial is time locked, 10 
minutes is not enough to see if 
the problem replicates through that app...?

Original comment by randomge...@btinternet.com on 4 Oct 2009 at 1:16

GoogleCodeExporter commented 8 years ago 
Forgot to add the specs... 

 MacBookPro 5.2 17 Uni
 Intel Core 2 Duo
 2.66 GHz
 4 GB

Snow Leopard 10.6.1

Original comment by randomge...@btinternet.com on 4 Oct 2009 at 1:19

GoogleCodeExporter commented 8 years ago 
This bug occured with Leopard too. I've never been able to suscessfully run
Soundflower with my NI Audio 4 DJ sound car.

Original comment by felip...@gmail.com on 4 Oct 2009 at 2:58

GoogleCodeExporter commented 8 years ago 
Issue 21 has been merged into this issue.

Original comment by 74obje...@gmail.com on 6 Oct 2009 at 10:21

GoogleCodeExporter commented 8 years ago 
Issue 19 has been merged into this issue.

Original comment by 74obje...@gmail.com on 6 Oct 2009 at 10:22

GoogleCodeExporter commented 8 years ago 
Issue 10 has been merged into this issue.

Original comment by 74obje...@gmail.com on 6 Oct 2009 at 10:23

GoogleCodeExporter commented 8 years ago 
Issue 40 has been merged into this issue.

Original comment by 74obje...@gmail.com on 6 Oct 2009 at 10:26

GoogleCodeExporter commented 8 years ago 
I have reproduced this problem using Max/MSP generating a sine wave with the 
AudioTester patcher -> 
SoundflowerBed.

Original comment by 74obje...@gmail.com on 6 Oct 2009 at 11:02

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
This problem does not require a Firewire audio interface -- it will occur with 
the built-in sound device.  

It is not at all obvious from looking through the code where the problem is 
occuring.

MacMini
Intel Core Duo
1.66 GHz
1GB
10.6.1

Original comment by 74obje...@gmail.com on 6 Oct 2009 at 5:08

GoogleCodeExporter commented 8 years ago 
Do you have an estimate on when this bug will be solved and a new version 
released?
Thanks.

Original comment by felip...@gmail.com on 6 Oct 2009 at 5:53

GoogleCodeExporter commented 8 years ago 
Phew, I'm glad this has been picked up.

I am gutted not being able to lay anything down at present, without sitting on 
tender hooks, waiting for the 
drops and clicks.

If you need any audio samples, feel free, I can provide to demo the problem

Original comment by randomge...@btinternet.com on 6 Oct 2009 at 8:36

GoogleCodeExporter commented 8 years ago 
Glad these apparently related issues have been picked up & merged. Thank you - 
please mail me if there is 
anything specific you would like tested.

Original comment by shoarth...@gmail.com on 10 Oct 2009 at 4:23

GoogleCodeExporter commented 8 years ago 
Coming in with my 2¢ here. I'm running soundflower on snow leopard, on a 
macbook3,1 
without any issues.

    One thing I've noticed about my laptop is that it ALWAYS is emitting faint buzzing and 
higher pitched beeping, whenever the soundcard is powered on. This is not a 
soundflower 
issue; this is a hardware issue. It is only noticeable when using headphones 
and when no other 
audio is playing (but the soundcard has not been cycled off). Additionally, 
messing with the 
audio settings, such as switching audio devices, will cause the soundcard to 
cycle off and "fix" 
this issue.

    Could it be possible that some you with the "buffer overrun" issue are simply experiencing 
the effects of the macbook's relatively average soundcard as well? Of course, 
this doesn't apply 
to those who are experiencing high cpu usage as well, I believe that's a 
separate issue.

Original comment by perconta...@gmail.com on 19 Oct 2009 at 5:39

GoogleCodeExporter commented 8 years ago 
@percontation: no, this has nothing to do with what you described. 1) if you 
hear the
sound you will immediatly know it is _not_ an hardware issue 2) it happens on 
certain
Soundcards, not with the apple chip. 3) I don't have a macbook ;-)

So really, it is soundflower itself which needs to be fixed

Original comment by kuderm...@alphanull.de on 19 Oct 2009 at 9:52

GoogleCodeExporter commented 8 years ago 
@percontation: I have a NI Audio 4 DJ interface and a MacBook 3,1. It does emit 
the
faint buzz ONLY when my MacBook sleep or is powering off. When it's on, the 
faint
buzz does not appear.

This faint buzz was introduced since I upgraded my system to Snow Leopard. I 
don't
know if it's a software issue, or if it's just a coincident hardware failure.

I don't know if it's related to SoundFlower also. But I have completely 
uninstalled
SoundFlower and the faint buzz becomes evident when I put my MacBook to sleep.

But this is a issue that doesn't botter me at all.

Original comment by felip...@gmail.com on 19 Oct 2009 at 1:58

GoogleCodeExporter commented 8 years ago 
@percontation: What does botter me is that SoundFlower does not work. Whenever 
I run
it with my Native Instruments Audio 4 DJ, after some period of time, the audio 
is
"jammed", and the weird sound artifacts appear. The audio only returns to 
normal when
I click in some option of the SoundFlowerBed icon in the menu bar.

*** But I think this bug may be perceived ONLY with expensive audio interfaces 
with
very low latency. Cheap ones, like the onboard audio interface of the MacBook, 
may
not have present the issue. ***

Original comment by felip...@gmail.com on 19 Oct 2009 at 2:04

GoogleCodeExporter commented 8 years ago 
Evidently these are different issues indeed. It just struck me how much your 
textual 
descriptions would resemble me trying to describe the crappy mbp built-in 
audio. I 
guess I'll fiddle around with the two USB audio cards I have and see if I can 
hit the 
problems you've been talking about (I've used them before without problems, 
though).

Original comment by perconta...@gmail.com on 21 Oct 2009 at 6:00

GoogleCodeExporter commented 8 years ago 
I Have the exact same issue with a native instruments audio kontrol 1. After a 
few
(less buffer) or more minutes (more buffer) the audio either stops completely
(happens with vlc video) or is completely jammed (using itunes/front row). 
Would it
be possible as a workaround to inlclude in a new version of SF an option with a 
much
bigger buffer ?

Original comment by psteixe...@gmail.com on 22 Oct 2009 at 9:35

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Disagree with comment 26 - not a true representation of the scope of the issue.

Original comment by shoarth...@gmail.com on 22 Oct 2009 at 4:07

GoogleCodeExporter commented 8 years ago 
Sorry, @shoarthing, it's just a guess.

Original comment by felip...@gmail.com on 22 Oct 2009 at 4:19

GoogleCodeExporter commented 8 years ago 
This problem also occurs on a hackintosh (OS X Leopard, a Gigabyte GA-P35-DS4
motherboard which has Realtek ALC889A integrated audio).

I used Soundflower to enable audio volume control when using optical output. 
But I
stopped using it because of this bug. Hopefully this will get fixed soon and I 
can
use those volume buttons on my keyboard again :)

Original comment by tou...@gmail.com on 23 Oct 2009 at 1:49

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Unfortunately, I gave up on waiting. 

When i reinstalled Leopard on a different partition the same issue appeared, 
which then indicated mine was 
hardware. 

So, following a board replacement, I have actually found a work around with 
Ableton, record the audio in there 
and then render to Wav, you don't need SF then.... Da Dah!

Original comment by randomge...@btinternet.com on 29 Nov 2009 at 10:09

GoogleCodeExporter commented 8 years ago 
Any position about this bug? Thanks.

Original comment by felip...@gmail.com on 13 Dec 2009 at 10:06

GoogleCodeExporter commented 8 years ago 
Please fix this fast! These Problem makes Soundflower absolutely not usable at 
all for now.

Original comment by christop...@gmail.com on 19 Dec 2009 at 1:58

GoogleCodeExporter commented 8 years ago 
yes, fix it! I reported this over 6 months ago and a LOT of people can't use 
this.
This is even more serious bc Soundflower remains the only option for certain
situations. PLEASE, fix this ASAP. Thank you!

Original comment by kuderm...@alphanull.de on 19 Dec 2009 at 12:20

GoogleCodeExporter commented 8 years ago 
exact same issue here.  selecting 2048 buffer size gives about an hour before 
it gets
"jammed", and clicking any current menu setting SF seems to 'reset the clock' 
as it
were on the countdown before it jams up again.  i use (or would like to use) SF 
for
streaming audio from my computer and would like to leave it to do its thing
automatically without coming back every hour to click on the SF menu to reset 
the
"jam countdown" (what i would guess, as others have guessed, is a buffer 
underrun issue).

until it's fixed i'll try to come up with an applescript that essentially does 
that
menu click, or equivelant, for me, every hour.

crossing fingers that this gets fixed soon, cos it's a great and quite necessary
app/function!

would be glad to do testing.

10.5.7
3 gigs ram
onboard audio

Original comment by dreamkno...@gmail.com on 29 Dec 2009 at 8:08

GoogleCodeExporter commented 8 years ago 
I guess there is no one looking at this bug (or this messages anyway...)

Original comment by psteixe...@gmail.com on 29 Dec 2009 at 2:47

GoogleCodeExporter commented 8 years ago 
we are working with final cut studio and are facing the same problem. 
soundflowerbed
seems the only option to us....since months we are working with this horrible 
bug,
it's no longer possible for us...

is there any solution upcoming?

Original comment by sonkeelb...@gmail.com on 2 Jan 2010 at 12:15

GoogleCodeExporter commented 8 years ago 
  I don't know why this has started happening! I was using Soundflower  to route all apps out of my M-Audio 
Projectmix's digital output so I can use the much better D/A conversion on my  
MOTU Traveller. 

It was working great for many months, but when I upgraded both Ableton LIve and 
MAX/MSP, I started getting 
these weird buffer artifacts, which I wrongly thought for a while were related 
to those programs updates, but 
now I get them eventually on any audio source when using Soundflower.  

This clearly didn't happen before, but now it does.  I am confused.

Original comment by lukaspea...@gmail.com on 6 Jan 2010 at 2:25

GoogleCodeExporter commented 8 years ago 
Just wanted to add that I have noticed the same problem, confirm the same 
workarounds
as effective to solve it too.
Platform is Snow Leopard 10.6 along with Soundflower 1.5.1, runnning in 32-bit 
kernel
mode.
Soundcard is onboard (Maximus Formula) with a Analog Devices chip AD1988B 
running an
unsupported kext.
I know this may not the best controlled environment you get but there it is.
I may just test 64-bit to check if there's any influence.
I'll report later.

Original comment by gamma.st...@gmail.com on 26 Jan 2010 at 2:59

GoogleCodeExporter commented 8 years ago 
Thank you, @gamma.stardust. Please, do you have any idea of when a new version 
(or beta) will be released 
solving this?

Original comment by felip...@gmail.com on 27 Jan 2010 at 5:26

GoogleCodeExporter commented 8 years ago 
@filipead, nopes... have no idea, I am just a newcomer around.

I am testing 64-bit right now... I'll report soon.

Original comment by gamma.st...@gmail.com on 29 Jan 2010 at 3:02

GoogleCodeExporter commented 8 years ago 
Test done, 64-bit suffers the same issue.
This was made with a buffer of 512.
With Soundflower 16ch output of a 5.1 ac3 track played on VLC 1.0.3 (32bit)

Original comment by gamma.st...@gmail.com on 29 Jan 2010 at 4:23

GoogleCodeExporter commented 8 years ago 
Following up with a minor report.

Same stuff happens with Quicktime Pro X.

Original comment by gamma.st...@gmail.com on 29 Jan 2010 at 6:59

GoogleCodeExporter commented 8 years ago 
Same problem here, using an iMac 2007 intel aluminum 24 inch with Snow Leopard 
10.6.2
and a MOTU 896. I have all sound output routed to soundflower 2ch and 
soundflowerbed
2ch routed to my Motu 896 to control volume via software. Works great for maybe 
half
an hour and then the sound starts to sound robotic and then locks up looping on 
a
sample. Changing output drivers fixed it for me.

Original comment by jordan.b...@gmail.com on 16 Feb 2010 at 11:33

GoogleCodeExporter commented 8 years ago 
Same prolem with a M-Audio Fast Track Ultra (FTU) on a 2.66 GHz Quad with 
10.5.8. ...

Original comment by mannetti...@googlemail.com on 25 Feb 2010 at 4:40

GoogleCodeExporter commented 8 years ago 
same on dual quad 2.8 intel mac pro, imac alu and mac book pro.
all running 10.6.2 and the problem is there when audio is routed from inside 
the computer to an external soundcard. happens with a 
MOTU 828mk3 firewire audio, MOTU ultralite mk2 (both MOTU drivers) 
and EDIROL fa66 (coreaudio drivers).
sound is ok for some 40-50 seconds and then KCHCHCHCHCHCHCHCH. noise.
switching the outputs (resetting the clocks?) makes things right again�
�for a moment.
it happens on 32 and 64 bit startup modes.

the first time this happened was with right after installing 
10.5. with 10.4 it worked fine. I was hoping for it to go away wit
h 10.6 but no, something is still screwed up and looking over 
the code, no obvious fix is seen.

I really wish this could work again someday in a not to far future.

Original comment by j...@kunstonline.info on 27 Feb 2010 at 1:21

GoogleCodeExporter commented 8 years ago 
It appears that Soundflower is an abandoned project... This bug is confirmed by 
several people, but no developer 
is trying to fix it. Too bad, it's a great tool. I would even pay for it to 
work properly.

Original comment by felip...@gmail.com on 27 Feb 2010 at 3:28

GoogleCodeExporter commented 8 years ago 
Issue 44 has been merged into this issue.

Original comment by 74obje...@gmail.com on 8 Mar 2010 at 5:40

GoogleCodeExporter commented 8 years ago 
Think Issue 43 is also describing the same problem. So, can we hope for a fix 
soon?
Seems that this is issue #1 for many many people. I hope you will have the 
ressources
to do this. And, as others I would even pay for a fix! Thank you.

Original comment by kuderm...@alphanull.de on 9 Mar 2010 at 3:50

GoogleCodeExporter commented 8 years ago 
Issue 43 has been merged into this issue.

Original comment by 74obje...@gmail.com on 9 Mar 2010 at 4:52