Hauptwerk Virtual organ incompatability

• Jul 14, 2013 - 12:10

This isn't necessarily a bug but I have found that when I try to play a file I have made in Musescore on the Hauptwerk virtual organ, It won't load. It said it detected an "unexpected meta-event".
Has anyone found a work around for that?


Comments

In reply to by ChurchOrganist

I guess it is. I have been able to download files from other sites and presumably done on other programs and they work ok except that I have to monkey around with the channel assignments to make them work right, I just downloaded a file from this site and it didn't work just like it didn't work with my musescore file.

In reply to by xavierjazz

OK. the MuseS Version is: 1.3 Revision: 5702 I am working with a Toshiba laptop with Windows 7. I write a piece of music for a 2 manual organ + pedals. I then Save it selecting "Standard MIDI File(*.Mid)". I then open Hauptwerk Version: 4.0.0.724 Free Edition and select St. Anne's Moseley.as my organ. When I try to load my MIDI file into it I get an error that says that my file " contains an unsupported MIDI meta event (Diagnostics hex meta event ID byte: 08.) Message code (for diagnostic purposes): 2586"
That is as far as I can go.I can't think of any other details that I have left out.

Thanks for the help by the way:)

In reply to by xavierjazz

I guess I can. It is a song out of our congregations song book that I was using as a test to see how it would sound in Hauptwerk. I was adding a peddle part but stopped when I couldn't load it. Where do you want it so that you know which one it is?

In reply to by Joen

I went to Preferences page and under the export tab I UNchecked the Expanded repeats check box under Export MIDI. Everything works fine now. Hauptwerk doesn't seem to like Expanded repeats.
Thanks all for your kind attention and help anyway. And maybe this may be a fix for someone else.
Take care
Joen

In reply to by Joen

Ok after a little digging I have found the following.

MuseScore appears to be using MIDI meta event 8 for a title string, whereas normally this meta event is used as a patch name and is immediately followed by Bank Select and patch select messages.

The normal meta event for a title string is 3

I will create an issue on this in the issue tracker later today

Hauptwerk, however should not be choking on it in this way - it should simply ignore the non-standard use.

In the meantime have you considered using one of the pre-release versions of MuseScore 2 and trialling the Aeolus Pipe Organ Synth?

That is pretty awesome, and will be even better when I've finished tweaking the stop definitions :)

HTH
Michael

In reply to by ChurchOrganist

As noted above I was able to find the problem and solve it. Hauptwerk now accepts my scores and plays them. The only concern is channel numbers which Hauptwerk uses to assign staffs to a manual. I have an other program to fix that and it works fine after that. As you may know, Hauptwerk uses actual recordings of individual pipes to create the actual sound of the organ and an interface to allow you to play it as though you were playing the real organ. And you have a large number of organs to choose from.
It comes standard with the St. Anne;s Moseley organ and you can download a free but diminished version of the Paramount 310
theater organ.

When you listen to these organs played you are listening to real recordings of individual notes. They both sound great and that is why I want to write music for them. My interest in music is great however my interest in music is exceeded only by my lack of talent.Life can be cruel that way. Hopefully this will be a way around that. Thank you for looking into this for me. I will look into Aeolus Pipe Organ Synth. It may be more interesting than I think.

Please take care
Joen

In reply to by Joen

Aeolus uses sophisticated additive synthesis algorithms to generate the sounds concerned, and it looks as though it is possible to use a Fast Fourier Transform analysis of a real pipe to import into the editor.

Unfortunately, currently the only available editor is in Linux, although one of the MuseScore community is currently working on an OSC version.

The benefit of this is that you have a pipe organ synth which takes up very little space in terms of CPU power and memory resources.

Do you still have an unanswered question? Please log in first to post your question.