CopperLan

I have just played both tracks through the al22 and they play fine. I admire your loyalty to your licensees but don't you think it looks like the al88 is either faulty or not quite there yet?

PiersW wrote:Here is the data file from the monitored al 88

Well... it seems that the file attachment failed. I can't see any file from here

PiersW wrote:I have just played both tracks through the al22 and they play fine. I admire your loyalty to your licensees but don't you think it looks like the al88 is either faulty or not quite there yet?

Ha! This is a very interesting observation too!

Actually, I never told that the AL-88 is not the cause But I'm trying to find a logic explanation to the issue... and I can't.

The fact that you got All Note Off/All Controller off on the AL-88 output makes me thinking about a connection loss, because the AL-88 is generating such messages when it is disconnected from its sources. Since you don't get it at rest and the issue is still present when you are using a straight cable between the PC and the AL-88, I supposed that the AL-88 was not faulty...

But this new observation with a AL-22 is changing my mind. If the setup is working with an AL-22 and not working with an AL-88, it can be considered as a proof that the AL-88 is not working properly. You are right.

I'll contact Alyseum to give my feedback about the tests and ask them to contact you asap.

Cheers,

/Phil

This is the corresponding data file to the v3 and v5 on second linked pc files monitoring the al 88 output simultaneously. I noticed it didn't upload rtf so I changed it to a docx thats not allowed so I changed it to a txt document and that's not allowed so what can I send it as. I assume you didn't get the v3 and v5 files either. Please let me know

if they would still be useful that is

PiersW wrote:if they would still be useful that is

Sure they would. Please send all the files related to this issue at pca@copperlan.org so I can archive them for future debug/support.

Thanks!