GO midi output

[e9925248]

I have published a new GO build, which includes MIDI output support:

https://sourceforge.net/projects/e9925248.u/files/GrandOrgue/
http://software.opensuse.org/download.html?project=home:e9925248:grandorgue&package=grandorgue

Coding has just been finished - testing is still going on.

 

[Ghekorg7 (Ret)]

Hi "e" , just got it OK.

I'll test asap and see that multi rank builds with this, also the pitch information override you posted about.
Big things going on !
Thanks for your continuing support and hard work on GO builds.

 

[Ghekorg7 (Ret)]

OK 'e', report :

I uninstalled 1026 x64 and installed this new one from you. All clear, no issues. It's the only GO version now on my system.

Opened ok loads OK and it warned me about loading earlier GO0.2 version stuff (coool !)
No warning with all my latest odf, except where I had added wrong integer values, for example : Stop001=001 ; Principal 8'
Deleting the ; Principal 8' and leave Stop001=001 gave no warnings (we discussed about that in the past)

Sound.
It found no Asio.... (left over from 1026...), so I switched to WASAPI analog out. I'll test the digital one when back in Athens...

With 1026 had set 128/48000 and with Wasapi this reads 20ms latency on GO.
Switched to 64/48000 to go down, still 20ms reading, but feels like 10~14ms even less , around 6ms

Had no problem at all playing with WASAPI , no cracks at all at 64/48000 for my older Intel T4400 dual core 2.2GHz
So far the largest set I loaded is my small custom v2 around 2GB allocated , lossless on.

Another thing I found :
I'm currently involved on a new sampling project, a 3m/p English type, and I started creating (for 1026) the first test odf (s).
There I had : PositionY= and PositionX= on manual without any numbers, for future repositioning if needed. Hehehe... opening with this new version I saw the keyboard on the upper left corner, as if I had typed PositionY=0, positionX=0 !
Two solutions : delete the "plain" Positions or indeed changing position of the keyboard by adding the relevant numbers.
1026 excused those "mistakes" by ignoring PositionX= ect without values :-D

Overall, so far I'm very pleased with this new version, though I would like to see the Asio support, mainly because I have many projects which rely on ReaRouteAsio x64 for my Reaper.

And speaking of Reaper, I did some test with this Midi out function to see what's going on.

I managed to record midi on Reaper going to GO and listening audio from GO's WASAPI configuration, then record audio with GO's rec function.
BUT, I wasn't able, so far, to do the oposite, ie play on GO and send Midi to Reaper for midi recording.... hmmmm (?)

The medium is the LoopMidi from Tobias. Set LoopMidi Port 1 on GO's midi out configuration.Midi in in Reaper from Port 1........
Probably my fault somewhere in the chain'... dunno......was already tired from many stuff here, so I'll try again tomorrow to see what did I step by step.
I kept the test recording (wav) for archive, I can upload it for you or anyone else interested. No editing at all.

 

[erikds]

OK 'e', report :

Another thing I found :
I'm currently involved on a new sampling project, a 3m/p English type, and I started creating (for 1026) the first test odf (s).
There I had : PositionY= and PositionX= on manual without any numbers, for future repositioning if needed. Hehehe... opening with this new version I saw the keyboard on the upper left corner, as if I had typed PositionY=0, positionX=0 !
Two solutions : delete the "plain" Positions or indeed changing position of the keyboard by adding the relevant numbers.
1026 excused those "mistakes" by ignoring PositionX= ect without values :-D

This resembles the behavior i experienced, concerning keyboard positioning, with the linux build from rev. 1072 when using your Dom Bedos derived dispositions.

All the best.

Erik.

 

[Ghekorg7 (Ret)]

Thanks Erik

Now I know how to update my files ! As you said, there were some keyboards travelling across the console :-D

 

[e9925248]

Sound.
It found no Asio.... (left over from 1026...), so I switched to WASAPI analog out. I'll test the digital one when back in Athens...

You have to ask JLD for a new ASIO build.

I managed to record midi on Reaper going to GO and listening audio from GO's WASAPI configuration, then record audio with GO's rec function.
BUT, I wasn't able, so far, to do the oposite, ie play on GO and send Midi to Reaper for midi recording.... hmmmm (?)

The MIDI output is designed for feedback to a console. Its not optimal for recoding, as you have to configure an appropriate feedback for each control element individually.

If you see MIDI problems, you could try to use Panic (or apply the settings via the setting dialog), as it reinitialisises all MIDI ports.

 

[Ghekorg7 (Ret)]

Thanks 'e'

Never, or to be true just a couple of times in three years, had to use the panic :-D
As I set-up thinkgs with Reaper I can do my (new) recordings Midi>audio. Can wait for a new Asio build, I'll talk with JLD.

