___________________________________jOrgan-User Link

__________________________________________(Mailing List Recent Archive)

This web-page allows you to view most posts sent to the jOrgan-User Mailing List from mid-July 2021 onwards, and is read-only.

To post a Reply or start a new Topic, you need to be registered with the Mailing List. For instructions on registering and using the

Mailing List, click HERE. Your post will normally be sent immediately to all subscribers, but will not appear here until the web-page

is updated. This is done manually, and perhaps once a week. Some topics or posts may not appear, if considered not archive material.

To contact the Compiler of this web-page, send a post with the Subject Line, “To the jOrgan Link Compiler”.

The main jOrgan-User archive can be accessed HERE, or the jOrgan-Sound archive HERE. If you click on a month, you need to scroll

down to see the result. Don’t overlook the Search facility at the left. After doing a successful search, you will be given a list of posts

where the key wording is found. After you select a post, you will find at the bottom of the page an opportunity to view the thread

where that post belongs.

SCROLL DOWN TO VIEW THE CURRENT LIST

To view the newest post, click on the coloured text

PAST ARCHIVES (Click to access)

2023 Jul-Dec______2023 Jan-Jun______2022 Jul-Dec______2022 Jan-Jun _____2021 Jul-Dec

jOrgan website for new users___Sticky Post

Updates to jOrgan Discovery Website___By JohnR__ Newest post on 2024-04-10

Implementing a sustain pedal___By Brian Sweetnam__ Most recent post on 2024-04-01___9 replies

Midi kit supplier in Ireland___By Bob Brown__ Most recent post on 2024-03-25___7 replies

Bruce Miles' Cinema Organ___By Brian Sweetnam__ Most recent post on 2024-03-22___2 replies

Mailing List Issues___By JohnR__ Most recent post on 2024-03-20___1 reply

Reiterate Question___By Brian Sweetnam__ Most recent post on 2024-03-18___1 reply

Hammond B3___By Bill Skees___Most recent post on 2024-03-15___2 replies

Problem with jOrgan 4.2 for RPi 4B (64-bit)___By JohnR___Most recent post on 2024-03-14___4 replies

jOrgan 4.2 on RPi 5 running Bookworm___By Marc-Paul on 2024-03-12

j3.20 Stiehr-Mockers 2.0 not importing to version 4x jOrgan

___By Marc-Paul___Most recent post on 2024-03-10___4 replies

Fluidsynth 2.3.4 PortAudio ALL build for Windows jOrgan 4.0 64-bit users

___By Graham Goode___Most recent post on 2024-03-06___1 reply

Quick Raspberry Pi question___By John Kuhns___Most recent post on 2024-03-05___25 replies

jOrgan and a DAW, the next level...___By Alex Stone___Most recent post on 2024-02-14

jOrgan and a DAW___By Alex Stone___Most recent post on 2024-02-14___33 replies

Dual Touch Screen Monitors___By Bill Skees___Most recent post on 2024-02-05___16 replies

Fluidsynth 2.3.4___By Dr. Mark Bugeja MD___Newest post on 2024-01-28___2 replies

Fluidsynth Reverb Parameters___By Pascal Collet___Most recent post on 2024-01-26___2 replies

Crescendo Volume___By Jolly Zekkariya___Most recent post on 2024-01-16___5 replies

Setting up jOrgan in Ubuntu Studio___By Dave Mac___Most recent post on 2024-01-12___23 replies

text on stops___By Dr. Mark Bugeja MD___on 2024-01-11

Pedal Volume___By Jolly Zekkariya___Most recent post on 2024-01-10___4 replies

About version 4.x for windows___By Pascal Collet___Most recent post on 2024-01-09___9 replies

jOrgan 4.1___By Mark Bugeja___Most recent post on 2024-01-05___3 replies

Advice on jOrgan Skins needed___By JohnR___Most recent post on 2024-01-05___3 replies

_

jOrgan website for new users

From JohnR

This website has been created to make it easier for internet users to discover jOrgan and to start

using it. Its main pages are HOME, STARTING, ADDING, GALLERY, F.A.Q., THIS SITE and CONTACT.

The web address is https://jorgan.info

JohnR

______________________________________________________________________________________________________________ *

Setting up jOrgan in Ubuntu Studio

From Dave Mac on 2024-01-03 20:28

evening all,

I have reloaded an earlier laptop of mine with Linux Ubuntu Studio and opened up

jOrgan that has come with it.

So far I can't get jOrgan audio out. jOrgan itself seems to work.

jOrgan Fluidsynth controls in "build" section doesn't bring up Jack in its list of

audio inputs.

Equally when I go into the "Audio- System settings" in Ubuntu Studio there is no

"Playback Stream" for jOrgan. There is a Playback Stream for Firefox when I brought

up YouTube.

I found Fluidsynth in the list of apps in Studio but it looks like it has to be set

up to run with jOrgan and "see" Jack.

I tried to work out if jOrgan and the Fluidsynth that came with Ubuntu Studio were

32 bit or 64 bit but no luck

Has anyone had any experience with this? I would REALLY appreciate some help

thanks

Dave

______________________________________________________________________________________________________________

From JohnR on 2024-01-04 15:30

On 2024-01-03 20:28, Dave Mac wrote:

“I have reloaded an earlier laptop of mine with Linux Ubuntu Studio and

opened up jOrgan that has come with it.

So far I can't get jOrgan audio out.”

Hi Dave,

Welcome to the jOrgan Mailing List!

I think we need more information. Please copy the error log which jOrgan generates,

and paste it into your next post.

Follow the "Error Log" entry in the jOrgan InfoBase Index:

https://jorgan.info/base/e/Error_Log.html

Best wishes,

JohnR

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-05 11:35

Hello Dave:

I have been using Ubuntu Studio for about a year in a testing environment with

jOrgan 4.1. Audio output tests include up to 4 stereo pairs on a usb sound card...

and just the audio in a laptop. I also have RPi, Mac and Windows. Make sure Alsa

is selected as audio driver. For testing push the gain up to 1.

I have written instructions about multi channel audio previously which will be in

the forum.

Let us know what definition you are loading.

Kindest Regards

Marc-Paul

______________________________________________________________________________________________________________

From Mark Bugeja on 2024-01-05 11:42

On Fri, 05 Jan 2024 at 01:36, Marc-Paul wrote:

"I have written instructions about multi channel audio previously which will be

in the forum."

Shouldn't these be part of jOrgan.info?

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-05 13:09

On Fri, 5 Jan 2024 at 10:36, Marc wrote: "Let us know what definition you are loading."

Marc,

Definition? or Dispositon?

The jOrgan Disposition I am using is Rick Whatson's Christie.

thanks muchly

Dave

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-05 13:13

Mark,

I wasn't aware of the jorgan log earlier. I have now printed out the relevant

