< Back to IRCAM Forum

Problem with a score-object and om 7.7

OpenMusic
#1

Hi everyone,
I have a problem with om 7.7 which didn’t appear with previous versions. I can no longer open a score object (by double-clicking on note, chord-se, voice and so on… ); I get an error message and a blank window that cannot be closed. Here is the message:

" An error of type simple error occurred: No applicable
 methods for #<standard-generic-function om-checked-p
 40E0D676CC> with args (#<edit-numbox 401049FB83>)"

my distribution is Debian 12
thank you all.

#2

Dear lacot,

Very strange. This works for me (i am now on Debian 13, but tested this on Debian 12).
MY guess it is something related to your workspace maybe. Have you tried with a new workspace?
If the works then, it is your patch i believe.

What window manager you are using?

Best
K

#3

Karim,
Thanks a lot for your answer.
I use Gnome. And as I have several workspaces, I get the same result with all of them.

Best,
G. Lacot

#4

Dear G. Lacot,

Just tried on gnome, and everything works as predicted…
Please can you try with a newly created workspace?
Most probably you have some old code loaded somewhere in your setup.

Don’t hesitate to report back.

Best
K

#5

To be precise, I would like to add: I went directly from om7.5 to om7.7 (so without om7.6).
Thankks,
G.Lacot

#6

Did you test this on a newly created workspace without any library loaded?

and can you please check out this in the terminal:

ls /usr/share/openmusic/init

and tell me the result output

Thanks

K

#7

I got the same result with no library loaded. Here is the Terminal output:

ls /usr/share/openmusic/init
1+1+.lisp essai1-lorrain.lisp patch_070125.lisp
1d-cellular-automata.lisp essai2.lisp patch_190825b-2.lisp
1d-cellular-automata-type-b.lisp essai3.lisp ped.08.CLtL2lambda.lisp
3dc_lib_fix.lisp exo2@11_ex.lisp ped.08.lisp
3dwan.lisp find-k.lisp ped.11.2a.lisp
3dwannab.lisp fix071122.lisp ped.11.3.lisp
addbylist.lisp font-defs.lisp ped.12.lisp
antoine.lisp ‘font-wkp .lisp’ ped13-lisp.lisp
ArvoP foo.lisp ped.13.suppl.lisp
arvo-part-utils.lisp funct_didier1.lisp perlin.lisp
auto-cell.lisp gauss-ser.lisp QuAlea.lisp
autocell.lisp.lisp getpos.lisp qwe.lisp
bpf-lib-scale.lisp get-view-font-icon.lisp random-bpf.lisp
bubble-sort.lisp group-indices.lisp redef-print-2.lisp
calcul-avec-liste-select.lisp group-max.lisp ‘rgb- hue.lisp’
canonforconlon.lisp iconpatch.lisp rotatetreelist.lisp
cassq.lisp info.txt scaling-sum.lisp
changechan.lisp interval-grouper.lisp sdif2self.lisp
cherche-pos.lisp item-position2.lisp s-dur.lisp
chord-seq_filt.lisp ItemPositions2.lisp sources
chordseq-tie.lisp itempositions5.lisp spiegel-series.lisp
chord-sorter.lisp lst-subst.lisp ‘string->ascii.lisp’
circular-nth-flat.lisp mac1.lisp sum-rand.lisp
circular-nth.lisp maki.lisp tempfix1.lisp
clappingmusic.lisp momentary_fix_100119.lisp tempomap-functions.lisp
clappingmusic.lisp~ multi-nth.lisp test.lisp
comb-rec21.lisp noise.lisp tintinnabulli.lisp
common-lisp-codes no-successive-random.lisp vl-positions.lisp
constellation1.lisp nth+.lisp x-nth-random.lisp
epicycles-CAP.lisp ‘OpenObjectEditor .lisp’
epicycles.lisp parenti.lisp

Best,
G. Lacot

#8

Ok ,

We are making progress here!

All these files should not be there! That’s where the conflict originates.
Please remove them (back them up if you want).
The init folder for now should be empty.

Best
K

#9

Karim,
YES !! The init folder is now empty, and everything works as before. However, two more questions, if you like.

  • What should the init-folder contain?
  • Where can I put the contents of the “old” init-folder, if it’s still useful?
    In any case, thank you for all this work on OM.
#10

Great to know, :slight_smile:

Well most of these files are extra codes, some of them are bug fixes.
The init folder is mainly reserved for bug fixes patches in form of lisp code.
When you install a new version, you should inspect the init folder, and clean it up.

So all these files you can keep somewhere since some of them are extra code from third party. Just as omlibraries add some code to the main OM one.
But since amongst them, you have bug fixes such as: patch_190825b-2.lisp they can get in conflict wiith OM code. So you better take care of what you are adding as code.

Some of these files are just extra functions and methods. But i don’t know all of them.

If you need to add them, just try one by one and put them instead in your workpsace user folder.

Best
K

#11 
Thank you for these explanations, the details of which I was unaware of; I think I understand better now.


Best,


G Lacot
1 Like