For the time being I'll stay with this new build of yours and exprore it more.

Also, sorry I forgot to mention..., all those new temperaments are.... SUPERGREAT !

 

[e9925248]

Also, sorry I forgot to mention..., all those new temperaments are.... SUPERGREAT !

If somebody is missing any specific temperament, please provide a list of the derivation to equal temperament of the 12 semitones (starting with C) in cent (+ name and its suggested sub-menu), eg:

m_Temperaments.push_back(new GOrgueTemperamentCent(wxTRANSLATE("Werckmeister III"), group, 11.73, 1.95, 3.91, 5.87, 1.96, 9.78, 0, 7.82, 3.91, 0, 7.82, 3.91));

 

[Ghekorg7 (Ret)]

Another good tip !

This will help me now re-create the Fr.Julien 1690 Roquemaure peculiar temperament, with settings as were shown in ArtMedia's older site (had a copy somewere...).
I'll try to post those settings here asap.

MidiOut.
Yep no work as I tried with Reaper, but worked sending/receiving with my Holidays KBD (PSR203) some very basic stuff (PSR limits not GO's).

 

[e9925248]

MidiOut.
Yep no work as I tried with Reaper

GO expects, that
1) the MIDI out port has a stable name
2) it is enabled in the GO MIDI settings
3) it exists before GO opens the port (= before Load, Panic or apply of GO settings)
4) GO connects to the target - not the other way around.

So if the virtual MIDI port created by Reaper is persistent (not closed/destroyed/recreated/opened during GO runtime) and Reaper allows GO to connect to it [not Reaper tries to connect to a GO Midi output port], GO should be able to send MIDI to it.

 

[Ghekorg7 (Ret)]

Hmmmm, I 'll do the whole procedure from the beginning, following the above rules. AFAIK Reaper can do anything(....OK alomost....), so I'll set things to GO's rules.
I'll post asap as I travel back to Athens tomorrow.

 

[astazou]

Can wait for a new Asio build, I'll talk with JLD.

Looks like Jean-Luc isn't available.
I have a TDM toolchain installed, so I just built 1081 with ASIO without WASAPI for both W32 and W64.
I'm not allowed to upload files to GO on SourceForge, so I uploaded to my SF account.
Links are
http://sourceforge.net/projects/ast...ndOrgue_0_3_0_6_TDM64.win64.1081.exe/download for 64 bits

and
http://sourceforge.net/projects/ast...ndOrgue_0_3_0_6_TDM64.win32.1081.exe/download for 32 bits

I'm mainly using the 64 bits build with Pibrac sampleset, unfortunately limited to 1/P and no stop rail, so I can't tell if MIDI output works well.

Hope that helps

 

[Ghekorg7 (Ret)]

Hi Astazou,
Thanks for these
I'll go now to get 64...
My main thing now is that I'm very good with 'e' 's latest build with all its features and mainly because of its warnings that help me construct sets with faults at minimum possible, so they can work OK with both windows and linux.

1026 is great too and indeed was stable in my OS and more forgiving if I left a command without a setting after equals :-D

Also with 1026 I wasn't able to use properties on any .organ file and attribute it to open exclusively with GO (????). With 'e' 's build this was so easy (as with GOv02) which also opens faster. Also has soooo many temperaments, very well indexed to choose. Occupies more MB in HDD though

Are these 1081 builds of yours based on 'e' 's latest build with Asio instead of Wasapi ?

 

[Ghekorg7 (Ret)]

If somebody is missing any specific temperament, please provide a list of the derivation to equal temperament of the 12 semitones (starting with C) in cent (+ name and its suggested sub-menu), eg:

m_Temperaments.push_back(new GOrgueTemperamentCent(wxTRANSLATE("Werckmeister III"), group, 11.73, 1.95, 3.91, 5.87, 1.96, 9.78, 0, 7.82, 3.91, 0, 7.82, 3.91));

OK, I found Roquemaure's Quiorin A=415Hz Tuning table

So, it would be like this ? :

m_Temperaments.push_back(new GOrgueTemperamentCent(wxTRANSLATE("Quiorin"), group, 0, 82, 196, 294, 392, 497, 585, 698, 780, 893, 996, 1091))

 

[astazou]

Are these 1081 builds of yours based on 'e' 's latest build with Asio instead of Wasapi ?

Yes. I'm not really a C++ developer, so I only update my source tree from the repository on SourceForge.

 

[Ghekorg7 (Ret)]

Hi again Astazou

OK , It works FINE and SOUND ! Yes it's the same with Asio instead of Wasapi. It gives the same warnings and has the same behaviour.Sounds Great too.