instructions and am working hard to familiarise myself.

I'm new to Linux in general and Ubuntu Studio in particular so its a very steep

learning curve for me.

regards

Dave

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-05 15:56

Thanks Dave...

...I will load the Christie Organ tomorrow and see what is necessary

to make it work in Ubuntu Studio.

Cheers

Marc-Paul

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-05 18:20

Marc-Paul

very kind offer and greatly appreciated.

All who are following this here is an update.

As I started getting my head around it all I realised that same as jOrgan is packaged

in Ub Stud so is Fluidsynth. and I suddenly realised today it had to be set up along

with jOrgan. I managed to track down the Soundfont file (still haven't found the

app.log file) and now I have the virtual keyboard in jOrgan appearing in the computer

audio output. Big development which was easily reached once I realised the issue.

HOWEVER jOrgan seems to be seeing the keyboards and pedal MIDI from the Teensy

microprocessor but there is no audio output from them.

It seems there is no Linux version of MIDI Ox so now scratching my head wondering

how to make sure there is input from those keyboards (standard USB music keyboards

into USB hub which have worked fine in Windows days).

regards

Dave

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-05 20:09

evening all,

further update clarifying an earlier statement

It seems from further checking in jorgan "build" that although the keyboards

are appearing in the dropdown configuration menu- they aren't talking to jorgan.

hunting like mad to work out how Ub Stud deals with MIDI

regards

Dave

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-06 07:14

Hello Dave:

On a clean install of Ubuntu Studio I downloaded jOrgan 4.1. I had to install

my network midi application as that's the way I distribute midi data. I downloaded

the Christie organ and placed it in "Public" as is my habit. I opened the Christie

organ and changed the driver to Alsa and selected my midi input. I pushed the

Volume up to 1. I previously set the default audio in Ubuntu to the internal audio

and tested for sound. I played the onscreen keyboard and got sound. I played the

midi keyboard and got sound.

A great help are the two little indicators in the lower right corner of jOrgan.

Midi in and Midi out. They flash at the presence of midi data key down and key up.

On "View" you can use "Debug" and copy to clipboard.

The computer I tested this on is an Intel i5 mac mini using built in audio.

So I guess I didn't help you any.

Best Wishes

Marc-Paul

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-06 17:12

Gday Marc-Paul,

Apologies for the deafening silence- I got caught up in my Saturday morning routine.

I really appreciate your effort. and it is of considerable value to me ... even if I'm

a dyed-in-the-wool Windows man (😂😂😂)

I've printed your email out and dot pointed your stages below and I'm about to investigate

those avenues.

thanks so much and I'll keep you posted

warm regards

Dave

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-07 08:07

Hi Dave...

...I am a certified tech and support Windows and Mac. I also operate Ubuntu

Studio and Rpi. All 4 on a daily basis. Please ask any questions you wish

as I am happy to help.

Depending on where you unpack the Christie organ... you may have to also reset the path to

the soundfont... the very bottom entry on fluidsynth in construct mode.

Best wishes

Marc-Paul

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-07 11:36

Good morning Marc-Paul

Thank you so much and I'm pretty sure I will be coming back later today for more help.

It is really appreciated. I'm slowly finding my way though it all.

warm regards

Dave

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-07 13:36

Good afternoon Marc-Paul.

well I'm back even sooner than I expected. I thought I was making headway but I realise

now that was illusory.

When I first brought Carla up to find my MIDI they were in the bottom left window, I

brought them up into the patch bay but I must admit I couldn't find what to connect them to.

however then I inadvertently closed Carla without saving that config; and now I have not

been able to bring those MIDI connections back.

I can play YouTube through the laptop speakers and also out through the USB

the virtual keyboard in jOrgan plays OK out to speakers

weirdly if I have the Qsynth window open I get a rather high pitched almost strangled

audio output which is playable on the USB keyboards which is definitely not from jOrgan,

when I close the Qsynth window it vanishes. And it plays in "touch sensitive " mode which

has never happened before.

search me

warm regards

Dave

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-07 15:55

Hi Dave...

...so that's great. jOrgan plays with the virtual keyboard thru

speakers... so you have sound.

I use Qsynth a lot. Remember that Qsynth accepts midi data and plays the soundfont

loaded in it. I have written extensive instructions in the forum for using jOrgan to

output MIDI data with a generic sound element and using Qsynth to host the soundfont

instead of fluidsynth. This means using jOrgan as a midi relay only. Qsynth setup

is a bit complicated. A block diagram would look like midi out from jOrgan to Qsynth

then audio to Jack via a2jmidid.

Using fluidsynth in jOrgan is quit a bit simpler. I use Qsynth for multi-channel output.

jOrgan should see your midi keyboard. Try plugging one keyboard into your computer

directly and see if jOrgan recognizes it. I could be the hub that's getting in the way...

just a test.

USB ports can appear and disappear... (depends on the hardware) sometimes simply

plugging the usb cable into a different port will bring it to its senses.

Best Wishes

Marc-Paul

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-07 17:08

Gday Marc-Paul

thanks for that. I've reverted back to fluidsynth and loaded it with the soundfile.

currently I have YT giving me audio and jOrgan is still playing on the virtual keyboard

jOrgan is seeing the keyboards (I didn't try a keyboard direct yet but I easily can if

necessary)

however when I attempt to patch the MIDI in Carla patchbay I find the engine isn't

running- when I attempt to start the engine I receive this

"Could not connect to Audio backend 'ALSA', possible reasons:

Current audio setup has no outputs, cannot continue"

I've obviously inadvertently changed something because originally I did find the MIDI

in the Carla patch bay.

regards

Dave

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-08 00:16 +16

Evening Marc-Paul,

well I'm nearly there. Found a setting in Carla which wasn't right (will need to

locate it again in morn) and I can now see all three keyboards and pedal Teensy in

Carla patch bay but quirkily enough only two of the keyboards are working!!!

will check for MIDI presence in jOrgan in morning

regards and thanks

DaveV__________MOST RECENT POST IN THE THREAD

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-10 18:40

Evening all,

I'm still struggling with getting jOgan working in Ubuntu Studio. The other night

I reached the point where suddenly I realised I had the first and third USB controller

keyboards working correctly through the internal speakers, but not the second keyboard

or the pedals using the Teensy microprocessor to provide MIDI pedals.

the virtual on-screen keyboards and pedals all work.

I can see MIDI coming into jOrgan on that first and third keyboard but not the second

and pedals.

I did no patching in Carla to achieve this connection it just happened.

I've been wondering if I need to patch MIDI in Carla-I can see all three keyboards and

Teensy pedals appearing as ports but no idea what to patch them to.

when I swing the virtual organ across to my WIndows personal laptop all three keyboards

work fine without changing anything, as do the pedals except that after a few seconds the

pedals crash jOrgan- presumably my personal laptop does not have the computing reserves

