I laugh at myself for being suspicions of CPU instructions, we exchange
 a couple of mails with Jean- Yves and now its solved. 

There where a couple of missing .dlls.

I'm glad it is solved, pdvst is great.



Mensaje telepatico asistido por maquinas.


From: lucarda27@hotmail.com
To: jyg@gumo.fr; pd-list@lists.iem.at
Subject: pdvst~ (some issues)
Date: Tue, 10 May 2016 22:09:02 +0000

Hi Jean-Yves,

When pdvst~ 0.0.3 was released I had no problems running it on computer a), lately I couldn't make it work on computers b) and c):

a) i5 
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, EM64T, VT-x, AES

b) Core 2 Duo 
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, EM64T, VT-x

c) Atom 
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, EM64T

I suspect it is related to the SSE4.x instruction.

All test were done inside Live 7.0.3, case b) and c) with fresh or first time installations of Os (win 8.1) and rest of software.

Case c) was started with onboard soundcard using DX driver in Live, when loading vst for the first time didn`t get normal “pd has stopped...” (this only happens the very first time you do it, then never again until next installation) and none of both pd windows appear, then the Live`s cpu meters shows something like 6879%, and gives you time to delete the vst from the chain, but if used with a good soundcard with ASIO drivers it simply crashes the Os (blue screen and restart).

Of course the work around for these machines is to use the original pdvst version, but 0.0.3 is better.

I`m doing something wrong?

May be others are having the same problem on not so bad machines.

I don't know how to compile but probably that's a solution.

Please let me know if there's a chance to make it work on those machines.


Salutti
Lucarda




Mensaje telepatico asistido por maquinas.