@d-healey @lalalandsynth

Okay I got a little upgrade here with 6 linked buttons. It does what radio-buttons do. One turned on turns the others off. Also, no button can ever be turned off, if it is trying to set itself to 0, we simply switch it on again.

onInit callback:

• const var all elements
• set array with elements var names
• sync array with states in 0s and 1s in arr_buttons_sw.

const var Button1 = Content.getComponent("Button1");
const var Button2 = Content.getComponent("Button2");
const var Button3 = Content.getComponent("Button3");
const var Button4 = Content.getComponent("Button4");
const var Button5 = Content.getComponent("Button5");
const var Button6 = Content.getComponent("Button6");
const var arr_buttons = [Button1, Button2, Button3, Button4, Button5, Button6];
const var arr_buttons_sw = [
	
	[1, 0, 0, 0, 0, 0], // for button 1 [0], we set all else to 0.
	[0, 1, 0, 0, 0, 0], 
	[0, 0, 1, 0, 0, 0], 
	[0, 0, 0, 1, 0, 0], 
	[0, 0, 0, 0, 1, 0], 
	[0, 0, 0, 0, 0, 1] 
];

Then the onControl callback:

for (var i = 0; i < arr_buttons.length; i++) { // loop through the 6.

	// for any button matching one in array list.
	if (number == arr_buttons[i]) { 

		if (value == 1) {

			var btn_nr = arr_buttons.indexOf(number);

			for (var j = 0; j < arr_buttons.length; j++) { 

				// now setting the elements all in one go to their pre-set values in the arr_buttons_sw array number presets.
				arr_buttons[j].setValue(arr_buttons_sw[btn_nr][j]);

			}

		} else {

			// we dont want the value to be able to be set to 0, cause that´s not radio-style.
			number.setValue(1); // just set it back to one.

		}
		
	}

}

Here´s the new project in all its might:

radio-buttons-control-samplermaps-v2.zip

@lalalandsynth

Hey there, I played around with it a while and found a solution. It´s not @d-healey style, like looping through everything all efficient n stuff But it gets it done.

Note: I just made the basic Samplemap loading using Sampler.loadSamplerMap(), but did not make any actual radio buttons in the design, but I gathered you got that covered from Healey´s video.

// onInit

Content.makeFrontInterface(633, 400);

// store references to the samplers.
const var Sampler1 = Synth.getSampler("Sampler1");
const var Sampler2 = Synth.getSampler("Sampler2");
const var Sampler3 = Synth.getSampler("Sampler3");

// UI references
const var ComboBox1 = Content.getComponent("ComboBox1");
const var boxVals = ComboBox1.getAllProperties(); // just get all properties of the combobox element, for later reference.

// just printing all values of the combobox´s available properties:
for (var i = 0; i < boxVals.length; i++) {
    Console.print("ComboBox1:s element id " + i + ": " + boxVals[i]);
}


// get state of combobox, on init:
const var cboxState = ComboBox1.getValue();
Console.print("Current choice made in combobox: " + cboxState);



// onControl ui-control:

function onControl(number, value) // this needs to be copied into the onControl callback.
{
	
    if (number == ComboBox1)
    {
        Console.print("ComboBox1: " + value);
        if (value == 1)
        {
            // loading Samplemap nr 1 for all three.
            Sampler1.loadSampleMap("Samplemap-1-1"); 
            Sampler2.loadSampleMap("Samplemap-1-2");
            Sampler3.loadSampleMap("Samplemap-1-3");
        }
        if (value == 2)
        {
            Sampler1.loadSampleMap("Samplemap-2-1");
            Sampler2.loadSampleMap("Samplemap-2-2");
            Sampler3.loadSampleMap("Samplemap-2-3");
        }
        if (value == 3)
        {
            Sampler1.loadSampleMap("Samplemap-3-1");
            Sampler2.loadSampleMap("Samplemap-3-2");
            Sampler3.loadSampleMap("Samplemap-3-3");
        }
    }
}

Here´s an upload of the full project from my hise testing, so you can load it directly, with a single sample in the all the sample maps.

radio-buttons-control-samplermaps.zip

Made using Scriptnode branch (2020-08 ish), if that´s important. On macos.

Ok, found the solution! I was treating all things in the modulator as data exportable by exportState(), but that one does not export or include table data, regardless of the modulator, it seems. So this one is the appending solution of for the table data of the "Global Static Time Variant Modulator", that has both buttons and table data:

Content.makeFrontInterface(633, 400);

// Prepping for export, original modulator
const var Modulator1 = Synth.getModulator("Global Static Time Variant Modulator1");
const var mod1Table = Modulator1.asTableProcessor(); // asTableProcessor, was the missing piece.

// Export the table (only one so index is 0)
const var export1 = mod1Table.exportAsBase64(0);
Console.print("export1: " + export1);

// Prepping for import, next modulator
const var Modulator3 = Synth.getModulator("modulator3");
const var mod3Table = Modulator3.asTableProcessor();

// Use the previous export1 as the data input for table index 0.
mod3Table.restoreFromBase64(0, export1); 

I´m trying to use the exportState and restoreState to export and import all settings for a modulator on a sampler´s release-time modulator setting.

(so from one to another, like presets for a modulator)

