ΣSigmaStudio Ask AI Русский Log in

Bug report FIR filter table

SigmaDSP & SigmaStudio seeker Jan 24, 2016 00:00 6 replies Original on forum ↗
Subscribe
seeker Question
Jan 24, 2016 00:00

Hi,

When using big FIR tables I often find the SigmaStudio runs out of memory and stops working. I've raised this issue already in another discussion with pa_py but it's not solved yet so I try to raise a bug report instead.

When closing the FIR table editor window I get error messages after several minutes, two examples attached. A few times I've managed to load the table but it took about 6 minutes. I also attach a FIR table example for info.

I'm using SigmaStudio 3.12.3 on a Win7 PC with 4GB memory.

Regards,

Mats

3.12.3

software bug

table

fir

crashes

seeker Reply
Feb 1, 2016 00:00

Hi,

I started this thread to raise a bug report that is critical to my project. After one week I can see that 28 people has read it but noone has answered.

It there a better or correct way to raise bug reports on SigmaStudio than to start a new discussion?

Regards,

Mats

Wilfrido Reply
Feb 1, 2016 00:00

Hello Mats,

The bug has been reported on December 14, 2015 and our Software Team is currently working on it to fix this issue.

Thank you for raising the flag towards this bug.

Best regards,

Wilfrido Sierra.

seeker Reply
Feb 3, 2016 00:00

Hello Wilfrido,

Good to know that you are working on a solution. Please reply to this post when a solution is available.

Best Regards,

Mats

seeker Reply
Feb 16, 2016 00:00

Hello Wilfrido,

This bug was reported 2 months ago as I understand. It's very critical to me that it is resolved in order to move forward.

Is there a time plan for a fix in Sigma Studio?

Best Regards,

Mats

Wilfrido Reply
Feb 16, 2016 00:00

Hello Mats,

The bug is still under our bug pipeline. I will push it forward to get the highest priority.

It will be available on SigmaStudio 3.12.5 Beta release in the following weeks.

Best Regards,

Wilfrido.

seeker Reply
Apr 6, 2016 00:00

Hello Wilfrido,

After a quick test with the latest beta 3.13.1 it looks like the issue is fixed now

Regards,

Mats