Paul Davis wrote:
> On Wed, 2006-10-18 at 19:13 +0200, Dragan Noveski wrote:
>
> nothing above this point is relevant:
>
>
>> cannot lock down memory for RT thread (Nicht genügend Hauptspeicher
>> verfügbar)
>> ALSA lib pcm_dmix.c:862:(snd_pcm_dmix_open) unable to open slave
>> ALSA lib pcm_dsnoop.c:556:(snd_pcm_dsnoop_open) unable to open slave
>>
>
> my wine config doesn't even try to open ALSA devices. not sure how you
> stop this, but Wine should not be attempting to get access to any audio
> devices.
>
>
dont know at all, ll try to get some information at the wine webpage
>> err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type (alsa
>> type is 100000) of this midi device. Assuming FM Synth
>>
>
> ditto for MIDI.
>
>
>> wine: Unhandled page fault on read access to 0xf746d4e4 at address
>>
>
> this is almost certainly a segfault in a VST plugin.
>
>
>> 0x7d95de0a (thread 0009), starting debugger...
>> Usage:
>> winedbg [ [ --gdb ] [ prog-name [ prog-args ] | <num> |
>> file.mdmp | --help ]
>> err:seh:raise_exception Unhandled exception code c000013a flags 0 addr
>> 0xb7dfb40f
>> nowhiskey@email-addr-hidden:~$
>> ...............
>>
>> and also generally, it looks for me that building ardour with vst
>> support, makes the appi much more "fragile" than when built without vst.
>> does anybody else has made similar experience?
>>
>
> you are loading random win32 code into ardour, some of which will crash
> wine. so of course its less stable, just like there still a few LADSPA
> plugins which can do the same thing.
>
> the thing to do is to remove all vst plugins from wherever VST_PLUGINS
> or VST_PATH points to. then start it up. see if it works. if thats OK,
> the issues are entirely to do with specific plugins. then add back ones
> you are interested one by one to verify that they work.
>
> --p
>
tried removing all the vst plugins from the directory called vst, than
running ardour without any plugins, but than trying to "close session" i
get the same behavior that i am only able to kill ardour.
console output:
...
cannot lock down memory for RT thread (Nicht genügend Hauptspeicher
verfügbar)
actually writing state
actually writing history
(ardour_vst.exe.so:3770): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
actually writing state
actually writing history
actually writing state
actually writing history
wine: Unhandled page fault on read access to 0xf790fae4 at address
0x7d95fe0a (thread 0009), starting debugger...
Usage:
winedbg [ [ --gdb ] [ prog-name [ prog-args ] | <num> |
file.mdmp | --help ]
err:seh:raise_exception Unhandled exception code c000013a flags 0 addr
0xb7ded40f
Speicherzugriffsfehler
nowhiskey@email-addr-hidden:~$
....
i just realized that wine dont complain about alsa/midi stuff anymore.
now i copied back the vst´s to the vst directory, and still wine is not
complaining about any alsa stuff anymore:
...
cannot lock down memory for RT thread (Nicht genügend Hauptspeicher
verfügbar)
actually writing state
actually writing history
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
actually writing state
actually writing history
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Gtk-WARNING **: Invalid input string
(ardour_vst.exe.so:3807): Gtk-WARNING **: Invalid input string
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Gtk-WARNING **: Invalid input string
(ardour_vst.exe.so:3807): Gtk-WARNING **: Invalid input string
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
(ardour_vst.exe.so:3807): Pango-WARNING **: Invalid UTF-8 string passed
to pango_layout_set_text()
actually writing state
actually writing history
wine: Unhandled page fault on read access to 0xf78fade4 at address
0x7d956e0a (thread 0009), starting debugger...
Usage:
winedbg [ [ --gdb ] [ prog-name [ prog-args ] | <num> |
file.mdmp | --help ]
err:seh:raise_exception Unhandled exception code c000013a flags 0 addr
0xb7e6940f
nowhiskey@email-addr-hidden:~$
-------------
any other suggestion what i could try to do?
cheers,
doc
>
>
> _______________________________________________
> ardour-users mailing list
> ardour-users@email-addr-hidden
> http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
>
Received on Thu Oct 19 00:15:03 2006
This archive was generated by hypermail 2.1.8 : Thu Oct 19 2006 - 00:15:03 EEST