Subject:Serious Crash in 4.0c
Posted by: tmasten
Date:5/29/2003 7:07:35 PM
I keep crashing everytime I try to render a 5.1 project as 6 mono WAV files. This did not crash me in 4.0b. Nothing in my setup has changed at all. My project is very simple. 12 audio files only, no VSTis, or MIDI. It renders fine as a stereo file, but crashes consistently trying to render 16bit 48Khz mono WAV files. Please help. Is there anyway I can get 4.0b back as I need to complete this project. Any help would be greatly appreciated. Following is the crash text: Sonic Foundry ACID Pro 4.0 Version 4.0c (Build 390) Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x108C6C1 In Module 'acid40k.dll' at Address 0x1000000 + 0x8C6C1 Thread: ProgMan ID=0xD2C Stack=0x15EF000-0x15F0000 Registers: EAX=00000000 CS=001b EIP=0108c6c1 EFLGS=00010246 EBX=00000000 SS=0023 ESP=015ef6e8 EBP=00000000 ECX=00002000 DS=0023 ESI=00223270 FS=0038 EDX=00008000 ES=0023 EDI=00000000 GS=0000 Bytes at CS:EIP: 0108C6C1: F3 AB 8B CA 83 E1 03 F3 ........ 0108C6C9: AA 5F 8B C3 5B C2 0C 00 ._..[... Stack Dump: 015EF6E8: 001A0AAB 00140000 + 60AAB 015EF6EC: 00000000 015EF6F0: 0119E8F1 01000000 + 19E8F1 (acid40k.dll) 015EF6F4: 01EA2784 01E30000 + 72784 015EF6F8: 00000000 015EF6FC: 00002000 015EF700: 015EF800 014F0000 + FF800 015EF704: 00223270 00140000 + E3270 015EF708: 002232BC 00140000 + E32BC 015EF70C: 00000006 015EF710: 00000000 015EF714: 0000BB80 015EF718: 085DFBC0 082B0000 + 32FBC0 015EF71C: 00000000 015EF720: 00140000 00140000 + 0 015EF724: 015EF700 014F0000 + FF700 > 015EF730: 77F5F485 77F50000 + F485 (ntdll.dll) > 015EF73C: 77F5F485 77F50000 + F485 (ntdll.dll) > 015EF740: 0119F126 01000000 + 19F126 (acid40k.dll) 015EF744: 00000000 015EF748: 00000000 015EF74C: 085DFBC8 082B0000 + 32FBC8 015EF750: 00002000 > 015EF760: 011E81D8 01000000 + 1E81D8 (acid40k.dll) 015EF764: 00000000 015EF768: 00000000 015EF76C: 00000000 015EF770: 085DFBC8 082B0000 + 32FBC8 > 015EF780: 5F39670B 5F380000 + 1670B (wavplug.dll) > 015EF87C: 0057E400 00400000 + 17E400 (acid40.exe) 015EF880: 00000000 > 015EF884: 5F386236 5F380000 + 6236 (wavplug.dll) 015EF888: 00180E30 00140000 + 40E30 015EF88C: 015EF8D8 014F0000 + FF8D8 > 015EF8B8: 5F3865EF 5F380000 + 65EF (wavplug.dll) > 015EF910: 74726145 74720000 + 6145 (MSCTF.dll) > 015EF928: 7473206D 74720000 + 1206D (MSCTF.dll) > 015EF930: 74726145 74720000 + 6145 (MSCTF.dll) > 015EF940: 00766177 00400000 + 366177 (acid40.exe) 015EF944: 015EF960 014F0000 + FF960 > 015EF948: 77F51D1C 77F50000 + 1D1C (ntdll.dll) 015EF94C: 00000003 015EF950: 01EA2F48 01E30000 + 72F48 > 015EF964: 77F51DC9 77F50000 + 1DC9 (ntdll.dll) > 015EF974: 77F5166A 77F50000 + 166A (ntdll.dll) > 015EF978: 77ED70E0 77E60000 + 770E0 (kernel32.dll) > 015EF998: 01044A30 01000000 + 44A30 (acid40k.dll) - - - 015EFFF0: 00000000 015EFFF4: 0040F4D0 00400000 + F4D0 (acid40.exe) 015EFFF8: 0063ADF8 00400000 + 23ADF8 (acid40.exe) 015EFFFC: 00000000 |
Subject:RE: Serious Crash in 4.0c
Reply by: SonyNateM
Date:5/30/2003 10:48:23 AM
tmasten, We have been able to reproduce your problem in house and are sorting out where the problem is occuring. I tried to email you with a link to download 4.0b, but the email address you have used to register in our forums is invalid. Please either update your account with a new, correct address, or send an email to our technical support team (support@sonicfoundry.com) requesting a link to download 4.0b. Thanks! Nate |
Subject:RE: Serious Crash in 4.0c
Reply by: tmasten
Date:5/30/2003 11:59:00 AM
I updated my account. Thanks Nate |
Subject:RE: Serious Crash in 4.0c
Reply by: SonicJG
Date:5/31/2003 8:24:34 PM
Fixed for a very quick 4.0d bump, which has been posted. Joel |
Subject:RE: Serious Crash in 4.0c
Reply by: skater
Date:6/2/2003 8:07:41 PM
Interesting. I'm also getting the same crash with 4.0 as tmasen reports Audigy 2 platinum Win2k AMD 2100 ATI Radeon 8500 Unfortunately any of the patches beyond 4.0 leave Acid hung on it's the startup screen--with what appears to me to be a somewhat related unhandled exception on this move instruction: mov edx, dword ptr (eax Looks to me like something minor with dynamic link libraries or drivers AND in my case I'm pretty sure it's been brought on at least partially by flaky WIN2K factors. Bottom line is that MS-operating systems and the aps and devices written for them are fragile in the extreme and the more you try to do with them the more frustrating it gets. At some point you just wanna get on with the real tasks at hand..... |