noise reduction sampling crashes audacity 1.3.5

[flyfischerjim]

OK. I stored a file called 15 sec snoring file.wav at http://4junglejim.zoomshare.com
Hope you can access it OK

username: 4junglejim
password: jelinek

[steve]

Sorry, I can't find it.
Try one of these sites: http://www.google.co.uk/search?q=%22fre ... hosting%22

[flyfischerjim]

Koz:
files are on http://4junglejim.zoomshare.com

username: 4junglejim
Password: jelinek
Jim

[kozikowski]

http://www.kozco.com/audacity/15_sec_sn ... rected.wav

I didn't spend a lot of time on it and I only corrected the middle third, not the two ends.

That was Audacity 1.3.5, but it was on an Intel Mac OS-X 10.4.11.

I was able to achieve corrections in both 1.2.5 and 1.3.5 with no odd machine behavior. I will say, though that it is the first time I ever saw a mono file sampled at 6KHz. That rate is not directly supported in Audacity.

Koz

[flyfischerjim]

Koz:
What were the settings on the three varriables that the routines use in sampling the noise?

J

[kozikowski]

Noise Reduction numbers between 15dB and 25dB. I think that one was 25.
Frequency Smoothing numbers between 20 and 760. I think that one was 200.
Attack/Decay always zero.

Gale Andrews has some notes on this:

http://audacityteam.org/forum/viewtopic.php?f=17&t=5672

Koz

[jan.kolar]

I confirm geting crash (several times, something like 1 in 5 or 10.).
Unfortunately I can not 'reproduce' the crash. Is not there something "random" involved?
Next step (to find the bug) would be either find reproducible(?) steps or find the bug in sources,
whatever is easier. Or have the luck to catch it under debuger. (I dont have my 'devel' hdd right now.)

<<It seems to be dependent on the spectral profile and the sensitivity parameters>>
I don't think so. (If yes, can you tell us what selection etc. to make it crash? (Please specify sample-precisely or use "Snap To".))

BTW, Since I did use it only several times, is there anybody here who used Noise Removal hundered times and is sure he got no crash? Thank you for telling me!

It is also worth to check on whatever was done on noise removal since 1.3.5. Does anybody remember any fixes?


