Saving the parameters of the supervp-processing

[spiropoulos]

Dear Karim,

is there a way to save all the parameters of the supervp-processing in a text file having the list of parameters as following ?

I created my own tool but it is not patch space savy…

“begin
end
window-size 4096
fft-size 4096
window-step 4
window-type hanning
shape-invariant
preserve-transient t
normalize
outfile NEW_filename
extend-across yes”

OR maybe save an excerpt similar to the information in the Listener, for exemple :

OLD_filename.aif
-Afft -M4096 -N4096 -Whanning -oversamp 4 -P1 -td_thresh 1.4 -td_band 0.0,22050.0 -td_ampfac 1.5 -D1.075 -Osa16
NEW_filename.aif

And another relative question.
How can I use the ’save-params’ or ’save-as-text’ or svp-paramfile’ ?
I can’t find any doc about…

Thank you !
Georgia

[rc0]

Hi,

there’s an old (but gold) trick to save and recall text here:

Calling External Scripts

+1 It would be great to have the stdout directly from the om-shell outlet. A work around would be to write the stdout in a text file and the open it in OM, then you can process the text as you want. Attached image with simple example retrieving ip information (OM 6.12 Ubuntu). [Screenshot_2017-08-06_01-24-09.png]

(just change the command with “echo your VP parameters”)

or the file box stuff:

https://support.ircam.fr/docs/om/om6-manual/co/ReadingWriting.html

I’m also interested in this topic! if you know more ways please share them if you can

best rc

[haddad]

Dear Georgia,

I don’t seem to understand exactly your question about the parameters. They are all available starting from supervp-processing method.
Now if you mean you need to create a shortcut starting from a script you can use om-terminal with a textfile. If you need me to send you an example, please do send the processing type you are using.

BEst
K

[haddad]

Dear Goergia,

Anyhow, if i understand you well here ia an example based on the info you gave:

And the patch:
01-one-treatment-1.omp (16.4 KB)

Best
K

[haddad]

…as for your next question, i think you are refering to this:

It’s in the OM prefs under externals tab pressing Options button

[spiropoulos]

Dear Karim,

sorry i it wasn’t clear.

I need to save automaticaly in a .txt all the parameters of 1) my treatment and 2) of the supervp processing.
By “automaticaly’ I mean without copy paste from terminal. The .txt should be saved together with the processing.

A .txt file containing either this:

"OLD_filename.aif
stretch 1.075
begin
end
window-size 4096
fft-size 4096
window-step 4
window-type hanning
shape-invariant nill
preserve-transient t
normalize nil
outfile NEW_filename.aif
extend-across yes”

OR this

“OLD_filename.aif
stretch 1.075
-Afft -M4096 -N4096 -Whanning -oversamp 4 -P1 -td_thresh 1.4 -td_band 0.0,22050.0 -td_ampfac 1.5 -D1.075 -Osa16
NEW_filename.aif”

I created myself the first version (for the moment without the ’in_filename and the treatment) but it is not space savvy.
In my version both the treated AF and the .txt file have the same name automatically.

I am sending you my patch

Thank you very much

[spiropoulos]

The second version would be more ‘universal’

“OLD_filename.aif
TREATMENT treatment_ALL_PARAMETERS
-Afft -M4096 -N4096 -Whanning -oversamp 4 -P1 -td_thresh 1.4 -td_band 0.0,22050.0 -td_ampfac 1.5 -D1.075 -Osa16
NEW_filename.aif”

thanks

[haddad]

Thank you Georgia,

I appreciate rather a patch than a picture:-)

Anyhow, in order to output the arguments for m supervp-processing you need to change the method. Because what are you doing in your screenshots is just formating the commands. So maybe this?:

01-one-treatment-1 2.omp (14.4 KB)

[haddad]

Dear Goergia,

Can you just tell me what do you want really to achieve here?
Is it to auto-rename your soundfile according to the transformation. Because if it is the case, you are rather complicating the matter ie, there is a simpler way to do so.

BEst
K

[spiropoulos]

Dear Karim

thank you for the patches.

I need to autoname the final file, autoname and save a .txt file.

The txt should have the name of the processed audio file, the parameters of the treatment, and the parameters of supervp-processing.

