Thread: Re: [Sdif-devel] [Fwd: eaSDIF - Python bindings]

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

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,
>=20
> thank you very much for the information. I did get the CVS files and
> found the python wrappers. They refuse to compile however. First 2 file=
s
> 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 i=
f
> some renaming has taken place since the interface files were done.
>=20
> I first compiled and installed easdif (and sdif) with no problems and
> they work fine.=20
>=20
> 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 efficient to
> convert to text and write a small parser.
>=20
> 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. Als=
o
> 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...
								...Diemo

> I forgot, here is the compilation error:
>=20
> eaSDIF_wrap.cxx:1760: error: no type named =E2=80=98category=E2=80=99 i=
n=20
> =E2=80=98struct swig::traits<std::pair<std::basic_string<char,=20
> std::char_traits<char>, std::allocator<char> >,=20
> std::basic_string<char, std::char_traits<char>, std::alloca
>=20
> On Tue, 2006-10-10 at 15:49 +0200, Diemo Schwarz wrote:
>> Hi Eduardo,
>>
>> look in the CVS sources of easdif.  (Now on=20
>> http://sourceforge.net/projects/sdif/!)  I think the java, perl and=20
>> python bindings are not part of the distribution, yet, because nobody=20
>> asked for them up to now.
>>
>> I'm forwarding this question to the sdif mailing list for more details=
...
>> 								...Diemo
>>
>>
>> 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