seq24-users Mailing List for seq24 (Page 12)
Brought to you by:
rcbuse
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
(4) |
Aug
(2) |
Sep
(10) |
Oct
|
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(10) |
Feb
(8) |
Mar
(28) |
Apr
(5) |
May
(13) |
Jun
|
Jul
|
Aug
(33) |
Sep
(5) |
Oct
(11) |
Nov
(11) |
Dec
(7) |
| 2006 |
Jan
(5) |
Feb
(10) |
Mar
(40) |
Apr
(28) |
May
(8) |
Jun
(6) |
Jul
(7) |
Aug
(54) |
Sep
(53) |
Oct
(5) |
Nov
(12) |
Dec
(8) |
| 2007 |
Jan
(3) |
Feb
(7) |
Mar
(9) |
Apr
|
May
|
Jun
(2) |
Jul
(2) |
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
(2) |
| 2008 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
|
May
(16) |
Jun
(2) |
Jul
(2) |
Aug
(28) |
Sep
(17) |
Oct
|
Nov
(13) |
Dec
(13) |
| 2009 |
Jan
(4) |
Feb
(5) |
Mar
(7) |
Apr
(24) |
May
(54) |
Jun
(20) |
Jul
(11) |
Aug
(6) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2010 |
Jan
(5) |
Feb
|
Mar
(5) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(10) |
Dec
(2) |
| 2011 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2012 |
Jan
(2) |
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(14) |
| 2016 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Esben S. <b0...@es...> - 2008-05-06 17:07:18
|
Is there anything happening with this project?. It doesn't seem to be
any activity here and it would be nice if the original author could
tell what's up, regarding plans, if there are any.
--
Esben Stien is b0ef@e s a
http://www. s t n m
irc://irc. b - i . e/%23contact
sip:b0ef@ e e
jid:b0ef@ n n
|
|
From: Nicholas M. <nic...@gm...> - 2008-03-28 09:18:17
|
When I try to edit, seq24 immediately crashes. Here is the terminal output: ======= Backtrace: ========= /lib/libc.so.6(__fortify_fail+0x48)[0x525b58] /lib/libc.so.6[0x524200] /lib/libc.so.6[0x523918] /lib/libc.so.6(_IO_default_xsputn+0xcd)[0x4a1e8d] /lib/libc.so.6(_IO_vfprintf+0x8ef)[0x478fcf] /lib/libc.so.6(__vsprintf_chk+0xad)[0x5239cd] /lib/libc.so.6(__sprintf_chk+0x30)[0x523900] seq24[0x80558ff] /usr/lib/libgtkmm-2.4.so.1 (_ZN3Gtk12Widget_Class16realize_callbackEP10_GtkWidget+0x92)[0x4554c12] /lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x49)[0x9f3409] /lib/libgobject-2.0.so.0[0x9e4779] /lib/libgobject-2.0.so.0(g_closure_invoke+0x123)[0x9e5f83] /lib/libgobject-2.0.so.0[0x9f691a] /lib/libgobject-2.0.so.0(g_signal_emit_valist+0x8c7)[0x9f7997] /lib/libgobject-2.0.so.0(g_signal_emit+0x29)[0x9f7b59] /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_realize+0x1ee)[0x3bd8ee2] /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0x166)[0x3bd8a5f] /usr/lib/libgtk-x11-2.0.so.0[0x39861b1] /usr/lib/libgtk-x11-2.0.so.0[0x3b06623] /usr/lib/libgtkmm-2.4.so.1 (_ZN3Gtk15Container_Class21forall_vfunc_callbackEP13_GtkContaineriPFvP10_GtkWidgetPvES5_+0x69)[0x44a77b9] /usr/lib/libgtk-x11-2.0.so.0(gtk_container_forall+0xea)[0x3983a27] /usr/lib/libgtk-x11-2.0.so.0[0x3986217] /usr/lib/libgtkmm-2.4.so.1 (_ZN3Gtk12Widget_Class12map_callbackEP10_GtkWidget+0x52)[0x4554d32] /lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x49)[0x9f3409] /lib/libgobject-2.0.so.0[0x9e4779] /lib/libgobject-2.0.so.0(g_closure_invoke+0x20c)[0x9e606c] /lib/libgobject-2.0.so.0[0x9f691a] /lib/libgobject-2.0.so.0(g_signal_emit_valist+0x8c7)[0x9f7997] /lib/libgobject-2.0.so.0(g_signal_emit+0x29)[0x9f7b59] /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0x183)[0x3bd8a7c] /usr/lib/libgtk-x11-2.0.so.0[0x39861b1] /usr/lib/libgtk-x11-2.0.so.0[0x3928772] /usr/lib/libgtkmm-2.4.so.1 (_ZN3Gtk15Container_Class21forall_vfunc_callbackEP13_GtkContaineriPFvP10_GtkWidgetPvES5_+0x69)[0x44a77b9] /usr/lib/libgtk-x11-2.0.so.0(gtk_container_forall+0xea)[0x3983a27] /usr/lib/libgtk-x11-2.0.so.0[0x3986217] /usr/lib/libgtkmm-2.4.so.1 (_ZN3Gtk12Widget_Class12map_callbackEP10_GtkWidget+0x52)[0x4554d32] /lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x49)[0x9f3409] /lib/libgobject-2.0.so.0[0x9e4779] /lib/libgobject-2.0.so.0(g_closure_invoke+0x20c)[0x9e606c] /lib/libgobject-2.0.so.0[0x9f691a] /lib/libgobject-2.0.so.0(g_signal_emit_valist+0x8c7)[0x9f7997] /lib/libgobject-2.0.so.0(g_signal_emit+0x29)[0x9f7b59] /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0x183)[0x3bd8a7c] /usr/lib/libgtk-x11-2.0.so.0[0x3beee3d] /usr/lib/libgtkmm-2.4.so.1(_ZN3Gtk6Widget6on_mapEv+0x46)[0x4557066] /usr/lib/libgtkmm-2.4.so.1 (_ZN3Gtk12Widget_Class12map_callbackEP10_GtkWidget+0x92)[0x4554d72] /lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x49)[0x9f3409] /lib/libgobject-2.0.so.0[0x9e4779] /lib/libgobject-2.0.so.0(g_closure_invoke+0x123)[0x9e5f83] /lib/libgobject-2.0.so.0[0x9f691a] /lib/libgobject-2.0.so.0(g_signal_emit_valist+0x8c7)[0x9f7997] /lib/libgobject-2.0.so.0(g_signal_emit+0x29)[0x9f7b59] /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0x183)[0x3bd8a7c] /usr/lib/libgtk-x11-2.0.so.0[0x3beec7c] /usr/lib/libgtkmm-2.4.so.1(_ZN3Gtk6Widget7on_showEv+0x46)[0x4557106] /usr/lib/libgtkmm-2.4.so.1 (_ZN3Gtk12Widget_Class13show_callbackEP10_GtkWidget+0x92)[0x4554ed2] /lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x49)[0x9f3409] /lib/libgobject-2.0.so.0[0x9e4779] /lib/libgobject-2.0.so.0(g_closure_invoke+0x123)[0x9e5f83] /lib/libgobject-2.0.so.0[0x9f691a] /lib/libgobject-2.0.so.0(g_signal_emit_valist+0x8c7)[0x9f7997] /lib/libgobject-2.0.so.0(g_signal_emit+0x29)[0x9f7b59] /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_show+0xfc)[0x3bd8214] ======= Memory map: ======== 00101000-0013f000 r-xp 00000000 fd:00 14148747 /usr/lib/libpango- 1.0.so.0.1800.4 0013f000-00141000 rw-p 0003e000 fd:00 14148747 /usr/lib/libpango- 1.0.so.0.1800.4 00143000-001e2000 r-xp 00000000 fd:00 14148752 /usr/lib/libgdk- x11-2.0.so.0.1200.5 001e2000-001e5000 rw-p 0009f000 fd:00 14148752 /usr/lib/libgdk- x11-2.0.so.0.1200.5 001e7000-00217000 r-xp 00000000 fd:00 14148749 /usr/lib/libpangoft2- 1.0.so.0.1800.4 00217000-00218000 rw-p 0002f000 fd:00 14148749 /usr/lib/libpangoft2- 1.0.so.0.1800.4 0021a000-0029d000 r-xp 00000000 fd:00 14148748 /usr/lib/libcairo.so.2.11.7 0029d000-0029f000 rw-p 00082000 fd:00 14148748 /usr/lib/libcairo.so.2.11.7 00358000-0035d000 r-xp 00000000 fd:00 14137427 /usr/lib/libsigc- 2.0.so.0.0.0 0035d000-0035e000 rw-p 00004000 fd:00 14137427 /usr/lib/libsigc- 2.0.so.0.0.0 0041d000-00438000 r-xp 00000000 fd:00 18514186 /lib/ld-2.7.so 00438000-00439000 r--p 0001a000 fd:00 18514186 /lib/ld-2.7.so 00439000-0043a000 rw-p 0001b000 fd:00 18514186 /lib/ld-2.7.so 0043c000-0058f000 r-xp 00000000 fd:00 18514196 /lib/libc-2.7.so 0058f000-00591000 r--p 00153000 fd:00 18514196 /lib/libc-2.7.so 00591000-00592000 rw-p 00155000 fd:00 18514196 /lib/libc-2.7.so 00592000-00595000 rw-p 00592000 00:00 0 00597000-005be000 r-xp 00000000 fd:00 18514298 /lib/libm-2.7.so 005be000-005bf000 r--p 00026000 fd:00 18514298 /lib/libm-2.7.so 005bf000-005c0000 rw-p 00027000 fd:00 18514298 /lib/libm-2.7.so 005c2000-005c5000 r-xp 00000000 fd:00 18514242 /lib/libdl-2.7.so 005c5000-005c6000 r--p 00002000 fd:00 18514242 /lib/libdl-2.7.so 005c6000-005c7000 rw-p 00003000 fd:00 18514242 /lib/libdl-2.7.so 005c9000-005de000 r-xp 00000000 fd:00 18515493 /lib/libpthread-2.7.so 005de000-005df000 r--p 00014000 fd:00 18515493 /lib/libpthread-2.7.so 005df000-005e0000 rw-p 00015000 fd:00 18515493 /lib/libpthread-2.7.so 005e0000-005e2000 rw-p 005e0000 00:00 0 005e4000-005f6000 r-xp 00000000 fd:00 18514277 /lib/libz.so.1.2.3 005f6000-005f7000 rw-p 00011000 fd:00 18514277 /lib/libz.so.1.2.3 005f9000-005fb000 r-xp 00000000 fd:00 14128937 /usr/lib/libXau.so.6.0.0 005fb000-005fc000 rw-p 00001000 fd:00 14128937 /usr/lib/libXau.so.6.0.0 005fe000-005ff000 r-xp 00000000 fd:00 14148714 /usr/lib/libxcb- xlib.so.0.0.0 005ff000-00600000 rw-p 00000000 fd:00 14148714 /usr/lib/libxcb- xlib.so.0.0.0 00602000-006fa000 r-xp 00000000 fd:00 14148715 /usr/lib/libX11.so.6.2.0 006fa000-006fe000 rw-p 000f7000 fd:00 14148715 /usr/lib/libX11.so.6.2.0 00700000-00705000 r-xp 00000000 fd:00 14148712 /usr/lib/libXdmcp.so.6.0.0 00705000-00706000 rw-p 00004000 fd:00 14148712 /usr/lib/libXdmcp.so.6.0.0 00708000-00723000 r-xp 00000000 fd:00 14148713 /usr/lib/libxcb.so.1.0.0 00723000-00724000 rw-p 0001a000 fd:00 14148713 /usr/lib/libxcb.so.1.0.0 00726000-00735000 r-xp 00000000 fd:00 14148721 /usr/lib/libXext.so.6.4.0 00735000-00736000 rw-p 0000e000 fd:00 14148721 /usr/lib/libXext.so.6.4.0 00738000-00757000 r-xp 00000000 fd:00 18515495 /lib/libexpat.so.1.5.2 00757000-00759000 rw-p 0001f000 fd:00 18515495 /lib/libexpat.so.1.5.2 0075b000-007e3000 r-xp 00000000 fd:00 14148734 /usr/lib/libfreetype.so.6.3.16 007e3000-007e7000 rw-p 00087000 fd:00 14148734 /usr/lib/libfreetype.so.6.3.16 007e9000-00810000 r-xp 00000000 fd:00 14148735 /usr/lib/libfontconfig.so.1.2.0 00810000-00818000 rw-p 00027000 fd:00 14148735 /usr/lib/libfontconfig.so.1.2.0 0081a000-00822000 r-xp 00000000 fd:00 14146050 /usr/lib/libXrender.so.1.3.0 00822000-00823000 rw-p 00007000 fd:00 14146050 /usr/lib/libXrender.so.1.3.0 00825000-0084a000 r-xp 00000000 fd:00 14144457 /usr/lib/libpng12.so.0.22.0 0084a000-0084b000 rw-p 00025000 fd:00 14144457 /usr/lib/libpng12.so.0.22.0 0084d000-00854000 r-xp 00000000 fd:00 18515494 /lib/librt-2.7.so 00854000-00855000 r--p 00007000 fd:00 18515494 /lib/librt-2.7.so 00855000-00856000 rw-p 00008000 fd:00 18515494 /lib/librt-2.7.so 00858000-00922000 r-xp 00000000 fd:00 18514314 /lib/libglib- 2.0.so.0.1400.6 00922000-00923000 rw-p 000ca000 fd:00 18514314 /lib/libglib- 2.0.so.0.1400.6 00925000-00927000 r-xp 00000000 fd:00 14148733 /usr/lib/libXinerama.so.1.0.0 00927000-00928000 rw-p 00001000 fd:00 14148733 /usr/lib/libXinerama.so.1.0.0 0092a000-00930000 r-xp 00000000 fd:00 14148732 /usr/lib/libXrandr.so.2.1.0 00930000-00931000 rw-p 00005000 fd:00 14148732 /usr/lib/libXrandr.so.2.1.0 00933000-00937000 r-xp 00000000 fd:00 14148723 /usr/lib/libXfixes.so.3.1.0 00937000-00938000 rw-p 00003000 fd:00 14148723 /usr/lib/libXfixes.so.3.1.0 0093a000-00945000 r-xp 00000000 fd:00 18515496 /lib/libgcc_s- 4.1.2-20070925.so.1 00945000-00946000 rw-p 0000a000 fd:00 18515496 /lib/libgcc_s- 4.1.2-20070925.so.1 00948000-00951000 r-xp 00000000 fd:00 14148724 /usr/lib/libXcursor.so.1.0.2 00951000-00952000 rw-p 00008000 fd:00 14148724 /usr/lib/libXcursor.so.1.0.2 00954000-0095c000 r-xp 00000000 fd:00 14148731 /usr/lib/libXi.so.6.0.0 0095c000-0095d000 rw-p 00007000 fd:00 14148731 /usr/lib/libXi.so.6.0.0 009dd000-00a1c000 r-xp 00000000 fd:00 18515445 /lib/libgobject- 2.0.so.0.1400.6 00a1c000-00a1d000 rw-p 0003f000 fd:00 18515445 /lib/libgobject- 2.0.so.0.1400.6 00a1f000-00aff000 r-xp 00000000 fd:00 14132112 /usr/lib/libstdc++.so.6.0.8 00aff000-00b03000 r--p 000df000 fd:00 14132112 /usr/lib/libstdc++.so.6.0.8 00b03000-00b04000 rw-p 000e3000 fd:00 14132112 /usr/lib/libstdc++.so.6.0.8 00b04000-00b0a000 rw-p 00b04000 00:00 0 00b0c000-00b0f000 r-xp 00000000 fd:00 18515504 /lib/libgmodule- 2.0.so.0.1400.6 00b0f000-00b10000 rw-p 00002000 fd:00 18515504 /lib/libgmodule- 2.0.so.0.1400.6 00b65000-00b7c000 r-xp 00000000 fd:00 14147775 /usr/lib/libcairomm- 1.0.so.1.1.0 00b7c000-00b7d000 rw-p 00016000 fd:00 14147775 /usr/lib/libcairomm- 1.0.so.1.1.0 00b9a000-00bb6000 r-xp 00000000 fd:00 14128816 /usr/lib/libgdk_pixbuf- 2.0.so.0.1200.5 00bb6000-00bb7000 rw-p 0001b000 fd:00 14128816 /usr/lib/libgdk_pixbuf- 2.0.so.0.1200.5 00bb9000-00c93000 r-xp 00000000 fd:00 18515508 /lib/libasound.so.2.0.0 00c93000-00c98000 rw-p 000da000 fd:00 18515508 /lib/libasound.so.2.0.0 00dd0000-00dea000 r-xp 00000000 fd:00 14148753 /usr/lib/libatk- 1.0.so.0.2009.1 00dea000-00dec000 rw-p 0001a000 fd:00 14148753 /usr/lib/libatk- 1.0.so.0.2009.1 00dee000-00df7000 r-xp 00000000 fd:00 14148750 /usr/lib/libpangocairo- 1.0.so.0.1800.4 00df7000-00df8000 rw-p 00008000 fd:00 14148750 /usr/lib/libpangocairo- 1.0.so.0.1800.4 00dfa000-00dfc000 r-xp 00000000 fd:00 14148751 /usr/lib/libXcomposite.so.1.0.0 00dfc000-00dfd000 rw-p 00001000 fd:00 14148751 /usr/lib/libXcomposite.so.1.0.0 038bc000-03cf3000 r-xp 00000000 fd:00 14148754 /usr/lib/libgtk- x11-2.0.so.0.1200.5 03cf3000-03cf9000 rw-p 00437000 fd:00 14148754 /usr/lib/libgtk- x11-2.0.so.0.1200.5 03cf9000-03cfa000 rw-p 03cf9000 00:00 0 03f5f000-03fa2000 r-xp 00000000 fd:00 14132432 /usr/lib/libgdkmm- 2.4.so.1.0.30 03fa2000-03fa5000 rw-p 00042000 fd:00 14132432 /usr/lib/libgdkmm- 2.4.so.1.0.30 03fa7000-03ff7000 r-xp 00000000 fd:00 14129313 /usr/lib/libglibmm- 2.4.so.1.0.24 03ff7000-03ff9000 rw-p 0004f000 fd:00 14129313 /usr/lib/libglibmm- 2.4.so.1.0.24 03ffb000-04023000 r-xp 00000000 fd:00 14129318 /usr/lib/libpangomm- 1.4.so.1.0.30 04023000-04026000 rw-p 00027000 fd:00 14129318 /usr/lib/libpangomm- 1.4.so.1.0.30 04028000-04066000 r-xp 00000000 fd:00 14132428 /usr/lib/libatkmm- 1.6.so.1.0.30 04066000-0406a000 rw-p 0003d000 fd:00 14132428 /usr/lib/libatkmm- 1.6.so.1.0.30 0406a000-0406b000 rw-p 0406a000 00:00 0 042e8000-045ef000 r-xp 00000000 fd:00 14132426 /usr/lib/libgtkmm- 2.4.so.1.0.30 045ef000-0463c000 rw-p 00307000 fd:00 14132426 /usr/lib/libgtkmm- 2.4.so.1.0.30 04810000-0481b000 r-xp 00000000 fd:00 14132140 /usr/lib/liblash.so.1.1.1 0481b000-0481c000 rw-p 0000a000 fd:00 14132140 /usr/lib/liblash.so.1.1.1 04823000-04826000 r-xp 00000000 fd:00 18515446 /lib/libuuid.so.1.2 04826000-04827000 rw-p 00002000 fd:00 18515446 /lib/libuuid.so.1.2 0484b000-04860000 r-xp 00000000 fd:00 18515498 /lib/libtinfo.so.5.6 04860000-04863000 rw-p 00014000 fd:00 18515498 /lib/libtinfo.so.5.6 04865000-04895000 r-xp 00000000 fd:00 18515499 /lib/libreadline.so.5.2 04895000-04899000 rw-p 00030000 fd:00 18515499 /lib/libreadline.so.5.2 04899000-0489a000 rw-p 04899000 00:00 0 04bea000-04bfc000 r-xp 00000000 fd:00 14148726 /usr/lib/libjack.so.0.0.28 04bfc000-04bfe000 rw-p 00011000 fd:00 14148726 /usr/lib/libjack.so.0.0.28 04bfe000-04c06000 rw-p 04bfe000 00:00 0 08047000-08102000 r-xp 00000000 fd:00 14137726 /usr/bin/seq24 08102000-08104000 rw-p 000bb000 fd:00 14137726 /usr/bin/seq24 08104000-0810f000 rw-p 08104000 00:00 0 0810f000-0817f000 rw-p 000bc000 fd:00 14137726 /usr/bin/seq24 0817f000-083a7000 rw-p 0817f000 00:00 0 [heap] b581a000-b587a000 rw-s 00000000 00:08 2785297 /SYSV00000000 (deleted) b587a000-b58da000 rw-s 00000000 00:08 2752528 /SYSV00000000 (deleted) b58da000-b594a000 r--p 00000000 fd:00 14519499 /usr/share/fonts/dejavu-lgc/DejaVuLGCSans.ttf b594a000-b594e000 r--s 00000000 fd:00 3342440 /var/cache/fontconfig/177aa5f8e4784b879645141d1d73ae7a-x86.cache-2 b594e000-b5952000 r--s 00000000 fd:00 3342438 /var/cache/fontconfig/f4023520196b2bc2c439adcafb2470ff-x86.cache-2 b5952000-b5954000 r--s 00000000 fd:00 3342475 /var/cache/fontconfig/87f5e051180a7a75f16eb6fe7dbd3749-x86.cache-2 b5954000-b595a000 r--s 00000000 fd:00 3342884 /var/cache/fontconfig/b79f3aaa7d385a141ab53ec885cc22a8-x86.cache-2 b595a000-b595c000 r--s 00000000 fd:00 3342433 /var/cache/fontconfig/c92de17a4917e89f837a0bbd6277be6a-x86.cache-2 b595c000-b595d000 r--s 00000000 fd:00 3342431 /var/cache/fontconfig/6cfc7d49b27ba7d3eb71ab86e04def2c-x86.cache-2 b595d000-b595e000 r--s 00000000 fd:00 3342905 /var/cache/fontconfig/b887eea8f1b96e1d899b44ed6681fc27-x86.cache-2 b595e000-b595f000 r--s 00000000 fd:00 3342910 /var/cache/fontconfig/860639f272b8b4b3094f9e399e41bccd-x86.cache-2 b595f000-b5960000 r--s 00000000 fd:00 3342891 /var/cache/fontconfig/211368abcb0ff835c229ff05c9ec01dc-x86.cache-2 b5960000-b5961000 r--s 00000000 fd:00 3342908 /var/cache/fontconfig/c46020d7221988a13df853d2b46304fc-x86.cache-2 b5961000-b5962000 r--s 00000000 fd:00 3342937 /var/cache/fontconfig/fa2b533b7056bdadb961f088bc0a978b-x86.cache-2 b5962000-b5963000 r--s 00000000 fd:00 3342906 /var/cache/fontconfig/df893b4576ad6107f9397134092c4059-x86.cache-2 b5963000-b5964000 r--s 00000000 fd:00 3342888 /var/cache/fontconfig/ff627ea95a65192232277bf7c8a56f23-x86.cache-2 b5964000-b5965000 r--s 00000000 fd:00 3342890 /var/cache/fontconfig/900402270e15d763a6e008bb2d4c7686-x86.cache-2 b5965000-b5966000 r--s 00000000 fd:00 3342907 /var/cache/fontconfig/2881ed3fd21ca306ddad6f9b0dd3189f-x86.cache-2 b5966000-b5967000 r--s 00000000 fd:00 3342445 /var/cache/fontconfig/e61abf8156cc476151baa07d67337cae-x86.cache-2 b5967000-b596a000 r--s 00000000 fd:00 3342889 /var/cache/fontconfig/b67b32625a2bb51b023d3814a918f351-x86.cache-2 b596a000-b596d000 r--s 00000000 fd:00 3342449 /var/cache/fontconfig/46b47dbc682d2ca4191e148ea7bde7f2-x86.cache-2 b596d000-b596e000 r--s 00000000 fd:00 3342442 /var/cache/fontconfig/b4d0b56f766d89640448751fcd18ec1e-x86.cache-2 b596e000-b5974000 r--s 00000000 fd:00 3342428 /var/cache/fontconfig/7ddba6133ef499da58de5e8c586d3b75-x86.cache-2 b5974000-b5978000 r--s 00000000 fd:00 3342435 /var/cache/fontconfig/766670f26ba71bf5eea34bac120eb600-x86.cache-2 b5978000-b5980000 r--s 00000000 fd:00 3342429 /var/cache/fontconfig/e19de935dec46bbf3ed114ee4965548a-x86.cache-2 b5980000-b5982000 r--s 00000000 fd:00 3342441 /var/cache/fontconfig/273572fe21058bf32b3be773088b9170-x86.cache-2 b5982000-b5985000 r--s 00000000 fd:00 3342827 /var/cache/fontconfig/d04038e664b0033ae700a78c51f179d3-x86.cache-2 b5985000-b598a000 r--s 00000000 fd:00 3342826 /var/cache/fontconfig/beeeeb3dfe132a8a0633a017c99ce0c0-x86.cache-2 b598a000-b5990000 r-xp 00000000 fd:00 14352422 /usr/lib/gtk-2.0 /2.10.0/loaders/libpixbufloader-xpm.so b5990000-b5991000 rw-p 00005000 fd:00 14352422 /usr/lib/gtk-2.0 /2.10.0/loaders/libpixbufloader-xpm.so b5991000-b5992000 ---p b5991000 00:00 0 b5992000-b6192000 rw-p b5992000 00:00 0 b6192000-b6193000 ---p b6192000 00:00 0 b6193000-b6c96000 rw-p b6193000 00:00 0 b6c96000-b6cab000 r-xp 00000000 fd:00 14129349 /usr/lib/libelf-0.131.so b6cab000-b6cad000 rw-p 00014000 fd:00 14129349 /usr/lib/libelf-0.131.so b6cae000-b6cbe000 r-xp 00000000 fd:00 14352785 /usr/lib/gtk-2.0 /2.10.0/engines/libnodoka.so b6cbe000-b6cbf000 rw-p 0000f000 fd:00 14352785 /usr/lib/gtk-2.0 /2.10.0/engines/libnodoka.so b6cbf000-b6d12000 r-xp 00000000 fd:00 14975863 /usr/lib/bug-buddy/libbreakpad.so.0.0.0 b6d12000-b6d13000 rw-p 00052000 fd:00 14975863 /usr/lib/bug-buddy/libbreakpad.so.0.0.0 b6d13000-b6f13000 r--p 00000000 fd:00 14125687 /usr/lib/locale/locale-archive b6f13000-b6f14000 ---p b6f13000 00:00 0 b6f14000-b7714000 rw-p b6f14000 00:00 0 b7714000-b7715000 ---p b7714000 00:00 0 b7715000-b7f15000 rw-p b7715000 00:00 0 b7f15000-b7f1f000 r-xp 00000000 fd:00 18514028 /lib/libnss_files-2.7.so b7f1f000-b7f20000 r--p 00009000 fd:00 18514028 /lib/libnss_files-2.7.so b7f20000-b7f21000 rw-p 0000a000 fd:00 18514028 /lib/libnss_files-2.7.so b7f21000-b7f2e000 rw-p b7f21000 00:00 0 b7f30000-b7f3e000 r-xp 00000000 fd:00 14354738 /usr/lib/gtk-2.0 /modules/libgnomebreakpad.so b7f3e000-b7f3f000 rw-p 0000d000 fd:00 14354738 /usr/lib/gtk-2.0 /modules/libgnomebreakpad.so b7f3f000-b7f40000 rw-p b7f3f000 00:00 0 b7f40000-b7f41000 r-xp b7f40000 00:00 0 [vdso] bfb9a000-bfbaf000 rw-p bffeb000 00:00 0 [stack] 2426227a-57b9-4329-4de7a6e6-687e637d is dumped Client Seq24 removed from project project-1 Project project-1 removed -------------- is it clashing the lash server? |
|
From: Rick B. \(HM\) <ri...@ho...> - 2008-03-19 12:44:00
|
Ahso. Somehow I could paint notes in patch edit mode, but when I switched to song mode I couldn't get it to work. Now it does. I think I had the right->left click procedure reversed (I thought I was seeing some weirdness in the window manager or something). Just getting started with this, but I've been looking forward to "playing" with this tool for quite some time now. Thanks! Rick ----- Original Message ----- From: <eri...@fr...> To: <seq...@li...> Sent: Tuesday, March 18, 2008 3:44 PM Subject: Re: [seq24-users] Can't edit in song mode? > Hi Rick, > > > I'm experimenting with seq24, and I've created some patterns, but > > when I go into song mode, if I right-click and drag the pencil, > > nothing is painteddrawn in the tracks. > > > Yeah, painting singles note is a bit of a pain in the lower back :-S > Click & hold right mouse button. Then, while still holding the right > mouse button, left click on the position where you want to put a note > (or a pattern, when in the song editor). > > Cheers, > Eric > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > seq24-users mailing list > seq...@li... > https://lists.sourceforge.net/lists/listinfo/seq24-users > |
|
From: <eri...@fr...> - 2008-03-18 20:55:17
|
Hi Rick,
> I'm experimenting with seq24, and I've created some patterns, but
> when I go into song mode, if I right-click and drag the pencil,
> nothing is painteddrawn in the tracks.
Yeah, painting singles note is a bit of a pain in the lower back :-S
Click & hold right mouse button. Then, while still holding the right
mouse button, left click on the position where you want to put a note
(or a pattern, when in the song editor).
Cheers,
Eric
|
|
From: Rick B. <ri...@ho...> - 2008-03-16 03:05:48
|
Hello all, I'm experimenting with seq24, and I've created some patterns, but when I go into song mode, if I right-click and drag the pencil, nothing is painted\drawn in the tracks. Does anyone have an explanation or can you tell me what I'm doing wrong? I'm using seq24 v0.8.7 on gOS Rocket beta (Enlightenment wm). Editing patterns using the pencil and dragging seems to work OK Thanks, Rick _________________________________________________________________ Connect and share in new ways with Windows Live. http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008 |
|
From: Ken R. <ke...@re...> - 2008-02-08 17:05:51
|
I've been using seq24 for about 6 months now, and it's great. The only thing that's really annoying me about it, is that it doesn't honor the tempo saved with the file. No matter what tempo is saved, seq24 keeps the default of 120bpm. I know the correct tempo is saved in the MIDI file, because I can inspect the file, and it's right there. Someone told me a while back that this has to do with a 64-bit number issue, or a a part of the seq24 code that reads the SMF, that only reads the high-order 32 bits and sees the tempo in the file as 0 instead of what it really is, and thus keeps the default instead of using the saved tempo. Has anyone fixed this? I've had an action item for months to go poking around in the code and try to fix it, but I'd be surprised if someone hasn't already done that. Thanks! -ken |
|
From: adolson <ad...@gm...> - 2007-12-04 16:32:29
|
Here's a doc I wrote last year: https://help.ubuntu.com/community/HowToSeq24Introduction Hope it helps. On Dec 4, 2007 11:11 AM, bseeadler <bse...@ea...> wrote: > I'm lnux newbie who has managed to write a mandolin tune with lilypond and save it as a .midi. I was hoping to add a drum and guitar track and then just hook up my desktop speakers to the laptop I'm using (fedora core 6) and play along. I downloaded seq24 but I'm lost. When I import the midi I can see it playing but I can't hear it and when try to open seq24 file for info it says it's a binary. Are there any instructions anywhere? Thanks > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > seq24-users mailing list > seq...@li... > https://lists.sourceforge.net/lists/listinfo/seq24-users > |
|
From: bseeadler <bse...@ea...> - 2007-12-04 16:12:09
|
I'm lnux newbie who has managed to write a mandolin tune with lilypond and save it as a .midi. I was hoping to add a drum and guitar track and then just hook up my desktop speakers to the laptop I'm using (fedora core 6) and play along. I downloaded seq24 but I'm lost. When I import the midi I can see it playing but I can't hear it and when try to open seq24 file for info it says it's a binary. Are there any instructions anywhere? Thanks |
|
From: Ken R. <ke...@re...> - 2007-09-25 18:21:37
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Sep 19, 2007 at 12:52:20PM +0200, Malte Steiner wrote: > Hello > > I've been using seq24 for a few weeks now, and I like it. I'll be using it for a liveset on Saturday. > > > > A few questions still remain after using it and reading docs, searching on the internets, etc: > > > > 1) How can I get seq24 to save and restore the BPM setting for a song? > You are using a 64 bit system, right? Same problem bothers me on 64 > Studio, in 32 bit Ubuntu it works alright. Yes, I'm on 64-bit. Gah, looks like it's a bug then. I'll bet it's in lurking somewhere in the bit-shifting of the tempo byte of the Format 1 MIDI file. > > Is seq24 maintained anymore or abandoned? I am thinking to jump on board > and help with coding. Would love to see a sceneswitch so that many > patterns can be activated at once. That would be much more useful to me than song mode. I was going to hack my own "scene mode" together in PD, by having it send MIDI events to seq24 to trigger groups of loops. But it'd be nicer if it was in seq24. > > > 4) I'd be really neat if seq24 was OSC-ified. It's such a nice GUI for loop entering/editing; it'd be great if I could just use it as a front-end to other programs written in PD/ChucK/SuperCollider/etc. > > We discussed OSC sequencers on LAU recently, but not many are available now. Or even if its parameters were OSC-controlled. Or, perhaps even more promising, dbus-enabled. Also, seq24 doesn't actually support the ALSA sequencer interface; it seems like it uses raw MIDI. Its connections don't show up in aconnect. Finally, if there's a wishlist somewhere: I'd be nice if it could support JACK MIDI, for sample-accurate MIDI framing and integration into JACK. Also, if it supports JACK MIDI, it would automatically obtain cross-platform connectivity: since JACK now runs on Linux, OSX, and now Windoze too. - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+VFne8HF+6xeOIcRAun+AKCHL2EeFA2sTI1hleO1QPf7v+ni2wCeJOwQ 188nmdqr6/64i5calUpOEkY= =ozlX -----END PGP SIGNATURE----- |
|
From: yawfle <se...@ya...> - 2007-09-20 19:15:54
|
On Wed, 19 Sep 2007 11:21:10 -0700 (PDT), "Sam Brauer" <sam...@ya...> said: > Would you post that tarball to this list? I'm curious to see what it > adds. Apparently the size limit for attachments on this list is 40k, so I've uploaded the patched version here: http://sharebee.com/434afda8 ...for posterity. :) |
|
From: Sam B. <sam...@ya...> - 2007-09-19 18:21:22
|
Would you post that tarball to this list? I'm curious to see what it adds= .=0AI'm using seq24 with various patches as my main sequencer, and love it,= but have a wishlist of improvements.=0A=0ACheers!=0A- Sam=0A=0A----- Origi= nal Message ----=0AFrom: yawfle <se...@ya...>=0ATo: steiner= @block4.com=0ACc: seq...@li...=0ASent: Wednesday, Sept= ember 19, 2007 2:12:39 PM=0ASubject: Re: [seq24-users] A few random questio= ns=0A=0AOn Wed, 19 Sep 2007 12:52:20 +0200, "Malte Steiner" <steiner@block4= .com>=0Asaid:=0A=0A> Is seq24 maintained anymore or abandoned? I am thinkin= g to jump on board =0A> and help with coding. Would love to see a sceneswit= ch so that many =0A> patterns can be activated at once.=0A=0AThere was a br= anch with some improvements over the last official version=0Aposted here:= =0A=0Ahttp://www.desfonema.com.ar/index.php?page=3Dsoftware=0A=0AThat domai= n doesn't seem to be there atm/anymore, but I can mail you a=0Acopy of the = source tarball if you wanted to include some of the=0Aimprovements in furth= er development (I've been using that version for so=0Along that I can't rem= ember all of the things that weren't in the=0Aoriginal - mostly quantize-as= -you-record and a bunch of interface=0Aenhancements, I think). It would be = great to see some further=0Adevelopment on this useful software, especially= since I've got a friend=0Ausing the windoze version and swapping files wit= h me now... :)=0A=0A-------------------------------------------------------= ------------------=0AThis SF.net email is sponsored by: Microsoft=0ADefy al= l challenges. Microsoft(R) Visual Studio 2005.=0Ahttp://clk.atdmt.com/MRT/g= o/vse0120000070mrt/direct/01/=0A___________________________________________= ____=0Aseq24-users mailing lis...@li...=0Ahttps= ://lists.sourceforge.net/lists/listinfo/seq24-users=0A=0A=0A=0A=0A=0A=0A=0A= =0A_________________________________________________________________= ___________________=0AMoody friends. Drama queens. Your life? Nope! - their= life, your story. Play Sims Stories at Yahoo! Games.=0Ahttp://sims.yahoo.c= om/ |
|
From: yawfle <se...@ya...> - 2007-09-19 18:12:45
|
On Wed, 19 Sep 2007 12:52:20 +0200, "Malte Steiner" <st...@bl...> said: > Is seq24 maintained anymore or abandoned? I am thinking to jump on board > and help with coding. Would love to see a sceneswitch so that many > patterns can be activated at once. There was a branch with some improvements over the last official version posted here: http://www.desfonema.com.ar/index.php?page=software That domain doesn't seem to be there atm/anymore, but I can mail you a copy of the source tarball if you wanted to include some of the improvements in further development (I've been using that version for so long that I can't remember all of the things that weren't in the original - mostly quantize-as-you-record and a bunch of interface enhancements, I think). It would be great to see some further development on this useful software, especially since I've got a friend using the windoze version and swapping files with me now... :) |
|
From: brian <job...@sb...> - 2007-09-19 13:09:42
|
And I'd love to see it decoupled from alsa so I can use it on my mac book. (or is there an alsa emulator for mac?) Malte Steiner wrote: > Hello > >> I've been using seq24 for a few weeks now, and I like it. I'll be using it for a liveset on Saturday. >> >> A few questions still remain after using it and reading docs, searching on the internets, etc: >> >> 1) How can I get seq24 to save and restore the BPM setting for a song? >> > You are using a 64 bit system, right? Same problem bothers me on 64 > Studio, in 32 bit Ubuntu it works alright. > > Is seq24 maintained anymore or abandoned? I am thinking to jump on board > and help with coding. Would love to see a sceneswitch so that many > patterns can be activated at once. > > >> 4) I'd be really neat if seq24 was OSC-ified. It's such a nice GUI for loop entering/editing; it'd be great if I could just use it as a front-end to other programs written in PD/ChucK/SuperCollider/etc. >> > > We discussed OSC sequencers on LAU recently, but not many are available now. > > Cheers, > > Malte > |
|
From: Malte S. <st...@bl...> - 2007-09-19 10:58:59
|
Hello > I've been using seq24 for a few weeks now, and I like it. I'll be using it for a liveset on Saturday. > > A few questions still remain after using it and reading docs, searching on the internets, etc: > > 1) How can I get seq24 to save and restore the BPM setting for a song? You are using a 64 bit system, right? Same problem bothers me on 64 Studio, in 32 bit Ubuntu it works alright. Is seq24 maintained anymore or abandoned? I am thinking to jump on board and help with coding. Would love to see a sceneswitch so that many patterns can be activated at once. > 4) I'd be really neat if seq24 was OSC-ified. It's such a nice GUI for loop entering/editing; it'd be great if I could just use it as a front-end to other programs written in PD/ChucK/SuperCollider/etc. We discussed OSC sequencers on LAU recently, but not many are available now. Cheers, Malte -- Malte Steiner media art + development -www.block4.com- |
|
From: Ken R. <ke...@re...> - 2007-09-19 06:51:36
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been using seq24 for a few weeks now, and I like it. I'll be using it for a liveset on Saturday. A few questions still remain after using it and reading docs, searching on the internets, etc: 1) How can I get seq24 to save and restore the BPM setting for a song? 2) Several of what look like editable GTK combo-boxes aren't editable, like # of measures, zoom ratio, and tempo! The keyboard commands work to increment/decrement, as do the up-down arrows and/or pop-up menus, but I just want to type a number into the box, it's faster, and the box is editable so it looks like it should be able to do that. 3) Song mode doesn't appear to work. No matter what I do in the song view, it doesn't appear to have any effect on which loops are enabled or not. Not a big deal; I may just blow off song mode and write a PD program to do my song-level arranging, triggering seq24 via MIDI (virmidi) instead. 4) I'd be really neat if seq24 was OSC-ified. It's such a nice GUI for loop entering/editing; it'd be great if I could just use it as a front-end to other programs written in PD/ChucK/SuperCollider/etc. - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG8Mawe8HF+6xeOIcRAor/AJ9SUJinTuO9zACVY0SYlL38HoTzJgCcCHoZ z+d1l6lnw7qEnSNi6pXyHpw= =dyXN -----END PGP SIGNATURE----- |
|
From: David <thr...@gm...> - 2007-09-11 01:54:59
|
How can I start recording real time midi events off my keyboard, the moment i start playing the keyboard? Currently I have to start the seq24 application first, then start playing on my midi keyboard. |
|
From: gregory z. <zi...@ho...> - 2007-07-09 09:11:00
|
hi, i've been getting error messages when i close seq24. i can't remember what it says and it doesn't seem to be happening right now, but now when i open a midi file, if i try to edit a track, seq24 crashes and quits. i can create new tracks and add notes, just not edit old ones. i just joined this list, so forgive me if this is old news. is there a known solution? thanks in advance, greg _________________________________________________________________ http://liveearth.msn.com |
|
From: europeen <sko...@or...> - 2007-07-01 10:10:44
|
Le lundi 19 mars 2007 à 11:11 -0300, Ivan Hernandez a écrit : > I forgotten instructions of use. 'p' to activate paint, 'P' (shift p) to > deactivate. > Remember to "select" the piano roll instead of writing on other > controls, like the name edit. that's a little tricky but you will > overcome that. > ivan Pfiouuuuuu, I was unoccupied this time and I tried again to patch with infos I found on a website. It runs good with : patch -Np1 -i paint_patch.diff 4 months after, I can use your feature. Thanks again :-) STan. |
|
From: Florian S. <mis...@gm...> - 2007-06-16 12:38:17
|
On Saturday 16 June 2007, ben.g wrote:
> hi there, im using seq24 in windows and wonder if anyone can post a list of
> all the keyboard shortcuts to use, as there isnt any documentation included
> w/ the app...any help is much appreciated.
> cheers,
> Ben
Download the tarball. It has a file called SEQ24 :) For your convenience i
post it here from the 0.8.7 tarball:
SEQ24 - Midi Sequencer
-----------------------------------------------------------
[1] What & Why
[2] Who
[3] Interface
[4] Contact / Bugs / Ideas
[5] License
-----------------------------------------------------------
[1] What & Why
Seq24 is a real-time midi sequencer. It was created to
provide a very simple interface for editing and playing
midi 'loops'. After searching for a software based
sequencer that would provide the functionality needed for
a live performance, there was little found in the
software realm. I set out to create a very minimal sequencer
that excludes the bloated features of the large software
sequencers, and includes a small subset of features that
I have found usable in performing.
-----------------------------------------------------------
[2] Who
Written by Rob C. Buse. I wrote this program to fill a
hole. I figure it would be a waste if I was the only one
using it. So, I released it under the GPL.
-----------------------------------------------------------
[3] Interface
The program is basically a loop playing machine with a
simple interface.
[3a] Main Window
* File.
The File menu is used to save and load standard
MIDI files. It should be able to handle any
Format 1 standard files, Any other sequencer
should be capable of exporting.
* Options
Used to configure what bus midi clock gets dumped to.
* Help.
Shows the About box.
* Boxes
Each box represents a loop. By right clicking
on an empty box you bring up a menu to create
a new loop, or edit a existing one.
Left clicking on a box will change its state
from muted (white) to playing (black) when
the sequencer is running.
By clicking and holding the left button on a sequence,
you can drag it to a new location on the grid.
Right Clicking will bring up a menu of available options
for the sequence. Here you can select the midi bus/channel.
You can also clear all performance data (on/off) see section
[3d] for more info.
* 'Screen Sets'
You only see 32 loops in the main window. This
is a screen set. You can switch between sets
by using the '[' and ']' keys on your keyboard or
the spin widget labeled set.
There are a total of 32 sets, for a total of
1024 loops.
* BPM
The ; and ' keys will increase/decrease tempo as
will the bpm spinner.
* Muting and Unmuting Tracks.
Left clicking on a Tracks will toggle its playing
status. Hitting its assigned keyboard key will
also toggle its status. Below is the grid thats
mapped to the loops on the screen set.
[1 ][2 ][3 ][4 ][5 ][6 ][7 ][8 ]
[q ][w ][e ][r ][t ][y ][u ][i ]
[a ][s ][d ][f ][g ][h ][j ][k ]
[z ][x ][c ][v ][b ][n ][m ][, ]
* Replace
Holding down 'Left Ctrl' while selecting a sequence
will mute all other sequences and turn on the selected
sequences.
* Restore
Holding 'Alt' will save the state of playing sequences
and restore them when 'Alt' is lifted.
Holding 'Left Ctrl' and 'Alt' at the same time will enable
you to flip over to new sequences briefly and then
flip right back upon lifting 'Alt'.
* Queue
Holding 'Right Ctrl' will queue a on/off toggle for a
sequence when the loop ends.
[3b] Options Window
This window allows us to select which sequence gets midi
clock, and which incoming midi events control the sequencer.
[3c] Edit Window
Right clicking on the main window then selecting
New/Edit will bring up the edit window.
The top bar of the sequence editor lets you
change the name of the sequence, the time
signature of the piece, and how long the loop
is.
Snap selects where the notes will be drawn. Note
Length determines what size they will be. Scale
is the relation between midi ticks and pixels.
1:4 = 4 ticks per pixel. The Bus button selects
which ALSA device to use, and which midi channel.
The 3rd line contains the Undo button, which will roll
back any changes to the sequence from this session.
You can select which Scale and Key the piece is in
and it will grey out those keys on the roll not in
the key. You can select a sequence to draw on the
background to help with writing corresponding parts.
Holding the mouse over any button for a short period
will let you view what it does.
While the sequencer is playing, you can mute/unmute
the sequence by toggling the [Play] button. The
[Thru] button will relay any ALSA midi input
to the sequences Bus and midi channel. [Record]
will capture and ALSA midi input and save it in the
sequence.
On both the grid window and the event window, HOLDING
down the right mouse button will change your cursor
to a pencil and put you in 'draw' mode. Then while
still HOLDING the right mouse button, click the left
mouse button to insert new notes. Many people find
this combination strange at first, but once you get
used to it, it becomes a very fast method of note
manipulation.
Pressing the middle mouse button will let you change
the length of the note.
The left mouse button lets you select multiple events
which can then be clicked and moved, cut (Ctrl-X),
copy (Ctrl-C), or pasted (Ctrl-V). When the notes are
selected, you can delete them with the Delete key.
Right clicking on the event strip ( directly under
the paino roll grid ) will allow you to add/select/move
midi events (not note on/off messages) somewhat like the
piano grid.
The data editor ( directly under the event strip ) is used
to change note velocities, channel pressure, control codes,
patch select, etc. Just click + drag the mouse across
the window to draw a line. The values will match that line.
Any events that are selected in the paino roll or event
strip can have their values modified with the mouse
wheel.
The [Event] button allows you to select which type of data
the event strip and data editor are currently displaying.
[3d] Performace Edit
Right Click on the Roll to enter draw mode, gray boxes
represent when the track is on. Right and left click to
drop the [R] and [L] anchors on the bar indicator. Use
the collapse and expand button to modify events. Middle
click on the bar indicator to drop a new start position.
You can only change the start position when the performace
is not playing.
[3e] .seq24rc File
After you run seq24 for the first time, it will generate
a .seq24rc file in your home directory.
It contains the the data for remote midi control, keyboard
control, and midi clock.
* [midi-control]
For each sequence, we can set up midi events to turn a
sequence on, off, or toggle it. We see the following
lines in the [midi-control] section:
0 [0 0 0 0 0 0] [0 0 0 0 0 0] [0 0 0 0 0 0]
1 [0 0 0 0 0 0] [0 0 0 0 0 0] [0 0 0 0 0 0]
2 [0 0 0 0 0 0] [0 0 0 0 0 0] [0 0 0 0 0 0]
...
The first number is the sequence in the main window. Each set
of brackets corresponds to a midi filter. If the incoming midi
event matches the filter, it will either [toggle],[on],or[off]
the sequence respectivaly.
The layout of each filter inside the bracket is as follows:
[(on/off) (inverse) (midi status byte (channel ignored))
(data1) (data2 min) (data2 max)]
If the on/off is set to 1, it will match the incoming midi
to the pattern and perfrom the action (on/off/toggle)
if the data falls in the range specified. All values
are in decimal.
The last three is the range of data that will match.
The following is an example of responding to note on events,
note 0, with any velocity to turn the sequence on, and note
off events, note 0, and any velocity to turn the sequence off.
Toggle On Off
1 [0 0 0 0 0 0] [1 0 144 0 0 127] [1 0 128 0 0 127]
the inverse field will make the sequence perform the opposite
action (off for on, on for off) if the data falls outside the
specified range. This is cool because you can map several
sequences to a knob or fader.
The following example would map a row of sequences to one knob
sending out changes for Control Code 1:
Toggle On Off
0 [0 0 0 0 0 0] [1 1 176 1 0 15] [0 0 0 0 0 0]
1 [0 0 0 0 0 0] [1 1 176 1 16 31] [0 0 0 0 0 0]
2 [0 0 0 0 0 0] [1 1 176 1 32 47] [0 0 0 0 0 0]
3 [0 0 0 0 0 0] [1 1 176 1 48 63] [0 0 0 0 0 0]
4 [0 0 0 0 0 0] [1 1 176 1 64 79] [0 0 0 0 0 0]
5 [0 0 0 0 0 0] [1 1 176 1 80 95] [0 0 0 0 0 0]
6 [0 0 0 0 0 0] [1 1 176 1 96 111] [0 0 0 0 0 0]
7 [0 0 0 0 0 0] [1 1 176 1 112 127] [0 0 0 0 0 0]
After the list of sequences and their midi events, you can
set seq24 to handle midi events and change the following:
bpm up and down, screen set up and down.
replace, snapshot, and queue ( see the end of 3a )
* [midi-clock]
The midi clock fields will contain the clocking state from the last
time seq24 was run. Turn off clock with a 0, or on with a 1.
* [keyboard-control]
The keyboard control is a dump of the keys that seq24
recognises and its corresponding sequence number.
There are also the modifier keys: replace, snapshot,
and queue ( see the end of 3a ).
To get the correct keys, run seq24 with --show_keys.
[3f] JACK Transport
In order to run seq24 with JACK Tranport Sync, you need
to enable it at the command line with the following flags:
--jack_transport : seq24 will sync to JACK transport
if the JACK server is available.
--jack_master : seq24 will try to be JACK master
--jack_master_cond : The attempt to be JACK master will
fail if there is already a master,
otherwise it will just take over.
--jack_start_mode <x> : When seq24 is synced to JACK,
The playback command comes
from the JACK server. seq24 will
play in performance mode
by default (section [3d]).
If you want live mode, set
--jack_start_mode 0.
It is best to run seq24 with another master like ardour.
You can not change the BPM of seq24 while
rolling in JACK sync mode.
-----------------------------------------------------------
[4] Contact
If you have Ideas about seq24 or a bug report,
please email se...@fi.... If its a bug report,
please add [BUG] to the subject.
-----------------------------------------------------------
[5] License
Released under the Terms of the GPL. See the COPYING file
for a full readout.
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
|
|
From: ben.g <be...@co...> - 2007-06-16 05:48:52
|
hi there, im using seq24 in windows and wonder if anyone can post a list of all the keyboard shortcuts to use, as there isnt any documentation included w/ the app...any help is much appreciated. cheers, Ben -- |
|
From: Florian S. <mis...@gm...> - 2007-03-30 22:42:45
|
On Friday 30 March 2007, Gareth Edwards wrote: > Hi there, > > I've been studying the seq24 code with a view to modifying the code for > my own application and I've got a question about the way it is written - > I'm an ALSA newbie so please forgive if it's a stupid question. > > The output thread seems to take great care of its timing accuracy in > setting it's sleep time in the main timing loop (so much that there is > an command line option to increase the thread priority, presumably to > increase this accuracy) - but the alsa sequencer API seems to look after > this timing for you. I guess I'm not seeing why seq24 needs to go to the > lengths it does when it could just supply the events to the sequencer > API and then relax? > > If the answer is "go away and read the API docs properly so you > understand them", then that's fine <G> Well, i suppose some people think it's easier to manage the timing in their own app and dispatch messages directly rather than relying on alsa seq's queues and timing. Alsa offers support for both paradigms. Flo -- Palimm Palimm! http://tapas.affenbande.org |
|
From: Gareth E. <gde...@bl...> - 2007-03-30 20:25:58
|
Hi there, I've been studying the seq24 code with a view to modifying the code for my own application and I've got a question about the way it is written - I'm an ALSA newbie so please forgive if it's a stupid question. The output thread seems to take great care of its timing accuracy in setting it's sleep time in the main timing loop (so much that there is an command line option to increase the thread priority, presumably to increase this accuracy) - but the alsa sequencer API seems to look after this timing for you. I guess I'm not seeing why seq24 needs to go to the lengths it does when it could just supply the events to the sequencer API and then relax? If the answer is "go away and read the API docs properly so you understand them", then that's fine <G> Cheers Gareth |
|
From: <lin...@ya...> - 2007-03-28 16:49:55
|
hello, i already asked here in the list some month ago, but got no reply, so i try again now: 1) are there any plans to make it possible to use seq24 as a midi-slave? if the answer is yes: 2.1) when will that happen (in the next release)?# or if the answer is no: 2.2) i use muse (or hydrogen) to make jack to a midi-slave und sync seq24 with jack-transport. does anyone know a smaller programm to make jack a midi-slave (muse and hydrogen are quite big and slow down my performance)? hope, that this time i get a reply (even if the answer is not what i want to hear)... thanks and greetings l.chaos -- _________________________________________________________________ http://www.audio4linux.de - musikmachen mit offenen quellen |
|
From: europeen <sko...@or...> - 2007-03-22 15:24:47
|
up ? Le lundi 19 mars 2007 à 17:10 +0100, europeen a écrit : > Le lundi 19 mars 2007 à 11:09 -0300, Ivan Hernandez a écrit : > > Ok. I have made a patch for that and it apply to the latest stable > > version (http://filter24.org/seq24/seq24-0.8.7.tar.gz) > > > > you can do this: > > $ wget http://filter24.org/seq24/seq24-0.8.7.tar.gz > > $ tar -xzvf seq24-0.8.7.tar.gz > > $ cd seq24-0.8.7 > > $ patch -p1 ../paint_patch.diff > > > > you have your patched source now. compile as usual. > > luck! > > ivan > > > Hi, thanks for the work :) > > Just a problem : I copied the .diff file in the folder. I run : patch > -p1 ../paint_patch.diff, but hothing happens. > > > STan. |
|
From: Ivan H. <ihe...@ki...> - 2007-03-19 18:56:39
|
try $ patch -p1 -i paint_patch.diff europeen escribió: > Le lundi 19 mars 2007 à 11:09 -0300, Ivan Hernandez a écrit : > >> Ok. I have made a patch for that and it apply to the latest stable >> version (http://filter24.org/seq24/seq24-0.8.7.tar.gz) >> >> you can do this: >> $ wget http://filter24.org/seq24/seq24-0.8.7.tar.gz >> $ tar -xzvf seq24-0.8.7.tar.gz >> $ cd seq24-0.8.7 >> $ patch -p1 ../paint_patch.diff >> >> you have your patched source now. compile as usual. >> luck! >> ivan >> > > > Hi, thanks for the work :) > > Just a problem : I copied the .diff file in the folder. I run : patch > -p1 ../paint_patch.diff, but hothing happens. > > > STan. > > > > |