POV-Ray : Newsgroups : povray.advanced-users : Binary file I/O? Server Time
29 Jul 2024 06:23:46 EDT (-0400)
  Binary file I/O? (Message 3 to 12 of 12)  
<<< Previous 2 Messages Goto Initial 10 Messages
From: Andrew Coppin
Subject: Re: Binary file I/O?
Date: 13 Apr 2003 10:00:54
Message: <3e996d96@news.povray.org>
> You're a sick, sick puppy.

Thankyou. I already know that...

> On the other hand, if POV could read binary files, you could use it to
> make a rendering OF the wav file...

Oh, I intend to do that too ;-)

Andrew.


Post a reply to this message

From: Apache
Subject: Re: Binary file I/O?
Date: 13 Apr 2003 17:54:24
Message: <3e99dc90@news.povray.org>
There are those people who manage to write synthesizer-like stuff in flash
(.swf) applets.


Post a reply to this message

From: Thomas Willhalm
Subject: Re: Binary file I/O?
Date: 17 Apr 2003 09:34:01
Message: <3e9ead49@news.povray.org>
Andrew Coppin wrote:

> Just a quick one... Would it be possible to get POV-Ray to read/write
> binary files? (As opposed to plain text?)
> 
> Why am I asking? Well, not content with making a microprocessor emulator
> with the SDL, I'm now thinking about making a sound synthesiser, so I want
> to be able to write .WAV files 

What about using an ASCII sound format. According to the manual, sox
(http://sox.sourceforge.net/) can read and write DAT files, which are
a text representation of audio data. This is perhaps easier than
discussing this binary data subject again.

I hope this helps
Thomas


Post a reply to this message

From: Andrew Coppin
Subject: Re: Binary file I/O?
Date: 17 Apr 2003 10:03:07
Message: <3e9eb41b@news.povray.org>
That's a fine idea... Thanx!

Andrew.


Post a reply to this message

From: nospam
Subject: Re: Binary file I/O?
Date: 17 Apr 2003 23:17:33
Message: <3e9f45a9.10506312@localhost>
On Sun, 13 Apr 2003 09:46:43 +0100, "Andrew Coppin"
<orp### [at] btinternetcom> wrote:

>Just a quick one... Would it be possible to get POV-Ray to read/write binary
>files? (As opposed to plain text?)
>
>I think I remember seeing  character <==> ASCII code conversion functions
>somewhere in the docs... POV-Ray doesn't do anything weird to the ASCII
>codes you ask it to write does it? (Like LF -> CR/LF conversions and stuff.)
>

Have povray write the bianry data as a uuencoded txt file.  Then
run through a separate uudecoder after thr render.

>Why am I asking? Well, not content with making a microprocessor emulator
>with the SDL, I'm now thinking about making a sound synthesiser, so I want
>to be able to write .WAV files (which are of course binary!) I'm planning to
>make an animation, and I want POV-Ray to synthesise the soundtrack...
>
>Thanks.
>Andrew.
>

I want to do this as well.  It's fun to use POV-Ray for completely
non-graphical tasks.  I even wrote a program to auto-generate
game levels in POV-RAy.  :)

It's fun to write .bat files from POV-Ray.  :) :) :)


Post a reply to this message

From: Andrew Coppin
Subject: Re: Binary file I/O?
Date: 21 Apr 2003 16:20:13
Message: <3ea4527d$1@news.povray.org>
> Have povray write the bianry data as a uuencoded txt file.  Then
> run through a separate uudecoder after thr render.

Hey, now that's using your noodle...

> I want to do this as well.  It's fun to use POV-Ray for completely
> non-graphical tasks.  I even wrote a program to auto-generate
> game levels in POV-RAy.  :)
>
> It's fun to write .bat files from POV-Ray.  :) :) :)

Mmm... and I thought I was crazy for writing DOS scripts that write DOS
scripts...

Andrew.


Post a reply to this message

From: Andrew Coppin
Subject: Re: Binary file I/O?
Date: 23 Apr 2003 13:57:50
Message: <3ea6d41e$1@news.povray.org>
> Have povray write the bianry data as a uuencoded txt file.  Then
> run through a separate uudecoder after thr render.

Actually... can anyone name a utility to do the decode? (Someone sent me
some email the other day, but somehow the attachment is now BASE-64 encoded
and the mailler thinks it's normal text, not an encoded attachment. Bloomin
daft thing...) I know various email clients do it as part of showing you
your email, but is there any utility which will do it for arbitary files?

Thanks.
Andrew.

PS. Is uuencode and BASE-64 the same or different?


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Binary file I/O?
Date: 24 Apr 2003 03:51:48
Message: <3ea79794$1@news.povray.org>
In article <3ea6d41e$1@news.povray.org> , "Andrew Coppin" 
<orp### [at] btinternetcom> wrote:

> PS. Is uuencode and BASE-64 the same or different?

Different.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Andrew Coppin
Subject: Re: Binary file I/O?
Date: 24 Apr 2003 15:41:33
Message: <3ea83ded$1@news.povray.org>
> > PS. Is uuencode and BASE-64 the same or different?
>
> Different.
>
>     Thorsten

Thanks.

Don't expect anyone to eloborate on this news group, but any chance of a
link to a suitable description? (I already know BASE-64, it's the other one
I'd like a link for.)

Becuase I'm curiouse.
Andrew.


Post a reply to this message

From: Warp
Subject: Re: Binary file I/O?
Date: 24 Apr 2003 20:06:57
Message: <3ea87c21@news.povray.org>
Andrew Coppin <orp### [at] btinternetcom> wrote:
> (I already know BASE-64, it's the other one
> I'd like a link for.)

  From the uuencode man page:

     The standard output is a text file (encoded in the character
     set of the current locale) that begins with the line:

          "begin%s%s\n", <mode>, decode_pathname

     and ends with the line:

          end\n

     In both cases, the lines have no preceding or trailing blank
     characters.

     The algorithm that is used for lines in  between  begin  and
     end  takes  three octets as input and writes four characters
     of output by splitting the input at six-bit  intervals  into
     four  octets,  containing  data  in the lower six bits only.
     These octets are converted to characters by adding  a  value
     of  0x20  to  each octet, so that each octet is in the range
     0x20-0x5f, and then it is assumed to represent  a  printable
     character. It then will be translated into the corresponding
     character codes for  the  codeset  in  use  in  the  current
     locale. (For example, the octet 0x41, representing A , would
     be translated to A in the current codeset, such as  0xc1  if
     it were EBCDIC.)

     Where the bits of two octets are combined, the least  signi-
     ficant bits of the first octet are shifted left and combined
     with the most significant bits of the second  octet  shifted
     right.  Thus the three octets A, B, C are converted into the
     four octets:

          0x20 + (( A >> 2                          ) & 0x3F)
          0x20 + (((A << 4)  ((B >> 4) & 0xF)) & 0x3F)
          0x20 + (((B << 2)  ((C >> 6) & 0x3)) & 0x3F)
          0x20 + (( C                                 ) & 0x3F)

     These octets are then translated into  the  local  character
     set.

     Each encoded line contains a length character, equal to  the
     number  of  characters to be decoded plus 0x20 translated to
     the local character set as described above, followed by  the
     encoded  characters.   The  maximum  number  of octets to be
     encoded on each line is 45.


-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -


Post a reply to this message

<<< Previous 2 Messages Goto Initial 10 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.