Audio Weaver crashing when clicking "Run" in Designer after reducing number of I/O channels

7 posts / 0 new
Last post
olemundbjerg
Offline
Last seen: 1 week 2 days ago
Joined: 05/23/2018 - 5:20am
Audio Weaver crashing when clicking "Run" in Designer after reducing number of I/O channels

I just started experiencing AWE Server crashes when clicking "Run" in Designer - when letting VisualStudio 2017 handle the debugging I get the following (not much info as it is built without debug symbols):

Seems to be an unhandled exception in FrameDll.dll..? It had been running fine for days but after changing number of input/output channels in the layout from 14 in/14 out to 4 in/12 out, it started crashing. Going back to 14 channels I/O makes it run again. Usually this works - Audio Weaver usually just skips the I/O channels higher than the ones used in the layout..

Andrew
Offline
Last seen: 4 days 14 min ago
Joined: 04/12/2018 - 9:25am

Hello,

Are you experiencing this crash while connected to the Native target, or when connected to an external target? I am unable to reproduce the crash on the native target. 

olemundbjerg
Offline
Last seen: 1 week 2 days ago
Joined: 05/23/2018 - 5:20am

It's on a native target, using an ASIO 14-in/14-out FireWire audio interface. I'm running Win 7 - wonder if that could make a difference? Any way I can aid with more logs or similar?

Andrew
Offline
Last seen: 4 days 14 min ago
Joined: 04/12/2018 - 9:25am

Hi again,

This is most likely caused by an issue with the ASIO driver for your FireWire interface. What is the exact device that you are using, and with which driver? I would also be able to provide more insight if you could get me the .AWD that you are using, but I understand if this isn't possible. 

You could also send me your 'awelog.txt' which can be found in Bin\win32-vc100-rel 

 

 

Andrew
Offline
Last seen: 4 days 14 min ago
Joined: 04/12/2018 - 9:25am

Actually, it looks like this is a known issue with the version that you are using. Are you utilizing any of the multicore features? If not, we can get you a release that does not contain multicore support and therefore will not have this problem. If you are using multicore, we can help you find some kind of workaround. 

olemundbjerg
Offline
Last seen: 1 week 2 days ago
Joined: 05/23/2018 - 5:20am

I am using a MOTU 828 mkII with their newest win driver ver. 4.0.6.6814 from 2015-07-14. The pc is a ThinkPad W530 (8 CPU threads and 16 SMP cores available). I don't think I am using any multi-core stuff - e.g. no use of "Multicore Subsystem".. I am using the SbAECV1 and the SCNRv1 modules but they shouldn't be utilizing multiple cores, right?
If you could provide an email address, I can send the .awd? The log file is attached:

For now the workaround for me is to keep the number of I/O at 14 in / 14 out..

Andrew
Offline
Last seen: 4 days 14 min ago
Joined: 04/12/2018 - 9:25am

Hello,

I just sent you an email with a link to a build that does not contain this bug. Thanks for bringing this to our attention.

-Andrew