loadMelodyFile.m
Go to the documentation of this file.
1 function [melody] = loadMelodyFile(filename)
2 
3 % Open raw file
4 fid = fopen(filename,'r+');
5 
6 % Read 1st line
7 tline = fgetl(fid);
8 onset_pitch(:,1) = sscanf(tline, '%*s %f %f');
9 
10 % Read rest of the lines
11 i=1;
12 while ischar(tline)
13  i = i+1;
14  tline = fgetl(fid);
15  if (ischar(tline))
16  onset_pitch(:,i) = sscanf(tline, '%f\t%f');
17  end;
18 end
19 melody = onset_pitch;
20 
21 % Close file
22 fclose(fid);
23 
f
Sinusoidal phase f
Definition: FFT of a Simple Sinusoid.m:8
if
initialize output if(nPeaks >3)%at least 3 peaks in spectrum for trying to find f0 nf0peaks
line
Definition: graph2dot.c:48
ischar
while ischar(tline) i
onset_pitch
onset_pitch(:, 1)
file
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 file
Definition: fate.txt:34
t
t
Definition: genspecsines3.m:6
fclose
Close file fclose(fid)
i
Read rest of the lines i
Definition: loadMelodyFile.m:11
end
if(ischar(tline)) onset_pitch( end
Definition: loadMelodyFile.m:15
melody
end melody
Definition: loadMelodyFile.m:19
tline
Read line tline
Definition: loadMelodyFile.m:7
Generated on Mon Nov 18 2024 06:51:57 for FFmpeg by   doxygen 1.8.11