Posts made by Sympol

@d-healey Thanks David..... Flushed with success I'm downloading the tutorials now to dig deeper....

Thanks, downloaded and compiled OK. I noticed there are new versions of both AsioSDK and VST SDK available - is it worth using these or should I just quit while I'm ahead :)

@d-healey Thanks, downloading now.....

Hi, I've been struggling with this for over 2 days now and have no hair left. I've followed all the steps in the 'Building HISE on Windows 10' video on Youtube. I'm using Windows 10 Pro, Visual Studio 2017 and have installed the w_ipp_2019.4.245.exe file as discussed in that video. When I run the projucer, I get a message about a new version of JUCE, but I've ignored this and run the version with HISE.
Trying to build the standalone HISE app, release, x64 as in the video, but getting multiple errors (1147 errors and 74 warnings) before the compiler crashes with too many errors.
Is there something I'm missing here? IPP has installed in C:\Program Files (x86)\IntelSWTools with a number of subdirectories 'compilers and libraries', compilers and libraries 2019 and compilers and libraries 2019.4.245
When I look at the Intel site it tells me:
After installing Intel IPP, set the PATH, LIB and INCLUDE
environment variables by running the script appropriate to your target platform architecture. The scripts are available in <install dir>\env
.
By default, the <install dir>
is C:\Program files (x86)\Intel\oneapi
Configure Your IDE Environment to Link with Intel IPP
To configure your Microsoft* Visual Studio* development system for linking with the Intel IPP library, follow the steps below. Though some versions of the Visual Studio* IDE may vary slightly in the menu items mentioned below, the fundamental configuring steps are applicable to all these versions.

