[gdigi] GNX3000 Segmentation Fault

11 views
Skip to first unread message

wjz

unread,
May 20, 2010, 11:42:07 PM5/20/10
to gdigi
I am trying to use gdigi-0.1.8 with a GNX3000 on Ubuntu Studio.

Running "amidi -l" displays
Dir Device Name
IO hw:0,0,0 GNX3K MIDI 1
IO hw:0,1,0 GNX3K MIDI 1

Running "gdigi -d hw:0,0,0" responds with a very long output with
memory allocations and includes messages such as:
** Message: Pushing correct message!
** Message: Received current edit buffer
** Message: Modified flag: 0 Name: PLEXIDRV
** Message: 1 ID 193 Position 4 Value 0...
** Message: 108 ID 8393 Position 21 Value 0
** Message: TOTAL 108
** Message: Unhandled message in preset messages list
Segmentation fault

This seems like a error in communicating a preset. I restored the
device to factory settings but no success. Do you have any
recommendations to get gdigi to work with my board?

--
You received this message because you are subscribed to the Google Groups "gdigi" group.
To post to this group, send email to gd...@googlegroups.com.
To unsubscribe from this group, send email to gdigi+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/gdigi?hl=en.

Tomasz Moń

unread,
May 21, 2010, 1:14:21 AM5/21/10
to gdigi
On May 21, 5:42 am, wjz <wjzukow...@gmail.com> wrote:
> This seems like a error in communicating a preset.

No, the "Unhandled message in preset messages list" refers to GeNetX.

> Do you have any recommendations to get gdigi to work with my board?

Try with latest hg, I think this has been fixed already.

wjz

unread,
May 21, 2010, 11:26:30 AM5/21/10
to gdigi
> Try with latesthg, I think this has been fixed already.

My apologies. Thank you for the fix. I ran hg clone
http://hg.atheme.org/users/desowin/gdigi/ gdigi before my first post
and I thought that updated it. Instead now I've manually downloaded
gdigi-fe2e9961e129 from http://hg.atheme.org/users/desowin/gdigi/users/desowin/gdigi/shortlog/fe2e9961e129
and replaced the old files in the gdigi-0.1.3 directory.

Gdigi now seems to be working.
Reply all
Reply to author
Forward
0 new messages