Audacity Forum

Steve:

Thank you.

mdubin

@mdubin - how much installed RAM do you have and what is the computer speed?

I can't get any crashes on Win 7 x64 or Ubuntu 12.04 32-bit.

It seems one of two things could be responsible 1) the quality improvements 2) the change from memcpy to memmove.

I somewhat doubt that 2) is responsible but if mdubin wants to test, I can make a build that has the quality improvements but goes back to memcpy. Let me know. If this was the reason then we might have to use memmove only for 64-bit.

One other thing you could test now. Do any other effects also crash towards the end of processing on the file you posted? Possibly try some effects with ... after the menu name that you do not normally use.


Gale

Gale Andrews wrote:if mdubin wants to test, I can make a build that has the quality improvements but goes back to memcpy.

That would be a very useful test.
As far as I'm aware those are the only two commits (changes) to the effect between 2.0.0 and 2.0.1 so if we could narrow it down to one or the other that would be great. (especially if it turns out to be the "memcpy" change as that should be easy to fix, though I agree that it looks more likely to be the other one).

Steve and Gale:

Thanks for all your support.

The fact that is that the error in 2.0.1 appears to be intermittent. I did several successful sliding time scale/pitch shift conversions with 32 bit float before the error happened again, and this was with a much smaller WAV file. All I can say is that after this error, I went back to 2.0.0 and had no further problems.

My computer (windows xp pro sp3) has 3 gb memory, Intel Pentium 4 CPU 3.00 GHz. I have no need for most of the audacity effects. I was attracted to the sliding time scale/pitch shift because I have so many recordings where I feel the tempo is too fast for my comfort. It is so uplifting to be able to slow down the speed of music without changing the pitch. I cannot hear any noticeable difference between the original track and the processed one except for the speed.

I would be willing to help you out by testing any special build which might pinpoint where the 2.0.1 problem originates from.

mdubin

@mdubin,

Here is a build of our current 2.0.2-alpha that goes back to using memcpy for memory functions (we had changed to memmove to fix quality problem with Sliding Time Scale on 64-bit Linux):
http://gaclrecords.org.uk/bugs/audacity ... -mmove.zip

Make sure other versions of Audacity are closed, then after downloading the zip above, extract the contents to a new folder of your choice. Then double-click "Audacity-revert-mcpy-to-mmove.exe" to start Audacity. There is no need to uninstall other Audacity versions.

I suggest you test first with 16-bit quality settings and the "Part 1.WAV", as this scenario seemed more prone to issue, if you do not mind doing that.


Thanks for your help.



Gale

PGA wrote:I'm out of town until Thursday mid-morning. I'll try at 16bit when I get back.

I'm back in town again but I see your discussion and understanding of the problem has moved along significantly in the past 24-36 hours. If I recall correctly that which I have just read, you are able to test on a Win 7 system so, as that is what I was offering, I'll take a back seat on this.

Gale:

Thank you. I saved the .zip to my flash drive and I will begin testing this evening when I get home from work.

mdubin

Gale Andrews wrote:@mdubin,

Here is a build of our current 2.0.2-alpha that goes back to using memcpy for memory functions (we had changed to memmove to fix quality problem with Sliding Time Scale on 64-bit Linux):
http://gaclrecords.org.uk/bugs/audacity ... -mmove.zip

Make sure other versions of Audacity are closed, then after downloading the zip above, extract the contents to a new folder of your choice. Then double-click "Audacity-revert-mcpy-to-mmove.exe" to start Audacity. There is no need to uninstall other Audacity versions.

I suggest you test first with 16-bit quality settings and the "Part 1.WAV", as this scenario seemed more prone to issue, if you do not mind doing that.


Thanks for your help.



Gale

I got the error on Part 1.WAV the very first time I tried it with the 2.0.2 alpha using 16 bit.

mdubin

mdubin wrote:I got the error on Part 1.WAV the very first time I tried it with the 2.0.2 alpha using 16 bit.

OK, thanks. A pity, because that would have been a simple fix.


Gale

Hi,

I am the author of the code, and just heard about this.
I made substantial changes to the effect code in 2.0.1, but never got a crash.
The link to the audio file which crashed it doesn't work anymore.
Can someone repost the file, please?
Hopefully I can fix this quick and we can get it in 2.0.2.

-Clayton