<div dir="ltr"><p>Jack's note that miniAudicle is only looking in C:\Program Files\ChucK\chugins\ ended up being the key here. I now have some o the chugins installed and working :) I had the 10/21/2015 .chug versions floating around my computer from 1.3.5.2, I made sure the 02/05/18 versions were in C:\Program Files\ChucK\chugins\ ( and the only versions in there, get the old ones out)</p><p>The following are not automatically installed with <a href="http://1.4.0.0">1.4.0.0</a>:<br>Binaural, Faust, Ladspa, NHHall, Random, Wavetable </p><p>Below are the steps I took to get Binaural, Wavetable, and Random to compile and install. Have not attempted Faust or Ladspa yet</p><p>I could not get NHHall working with this method. NHHall does not come with a VCXPROJ file so I used the VCXPROJ file from another chugin as a template and made my own for NHHall. Using the steps below I was able to sucessfully build a .CHUG file for NHHall, but when trying to load the chugins in miniAudicle I get an error:<br>[chuck]:(3:SEVERE): | | | error loading chugin 'NHHall.chug', skipping<br>[chuck]:(3:SEVERE): | | | error from chuck_dl: 'no version function found in dll 'C:\Program Files\ChucK\chugins/NHHall.chug''</p><div>Not sure if this is a problem with the NHHall files or user error on my part.</div><div>Anyone have NHHall working on windows 10?</div><div><br></div><div>Thanks</div><div>Ben</div><div><br></div><div>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</div><p><br>After many days on stack overflow, trying to set up my laptop to use the VS 2010 build tools in the year 2018, I gave up and just tried stuff until I came up with this brute force method of installing the rest of the chugins</p><p>Step 1:<br>git clone <a href="https://github.com/ccrma/chugins.git">https://github.com/ccrma/chugins.git</a><br>the git repo will be placed in C:\Users\<name>\chugins<br>Open the makefile in C:\Users\<name>\chugins, the first lines are a list of chugins in the order they will be built/installed in. Put the chugin you want to install at the beginning, e.g. CHUGINS= Wavetable etc. ( This is just so that you don't have to go through the steps below for each of the chugins that are already installed).</p><p><br>Step 2a:<br>You might get the following error when running $ make win32:<br><font face="monospace,monospace">msbuild.exe /p:Configuration=Release<br>process_begin: CreateProcess(NULL, msbuild.exe /p:Configuration=Release, ...) failed.<br>make (e=2): The system cannot find the file specified.</font></p><p>You need to find the directory containing msbuild.exe and add it the MINGW64 path, this worked for me:</p><p>$ export PATH=$PATH:"C:\Windows\Microsoft.NET\Framework64\v4.0.30319"</p><p>Step 2b:<br>Open the VCXPROJ file in C:\Users\<name>\chugins\Wavetable, note that the first line indicates ToolsVersion="15.0"<br>make sure you have the 15.0 buils tools for VS installed and that MINGW64 can access the folder:</p><p>$ export PATH=$PATH:"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin"</p><p>Step 3: <br>$ cd chugins<br>$ make win32</p><p>Although I had all the build tools, compilers, and SDKs for the v100 platform toolset, chugins would not compile and I couldn't get past the following error:</p><p><font face="monospace,monospace">error MSB8020: The build tools for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. </font></p><p>I noticed on the github history that there was a fix on 01/17/18 that changed the VCXPROJ file for each chugin from <PlatformToolset>v141</PlatformToolset> to <PlatformToolset>v100</PlatformToolset>.<br>So as an experiment I changed this back to <PlatformToolset>v141</PlatformToolset> in the VCXPROJ file for the chugin (there are a few different lines of this in the file) <br>NB: v141 did not work for each of them, for example Binaural needed v140 to compile</p><p>Step 4:<br>run make win32 again. Should get a 'build succeeded" in the log</p><p>Step 5:<br>make install. get the following error:<br><font face="monospace,monospace">$ make install<br>CHUCK_STRICT=1 make -C Wavetabler/ install<br>make[1]: Entering directory 'C:/Users/Ben/chugins/Wavetable'<br>gcc -O3 -Werror -c -o Wavetable.o Wavetable.cpp<br>process_begin: CreateProcess(NULL, gcc -O3 -Werror -c -o Wavetable.o Wavetable.cpp, ...) failed.<br>make (e=2): The system cannot find the file specified.</font></p><p>Step 6:<br>move the contents of C:/Users/<name>/Wavetable/Release to C:/Users/<name>/Wavetable/ and change the file name of Wavetable.obj to Wavetable.o</p><p>Step 7:<br>run make install again. then move the Wavetable .CHUG file from C:/Users/<name>/chugins/Wavetable to C:\Program Files\ChucK\chugins<br>Double check that C:\Program Files\ChucK\chugins is a directory for chugins in miniAudicle and re-start miniAudicle. The chugin should be working now, at least avoiding the 'undefined type' error in miniAudicle.<span></span></p></div><div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid #d3d4de">
<tr>
<td style="width:55px;padding-top:13px"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;"></a></td>
<td style="width:470px;padding-top:12px;color:#41424e;font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link" target="_blank" style="color:#4453ea">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 23, 2018 at 8:49 PM, Spencer Salazar <span dir="ltr"><<a href="mailto:spencer.salazar@gmail.com" target="_blank">spencer.salazar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">The main difference between the two is that when I was looking to use MidiRW, it didnt/doesn't actually work and is just a shell around an unimplemented interface, so MidiFileIn was added, which mostly just maps to STK's implementation. <div><br></div><div>Spencer</div><div><br></div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Wed, May 23, 2018 at 9:54 AM, Juan Reyes <span dir="ltr"><<a href="mailto:juanigrp@gmail.com" target="_blank">juanigrp@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">Hi Michael, Mario,<br>
<br>
Thanks a lot for the links. Need to try these classes, they look cleaner.<br>
<br>
MidiFileIn inherits from STK also (sorry Gary but thanks!).<br>
<br>
Not so sure about MidiRW either. Looks like it has methods to open,<br>
close, read and write MIDI files. Seems to me that it is also used in<br>
conjunction with MidiMsg. I guess its usage might be like opening and<br>
manipulating audio files.<br>
<br>
Cheers,<br>
<br>
-- Juan<span class="m_4641563494260290737im m_4641563494260290737HOEnZb"><br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<br>
LiCK contains NoteOn/NoteOff/ControlChangeMi<wbr>diMsg classes that<br>
extend MidiMsg and hide some of the details.<br>
<br>
<a href="https://github.com/heuermh/lick/tree/master/lick/midi" target="_blank" rel="noreferrer">https://github.com/heuermh/lic<wbr>k/tree/master/lick/midi</a><br>
<br>
Here's an example of how they might be used<br>
<br>
<a href="https://github.com/heuermh/lick/blob/master/lick/midi/AnimoogMidi.ck#L104" target="_blank" rel="noreferrer">https://github.com/heuermh/lic<wbr>k/blob/master/lick/midi/Animoo<wbr>gMidi.ck#L104</a><br>
<br>
</blockquote></span><div class="m_4641563494260290737HOEnZb"><div class="m_4641563494260290737h5">
______________________________<wbr>_________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu" target="_blank">chuck-users@lists.cs.princeton<wbr>.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank" rel="noreferrer">https://lists.cs.princeton.edu<wbr>/mailman/listinfo/chuck-users</a><br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_4641563494260290737gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div style="font-family:arial;font-size:small"><div style="font-family:arial,sans-serif;font-size:12.8px"><font size="2">Spencer Salazar, PhD</font></div><div style="font-family:arial,sans-serif;font-size:12.8px"><font size="2">Special Faculty</font></div><div style="font-family:arial,sans-serif;font-size:12.8px"><font size="2">Music Technology: Interaction, Intelligence, and Design</font></div><div style="font-family:arial,sans-serif;font-size:12.8px"><font size="2">California Institute of the Arts</font></div><div style="font-family:arial,sans-serif;font-size:12.8px"><font size="2"><br></font></div><div style="font-family:arial,sans-serif;font-size:12.8px"><font size="2"><a href="mailto:ssalazar@calarts.edu" target="_blank">ssalazar@calarts.edu</a> | +1 831.277.4654</font></div><div style="font-family:arial,sans-serif;font-size:12.8px"><font size="2"><a href="https://spencersalazar.com/" target="_blank">https://spencersalazar.com</a> </font></div><div><font size="2"><br></font></div></div></div></div>
</font></span></div>
<br>______________________________<wbr>_________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.<wbr>princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank" rel="noreferrer">https://lists.cs.princeton.<wbr>edu/mailman/listinfo/chuck-<wbr>users</a><br>
<br></blockquote></div><br></div>