spsmodel.m
Go to the documentation of this file.
1 function [y,yh,ys] = spsmodel(x,fs,w,N,t,maxnS,stocf)
2 %=> analysis/synthesis of a sound using the sinusoidal harmonic model
3 % x: input sound, fs: sampling rate, w: analysis window (odd size),
4 % N: FFT size (minimum 512), t: threshold in negative dB,
5 % maxnS: maximum number of sinusoids,
6 % stocf: decimation factor of mag spectrum for stochastic analysis
7 % y: output sound, yh: harmonic component, ys: stochastic component
8 M = length(w); % analysis window size
9 Ns = 1024; % FFT size for synthesis
10 H = 256; % hop size for analysis and synthesis
11 N2 = N/2+1; % half-size of spectrum
12 soundlength = length(x); % length of input sound array
13 hNs = Ns/2; % half synthesis window size
14 hM = (M-1)/2; % half analysis window size
15 pin = max(N2,1+hM) % initialize sound pointer to middle of analysis window
17 fftbuffer = zeros(N,1); % initialize buffer for FFT
18 yh = zeros(soundlength+Ns/2,1); % output sine component
19 ys = zeros(soundlength+Ns/2,1); % output residual component
20 w = w/sum(w); % normalize analysis window
21 sw = zeros(Ns,1);
22 ow = triang(2*H-1); % overlapping window
23 ovidx = Ns/2+1-H+1:Ns/2+H; % overlap indexes
24 sw(ovidx) = ow(1:2*H-1);
25 bh = blackmanharris(Ns); % synthesis window
26 bh = bh ./ sum(bh); % normalize synthesis window
27 wr = bh; % window for residual
28 sw(ovidx) = sw(ovidx) ./ bh(ovidx);
29 sws = H*hanning(Ns)/2; % synthesis window for stochastic
30 lastysloc = zeros(maxnS,1); % initialize synthesis harmonic locations
31 ysphase = 2*pi*rand(maxnS,1); % initialize synthesis harmonic phases
32 fridx = 0;
33 
34 
35 
36 
37 
38 while pin<pend
39  %-----analysis-----%
40  xw = x(pin-hM:pin+hM).*w(1:M); % window the input sound
42  fftbuffer(1:(M+1)/2) = xw((M+1)/2:M); % zero-phase window in fftbuffer
43  fftbuffer(N-(M-1)/2+1:N) = xw(1:(M-1)/2);
44  X = fft(fftbuffer); % compute the FFT
45  mX = 20*log10(abs(X(1:N2))); % magnitude spectrum
46  pX = unwrap(angle(X(1:N/2+1))); % unwrapped phase spectrum
47  ploc = 1 + find((mX(2:N2-1)>t) .* (mX(2:N2-1)>mX(3:N2)) ...
48  .* (mX(2:N2-1)>mX(1:N2-2))); % find peaks
49  [ploc,pmag,pphase] = peakinterp(mX,pX,ploc); % refine peak values
50  % sort by magnitude
51  [smag,I] = sort(pmag(:),1,'descend');
52  nS = min(maxnS,length(find(smag>t)));
53  sloc = ploc(I(1:nS));
54  sphase = pphase(I(1:nS));
55  if (fridx==0)
56  % update last frame data for first frame
57  lastnS = nS;
58  lastsloc = sloc;
59  lastsmag = smag;
60  lastsphase = sphase;
61  end
62  % connect sinusoids to last frame lnS (lastsloc,lastsphase,lastsmag)
63  sloc(1:nS) = (sloc(1:nS)~=0).*((sloc(1:nS)-1)*Ns/N); % synth. locs
64  lastidx = zeros(1,nS);
65  for i=1:nS
66  [dev,idx] = min(abs(sloc(i) - lastsloc(1:lastnS)));
67  lastidx(i) = idx;
68  end
69  ri= pin-hNs; % input sound pointer for residual analysis
70  xr = x(ri:ri+Ns-1).*wr(1:Ns); % window the input sound
71  Xr = fft(fftshift(xr)); % compute FFT for residual analysis
72  Xh = genspecsines(sloc,smag,sphase,Ns); % generate sines
73  Xr = Xr-Xh; % get the residual complex spectrum
74  mXr = 20*log10(abs(Xr(1:Ns/2+1))); % magnitude spectrum of residual
75  mXsenv = decimate(max(-200,mXr),stocf); % decimate the magnitude spectrum
76  % and avoid -Inf
77  %-----synthesis data-----%
78  ysloc = sloc; % synthesis locations
79  ysmag = smag(1:nS); % synthesis magnitudes
80  mYsenv = mXsenv; % synthesis residual envelope
81 
82 
83 %-----transformations-----%
84 
85 %-----time mapping-----%
86 outsoundlength = soundlength*2;
87 TM=[ 0 soundlength/fs; % input time (sec)
88 0 outsoundlength/fs ]; % output time (sec)
89 
90 %%-----frequency stretch-----%
91 %fstretch = 1.1;
92 %ysloc = ysloc .* (fstretch.^[0:length(ysloc)-1]');
93 
94 %-----synthesis-----%
95  if (fridx==0)
96  lastysphase = ysphase;
97  end
98  if (nS>lastnS)
99  lastysphase = [ lastysphase ; zeros(nS-lastnS,1) ];
100  lastysloc = [ lastysloc ; zeros(nS-lastnS,1) ];
101  end
102  ysphase = lastysphase(lastidx(1:nS)) + 2*pi*(lastysloc(lastidx(1:nS))+ysloc)/2/Ns*H; % propagate phases
103  lastysloc = ysloc;
104  lastysphase = ysphase;
105  lastnS = nS; % update last frame data
106  lastsloc = sloc; % update last frame data
107  lastsmag = smag; % update last frame data
108  lastsphase = sphase; % update last frame data
109  Yh = genspecsines(ysloc,ysmag,ysphase,Ns); % generate sines
110  mYs = interp(mYsenv,stocf); % interpolate to original size
111  roffset = ceil(stocf/2)-1; % interpolated array offset
112  mYs = [ mYs(1)*ones(roffset,1); mYs(1:Ns/2+1-roffset) ];
113  mYs = 10.^(mYs/20); % dB to linear magnitude
114  pYs = 2*pi*rand(Ns/2+1,1); % generate phase spectrum with random values
115  mYs1 = [mYs(1:Ns/2+1); mYs(Ns/2:-1:2)]; % create complete magnitude spectrum
116  pYs1 = [pYs(1:Ns/2+1); -1*pYs(Ns/2:-1:2)]; % create complete phase spectrum
117  Ys = mYs1.*cos(pYs1)+1i*mYs1.*sin(pYs1); % compute complex spectrum
118  yhw = fftshift(real(ifft(Yh))); % sines in time domain using inverse FFT
119  ysw = fftshift(real(ifft(Ys))); % stochastic in time domain using IFFT
120  yh(ri:ri+Ns-1) = yh(ri:ri+Ns-1)+yhw(1:Ns).*sw; % overlap-add for sines
121  ys(ri:ri+Ns-1) = ys(ri:ri+Ns-1)+ysw(1:Ns).*sws; % overlap-add for stochastic
122  pin = pin+H; % advance the sound pointer
123  fridx = fridx+1;
124 end
125 y= yh+ys; % sum sines and stochastic
static struct ResampleContext * create(struct ResampleContext *c, int out_rate, int in_rate, int filter_size, int phase_shift, int linear, double cutoff, enum AVSampleFormat format, enum SwrFilterType filter_type, int kaiser_beta, double precision, int cheby)
Definition: soxr_resample.c:32
Definition: start.py:1
initialize buffer for FFT yh
Definition: spsmodel.m:18
FFT size for synthesis H
Definition: spsmodel.m:10
analysis window size Ns
Definition: spsmodel.m:9
magnitude spectrum pX
Definition: stft_peak.m:24
if max(w)>1 w=0.9 *w/max(w)
initialize synthesis harmonic locations ysphase
Definition: spsmodel.m:31
output residual component w
Definition: spsmodel.m:20
About Git write you should know how to use GIT properly Luckily Git comes with excellent documentation git help man git shows you the available git< command > help man git< command > shows information about the subcommand< command > The most comprehensive manual is the website Git Reference visit they are quite exhaustive You do not need a special username or password All you need is to provide a ssh public key to the Git server admin What follows now is a basic introduction to Git and some FFmpeg specific guidelines Read it at least if you are granted commit privileges to the FFmpeg project you are expected to be familiar with these rules I if not You can get git from etc no matter how small Every one of them has been saved from looking like a fool by this many times It s very easy for stray debug output or cosmetic modifications to slip in
Definition: git-howto.txt:5
bh
Definition: spsmodel.m:25
normalize synthesis window wr
Definition: spsmodel.m:27
N, 1 zeros()
function ploc
normalize analysis window sw
Definition: spsmodel.m:21
FFT size for synthesis(even) H
#define sample
FFT of current buffer mX
Definition: stft_peak.m:23
About Git write you should know how to use GIT properly Luckily Git comes with excellent documentation git help man git shows you the available git< command > help man git< command > shows information about the subcommand< command > The most comprehensive manual is the website Git Reference visit they are quite exhaustive You do not need a special username or password All you need is to provide a ssh public key to the Git server admin What follows now is a basic introduction to Git and some FFmpeg specific guidelines Read it at least if you are granted commit privileges to the FFmpeg project you are expected to be familiar with these rules I if not You can get git from etc no matter how small Every one of them has been saved from looking like a fool by this many times It s very easy for stray debug output or cosmetic modifications to slip please avoid problems through this extra level of scrutiny For cosmetics only commits you should e g by running git config global user name My Name git config global user email my email which is either set in your personal configuration file through git config core editor or set by one of the following environment VISUAL or EDITOR Log messages should be concise but descriptive Explain why you made a what you did will be obvious from the changes themselves most of the time Saying just bug fix or is bad Remember that people of varying skill levels look at and educate themselves while reading through your code Don t include filenames in log Git provides that information Possibly make the commit message have a descriptive first an empty line and then a full description The first line will be used to name the patch by git format patch Renaming moving copying files or contents of making those normal commits mv cp path file otherpath otherfile git add[-A] git commit Do not rename or copy files of which you are not the maintainer without discussing it on the mailing list first Reverting broken commits git revert< commit > git revert will generate a revert commit This will not make the faulty commit disappear from the history git reset< commit > git reset will uncommit the changes till< commit > rewriting the current branch history git commit amend allows to amend the last commit details quickly git rebase i origin master will replay local commits over the main repository allowing to merge or remove some of them in the process Note that the reset
Definition: git-howto.txt:153
initialize sound pointer to middle of analysis window pend
initialize output if(nPeaks >3)%at least 3 peaks in spectrum for trying to find f0 nf0peaks
#define M(a, b)
Definition: vp3dsp.c:43
pphase
Definition: stft_peak.m:27
end end
trying all byte sequences megabyte in length and selecting the best looking sequence will yield cases to try But first
function magnitudes and phases
#define N
Definition: vf_pp7.c:200
static void interpolate(float *out, float v1, float v2, int size)
Definition: twinvq.c:280
Plot spectral magnitude
return end harmonic
Definition: extra/TWM.m:29
initialize synthesis harmonic phases fridx
Definition: spsmodel.m:32
frame
Definition: stft.m:14
Discrete Time axis x
half analysis window size pin
Definition: spsmodel.m:15
synthesis window for stochastic lastysloc
Definition: spsmodel.m:30
Spectrum Plot time data
#define zero
Definition: regdef.h:64
these buffered frames must be flushed immediately if a new input produces new the filter must not call request_frame to get more It must just process the frame or queue it The task of requesting more frames is left to the filter s request_frame method or the application If a filter has several the filter must be ready for frames arriving randomly on any input any filter with several inputs will most likely require some kind of queuing mechanism It is perfectly acceptable to have a limited queue and to drop frames when the inputs are too unbalanced request_frame This method is called when a frame is wanted on an output For an input
phase spectrum(unwrapped) ploc
overlapping window(triangular window to avoid too much overlapping) ovidx
static const uint8_t offset[127][2]
Definition: vf_spp.c:70
int size
clear max peak[Mmag2, Mloc2]
Definition: extra/TWM.m:16
last sample to start a frame fftbuffer
Definition: spsmodel.m:17
overlapping window ovidx
Definition: spsmodel.m:23
use a maximum of peaks[f0, f0error]
Sampled sinusoid X
t
Definition: genspecsines3.m:6
Harmonics mapping(fx) Xmag(ploc)
size of positive spectrum soundlength
Definition: gong.m:8
sws
Definition: spsmodel.m:29
sound(x3, Fs)
the buffer and buffer reference mechanism is intended to avoid
mag
Definition: lab5.m:14
About Git write you should know how to use GIT properly Luckily Git comes with excellent documentation git help man git shows you the available git< command > help man git< command > shows information about the subcommand< command > The most comprehensive manual is the website Git Reference visit they are quite exhaustive You do not need a special username or password All you need is to provide a ssh public key to the Git server admin What follows now is a basic introduction to Git and some FFmpeg specific guidelines Read it at least if you are granted commit privileges to the FFmpeg project you are expected to be familiar with these rules I if not You can get git from etc no matter how small Every one of them has been saved from looking like a fool by this many times It s very easy for stray debug output or cosmetic modifications to slip please avoid problems through this extra level of scrutiny For cosmetics only commits you should get(almost) empty output from git diff-w-b< filename(s)> Also check the output of git status to make sure you don't have untracked files or deletions.git add[-i|-p|-A]< filenames/dirnames > Make sure you have told git your name and email address
synthesis window for stochastic i
static const int factor[16]
Definition: vf_pp7.c:202
half synthesis window size hM
Definition: spsmodel.m:14
function pmag
fftbuffer, N fft()
FFmpeg Automated Testing Environment ************************************Table of Contents *****************FFmpeg Automated Testing Environment Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass target exec to configure or set the TARGET_EXEC Make variable Submitting the results to the FFmpeg result aggregation server ****************************************************************To submit your results to the server you should run fate through the shell script tests fate sh from the FFmpeg sources This script needs to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at doc fate_config sh template Create a configuration that suits your based on the configuration template The slot configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern< arch >< os >< compiler >< compiler version > The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the fate_recv variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ssh command with one or more v options You should get detailed output concerning your SSH configuration and the authentication process The only thing left is to automate the execution of the fate sh script and the synchronisation of the samples directory FATE makefile targets and variables *************************************Makefile can be set to
Definition: fate.txt:142
1:W2 xw()
function fs
the buffer and buffer reference mechanism is intended to as much as expensive copies of that data while still allowing the filters to produce correct results The data is stored in buffers represented by AVFilterBuffer structures They must not be accessed but through references stored in AVFilterBufferRef structures Several references can point to the same buffer
these buffered frames must be flushed immediately if a new input produces new output(Example:frame rate-doubling filter:filter_frame must(1) flush the second copy of the previous frame, if it is still there,(2) push the first copy of the incoming frame,(3) keep the second copy for later.) If the input frame is not enough to produce output
function y
Definition: D.m:1
hop size for analysis and synthesis N2
Definition: spsmodel.m:11
length of input sound array hNs
Definition: spsmodel.m:13
static uint32_t inverse(uint32_t v)
find multiplicative inverse modulo 2 ^ 32
Definition: asfcrypt.c:35
ow
Definition: spsmodel.m:22
float min
for(j=16;j >0;--j)
x length()
these buffered frames must be flushed immediately if a new input produces new the filter must not call request_frame to get more It must just process the frame or queue it The task of requesting more frames is left to the filter s request_frame method or the application If a filter has several the filter must be ready for frames arriving randomly on any input any filter with several inputs will most likely require some kind of queuing mechanism It is perfectly acceptable to have a limited queue and to drop frames when the inputs are too unbalanced request_frame This method is called when a frame is wanted on an output For an it should directly call filter_frame on the corresponding output For a if there are queued frames already one of these frames should be pushed If the filter should request a frame on one of its repeatedly until at least one frame has been pushed Return values
output sine component ys
Definition: spsmodel.m:19