No sound using timidity

[marcusantonius]

Hi everybody,

I cannot get any sound out of rosegarden (e.g. when trying to play the examples which came with it). I am running 64 Studio 3.0 (Beta3), and have a M-Audio 1010lt soundcard. What I did:
1) Start Jack
2) Start Rosegarden
3) In Jack, I connect the Rosegarden General Midi Device to Timidity Port 0 (in the Jack configuration the default Midi-Driver is set to none, do I have to change this?)
4) I load an example and press play, but I cannot hear any sound.

Recording via my Midi-Keyboard works (I can see the notes in the editor, but again cannot hear them when  I press play). Using Hydrogen or Tuxguitar works, so I think the Timidity installation is fine.

What am I doing wrong? Thanks in advance,

Markus

Here some information from rosegarden about my system

Rosegarden 1.7.3 - AlsaDriver [ALSA library version 1.0.16, module version 1.0.18a, kernel version 2.6.29-1-multimedia-amd64]

JackDriver::initialiseAudio - JACK sample rate = 44100Hz, buffer size = 1024
JackDriver::initialiseAudio - creating disk thread
JackDriver::initialiseAudio - found 8 JACK physical outputs
JackDriver::initialiseAudio - connecting from "rosegarden:master out L" to "system:playback_1"
JackDriver::initialiseAudio - connecting from "rosegarden:master out R" to "system:playback_2"
JackDriver::initialiseAudio - found 2 JACK physical inputs
JackDriver::initialiseAudio - connecting from "system:capture_1" to "rosegarden:record in 1 L"
JackDriver::initialiseAudio - connecting from "system:capture_2" to "rosegarden:record in 1 R"
JackDriver::initialiseAudio - initialised JACK audio subsystem

  ALSA Client information:

    14,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype 2, ptype 655362, cap 99]
    24,0 - (M Audio Delta 1010LT, M Audio Delta 1010LT MIDI) (DUPLEX) [ctype 2, ptype 589826, cap 127]
    128,0 - (TiMidity, TiMidity port 0) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    128,1 - (TiMidity, TiMidity port 1) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    128,2 - (TiMidity, TiMidity port 2) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    128,3 - (TiMidity, TiMidity port 3) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    129,0 - (TiMidity, TiMidity port 0) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    129,1 - (TiMidity, TiMidity port 1) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    129,2 - (TiMidity, TiMidity port 2) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    129,3 - (TiMidity, TiMidity port 3) (WRITE ONLY) [ctype 1, ptype 2, cap 66]

Creating device 0 in Play mode for connection 128:0 TiMidity port 0 (write)
Default device name for this device is MIDI software device
Creating device 1 in Play mode for connection 128:1 TiMidity port 1 (write)
Default device name for this device is MIDI software device 2
Creating device 2 in Play mode for connection 128:2 TiMidity port 2 (write)
Default device name for this device is MIDI software device 3
Creating device 3 in Play mode for connection 128:3 TiMidity port 3 (write)
Default device name for this device is MIDI software device 4
Creating device 4 in Play mode for connection 129:0 TiMidity port 0 (write)
Default device name for this device is MIDI software device 5
Creating device 5 in Play mode for connection 129:1 TiMidity port 1 (write)
Default device name for this device is MIDI software device 6
Creating device 6 in Play mode for connection 129:2 TiMidity port 2 (write)
Default device name for this device is MIDI software device 7
Creating device 7 in Play mode for connection 129:3 TiMidity port 3 (write)
Default device name for this device is MIDI software device 8
Creating device 8 in Play mode for connection 24:0 M Audio Delta 1010LT MIDI (duplex)
Default device name for this device is MIDI external device
Creating device 9 in Record mode for connection 24:0 M Audio Delta 1010LT MIDI (duplex)
Default device name for this device is MIDI hardware input device
Creating device 10 in Play mode for connection 14:0 Midi Through Port-0 (duplex) (not connecting)
Default device name for this device is MIDI output system device
Creating device 11 in Record mode for connection 14:0 Midi Through Port-0 (duplex) (not connecting)
Default device name for this device is MIDI input system device
    Current timer set to "system timer" with timer checks
