Hi, I have finally managed to get HISE compiled and working from an exported RNBO file as a hardware FX and it's great!

In my RNBO patch, I am referencing a Buffer and would like to know how, in HISE I can replicate an audio Buffer that is called from within my compiled RNBO FX Hardware (compiled) DLL.

So in essence I would like to setup a buffer in HISE!
I think?
Thanks

@d-healey

Ah! I see…I’ll have a go. Hopefully this will work and I can begin setting up my RNBO patch with a HISE interface…

Thanks again

As a newbie, I would like to know how I can route my MIDI MPE input data into HISE to send each note/pad to have its own independent effects.

For example, the keyboard uses a waveform generator with all its keys, my interface has 16 individual MPE keys/pads that trigger an audio buffer /MIDI note and CC.

So I guess the question is:
How do I setup all 3…

1. Input for each Note
2. Buffer for each Note
3. Effect for each input

Thanks!

Hi, I have finally managed to get HISE compiled and working from an exported RNBO file as a hardware FX and it's great!

In my RNBO patch, I am referencing a Buffer and would like to know how, in HISE I can replicate an audio Buffer that is called from within my compiled RNBO FX Hardware (compiled) DLL.

So in essence I would like to setup a buffer in HISE!
I think?
Thanks

@d-healey

IVE SUSSED IT OUT!!!!!!!
It was a real challenge.

OK, so it has something to do with the path of JUCE and the location of it in the developer folder. This needs to be explicitly written in JUCE or it won't compile.

I also made the folder for the compiled DLL so copy into: Binaries\VisualStudio2022\PAD1.sln

After a restart, it all worked and hey presto an RNBO Chorus compiled.
I also Exported a Standalone as you advised from a clean build and this worked too.

I WOULD REALLY APPRECIATE A FUTURE VERSION OF HISE TO BE MORE USER FRIENDLY AND AUTOMATICALLY ADD PATHS FOR MSBUILD OR THE VS Solution.

Thanks !

@Christoph-Hart

THIS IS JUST A THOUGHT...................................................

I develop using VR and UNREAL so I have lots of developer plugins added in C++ together with MAX externals, what if there is a conflict with all of this?

@d-healey

Hi, Apologies for the late response to you and Christopher...
I have been away on business. I have tried both uninstalling and reinstalling VS 2022.

Using Christophers advice, I installed the MS BUILD for VS2022 and initiated all paths in the environment variables option. MS BUILD was installed and this was confirmed using the msbuild-version command.

Then when I rebuilt HISE again to double-check from source and Exported from a clean version (NO Effects/no nothing) I got the same error for the PATH Once again?

The only thing I could maybe try is installing HISE on a MAC and see if this works.
But I do all my coding on Windows with MAX too!

I must admit, I am very disappointed as I would like to develop a UI for my RNBO interface for a standalone application using C++ and wanted to use HISE to do this.

For now ive given up as it's taking up too much time out of my business to faf around with this!!

Thanks for your help though If this gets sorted and one day I can build even a standalone (without any errors popping up) I would really like to use HISE to develop my application for clinical and special needs applications.

Thanks !!!!

@Christoph-Hart

I am not sure if its Basic windows stuff !

The error message “MSBUILD : error MSB1003: Specify a project or solution file” occurs when you’re trying to build a .NET project, but the build process can’t find a valid project or solution file. Here are some steps to resolve this issue:

Specify the Project or Solution File Explicitly:
Make sure you’re in the correct directory that contains your project or solution file.
Explicitly specify the project or solution file as an argument in the dotnet publish command. For example:
dotnet publish <path_to_project_or_solution_file>

Replace <path_to_project_or_solution_file> with the actual path to your .csproj or .sln file.
Check Your Project Structure:
Ensure that your project directory contains a valid .csproj or .sln file. If it doesn’t, create one.
If you’re working with a .NET Core project, you’ll need a .csproj file. You can create one manually or use the dotnet new command to scaffold a new project.
Package Versions and Dependencies:
If you’ve created a .csproj file, make sure it includes the necessary package references (dependencies) for your project. You can manage these using NuGet or by editing the .csproj file directly.
If you’re unsure about the correct package versions, consult the official documentation or search for the packages on NuGet.org.

NOPE!!!!

@GreekProgrammer

Hi is this it??

@Christoph-Hart

Hi Yes I have VS 2022 installed already and its set to 2022 in HISE too...
any suggestions?

Thanks

@d-healey
yep still the same error!

AAAARRRGGGHHH!

I GIVE UP

What do you think it could be?