View other reviews for this product:
Remco Z « Ouch! »
Published on 11/10/13 at 02:18Price, 4 ins & outs 4
UTILIZATION
Drivers? * ... * Cough ...
OVERALL OPINION
Interesting and attractive on paper, until I connect:
Random detection on Windows XP SP3, it is recognized only after 4 attempts ... Finally!
I run my DAW / VSTi, the interface is in the list, but no signal is transmitted twelve o'clock.
Lights out, cold re-boot ... re-launch DAW / VSTi, phew! noon signal passes.
I start to play, and Arghh! Latency south of about 50 ms. . Simply unplayable live.
I checked my other 2 interfaces noon, that they, in the same session, give me a midi timing / latency instant ... What normal!
Re-check the Prodipe 4I4O, again the latency of 50 ms.
And this is the biggest concern of "Class Compliant" c ie using a generic driver for Windows / MacOS.
It reminds me of the mini keyboard Behringer UMA25S, which has a similar latency (in Class Compliant mode) to 4I4O.
But now, Behringer offers a specific driver that addresses this concern (like an ASIO driver, but for some midday).
Since the install of the driver, the afternoon of UMA25S timing is impeccable.
Back to 4I4O prodipe:
Some Google searches lead me to moults user forums with the same latency problem (+ bcp other worries ...), some posts dating 3-4 years!
You should know that despite that, Prodipe still offers no specific driver for this interface.
I have two kits ST8 Prodipe Drum Microphones that quality / price ratio, give me satisfaction.
However, I find that Prodipe ASHAMED to allow to continue to sell this 4I4O. It is just acceptable to play midi files, but unusable serious computer music.
Whether they derive from their catalog ... or when they hire an engineer / developer worthy of the name to write a driver solving all these problems (circa 3-4 years I remember ^ ^).
In short, the current state of things, a product to avoid like the plague, because loss of energy & time for nothing.
I sent the package and make me pay.
UTILIZATION
Drivers? * ... * Cough ...
OVERALL OPINION
Interesting and attractive on paper, until I connect:
Random detection on Windows XP SP3, it is recognized only after 4 attempts ... Finally!
I run my DAW / VSTi, the interface is in the list, but no signal is transmitted twelve o'clock.
Lights out, cold re-boot ... re-launch DAW / VSTi, phew! noon signal passes.
I start to play, and Arghh! Latency south of about 50 ms. . Simply unplayable live.
I checked my other 2 interfaces noon, that they, in the same session, give me a midi timing / latency instant ... What normal!
Re-check the Prodipe 4I4O, again the latency of 50 ms.
And this is the biggest concern of "Class Compliant" c ie using a generic driver for Windows / MacOS.
It reminds me of the mini keyboard Behringer UMA25S, which has a similar latency (in Class Compliant mode) to 4I4O.
But now, Behringer offers a specific driver that addresses this concern (like an ASIO driver, but for some midday).
Since the install of the driver, the afternoon of UMA25S timing is impeccable.
Back to 4I4O prodipe:
Some Google searches lead me to moults user forums with the same latency problem (+ bcp other worries ...), some posts dating 3-4 years!
You should know that despite that, Prodipe still offers no specific driver for this interface.
I have two kits ST8 Prodipe Drum Microphones that quality / price ratio, give me satisfaction.
However, I find that Prodipe ASHAMED to allow to continue to sell this 4I4O. It is just acceptable to play midi files, but unusable serious computer music.
Whether they derive from their catalog ... or when they hire an engineer / developer worthy of the name to write a driver solving all these problems (circa 3-4 years I remember ^ ^).
In short, the current state of things, a product to avoid like the plague, because loss of energy & time for nothing.
I sent the package and make me pay.