to handle it.

thanks

Dave

______________________________________________________________________________________________________________

From John Beach on 2024-01-11 01:05

Try disconnecting the one and three keyboards to see if the system recognizes the second

and pedals. Make sure that, in jOrgan, your channel numbers for the USB keyboards are

set to default (probably #1), but it should identify each keyboard by type. If they are

all the same type (manufacturer), it, still, recognizes each according to the jOrgan

division. The channel numbers for division (keyboards) in jOrgan will be 1,2,3,4,

But the MIDI channel numbers for those keyboards must be the manufacturer's default.

Otherwise, they will not work.

Hope this helps.

John Beach

______________________________________________________________________________________________________________

From JohnR on 2024-01-11 07:08

Hi Dave,

I'm not sure what your problem is. But see if this jOrgan InfoBase page helps:

https://jorgan.info/base/e/Enumerate.html

Best wishes,

JohnR

______________________________________________________________________________________________________________

From RickW on 2024-01-11 11:57

Hi Dave

As John has mentioned, "Enumerate devices" might have something to do with getting the

last aspects functioning for your setup in jOrgan.

Go to: View - Configuration (this will bring up the "Preferences" window)

Select "Midi"

Tick both "Cache devices" and "Enumerate devices"

Close jOrgan and reboot your operating system.

On a fresh start, look in File - Customize...

Check the "Device" dropdown list for each division of the organ.

Experiment with with which #number device correctly relates to the physical position

of your keyboards.

Just to recap for anyone following along.

This "Enumerate devices" function (not activated by default) makes jOrgan allocate a

#number (eg. #1, #2...) to each MIDI device jOrgan sees as active in the operating system.

Multiple generic MIDI devices all have the same name in the operating system. Without

activating this function, jOrgan only shows 1 device of identical named duplicate devices.

By adding a #number to each name, each device gets a unique name.

I hope this now gets everything working for you.

You have done a great job to get a failing Windows laptop to install Ubuntu Studio as its

operating system and get jOrgan working in a completely new environment, in such a short

timeframe.

Regards

Rick

______________________________________________________________________________________________________________

From Dave Mac on 2024-01-12 09:57

Morning all

Wasn't it Charlie Brown from Peanuts who said "Into every life a little rain must fall

but this is ridiculous??"

After taking note of and working over everyone's latest suggestions without success I

finally decided late yesterday to do a total reinstall of Ubuntu Studio which wasn't

overly difficult. Except that where I'm positive jOrgan had been part of that package

first time I couldn't find it second time (and no I hadn't been drinking!). So a

download of jOrgan 64 bit soon sorted that.

In quite a short time I had jOrgan WORKING on Ubuntu Studio this morn and I really

appreciated all the suggestions of the last few days because they enabled me to work

straight through in an informed manner this time. Last time I started out with no idea

at all. And also thanks Rick for your kind words- your unflagging support and

encouragement over many years has brought me to this point.

HOWEVER as I sat down to triumphantly enjoy my success- the moment my feet touched the

pedals jOrgan fell over as before. The skin stays up- but it is dead. The sin of

assumption has hit me again. I had assumed my Windows personal computer was the issue

but it seems the fault is in jOrgan or peripherals.

The fault appeared out of nowhere... it all worked bearably well on my personal Windows

laptop (in lieu of organ laptop which had failed)- I hadn't played with any settings-

I went away for a few days and when I returned to the organ jOrgan would fail every

time I started playing the pedals.

I'm still enormously grateful the organ laptop is functional again because it makes

life much simpler. But I need to sort the pedal issue.

Any ideas?

many thanks and warm regards

Dave

______________________________________________________________________________________________________________

From Dr. Mark Bugeja MD on 2024-01-12 10:38

I thought I had sorted the latest fluidsynth 2.3.4 to work with jOrgan 4.01. Apparently

I was wrong. I get nothing but fluidsynth failure no matter what I did with it, jOrgan

and java. I guess I have to abandon this update of FS until someone (usually it is

Graham Goode) adapts it as a backend update. I did put my request to him in a private

message. I hope he can spare a few minutes for the community which I trust he would.

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-12 11:36

Hi Dave...

...personally, I would troubleshoot it like any issue. Find the possible

midi problem by unplugging the other keyboards and use only the pedal midi

interface and see if jOrgan still crashes. It could be the midi interface

and not jOrgan as an example. I have found that Ubuntu Studio is not as

good at handling faults as Windows.

Congratulations on all your work.

Something that was not mentioned if you use enumerate is that you have to redo your

midi connections in jOrgan. The same goes if you were using enumerate and then turn

it off.

Best Wishes.

Marc-Paul ____MOST RECENT POST IN THE THREAD

______________________________________________________________________________________________________________*

Advice on jOrgan Skins needed

From JohnR on 2024-01-03 21:45

Hi all,

John Maher and I have been working hard creating the jOrgan soundfont for Mark Bugeja’s

latest VPO – a modern German pipe organ installed in a church in Malta. We have nearly

finished the soundfont.

I am finding the sound very pleasing, and look forward to having it on my home console.

Neither of us is very experienced with jOrgan Skins. I have started with the Classic

skin and begun to add things as necessary. Mark supplied graphics, but we have to get

them into the jOrgan framework.

I have started with the Stop image, and have uploaded to Dropbox a folder with a small

disposition file and the skin needed for it. Here is the link to download the folder:

https://www.dropbox.com/scl/fo/k4kcdhbmzz6bbekxc1ofx/h?rlkey=p4xg03d8vbkmw6ixx1e412jj1&dl=0

If you place the disposition file and the skin folder into the one location on your

computer, and double-click on the disposition file, you will be able to see and operate

the stop (if you have a working version of jOrgan installed). There is no audio associated

with this. Below are lines in the XML Skin file related to the Stop switch. “stop0”

indicates Stop off. "Blank off.png" is the image for Stop off. I have added the numbering

to make it easier to refer to the lines in question.

My particular concerns are these:

1. I have tried increasing the size of the text by changing the “12” in lines 34 and 92,

but doing this has made no difference. How can the text size be increased? Also, how

