Hi Graham and Lynn!

Thanks both of you for this info.
Although I am also very much interested in making a jOrgan front-end to HW, my goal is more towards a monitor-less solution and fiddling with exchangable stop-labels, because I get more and more worried about the environment, and I read somewhere that in touch-screens there are materials used that are becoming very rare.

Can you confirm this, or is it a bit exaggerated??

Many greetings from a snowy Holland, and Graham, be careful with all that snow over there !!

Geert

2010/1/6 Graham Harrison <fg.harrison@virgin.net>
Hi Lynn

This certainly looks worth following up - thank you.
First off I need to get another graphics card!

GrahamH


----- Original Message -----
From: "Lynn Walls" <lwalls@comcast.net>
To: <jorgan-user@lists.sourceforge.net>
Sent: Wednesday, January 06, 2010 1:20 AM
Subject: [jOrgan-user] Multiple Monitors (was: Getting started with j-organ)


> If you have TWO monitors on your computer, enter jOrgan Construct mode
> and built TWO console elements -- each one having the stops and other
> controls that you want to see on each respective console display.
>
> Then for each Console element, click on its Properties tab and locate
> its Screen property.  When you have more than one console you will see a
> drop-down selector in the value spec area of the Screen property.  For
> two display monitors defined on your computer you will see two choices:
> \Display0 and \Display1.
>
> Simply select one of these values for one Console element, and select
> the other value for the other Console element.
>
> Now, in FULL SCREEN MODE only, each Console element will display on its
> own monitor.
>
> CLW
> -------------------------------------------------------------------------
>
> Graham Harrison wrote:
>> I have just done a little experiment, and what David is proposing can
>> certainly be done.  i.e. It is relatively easy to use jOrgan as the GUI
>> for
>> selecting stops in a Hauptwerk organ - and creating a jOrgan disposition
>> is
>> certainly much easier than using the Hauptwerk Custom Organ Design Module
>> to
>> create a custom Hauptwerk virtual console.
>> However, I don't possess the hardware (graphics card etc.) to check
>> exactly
>> how one would present the left hand stop jamb on one monitor screen and
>> the
>> right hand stop jamb on the other screen.  In my experience it takes
>> quite a
>> bit of fiddling to get a full jOrgan disposition to sit centrally and
>> symmetrically on a single monitor screen in full screen mode - how would
>> one
>> go about getting half the disposition on one screen and the other half on
>> the other screen?  Has anybody done this satisfactorily?
>> If there is a way of doing it, I too would seriously consider touch
>> screens
>> as a solution to my problem of too few physical stops etc.
>>
>> GrahamH
>>
>>
>> ----- Original Message -----
>> From: "Sven Meier" <sven@meiers.net>
>> To: <jorgan-user@lists.sourceforge.net>
>> Sent: Thursday, December 31, 2009 10:50 AM
>> Subject: Re: [jOrgan-user] Getting started with j-organ?
>>
>>
>>> Hi David,
>>>
>>> sure, you can use jOrgan as a Midi relay in front of Hauptwerk as other
>>> users have already done.
>>>
>>> Just create a Console element, put Switches and Continuous element on it
>>> as needed and forget about all sound related features in jOrgan.
>>>
>>> Bernd and Paul have done marvellous jobs on creating their own skins,
>>> perhaps you can create your own and give something back to the jOrgan
>>> community?
>>>
>>> Have fun
>>>
>>> Sven
>>>
>>>
>>> Dr. David Pitches wrote:
>>>> Hello to all,
>>>>
>>>> I am contemplating, as a New Year project, the
>>>> construction of a digital practice organ using virtual
>>>> organ software. I'm hoping to have four manuals and pedals
>>>> and a PC running Hauptwerk with ultimately several of the
>>>> larger sample sets available interchangably, but I need a
>>>> solution for selecting stops according to the organ
>>>> loaded. Having effectively ruled out physical switches and
>>>> interchangable labels as too fiddly, I'm tempted by the
>>>> thought that having two 1920x1080 touch sensitive
>>>> widescreen monitors of 20 inches or more, rotated in
>>>> portrait mode, one either side of the keys, would be very
>>>> similar to the size of typical stopjams of larger organs.
>>>> I am considering having a third monitor over the Solo
>>>> keyboard to act as a digital music desk and as a means of
>>>> control (selecting organs, voicing etc).
>>>>
>>>> I was advised on the Hauptwerk forum that the intrinsic
>>>> organ design module is pretty complicated for non-computer
>>>> programmers and has certain limitations too such as
>>>> multiple release is disabled. I am therefore essentially
>>>> looking for how to create a graphical user interface with
>>>> the representation of stopknobs for a variety of different
>>>> organs, shown fullscreen on two large portrait-orientated
>>>> screens, that is capable of sending a midi-out signal or
>>>> equivalent for Hauptwerk to recognise when stops are
>>>> selected or deselected. A bonus would be if physical
>>>> combination pistons between the manuals could be used to
>>>> select stops (since again, if I correctly understand,
>>>> Hauptwerk doesn't let you do that for organs that don't in
>>>> reality also have combination pistons).
>>>>
>>>> So: is j-organ the right software package to let me do
>>>> this? I guess I don't need to control an entire organ ie
>>>> keys, pedals and swell etc since the midi input from
>>>> keyboards etc would presumably go straight into Hauptwerk,
>>>> it's just the stops that would be controlled via
>>>> touchscreen as opposed to physical switches. But I need
>>>> something that presents, on the left and right monitors, a
>>>> representation of the console jambs (of course, in the
>>>> case of say Cavaille-Coll consoles, I'd need to redesign
>>>> the stop layout as though the stops were arranged in a
>>>> portrait configuration rather than in terraces) - and that
>>>> converts the touched stops into a signal that tells
>>>> Hauptwerk to select the stops. The advice I was given on
>>>> the Hauptwerk forum was that j-organ probably fitted the
>>>> bill but that it was best to discuss using j-organ as a
>>>> midi interface for Hauptwerk on the j-organ forum rather
>>>> than the Hauptwerk forum. If anyone has had experience
>>>> doing this, or can advice me what the next steps should be
>>>> - or indeed, whether there are any other softwares "out
>>>> there" that I should look at instead, I would be most
>>>> grateful of your advice.
>>>>
>>>> Many thanks in anticipation! Organorak
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.Net email is sponsored by the Verizon Developer Community
>>>> Take advantage of Verizon's best-in-class app development support
>>>> A streamlined, 14 day to market process makes app distribution fast and
>>>> easy
>>>> Join now and get one step closer to millions of Verizon customers
>>>> http://p.sf.net/sfu/verizon-dev2dev
>>>> _______________________________________________
>>>> jOrgan-user mailing list
>>>> jOrgan-user@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>>>>
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Verizon Developer Community
>>> Take advantage of Verizon's best-in-class app development support
>>> A streamlined, 14 day to market process makes app distribution fast and
>>> easy
>>> Join now and get one step closer to millions of Verizon customers
>>> http://p.sf.net/sfu/verizon-dev2dev
>>> _______________________________________________
>>> jOrgan-user mailing list
>>> jOrgan-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.5.431 / Virus Database: 270.14.123/2594 - Release Date:
>> 12/30/09
>> 07:27:00
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and
>> easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev
>> _______________________________________________
>> jOrgan-user mailing list
>> jOrgan-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jorgan-user


--------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.432 / Virus Database: 270.14.126/2601 - Release Date: 01/05/10
07:35:00


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
jOrgan-user mailing list
jOrgan-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jorgan-user