THANKS !!

I still insist that I'm listening and feeling some difference between Asio and Wasapi....... Asio4all it's slightly cleaner on sound and faster on latency, or is just me I'm feeling this? :-D :-D

Anyway both versions are SUPER.

Now I have to re-do the Reaper Midi In/OUT test from the beginning to see again the Midi out function following Martin's instructions.

I'll post asap here...

 

[e9925248]

m_Temperaments.push_back(new GOrgueTemperamentCent(wxTRANSLATE("Quiorin"), group, 0, 82, 196, 294, 392, 497, 585, 698, 780, 893, 996, 1091))

First, please add a suggestion, in which (new) submenu the temperament should be put.

Syntactically, a semicolon is missing at the end.

The number don't look plausible: a d would 196 cent above a d in equal temperament. The numbers (digits after the decimal point are allowed) are the difference in cent to the 12 semitones in equal temperament, so anything above/below +/- 50 cent is probably incorrect.

You can look at the already implemented examples:
http://ourorgan.svn.sourceforge.net...rgueTemperament.cpp?revision=1059&view=markup

 

[e9925248]

I have a TDM toolchain installed, so I just built 1081 with ASIO without WASAPI for both W32 and W64.

I only consider TDM64 (= mingw-w64) as supported for building Win32 and Win64 version.
TDM (=mingw) only offers outdated windows headers - the old header may cause various build errors.

WASAPI should be buildable with TDM64 (try -DPROPERTYKEY_DEFINED as compiler flag). If you hit another error, I need all compiler errors.

 

[Ghekorg7 (Ret)]

First, please add a suggestion, in which (new) submenu the temperament should be put.

Syntactically, a semicolon is missing at the end.

The number don't look plausible: a d would 196 cent above a d in equal temperament. The numbers (digits after the decimal point are allowed) are the difference in cent to the 12 semitones in equal temperament, so anything above/below +/- 50 cent is probably incorrect.

You can look at the already implemented examples:
http://ourorgan.svn.sourceforge.net...rgueTemperament.cpp?revision=1059&view=markup

Yep, I know it would have a period, like 1.96 for D, but this is how it was on ArtMedia's site a couple of years back and as I found out even today prof. H.Maier gives the same numbers. That's why I posted as I found it.

So I'm guessing must be : 0, 0.82, 1.96, 2.94, 3.92, 4.97, 5.85, 6.98, 7.80, 8.93, 9.96, 10.91

Also I'm not sure to which category to apply..... It sounds like a 4th comma, but it plays good and Fm/Cm/Bbm/C and close to Wolf an Em/B. Quiorin was the brand that made the restoration in the 20th century, so it's not the original tuning I suppose.
But it looks like an evolving scale for zero to ten accordingly to C~B (?) Nevertheless it sounds very peculiar and characteristic at 415Hz.

Thanks for the link and advice ! and for your excellent latest build. I just love it.

 

[L.Palo]

Hi!

So I'm guessing must be : 0, 0.82, 1.96, 2.94, 3.92, 4.97, 5.85, 6.98, 7.80, 8.93, 9.96, 10.91

No, that's very unlikely... from the first description I'd believe that this is the normal temperament denotation system that has it's origin on C (0) and then the next note (C sharp) is the number of cents from C etc.

In GO we choosed to have the A as the reference note (like in a1=440 Hz) so all the numbers need to be shifted like mentioned in the comments to the feature request on sourceforge.

The method of converting the numbers to relative equalbeating and with a as reference:
0 -> 0 - 0 = 0 -> 0 + 7 = 7
82 -> 82 - 100 = -18 -> -18 + 7 = -11
196 -> 196 - 200 = -4 -> -4 + 7 = 3
294 -> 294 - 300 = -6 -> -6 + 7 = 1
392 -> 392 - 400 = -8 -> -8 + 7 = -1
497 -> 497 - 500 = -3 -> -3 + 7 = 4
585 -> 585 - 600 = -15 -> -15 + 7 = -8
698 -> 698 - 700 = -2 -> -2 + 7 = 5
780 -> 780 - 800 = -20 -> -20 + 7 = -13
893 -> 893 - 900 = -7 -> -7 + 7 = 0
996 -> 996 - 1000 = -4 -> -4 + 7 = 3
1091 -> 1091 - 1100 = -9 -> -9 + 7 = -2

And as it happens this temperament already exist in GO! And it's line reads:

m_Temperaments.push_back(new GOrgueTemperamentCent(wxTRANSLATE("Freres Jullien Organ, France (1690)"), group, 7, -11, 3, 1, -1, 4, -8, 5, -13, 0, 3, -2));

Kind regards

Lars P