Hi

Is there a way to visually see in a text editor or a terminal the 1's and
0's that sample an audio file? Im interested because since understanding
coding the beauty of it is that you can use these same scripts on other
operating systems and hardware and some on and store the information on
paper in text of course but is it possible to do the same with a bit of
sampled audio? Rather than copying or moving  intangible audio files from
one place to another can it be done in text somehow? 

Thank you for reading 



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-sample-Binary-tp5734840.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I suppose one way to do it is to notate the sampled audio but that becomes a
little more complex when it really is specifically designed obscure 
'noises' you want to store physically...



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-sample-Binary-tp5734840p5734841.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

If you open a file with audacity and zoom in completely, you will see dots, which are the plots of each audio sample.
========================
Dr Victor Lazzarini
Senior Lecturer
NUI Maynooth, Ireland
victor dot lazzarini at nuim dot ie




On 30 Apr 2014, at 18:56, jpff@cs.bath.ac.uk wrote:

> emacs can do that, or in linux the command od does most of what you ask.
> 
> Not convinced it will help you though
> 
> Quoting fauveboy :
> 
>> Hi
>> 
>> Is there a way to visually see in a text editor or a terminal the 1's and
>> 0's that sample an audio file? Im interested because since understanding
>> coding the beauty of it is that you can use these same scripts on other
>> operating systems and hardware and some on and store the information on
>> paper in text of course but is it possible to do the same with a bit of
>> sampled audio? Rather than copying or moving  intangible audio files from
>> one place to another can it be done in text somehow?
>> 
>> Thank you for reading
>> 
>> 
>> 
>> --
>> View this message in context: http://csound.1045644.n5.nabble.com/Audio-sample-Binary-tp5734840.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>> 
>> 
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 
> 
> 
> 
> Send bugs reports to
>       https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 
> 



Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Okay Thank you. I'll go and investigate Hex editing...So what do people
usually use this form of coding for? Is it ridiculous to assume you can
manipulate the sound of the audio in this form or improve or reduce its
resolution?



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-sample-Binary-tp5734840p5734846.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Pretty much. Why would you want to? That's why we have tools like
Csound :) You can concentrate on the entire stream of samples one
block at a time.

On 1 May 2014 00:19, fauveboy  wrote:
> Okay Thank you. I'll go and investigate Hex editing...So what do people
> usually use this form of coding for? Is it ridiculous to assume you can
> manipulate the sound of the audio in this form or improve or reduce its
> resolution?
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Audio-sample-Binary-tp5734840p5734846.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

On Wed, 30 Apr 2014, fauveboy wrote:
> Okay Thank you. I'll go and investigate Hex editing...So what do people
> usually use this form of coding for?

Editing save files to cheat at video games.

> Is it ridiculous to assume you can
> manipulate the sound of the audio in this form or improve or reduce its
> resolution?

Yes.

The thing is, there are just too many numbers.  If you're working with
CD-quality audio, that'll be 352800 digits of hexadecimal per second of
audio (four times as many if you want to use binary instead of hex).  If
you can type ten keystrokes per second, assuming one keystroke per digit
edited and you require no additional time to think about what you're
doing, then you'll take 9.8 hours to edit one second of audio.  There are
very few audio editing tasks that can't be accomplished much more easily
by other techniques.

You would probably get better results by working at a more abstract level
- defining the editing operations you want to do in terms of arithmetic,
such as "multiply everything in this range by two" and then having the
computer actually do the sample-by-sample editing and sound generation, so
that you can operate on thousands or millions of samples with a single
command instead of one at a time.  And that's exactly what Csound is for.

I have read in a few books how it was very tedious and hard to produce
something musical out of a computer back in the day... Never really
understood the hard and tedious part fully... I think after this thread i do
now.



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-sample-Binary-tp5734840p5734853.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

thanks guys so just to clarify, its possible for me to see the raw data using
something like hex editor and for extra back up I could print the numbers
off if i loose the hardware and re type the raw data somehow and still have
the same sample, so its not all digital I could make it tangible and store
the information physical along with c scripts ?



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-sample-Binary-tp5734840p5734963.html
Sent from the Csound - General mailing list archive at Nabble.com.