[visurfacereader] Re: Surface reader and digi003
- From: "Tim Burgess" <tim@xxxxxxxxxxxxx>
- To: <visurfacereader@xxxxxxxxxxxxx>
- Date: Wed, 8 Jan 2014 18:00:03 -0000
Pete,
The problems I'm experiencing on the Mac are caused by a combination of the
following factors:
1 - Apple dropped support for the LLVM-GCC compilers at V4.2 - they now
prefer you to use the alternative clang compiler for c/c++/Objective-C
development;
2 - One of the libraries I need to use still has some issues when built
using clang. In fact, it's not even as simple as this - the version of this
library available at the start of the SurfaceReader project would not build
using clang - the latest version does, but has significant changes that
would mean a serious recode of the speech provision, which is one of the
most complex parts of SurfaceReader, so we're sticking with the older
version of the library;
3 - Another of the libraries used has a documented problem when built using
GCC 4.2. The only fix is to use either clang or a later version of GCC.
Given what I've written above, the obvious solution is to update GCC to a
later version and this is what I was advised to do;
4 - It took several attempts to build GCC 4.8.2 with all of the correct
options for SurfaceReader and each attempt took most of a day in
configuration and build time;
5 - Having successfully built GCC 4.8.2, it took a lot of time to get all of
my 3rd-party libraries to build correctly with the new build system;
6 - In order to get Xcode to use the new compiler, you have to write an
Xcode plug-in that defines what build options the compiler will accept, as
different versions of the same compiler don't necessarily support the same
command-line options.
The fix I referenced in my earlier posting yielded a small success, but then
revealed a problem with an unsupported command-line option for GCC 4.8.2, so
I've now got to research how to modify my custom compiler plug-in to drop
the use of this flag.
Hopefully this very abbreviated narrative gives you a flavour of the amount
of hassle generating the Mac build has caused - I'm not battling bugs in the
SurfaceReader code, just trying to get all of the required build tools to
play nicely together. The version of SurfaceReader that I issued to
everybody quite a while ago did successfully build on the Mac, but fixing
the reported crashing and memory leak issues required significant changes
that, unfortunately, brought into play new library components that were
rather more picky about what compilers they'll work with, hence the very
long delay as I spend whole days researching work-arounds and fixes.
Best wishes.
Tim Burgess
-----Original Message-----
From: visurfacereader-bounce@xxxxxxxxxxxxx
[mailto:visurfacereader-bounce@xxxxxxxxxxxxx] On Behalf Of
ptorpey00@xxxxxxxxx
Sent: 08 January 2014 13:47
To: visurfacereader@xxxxxxxxxxxxx
Subject: [visurfacereader] Re: Surface reader and digi003
Wow - Sounds like developing this program for the MAC has been a real
frustration and roadblock for making progress on the Windows version since
you seem to be trying to keep them in sync. Just curious, is development on
the MAC more difficult in general or were the third-party libraries
available for the MAC just broken?
Anyway, good luck. Don't pull all of your hair out!
--Pete (freezing in the northeastern U.S.)
-----Original Message-----
From: visurfacereader-bounce@xxxxxxxxxxxxx
[mailto:visurfacereader-bounce@xxxxxxxxxxxxx] On Behalf Of Tim Burgess
Sent: Wednesday, January 08, 2014 8:21 AM
To: visurfacereader@xxxxxxxxxxxxx
Subject: [visurfacereader] Re: Surface reader and digi003
Pete,
I was hoping to have a joint release out before Christmas, but some family
issues held me up, together with yet another library problem for the Mac.
However, I've literally just received a suggestion to fix the library issue,
so I'm going to give it a try and I'll be in a better position to make some
predictions.
Best wishes.
Tim Burgess
-----Original Message-----
From: visurfacereader-bounce@xxxxxxxxxxxxx
[mailto:visurfacereader-bounce@xxxxxxxxxxxxx] On Behalf Of
ptorpey00@xxxxxxxxx
Sent: 08 January 2014 13:15
To: visurfacereader@xxxxxxxxxxxxx
Subject: [visurfacereader] Re: Surface reader and digi003
Tim,
Just wondering if there is a status on the next release. Sounded like you
were getting close to having a new version with some bug fixes before the
holidays.
Thanks and hope all goes well for you in the new year.
--Pete
-----Original Message-----
From: visurfacereader-bounce@xxxxxxxxxxxxx
[mailto:visurfacereader-bounce@xxxxxxxxxxxxx] On Behalf Of Tim Burgess
Sent: Wednesday, January 08, 2014 6:57 AM
To: visurfacereader@xxxxxxxxxxxxx
Subject: [visurfacereader] Re: Surface reader and digi003
Nick,
If you set up a protocol definition for the device it'll give you some
feedback. Exactly what feedback you get will be down to what the device is
capable of - if it's one-way communication with your software then the best
you'll manage will be the ability to label controls and announce the MIDI
value that they're transmitting. If it's two-way communication then there's
the possibility of getting output more like you've experienced with your
BCF/Mackie. You'll need to study the MIDI documentation for the device and
the Advanced Configuration section of the SurfaceReader manual to figure out
what's possible.
Best wishes.
Tim Burgess
-----Original Message-----
From: visurfacereader-bounce@xxxxxxxxxxxxx
[mailto:visurfacereader-bounce@xxxxxxxxxxxxx] On Behalf Of Nick Daniels
Sent: 07 January 2014 18:13
To: visurfacereader@xxxxxxxxxxxxx
Subject: [visurfacereader] Re: Surface reader and digi003
oh yes and 1 other thing to add hear.
i've aquired a korg nano controll surface unit around christmas time. can it
be worked with surface reader?
Other related posts:
