I don't see some parameters from FAUST to Scriptnode

[Mighty23]

@Lindon I'm running some tests for a vocal harmonizer, exploring different solutions. I still don't think I'm quite there yet, but I really appreciate the help.

Like many, I rely on AI to assist me. Personally, I prefer Claude over chatGPT.
I believe that, for now, without proper 'guidance,' they tend to oversimplify the structure of what you ask for. They first need to be supplied with solid documentation and, ideally, an already working example of what you're trying to achieve

[Lindon]

@Mighty23 so you are using AI(Claude/ChatGPT) to generate Faust code for you?

[Mighty23]

@Lindon Yes, I use it as a support tool to explore different solutions in Faust, but not primarily to generate code directly. In my experience, using it to generate code from scratch can often be much more time-consuming. Instead, I focus on:

• Analyzing and better understanding the documentation
• Discussing various approaches and strategies
• Reviewing the logic of my code
• Getting suggestions for potential optimizations

[Lindon]

@Mighty23 wow it really seems to be working for you - love to see what you come up with at the end...

[DabDab]

@Lindon said in I don't see some parameters from FAUST to Scriptnode:

Claude

Which prompt you entered on claude ?

[sletz]

@Mighty23 as you see HISE ignores the Faust vgroup construct,

what do you mean here ?

[Lindon]

@sletz
In the Faust environment you can name sliders(for example) the same as long as they are in a vgroup.... in the HISE environment you cant have two sliders with the same name, no matter where they are, or how they are grouped :

Two hsliders both called "mySlider" results in only one of them showing up in the interface...

as you can see in the original post,:

pitch1 = vgroup("Voice 1", hslider("Pitch[unit:semitones]", -12, -12, 12, 1));
pitch2 = vgroup("Voice 2", hslider("Pitch[unit:semitones]", -7, -12, 12, 1));
pitch3 = vgroup("Voice 3", hslider("Pitch[unit:semitones]", -5, -12, 12, 1));

gets one just one knob called Pitch

[Lindon]

@sletz meanwhile if you are here...could you look at this:

More than one faust node = one not compiling and running properly

So I havent tried this in a compiled DLL yet, but if I have a scriptnode network with two core.faust nodes then when I load it one of them doesn't work until...

Forum (forum.hise.audio)

[sletz]

@Lindon

OK then the HISE architecture machinery could possibly use "shortname", which can be generated to uniquely name same "labels" in different groups. See: https://faustdoc.grame.fr/manual/architectures/#dsp-json-description

@Christoph-Hart would this make sense ?

[Lindon]

@sletz said in I don't see some parameters from FAUST to Scriptnode:

@Lindon

OK then the HISE architecture machinery could possibly use "shortname", which can be generated to uniquely name same "labels" in different groups. See: https://faustdoc.grame.fr/manual/architectures/#dsp-json-description

@Christoph-Hart would this make sense ?

Im not sure its that big a deal really - once you know it then you can work with it.

[sletz]

@sletz sure but then you cannot simply copy/paste Faust code and be sure it will work this can surely be improved.

[Mighty23]

@DabDab said in I don't see some parameters from FAUST to Scriptnode:

Which prompt you entered on claude ?

Provide prompts that clearly outline your goal and your level of expertise. Guide the AI to steer clear of common pitfalls by specifying the libraries and functions you intend to use upfront. Keep in mind that the most frequent AI errors are related to signal routing rather than syntax. Therefore, describe the 'sequential composition' you aim to achieve, even if it seems like a minor or obvious detail to you.
Have it tackle one step at a time, avoiding the assignment of multiple tasks simultaneously. Once your questions are clarified or you've obtained a portion of code that satisfies you, start a new chat and move on to the next (sub)task.

[DabDab]

@Mighty23 said in I don't see some parameters from FAUST to Scriptnode:

Provide prompts that clearly outline your goal and your level of expertise. Guide the AI to steer clear of common pitfalls by specifying the libraries and functions you intend to use upfront. Keep in mind that the most frequent AI errors are related to signal routing rather than syntax. Therefore, describe the 'sequential composition' you aim to achieve, even if it seems like a minor or obvious detail to you.
Have it tackle one step at a time, avoiding the assignment of multiple tasks simultaneously. Once your questions are clarified or you've obtained a portion of code that satisfies you, start a new chat and move on to the next (sub)task.

Nice. I am using FAUST for the past 5-6 years. But I am curious to implement it with AI.