torstenanders

Update: I made some progress with the Emacs/Slime interface for Opusmodus 3, but not yet a fully working solution. Just sharing here an intermediate progress report for those interested. I found out that I could start the swank server (the Lisp compiler part of Slime) in the following way. 1. Install the latest version of Slime (link) where it can be found by ASDF (which is by default the folder ~/common-lisp). 2. Execute the following code within Opusmodus (or some file loaded by Opusmodus): (asdf:load-system :swank) (swank:create-server :dont-close t) There is then no error message any longer, but instead I get the following message. ;; Swank started at port: 4005. On the Emacs side, Slime needs to be installed in the usual way (e.g., via a MELPA repository). On the Emacs side then, as before, call M-x slime-connect with the localhost IP 127.0.0.1 and the relevant port (4005 by default). On my particular system, Emacs then somehow gets stalled for a long time, much longer than before when trying to do the same with Opusmodus 2. Emacs is then completely frozen. Anyway, sometimes I already got a working connection between Emacs Slime and Opusmodus 3 now, but not necessarily reproducible. Anyway, will continue following this up and keep you in the loop if I make further progress. If anyone else finds out more, I would be grateful!

Ah, nice. Will check that out. Thank you!

So, I understand that the export menu is now integrated into the respective player, and that so far unfortunately there is no MIDI export Lisp function complementing the import functions midi-to-omn or midi-to-score. Thank you!

Is there perhaps a MIDI export function? Something like the opposite of midi-to-omn or midi-to-score, which expects a snippet/score and exports a MIDI file? I would like to export a bunch of MIDI files in one go... BTW: In Opusmodus 2, for exporting individual files we had a menu File > Export. Where is the equivalent in Opusmodus 3? Thanks!

Thanks for your encouragement, Stephane! In case you want to use this and run into difficulties, just let me know. If I am not responding to any messages on the forum (apologies in advance), feel free to send me an email. You'll find my email address in the impression on my website linked in my profile.

Dear Janusz, > I need to check if we can use Emacs with the new Opusmodus (LispWorks). Any updates on the Emacs/Slime interface for Opusmodus 3? I understand/assume that in order to simplify the Opusmodus interface for most of its users, Opusmodus provides its own IDE with convenient features for things like snippet playback. Indeed, Emacs would be unnecessarily confusing for most of Opusmodus' users. However, for actual Lisp/Opusmodus library development, I personally feel the Opusmodus IDE is currently far less suited than Slime. While there is a debugger already integrated in the Opusmodus IDE (thanks), it is basically only the command line version of the 80s. Also, I have not found any cross referencing support in the Opusmodus IDE (e.g., for jumping to the definition of a function call with a single shortcut). Not sure whether the Opusmodus listener has some short cuts to go back in its history etc. Perhaps I am missing some things, but Slime is a completely different cattle of fish for developers in contrast of users (of course, only after its learning curve). Anyway, I understand if you do not have the resources (or if LW does not allow) for Emacs/Slime integration into Opusmodus 3. I just keep using mainly Opusmodus 2 with working Slime in the meantime. Thanks for all your work on Opusmodus!

Update: My tot library can now in principle be loaded into Opusmodus 3. However, note the current disclaimer (link) in the Readme on some still existing issues with its Opusmodus 3 support. Myself, I will for now continue using mainly Opusmodus 2, because there the Emacs/Slime interface still works. For my workflow, that interface makes a huge difference in terms of work speed etc. (I cannot really develop Lisp libraries without access to an interactive debugger, the convenient cross references between different definitions and so on).

Update: I meanwhile managed to fix one of the issues, which prevented loading cluster-engine (some Swedish word in a comment caused some character encoding and end-of-line style mismatch, that was tricky to pin down, in particular also due to a somewhat cryptic error message ). Unfortunately, there is still some other problem when loading the tot library, which I will hunt down eventually, and then share my fixes at Github. In the meantime, I decided to simply use Opusmodus 2 on my old MacBook for a little longer, as there also the Emacs/Slime interface just works.

