< Back to IRCAM Forum

PM2 Warning: don't recognize -filepat Kernel returned error -1

AudioSculpt
#1

Dear,

I’m analyzing a wav file (mono, 16bit) of orchestral performance captured from the audience, close to the stage.

I chose to apply markers manually to each section of the part.

Then I generated a sonogram so I could get a CHORD-SEQ result to extract an SDIF file from the recording.

However, the moment I click “Do analysis”, the following message appears: “the kernel pm2 reported an error”:

PM2 Warning: don’t recognize -filepat
Kernel returned error -1

pm2 -t -S"/Volumes/Dados/Thiago/Dropbox/Doutorado_UFPB_2013_2017/Tese/Sinfonia em Quadrinhos/HP - SQ - audio/Hermeto.Pascoal.-.Sinfonia.em.Quadrinhos.MONO.XXX.wav" -filepat XXX=2016 -Aseqs -B0.000000 -E1340.217163 -N8192 -M2229 -I278.625000000000000 -Wblackman -OS -p1 --mode=0 -q40 -m55.000000000000000 --chords="/Applications/AudioSculpt 3.4.0/Temp/chords" -B0.000000 -E1340.217163 “/Applications/AudioSculpt 3.4.0/ChordSeqs/tempChord-0054.cs.sdif”

Would any of you know how to resolve this situation?

Thanks for the help.

#2

Hi,

Are you running this on Sierra (OS) ? If it is the case, well there is your problem. New apple security policy is preventing pm2 to run. THe dev team are aware of this and will try to fix this issue ASAP.

Best
K

#3

HI MUS3,

I think this is probably a problem due to the parsing of the filename, and AudioSculpt find possibly
a tag used to activate the filepat option.

1-Try to remove or replace all ‘[’ and ‘]’ with another character.
2-Or simply rename the file using a simple name (to test)

And retry :slight_smile:
Tell me how it goes then.

HTH

Best,
Charles

#4

I am afraid on Sierra that this is not the problem. The message is not the one that was reported as the kernel is started but does create the error message with filepat.

In fact the filepat thing is meant to support split audiofiles that are stored as a pair of files named according to name.L.wav name.R.wav, we use
the name name.XXX.wav -filepat XXX=L,R in supervp to process these two files synchronously. Pm2 however does not support these split files (yet)
and so that’s where the error comes from.

Now as the command line is containing

-S”/Volumes/Dados/…MONO.XXX.wav” -filepat XXX=2016

The file appears to be MONO and is probably named with XXX by MUS3 - so it could be that due to some misguided automatism triggered by the XXX in the name AS expects this file to be a split multi channel file and invents the pattern 2016 out of the blue. If I am guessing correctly here MUS3 should be able to solve the problem by means of renaming the file avoiding the XXX in the name.

If this is the case then we should probably have a more robust means to trigger the file-pattern mechanism.

If really this is a split audio file then for sinusoidal analysis the file needs to be converted to interleaved format prior to running the analysis.

Best
Axel

#5

In fact my reply was to Karim and not to Charles who wrote just a few seconds before me :slight_smile:
Axel

#6

Yes Axel,

It is a bug in the way it is triggered/detected in AudioSculpt and it should be strengthen.

Best,
Charles

#7

Sorry guys,
my bad
k

#8

Well, actually it is more my bad than yours Karim :wink:

#9

Dear friends,

As mentioned, the problem was solved by changing the file name.

Thanks for the help and suggestion of all.

Best,
Thiago Cabral (Member of the research group “MUS3” from Brazil).