Csound Csound-dev Csound-tekno Search About

pvsfwrite and 0dbfs

Date2016-03-02 17:29
FromIain McCurdy
Subjectpvsfwrite and 0dbfs
The appended csd analyses fox.wav and writes a file fox.pvx using pvsfwrite in instr 1. It then read and resynthesises the audio in instr 2. If 0dbfs=1 this performs as expected but if 0bdfs is removed - so it defaults to 32768 - the resynthesised playback in instr 2 is hugely distorted. Obviously an amps mismatch. pvsfread and pvsdiskin give the same results. I am just trying to decide where the problem lies (pvsfwrite I think) and if it is something that should be fixed. 

<CsoundSynthesizer>

<CsOptions>
-odac -dm0
</CsOptions>

<CsInstruments>

sr              =       44100
ksmps           =       64
nchnls          =       1
0dbfs           =       1

#define SoundName #fox#

instr   1
 p3     filelen "$SoundName..wav"
 asig   diskin  "$SoundName..wav"
 fsig   pvsanal asig, 1024, 256, 1024, 0
        pvsfwrite fsig, "$SoundName..pvx"
        out     asig
        event_i "i",2,p3+0.5,p3
endin

instr   2
 p3     filelen         "$SoundName..pvx"
 kptr   linseg          0,p3,p3
 ;fsig  pvsdiskin       "$SoundName..pvx",1,1
 fsig   pvsfread        kptr, "$SoundName..pvx"
 asig   pvsynth         fsig
        out             asig
endin


</CsInstruments>

<CsScore>
i 1 0 0.1 ; read file and write analyse
;i 2 5 0.1 ; read analysis and resynthesise
f 0 20
</CsScore>

Date2016-03-03 10:38
FromRichard Dobson
SubjectRe: pvsfwrite and 0dbfs
Obviously as the author I should investigate this, but am away from computer all day, as also yesterday, so I am kind of hoping someone else can step in. Victor?

Richard Dobson

Sent from my iPhone

On 2 Mar 2016, at 17:29, Iain McCurdy <i_mccurdy@HOTMAIL.COM> wrote:

The appended csd analyses fox.wav and writes a file fox.pvx using pvsfwrite in instr 1. It then read and resynthesises the audio in instr 2. If 0dbfs=1 this performs as expected but if 0bdfs is removed - so it defaults to 32768 - the resynthesised playback in instr 2 is hugely distorted. Obviously an amps mismatch. pvsfread and pvsdiskin give the same results. I am just trying to decide where the problem lies (pvsfwrite I think) and if it is something that should be fixed. 

<CsoundSynthesizer>

<CsOptions>
-odac -dm0
</CsOptions>

<CsInstruments>

sr              =       44100
ksmps           =       64
nchnls          =       1
0dbfs           =       1

#define SoundName #fox#

instr   1
 p3     filelen "$SoundName..wav"
 asig   diskin  "$SoundName..wav"
 fsig   pvsanal asig, 1024, 256, 1024, 0
        pvsfwrite fsig, "$SoundName..pvx"
        out     asig
        event_i "i",2,p3+0.5,p3
endin

instr   2
 p3     filelen         "$SoundName..pvx"
 kptr   linseg          0,p3,p3
 ;fsig  pvsdiskin       "$SoundName..pvx",1,1
 fsig   pvsfread        kptr, "$SoundName..pvx"
 asig   pvsynth         fsig
        out             asig
endin


</CsInstruments>

<CsScore>
i 1 0 0.1 ; read file and write analyse
;i 2 5 0.1 ; read analysis and resynthesise
f 0 20
</CsScore>
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2016-03-03 11:00
FromVictor Lazzarini
SubjectRe: pvsfwrite and 0dbfs
 I think the ball is in my court, the problem most likely to be with pvsfwrite. Can a ticket be open in github?

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 3 Mar 2016, at 10:38, Richard Dobson <richarddobson@BLUEYONDER.CO.UK> wrote:

Obviously as the author I should investigate this, but am away from computer all day, as also yesterday, so I am kind of hoping someone else can step in. Victor?