AlsaDriver::initialiseMidi -  initialised MIDI subsystem

    Current timer set to "system timer" with timer checks
AlsaDriver::setRecordDevice - successfully subscribed device 9 as record port

  ALSA Client information:

    14,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype 2, ptype 655362, cap 99]
    24,0 - (M Audio Delta 1010LT, M Audio Delta 1010LT MIDI) (DUPLEX) [ctype 2, ptype 589826, cap 127]
    128,0 - (TiMidity, TiMidity port 0) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    128,1 - (TiMidity, TiMidity port 1) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    128,2 - (TiMidity, TiMidity port 2) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    128,3 - (TiMidity, TiMidity port 3) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    129,0 - (TiMidity, TiMidity port 0) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    129,1 - (TiMidity, TiMidity port 1) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    129,2 - (TiMidity, TiMidity port 2) (WRITE ONLY) [ctype 1, ptype 2, cap 66]
    129,3 - (TiMidity, TiMidity port 3) (WRITE ONLY) [ctype 1, ptype 2, cap 66]

[D. Michael McIntyre-3]

On Sunday 21 June 2009, marcusantonius wrote:

> Recording via my Midi-Keyboard works (I can see the notes in the editor,
> but again cannot hear them when  I press play). Using Hydrogen or Tuxguitar
> works, so I think the Timidity installation is fine.
>
> What am I doing wrong?

Actually, I think what you're probably doing wrong is making the assumption
that because Hydrogen and Tuxguitar work, the Timidity installation is fine.

This suggests the opposite to me, and I think it might be broken.  The most
likely suspect is that if Timidity is trying to connect directly to the audio
hardware via ALSA, it will fail since JACK is running, because this hardware
only accepts one connection at a time, and JACK will monopolize the hardware.

The solution to that one from the command line is to start Timidity with
something like:

  timidity -iA -Oj

Another possibility is that it might not have a soundfont installed, or might
not be configured properly out of the box.  I'm a bit rusty on those issues,
since I don't actually use Timidity myself.  When I need a General MIDI soft
synth, I tend to use QSynth, which you could try yourself if Timidity
continues to give you trouble.  I imagine 64 Studio probably has the Fluid
Soundfont package by now, and that works well with QSynth (and can be made to
work with Timidity too, though the details of how also escape me at the
moment.  Someone just explained this recently, but I'm afraid I've forgotten
everything.)
--
D. Michael McIntyre

------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[Ilan]

Michael,
I would also like to use Timidity for the simple reason that it seems to come bundled with Rosegarden.
In fact I am using Qsynth because it is the only thing which gives me sound.

I have Rosegarden configured so that it automatically starts JACK for me, which is very convenient.
Then I go into Patchage and see that Timidity is connected to the General Midi out, which is what
Rosegarden uses for a default. So I disconnect Timidity and connect Qsynth and everything works.

The thing is I would like to make it completely automatic for my wife's use, since she understands music and not computers. If I could get Timidity to work it would be very simple for her: double click on a rosegarden file and up comes Rosegarden all configured properly. Not start Rosegarden, start Qsynth, start Patchage and then make the proper connections.

I suspect Timidy might be missing a sound font, but try as I may, either my efforts to install one haven't worked, or something else is wrong.

In any case Rosegarden is fantastic software, even though there is MUCH to learn.

Ilan

[D. Michael McIntyre-3]

On Monday 29 June 2009, Ilan wrote:

> I would also like to use Timidity for the simple reason that it seems to
> come bundled with Rosegarden.

It's not bundled with Rosegarden.  Some distros set it up to run out of the
box.  Ubuntu is supposed to do this, for example.  If TiMidity (or QSynth) is
running, Rosegarden typically picks it up and connects it to the default
playback device.

