Ethno startup problem!

Moderator: James Steele

Post Reply
michi1260
Posts: 2
Joined: Sun Sep 17, 2006 6:24 am
Primary DAW OS: Unspecified

Ethno startup problem!

Post by michi1260 »

Hi!


I have a problem. My MOTU Ethno Instrument doesn't start. After the first installation all went well, the program worked fine but startup took some time (about 15 sec.).
But after installing the new Samplitude version 9 (which has a codemeter dongle by wibu), it didn't work. When starting the standalone version an error message occurs saying: "unexpected problem detected in the program "motu ethno instrument.exe". See the report file for more info." You can see the content of the text-file belowl. When I try to start the ethno-instrument as vsti in samplitude I get a pop-up window which is black. After a windows install and formatting of my hard drives (which I had to do anyway) the problem stayed the same. All drivers are updated, too, including the ilok drivers.

I hope somebody here can help me! I already contacted the consumer service, but it is very slow and they only told me to update my drivers...

Greetings,
Michael

My system:

Intel Celeron 2.8 GHz
Soundcard: Emu 1820m
Mainboard: msi ms-7012 (medion)
Ati Radeon 9800 xxl
2x 120 GB 8 MB Cache HDD
1 GB DDR333 RAM
Windows XP home sp2
Host-App.: Samplitude 9.0

Error log (crashreport.txt):
Unhandled exception 0xC0000005 (ACCESS_VIOLATION) caught at address 0x69243D0D in the thread 3904.
-> Registers:
EAX = 0x1466FEC8, EBX = 0x09DCB784, ECX = 0x00000D3A, EDX = 0x00000001,
ESI = 0x14670000, EDI = 0x00008CE0, EBP = 0x00000400, ESP = 0x0012F944,
EFlags = 0x00010206, CS = 0x001B, SS = 0x0023, DS = 0x0023, ES = 0x23, FS = 0x003B, GS = 0x0000
-> Last error: 0x000000B7
-> Call stack (thread 3904):
?(?) : 0x69243D0D(,...)
-> Call stack (thread 3940):
ntdll(?) : KiFastSystemCallRet(0x000001A4,0xFFFFFFFF,0x00000000,0x07A7FFEC,0x01AF5C05)
kernel32(?) : WaitForSingleObject(0x000001A4,0xFFFFFFFF,0x01A6043A,0xFFFFFFFF,0x0012F788)
Ethno(?) : iZOmega::GetDefaultSampleProperties(void)
-> Call stack (thread 3952):
ntdll(?) : KiFastSystemCallRet(0x00000001,0x00000000,0x031830A0,0x01B1F2CB,0x00000001)
kernel32(?) : Sleep(0x00000001,0x01A3A470,0x00000001,0x01390608,0x031830A0)
Ethno(?) : iZOmega::GetDefaultSampleProperties(void)
-> Computer configuration:
OS type: WIN32 NT
OS version: major 5, minor 1, build 2600
Number of processors: 1
Processor type: GenuineIntel, stepping 3, model 3, instruction family 15
Processor name: Intel(R) Celeron(R) CPU 2.80GHz
Processor features: FPU, MMX, SSE, SSE2, CLFLUSH, RDTSC, CMPXCHG8B, CMOV
More processor features: VME, DE, PSE, MSR, PAE, MCE, APIC, SEP, MTRR, PGE, MCA, PAT, PSE36, FXSR, DS, SS, TM
scantlinj
Posts: 8
Joined: Wed Oct 25, 2006 11:02 am
Primary DAW OS: Unspecified

See above post

Post by scantlinj »

ATI Graphics Card & Ethno /Symphonic Instrument Incompatible
meeloo
Posts: 83
Joined: Sun Aug 21, 2005 10:01 pm
Primary DAW OS: Unspecified

Re: See above post

Post by meeloo »

scantlinj wrote:ATI Graphics Card & Ethno /Symphonic Instrument Incompatible
Not at all. Whe do you see ATI or OpenGL mentionned in the above crashlog?
I heard that a new version of Ethno might fix this problem soon.
scantlinj
Posts: 8
Joined: Wed Oct 25, 2006 11:02 am
Primary DAW OS: Unspecified

Try it!

Post by scantlinj »

Turn hardware acceleration all the way off on the Troubleshooting tab of the properties in your graphics driver and see if the error goes away. It did for me. Believe me, I'd rather be using hardware accelration, but I've now seen this problem reported in the forums by three different people using the 9600, 9800, and X800 ATI graphics cards.
michi1260
Posts: 2
Joined: Sun Sep 17, 2006 6:24 am
Primary DAW OS: Unspecified

Post by michi1260 »

Hi!

I solved the problem by disabling the hardware acceleration. Found out a while ago...
What is strange is that Ethno first worked and stopped working after I installed several progs (all the time having the same graphics driver). So it seems that there is another factor together with the graphics card resonsible for this problem.

BTW the customer support was in no way helpful...

Greetings,
Michael
Post Reply