it should be straightforward just clone it and then use the linux build script
in grace/Builds/ directory. here is the list of juce dependencies for linux:
https://forum.juce.com/t/list-of-juce-dependencies-under-linux/15121/33
I did not have any problems building either sndlib or grace on my
Thanks, that worked!
(Now to go wrestle with juce...)
On Tue, Mar 3, 2020 at 5:35 PM Taube, Heinrich K wrote:
> yes i hit that too, i thought i sent the edited file to bil but i see i
> forgot.
> you can edit the premake.lua file replace that call with either true or
> false for your machine
yes i hit that too, i thought i sent the edited file to bil but i see i forgot.
you can edit the premake.lua file replace that call with either true or false
for your machine type. there might be some lua call that will return that
value. im not sure why its not in premake.
On Mar 3, 2020, at
im working on midi in/out right now. im going to replace the old ports with the
standard juce audio device manager, wichc lets you set multiple midi inputs
(and outputs i assume)
> On Mar 3, 2020, at 5:37 PM, Neil Baylis wrote:
>
> I have a project that needs to send midi to more than 40
How to proceed?
Building this on Ubuntu 19.10, I end with:
premake4 --with-g++
/home/forrest/parent/sndlib/premake4.lua:95: attempt to call field
'is64bit' (a nil value)
"lua" in this case seems to be lua 5.3.3
(?)
Forrest Curo
San Diego
On Tue, Mar 3, 2020 at 9:21 AM Taube, Heinrich K
I have a project that needs to send midi to more than 40 instruments at the
same time. Is there a way to specify more than one midi bus for output in
CM/Grace? The dialog for selecting midi bus seems to only allow one at a
time.
I've been able to make this work with Pure Data, but was hoping to
Thank you Orm and Ric.
I'm sure I'll have success with that tonight, as that all makes great sense.
Fomus is good to have around.
On Tue, 2020-03-03 at 18:22 +0100, Orm Finnendahl wrote:
> Hi Adam,
>
> sorry, I was unaware of the fomus dependency in cm. I will get rid of
> it as it is
Hi Adam,
I removed the fomus dependency from cm. Download cm from the github
repository, put the folder into ~/quicklisp/local-projects and issue
(ql:quickload "cm") followed by (cm)
That should get you into the vanilla cm package.
Best,
Orm
Am Dienstag, den 03. März 2020 um 14:48:48 Uhr
Hi Adam,
sorry, I was unaware of the fomus dependency in cm. I will get rid of
it as it is unneccessary. To get it running in the meantime, please
just go ahead and also clone "fomus" and "cm-fomus" from the same
github repo (they are fairly small):
https://github.com/ormf/cm-fomus
Ive moved the Grace repo to github where you can now download the sources. It
seems to build fine on MacOS and Linux, but I haven’t done tons of testing yet
so there are probably still some issues to fix. Windows doesn't work yet — I
can compile and link everything, the app boots but I dont
You should be able comment out the fomus loading, that was just an optional
package.
> On Mar 3, 2020, at 4:18 AM, adam wrote:
>
>
> Forgive me for asking, but how would I load and run the ../ormf/cm package?
>
> I have tried several approaches, including even /bin/cm.sh, with no success.
Forgive me for asking, but how would I load and run the ../ormf/cm package?
I have tried several approaches, including even /bin/cm.sh, with no success.
Am on Linux with a fresh and working Emacs Slime sbcl setup.
Step one may be to save a working image, to thereafter load as slime's
lisp
12 matches
Mail list logo