Here's a video:
https://youtu.be/xSYADiCXL1o
Simple app. Only 14mb after repack.
Available for all platforms win, mac, Linux.
DO YOU WANNA TRY:
Download page:
https://github.com/Archie3d/aeolus_plug...ag/v0.1.12
What do you think about?
It's 0.1.12 version so many can be done yet.
And there is a version which runs on the Raspberry PI, so you don't even need to invest in a PC (neither Windows nor Apple)! And, while a couple of demonstration organ definitions (one three-manual, the rest two-manual) are included, there is also an editor which allows you to modify existing organ definitions, or even create your own from scratch (which can be a LOT of work!)
Details at: www.organnery.com
Some limitations with Organnery I've noted so far:
No provisions for borrowing or extended stops. Organs must be completely "straight".
No sub- or super-octave couplers. Unison only.
Console images created are somewhat rudimentary (but completely adequate)
However, there are demonstrations that can be played on YouTube, so you can get some idea what it sounds like.
Looks nice! I won't comment on the sound fidelity as I'm no organist, but I'd certainly use it in my own music.
Would you consider adding Scala file or MTS-ESP support? That's all I'm waiting for from Organteq but it's obviously not been a high priority. I see you have some hard-coded temperaments already so I imagine it would be reasonably straightforward.
And other "competition" which probably most people on this forum know but some might not
https://github.com/GrandOrgue/grandorgue
If Aeolus could be recompiled for MacOS, embedded with Jack Audio, etc, then yes.
A note to users regarding the Organnery project is that it does not support Raspberry Pi 4 series onwards, so it won't work. I spent a lot of time with that nightmare for linux and absolutely HATE IT. accessibility is completely impossible, so abandoned that one.
lew
If Aeolus could be recompiled for MacOS, embedded with Jack Audio, etc, then yes.
A note to users regarding the Organnery project is that it does not support Raspberry Pi 4 series onwards, so it won't work. I spent a lot of time with that nightmare for linux and absolutely HATE IT. accessibility is completely impossible, so abandoned that one.
lew
I already send request for iOS version to author of aoulus for PC.
He doesn’t have newest Mac to work on appliction for mac/iOS
lewisalexander2020 wrote:If Aeolus could be recompiled for MacOS, embedded with Jack Audio, etc, then yes.
A note to users regarding the Organnery project is that it does not support Raspberry Pi 4 series onwards, so it won't work. I spent a lot of time with that nightmare for linux and absolutely HATE IT. accessibility is completely impossible, so abandoned that one.
lew
I already send request for iOS version to author of aoulus for PC.
He doesn’t have newest Mac to work on appliction for mac/iOS
he doesn't need a top spec new mac, any intel mac from 2012 onwards will do, you don't always need the latest tools to test and develop. even a hackintosh would work well.
lew
If Aeolus could be recompiled for MacOS, embedded with Jack Audio, etc, then yes.
he doesn't need a top spec new mac, any intel mac from 2012 onwards will do, you don't always need the latest tools to test and develop. even a hackintosh would work well.
Hi, the project compiles fine for iOS, if you have a mac and an iPad, you can compile and deploy it yourself on your personal iPad. I have no means currently do publish it on Apple Store though.
just a quick update here.
Aeolus is available through the following link:
https://archie3d.github.io/aeolus_plugin/
you can download the VST plugin for Windows, Mac, etc and there is a standalone version also. good old github.
will be testing this out soon.
Also, GrandOrgue is now Build 3.12 and I have to admit, seems much better since last I checked a couple of years back. I'm in touch with them to look in to accessibility resource development to open doors for blind and sight impaired organists as that's my background.
lew
just a quick update here.
Aeolus is available through the following link:
https://archie3d.github.io/aeolus_plugin/
you can download the VST plugin for Windows, Mac, etc and there is a standalone version also. good old github.
will be testing this out soon.
Also, GrandOrgue is now Build 3.12 and I have to admit, seems much better since last I checked a couple of years back. I'm in touch with them to look in to accessibility resource development to open doors for blind and sight impaired organists as that's my background.
lew
Thanks for the link - didn't know that.
I tried the vst3 out with my studio computer (win 10 64 bit; Studio One v5 (latest version)) and my live computer (win 10 64 bit; Cantabile v3/v4 live host).
It worked fine in both cases and sounds really nice. I described the setup procedure with Cantabile in the Cantabile forum and added a demo video.
Nonetheless; probably I'll buy Organteq some day too.
lewisalexander2020 wrote:just a quick update here.
Aeolus is available through the following link:
https://archie3d.github.io/aeolus_plugin/
you can download the VST plugin for Windows, Mac, etc and there is a standalone version also. good old github.
will be testing this out soon.
Also, GrandOrgue is now Build 3.12 and I have to admit, seems much better since last I checked a couple of years back. I'm in touch with them to look in to accessibility resource development to open doors for blind and sight impaired organists as that's my background.
lew
Thanks for the link - didn't know that.
I tried the vst3 out with my studio computer (win 10 64 bit; Studio One v5 (latest version)) and my live computer (win 10 64 bit; Cantabile v3/v4 live host).
It worked fine in both cases and sounds really nice. I described the setup procedure with Cantabile in the Cantabile forum and added a demo video.Nonetheless; probably I'll buy Organteq some day too.
I've been testing this out, to be honest, I've heard better.
There's a disturbing lack of 16' stops and any modification work requires json script knowledge, midi configurations have to be made via scripting, etc. this is a pull of Aeolus for linux and to be honest, could be so much better. I've ditched it and don't support it as a musician. GrandOrgue as a multi-platform organ is quite decent, but from a blind persons's perspective, it's inaccessible.
lew
As an alternative to organteq you could try eplayOrgan. This has a built in organteq organ and is capable of being tuned to any temperament. There are also many other organs built in, many of which outperform organteq. There is a built in organ designer so you can even make an organ to your personal liking. It comes with a comprehensive organ sound font but you can alternatively use any other .sf2 soundfont.
There is no vst capability but it will run on any 64 bit Windows computer. Also runs on Linux or Mac under Wine.
eplayOrgan is completely free to download and use. Get it from my website:
https://midimusic.github.io
csw900
eplayOrgan is completely free to download and use. Get it from my website:
https://midimusic.github.io
Are you the author? Do you release only the binary or the source code too?
@dv
Thanks for your interest. Yes I am the author. I have not published the source code. Why on earth would you need it? However you will learn a lot by trying it out .
csw900
Thanks for your interest. Yes I am the author.
Thank you for sharing it and for responding.
I have not published the source code. Why on earth would you need it?
Strange that you ask such a question. These days software is either proprietary or open source, it's very uncommon to stumble in something that is given away at no price, yet closed source. It feels like a practice of the 90s.
Open source has gazillions benefits, and I'm not going to list them all here, just mentioning 3 things:
1) I am picky and I often find things that I don't like in software, as such I like open source because it allows me to change it as I feel important to me. If I think my changes can be useful (perhaps as an option) to others, I create PR to contribute back to the original project (one of the major advantages of open source: everybody can contribute and the project becomes better)
2) I run Linux and I've found that things with Wine sometimes work, but I've never found anything that runs optimally. I suspect for a real-time audio project like this it would be even worse. Having the source would allow me to evaluate the possibility of a native port.
3) Having the code allows people to build trust that there is no trojan or virus in the binary. It does not matter to me since my music computer is isolated, off the internet, and does not run anything other than pianoteq, organteq demo and fluidsynth, but I suspect it matter to others who do not have a dedicated "throw-away" computer.
@dv
Interesting comments but not convincing.
I already have versions of eplayOrgan which run natively on Linux and have found that wxWidgets has significant shortcomings which make a Linux version of eplayOrgan unworkable at present. The problems are with the graphics not the sound.
The last time I tried eplayOrgan on Linux under Wine it worked just as well as it did under windows - obviously you have not even bothered to try it.
As for improvements - if you tell me what needs improving I will improve it.
csw900
The last time I tried eplayOrgan on Linux under Wine it worked just as well as it did under windows - obviously you have not even bothered to try it.
Indeed I did not try it, but not because "I did not bother": simply my digital controller is broken at the time and I have only my acoustic piano.
I already have versions of eplayOrgan which run natively on Linux and have found that wxWidgets has significant shortcomings which make a Linux version of eplayOrgan unworkable at present. The problems are with the graphics not the sound.
Are you saying that Wine does not introduce any additional latency at all in the MIDI or in the Audio pipeline? That's interesting and not what I experienced last time I tried (obviously not with eplayOrgan, since I've just learned about it). As I wrote above it's impossible for me to test that at the moment.
Also, there are many experts who may be able to help and contribute to solve the shortcomings you mentioned, so that very reason is for you to make the code open, rather than keep it closed.
Interesting comments but not convincing.
As for improvements - if you tell me what needs improving I will improve it.
Of course this is your baby and you can do with it as you please, and the rest of the world can only be thankful to you for sharing whatever you want to share, if anything.
That said, your answer is unsatisfactory and does not explain why you are so secretive. I mean, I can speculate about some reasons, e.g. you want to have users as beta-testers, like when OrganTeq was in beta IIRC it was free and did not have the current limitations of the demo mode, and they did that because Modartt obviously wanted to eventually sell it. Nothing wrong with it, just that I believe you can gain more trust if you are more clear about your goals, strategies and tactics.
After all, both you and I are just "random strangers on the internet", I could be a troll or a competitor who wants to steal your code, or you can be somebody who wants to steal keystrokes from people, hoping to gain access to their credit cards (or worse). I mean, seriously, I'm not a troll nor a competitor, and I don't think you have any bad intention, in fact the reason I'm challenging you (rather than drop the conversation) is the hope that with your answer you will build trust in you! For everybody.
In any case, all the best to you and to your project!