< Back to IRCAM Forum

Segmentation violation in sound sequencing

OpenMusic
#1

Hello!
I am doing a patch for algorithmic beat-slicing and remixing of audio material. Very often i encounter this error when i employ the sound-seq function with a crossfade time (?)

In this case it’s invoked by reduce function and used in lambda mode, but i get it in many other context so the problem should not be reduce…

Error while evaluating the box REDUCE : Segmentation violation(11) [code 0] at 2018C189
{Offset 15 inside #<Function 1 subfunction of (top-level-form 2) 2018C17A>}
eax 14C000 ; ebx 2018C17A ; ecx 228 ; edx 219051D3
esp EF2FE690 ; ebp EF2FE6E8 ; esi 26540DA7 ; edi 279E3000

noise-extraction.omp (47.6 KB)

#2

is it possible that your sound segments are too short wrt the cross-fade duration ?
could you provide an example + soundfile which causes the error?
jean

#3

Hello Jean, I think it’s not the cause,
as you see i did put a loop to eliminate the shorter slices and ensure all my slices where at least 2 times the fade length. Also the error is not happening all the time, but when it gets in, it lasts until i close the patch or sometimes OM completely.
It has a strange behaviour: for example i try 50 ms fade, everything is good. I try a longer fade, for example 200, the error comes in. then if I get back to 50 ms again it will give error even if was not the case at the first time.
Anyway if it can help i attach you the sound file:

Cecco-NonnoMorto_02.wav (3.99 MB)

#4

Hi guys,

I had the same issue (segmentation violation), on om6.9 (Linux version). With a patch using simple objects :

sdiffile, and sound object with an embeded maquette.

Now When i moved my patch into another location (a folder), i had the same message (segmentation violation).

I am just posting this because it might be related to a path thing, i am not sure.

But what i did is this:

saved my workspace, then launched again om and everything went fine except that the sound and sdif file related to the patch were missing (needed to load them again).

And i had this issue many times while moving the patch’s location.

Best
K

#5

Hello,

It sounds like a bug I already fixed.
Please find attached a Lisp file that you have to put in the “/Applications/OM6.9/patches/” folder, so it loads at startup.
If it doesn’t solve your issue, please let us know.

Best,

Dimitri.

SOUND-SEQ_FIXPATCH.lisp (2.59 KB)

#6

Dear Dimitri,

Unfortunately it didn’t resolve my problem (see attachment). I think it is related not to the sound-seq function but
with some sort of folder hierarchy . (i am under Linux Debian, latest release).
It is fixed when i relaunch om.
But when i create a patch on the same level of folders including my buggy patch it happens.
(see attachments).

BEst
K

bug_patch.jpg

#7

Ok Karim thank you for the details I’ll investigate asap.
Ratox on what OS are you running OM?

Best,

Dimitri

#8

Hello dimitry sorry for not replying soon. I was in the middle of Cursus 1 Piece…so no time for sleep…
I tried the patch and unfortunately:
1-did not solve the problem of segmentation fault
2-the processing time of re-sequencing operations did explode in something like 10 times more than before…

Sorry not to be able to give a more positive feedback…consider me at your disposal for the ongoing research on the subject and bugfxing! Alessandro…

#9

This error is also common when selecting several simple objects and Option+Dragging to copy the objects to another location in the patch.

Best,

jc