@Nater Looks like you can still get the VS22 installer from TechSpot: https://www.techspot.com/downloads/7493-visual-studio-2022.html

@David-Healey Got it...thanks so much! I was wondering the same thing about the sandbox thing...was trying to make sure I wasn't missing something lol

@David-Healey thanks!

@flameshower you will need to build HISE with ipp if you want to use it.

it's fixed now.

@udalilprofile
This bug has already been discussed twice in the forum. Do not use the latest commit to compile HISE.

Use this commit: cf3fc78

You can do this as follows:

Clone HISE in the usual way with git clone https://github.com/christophhart/HISE.git Set the head to the last working commit: git reset --hard cf3fc78

Now you can compile HISE without errors.

PS. Use the develop branch.

@David-Healey An issue I run into now is when

function onNoteOn() { for (note in track) { if (note.isNoteOn()) { Console.print(note.dump()); Console.print("Note: " + note.getNoteNumber()); //Synth.playNote(note.getNoteNumber(), note.getVelocity()+1); //Synth.playNote(note.getNoteNumber()+12, note.getVelocity()+1); //Synth.playNote(note.getNoteNumber()-12, note.getVelocity()+1); } //Synth.noteOffByEventId(note.getEventId()); } } function getNoteOn(list, noteOn) { for(note in track) { if(note.isNoteOn() && note.getEventId() == noteOn.getEventId()) return note; } } MIDIPlayer1.flushMessageList(track);

I uncomment any of the synth.playNote function calls, it plays very distorted, notes playing for far longer than they are supposed to, like I mentioned earlier.

@David-Healey I have an Utils.js file where I create abstractions for every tedious thing like this, but a native function would be useful indeed

@JamesC if I understand correctly, you want the loops to follow the DAW tempo, but the Sampler’s tempo-sync won’t time-stretch them. Wouldn’t be better to use an Audio Loop Player module instead?

@dannytaurus oh, didn't know about this feature. I actually like it 😬

@tjrob

That shortcut takes you to the project's App Data folder. This folder is created when you compile and run your plugin. It's used to store plugin data files on the end-user's system. It's unrelated to your HISE project folder.

https://docs.hise.dev/working-with-hise/menu-reference/file/index.html#show-hise-app-data-folder-in-explorer

https://docs.hise.dev/working-with-hise/project-management/index.html

@Christoph-Hart said in C++ Version Preprocessor?:

everything will explode

I am yet to experience an explosion, RTNeural-NAM is using std::span and the Linux/Mac compilers are complaining unless I switch the AutoGeneratedProject.jucer to C++20

C++17 works fine on Windows so I'm not even sure if the span is ever actually created

Edit: Yep it's some weird ghost function which isn't being called anywhere, might be for a specific edge-case but I can comment it out and use C++17

@Christoph-Hart I updated to the latest dev build and the crashing no longer happens

@pcs800 The bootcamp course has the latest compiling videos

https://audiodevschool.com/courses/hise-bootcamp/

@MysticForgeRider yes to both!

But I've found a workaround for the moment: create a new project, and copy all elements manually. Long live VM's.

@David-Healey said in Exporting samples efficiently:

@jonalexander23 The samples aren't embedded. Does your project contain images?

Thanks that's good to know..it's a small project but actually can't be small as 77mb of samples (they total around 100mb in Samples folder)..there are 20mb of images..so guess the rest is just stuff in the build..thanks again.

After all struggling I've decided to switch to pure C++ VST3 programming.

@dannytaurus Looks good