would one discover what other fonts are available? (I have just noticed that the version

of the Classic Skin I have used does not include a font file. Could this be the reason

I can't change the size?)

2. How can I give the text lines just a little more width, if needed?

3. How can I place the text higher up on the image of Stop Off?

4. How can I place the text lower down on the image of Stop On, so that the text appears

to move down the same amount as the stop does?

A short explanation from someone of the main terms being used in the XML file would be useful

for any folk who wish to make up their own Skins. This could lead to a tutorial being created

for the jOrgan InfoBase (e.g. button, border, anchor, padding, font style).

<style>

<name>stop</name>

<layers>

<button>

5 <binding>active</binding>

<layers>

<composite>

<layers>

<image>

10 <file>Blank off.png</file>

<border>

<top>0</top>

<left>0</left>

<bottom>0</bottom>

15 <right>0</right>

</border>

<anchor>CENTER</anchor>

<fill>NONE</fill>

<width>0</width>

20 <height>0</height>

<padding>

<top>0</top>

<left>0</left>

<bottom>0</bottom>

25 <right>0</right>

</padding>

</image>

<text>

<alignment>CENTER</alignment>

30 <binding>name</binding>

<font>

<name>Arial</name>

<style>1</style>

<size>12</size>

35 </font>

<color>

<red>0</red>

<green>0</green>

<blue>0</blue>

40 </color>

<antialiased>true</antialiased>

<anchor>CENTER</anchor>

<fill>NONE</fill>

<width>75</width>

45 <height>75</height>

<padding>

<top>0</top>

<left>0</left>

<bottom>0</bottom>

50 <right>0</right>

</padding>

</text>

</layers>

<anchor>CENTER</anchor>

55 <fill>NONE</fill>

<width>0</width>

<height>0</height>

<padding>

<top>0</top>

60 <left>0</left>

<bottom>0</bottom>

<right>0</right>

</padding>

</composite>

65 <composite>

<layers>

<image>

<file>Blank on.png</file>

<border>

70 <top>0</top>

<left>0</left>

<bottom>0</bottom>

<right>0</right>

</border>

75 <anchor>CENTER</anchor>

<fill>NONE</fill>

<width>0</width>

<height>0</height>

<padding>

80 <top>0</top>

<left>0</left>

<bottom>0</bottom>

<right>0</right>

</padding>

85 </image>

<text>

<alignment>CENTER</alignment>

<binding>name</binding>

<font>

90 <name>Arial</name>

<style>1</style>

<size>12</size>

</font>

<color>

95 <red>80</red>

<green>20</green>

<blue>20</blue>

</color>

<antialiased>true</antialiased>

100 <anchor>CENTER</anchor>

<fill>NONE</fill>

<width>75</width>

<height>75</height>

<padding>

105 <top>0</top>

<left>0</left>

<bottom>0</bottom>

<right>0</right>

</padding>

110 </text>

</layers>

<anchor>CENTER</anchor>

<fill>NONE</fill>

<width>0</width>

115 <height>0</height>

<padding>

<top>0</top>

<left>0</left>

<bottom>0</bottom>

120 <right>0</right>

</padding>

</composite>

</layers>

<anchor>CENTER</anchor>

125 <fill>BOTH</fill>

<width>0</width>

<height>0</height>

<padding>

<top>8</top>

130 <left>8</left>

<bottom>8</bottom>

<right>8</right>

</padding>

</button>

135 </layers>

<anchor>CENTER</anchor>

<fill>NONE</fill>

<width>0</width>

<height>0</height>

140 <padding>

<top>0</top>

<left>0</left>

<bottom>0</bottom>

<right>0</right>

145 </padding>

</style>

Best wishes,

JohnR

______________________________________________________________________________________________________________

From JohnR on 2024-01-05 06:46

Hi all,

I have good news. I tried using Mark’s stop images on a skin other than the Classic,

and it obviously works, at least in a fashion, so I am now well on the way to

solving the issue for this VPO. Once I have nailed down the actual parameter values,

I shall pass the solution on to Mark:

a working stop image, with text that can be controlled as to position and as to font

size and type. Mark has generously offered to take over the work of creating the skin.

Best wishes,

JohnR

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-05 07:14

JohnR and Mark:

I would simply like to offer my gratitude for your work... from which so many people

will benefit. I have never created a skin.

Kindest Regards

Marc-Paul

______________________________________________________________________________________________________________

From Dr. Mark Bugeja MD on 2024-01-05 08:28

On 04/01/2024 21:14, Marc-Paul via jOrgan-user wrote:

“JohnR and Mark:

I would simply like to offer my gratitude for your work... from which so many

people will benefit. I have never created a skin.

Kindest Regards

Marc-Paul”

Hi Marc-Paul,

It is uplifting to get such feedback every now and again. A lot of work is involved

often by more than one individual, hundreds of hours of work, sound editing that hurts

the ears and drives the mind to near madness, a great deal of knowledge and much trial

and error when software lack what it takes to solve specific problems and having to go

through very long and winding routes to get to where one needs to go.

Needless to say, the software we have is indispensable even with the limitations - don't

get me wrong - but I feel there is room for improvement. Another free rival software has

been taken over from the original developers and is being upgraded as needs arise and

requests made for new features and a new organ building software has finally been created

facilitating the job considerably. For jOrgan that never had its own integrating sound

engine and creating an sf2 font file for fluidsynth is already a stumbling block in sample-

set creation.

There comes a time when any piece of software, jOrgan being no exception, needs re-visiting

and a nudge forward to meet demands. If it does not, it will inevitably fall by the wayside.

It would be a great pity if that happens.

Mark__________MOST RECENT POST IN THE THREAD

______________________________________________________________________________________________________________*

jOrgan 4.1

From Mark Bugeja on 2024-01-05 11:41

It appears that the latest version of jOrgan is 4.1. Is there one for windows?

______________________________________________________________________________________________________________

From JohnR on 2024-01-05 12:52

On 2024-01-05 11:41, Mark Bugeja wrote:

“It appears that the latest version of jOrgan is 4.1. Is there one for windows?”

Hi Mark,

The answer is, "Yes". Its full name is jOrgan-4.0.Beta1 and it was created by Sven

to allow jOrgan easy use of Fluidsynth Version 2.

The 4.1 was created by Sven for use with the Raspberry Pi 4B. It is 64-bit. It also uses

Fluidsynth Version 2. But just before 2023 ended, with the discovery that Raspberry Pi

now has Fluidsynth Version 3 being installed by default, Sven created jorgan_4.2_arm64

to cope with this situation.

My impression is that Sven intends to create only 64-bit versions of jOrgan from now on.

The easiest way to get to the jOrgan downloads page is to do a search on "jorgan files".

Best wishes,

JohnR

______________________________________________________________________________________________________________

From Dr. Mark Bugeja MD on 2024-01-05 13:08

Thanks John,

I do have 4.0.Beta1 (64x with FS 2.2.8). I was first alerted to a possible update

when I loaded your files and got a warning whilst using 4.0.b1. I searched sourceforge

but did not find a windows version for 4.1.

I do install 64x version of software when the option between 32x and 64x exists.

Can FS 3 be used with 4.0.b1 (for windows)? I suppose not!

Regards

Mark

______________________________________________________________________________________________________________

From Dr. Mark Bugeja MD on 2024-01-05 14:33

I have successfully installed FS 2.3.4 (I had to create an xml file and relocate

the corresponding files in the same structure as 2.2.8) but cannot find any FS 3

for windows.__________MOST RECENT POST IN THE THREAD

______________________________________________________________________________________________________________*

Pedal Volume

From Jolly Zekkariya on 2024-01-07 18:19

Greetings jOrgan community!

Could anybody be knowing how I can lower the volume of one stop. Specifically the

Bombarde is too loud in the pedal division. I would much like to reduce its volume

so it can blend well with other registrations.

Regards,

Jolly Avishai

______________________________________________________________________________________________________________

From Chris Pearson on 2024-01-08 01:42

Hi, Jolly

There are two ways to do this.

What I would consider the best way is:

1. Open the disposition as normal. (I would suggest making a copy first)

2. Click on the "construct organ" icon, (top left of screen)

3. Click on "View" at the top of the screen and in the drop down list, select

"References" and "Messages", if not already showing.

4. Now click on the stop who's volume you want to alter, in your case the Bombarde.

5. The Bombarde should now appear in the References panel. With "References TO elements"

selected.

6. Double click on "Bombarde"

7. The "Messages" panel should now show a list of items.

8. Find the message "Note played" and in the MPL column against it will be

"set 144, set pitch, set xx". Where "xx" is the volume of the note, a number

between 0 and 127.

9. Click with your cursor just after this number, backspace to clear the number

and enter a lower value, (higher to make in louder) I usually adjust in 10's

with, and then a lower value.

10. Exit construct mode and save.

11. Test and adjust accordingly by repeating steps 2 to 10.

The other way is to amend the sf2 file.

Hope this helps!

Regards

Chris Pearson

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-08 01:47

Hello Jolly...

...it would be helpful to know the platform and version of jOrgan

you are using. i.e. Windows, Mac, Rpi etc. Have you built your

own disposition or are you using one of the downloadable ones.

The answer in a general way is yes. You can edit the soundfont and reduce the volume.

Best Regards

Marc-Paul

______________________________________________________________________________________________________________

From John Beach on 2024-01-08 06:34

You can, either, modify the volume of the instrument or preset in Poly phone Soundfont

editor, or in jOrgan, make a volume control, uniquely, for the bombard stop. Either has

its different advantages.

The latter would allow for variable changes in loudness in jOrgan, while the former

would not. If you can set the volume in Poly phone to be in balance with the other

stops, that is likely to be preferred.

John Beach

______________________________________________________________________________________________________________

From Jolly Zekkariya on 2024-01-10 01:56

Thank you Chris Pearson

It has absolutely worked! Great advice you gave.

Thankful!

Jolly__________MOST RECENT POST IN THE THREAD

______________________________________________________________________________________________________________*

About version 4.x for windows

From Pascal Collet on 2024-01-08 03:16

To protect your privacy remote resources have been blocked.

Hello, first of all "best musical wishes" to all that contribute to this project.

I want to migrate from 16 bit version to 32 bit version (as new computer allow this).

- Step 1 : have tested 16 bit version and it work fine.

- Step 2 : loading, extact and install "jOrgan-4.0.Beta1-installer-amd64"

- Check with "NORDEN SCHNITGER" dispositon but no sound comes out (with a midi keyboard,

see activation of the key on the virtual keyboard and also try without success on the

virtual keyboard on screen)

Gives an error "could not load soundfound" (have check the location of SF2 in construct

mode and that's the right directory and name). In construct mode / Fluidsynth sound

(properties), there is no "audio driver" selectable (and, of cours, "audio device".

In configuration (preferences) for Fluidsynth, there are no backend available.

Have download version 2.3 of fluidsynth and copy in jOrgan/lib/fluidsynth. I so the

backend and select it. Restart jOrgan wihtout success.

Is there an help/guidlines to install this program ?

Thanks for the care.

Pascal C.

Belgium - Rixensart

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-08 04:05

Hello Pascal:

I appears you are moving to the 64bit version of jOrgan. Do you have the 64bit version

of Java installed?

You can check in the Control Panel/Java/Java/View

jOrgan already has Fluidsynth in it.

Best Wishes

Marc-Paul

______________________________________________________________________________________________________________

From John Beach on 2024-01-08 07:44

You must be sure that you do NOT mix a 32-bit version of Java RE with a 64-bit version

of jOrgan. You must install Java RE 64-bit and jOrgan version 4.1 Beta 1 64-bit.

Otherwise, it will not work. Access the Error Log and it will inform you of what the

error or problem is, generally, with a "failed" or "failure" message. If you copy the

information to clipboard you can paste it in the body of the email post to this forum

for help if you need it.

John Beach

______________________________________________________________________________________________________________

From Pascal Collet on 2024-01-09 01:59

After reading your advice, i'd check the configuration. There were two versions of java,

a 32 bits and a 64 bits who's active. So after deinstallation of both and jOrgan. I could

re-install the 64 bits and jOrgan 4. And now, it works fine.

Apologize for my mistake and thank to take care of my problem.

regards

Pascal C.

______________________________________________________________________________________________________________

From Mark Bugeja on 2024-01-09 02:02

I'm assuming you had a 32 x Java installed in the Program files directory instead of

the 64x

______________________________________________________________________________________________________________

From Pascal Collet on 2024-01-09 04:03

32bits was in Program (x86)

64bit s was in Program Files

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-09 04:20

Regarding versions of jOrgan and Java:

The location of Java is the secret to running 32bit and 64 bit side by side. If you

specify the location of Java like this as an example:

"C:\Program Files (x86)\Java\jre1.8.0_321\bin\java.exe" -jar "c:\jOrgan3211_32\jorgan.jar"

You can run any version you wish. I have 2 versions of jOrgan each 32bit and 64bit running

from my desktop in Windows 11p. You must be careful about the backends.

Best wishes

Marc-Paul

______________________________________________________________________________________________________________

From RickW on 2024-01-09 15:55

Regarding different "bits" of Java.

It is my understanding (in a Windows environment) if there are both 32 bit and 64 bit

versions of Java, that the last version of Java installed prior to installing jOrgan is

the version of Java that will be linked automatically when starting jOrgan (whether it

is suitable or not for jOrgan).

This can be manipulated by a user who understands setting Path commands.

I must admit that I know nothing about creating installer packages, but it would seem to

me that it should be possible for an installer package to check for the correct package

and install it if needed. (this is done by other software I use).

I have also been suggesting for well over 10 years that the jOrgan Windows installer

package should install some of the package files in different places to what it does.

(again, I don't know what is involved to make this change)

It seems to me that altering these two things would greatly improve the chances of a first

time user of jOrgan having sucess.

Maybe it is left as a hurdle to keep out those who don't show enough commitment.

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-09 16:20

A further note about Java.

In the Windows Control Panel/Java/Java/View you can activate or de-activate an individual version.

Best Wishes

Marc-Paul____MOST RECENT POST IN THE THREAD

______________________________________________________________________________________________________________*

Dual Touch Screen Monitors

From Bill Skees on 2024-01-09 02:11

At last I have acquired two touch-screen monitors. Ultimately I hope to use them

with Allman’s multi-multi-stop disposition. Meanwhile I am thoroughly enjoying playing

Rick Whatson’s excellent Christie disposition FS 3MP V320 03.

Problem is that Christie and the other dispositions I have tried seem to see only one

monitor in the customize mode. I can’t figure out whether the “elements” mode can help me.

I am using a Mac Book Air with OS 10.11.6 and jOrgan 3.20.

Could anyone give me some guidance here?

Thanks,

Bill

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-09 03:32

Hey Bill...

...I wish I could help, but my oldest OS X is Mojave 10.14 and I use

iPads as external monitors... which solves the touch need. I am very

interested to see if anyone offers help.

Best Wishes

Marc-Paul

______________________________________________________________________________________________________________

From Howard A. Ashley on 2024-01-09 04:24

Hi Bill (The Bill?),

I use Windows for jOrgan but Macs for other things. I've never set up

dual monitors in Mac OS but it should be fairly intuitive. Are the

monitors working when not in jOrgan? Windows gives you the option of

configuring dual monitors in various ways: as a mirror of each other

or as an extended continuous space. My assumption is to treat the two

monitors as one large extended space. The touch is configured

separately in an appropriate part of the 'Settings'. You should be

able to interact with both monitors and make sure the computer

recognizes touch input from each. About the only aspect of dual

monitor use where jOrgan itself gets involved is that "Full Screen" mode

has to be in force for you to see the second screen. In Windows F11

toggles 'full screen' on and off. Hope this gets you closer.

______________________________________________________________________________________________________________

From Andrew Larkham on 2024-01-09 04:38

Hi Bill.

I've done this in Windows...

From memory.

In jOrgan construct mode.

Add 2 additional screen. (Might be called display or something) I call mine Left and

Right but leave the original screen as was.

You then need to copy the elements from the Original screen to the appropriate new screen.

This can be frustrating!

Assuming your OS has detected both screens when you go into each screen property you should

be able to select Display 0 or Display 1

F11 should then give you 2 screens!

Good luck.

Andy

______________________________________________________________________________________________________________

From Howard A. Ashley on 2024-01-09 05:18

Hi Andrew,

It should not be necessary to take the steps you have outlined when using

an existing disposition. If you are creating the disposition, yes, you would

need to construct those elements, but you would then also have to construct

the skins for it and assemble all the new elements that would allow it to

function as an interface. Most people don't want an identical copy of the

first display on the second monitor, they want a left and right pair of

'jambs' like the real organ does. This usually means the first monitor's

'skin' has to be modified to reflect that it now only controls half the organ.

My assumption is that the disposition Bill is using already has all the dual

monitor functionality necessary built in. If not, then a second monitor cannot

be used without a lot more work.

______________________________________________________________________________________________________________

From Andrew Larkham on 2024-01-09 05:42

Hi Howard.

It's personal choice really.

I found it useful to still have the original display as:

1 it made it easier to copy paste to the new displays.

2 you had a way back if something goes wrong.(and I found it does)

there is no problem leaving it alone.

Andy.

______________________________________________________________________________________________________________

From RickW on 2024-01-09 16:03

Hi Bill

Nice to see you still active with jOrgan.

I am pleased people still find the Christie disposition useful.

I have not yet tried to use two screens with virtual organ.

Can I suggest that going into construct mode, you should be able to simply start drag-and-

dropping stops on your screen further to the right to stretch a single "console" view across

two screens.

As has already been suggested, you could also create another "console" element and copy-paste

stops to the new screen.

Regards

Rick.

______________________________________________________________________________________________________________

From RickW on 2024-01-09 16:10

A further thought.

The magnification factor of jOrgan can be adjusted in the "Customize" settings, and

individual "elements" can have their size adjusted in Construct mode.

Some experimentation will be needed to get this all to balance.

Someone mentioned doing this dual screen application would require changes to the "skin".

This is not the case at all.

Regards

Rick.

______________________________________________________________________________________________________________

From Bill Skees on 2024-01-16 05:44

Both touch screen monitors are operational with a dedicated Mac Mini running OS 10.14.6

I think I could have the configuration I wanted if I could get either of these two things

to work:

• in jOrgan display two consoles at once (the consoles show up in the customize 2nd

screen with screen/displays settings)

• in Mac OS stretch the same window over two monitors.

Any thoughts?

Thanks,

Bill

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-16 07:09

Hi Bill...

In my not so humble opinion, Mojave is the best OS that Mac has ever released. And the

Mac mini can be upgraded with 16gb Ram and a SSD( Intel Core i5). It works with jOrgan,

Qsynth and Loopback which is how I distribute audio.

System Preferences/Displays/Arrangement and check the "Mirror Displays" box.

That should get you what you want.

Best Wishes

Marc-Paul

______________________________________________________________________________________________________________

From Bill Skees on 2024-01-16 08:17

Thanks for thinking this through for me, Marc-Paul. I also am happy with Mojave.

The problem for me with "Mirror Displays” is that I want the two displays to show two

different windows, in effect I want a left console and a right console like you would

have on a large church organ or a large theatre organ. I have physical push buttons

below each keyboard manual for combinations and generals, but I want the “wings” (left

and right consoles) to house the tabs for the individual voices.

Don’t worry though, if it can’t be done, then it can’t be done.

Thanks again and best wishes,

Bill

______________________________________________________________________________________________________________

From Andrew Larkham on 2024-01-16 08:45

Just a thought....

In console properties have you selected display0 for one and display1 for the other?

Andy

______________________________________________________________________________________________________________

From Howard A. Ashley on 2024-01-16 16:51

Hi Bill,

I was attempting to tell you how I've seen it done in the dispositions I've used.

I suspected what you were after. Why don't you download one of Rev. Stratman's large

organ dispositions: American Classic Organ or English Cathedral organ and see how he

does it. And, yes, I found that using the extended desktop is the way and in the

jOrgan program using the "full screen' option. With your background you will have it

in a cinch if you download a working example of what you want to accomplish and

reverse engineer your own from it.

______________________________________________________________________________________________________________

From Marc-Paul on 2024-01-16 16:54

Hello Bill...

I have played around with Stratman Stiehr-Mockers / Jeux d’orgues 2. It has several consoles.

My thought is if you could cut the console graphic right down the middle one could achieve

what you are interested in.

______________________________________________________________________________________________________________

From RickW on 2024-01-16 17:42

Hello Bill

I have tried some things and found the following.

I have 2x AOC (USB-C) 15.6" touch screens on Windows 11 set as extended desktop.

USB-C is supposed to be able to provide monitor power, video signal and touch control,

but to get a second screen to function I need to provide one of the screens a second USB

cable. I have not yet got to the bottom of this, but it seems that my Intel NUC (computer)

is only able to send the triple function signal out of one of its two USB-C ports.

Once I do get both screens displaying, the touch function on the right screen only works

on the taskbar and not on any applications running on the right screen. The mouse is able

to activate functions on the right screen though.

With regard to jOrgan and the Christie disposition.

I made a copy of a disposition file then went into "Construct Mode". I turned off all other

display tabs so the drag and drop element edit screen is the only thing shown in the display.

I then started highlighting sections of tabs and dragged them around, moving the Solo and

Great to the right and moving other sections as needed. I went back and forth from Construct

mode to Play mode to see what things looked like. Once I was close, I went into "Customize"

mode and increased the display size (It had been set to 0.8, I found 1.0 was good). then some

more back and forth.

Once close, I found that putting the display size back down allowed me more screen room to

move things, but once positioned where I wanted them I put the display size back to 1.0.

The screen layout looks good across the two screens and is significantly larger than the

cramped single screen.

I can't "touch" on the right screen, but that is a hardware problem, not jOrgan.

If I set jOrgan to Full Screen it only fills the left screen, so half the console is missing,

but with the jOrgan window dragged to fit across both screens it looks good.

I only spent about half an hour fiddling, and was quite pleased with the results.

I do have the "Settings" Tab in the Christie disposition, but in this experiment I couldn't

make it display on the second screen.

What have you tried so far?

Regards

Rick

______________________________________________________________________________________________________________

From Bill Skees on 2024-01-17 04:58

On Jan 15, 2024, at 4:45 PM, Andrew Larkham wrote:

"Just a thought....

In console properties have you selected display0 for one and display1 for the other?"

Hi Andy,

Yes I did, but apparently jOrgan will not display both at the same time.

Bill

______________________________________________________________________________________________________________

From Andrew Larkham on 2024-01-17 05:09

Hi Bill.

That's strange...

I have 2 touchscreens and can make each console display on separate screens.

Possibly hardware?

I'm using Win10.

Andy

______________________________________________________________________________________________________________

From RickW on 2024-01-17 13:42

A link to pictures of my dual screen experiment posted on Facebook jOrgan group.

https://www.facebook.com/groups/692660577561309/permalink/2542523089241706/?mibextid=Nif5oz

Regards

Rick.

______________________________________________________________________________________________________________

From Mark Bugeja on 2024-01-17 16:16

Try right click on one of the screens and select appropriate display.

______________________________________________________________________________________________________________

From Dr. Mark Bugeja MD on 2024-01-17 16:23 +19

I noted that that this is possible in full screen mode. I am currently using Win 11

and jOrgan 4.0 beta1.

______________________________________________________________________________________________________________

From JohnR on 2024-02-05 16:33

I have taken the liberty of including here an excerpt from RickW's recent post to

the jOrgan Facebook Group, because of its relevance to this thread:

"I have been using the Windows Project setting of Extended Desktop, and have solved

the Touch issue for the second screen. I did a search and found the solution.

In Control Panel - Tablet PC Settings, Configure - Setup... and follow the prompts.

It asks you to touch one screen then the next. All fixed."

Best wishes,

JohnR______MOST RECENT POST IN THE THREAD

______________________________________________________________________________________________________________*

text on stops

From Dr. Mark Bugeja MD on 2024-01-11 07:28

How can one apply two different text styles on a single stop eg 2 colours for different

parts of the text?

(NOTE FROM JOHNR: I did not receive this post from Sourceforge for some reason, but

I did receive it as an email. I replied by email.)

______________________________________________________________________________________________________________*

Crescendo Volume

From Jolly Zekkariya on 2024-01-16 00:12

Greetings jOrgan community,

I appreciate all the help I have been receiving from this forum that has made me a

better user by the months.

A recent issue I am experiencing is about the crescendo volume.

I am using the Dynamic Wind disposition with jOrgan 3.21-beta1 on Windows 10.

The crescendo volume seems to have its own registrations therein because even when

I don't have any stops active, once the volume is up by even a few bars, there is sound.

I thought the crescendo is supposed to amplify what has already been selected. I could

be wrong on that!

I need help in trying to get more volume from my registrations. From customization I am

already at 0.8 gain.

Is there a way, I can have the crescendo volume do that for me; amplify what I have

already selected. (Or in a way, increase my gain?)

Thanks,

Jolly Z. A

______________________________________________________________________________________________________________

From Roy Radford on 2024-01-16 00:44

Hi, Jolly,

I've not been doing much of this sort of thing for several years now but,

so far as I remember, a Crescendo pedal has its own set of stops and

engages progressively louder ones independently of any user stops.

Have fun,

Roy. (UK)

______________________________________________________________________________________________________________

From Jolly Zekkariya on 2024-01-16 00:54

Thanks Roy,

Yes, I've found out it does have its own registrations. I guess, I'll have to increase

the individual stop volumes to get my registrations louder.

______________________________________________________________________________________________________________

From John Beach on 2024-01-16 02:54

Crescendo, as differentiated from sforzando, should be effectuated by the use of the

swell pedal with the stops that are activated in the swell division.

However, years ago, the construction of a crescendo was a progressive-stage, numbered

sequence of regulators and activators of referenced combinations and/or stops comprising

the build-up of the crescendo with stops from any division of the organ. This is more

akin to the sforzando pedal where the build-up is in graduated stages of added stops,

with a series of green lights that indicate the specific level at which the pedal is,

in the progression.

John Beach

______________________________________________________________________________________________________________

From Dr. Mark Bugeja MD on 2024-01-16 02:55

Hi Jolly,

I think you are mixing a crescendo with a swell pedal. They are two different things.

It is the swell pedal that increases the volume only (usually of the swell, hence the name,

or positive or solo divisions - each having its own "swell pedal"); a crescendo pedal, on

the other hand, adds pre-designated sequence of stops, with more stops being added as the

pedal is pressed down.

Mark

______________________________________________________________________________________________________________

From Jolly Zekkariya on 2024-01-16 05:04

Thanks for the clarification.______MOST RECENT POST IN THE THREAD

______________________________________________________________________________________________________________*

Fluidsynth Reverb Parameters

(WAS About version 4.x for windows)

From Pascal Collet on 2024-01-26 07:58

hello, See below about fluidsynth and its parameters.

On 19/01/2024 10:34, Pascal Collet wrote:

Indeed, I would like to re-install version 32 (it seems possible to have both versions

and to choose the active one). With the 64-bit version, I cannot find the right parameters

for fluidsynth reverberation, and have re-use the same for the four main (level, room,...)

as in version 32 bits (the sound does not decrease regularly). I will look to see if there

is a description of all the settings. There was a discussion about this in the past.

______________________________________________________________________________________________________________

From RickW on 2024-01-26 09:52

There is nothing odd about reinstalling Java solving Fluidsynth issues.

In a Windows environment, the last installed "version" (either 32 bit or 64 bit) has the

correct "Path" link.

Having both 32 bit and 64 bit of Java installed is no guarantee it will work. It is only

the last installed version that has correct "Path" links.

It is possible to get both versions running and active on a system, but to do so requires

creating DOS Batch files to address the correct "Path" when starting different versions of

jOrgan.

I don't know how to tell you how to write the DOS batch files. I just know that it is

necessary, and that the last installed version is the only one that will work

"automatically" without needing a DOS batch file.

Regards

Rick.

______________________________________________________________________________________________________________

From JohnR on 2024-01-26 12:37

On 2024-01-26 09:52, RickW wrote:

"There is nothing odd about reinstalling Java solving Fluidsynth issues."

Thank you, Rick, for replying to this post and to many others on the List. I think that

Pascal has moved on from that matter, and is now asking about what the Fluidsynth Reverb

parameters mean.

I shall try to address this.

Note that all the parameters must be in the range 0-1.

LEVEL controls the level of the reverberation output from Fluidsynth accompanying the

"straight" output.

"0" means there will be no reverb signal output.

I suggest something in the range 0.1-0.2, but this is up to each user. Just bear in mind

that a number of users find the cyclic modulation (of phase?) produced by the Fluidsynth V.2

to be annoying. The higher the LEVEL setting, the more obvious it will be. High settings of

this parameter may cause the sound to build up in an obviously delayed way, which I think

can sound unnatural.

ROOM controls the "size" of the space being synthesized. "1" may run the risk of causing

uncontrollable feedback. I suggest using anything up to about 0.95 - but even this much will

produce the effect of a very large cathedral.

DAMPING tries to emulate the way reverberation is pitch-selective: treble sounds become

attenuated more than bass sounds. Settings are often found in the range 0.2-0.3 . I think

it would be interesting for someone to do a test on various settings of this parameter,

and report back.

WIDTH controls (I think) the panning of the reverb signal compared to the straight signal.

I normally just use "1", which I think means that the two signals will be spread across

the sound field in an equal fashion. It would be interesting to hear people report on much

smaller settings (causing a narrowing of the reverb towards the middle, I think).

For the record, I think that the sound quality of the Fluidsynth V.2 reverb is much higher

than that of Fluidsynth V.1, even with that modulation. I don't really notice it when music

is being played. Of course, if you are holding down just single notes, on a single stop, it

is a different matter altogether.

Best wishes,

John______MOST RECENT POST IN THE THREAD

______________________________________________________________________________________________________________*

Fluidsynth 2.3.4

From Dr. Mark Bugeja MD on 2024-01-27 22:37

Fluidsynth has recently been updated to version 2.3.4 (September 2023).

jOrgan still depends on PortAudio which is based on FS 2.1.0 or Fluidsynth 2.2.8.

I imagine that it would help us get better sound quality out of these backends if they were

updated accordingly to utilise the latest FS version.

In my ignorance to what is required, I thought I could download FS 2.3.4, amend the old

backend xml to include the updated files and transfer the respective files in the same

structure as 2.2.8 but that did not work out. I got to see it in jOrgan's configuration

of FS but there is no sound and "Fluidsynth failure" is reported by jOrgan. So there must

be more to it than what I did. I tried..... 🙁 .

Sven? Graham?

Mark

______________________________________________________________________________________________________________

From John Beach on 2024-01-28 02:54

Has any progress been made regarding the change of the parameters that cause the reverb,

above a setting of 10-15 in jOrgan, to, objectionably, alter the speed of the looped wave

files of engaged stops?

This has been our problem with Fluidsynth. For users with Creative Labs soundcards, it

is possible to get good reverb with a Creative Sound version of dispositions. However,

you do have to use the Soundfont Bank Manager to load the Soundfont(s) of the disposition,

manually, and use the audio console app to set the reverb. It is of a higher quality than

Fluidsynth which can be acceptable if level is kept between 10 and 15.

Both the Audigy 5 RZ and the Audigy 2 (ZS) can be used with the same driver from the

5 RZ. If using with the 2 ZS, install the driver, manually, by unzipping the "audio" file,

navigate to the "wdm" file and select it, right click, then, "install." Reboot and you are

good to go.

John Beach

______________________________________________________________________________________________________________

From Mark Bugeja on 2024-01-28 05:11

Perhaps you might find your answer on the fluidsynth website:

https://www.fluidsynth.org/

______MOST RECENT POST IN THE THREAD

______________________________________________________________________________________________________________*

jOrgan and a DAW

From alex stone on 2024-02-09 04:05

Hello, I'm currently trying to run Jorgan, and give it messages from a DAW (Muse4).

OS: AVL-MXDE (Linux)

Jorgan version: 4.1

Disposition: English Cathedral organ.

Midi port connecting Jorgan to Muse4: Virtual_midi 1.0 (midi channels 1-6)

I've set up 5 tracks, for the manuals and pedals, each one with a different midi channel,

through a single mid port.

When I enter the customize wizard and navigate to the Switches tab, I can press a key,

with the mouse, in the vertical keyboard of the Muse midi editor, and a yellow icon

appears in the "activate" cell. So Jorgan knows "something" is connecting to it.

However, when i add a midi note to the canvas in the Muse Midi Editor, which corresponds

to the note from which i sent the message, nothing happens.

Example, for the 5 presets, plus the "clear" preset, I clicked on C0 to A0, representing

six white notes to match 5 plus 1 presets.

C0 is "clear", the rest are the presets. I add a note at D0, expecting Jorgan to recognize

the midi note message, and select the first preset.

None of this works.

Has anyone tried this, or is currently using a similar setup, and if so, where am I going

wrong? (I assume user error, by default)

Alex.

______________________________________________________________________________________________________________

From JohnR on 2024-02-09 09:11

Hi Alex,

Welcome to the jOrgan Mailing List!

Have you followed the INSTRUCTIONS FOOTNOTES a) Use of the Customizer, at this address:

https://jorgan.info/INSTRUCTIONS.pdf

Best wishes,

JohnR

______________________________________________________________________________________________________________

From alex stone on 2024-02-09 09:39

Hello John.

Yes, I've been through the footnotes, but it doesn't say anything about assigning

midi program changes in a DAW (digital audio sequencer) to Jorgan presets. It only

refers to physical midi hardware, unless i've misunderstood.

Alex

______________________________________________________________________________________________________________

From JohnR on 2024-02-09 10:11

Hi Alex,

Does this indicate that your intention is to use only one preset at a time?

A separate question- have you used the jOrgan MIDI Monitor (set to Input messages)

to verify that the expected program change messages are getting through?

Best wishes,

JohnR

______________________________________________________________________________________________________________