Oh, thanks for clarifying that for loading modules is still possible to use asdf:load-system as a workaround. Nice. I can confirm that this is working! I still get errors, e.g., when loading cluster-engine, but it is now up to me trying to get that fixed.

Thanks a lot!

Any progress on using Emacs (Slime) with Opusmodus 3? It appears the file Emacs-Slime Setup.lisp is still part of the Extensions folder, but as reported (start-swank) results in an error. Thanks!

I just tried using Opusmodus 3, but unfortunately there is a principle problem for me: it prevents me from loading any of me pre-existing libraries, which provide a lot of functionality already, but which I created for Opusmodus 2 (libraries like tot, cluster-engine, cluster-rules, cm-patterns etc.). It appears this is caused by the switch of Lisp compilers, and that the new version -- now based on LispWorks -- has been "delivered" without ADSF support. However, it appears this can be changed easily for Opusmodus by adjusting the parameters for creating the delivery to :KEEP-MODULES T (see docs). This is also what the error message I get is saying. > (require :tot) Error: REQUIRE was called after delivery time with module :tot. To fix this, either require the module before delivery or use :KEEP-MODULES T. 1 (abort) Return to top loop level 0. Type :b for backtrace or :c <option number> to proceed. Type :bug-form "<subject>" for a bug report template or :? for other options. Context for those interested in tech details: ADSF is the de facto standard for loading Common Lisp applications that consist of multiple source files etc. It is also part of LispWorks (though seemingly in the outdated version 2, because LispWorks has its on system for such purposes, but that is another matter). LispWorks is a commercial Lisp compiler, and when you deliver your Lisp application to your client, you usually create a delivery of your software, which disables some of the LispWorks features. After all, LispWorks still wants to sell further copies of its development environment (in fact, it is amazing how much development functionality can be preserved in a delivery as demonstrated by Opusmodus itself). Nevertheless, when creating the delivery it is possible to opt out of disabling some of the features, e.g., with the above-mentioned parameter KEEP-MODULES, as documented by LispWorks (I also remember from PWGL times, which was also a LispWorks delivery, that it was possible to load modules with ADSF). Sorry, but it has been a few years since I have had time using Opusmodus for the last time, and at the time I have still been using version 2 (on my previous MacBook). Thanks a lot! BTW: There are a bunch of hopefully helpful links in the above post, but for some reason they are not highlighted as such.

I once implemented a version of this in PWGL with constraint programming (rule based programming) and the help of pwgl-cluster-engine and pwgl-cluster-rules. Unfortunately, I PWGL is meanwhile broken for me, and I cannot open this patch anymore, but just in case you have used PWGL and these libraries before, I attach a patch demonstrating it. If not, then this likely will not really help you. Sorry that I cannot help more. Its about 10 years ago since I did this... Best, Torsten 04-tintinnabuli.pwgl

Thanks a lot for this info! > You can't use 2.2 and 3.0 on the same cpu Fair enough. I currently have 2.2 working on an my old Mac. I just keep that and wait for the Windows version, then I can use version 3 with my PC. Thanks for all your work on this update!

>> what exactly are the new features in Opusmodus 3 (vs 2.2)? > 30 days trial should do the trick, hopefully less elusive and vague. Is it possible to run both Opusmodus 2 and 3 in parallel to test the new version without loosing the old one? I am afraid that the new version might have broken some of my Opusmodus libraries (porting them to a new compiler can be tricky). Also, I am very surprised that several people need to ask about a list of the changes of the new version, and there is still no response. (I also sent a private message with the very same question a few weeks ago.) I don't want to be impolite, but this makes the impression of a software company that does not really care about users finding its product useful. I actually know that this is not the case, but this is a very strange communication strategy. > Is it possible to run both Opusmodus 2 and 3 in parallel to test the new version without loosing the old one? I meanwhile found a response in another thread (link). I think I will then have to wait with the update and trial until I know more about the new version and perhaps have another computer to test it on. Thanks!