@d-healey said in Issue with working with global scripts/recompiling after fixing errors:

@thrice801 All included files should be available from the little drop down at the top of the script editor in which they are included.

ahh ok I see thank you! been meaning to subscribe to your patreon gonna do that now

@ulrik that did it thanks! swore I tried it yesterday but think I did something wrong

@ulrik that did it thanks! swore I tried it yesterday but think I did something wrong

Hi,

I'm trying to make a midi effect type plugin where I play a midi drum loop based on a single keypress. It's kind of working, however, I can't figure out how to properly do it where it doesn't cause issues in abelton (I am using the vst instrument workaround for abelton). Note on is working the way I want it to, but the note off events aren't being written, so it shows up as a giant messed up blob of midi when you try to record the output.

The following, the clip labeled track 1 is me dragging one of the clips in manually. What you see after is the issue I'm trying to solve (I can confirm there are no note offs being sent from the midi player by logging also).

Here is what my chain looks like. And for context, in the onNoteOn/off in the main interface I am doing Message.ignoreEvent(true); (to stop the main key being pressed from propogating and dual triggering), but even if I say Message.ignoreEvent(false) in the note off, none of the loops note off messages are being sent, only note on. Anyone know how I could fix this properly? (also just to be clear, in Script Processor 1 onNoteOn/off, I am doing Message.sendToMidiOut(), but onNoteOff callback never fires)

@thrice801 yep that's exactly what I just was figuring out. then after compiling manually in xcode thought it still wasn't working but turns out it was, just issues with abelton and midi fx plugins I think so it wouldn't load. Got a different snippet to compile; I think I had to disable IPP also to get it to compile. -- actually export seems to be working from within hise now after ipp thing (I believe), it still throws the error on export but looks like the xcbeautify step doesn't need to succeed in order to compile. Thanks for the help!

@d-healey HISE's, the HISE Standalone projucer, before compiling HISE. I've tried it with and without arm selected as valid architectures and recompiling

After finally getting the HISE release version to build, I can't seem to be able to export either VST or AU plugins. Trying to export a midifx plugin. - The weird thing, is I actually only had x86_64 selected in valid architechtures in the projucer file, and still got this after building the hise release and trying to export. So I'm not sure what's going on, anyone have any idea? Did a forum search and found some similar stuff but nothing that looked like this specifically. - But also there isn't any arm references or anything in the error, just x86_64

Re-saving file: /Users/jasonayre/code/hise_projects/alientoric_midi_player/Binaries/AutogeneratedProject.jucer
Finished saving: Visual Studio 2017
Finished saving: Xcode (macOS)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling MIDI FX plugin alientoric_midi_player ...
/Users/jasonayre/code/hise_projects/alientoric_midi_player/Binaries/batchCompileOSX: line 7: /Users/jasonayre/code/hise_develop/tools/Projucer/xcbeautify: Bad CPU type in executable
** BUILD FAILED **


The following build commands failed:
	CompileC /Users/jasonayre/code/hise_projects/alientoric_midi_player/Binaries/Builds/MacOSX/build/alientoric_midi_player.build/Release/alientoric_midi_player\ -\ Shared\ Code.build/Objects-normal/x86_64/include_hi_streaming.o /Users/jasonayre/code/hise_projects/alientoric_midi_player/Binaries/JuceLibraryCode/include_hi_streaming.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'alientoric_midi_player - Shared Code' from project 'alientoric_midi_player')
(1 failure)```

@d-healey success! (sort of, exporting still not working but will post separately). Thanks for the help

@d-healey oh wait according to that I can update to 14.2, I'll try that thanks

@d-healey was hoping not to have to because I think I have to update my entire OS to get newer version of xcode iirc which always seems to break things, but may be at that point

@d-healey 13.4.1 -- and as an update, nothing I did worked, including disabling everything but x86_64 - I've tried clearing build folder, blowing away the xcode project completely so the projucer can create a new xcode project, nothing. Keeps getting stuck on that same error, on the link HISE step.

Also for context, I am trying to build the release version so I can export my plugin to vst so I can test it. When I've tried doing that via the debug build I get a version mismatch error though, and it fails to compile it if I try to force it through. Not sure if there is some workaround I can employ or something.

@thrice801 oh wait.. I was clicking on "Release" in the projucer, I just found valid architectures, by clicking on the parent item above it. trying build again