I have a question about full‑screen mode. I’m using Fedora Silverblue, and when I start the mode via the menu Windows -> Toggle fullscreen mode, I get a different result than when I use the start‑parameter --fullscreen. I’ve attached two screenshots.
With the --fullscreen parameter, the GNOME panel remains visible.
When selecting the option from the menu, the panel is correctly hidden.
Am I doing something wrong? The panel should be hidden.
1. Screenshot: Menu -> Fullscreen https://ibb.co/sddqN1Z9
2. Screenshot: --fullscreen https://ibb.co/5XFP9bf4
Additionally, is it possible to start directly in the Jamb View view?
Thanks a lot!
]]>I'm looking at this pedalboard, apparently it's a bit smaller than their classical organ pedalboards and only 25 keys, but also cheaper and more portable.
I would like to keep the door open for the possibility of music outside the house and outside churches. You never know.
Regarding quality, can I expect the same as their 30-keys pedalboards?
And the keyboards, will it be enough to plug them in a powered MIDI hub and the pedalboard in a Lexicon Lambda audio interface?
https://cdn.djcity.com.au/wp-content/up...bda_lg.jpg
Sorry for the newbie questions, I just don't want to order the wrong equipment.
Thanks.
]]>first I want to thank you for releasing this great product. I am a long time Hauptwerk user, but decided to give your software a try since I really like the concept.
I find it is already better in terms of playability, which is of course expected from physical modelling.
The labials are already sounding very nice, but I think the linguals still need work, especially in the pedal registers.
I was surprised to find that Organteq doesn't seem to replicate the velocity based attack found on tracker organs.
Are there plans to simulate this behaviour?
(for those not aware: Tracker organs keys are linked directly to the valves regulating airflow, allowing for softer and harder attack [slower and faster onset of the airstream], you can even play pipes "partially" by pressing keys only to a certain point, allowing for a "overblown" sound, though I understand this cannot be replicated on a midi-keyboard.)
Another feature suggestion:
In Pianoteq you have the very handy compression slider.
I think it would be really nice to have a similar slider, kind of "master compressor" in Organteq, to be able to reduce the large differences in loudness between sparse and full registrations.
best regards, Wolfgang Laser
]]>- Ableton
- Logic Pro
In Logic Pro I noticed that Recit and Positive are panned to left and right channel.
Opening the template in Ableton the panning for Recit and Positive have no panning.
Why is that so ? I assume both templates should be identical.
I am not sure if I missed some tweaked parameters or missed anything else.
Modartt - can you check and let us know if this is a mistake or intended.
Another question would be: can you maybe tell us which of the presets exactly have been used for the audio examples on the organteq website? It just says ‚baroque‘ or „romantic“.
Thanks and kind regards.
Tim
]]>This is how it looks:
https://www.icloud.com/sharedalbum/fr-f...4CBC940198
My device has:
(A) 14 buttons for easy/quick access to the stop combinations, namely
on the lower row: 10 buttons, a button for each stop combination.
on the upper row: buttons for previous/next stop combination and previous/next bank.
The buttons are positioned in the same way as the corresponding touch screen buttons in Organteq’s Jamb View
(B) A knob for easy access to volume control.
It works as follow: when one of the 14 buttons is pressed, a note on/note off MIDI message is sent and the nearby LED flashes for 200ms to confirm the MIDI action. No need to have the LED lit longer, because the organist can see the current (active) stop combination on the screen. Moreover, my MIDI controller is USB powered, so it is not reasonable to strain the USB port for a LED light which nobody needs.
I attach a video showing how it works:
https://www.icloud.com/sharedalbum/fr-f...B7FBBF654E
The front panel has been made of PLA using a 3D printer. For the electronics I used an Arduino Pro Micro PCB and WS2812B individually addressable LEDs. The wiring has been designed by … Claude (free version), who also wrote the firmware code and explained me how to upload it. The price of the materials is very low, but there is a lot of work, especially precision soldering.
Why did I build this?
Why was I not happy with MIDI controllers available on the market?
First of all, the positioning of the buttons on the front panel of the available MIDI controllers is not at all suited for the Organteq interface. Usually such MIDI controllers have a 4x4 or 5x3 button matrix.
I saw that a very popular choice is Elgato’s Stream Deck MK2.
I did not try this device, but studying the specifications, I think that it is not optimal for Organteq use.
The main reason: Elgato’s Stream Deck is not a MIDI controller. It can be converted into a MIDI controller by installing a MIDI plugin. But the device requires the application Stream Deck running in the background, taking processor power, RAM and straining the USB port.
A simple MIDI controller (as mine) does not take any meaningful computer power and is natively compatible with any computer platform without any driver or application running in the background.
]]>Our best solution is to lean towards a flute based registration. The great is always playing broken chords to keep the choir in time.
Organteq has so many options that I can spend days chasing a registration that I think works but at our church does not. We are a Catholic Church in Perth Western Australia playing traditional and more modern Catholic approved hymns.
Does anyone have experience in using Organteq for hymns? Is someone able to assist with some suggested registrations please.
I face the uncomfortable reality of explaining to my wife, who is also our choir leader, that the investment we made in Organteq may not have been the sure fire answer I thought it would be.
Thank you for listening to me.
]]>At the moment I have a setup with 1 keyboard en one pedal board for the base.
Wen I play a base note (on one of the pedals) and play 4 notes at the same time on the keyboard all sounds fine.
But wihen I press 5 notes at the same time on the keyboard instead of 4 the base note stops playing. But the base note continues playing again when I release the 5th note.
And when I play 5 notes arpeggio on the keyboard (not together at the same time, but slightly after eachother but holdding the notes instead of releasing the notes) all six notes (that is including the base note) are audible and perfect.
Is there a setting to solve thius problem?
Thanks
Koen
]]>Many thanks.
]]>This is a playlist with 4 videos showing the digital organ which I built last spring (using Organteq) in full action:
https://www.youtube.com/playlist?list=P...kb0GhpfxrZ
The recording does not reproduce perfectly the beautiful/deep sound we had in the church. For two reasons:
First, I am an ignorant mathematician, not a sound engineer.
Second, for the recording I had only 3 mics, whereas the sound system has 8 (eight) speakers, namely:
- Two powerful full range speakers in front of the church, and
- 2+2 high/middle range speakers + 2 massive subwoofers mounted behind the church, at about 3 m heigh!
Since our church is quite small, I use a simple stereo system, so only 2 channels (3 speakers per channel).
The distance between the two front speakers and the six rear speakers is about 12m. For the connection I used a 20 m long ethernet cable and 2 baluns. No signal strength loss, no noise, perfect synchronisation!
The whole investment for the organ (including the 8 speaker sound system and the Italian made pedalboard) was about 5 500€, whereas restoring the old UK made pipe organ would cost many tens (maybe hundreds) of thousands of €!
Best regards,
Andrei
P.S. The image from the left is taken using a 200€ PTZ Tenveo camera (bought on Amazon) and the image from the right (which shows the manuals) is taken using an iPhone connected wirelessly to my Mac. This explains the latency of the recording from the right.
]]>