In case you can not do your job with noise removal, I suggest
1. to try ten times. Make your OS happy and do not run other applications simultaneously.
Pay attentions to popular Forum myths like defragmenting disk, having 10% free etc.
2. Play a bit around (I was changing Preferences>AudioIO: 16 versus 32float, quiting Audacity afterwards, I changed the track Rate and the Project Rate to 44100 and back; I did "Get Noise Profile" from generated Sin (30 seconds of it)". Might be handy to make before it a complete copy of directory c:Documents and Settings<USERNAME>Application DataAudacity (this is in XP, other systems likewise), if the bug decides to hide.


Crash report 1.
file 8-13-2008_2_clear-apnea.wav; snap to seconds, selection 100s-109s.
Settings: 44100Hz (before import, after import the project and the track was 6kHz), 32float, fast no-copy import, imported by Ctrl-Shift-I. OD finished (diagonal bars disappeard with 1/4 of second).
Detail: I changed 16bit to 32float in preference, I believe before the import.
Noise-removal: Default setting (24dB, 150Hz, 0.15 sec).
[[With recent dev. version "Audacity 1.3.6a5 Development Team" from gaclrecords, however the only related crash with such a fresh version -- need to see some more to avoid a mistake.]]

Result: Get Noise Profile crashed.
Non-repeatable

It also crashed
in version 1.3.6a3
using different steps (I normalized the track to -6dB, e.g.).

Other crash.
the other file 15_sec_snoring_file.wav
snap to seconds, 10s to 14s
1.3.5.
#0 0x004f43e4 in
#1 0x012b0178 in ?? ()
#2 0x013abc48 in ?? ()
#3 0x0012f820 in ?? ()
#4 0x00000000 in ?? ()
AppName: audacity.exe AppVer: 1.3.5.0 ModName: audacity.exe
ModVer: 1.3.5.0 Offset: 000f43e4
C:DOCUME~1UFALLOCALS~1Temp74f2_appcompat.txt
Non-repeatable.

Another crash:
1.3.5, Snap to, 9-14s, small file etc.
Program received signal SIGSEGV, Segmentation fault.
0x004f43e4
This happend several times, under gdb. The speed of machine might be a factor.

Code: Select all

#0  0x004f43e4 in
#1  0xbaadf00d in ?? ()
#2  0x013535f8 in ?? ()
#3  0x0012f820 in ?? ()
#4  0x00000000 in ?? ()
(gdb) disas 0x004f43c4 0x004f43f4
Dump of assembler code from 0x4f43c4 to 0x4f43f4:
0x004f43c4 <audacity!ExecCommand+698532>:       sub    %eax,%edx
0x004f43c6 <audacity!ExecCommand+698534>:       push   %esi
0x004f43c7 <audacity!ExecCommand+698535>:       mov    %edx,0x18(%esp)
0x004f43cb <audacity!ExecCommand+698539>:       jmp    0x4f43d8 <audacity!ExecCommand+698552>
0x004f43cd <audacity!ExecCommand+698541>:       lea    0x0(%ecx),%ecx
0x004f43d0 <audacity!ExecCommand+698544>:       mov    0x10(%esp),%ecx
0x004f43d4 <audacity!ExecCommand+698548>:       mov    0x18(%esp),%edx
0x004f43d8 <audacity!ExecCommand+698552>:       cmp    $0x4,%edx
0x004f43db <audacity!ExecCommand+698555>:       mov    0xc0(%ebp),%eax
0x004f43e1 <audacity!ExecCommand+698561>:       mov    (%eax,%ebx,4),%esi
0x004f43e4 <audacity!ExecCommand+698564>:       flds   (%edi,%esi,1)                       ========================
0x004f43e7 <audacity!ExecCommand+698567>:       lea    0x1(%ebx),%esi
0x004f43ea <audacity!ExecCommand+698570>:       fstps  0x24(%esp)
0x004f43ee <audacity!ExecCommand+698574>:       jl     0x4f4485 <audacity!ExecCommand+698725>
(gdb) p $edi
$1 = 0
(gdb)  p /x $esi
$3 = 0xabababab            ?????
(gdb) p /x $eax
$6 = 0x1e27c38
(gdb) p /x $ebx
$7 = 0x1
(gdb) x $eax+4*$ebx
0x1e27c3c:      0xabababab
(gdb) disas  0xbaadf00d 0xbaadf00e
0xbaadf00d:     Cannot access memory at address 0xbaadf00d
hmmmm

-========================================================

<<crash removal>>
This was a nice typo of myself during writing this post :-)

[jan.kolar]

I sampled about 3 seconds of almost white noise and the program crashes. anyone have this problem?

I think so: http://www.audacityteam.org/forum/viewt ... =17&t=5672

[jedi]

Open Audacity
Open .WAV file
Cut out very load sounds by highlight and del-key
Save - keep all audio data.

Normalise to 1.0dB

Everything was normal
However I am talking after the fact and I believe this:

Importing an stereo file and disply only 1/2 of one wave form (to save display space)
and doing what I have done will display 2 copies of Audacity. Close one copy (Oh I might have double clicked the program crashes at that point. Reloadiing the data was too scary because I am a first time user of audio engineering s/w.
The workflow that I had when I had the trouble was:

Open Audacity
Open a 876Mb .wav file of a speech
Cut out very load sounds by highlighting the sound and del-key
Normalise to 1.0dB

I am running a 2Gh dual core with 2 Gig RAM Vista on a Toshiba Laptop.A100 or is it an A200 G01

[jan.kolar]

Nothing to do with noise reduction -- It would constitute separatate topic.

Might be this is the core message ?

<< (Oh I might have double clicked the program [[when starting it]]>>
<< Close one copy >>
<< crashes at that point. >>

There were some known problems when Audacity started simultaneously twice.
(Was it only about false-iconified state or were crashes known, too?)
(Was that fixed in 1.3.6 development?)


Jedi,
avoid multiple clicks.
If any more problems, tell us also the version of Audacity.