[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Om-synth] using om_patch_loader
From: |
Dave Robillard |
Subject: |
Re: [Om-synth] using om_patch_loader |
Date: |
Fri, 05 Aug 2005 12:55:11 +1000 |
On Thu, 2005-04-08 at 14:24 +0200, Atte André Jensen wrote:
> Hi
>
> I'm trying to load some patches from a script using om_patch_loader, but
> "it doesn't work". No sound, don't know if it's the midi connection to
> om or the audio from that's messed up...
>
> Before I file a more complete report, is this something that has
> happened to you, and what could be a solution? I noticed that loading
> with om_patch_loader displays something like
>
> No engine port or URL specified. Attempting to use localhost:16180.
> [Comm] Started OSC listener on port 17018 ***
> [Comm] Sending to engine at address osc.udp://localhost:16180/
> WaitingJack driver already activated.
> Added client ::ffff:127.0.0.1:17018 to clients list (1 clients)
> for response 2: [JackDriver] Enabling.
> . received.
> Waiting for response 3: . received.
> FILENAME = sine_w_portamento_01.om
> [PatchLibrarian] Loading patch sine_w_portamento_01.om
> Waiting for response 4: . received.
> Unregistered client.
>
> Where as loading with om_gtk gives:
> FILENAME = /home/atte/music/synth/om/own/open_saw_bass_01.om
> [PatchLibrarian] Loading patch
> /home/atte/music/synth/om/own/open_saw_bass_01.om
> Waiting for response 85: . received.
> FILENAME = /home/atte/music/synth/om/own/open_saw_bass_01.om
> Yanking patch, filename = /home/atte/music/synth/om/own/open_saw_bass_01.om
>
> (om_gtk:8374): Gtk-CRITICAL **: gtk_widget_get_parent_window: assertion
> `widget->parent != NULL' failed
> FILENAME = /home/atte/music/synth/om/own/open_saw_bass_01.om
>
> I thought that the -c and -o options for om_patch_loader could help out,
> but have no clue what to specefy with them...
Looks good to me, but it might be the path bug (which I fixed in the
latest CVS now, BTW).
Load the gtk client and see what's going on then. That shiny multiple
client functionality isn't there for no reason. ;)
There shouldn't be any difference loading a patch with the gtk client or
the patch_loader - it's the exact same bit of code that does it for
both.
-DR-