Hi docB!

I'm finally starting to play with dbRackCsound, experimenting with porting a custom instrument I made for the Nebulae module. I'm getting compilation error (assuming that's what the blinking red light indicates). Is there any way to see the error messages?

Thanks,

Dave

---

http://mysterybear.net

https://mysterybear.bandcamp.com

https://www.youtube.com/c/DaveSeidel

https://soundcloud.com/mysterybear

https://mysterybear.bandcamp.com/album/involution

OK, got it working. Didn't think to actually run the code through Csound on the commandline. D'oh!

On Sun, Jan 8, 2023 at 11:04 AM Dave Seidel <dave.seidel@gmail.com> wrote:

Hi docB!

I'm finally starting to play with dbRackCsound, experimenting with porting a custom instrument I made for the Nebulae module. I'm getting compilation error (assuming that's what the blinking red light indicates). Is there any way to see the error messages?

Thanks,

Dave

---

http://mysterybear.net

https://mysterybear.bandcamp.com

https://www.youtube.com/c/DaveSeidel

https://soundcloud.com/mysterybear

https://mysterybear.bandcamp.com/album/involution

Argh! That was it, thanks! One of those insidious bugs that isn't  caught by a syntax check. This works now for IN1, but now my usage of IN2 is failing (without that bug, but probably with a different one:

  kndxa = scale2(chnget:k("P2"), giNumTables-1, 0, -10, 10)  
  kndxb = scale2(chnget:k("IN2C1"), giNumTables-1, 0, -5, 5)
  kndx = kndxa ;+ kndxb
  ftmorf kndx, giList, giMorf  
  

I threw in the qnan() check just to see what happens, but this code fails with or without that check, apparently on use of the kndxb variable.. I'm sure that there's some other horrible bug that I am just not seeing. I am sending similar LFOs to IN1 and IN2 (-5 to +5).

(BTW: the workflow I'm using now is to edit the Csound code in VSCode as an ORC file, and then execute "csound --orc --syntax-check-only <filename>"  before pasting it into the module.)

On Sun, Jan 8, 2023 at 1:25 PM docB <000005d2745f1ec0-dmarc-request@listserv.heanet.ie> wrote:

Hi

i think here is the problem

 > koffb = scale2(chnget:k("IN1C1"), 0.001, 0.1, -5, -5)

as scale2 seems to return infinity or "not a number" if the range is -5,-5

should be -5,5 i guess

On linux this does not crash Rack but there is NAN on the output.

best regards

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Attaching the entire ORC file for context.

On Sun, Jan 8, 2023 at 2:29 PM Dave Seidel <dave.seidel@gmail.com> wrote:

Argh! That was it, thanks! One of those insidious bugs that isn't  caught by a syntax check. This works now for IN1, but now my usage of IN2 is failing (without that bug, but probably with a different one:

  kndxa = scale2(chnget:k("P2"), giNumTables-1, 0, -10, 10)  
  kndxb = scale2(chnget:k("IN2C1"), giNumTables-1, 0, -5, 5)
  kndx = kndxa ;+ kndxb
  ftmorf kndx, giList, giMorf  
  

I threw in the qnan() check just to see what happens, but this code fails with or without that check, apparently on use of the kndxb variable.. I'm sure that there's some other horrible bug that I am just not seeing. I am sending similar LFOs to IN1 and IN2 (-5 to +5).

(BTW: the workflow I'm using now is to edit the Csound code in VSCode as an ORC file, and then execute "csound --orc --syntax-check-only <filename>"  before pasting it into the module.)

On Sun, Jan 8, 2023 at 1:25 PM docB <000005d2745f1ec0-dmarc-request@listserv.heanet.ie> wrote:

Hi

i think here is the problem

 > koffb = scale2(chnget:k("IN1C1"), 0.001, 0.1, -5, -5)

as scale2 seems to return infinity or "not a number" if the range is -5,-5

should be -5,5 i guess

On linux this does not crash Rack but there is NAN on the output.

best regards

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

In the logfile of Rack there is the csound error message:

Invalid ftable no. 0.000000

so i guess that frmorf gets a table index of 0.

maybe this should be checked before passing.

On 1/8/23 20:33, Dave Seidel wrote:

Attaching the entire ORC file for context.

On Sun, Jan 8, 2023 at 2:29 PM Dave Seidel <dave.seidel@gmail.com> wrote:

Argh! That was it, thanks! One of those insidious bugs that isn't  caught by a syntax check. This works now for IN1, but now my usage of IN2 is failing (without that bug, but probably with a different one:

  kndxa = scale2(chnget:k("P2"), giNumTables-1, 0, -10, 10)  
  kndxb = scale2(chnget:k("IN2C1"), giNumTables-1, 0, -5, 5)
  kndx = kndxa ;+ kndxb
  ftmorf kndx, giList, giMorf  
  

I threw in the qnan() check just to see what happens, but this code fails with or without that check, apparently on use of the kndxb variable.. I'm sure that there's some other horrible bug that I am just not seeing. I am sending similar LFOs to IN1 and IN2 (-5 to +5).

(BTW: the workflow I'm using now is to edit the Csound code in VSCode as an ORC file, and then execute "csound --orc --syntax-check-only <filename>"  before pasting it into the module.)

On Sun, Jan 8, 2023 at 1:25 PM docB <000005d2745f1ec0-dmarc-request@listserv.heanet.ie> wrote:

Hi

i think here is the problem

 > koffb = scale2(chnget:k("IN1C1"), 0.001, 0.1, -5, -5)

as scale2 seems to return infinity or "not a number" if the range is -5,-5

should be -5,5 i guess

On linux this does not crash Rack but there is NAN on the output.

best regards

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

🤔🤔 Hmmm,… double hmmm,… 

-PBS 

-----Original Message-----
From: docB <000005d2745f1ec0-dmarc-request@LISTSERV.HEANET.IE>
To: CSOUND@LISTSERV.HEANET.IE
Sent: Sun, Jan 8, 2023 9:10 pm
Subject: Re: [Csnd] question for docB re dbRackCsound

i cannot understand your compiling issue with csound, but dbRackCsound simply runs one csound instance

which does not interfere with any audio devices of the system as it uses the vcvrack audio inputs and outputs.

If the csound module is deleted in a vcv rack patch, the csound instance is stopped and destroyed.

On 1/8/23 21:53, Partev Sarkissian wrote:

Had issue with compiling error with my onboard mic a couple weeks back, which 

I never use to begin with, I leave it turned off, 'mic in 0' and never a problem. 

Checked internal setting on the laptop, still got 'mic in 0' which was never a 

problem before. Still had compiling error. 

I uninstalled dbRackCsound, check my system preference settings for audio, 

nothing changed, ran one of my Csound projects and it all came back. No 

compiling errors. 

Maybe with all the audio software on my computer, it didn't want to deal 

with another. So now I'm wondering about that. dbRack use resources that 

prioritized for itself over Csound???

-PBS

Hmmm,.... 

-----Original Message-----
From: Dave Seidel <dave.seidel@GMAIL.COM>
To: CSOUND@LISTSERV.HEANET.IE
Sent: Sun, Jan 8, 2023 4:37 pm
Subject: Re: [Csnd] question for docB re dbRackCsound

OK, got it working. Didn't think to actually run the code through Csound on the commandline. D'oh!

On Sun, Jan 8, 2023 at 11:04 AM Dave Seidel <dave.seidel@gmail.com> wrote:

Hi docB!

I'm finally starting to play with dbRackCsound, experimenting with porting a custom instrument I made for the Nebulae module. I'm getting compilation error (assuming that's what the blinking red light indicates). Is there any way to see the error messages?

Thanks,

Dave

---

http://mysterybear.net

https://mysterybear.bandcamp.com

https://www.youtube.com/c/DaveSeidel

https://soundcloud.com/mysterybear

https://mysterybear.bandcamp.com/album/involution

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

On 1/8/23 22:37, Dave Seidel wrote:

I need to take a break from this and cook dinner. However, I note that "printk" does not leave anything in the rack log for me.

ok i will check this, maybe i have to grab the csound messages and put them into the rack info log.

On Sun, Jan 8, 2023 at 4:20 PM Partev Sarkissian <0000060b2ef1338e-dmarc-request@listserv.heanet.ie> wrote:

🤔🤔 Hmmm,… double hmmm,… 

-PBS 

-----Original Message-----
From: docB <000005d2745f1ec0-dmarc-request@LISTSERV.HEANET.IE>
To: CSOUND@LISTSERV.HEANET.IE
Sent: Sun, Jan 8, 2023 9:10 pm
Subject: Re: [Csnd] question for docB re dbRackCsound

i cannot understand your compiling issue with csound, but dbRackCsound simply runs one csound instance

which does not interfere with any audio devices of the system as it uses the vcvrack audio inputs and outputs.

If the csound module is deleted in a vcv rack patch, the csound instance is stopped and destroyed.

On 1/8/23 21:53, Partev Sarkissian wrote:

Had issue with compiling error with my onboard mic a couple weeks back, which 

I never use to begin with, I leave it turned off, 'mic in 0' and never a problem. 

Checked internal setting on the laptop, still got 'mic in 0' which was never a 

problem before. Still had compiling error. 

I uninstalled dbRackCsound, check my system preference settings for audio, 

nothing changed, ran one of my Csound projects and it all came back. No 

compiling errors. 

Maybe with all the audio software on my computer, it didn't want to deal 

with another. So now I'm wondering about that. dbRack use resources that 

prioritized for itself over Csound???

-PBS

Hmmm,.... 

-----Original Message-----
From: Dave Seidel <dave.seidel@GMAIL.COM>
To: CSOUND@LISTSERV.HEANET.IE
Sent: Sun, Jan 8, 2023 4:37 pm
Subject: Re: [Csnd] question for docB re dbRackCsound

OK, got it working. Didn't think to actually run the code through Csound on the commandline. D'oh!

On Sun, Jan 8, 2023 at 11:04 AM Dave Seidel <dave.seidel@gmail.com> wrote:

Hi docB!

I'm finally starting to play with dbRackCsound, experimenting with porting a custom instrument I made for the Nebulae module. I'm getting compilation error (assuming that's what the blinking red light indicates). Is there any way to see the error messages?

Thanks,

Dave

---

http://mysterybear.net

https://mysterybear.bandcamp.com

https://www.youtube.com/c/DaveSeidel

https://soundcloud.com/mysterybear

https://mysterybear.bandcamp.com/album/involution

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

https://github.com/docb/dbRackCsound/releases/tag/v2.0.4

here you can get a version which displays the csound messages as Rack INFO messages.

(tested on Win11 VM)

On 1/8/23 23:02, Dave Seidel wrote:

I'm on Win11, if that makes a difference.

On Sun, Jan 8, 2023 at 4:47 PM docB <000005d2745f1ec0-dmarc-request@listserv.heanet.ie> wrote:

On 1/8/23 22:37, Dave Seidel wrote:

I need to take a break from this and cook dinner. However, I note that "printk" does not leave anything in the rack log for me.

ok i will check this, maybe i have to grab the csound messages and put them into the rack info log.

On Sun, Jan 8, 2023 at 4:20 PM Partev Sarkissian <0000060b2ef1338e-dmarc-request@listserv.heanet.ie> wrote:

🤔🤔 Hmmm,… double hmmm,… 

-PBS 

-----Original Message-----
From: docB <000005d2745f1ec0-dmarc-request@LISTSERV.HEANET.IE>
To: CSOUND@LISTSERV.HEANET.IE
Sent: Sun, Jan 8, 2023 9:10 pm
Subject: Re: [Csnd] question for docB re dbRackCsound

i cannot understand your compiling issue with csound, but dbRackCsound simply runs one csound instance

which does not interfere with any audio devices of the system as it uses the vcvrack audio inputs and outputs.

If the csound module is deleted in a vcv rack patch, the csound instance is stopped and destroyed.

On 1/8/23 21:53, Partev Sarkissian wrote:

Had issue with compiling error with my onboard mic a couple weeks back, which 

I never use to begin with, I leave it turned off, 'mic in 0' and never a problem. 

Checked internal setting on the laptop, still got 'mic in 0' which was never a 

problem before. Still had compiling error. 

I uninstalled dbRackCsound, check my system preference settings for audio, 

nothing changed, ran one of my Csound projects and it all came back. No 

compiling errors. 

Maybe with all the audio software on my computer, it didn't want to deal 

with another. So now I'm wondering about that. dbRack use resources that 

prioritized for itself over Csound???

-PBS

Hmmm,.... 

-----Original Message-----
From: Dave Seidel <dave.seidel@GMAIL.COM>
To: CSOUND@LISTSERV.HEANET.IE
Sent: Sun, Jan 8, 2023 4:37 pm
Subject: Re: [Csnd] question for docB re dbRackCsound

OK, got it working. Didn't think to actually run the code through Csound on the commandline. D'oh!

On Sun, Jan 8, 2023 at 11:04 AM Dave Seidel <dave.seidel@gmail.com> wrote:

Hi docB!

I'm finally starting to play with dbRackCsound, experimenting with porting a custom instrument I made for the Nebulae module. I'm getting compilation error (assuming that's what the blinking red light indicates). Is there any way to see the error messages?

Thanks,

Dave

---

http://mysterybear.net

https://mysterybear.bandcamp.com

https://www.youtube.com/c/DaveSeidel

https://soundcloud.com/mysterybear

https://mysterybear.bandcamp.com/album/involution

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

OK, I found my fundamental problem, which was that two of my calls to scale2 had the min/max values reversed.

Now I am running into a different issue, which is a bit subtle. I am using IN1 and IN2 for LFO inputs. The LFO I'm using (which is typical) has a range of -5 to 5, so I am scaling the input based on those min/max values. If I remove the cable from INx, they return to 0. This makes sense, but my scaling converts them to non-zero values. I understand what is happening, but what I'd really like is a way to know that INx is not cabled so I can then completely disregard the value from the corresponding channel. I hope this makes sense. Basically, I need to know if each IN port is cabled or not. I can't just compare to 0.

OK, I can work around this by using unipolar LFOs instead of bipolar LFOs. But I still think we need a way to know if the control inputs are connected if we want to be able to use bipolar control inputs.

Another issue: if I have a control signal connected, and then disconnect it, the channel for that input retains the value of the last incoming signal. I think input channels should reset to 0 when disconnected.

ok this an easy one.

but the other issue is more difficult. i think would have to provide an additional built in opcode which delivers the connection status of an input.

On Mon, Jan 9, 2023 at 10:41 AM Dave Seidel <dave.seidel@gmail.com> wrote:

OK, I found my fundamental problem, which was that two of my calls to scale2 had the min/max values reversed.

Now I am running into a different issue, which is a bit subtle. I am using IN1 and IN2 for LFO inputs. The LFO I'm using (which is typical) has a range of -5 to 5, so I am scaling the input based on those min/max values. If I remove the cable from INx, they return to 0. This makes sense, but my scaling converts them to non-zero values. I understand what is happening, but what I'd really like is a way to know that INx is not cabled so I can then completely disregard the value from the corresponding channel. I hope this makes sense. Basically, I need to know if each IN port is cabled or not. I can't just compare to 0.

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

I just put up a draft PR to reset the control channels when they disconnect, it's probably going in the wrong direction: https://github.com/docb/dbRackCsound/pull/10

On Mon, Jan 9, 2023 at 1:20 PM docB <000005d2745f1ec0-dmarc-request@listserv.heanet.ie> wrote:

OK, I can work around this by using unipolar LFOs instead of bipolar LFOs. But I still think we need a way to know if the control inputs are connected if we want to be able to use bipolar control inputs.

Another issue: if I have a control signal connected, and then disconnect it, the channel for that input retains the value of the last incoming signal. I think input channels should reset to 0 when disconnected.

ok this an easy one.

but the other issue is more difficult. i think would have to provide an additional built in opcode which delivers the connection status of an input.

On Mon, Jan 9, 2023 at 10:41 AM Dave Seidel <dave.seidel@gmail.com> wrote:

OK, I found my fundamental problem, which was that two of my calls to scale2 had the min/max values reversed.

Now I am running into a different issue, which is a bit subtle. I am using IN1 and IN2 for LFO inputs. The LFO I'm using (which is typical) has a range of -5 to 5, so I am scaling the input based on those min/max values. If I remove the cable from INx, they return to 0. This makes sense, but my scaling converts them to non-zero values. I understand what is happening, but what I'd really like is a way to know that INx is not cabled so I can then completely disregard the value from the corresponding channel. I hope this makes sense. Basically, I need to know if each IN port is cabled or not. I can't just compare to 0.

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here