Richard Dobson

Sent from my iPhone

On 2 Mar 2016, at 17:29, Iain McCurdy <i_mccurdy@HOTMAIL.COM> wrote:

The appended csd analyses fox.wav and writes a file fox.pvx using pvsfwrite in instr 1. It then read and resynthesises the audio in instr 2. If 0dbfs=1 this performs as expected but if 0bdfs is removed - so it defaults to 32768 - the resynthesised playback in instr 2 is hugely distorted. Obviously an amps mismatch. pvsfread and pvsdiskin give the same results. I am just trying to decide where the problem lies (pvsfwrite I think) and if it is something that should be fixed. 

<CsoundSynthesizer>

<CsOptions>
-odac -dm0
</CsOptions>

<CsInstruments>

sr              =       44100
ksmps           =       64
nchnls          =       1
0dbfs           =       1

#define SoundName #fox#

instr   1
 p3     filelen "$SoundName..wav"
 asig   diskin  "$SoundName..wav"
 fsig   pvsanal asig, 1024, 256, 1024, 0
        pvsfwrite fsig, "$SoundName..pvx"
        out     asig
        event_i "i",2,p3+0.5,p3
endin

instr   2
 p3     filelen         "$SoundName..pvx"
 kptr   linseg          0,p3,p3
 ;fsig  pvsdiskin       "$SoundName..pvx",1,1
 fsig   pvsfread        kptr, "$SoundName..pvx"
 asig   pvsynth         fsig
        out             asig
endin


</CsInstruments>

<CsScore>
i 1 0 0.1 ; read file and write analyse
;i 2 5 0.1 ; read analysis and resynthesise
f 0 20
</CsScore>
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2016-03-03 11:15
FromIain McCurdy
SubjectRe: pvsfwrite and 0dbfs
Done.


Date: Thu, 3 Mar 2016 11:00:12 +0000
From: Victor.Lazzarini@NUIM.IE
Subject: Re: [Csnd] pvsfwrite and 0dbfs
To: CSOUND@LISTSERV.HEANET.IE

 I think the ball is in my court, the problem most likely to be with pvsfwrite. Can a ticket be open in github?

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 3 Mar 2016, at 10:38, Richard Dobson <richarddobson@BLUEYONDER.CO.UK> wrote:

Obviously as the author I should investigate this, but am away from computer all day, as also yesterday, so I am kind of hoping someone else can step in. Victor?

Richard Dobson

Sent from my iPhone

On 2 Mar 2016, at 17:29, Iain McCurdy <i_mccurdy@HOTMAIL.COM> wrote:

The appended csd analyses fox.wav and writes a file fox.pvx using pvsfwrite in instr 1. It then read and resynthesises the audio in instr 2. If 0dbfs=1 this performs as expected but if 0bdfs is removed - so it defaults to 32768 - the resynthesised playback in instr 2 is hugely distorted. Obviously an amps mismatch. pvsfread and pvsdiskin give the same results. I am just trying to decide where the problem lies (pvsfwrite I think) and if it is something that should be fixed. 

<CsoundSynthesizer>

<CsOptions>
-odac -dm0
</CsOptions>

<CsInstruments>

sr              =       44100
ksmps           =       64
nchnls          =       1
0dbfs           =       1

#define SoundName #fox#

instr   1
 p3     filelen "$SoundName..wav"
 asig   diskin  "$SoundName..wav"
 fsig   pvsanal asig, 1024, 256, 1024, 0
        pvsfwrite fsig, "$SoundName..pvx"
        out     asig
        event_i "i",2,p3+0.5,p3
endin

instr   2
 p3     filelen         "$SoundName..pvx"
 kptr   linseg          0,p3,p3
 ;fsig  pvsdiskin       "$SoundName..pvx",1,1
 fsig   pvsfread        kptr, "$SoundName..pvx"
 asig   pvsynth         fsig
        out             asig
endin


</CsInstruments>

<CsScore>
i 1 0 0.1 ; read file and write analyse
;i 2 5 0.1 ; read analysis and resynthesise
f 0 20
</CsScore>
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here