Support

If you have a problem or need to report a bug please email : support@dsprobotics.com

There are 3 sections to this support area:

DOWNLOADS: access to product manuals, support files and drivers

HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects

USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here

NEW REGISTRATIONS - please contact us if you wish to register on the forum

Very simple synth with powerful sound, thanks to MV

Post any examples or modules that you want to share here

Re: Very simple synth with powerful sound, thanks to MV

Postby DSP-Robotron » Tue Aug 18, 2020 11:11 pm

My bad. I tried again and the 32bit version opened now just fine. I think when the 64bit version crashed the crash reporter was still active in the background, behind the main window and that's why was not allowing me to load the 32bit version properly. Now it loaded just fine. By the way, that crash reporter is not really reporting anything because it needs something. I think it was asking for an email program or something. In the end it didn't send any reports.
DSP-Robotron
 
Posts: 58
Joined: Tue Aug 18, 2020 3:39 am

Re: Very simple synth with powerful sound, thanks to MV

Postby Spogg » Wed Aug 19, 2020 7:40 am

DSP-Robotron wrote:... By the way, that crash reporter is not really reporting anything because it needs something. I think it was asking for an email program or something. In the end it didn't send any reports.


It doesn't send anything because the embedded email address is incorrect. I told Malc about it ages ago.
User avatar
Spogg
 
Posts: 3318
Joined: Thu Nov 20, 2014 4:24 pm
Location: Birmingham, England

Re: Very simple synth with powerful sound, thanks to MV

Postby DSP-Robotron » Wed Aug 19, 2020 8:22 am

This bug reporting email is not working either. (support@dsprobotics.com).
I sent these super buggy files to that email and they never received them.
Can you please check why is the ADSR silently overloading the CPU please ?
It's like all the voices are silently accumulating in the background until it reaches 86% CPU load or more.
Attachments
Very Buggy Synth.zip
(3.81 MiB) Downloaded 845 times
DSP-Robotron
 
Posts: 58
Joined: Tue Aug 18, 2020 3:39 am

Re: Very simple synth with powerful sound, thanks to MV

Postby Spogg » Wed Aug 19, 2020 10:45 am

The problem is the Ruby code. I’m not very good at Ruby but I can see that a midi event causes the midi to be switched to one of the midi outputs. This means each “synth” may get a note-on without the later corresponding note-off. This in turn means that poly channels stay open so the cpu accumulates as you play.

To fix this the Ruby code needs to be far more sophisticated and keep track of which notes are turned on and supply a note-off at some point for the currently playing notes. It can be done I think, but not by me I’m afraid.
User avatar
Spogg
 
Posts: 3318
Joined: Thu Nov 20, 2014 4:24 pm
Location: Birmingham, England

Re: Very simple synth with powerful sound, thanks to MV

Postby DSP-Robotron » Wed Aug 19, 2020 11:55 am

Well since you know what's causing the overload... Can't we just gate it somehow ? That seems to be the problem then because even in my other files the notes were sustaining way past the ADSR levels. Even after I reduced the Sustain/Decay/Release the sounds were still accumulating. How do we contact the developers to tell them to fix that bug ? Because the Ruby module is not supposed to add any additional triggers.

I have a similar switcher that switches between 8 samples done in SynthEdit and it's using only 1% CPU. This thing is at least 10 times slower because of those sustaining bugs.

support@dsprobotics.com is not working. They have no support email at all.
DSP-Robotron
 
Posts: 58
Joined: Tue Aug 18, 2020 3:39 am

Re: Very simple synth with powerful sound, thanks to MV

Postby DSP-Robotron » Wed Aug 19, 2020 12:06 pm

Spogg wrote:The problem is the Ruby code. I’m not very good at Ruby but I can see that a midi event causes the midi to be switched to one of the midi outputs. This means each “synth” may get a note-on without the later corresponding note-off. This in turn means that poly channels stay open so the cpu accumulates as you play.

To fix this the Ruby code needs to be far more sophisticated and keep track of which notes are turned on and supply a note-off at some point for the currently playing notes. It can be done I think, but not by me I’m afraid.



Can't we just send note off signals to everything after every 8 notes or at the end of every ARP cycle ?
That should work I think. The bug must be in the arpeggiator code then.
DSP-Robotron
 
Posts: 58
Joined: Tue Aug 18, 2020 3:39 am

Previous

Return to User Examples

Who is online

Users browsing this forum: No registered users and 31 guests