Re: [Sdif-devel] eaSDIF - SWIG Python Bindings

[Axel R. <Axe...@ir...>]

On Tuesday 17 October 2006 11:46, Eduardo Moguillansky wrote:
> hi!
>
> I tried to compile the python bindings of eaSDIF but swig keeps
> reporting some errors. I tried it both in Linux (swig 1.3.24) and OSX
> (1.3.28). I was told that new versions of swig sometimes mess with c++
> but since I found two naming differences between the interface and the
> source files  I thought that maybe the interface files are not
> completely updated.

I fixed the names in the swig interface files.
For me it now compiles cleanly with swig version 1.3.21,
I've tested all wrappers : perl, python and java.

Let me know if you have success with a more recent=20
version of swig.

> Only to try if swig was working fine I compiled the perl bindings and
> they work perfectly in both versions of swig.
>
> As told, sdif 1TRC can be read in python through the Loris wrappers, bu=
t
> it would be great to have access to all the other formats used by
> supervp without having to convert to text first.
>
> thanks!
>
> Eduardo Moguillansky
>
> On Tue, 2006-10-17 at 10:05 +0200, Diemo Schwarz wrote:
> > Dear Eduardo,
> >
> > I'm also forwarding this mail to the sdi...@so... list
> > (subscribe at
>
> https://lists.sourceforge.net/lists/listinfo/sdif-devel),
>
> > where interesting development topics like these should go and where
>
> Axel
>
> > can read them who wrote eaSDIF and the swig python bindings.  I
>
> started
>
> > all this swig thing, but only took care of the perl bindings.
> >
> > What version of swig are you using?
> >
> > Eduardo Moguillansky wrote:
> > > dear Diemo,
> > >
> > > thank you very much for the information. I did get the CVS files an=
d
> > > found the python wrappers. They refuse to compile however. First 2
>
> files
>
> > > have changed name: sdifframe.hpp and sdifmatrix.hpp appear as
> > > sdif_frame.hpp and sdif_matrix.hpp. That changed, it starts
>
> compiling
>
> > > but throws an error when trying to compile the wrapped file. I
>
> wonder if
>
> > > some renaming has taken place since the interface files were done.
> > >
> > > I first compiled and installed easdif (and sdif) with no problems
>
> and
>
> > > they work fine.
> > >
> > > I did actually write a parser for 1TRC files from scratch just by
> > > following the specifications and reading the hex dumps.
> > > But for all the other formats, it seems at the moment more efficien=
t
>
> to
>
> > > convert to text and write a small parser.
> > >
> > > The whole idea is to be able to provide a scripting layer which is
> > > common to some of the softwares working with spectral data -supervp
>
> and
>
> > > loris at the moment (I'm trying to make it work both for mac and
>
> linux,
>
> > > so it is a pity that Pm2 does not seem to have a Linux version),
>
> spear
>
> > > for fast visualization of partial tracking with loris and Pm2. In
>
> this
>
> > > way it is possible to choose the best tool for each task -to do
> > > morphing, for instance, it is very useful to resort to Loris, for
> > > cross-synthesis supervp is much better -also because it is so fast.
>
> Also
>
> > > it is useful to do peak analysis in supervp and use the information
>
> to
>
> > > control the morphing envelope in Loris, and things of the sort.
> > >
> >  > Thanks!
> >  >
> >  > Eduardo
> >
> > That sounds great!  Your work would make for an interesting
>
> presentation
>
> > at the Ircam Forum Workshops.
> >
> > Cheers...
> >                                                               ...Diem=
o
> >
> > > I forgot, here is the compilation error:
> > >
> > > eaSDIF_wrap.cxx:1760: error: no type named =E2=80=98category=E2=80=99=
 in
> > > =E2=80=98struct swig::traits<std::pair<std::basic_string<char,
> > > std::char_traits<char>, std::allocator<char> >,
> > > std::basic_string<char, std::char_traits<char>, std::alloca
> > >
> > > On Tue, 2006-10-10 at 15:49 +0200, Diemo Schwarz wrote:
> > >> Hi Eduardo,
> > >>
> > >> look in the CVS sources of easdif.  (Now on
> > >> http://sourceforge.net/projects/sdif/!)  I think the java, perl
>
> and
>
> > >> python bindings are not part of the distribution, yet, because
>
> nobody
>
> > >> asked for them up to now.
> > >>
> > >> I'm forwarding this question to the sdif mailing list for more
>
> details...
>
> > >>                                                            ...Diem=
o
> > >>
> > >>
> > >> email message attachment (eaSDIF - Python bindings)
> > >>
> > >>> -------- Forwarded Message --------
> > >>> From: Eduardo Moguillansky <mog...@gm...>
> > >>> To: Die...@ir...
> > >>> Subject: eaSDIF - Python bindings
> > >>> Date: Tue, 10 Oct 2006 14:36:49 +0200

--=20
Axel Roebel   =20
IRCAM Analysis/Synthesis Team
Phone: ++33-1-4478 4845 | Fax: ++33-1-4478 1540