> Rosegarden uses for a default. So I disconnect Timidity and connect Qsynth
> and everything works.

You can connect Rosegarden's default device to QSynth and save that as your
default studio.

> The thing is I would like to make it completely automatic for my wife's
> use, since she understands music and not computers. If I could get Timidity
> to work it would be very simple for her: double click on a rosegarden file
> and up comes Rosegarden all configured properly. Not start Rosegarden,
> start Qsynth, start Patchage and then make the proper connections.

I haven't played with it in years, but if you're open to trying different
distros, one clever thing I always liked about Musix was the way Marcos set
it up where you clicked one icon to get all of this up and running and ready
to go.

--
D. Michael McIntyre

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[Ilan]

Michael,
Your guess is correct that I am using Ubuntu 9.04.

I decided to take your suggestion and try to implement it.
I setup Qsynth to connect to the General Midi output and setup Patchage to display the results.
Then I saved that as my default studio.

As I expected, starting Rosegarden didn't start either Qsynth or Patchage.
Again the goal is for my wife to be able to double click on a rosegarden project file and that would bring up her chosen composition with all else that is necessary, i.e. Qsynth and possibly Patchage (although she doesn't actually need Patchage).

Quite possibly this is asking too much, but since you suggested changing the default studio I thought I would give it a shot.

Thanks,
Ilan

[Jim Cochrane-8]

On Mon, 29 Jun 2009 22:07:28 -0700 (PDT)
Ilan <ilan.tal@...> wrote:

>
> Michael,
> Your guess is correct that I am using Ubuntu 9.04.
>
> I decided to take your suggestion and try to implement it.
> I setup Qsynth to connect to the General Midi output and setup
> Patchage to display the results.
> Then I saved that as my default studio.
>
> As I expected, starting Rosegarden didn't start either Qsynth or
> Patchage. Again the goal is for my wife to be able to double click on
> a rosegarden project file and that would bring up her chosen
> composition with all else that is necessary, i.e. Qsynth and possibly
> Patchage (although she doesn't actually need Patchage).

I suspect that it's possible to do this by writing a shell script that
starts Qsynth (and anything else needed), then starts Rosegarden. (?)

>
> Quite possibly this is asking too much, but since you suggested
> changing the default studio I thought I would give it a shot.
>
> Thanks,
> Ilan
>


--

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[Jim Cochrane-7]

On Mon, 29 Jun 2009 22:07:28 -0700 (PDT)
Ilan <ilan.tal@...> wrote:

[2nd try, this time with the right from: address.]

>
> Michael,
> Your guess is correct that I am using Ubuntu 9.04.
>
> I decided to take your suggestion and try to implement it.
> I setup Qsynth to connect to the General Midi output and setup
> Patchage to display the results.
> Then I saved that as my default studio.
>
> As I expected, starting Rosegarden didn't start either Qsynth or
> Patchage. Again the goal is for my wife to be able to double click on
> a rosegarden project file and that would bring up her chosen
> composition with all else that is necessary, i.e. Qsynth and possibly
> Patchage (although she doesn't actually need Patchage).

I suspect that it's possible to do this by writing a shell script that
starts Qsynth (and anything else needed), then starts Rosegarden. (?)

>
> Quite possibly this is asking too much, but since you suggested
> changing the default studio I thought I would give it a shot.
>
> Thanks,
> Ilan
>


--

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[D. Michael McIntyre-3]

On Tuesday 30 June 2009, Ilan wrote:
> As I expected, starting Rosegarden didn't start either Qsynth or Patchage.

Oh no, it won't.  I didn't mean to mislead you on that score.

As I read your message, even starting QSynth didn't cause magic to happen,
because your existing default studio was targeting TiMidity, which was
broken, and not making use of QSynth when you ran it.

Making this change, starting QSynth should get magic to happen.  But you still
have to start QSynth somehow.

Or try using the Fluidsynth-DSSI plugin perhaps.

It's all too hard for your wife, and my teenage daughter too.  I have no magic
answers as far as that goes.
--
D. Michael McIntyre

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[Ilan]

I just recently heard about the DSSI plugins, and I think here may be
the answer. It will require some learning to use them, but I'm happy to
learn something new.

There is no magic for anything but patience and work generally solves
most problems. The bottom line is that Rosegarden is REALLY nice software
and I'm glad I chose it when I had to choose which software would be best
for the MIDI problem.

[Ilan]

Michael
Whew. I just managed to get FluidSynth DSSI into the ManageSynth Plugins, but what a job it was.
Something completely trivial, but annoying.
I have my laptop running at its maximum screen resolution but that isn't enough for the dialog box.
There are 24 entries, but only 20 can fit onto the screen.
When I hit on entry #1, it jumps and I end up at entry #5, but I want my one and only DSSI in entry #1 and not in entry #5. (It might not be of any consequence, but then again, just maybe it is important.)
I tried to resize the dialog but it didn't work. After 20 minutes of messing around somehow once I managed to hit entry #1. I quickly put in the DSSI. There are Controls and Editor buttons but I can't get to them (because the dialog box keeps jumping to entry #5).
I would suggest maybe 2 columns of 12 each since there is no lack of room in the horizontal direction.
I'll attach a screen shot.
Thanks,
Ilan

[Ilan]

I see this thread is getting confused. I hope you see my message about the too big dialog box.

In any case I think I managed to install a sound font, but hear nothing.
If I look via Patchage, I see there is no sign of the DSSI, so obviously there is no sound.
Do I have to do something special in order to "start it"? I sort of get the impression that
restarting Rosegarden would start it for me, but that doesn't seem to be true.
I'll send you another screen shot so you can see what is happening.

Thanks for all your help,
Ilan

[D. Michael McIntyre-3]

On Wednesday 01 July 2009, Ilan wrote:

> Whew. I just managed to get FluidSynth DSSI into the ManageSynth Plugins,
> but what a job it was.
> Something completely trivial, but annoying.

Interesting fresh thinking.  I don't think I've ever used that dialog, and I'm
not sure off hand what purpose it might serve.  You probably put yourself
through that trial needlessly, although it's just as well you did, in that
you've drawn a real issue to our attention at a good time to do something
about it.

I usually just use the right click menu on one of the track buttons to assign
the track to, say, Synth Plugin #1, then load a plugin with the button in the
instrument parameters box.

> I have my laptop running at its maximum screen resolution but that isn't
> enough for the dialog box.

Sorry about your pain.  When I look at this dialog in Classic with my standard
obnoxiously large (and easy on the eyes) fonts configured, this dialog weighs
in at a whopping 1298 x 953 pixels.  Ouch.

One tip it sounds like you could use is that we have less brain damaged GUIs
over here on this side of the street, and if a window is too big to fit your
screen, you can hold Alt while clicking anywhere in the window, and drag it
around until the part you need to interact with is in view.  I'm not saying
obnoxiously large dialogs are acceptable, but they don't have to be
crippling.

Anyway, I don't think this is still a problem.  The dialog is only 766 x 547
for me in Thorn, and it has a scrollbar, while the same dialog in Classic
does not.  The dialog in Thorn can be resized both horizontally and
vertically, while the one in Classic can only resize horizontally.

I don't think anyone made improvements to this dialog on purpose, but we seem
to have corrected this irritating situation nonetheless, and it should no
longer be a problem.

--
D. Michael McIntyre

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[D. Michael McIntyre-3]

On Wednesday 01 July 2009, Ilan wrote:

> I see this thread is getting confused. I hope you see my message about the
> too big dialog box.

I just responded to it.

I think what we probably have here is a failure of our user interface to be
intuitive.  You're fooling around with a dialog I never use (and I wonder why
it's there...  I've never, ever used it, and haven't looked at it in years,
so could we do without it without losing anything that mattered to someone?)
and missing out on the whole assignment step I talked about in the last
message.

You probably just need to pick a track, right click and assign to Synth Plugin
(in the first popup menu level) and #1 (in the second level) and then it will
start working.

Or, you do have Timidity running (I saw your screenshot) so maybe we can
figure out why it isn't making noise.  The usual bog standard (and not very
good sounding) configuration of Timidity is to set it up with something
called "Freepats."  It's a package. Do you have freepats installed?

dpkg -l | grep freepats

ii  freepats     20060219-1      Free patch set for MIDI audio synthesis

> In any case I think I managed to install a sound font, but hear nothing.
> If I look via Patchage, I see there is no sign of the DSSI,

You won't see these outside of Rosegarden.  They don't use ALSA MIDI, but some
other technology (DSSI, I guess, actually)

Um, one thing comes to mind.  Go to File -> Open, and click on the "Example
Files" icon.  You should see something called "perfect-moment.rg" on the
list.  This is a file done up to run entirely with DSSI plugins, and it
should make noise if you have Hexter and XSynth installed.  (It doesn't
actually sound very good in this form, but ignore all that, and just see if
it makes noise.)
--
D. Michael McIntyre

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[Ilan]

Before I start to check out all the ideas you gave me, I want to setup my computer for downloads.

I have many friends whom I am trying to convince that there is life beyond Microsoft Windows.
For some of them for whom I have set up Ubuntu, I want to keep my computer simple and close
to theirs. I love these repositories as they keep things organized automatically.
99.9% of the software I want to keep plain vanilla, but Rosegarden is different.
I'm not about to wait for Ubuntu 9.10 for an update.

There is third party software like "http://archive.canonical.com/ubuntu".
I looked in Google for something similar for Rosegarden updates but didn't find anything.
I wonder if you have something organized in the repositories?
If not, I'll do the update manually.

While I'm on the subject, you probably aren't aware that your dialog box offering to update does absolutely nothing. I can click on the link to my heart's content and nothing will happen.
I'll include a screen shot.

Ilan

[wg2002a]

> Date: Mon, 29 Jun 2009 12:17:40 -0700 (PDT)
> From: Ilan <ilan.tal@...>
>
> The thing is I would like to make it completely automatic
> for my wife's use,
> since she understands music and not computers. If I could
> get Timidity to
> work it would be very simple for her: double click on a
> rosegarden file and
> up comes Rosegarden all configured properly. Not start
> Rosegarden, start
> Qsynth, start Patchage and then make the proper
> connections.
>
> I suspect Timidy might be missing a sound font, but try as
> I may, either my
> efforts to install one haven't worked, or something else is
> wrong.
>

I assume you use Linux.  Hope this will help you and others out there.

Since you already have Qsynth working sound-wise.  This is to run jackd, fluidsynth, rosegarden.  If you want timidity++, the idea is similar, you just have to configure timidity properly, then you can modify the script to use timidity instead of fluidsynth.  If you still want to get timidity going, let me know, I can probably write it up.  You can also try web search for "timidity jackd", or "timidity soundfont", or "timidity jackd soundfont" for how to run Timidity with Jackd and soundfonts.

Included below are two script files you can use.  You need to copy the script code between the dash-lines into two separate script files.  I have suggested the script names as:

   zRunRosegarden.sh
   zConnectRosegardenFluidsynth.sh

the second script is called from the first script.  So if you decide to use different names for them, just modify the appropriate line in the first script to invoke the second script.  I am not explaining the second script, but if you really want me to, just ask.

You will need to put those two files in the same directory.  I would create a directory for all personal scripts like these as /home/username/bin/ , but you are free to do whatever you want, just makesure "/home/username" is the actual home directory for the user.  You will only need to run the first script as either one of:

   ~/bin/zRunRosegarden.sh

   /home/username/bin/zRunRosegarden.sh

which also invokes the second script from there.  Make sure you set the executable flag for the files with:

   chmod +x ~/bin/zRunRosegarden.sh
   chmod +x ~/bin/zConnectRosegardenFluidsynth.sh

The lines starting with "#" are comment lines.  I have them there to show you various ways I have tried , and keep those lines there to remind me of how things could be done differently, and had worked for me before.

Of course you will also need to adapt the script for your own use.  One is the line that starts up jackd.  If you already have qjackctl started jackd then you are all set.  Once you have qjackctl running and started jackd, try this command from the command line:

   ps -ef | grep -v grep | grep jackd


it should show something similar to:

someusername       32428  6412  2 23:51 ?        00:00:00 /usr/bin/jackd -dalsa -dhw:1 -r48000 -p128 -n2 -Xseq


it means that Jackd was started by Qjackctl with the command:

   /usr/bin/jackd -dalsa -dhw:1 -r48000 -p128 -n2 -Xseq


Note that "-dhw:1" means that it is using the second soundcard.  Of course, if it uses the first soundcard, or the only soundcard in your system, it should show "-dhw:0" or not even there (as default).  Also note the "-r" option, "-r48000" or "-r44100" means it uses the corresponding audio sample rate.

Now you have the full command to start Jackd from the command line without the need for Qjackctl.  Copy everything you see from the output starting from the /usr/bin/jackd to the end, put all of that into the first script just below the existing line that starts with /usr/bin/jackd , then comment out the line I had starting with /usr/bin/jackd .  So the script would use the appropriate parameters to to run jackd with your sound card hardware.

Also, the line to invoke fluidsynth in the first script file need to be commented out, copied and replace the full path to your own GM soundfont file.  That way fluidsynth could load the soundfont of your choice on your system.  Note the audio sample rate for fluidsynth should match that number that jackd uses.

If you have questions, ask away.  Other than that, those are the flexibility of various command line programs that allow us to do things our way.  Don't be intimidated, learn those and you will be glad you did.  There are books and free books online, but I don't have the time to learn things from books (cover to cover) that I may not need for a long time, or ever.  Web searches are how I learn those, one task at a time.

Jimmy




---------- Start of zRunRosegarden.sh ----------
#/bin/bash
#/bin/bash -x


      zscriptdir=`dirname $0`

      ### /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p64 -n2  &
      ### /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p32 -n2  &
      ### /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p128 -n2  &
      ### /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n2 -Xseq &

      ### /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p64 -n2  &
      ### /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p32 -n2  &
      ### /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p128 -n2  &
      ### /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p256 -n2 -Xseq &
      ### /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p256 -n2 -Xseq &

      /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p256 -n2 -Xseq &
 
      ### qjackctl &


      ### ${zscriptdir}/jnTimidityServer.sh &

      ### --- waits for jackd to start up
      sleep 5

      ### vkeybd --octave 5 &
      ### sleep 3

      ### ${zscriptdir}/qmidiroute &


      ### sleep 5 && qsynth &
      ### sleep 5 && ${zscriptdir}/jnTimidityServer.sh &
      ### sleep 5 && fluidsynth -s -a jack -j   ~/download/soundfonts/FluidR3_GM.sf2  & ~/download/soundfonts/FluidR3_GS.sf2  &
      ### sleep 5 && fluidsynth -s -a jack -j   ~/download/soundfonts/Unison.sf2  &
      ### sleep 5 && fluidsynth -s -a jack -j   ~/download/soundfonts/merlin_8mbgm_plus13.sf2  &
      ### sleep 5 && fluidsynth -s -a jack -j   ~/download/soundfonts/merlin_gmv22.sf2  &
      ### fluidsynth -s -a jack -j   ~/download/soundfonts/merlin_gmv22.sf2

      fluidsynth  --no-shell  --server  --audio-driver jack  --connect-jack-outputs  --sample-rate 48000  ~/download/soundfonts/Unison.sf2 &

      rosegarden &

      ### --- waits for rosegarden to start up
      sleep 7

      ### --- disconnect all Midi connections, rosegarden messed up big time
      aconnect -x

      ### --- use aconnect to connect Rosegarden to Fluidsynth.  You can use patchage or other programs instead.
      ${zscriptdir}/zConnectRosegardenFluidsynth.sh



---------- End of zRunRosegarden.sh ----------




---------- Start of zConnectRosegardenFluidsynth.sh ----------
#/bin/bash
#/bin/bash -x


      zscriptdir=`dirname $0`

      ### find Alsa-Midi client number for rosegarden
      rgClient=$( aconnect -li | grep 'rosegarden' | grep 'client' | sed -e "s~client \([0-9]*\).*~\1~" )

      ### find rosegarden GM device number
      rgGMout=$( aconnect -li | grep 'out 1 - General MIDI Device' | sed -e "s~ *\([0-9]*\).*~\1~" )

      ### find Alsa-Midi client number for fluidsynth
      fluidClient=$( aconnect -lo | grep 'FLUID Synth' | grep 'client' | sed -e "s~client \([0-9]*\).*~\1~" )

      ### connect rosegarden GM device to fluidsynth
      aconnect "${rgClient}:${rgGMout}"  "${fluidClient}:0"


---------- End of zConnectRosegardenFluidsynth.sh ----------





     

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[Ilan]

Hi Michael,
Trying your perfect-moment turned out to be more useful than anyone could
imagine. It took me some time to get it to make some sounds but I learned
a lot in the process.
I also looked into the TiMidity again. It seems to be activated by JACK because
when I exit Rosegarden TiMidity is still active. I played around with JACK hoping
I could get it to make some sound but nothing I tried worked.
The freepat was already installed

I am unable to verify if TiMidity has a sound font or not.

On some other issues, I tried and failed again to delete that first bar which I shifted
to get rid of the quarter note rest. I can't find your suggestion on what to do. You wrote
but I can't find it.

The other issue is playing with the grid. I want to see what it does with the notes,
how it shifts them. I know I won't reach the Holy Grail, but at least I gain some
experience from the exercise. The problem is I can't find in the program how to set
the grid.

Once I get this figured out in my mind, I'll try to decide what is the easiest way to get
my wife really started with Rosegarden. There is no magic, but still TiMidity would be
nice if it would work. Start easy and then ramp up with more experience.

Ilan

[D. Michael McIntyre-3]

On Thursday 02 July 2009, Ilan wrote:

> While I'm on the subject, you probably aren't aware that your dialog box
> offering to update does absolutely nothing. I can click on the link to my
> heart's content and nothing will happen.

There was nothing we could do about that in Rosegarden Classic.  Our code was
fine, but it didn't actually work.  It does work now in Thorn.  I just tested
to confirm this.

It takes you to http://rosegardenmusic.com/getting/source which is not really
the magic solution you're hoping for.

I'm not aware of a pre-packaged solution to this problem.  Users pretty much
either have to build from source or use whatever version their distro
provides, which is normally quite old.

This is a really big thing about the Linux experience itself that's totally
different from the Windows world.  How do I, as a software author, distribute
my latest version to my users?

Source code really is the only answer.  It's the Linux world's biggest
strength and biggest weakness at the same time.
--
D. Michael McIntyre

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[D. Michael McIntyre-3]

On Thursday 02 July 2009, Ilan wrote:

> I also looked into the TiMidity again. It seems to be activated by JACK
> because when I exit Rosegarden TiMidity is still active.

No.  JACK is a mechanism through which multiple pieces of software can
exchange audio data, and ultimately get that audio passed through to
soundcard hardware, where it can be heard.  It is also a mechanism through
which audio sources originating outside the computer and coming in through
the soundcard can be recorded, such as a signal coming from a microphone or
an electric guitar.

TiMidity is running independently of any of that.  On my Ubuntu 8.04 system,
it runs as a fake daemon using a script in /etc/init.d/timidity that is
configured out of the box to start at boot time.

Looking at that script, there is nothing in there to make TiMidity send its
audio through JACK.  In fact, now that I think about it, for this to work,
JACK would also need to be run as a fake daemon process, and it would need to
be started *before* TiMidity in order for TiMidity to communicate with it.

Unless things have changed in the last couple of years, JACK applications all
have to be run by the same user, so if you ran JACK as a daemon you'd have to
run everything as root.

I don't understand what they're thinking with this script.  It seems
impossible for it to work on a typical system with JACK, and JACK is
everything in the Linux audio world.

Forgive me for such a potentially offensive comparison, but now that I've had
this thought, I just can't help myself.  If you've ever watched South Park,
there was an episode where Mr. Garrison invented a revolutionary new means of
transportation called the IT.  It was faster than an airplane and cheap to
buy, and it could run circles around anything else that had ever been
invented.  The only problem with it was to make it work, you had to sit down
on a very large anal probe.

That's JACK.

> On some other issues, I tried and failed again to delete that first bar
> which I shifted to get rid of the quarter note rest. I can't find your
suggestion on what to do. You wrote but I can't find it.

If you want to delete the entire bar (not just the rest) then try double
clicking in the bar (to highlight all the events in the bar) then Edit->Cut
and Close.

> The other issue is playing with the grid. I want to see what it does with
> the notes,
> how it shifts them. I know I won't reach the Holy Grail, but at least I
> gain some
> experience from the exercise. The problem is I can't find in the program
> how to set
> the grid.

Highlight some notes, and hit the big Q icon.  The "heuristic" quantizer is
the one that tries to make the notes easier to read without changing
performance start times or durations, while the "grid" quantizer physically
moves notes around to line them up more neatly.  Both have a pile of options
to fiddle with, and no magic recipe for which ones will work.  (There may be
other quantizers, such as if the "legato" is still around.  None of these are
useful in practice, and may do permanent harm.  Which is another issue we
should thinking about at this point in time, for Thorn, now that I think
about it.  Fix it or ditch it.)

> Once I get this figured out in my mind, I'll try to decide what is the
> easiest way to get
> my wife really started with Rosegarden. There is no magic, but still
> TiMidity would be
> nice if it would work. Start easy and then ramp up with more experience.

Having a script connected with an icon she could click on to start everything
is probably one of the most sensible ways to go.  That's probably what I'll
set up for my teenage daughter eventually, since she has no inclination to
ever become a hacker like her old man.
--
D. Michael McIntyre

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[cannam]

On Thu, Jul 2, 2009 at 8:31 PM, D. Michael
McIntyre<rosegarden.trumpeter@...> wrote:
> Looking at that script, there is nothing in there to make TiMidity send its
> audio through JACK.  In fact, now that I think about it, for this to work,
> JACK would also need to be run as a fake daemon process, and it would need to
> be started *before* TiMidity in order for TiMidity to communicate with it.

These days, the JACK client library will automatically start the JACK
daemon if it isn't already running, when an application tries to
connect to JACK.

There are some exceptions -- e.g. an application can ask for this not
to happen, and it won't happen with RG 1.7.x because that uses an
older JACK client API.  I don't know about Timidity; this might not be
what is actually happening there, it's just a thought.

And of course it only works if starting JACK without any particular
configuration and with the default audio device happens to work for
you on your hardware.


Chris

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

[david-602]

On Thu, Jul 2, 2009 at 8:31 PM, D. Michael
> McIntyre<rosegarden.trumpeter@...> wrote:
>> Looking at that script, there is nothing in there to make TiMidity send its
>> audio through JACK.  In fact, now that I think about it, for this to work,
>> JACK would also need to be run as a fake daemon process, and it would need to
>> be started *before* TiMidity in order for TiMidity to communicate with it.

FWIW, I was never able to get sound out of Timidity (with or without
Rosegarden or JACK), so I went with fluidsynth and haven't looked back.

--
David
gnome@...
authenticity, honesty, community

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user