In Solution Explorer, right-click your project and click Properties
.
Select Configuration Properties
> VC++ Directories
and set the following from the Select directories for drop down menu:
Include Files menu item, and then type in the directory for the Intel IPP include files (default is <install_dir>\include
Library Files menu item, and then type in the directory for the Intel IPP library files (default is <install_dir> \lib<arch>
Executable Files menu item, and then type in the directory for the Intel IPP executable files (default is <install_dir>\redist<arch>
The values for the include files directories and the library files directories are correct as above, but there is no mention of ipp in the executable files directories
Any help would be appreciated. I realise I can just download the compiled version of HISE 2.0 but would really like to solve this....
Thankyou......

Thanks Christoph - didn't expect you to produce this tutorial so quickly :)
I'm a bit tied up for the next couple of days stacking firewood for the coming winter, but as soon as I get a chance I'll go through the tutorial and do some experimenting.....
Thanks again!

Thanks again Christoph - thought there would be a way of doing it. I now have 3 sets of samples from selected organ stops, but would appreciate some advice as to how to call each SampleMap from a user interface, but don't get distracted by this - you have better ways to spend your time, I'm sure :)

Thankyou very much! Appreciate you taking the time to answer my dumb questions...
Have now renamed the files to PedalOrgan_C3_0_127.wav and so on and successfully imported them into the sample map in HISE, so now I know how to do that.....
The next step is to add some effects etc. as in the tutorial and maybe create a simple user interface whereby I could add some controlled reverb, also as in the tutorial....
Obviously I only have recorded a single octave at this stage for testing - each wav file has to be cleaned up to remove extraneous noises such as clicks and wheezes from the pedals and bellows but I'm well on the way now....
Ideally I would like to create a user interface (for my own use only) whereby I could add in the various stops from the organ (its a very ancient one and has stops for such effects as 'Vox Humana', 'Bass Coupler', 'Treble Coupler' etc.....)
I presume I will need to record each note in turn with these stops applied, which will lead to a pretty large number of samples.... Without delving into specifics (which I'll need to do at a later stage) is it possible to select which set of samples (eg relating to a specific organ stop) are played through the user interface? In other words, use an interface control to select a specific set of wav files?
Many thanks again for your time and patience....

Hi,
As you may have gathered from my previous questions, this is all very new to me!
Completed the tutorial and now want to move on to try supplying my own sample wav files instead of the Music Box samples as a test. I have an old pedal organ, from which I have recorded a series of individual notes as separate wave files, with names such as Organ_C.wav, Organ_Csharp.wav and so on for a total of 12 individual files over an octave.
I have created a new test project and copied these wav files into the samples folder and then tried to import them into the HISE sampler in the same manner that the Music Box samples were added in the tutorial. But the results are garbage!
Is there a particular naming convention I should be using for each file?
I followed through the Youtube video suggested in another post about rendering samples using Reaper, but the end result of that video seemed to be a series of wav files similar to my own.
When I import my wav files into my test project they sound very much like the music box samples and not at all like the originally recorded wav files from the pedal organ.....
Does anyone have any clues which could help me over this hurdle please?
Thanks.....

I may have found the answer!
Just tried again, starting from scratch as far as saving as a preset, but then this time instead of loading the project (step 2 in the reload as work in progress section) after restarting HISE, I simply opened the .hip file without doing anything else, and there was my project as I had left it, with working sound from mouse and midi keyboard.
It seems that the 'Load Project' option under Files is not necessary and indeed stuffs up the sound from the project - all that is required is to load the .hip preset file.....
It takes a while to get used to the terminology used - I had assumed that loading a project would re-load a previously closed project in the state that it was when closed, but obviously not so. So really the preset is a backup of the project at a certain state and if I want to go back to a selected point in the project development, as long as I have saved a preset at that point (with a suitable name) I just need to load that particular preset.
Now I'll continue with the tutorial, saving a preset at various stages and see what happens when I restore from each.....

Hi and thanks for responding. yes, I've downloaded and watched your video a number of times, but I still have the problem of no sound when I re-open my preset file....
These are the steps I've taken again today:

1. Open HISE
2. Create new project folder (Organ) version 1.0.0
3. Copy MusicBox samples into Samples folder under Organ project
4. Master Chain, click ’+’ and select ’Sampler’
5. Switch to dedicated Sampler workspace view.
6. Double-click Samples folder, select all and drag to Sample map editing area.
7. Select File Token Parser, click OK and set Tokens to:
   Ignore
   Single Key
   Low Velocity
   High Velocity
8. Fix mapping – lassoo all samples and click Close vertical gaps; Move selection up 2 octaves..
9. Export as HLAC Monolith, named OrganMap, low file size….
10. At this stage have sound from using both midi keyboard or on screen keyboard (using mouse).

Now wish to save this in its working state, so:

1. Save file as xml backup (OrganBackup.xml) in XmlPresetBackups folder
2. Cancel on next two boxes.. ( )
3. File → Save → OrganBackup preset.
4. Now have the following extra files:
   OrganMap.ch1 in ’Samples’ folder in addition to the MusicBox samples copied in earlier
   OrganMap.xml in ’SampleMaps’ folder
   OrganBackup.hip in ’Presets’ folder (together with a series of Autosave_n.hip files)
   OrganBackup.xml in ’XmlPresetBackups’ folder
5. File → Close Project. ’The current preset will be discarded’ - click OK as already saved preset
6. Close HISE

Now try to reload as a work in progress project…..

1. Open HISE
2. Load Project (Organ) – nothing appears…..
3. Open xml backup – select OrganBackup.xml from XmlPresetsBackup folder, nothing happens…..
4. Open file OrganBackup.hip from Presets folder – shows the samples in the Map Editor in the Sampler – but no sound from either midi keyboard or by using mouse on the on-screen keyboard….
5. Checked Audio device settings from ’View’ Menu. All seems to be correct and sound produced when the ’Test’ button is pressed.

There must be some simple mistake I am making that is killing the output after I have loaded in the .hip file but for the life of me I cannot find what that is...

Any help from anyone would be wonderful - at this stage I'm simply going around in circles. If I'm unable to reload a working project I may as well give up, which would be a shame after all the effort that has gone in to building HISE - not to mention all the hours I've wasted trying to solve what is surely a very basic problem....

Hi - this seems to be a very basic question but I have been unable to find an answer.
I've been working through the tutorial, using HISE 1.0.0 but have not yet found a method whereby I can save and close a project mid-term and come back to it later, maybe the next day and continue where I left off.

I have tried various computations, but nothing seems to work completely successfully. Here's what I have tried (documented as I went):

1. Create new project
2. Follow Tutorial to drag in samples to Sample Map Editor:
   Want to save project now. Click ’Close project’ window appears with ’Discard the current Preset – the current preset will be discarded’

If click cancel – back to project unaltered.
If click OK, back to project (unaltered and not closed) but close project option under ’File’ is greyed out….
3. Click Save and message box appears: ’Save Master Chain – do you want to save this preset:

Click cancel and back to project unaltered
Click OK, enter name for preset. Call it Test1 – back to project unaltered but no preset appears under Presets or UserPresets in file browser – where did it go?
4. Click Save As, enter name Test1 and get message – do you want to overwrite file Test1.hip
Say no and back to project, say yes, back to project (close project still greyed out) and still no file under Presets / UserPresets.
Select ’Save current state as new user preset’ and again no files appear under either sub directory.
5. Select Quit (no option available to close project) – message box ’Do You Want To Quit OK/Cancel’
Select Cancel – remains unaltered
Select OK – HISE closes.

Restart HISE
Load project Test1 – as if new project but project properties and user settings as created initially.
No info in master chain – eg, samples not loaded, nothing in sample workspace, everything lost……

Repeat process as above from tutorial, but take next step – eg Fix Mapping and drag 2 octaves up, save as monolithic file named Test1.
Cannot see either .xml file in SampleMaps or .ch1 in Samples via HISE – but using file explorer in Windows both files are present…..

Add velocity modulator as per tutorial, then archive project as zip file (ZippedTest1.zip).
Save from File menu as Test1b.
Close project and close HISE

Restart HISE
Load Project (Test1) again empty
Open file from project (lists a number of autosaves + Test1b)
Select Test1b and all back except – no sound from keyboard although samples are present and velocity modulator as added is present on main workspace view. Sample Workspace view is empty however, until click on ’up/down’ arrow and select ’Sampler’ from 2 options Disconnect or Sampler, when samples appear, but again no sound when clicking on keyboard or playing midi keyboard.
Closed project and quit HISE

There must be something I'm missing - it cannot be so difficult to be able to save a project and then re-open it again to continue at the same point at a later date or time without having to go back and recreate the previous work.....

Thanks for uploading that Christoph - I'll check it out!

OK - many thanks for the response. Appreciate you taking the time to help me out :)
Now I see how it works! Did as you suggested above and managed to create the factory function successfully - now onward and upwards with the remaining controls and the reast of the tutorial....

Also located the editorData.json file, deleted it and yes, 1.0.0 now starts OK

Now I'm wondering how best to pause a project overnight and reload it the next day to continue. I tried File -> Close Project, shutdown HISE, restarted and attempted to load the project(MusicBox), but there was nothing displayed - it was if it was an empty project.
Tried File -> Open File -> Presets folder and selected the latest autosave.hip and there was my tutorial stuff - except the keyboard now only plays the mallet sound, no musical notes. I may have stuffed something up by switching between versions 1.1.0 and 1.0.0 so I'll manually delete the MusicBox project folder and sub folders and start from the beginning again using version 1.0.0

What is the recommended way to save a project to enable a computer shutdown so that I can pick up again the next day?

Sorry for all the questions!

Thanks for responding, but I'm more confused than ever.
I'm still none the wiser as to how I would create a factory function.....
I've tried adding this code:
inline function createMusicBoxKnob(name, x, y)
{

}
in the script editor, highlighting it and right clicking. Still the Convert to UI factory method is greyed out.....
Tried just adding inline function by itself and opening context menu - same result.
In simple terms, how do I create a factory function?
Incidentally, I'm using version 1.1.0 compiled yesterday from the latest source code on a Windows 10 Pro machine x-64.
Thought I'd try going back to the download version 1.0.0 from the website, but after installing this, I can't get it to run anymore (it worked well previously) - double click the icon and apart from the spinning wheel icon for a few seconds, nothing happens at all. Tried uninstalling it and reinstalling with same result. Is there a problem with having both versions 1.1.0 and 1.0.0 installed at the same time? Should I remove the both the later version (1.1.0) and the 1.0.0 version totally and try starting from scratch?
If I had any hair left it would all have been pulled out by now :)

I did that, but can't access Convert to UI factory method in the options - see attached screenshot
Am I in the wrong area? I put the code in ScriptEditor Interface. oninit. Highlighted the relevant code, right clicked and got the attached context menu, but the option is greyed out so unavailable.....
Many thanks for your patience

OK, so I'm a real novice at this. Been following the tutorial after compiling the latest HISE from GitHub source. All going well until I get to the section referring to adding the various controls to the plugin. Created the first 'modWheelAttKnob' but then creating subsequent knobs I get lost....
The tutorial says:
'If you rewrite the widget definition as factory method, you'll end up with something like this:
inline function createMusicBoxKnob(name, x, y)
{
local widget = Content.addKnob(name, x, y);

Content.setPropertiesFromJSON(name, {
  "width": 32,
  "height": 38,
  "filmstripImage": "{PROJECT_FOLDER}knob_128frames.png",
  "numStrips": "128"
});

return widget;

};

const var modWheelAttKnob = createMusicBoxKnob("modWheelAttKnob", 87, 99);
This does not seem to be less code, but from now on, you can add the same knob type with a simple line:
const var clickAttackKnob = createMusicBoxKnob("clickAttackKnob", 127, 99);
Now comes the best part: HISE can automatically convert a widget definition plus its JSON properties into a factory method. Select everything you want to move into the factory method (in this case the widget definition line and all JSON code including the comments), and select "Convert to UI factory method" in the context menu. Enter a name for the method (start with createXXX) and it will replace the definition with the lines shown above:'
How do I get to the context menu to do this? Highlighted the required code, tried ESC but there is no Convert to UI factory method shown.......
Looked through the documentation on Scripting and Script Panel, but couldn't work out how to do this.......
Sorry to be a nuisance and asking basic questions but again I'm stuck and any help much appreciated.....

OK, Recompiled from the GitHub build and was concerned when I ended up with an empty plugin window. This explains it!
Added the above code and now have the keyboard, but as a raw novice, what is the code to add in the other missing bits, such as the Output Meter please?
I'm not sure what the new Floating Tile system is or how I would add a FloatingTile - presumably use the above code as a template and instead of 'Keyboard' use something else such as outputMeter or cpuTempoVoices. Where would I find more info on this please?

OK, downloaded the images and was able to continue to the next step of adding the first control knob, but suddenly HISE has stopped responding and I am unable to restore my project on restarting....
Think I'll shut down Windows and start again tomorrow......

No - that would certainly help! Didn't realise I had to download anything other than the Music box samples and the standalone HISE....
Are there any other files relating to the tutorial I should download?
Thanks for the quick reply :)

Hi,
Totally new to this, so forgive a basic question.
Following the tutorial and all going well with a few backtracks.
Up to part IV - creating the interface content. Added the bgImage OK but when trying to select the Background.png image at the filename property, I have no images in my Images folder....
Running Windows 10 Pro - did a file search for the image and found nothing....
Have I missed something vital in the setup?
My version is 1.0.0 8 June 2017 version 649
Little bit stuck at this stage :) so any help very welcome