Posts by roussel2nis
-
-
-
-
Hi GrandOrgue enthusiasts!
GrandOrgue 3.10 has been released. See the release notes for details. Some features added in this version.
https://github.com/GrandOrgue/…gue/releases/tag/3.10.0-1
As I'm quite a newbie - I discovered GrandOrgue two years ago - I would take time here to thank a lot some great people involved in the project for some time now.
Oleg Samarin for his great technical abilities to transform ideas into code in a minimum amount of time.
Lars Palo who is the active memory of the project and has clear idea of what GrandOrgue should be (and what it shouldn't).
Eric Turpault for his last contributions on Hauptwerk to GrandOrgue sample set conversion tool. See https://github.com/GrandOrgue/ODFEdit
Thanks also to all people around issues and discussions submissions to help us having feedback. I'm convinced we are going into the right direction, making the software able to run most of sample sets available! See you on Github (and in other places
) -
-
Hi everybody,
We are facing questioning about old Linux distributions support as github will give up ubuntu 18.04 on 2023-04-01. So, it won't be possible (easily) to release new version of GrandOrgue for old systems after that date.
A discussion has been opened by Oleg Samarin there: https://github.com/GrandOrgue/grandorgue/discussions/1334
We want to have your feedback on this. Thanks
-
Which version is actually running stable under Windows 11 64 bit?
Niederrheiner 3.9.4 which is the last one
-
This sample set has been released.
I hope ahall41 would have kindness sharing his work on demo sample set for GO.
Many thanks
-
GrandOrgue 3.9.3 has been released. See release notes for further details. https://github.com/GrandOrgue/…rgue/releases/tag/3.9.3-1
-
-
robertodelfrate is your problem solved?
-
Forgot to publish here but GrandOrgue 3.9.0 and 3.9.1 have been released.
https://github.com/GrandOrgue/…rgue/releases/tag/3.9.0-1
-
Quote
Im Prinzip läuft es genau darauf hinaus. Jeder (Sampleset-) Hersteller, der auf seiner Webseite nicht nur Hauptwerk, sondern auch GrandOrgue o. ä. unterstützt , wird von Brett Milan (MDA) boykottiert. Nachzulesen im Hauptwerk Forum in einem Beitrag von 2013
Ok, I understood this as : you cannot promote on your website other things than Hauptwerk.
I found that would be so much intrusive if it was true.
-
Mikelectric please re-read. Milan said that threads about GrandOrgue (or others) will be deleted from the forum.
He didn't speak about creators' websites or...
You could look at that sentence:
QuoteIf someone wishes to link to a site that promotes their instruments while also promoting other software then please feel free to announce this elsewhere on your own websites, but not here as it will be removed without warning.
That's just about moderation on Hauptwerk forum, nothing else.
-
Quote
m Prinzip läuft es genau darauf hinaus. Jeder (Sampleset-) Hersteller, der auf seiner Webseite nicht nur Hauptwerk, sondern auch GrandOrgue o. ä. unterstützt , wird von Brett Milan (MDA) boykottiert. Nachzulesen im Hauptwerk Forum in einem Beitrag von 2013:
It seems you haven't read well B Milan. He just spoke about the Hauptwerk forum.
-
Quote
Mit Piotr gibt es einen Hersteller, der GO-Sets erstellt! Die GO-Programmierer sollten mit ihm zusammen arbeiten und nicht auf GitHub-Meldungen warten! Da werden sie genug Input für die Weiterentwicklung bekommen.
Hier sind einige Gründe nachzulesen, was bei Hauptwerk besser läuftYou haven't seen the discussion thread I've done on that subject.
https://github.com/GrandOrgue/grandorgue/discussions/1162
Many remarks of Piotr have been answered.
I've also asked him directly what is missing in GO to make him back on it and never been answered. So, let's go forward and make the software ours like it has always been: open-source, made and shared by contributors, for users.
-
zu 2)
Piotr Graboswki sagt zu einigen seiner Samplesets, dass bestimmte Funktionalitäten, die in Hauptwerk vorhanden sind, in GO fehlen und das es deshalb keine GO-Version gibt.
In dem Fall könnte z.B. ein GO-Entwickler nachfragen, was genau fehlt. Hier den GO-Usern zu sagen, sie sollen bei GitHub ihre Wünsche äußern, finde ich ziemlich unpassend.
GitHub is the new home of GrandOrgue and has also discussions features, so, it's a way like another to discuss about features, like this forum. The difference is that's the official one and the one through requests will be adressed.
-
zu 1)
Wenn es am "Unvermögen der Anwender" scheitert, dann sollte sich der Programmierer die Frage stellen, ob er vielleicht versagt hat, eine Funktionalität verständlich zu implementieren
Of course.
But as said many times, that's collaborative work, through changes request and review processes. The more we have people that do both jobs, the more we can expect quality of work (that's not an absolute).
-
>Und warum lässt man die MacOS-Anwender, die noch die Intel-basierte Hardware der Jahre 2009 bis 2018 mit MacOS 10 verwenden und nicht schon wieder updaten können bzw. wollen, im Regen stehen?
GrandOrgue is built by GitHub and macOS ≤ 10.15 is no longer supported. A workaround makes it possible to build GrandOrgue for macOS 10.15 but ≤ 10.14 is not supported.
See [End of support of Mac OS 10.15](https://github.com/GrandOrgue/grandorgue/discussions/1149)
Old Mac -> old macOS -> old apps. New Macs with Apple Silicon are not supported either.
I'm glad there's GrandOrgue for macOS at all.
As said in the specific thread, automatic builds for those versions are no more supported by GitHub, but you can continue building new versions of GrandOrgue on your own. If someone has a better solution, I encourage to post it. Same answer for Silicon.
-
>I encourage you to post issues on GitHub
I asked, no answer.
Of course they have.
kerkovits user answered.
If you have still an issue, don't hesitate to ping.
