@d-healey Thanks.
Posts made by NoTan2
-
RE: The XML file is not valid
@d-healey v 1.6.0 Build 650.
Built from source which I downloaded about 10 days ago, David.If you think the behaviour is non-typical, I have two other PCs on which I can build it and carry out the same tests in case it's a PC-related issue.
-
RE: The XML file is not valid
I don't wish to hijack this thread but it is somewhat related. David's comments prompted me to do some experimentation.
Since I wasn't entirely clear on what the various File\Open and Save options do (I can't find the documentation for them?), I decided to start a new project and document exactly what was created under the Project folder at each point.
I'll include the full description of what I found below but I don't really expect anyone to read it through.
The significant points are:-
After setting up some modules and a little scripting, I selected Edit Script Editor\Save Script To File. This created Interface.js under the Scripts folder.
Then I selected File\Save as XML and this action deleted the Interface.js but the script did not appear to be in the XML Preset backup file.
After this Edit Script Editor\Save Script To File refused to create Interface.js.
So I quit the application and re-opened it and pretended that the .hip was corrupt as for David above.
I selected File\Open recent XML and selected the backup I just created.
The script was missing, the Canvas was blank but the Widget List shows the Slider and Button that I created.I've also noted some strange behaviour with the <ESC> popup in the Script Editor but that doesn't really pertain to this thread.
Clearly I'm doing something wrong but not sure what it is.
Here is everything I did.
- Created new Project Folder - HISE_2
- Copied .wav and .sfz into Samples folder
- From Master Chain, added Sampler
- Dragged .sfz onto Sampler
- Selected all samples and right-clicked "Tools\Automap using Metadata"
- Added Simple Reverb to Sampler
- Autosave created Presets\Autosave_1.hip. (No scripts in this file yet)
- Switched to Interface Designer view and clicked Frontend Panels button.
- Clicked Ok on "Create User Interface" dialog
- Clicked OK on "Switch to Interface Designer" dialog
- Autosave created Presets\Autosave_2.hip. (Default script is now in this file)
- Added Knob to Canvas and renamed to "knReverbAmount", text to "Reverb Amount"
- Set processorId to Simple Reverb and parameterId to WetLevel.
- Right-clicked on Simple Reverb and selected "Create script variable declaration" and pasted into Script Editor.
- Created button and renamed to btnReverbEnabled and text to "Reverb Enabled"
- Right-clicked on btnReverbEnabled and selected "Create custom callback definition and pasted into Script Editor.
- Autosave created Presets\Autosave_3.hip. Script seems to be up to date in this file.
- In Script Editor, removed comment from the new inline function and <ESC>. NOTE: SimpleReverb was not shown. Typed "Simp" and <ESC>. Only shows ModuleIds.SimpleReverb. Doesn't offer the SimpleReverb var declared above.
- Selected File\Save Archive, clicked OK on "Save Master Chain" dialog. Typed "HISE_2 as unique name. Clicked OK. Saved as Presets\HISE_2.hip.
- File\Quit.
- Re-opened HISE.
- File\Recent Projects and selected the HISE_2.
- Clicked OK on Switch projects? dialog. This appeared to do nothing.
- Selected File\Open Recent Archive and selected "HISE_2". This loaded project.
- Back to Script Editor and typed "S" and <ESC>. Popup now shows "SimpleReverb".
- Typed "SimpleReverb.setBypassed(value == true ? false : true);"
- Compiled. Tested and works Ok.
- Selected Edit Script Editor\Save Script To File. Created Interface.js under the Scripts folder.
- Selected File\Save as XML and typed "HISE_2". This created XmlPresetBackups\HISE_2.xml but DELETED the script Interface.js.
- Selected Edit Script Editor\Save Script To File. This time it did NOT create Interface.js.
- File\Quit.
- Re-opened HISE. Pretended that the .hip was corrupt and selected File\Open recent XML and selected HISE_2.xml.
- I got back the Sample with all the samples and the Simple Reverb.
- In Interface Designer view, I have no script, the Canvas is blank but the Widget List shows the Slider and Knob.
- Rebuild Interface does nothing.
- File\Open Recent Archive. This restores the Canvas and the script but not the last line I entered.
- In Script Editor, <ESC> now presents the SimpleReverb var as a String and offers String functions after the fullstop.
-
RE: New to HISE - some issues
@christoph-hart said in New to HISE - some issues:
I am also not 100% sure what you did here ;), but the loop points can also be imported afterwards by selecting all samples and running the command in the context menu (I think it‘s called Import loop points from metadata).
Don't mind me - I'm just demonstrating my lack of experience with samplers.
Found it - it's called "Automap from metadata" and it works fine.TBH I dislike this format as it weirdly mix instrument properties (like Filter Envelope Attack) with mapping data and is terrible to parse because it doesn‘t use quotes to delimit strings so a filename with spaces in it gets treated as two tokens. I don‘t know who decided this but they were surely having too much red wine that day...
I agree - the SFZ format is a dog's breakfast but it's not the worst I've had to work with over the years.
-
RE: New to HISE - some issues
@notan2 said in New to HISE - some issues:
I decided to experiment with an SFZ instrument (alto Sax). I imported it into the Sampler and all looked fine except that the note was only playing for the length of the sample and then cutting off. I looked in the Sample Editor and it appeared that the loop points hadn't been extracted from the .wav files.
Just had a look through the code for the Sfz Importer and noticed that it supports the loopstart, loopend and loop_mode opcodes. So I edited my original SFZ file and added these opcodes to one of the samples, imported it into HISE and it worked.
That explains why the Sfz Importer (quite reasonably) doesn't offer to read the loop points from the .wav file.
-
RE: New to HISE - some issues
@d-healey I certainly am. I enjoyed your video about using Loop Auditioneer and downloaded a copy as well as Wavosaur.
-
RE: New to HISE - some issues
I'm finally getting some traction and having a lot of fun. I've read all the documentation I could find and watched all/most of the excellent videos by @d-healey. Clear, well-prepared and well-paced - great work, David!
I decided to experiment with an SFZ instrument (alto Sax). I imported it into the Sampler and all looked fine except that the note was only playing for the length of the sample and then cutting off. I looked in the Sample Editor and it appeared that the loop points hadn't been extracted from the .wav files.
So I renamed one of the .wav files with tokens and selected "Filename Token Parser" and it asked if I wanted to set the loop points from metadata and this time it worked fine.
So I thought, no problem, and wrote a utility to parse the SFZ and rename the .wav files with tokens. At which point I realised that the lokey and hikey did not appear to be part of the available properties. (Serves me right for not reading the documentation carefully - but did I read somewhere that the Importer is scriptable and perhaps I could map additional properties?).
Again, no problem, so I wrote another utility to parse the SFZ, extract the loop points from the .wav files and write out a SampleMap XML. Imported it and this time everything worked fine.
While it was an entertaining couple of hours of coding, it's occurred to me that some of the HISE users will not be programmers, so, (likely as a result of me being a novice at sampling), I'm probably going about things the wrong way.
-
RE: New to HISE - some issues
Hi David and Christoph,
Thank you for the prompt replies and the links for further reading.
I confess that, as I have a few projects on the go at the moment, I was looking for a "quick and dirty" overview of HISE. This is out of character for me so I'll consider it a lesson learned and dive in and read the manuals as I normally do.
I've located David's videos on his youtube channel and I'll read through the links you have provided on the new Interface designer.
I'm sure that I'll enjoy learning about the product - I'm always keen to mix programming and music.
HISE is a truly impressive project, Christoph. Thank you so much for making it available.
Paul.
-
New to HISE - some issues
Hi All,
My first post here.
I recently discovered HISE and decided it looked very interesting. I've been a C/C++ programmer for more than 30 years and I'm extremely impressed with the quality and breadth of Christoph's work on this project.
I've downloaded the code from github and after a few issues building it in VS2015 Pro, I installed VS2017 Community and it all went well after that. Environment is Windows 10 ver 1803.
I've read through the tutorials and watched David's videos and lastly started following Christoph's video on building an instrument in 5 minutes.
Unfortunately, I'm getting somewhat different results from this video. I've got to the part where he adds a Table to the Script Processor and this is where my copy diverges. After adding the table, I don't see the popup which asks for the name of the table. After playing with the Right Panel, I managed to display the InterfacePropertyEditor which was "Disconnected". After connecting it to the Script Processor and selecting the Table, I was able to change the name.
However, the next issue was that there was no code being added to the Script Editor when I added the Table and no JSON code appeared when I dragged the Table.
Seems like I may have missed something in the setup somewhere. I've recompiled the code several times and there are quite a few Warnings (just usual things like unreachable code , unreferenced formal parameters and conversion loss of data) but no Errors. I'm not using IPP at this stage.