Exporting is easy as pie, eihter via the built in function that you get in the edit menu of the object when clicking on the modulator, or via scripting, like so:

Menu option:

1. click on modulator
2. choose "edit name of modulator" -> "Create Base64 encoded state"

HISE-script option:

In the onInit in the interface script I put:

Content.makeFrontInterface(633, 400);

const var Modulator1 = Synth.getModulator("Global Static Time Variant Modulator1");
const var export1 = Modulator1.exportState();

Console.print(export1); // this outputs fine, same base64 string as the menu option.

So far so good, I get the base64 code no matter which option I choose, but I cannot in any situation I´ve tried get the new modulator restored with the .restoreState of Modulator. This is my coding attempt:

Content.makeFrontInterface(633, 400);

const var Modulator1 = Synth.getModulator("Global Static Time Variant Modulator1");
const var export1 = Modulator1.exportState();

const var modulator3 = Synth.getModulator("modulator3");
modulator3.restoreState(export1);

I get nothing imported except for the state of the "UseTable" knob set to "on", that one is the same way it was saved. The state of the table is empty, default linear. None of my entered points in the "graph/table" view is correct.

Is this a known bug? Or am I having to expand on the specificity of restoreState?

(specs: macos 10.13, hise scriptnode 2020-08 ish.)

@d-healey Okay, cool, but how does that work, do you include that in the samples folder or do you serve the samples folder or zip as a separate thing? I want to do the same with the code but leave the art-work to the authors there.

@d-healey said in JUCE 6:

... by releasing samples under the GNU GPL you also require derivative works (aka compositions) by end users to be released under the same license, and presumably they'd have to release their non-existent source code too?

Indeed the GPL is not inclusive of circumstances, but want´s it all to be it´s own little product of everything, as do CC licenses.

I think a CC license is more appropriate for assets.

Yes, I agree. Although they seem to have an issue coexisting in one product:
https://www.linux.com/news/trouble-artwork-and-free-software-licenses/

Quote from that article:

Applying the GPL to non-software works

If none of the CC licenses allow a work to be combined with GPLed software, one common alternative is to license the artwork itself under the GPL. The FSF suggests this possibility, but it also cautions that what constitutes the “source code” of the licensed work must be clear.

So very much up to the developer him/herself to write out what "constitutes" the program. That document is quite old now, however, and in any case just a post on the web.

Samples delivered as one component in a sampled instrument is one option, like a multi-part product containing a player and the loaded samples. Those are then licensed under a CC or other type of license. In sample making you would not find much use of GPL, no, as you say, because of the implications for the end user who makes the music. Are you using more than one license for assets then? Or you just think that would be preferable? (as do I)

@d-healey said in JUCE 6:

I agree, but Christoph's license requires you to release the samples under the GPL too.

No mention of that in the License pages on github at all. Only that you release your software under the same license or any later version than v3.

https://github.com/christophhart/HISE/blob/scriptnode/license.txt

Or perhaps it´s JUCE that pose those restrictions?

@d-healey said in JUCE 6:

@andioak said in JUCE 6:

never the samples. They are not made using the source code provided by the GPL software original.

I agree, but Christoph's license requires you to release the samples under the GPL too.

Okay, but if the license of those samples has already been set by another license, that part license is overridden by the artwork´s own licensing. Or perhaps that would make them unusable with HISE?

@d-healey said in JUCE 6:

You need to provide everything that is required to build the project, including the samples.

The code is the thing licensed under GPL and written using open source original code and guide-lines and thus the code will be redistributed, never the samples. They are not made using the source code provided by the GPL software original.

You could of course provide dummy files for all sounds that use the same filenames and thereby make it entirely usable for someone looking to base their instruments on yours.

Here is a little bit from:
https://www.gnu.org/licenses/gpl-faq.en.html#WhatCaseIsOutputGPL

Keep in mind that some programs, particularly video games, can have artwork/audio that is licensed separately from the underlying GPLed game. In such cases, the license on the artwork/audio would dictate the terms under which video/streaming may occur.

So the artworks and thus the sounds in our cases can be distributed in other license types, but the work derived from the HISE script and all C++ / JUCE libraries would be bound by their GPL or commercial licenses.

It must surely be an ability of a recording artist to protect his/her works in this day in age. Even for "royalty free" samples.

@Christoph-Hart said in JUCE 6:

Hmm, the upgrade cost is rather steep, and everybody that uses HISE would have to pay the upgrade so I am not sure that's a viable step at the moment.

I don't intend to stay on JUCE 5 forever though...

Yes, that is a bit costly for some. It´s too bad that JUCE do not handle cross-grades from one-time to monthly. Too bad that JUCE do not have a mini/startup yearly plan below 300. The one-time seems to be around the same as a per-month costs in as little as 1,6 years. I guess a lot of people here got the Indie plan. It seems to be an okay price for a yearly income of max 500usd. Of course the plan allows for that much but I can´t imagine that the actual income for small/individual devs are astronomical or reaching those levels.

@d-healey said in JUCE 6:

@Christoph-Hart There's an upgrade cost? Is this for commercial licensees?

I don´t think JUCE has any but commercial ones. Unless you use the Personal or Education plan. Are you using one of those? (I guess the splash screen wouldn't be the worst thing if it did not break the branding)