Jump to content

Automatic opening last MIDI file files in Musescore (or Sibelius, etc)


Recommended Posts

Dear Friends,

Is there some way to automatically opening a MIDI FILE (related to the last snippet/score generated)  from Opusmodus to other application (Musescore, Sibelius) ?

 

Something similar to this solution ?

last-score-to-musescore

 

solution, but for last midi files ?

 

Like this post ? But for midi file?

 

Many thanks in advance !

Much needed now.

 

Best,

Julio

Link to post
Share on other sites

Thanks, Janusz !

 

But I need the Midi File to get the VSL articulations from it.

I take the notated part from the XML, using

(last-score-to-musescore)

wich makes musescore open "automagically" the XML

I´d like to have the same thing for Export/Last Score to Midi...

without having to save midi file in disk first, then opening to Musescore.

Just the command and boom ! Like I have with the XML.

Then I will cut just the articulation keyswitches part and paste alongside the XML part.

 

Best !

Julio

Link to post
Share on other sites

Many thanks, Janusz

 

If possible, add the idea of filtering tracks, for

 picking specific tracks on rendering the files, like

a keyword

:tracks

 

 

(midi-to-editor :tracks '(0 2 3 5))

For rendering/saving  just some tracks

 

It would be AWESOME !!

Link to post
Share on other sites

This you will need to do before.

 

(midi-to-editor) ;is using the default editor
(midi-to-editor "filename") ;specific midifile (not *last-score*)
(midi-to-editor :application Musescore) ;*last-score* midi will open in Musescore

the default will be:
 

(defparameter *default-notation-editor* "Sibelius")

 

which you can changed to your editor application.

The same I will do to the musicxml:
(musicxml-to-editor)

Link to post
Share on other sites

Thank you, Janusz

Yes, I already have some user defined things, like this:

 

(defparameter *snippet-clef-default* :treble-down8)

(defun last-score-to-musescore ()
  (compile-score *last-score* :output :musicxml :file "temp-last-score")
  (musicxml-to-editor "temp-last-score" :application "/Applications/MuseScore3.app"))

 

Thanks !!

I will try this to see if works !

 

(defun last-midi-to-musescore ()
  (compile-score *last-score* :output :midi :file "temp-last-midi")
  (midi-to-editor "temp-last-midi" :application "/Applications/MuseScore3.app"))

 

Link to post
Share on other sites

I tried using the musicxml-to-editor

 

(defun last-midi-to-musescore ()
  (compile-score *last-score* :output :midi :file "temp-last-midi")
  (musicxml-to-editor "temp-last-midi" :application "/Applications/MuseScore3.app"))

Like above, but the musicxml gives an error with midi files...

 

How about to create a generic-file-to-editor choice, to send any type of file to other auxiliary apps ?

 

Best !

Julio

Link to post
Share on other sites

In the next update:


MUSICXML-TO-EDITOR
 

The MUSICXML-TO-EDITOR function opens a MusicXML file or the last compiled score (DEF-SCORE, PS or snippet) in any notation editor like Sibelius, Dorico, MuseScore etc...

 

In Opusmodus the default editor is set to Sibelius:

 

(defparameter *default-notation-editor* "Sibelius.app")

 

To change the default editor you need to replace the  "Sibelius.app" string with the name of your own editor and paste the expression into the ‘User Source.lisp’ file which you will find in the ~/Opusmodus/Extensions directory.

 

For example:

 

(defparameter *default-notation-editor* "Dorico 3.5.app")

(defparameter *default-notation-editor* "MuseScore 3.app")

 

Examples:

 

To open the last compiled score (DEF-SCORE, PS or snippet) in the notation editor:

 

(musicxml-to-editor)

 

To open the 2nd instrument from the last compiled score (DEF-SCORE, PS or snippet) in the notation editor:

 

(musicxml-to-editor :instrument 2)

 

To open a MusicXML file in the notation editor:

 

(musicxml-to-editor "file-name")

 

To open the file in Finale:

 

(midi-to-editor "file-name" :application "Finale")

 

Should the application not open you can use the identifier keyword with the bundle-identifier.

For example the Sibelius 7.5 version identifier is "com.avid.Sibelius75"

 

(musicxml-to-editor "file-name" :identifier "com.avid.Sibelius75")
 


MIDI-TO-EDITOR
 

The MIDI-TO-EDITOR function opens a MIDI file or the last compiled score (DEF-SCORE, PS or snippet) in any notation editor like Sibelius, Dorico, MuseScore etc...

 

In Opusmodus the default editor is set to Sibelius:

 

(defparameter *default-notation-editor* "Sibelius.app")

 

To change the default editor you need to replace the  "Sibelius.app" string with the name of your own editor and paste the expression into the ‘User Source.lisp’ file which you will find in the ~/Opusmodus/Extensions directory.

 

For example:

 

(defparameter *default-notation-editor* "Dorico 3.5.app")

(defparameter *default-notation-editor* "MuseScore 3.app")

 

Examples:

 

To open the last compiled score (DEF-SCORE, PS or snippet) in the notation editor:

 

(midi-to-editor)

 

To open the 2nd instrument from the last compiled score (DEF-SCORE, PS or snippet) in the notation editor:

 

(midi-to-editor :instrument 2)

 

To open MIDI file in the notation editor:

 

(midi-to-editor "file-name")

 

To open the file in Finale:

 

(midi-to-editor "file-name" :application "Finale")

 

Should the application not open you can use the identifier keyword with the bundle-identifier.

For example the Sibelius 7.5 version identifier is "com.avid.Sibelius75"

 

(midi-to-editor "file-name" :identifier "com.avid.Sibelius75")

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

Terms of Use Privacy Policy