I would like to find this information in order to repeat a treatment with exactly the same parameters if needed.

The command you are using is in a textfile separate from the supervp-processing object. That means that on have to add twice the parameters.

Is it possible to extract this command at the end of processing, directly from supervp-processing object, and save it as .txt?

[haddad]

Dear Georgia,

This is possible of course if we re-write the supervp-processing method, or do a new one for that. Because this implies two actions: Writing a soundfile and a textfile.
By the way, the method you use for naming your soundfile is rather problematic. Ie you are using white spaces which is not a standard method of dealing with pathnames at least in the unix world. I suggest you use underscores instead of white spaces.

Now if you need me to write a new method for doing so, i suggest you define clearly your needs. In your examples it is rather unclear which are the fields you want to name your soundfile. As for the commandline, we can of course write it in a file.

Best regards

Karim

[haddad]

Dear Georgia,

Here is a code for writing the commandline on disk + processing the soundfile:

The code:
svp-proc.lisp (6.4 KB)

Waiting for your specs for naming the soundfile. Please be specific and clear if possible.

Best
K

[spiropoulos]

Dear Karim,

(I wrote the following before having seen your message. I am checking your attached file. Thank you very much!)

I am not sure how to tell it in a different way. Let’s try a different option:

1. Name and save the processed audio file AND a .txt file
2. The .txt file should contain :

• the OLD_filename.aif
• the NEW_filename.aif
• the name of the TREATMENT
• All the PARAMETERS of the TREATMENT (for any king of treatment, transpostion, freeze, stretch, cross, fshift, bandfilter,…)
• all the PARAMETERS of the supervp-processing

3. I would like to retrieve the above information after the supervp-processing object.

The .txt file is for me an info file describing the whole process. I need to check easily and fastly its content in order 1) to repeat a treatment with exactly the same parameters and 2) for my presentations.

I am sending an exemple of the wanted .txt file attached.

Does the OM community need a re-written supervp-processing method ? I don’t know…
The fact is that it’s time consuming to find all the necessary information about the processes easily and quickly.
Personnaly I would love to have such a quick access for the applied processes.

As I said I programmed my patch and I can extend/improve it;
wanted output.txt (474 Bytes)
but my version is not general (for all treatments) neither space savvy.

Thank you very much!

PS: It is strange, I never name my sound files with white spaces.

[haddad]

What you are asking for is a complete rebuild of the OMSuperVp library.
Of course you can try to patch it up. But still, coding it is much more efficient.

I find two main issues here:

1. Naming the process. When you patch a process in the second input of supervp-processing, as it is right now, you cannot tell from within the method what is passed into it as a treatment. They are not named.

2. If you use parameters file, the parameters are passed to the method as a text file pathname, So we need to read it internally so we can print it out.

This is of course possible but needs some development in order to make all this work.
I will see what i can do without of course modifying the lib, but adding more code.

Best regards
K

[haddad]

Dear Georgia,

Here is a new version pf code doing nearly what you want:
svp-proc1.lisp (9.0 KB)

Still todo:

1. find a way i can explicitly print the Process and its value apart
2. In case using parameter file, print it in the correct field.

Tell me if i am closer to what you want

Best
K

[spiropoulos]

Dear Karim,

how may I test the svp-proc1.lisp file?
I added it in mylib>sources
I added the “svp-proc1” string in my GEORGIA.lisp and GEORGIA.lisp~ Library.
but I can’t call it in my workspace.

Concerning what you have asked me for I would suggest the following.

1. For the output soundfile and.txt name :
   toto_clip.aiff, toto_clip2.aiff,…
   toto_clip1.txt, toto_clip2.txt,…

2. For the treatment names (.aif and .txt name) :
   clip
   trans
   crossg
   crosssf
   fband
   fbpf
   ffo
   freeze
   freezetr
   fshift
   stretch
   gain
   mrk
   bpf

Thank you very much

Georgia

[haddad]

Thank you Georgia,

Concerning the svp-proc method, you should first load OM-SupeVp lib.
If you have trouble loading it from your library, i suggest you send your library to me so i can see if there is something wrong in your code. Just be aware that the code i sent you relies on OM-SuperVp lib. So the :svp package should be declared first.

Best
K