Hello list,
I recently tried out petri-foo and I like it enough to care about it in
the form of bug reports.
I don't know how to contact the developers though.
The website http://petri-foo.sourceforge.net/ says last release 2012,
the github repository is switched to read-only.
Did I miss the active development place somehow? Fork of a fork?
-hgn
Daniel Swärd:
>
> Hi all.
>
> Just found out that one of the Bitwig devs has released an older (commercial)
> project of his as open source: https://github.com/kurasu/surge
>
> Doesn't yet build on Linux, but quoting from the github page:
> "It currently only builds on windows, but getting it to build on macOS again &
> Linux should be doable with moderate effort."
>
> How about we get it building at the next Berlin LAU meeting?
>
I took a quick procrastination-shot at it:
https://github.com/kmatheussen/surge
(first copy various VST directories into the build)
premake5 gmake
make surge-vst2 verbose=1 -j8
ldd -r target/vst2/Debug/Surge-Debug.so
undefined symbol: _ZN6VSTGUI8soHandleE (target/vst2/Debug/Surge-Debug.so)
undefined symbol:
_ZN3Gtk11FileChooser18set_current_folderERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: _ZNK3Gdk11DragContext12list_targetsB5cxx11Ev
(target/vst2/Debug/Surge-Debug.so)
undefined symbol:
_ZN4Glib7ustringC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(target/vst2/Debug/Surge-Debug.so)
undefined symbol:
_ZN12SurgeStorage11load_wt_wavENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEP9Wavetable
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: __cpuid (target/vst2/Debug/Surge-Debug.so)
undefined symbol:
_ZN3Gtk11CssProvider14load_from_dataERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: _Z19spawn_miniedit_textPci
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: _ZNK3Gtk11FileChooser13get_filenamesB5cxx11Ev
(target/vst2/Debug/Surge-Debug.so)
So, a little bit work left, but maybe it's enough to link with a newer
version of
gtkmm than I did.
Don't know how well VSTGUI works on linux though. Using
gtkmm as the underlying GUI to implement VSTGUI on top of
seems worrying.
Hi all.
Just found out that one of the Bitwig devs has released an older (commercial)
project of his as open source: https://github.com/kurasu/surge
Doesn't yet build on Linux, but quoting from the github page:
"It currently only builds on windows, but getting it to build on macOS again &
Linux should be doable with moderate effort."
How about we get it building at the next Berlin LAU meeting?
Cheers
/Daniel
Apart from the new list of helpers, there is little visible change for most
users, but the command line has now been greatly extended.
Full details are in doc/Yoshimi_1.5.9_features.txt
Also, there have been significant changes in the underlying code. These were
always planned, but maybe not reported and explained as well as they could have
been.
More info is in dev_notes/Selection_Structure.txt
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Amongst many other things this will have a new child of the 'About' window.
This will consist of an acknowledgement of all the people who've helped Yoshimi
in some way. If anyone particularly *doesn't* want their name on it please let
me know. Then again, if there are missing names I'd like to know about that too!
This list (Yoshimi_Helpers) has only existed in the source files since
V 1.5.1 and is my best attempt at finding everybody.
Release is planned for later this month.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Hi all,
Sorry to bother you again with this. I’m running into the same problem again as before (see the latter part of the [LAD] jackd not using jackdrc… thread).
And apparently my last fix involved some magic rather than replicable logic… :-( i.e. the problem seems to have disappeared on that system, without knowing exactly why)
Now I am installing my jack client again on another fresh install of ubuntu 17.04. and a get the same error.
I have installed jackd1, to be exact, these packages are current.
jackd/artful,artful,now 5 all [installed,automatic]
jackd1/artful,now 1:0.125.0-2 amd64 [installed]
jackd1-firewire/artful,now 1:0.125.0-2 amd64 [installed,automatic]
libjack0/artful,now 1:0.125.0-2 amd64 [installed]
qjackctl/artful,now 0.4.5-1ubuntu1 amd64 [installed,automatic]
when I start my client jackd is automatically started but i get the error:
connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file or directory)
By browsing the jack sources i found the message seems to come from libjack/client.c in server_connect()
peeking into the /dev/shm directory it seems /dev/shm/jack-0/default/jack_0 is briefly created,but disappears again, presumably just before the client is able to connect.
I have been breaking my head over this, but I really have no clue why this is happening, especially as this has worked fine in the past.
I would really like to know what could possibly cause this error and how to fix it.
thanks,
fokke
>From the LAU list:
Am 08.09.18 um 17:23 schrieb Len Ovens:
> I would be willing to help with a govering body if there are others so
> inclined.
I'd definitely be interested in helping OSC staying relevant.
I've dabled with different OSC-to-X bridges in the past. [1] [2] [3]. My
main interest is controlling applications, which talk to some MIDI
device, running on a desktop or Raspi or similar, from another
application on an Android device, since MIDI and USB-OTG support on
Android devices is still somewhat a matter of luck.
The protocols I've seen so far, which embed MIDI in OSC are often too
simplistic. If I can't transmit Sysex, for example, it's no use to me.
And what is the advantage of the verbose commands MidiOSC/midioscar use
over just using the MIDI data type OSC provides?
Also, the MIDI specification has had a few additions in the past years
and a OSC-MIDI protocol hould make sure to support those as well.
Chris
[1] https://github.com/SpotlightKid/osc2rtmidi
[2] https://github.com/SpotlightKid/osc2mqtt
[3] https://github.com/SpotlightKid/touchosc2midi