> Somewhere on my long do-list is an idea to make an addition to soundfiler
> to read binary chanracters into an array.

+1

@Mario: in the meantime you can use [mrpeach/binfile] to read arbitrary binary data.

> Gesendet: Montag, 21. Januar 2019 um 00:34 Uhr
> Von: "Miller Puckette" <msp@ucsd.edu>
> An: "Mario Buoninfante" <mario.buoninfante@gmail.com>
> Cc: pd-list <pd-list@lists.iem.at>
> Betreff: Re: [PD] [text] issue reading SysEx files
>
> The trouble is probably the presence of a '{' character in the file.
> But there will be other problems - ASCII NULL characters will simply
> terminate the string early, and semicolons, spaces, and commas will
> confuse things.
>
> Somewhere on my long do-list is an idea to make an addition to soundfiler
> to read binary chanracters into an array.
>
> cheers
> Miller
>
> On Fri, Jan 18, 2019 at 04:39:04PM +0000, Mario Buoninfante wrote:
> > Hi,
> >
> > I've been trying to read SysEx files using [text], and I noticed that the
> > loaded file end up being corrupted in a way with bits and bops missing.
> > Also trying to manually copy and paste part of the file (from Atom text
> > editor) I'm not able to copy the entire file, there's always something
> > missing (ie select all the file in Atom, copy and paste in [text]).
> > When loading the file I've got no error, but then when I open the [text]
> > window, this is returned on the console:
> >
> > (Tcl) UNHANDLED ERROR: extra characters after close-brace
> >     while executing
> > "pdtk_textwindow_append .x100617310 {d 0 iM @?, f h I R kQ, [ ???? ), Y Q Y1
> > -" ( , XFN `  8 ) 6{` )  ) ;
> > }
> > pdtk_textwindow_append .x1006173..."
> >     ("uplevel" body line 39)
> >     invoked from within
> > "uplevel #0 $docmds
> >
> > I know, it's a kind of a weird thing trying to read SysEx files in this way
> > and probably it's just me trying to do something with the wrong tool.
> > But weirdly enough the sequences of characters I cannot copy and paste from
> > Atom, can then be directly typed in the [text] window.
> > I suspect this has to do with the character encoding.
> > Does anyone know why [text] behave this way?
> >
> > Cheers,
> > Mario
>
> > _______________________________________________
> > Pd-list@lists.iem.at mailing list
> > UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
>
>
>
>
> _______________________________________________
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
>



_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list