seq24-users — A place for seq24 users to ask questions and share ideas.

Re: [seq24-users] expected primary expression during make (seq24-0.6.3)

[Esben S. <b0...@es...>]

"Rob Buse" <rc...@fi...> writes:

> distro 

I have my own distro, using glibc-2.3.4-20040828,
linux-2.6.12-rc3-RT-V0.7.46-02

> what does your /usr/include/pthread.h file look like?

http://esben-stien.name/goldenarms/pthread.h

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
          [sip|iax]:   e     e 
           jid:b0ef@    n     n

[seq24-users] seq24 & OSX

[c h. <cal...@ho...>]

I made a bit of a foray into this a few months ago, but got caught up with 
other things.  Here's what I found.

The CoreMidi/AudioToolbox classes of most immmediate interest are 
MIDIEndpointRef, MusicSequence, MusicTrack, MIDINoteMessage, and MusicPlayer 
(anyone interested should have a look at <AudioToolbox/AudioToolbox.h> and 
<CoreMIDI/MIDIServices.h>).  A Music Player is used to control the playing 
of a MusicSequence and is associated with at most one Music Sequence (which 
can also only be associated with one MusicPlayer).  MusicSequences are 
associated with a single MIDIEndpointRef (midi device), and contain 
MusicTracks, which in turn contain events such as MIDINoteMessages.  In a 
departure from the Seq24 model, midi channel information is associated with 
events rather than tracks.  The analogy between master/midibus and 
MIDIEndPointRef is also not perfect.  Not having programmed with alsa, I'm 
not sure what an Alsa sequencer client's responsibilities are.  I thought it 
might be more or less equivalent to a MusicPlayer.

Therefore, I thought the following Seq24/Alsa:CoreMidi correspondences might 
provide a starting point:

event -> MIDINoteMessage
sequence -> MusicTrack
perform -> MusicSequence
mastermidibus/midibus (?) -> MIDIEndPointRef
snd_seq_t* -> MusicPlayer

Initially I managed to eliminate all the Alsa dependencies (compiled and ran 
but didn't do much).  Then, as a quick hack, I thought I'd make Seq24 
objects wrapper for the corresponding CoreMidi objects.  A few other things 
had to be shifted around to account for the discrepancies between the two 
models.  I've managed to send some midi to my synth, but haven't been too 
thorough, and really all I have are some rudimentary tinkerings.  I'd be 
interested in helping to port Seq24 as time permits.

Cheers,
Callum.

_________________________________________________________________
Be the first to hear what's new at MSN - sign up to our free newsletters! 
http://www.msn.co.uk/newsletters

Re: [seq24-users] expected primary expression during make (seq24-0.6.3)

[Rob B. <rc...@fi...>]

which linux distro are you using?
what does your /usr/include/pthread.h file look like?

-rob


>Esben Stien <b0...@es...> writes:
>
>> gcc -E mutex.cpp gives me:
>> const pthread_mutex_t mutex::recmutex =3D { .__data =3D { .__kind =3D PTHR=
EAD_MUTEX_RECURSIVE_NP } };
>
>Are we getting nowhere with this issue?. Any more information I could
>provide?
>
>--
>Esben Stien is b0ef@e     s      a
>         http://www. s     t    n m
>          irc://irc.  b  -  i  .   e/%23contact
>          [sip|iax]:   e     e
>           jid:b0ef@    n     n
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: NEC IT Guy Games.
>Get your fingers limbered up and give it your best shot. 4 great events, 4
>opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
>win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=3D20
>_______________________________________________
>seq24-users mailing list
>seq...@li...
>https://lists.sourceforge.net/lists/listinfo/seq24-users

Re: [seq24-users] expected primary expression during make (seq24-0.6.3)

[Esben S. <b0...@es...>]

Esben Stien <b0...@es...> writes:

> gcc -E mutex.cpp gives me: 
> const pthread_mutex_t mutex::recmutex = { .__data = { .__kind = PTHREAD_MUTEX_RECURSIVE_NP } };

Are we getting nowhere with this issue?. Any more information I could
provide?

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
          [sip|iax]:   e     e 
           jid:b0ef@    n     n

[seq24-users] seq24 & OSX

[Kasper J. <kas...@gm...>]

interested.. yes

but how are you going to bypass the alsa-dependency?

so "anyone interested in porting alsa?" is the real question.

Or am I wrong here?



Kasper

Re: [seq24-users] expected primary expression during make (seq24-0.6.3)

[Esben S. <b0...@es...>]

federico <xa...@in...> writes:

> line 24 is:
> const pthread_mutex_t mutex::recmutex = PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP;
> which after preprocessing is:
> const pthread_mutex_t mutex::recmutex = {0, 0, 0, PTHREAD_MUTEX_RECURSIVE_NP, { 0, 0 }};

gcc -E mutex.cpp gives me: 
const pthread_mutex_t mutex::recmutex = { .__data = { .__kind = PTHREAD_MUTEX_RECURSIVE_NP } };

-- 
Esben Stien is b0ef@e     s      a
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
          [sip|iax]:   e     e 
           jid:b0ef@    n     n

[seq24-users] seq24 & OSX

[Vincent L. <vlo...@wa...>]

Hi all,

Anyone interested in porting seq24 to OSX  ?
Please let me know...

vincent

Re: [seq24-users] expected primary expression during make (seq24-0.6.3)

[federico <xa...@in...>]

i looked into the mutex.cpp source code (preprocessed output)

line 24 is:
const pthread_mutex_t mutex::recmutex = 
PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP;

which after preprocessing is:
const pthread_mutex_t mutex::recmutex = {0, 0, 0, 
PTHREAD_MUTEX_RECURSIVE_NP, { 0, 0 }};

this sounds strange because there is no '.' token.
could you verify this?

>mutex.cpp:24: error: expected primary-expression before '.' token
>mutex.cpp:24: error: expected primary-expression before '{' token
>mutex.cpp:24: error: expected `}' before '{' token
>mutex.cpp:24: error: expected `,' or `;' before '{' token
>mutex.cpp:24: error: expected declaration before '}' token
>make[2]: *** [mutex.o] Error 1
>make[2]: Leaving directory `/src/seq24-0.6.3/src'
>make[1]: *** [all] Error 2
>make[1]: Leaving directory `/src/seq24-0.6.3/src'
>make: *** [all-recursive] Error 1
>
>  
>

Re: [seq24-users] expected primary expression during make (seq24-0.6.3)

[Esben S. <b0...@es...>]

Esben Stien <b0...@es...> writes:

> make: *** [all-recursive] Error 1

I'm also getting the exact same error with 0.6.2, 0.6.1 and 0.6.0.

I'm on linux-2.6.12-rc1-RT-V0.7.41-15 on a p3-600,
glibc-2.3.4-20040828 and gcc-3.4.2

-- 
Esben Stien is b0...@es...
         http://www.
          irc://irc.                /%23contact
          [sip|iax]:
           jid:b0ef@

[seq24-users] expected primary expression during make (seq24-0.6.3)

[Esben S. <b0...@es...>]

mutex.cpp:24: error: expected primary-expression before '.' token
mutex.cpp:24: error: expected primary-expression before '{' token
mutex.cpp:24: error: expected `}' before '{' token
mutex.cpp:24: error: expected `,' or `;' before '{' token
mutex.cpp:24: error: expected declaration before '}' token
make[2]: *** [mutex.o] Error 1
make[2]: Leaving directory `/src/seq24-0.6.3/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/src/seq24-0.6.3/src'
make: *** [all-recursive] Error 1

-- 
Esben Stien is b0...@es...
http://www.esben-stien.name
irc://irc.esben-stien.name/%23contact
[sip|iax]:esben-stien.name

[seq24-users] Re: [Alsa-devel] seq24 not in aconnect or qjackctl

[Martin H. <err...@mp...>]

On Thu, Mar 31, 2005 at 10:31:41AM +0200, Clemens Ladisch wrote:
> Martin Habets wrote:
> > Problem I'm having is that seq24 does not show up in
> > aconnect or qjackctl.
> >
> > $ cat /proc/asound/seq/clients
> > ...
> > Client 128 : "seq24" [User]
> >   Port   0 : "seq24 out" (r---)
> >   Port   1 : "seq24 in" (-w--)
> >   Port   2 : "seq24 in" (-w--)
> 
> seq24 doesn't allow connecting from other programs, you have to do it
> from inside seq24.

Thanks. So this is a 'feature', not a bug. Personally it's a 'feature'
I could do without.

-- 
Martin

[seq24-users] Re: [Alsa-devel] seq24 not in aconnect or qjackctl

[Clemens L. <cl...@la...>]

Martin Habets wrote:
> Problem I'm having is that seq24 does not show up in
> aconnect or qjackctl.
>
> $ cat /proc/asound/seq/clients
> ...
> Client 128 : "seq24" [User]
>   Port   0 : "seq24 out" (r---)
>   Port   1 : "seq24 in" (-w--)
>   Port   2 : "seq24 in" (-w--)

seq24 doesn't allow connecting from other programs, you have to do it
from inside seq24.


HTH
Clemens

[seq24-users] seq24 not in aconnect or qjackctl

[Martin H. <err...@mp...>]

Hi,

I'm using seq24 0.6.2 with ALSA 1.0.9rc1 and jack 0.99.0-4.
Problem I'm having is that seq24 does not show up in
aconnect or qjackctl. At first I had no clue if/how it was
connected. seq24 only showed up in /proc/asound/seq/clients.
Still haven't found how to disconnect/reconnect seq24.

Any idea why I'm not seeing seq24? Some output below.

Thanks,
Martin

$ cat /proc/asound/seq/clients 
Client info
  cur  clients : 4
  peak clients : 8
  max  clients : 192

Client   0 : "System" [Kernel]
  Port   0 : "Timer" (Rwe-)
  Port   1 : "Announce" (R-e-)
    Connecting To: 63:0, 128:2[t:0]
Client  62 : "Midi Through" [Kernel]
  Port   0 : "Midi Through Port-0" (RWe-)
    Connecting To: 128:1[t:0]
    Connected From: 128:0
Client  63 : "OSS sequencer" [Kernel]
  Port   0 : "Receiver" (-we-)
    Connected From: 0:1
Client 128 : "seq24" [User]
  Port   0 : "seq24 out" (r---)
    Connecting To: 62:0
  Port   1 : "seq24 in" (-w--)
    Connected From: 62:0[t:0]
  Port   2 : "seq24 in" (-w--)
    Connected From: 0:1[t:0]
  Input pool :
    Pool size          : 200
    Cells in use       : 0
    Peak cells in use  : 2
    Alloc success      : 9
    Alloc failures     : 0
$ aconnect -lo
client 62: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
        Connecting To: 128:1[real:0]
        Connected From: 128:0
$ aconnect -li
client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
        Connecting To: 63:0, 128:2[real:0]
client 62: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
        Connecting To: 128:1[real:0]
        Connected From: 128:0

[seq24-users] seq24-0.6.3

[Rob B. <rc...@fi...>]

I just released seq24-0.6.3.

It has a few small fixes including note movement and snaping.  Some
weirdness with the song editor.  And a fix for mislabeled transpose
amounts.

cheers!
rob




---------------------------------------------------
http://filter24.org                art + technology

Re: [seq24-users] Changing default velocity...

[Peter L. <pet...@gm...>]

On Fri, 18 Mar 2005 13:51:42 -0500, Erik Thorsson
<eth...@ne...> wrote:
> v0.6.2
> 
> Is there a compile time option to set the default velocity of an
> inserted note?
> 
> Or, where is the parameter in the source?
> 
> I'd like it to default to 100 instead of 127.

Erm, I'm far from being an authority on this, but I think the note-on
and note-off velocities *do* default to 100, if those are what
you're talking about - at least if you look at the bottom of the
bars in the lower half of the sequence editor window, you'll see
"100" in tiny vertical writing.

They're set at lines 1226 and 1232 in sequence.cpp, it seems

- Pete.

[seq24-users] Changing default velocity...

[Erik T. <eth...@ne...>]

v0.6.2

Is there a compile time option to set the default velocity of an 
inserted note?

Or, where is the parameter in the source?

I'd like it to default to 100 instead of 127.

-E

[seq24-users] Default velocity compile-time option?

[Jesse L. <jl...@ne...>]

v0.6.2

Is there a compile time option to set the default velocity of an 
inserted note?

Or, where is the parameter in the source?

I'd like it to default to 100 instead of 127.

-J

[seq24-users] Compiling 0.6.2 on Debian...

[Erik T. <eth...@ne...>]

Okay, I got 0.6.2 compiled on Debian Sarge (testing).

I had to...

# apt-get install libgtk2.0-0

# apt-get install libgtkmm2.0-dev

# apt-get install g++

...among other things.

I installed just the Debian base when I installed this machine.  Others 
might have those packages installed already.

Will check it out soon.

Good luck to others.

-J

Re: [seq24-users] GREAT, but....

[Hendrik W. <hwo...@pa...>]

Op ma, 14-03-2005 te 13:08 -0500, schreef Rob Buse: 

> I'll put in the key start / stop keyboard commands in.  It's just
> something that was overlooked.



> As far as muting and unmuting more than 2 tracks, that is a hardware
> problem with computer keyboards.  You will notice that if you are using
> any software (such as a text editor) and you mash down 4-5 keys, they
> will not appear.
> 
> Adding Latency would be a good idea.  I'll put that on my TODO list.
> 
> cheers
> rob
> 
> 
> >Hi,
> >
> >
> >I just replaced my roland mc-50 with seq24. What a GREAT app!
> >
> >2 minor problems:
> >It's great to control the patterns with the cumputer keyboard for live
> >performance, but do I really have to start seq24 with my mouse. Enter
> >should start the player, space for pause and 2 times space to restart
> >all loops.

Maybe 'space' shoudn't have a function, because it's too close to the
alt-button, which could be a disaster at live performance.

I have another advice: There should be a key (shift key), for activating
a lot of tracks at a given time; in other words, hold the Shift-button
while (de)selecting some tracks,  and the (de)selected acks should
(des)activate when realeasing the shift key. The Shift Lock button
should act the same way as in a text editor (pushing shift lock should
activate the shift mode permanently, and pushing it again should
desactivate the shift mode).  

Sorry about giving so many advice and so few code (Im not a progammer).
I'll definitaly buy a seq-24 T-shirt, someday! :)

Greetings


> >
> > It looks like seq24 has problems to (des)active more than 2 tracks
> >simultanously with the computer keyboard. Anyone has the same
> >experience?
> >
> >
> >P.S. It would be nice to give some latency to certain patterns. This
> >should be usefull to synchronize external devices with
> >jack-audio-connection-kit applications (and other devices that have a
> >little latency).
> >
> >Greetings Hendrik
> >
> >
> >-- 
> >Hendrik Wouters <hwouters@pandora. be>
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
> 

cheers
Hendrik
-- 
Hendrik Wouters <hwo...@pa...>

Re: [seq24-users] Compiling 0.6.2 on Debian Sarge...

[Erik T. <eth...@ne...>]

Rob Buse wrote:
> is there a seperate alsa development package in Debian?
> anyone know?

Thanks.

# apt-get install libasound2-dev

...gets me past that error.  More to come.


yew:/tmp/seq24-0.6.2# apt-cache search alsa
aconnectgui - graphical ALSA sequencer connection manager
alsa-base - ALSA driver configuration files
alsa-headers - transitional dummy package that can be safely removed
alsa-modules-2.4-386 - ALSA modules for kernel 2.4 on 386
alsa-modules-2.4-586tsc - ALSA modules for kernel 2.4 on Pentium Classic
alsa-modules-2.4-686 - ALSA modules for kernel 2.4 on 
PPro/Celeron/PII/PIII/P4
alsa-modules-2.4-686-smp - ALSA modules for kernel 2.4 on 
PPro/Celeron/PII/PIII/P4 SMP
alsa-modules-2.4-k6 - ALSA modules for kernel 2.4 on AMD K6/K6-II/K6-III
alsa-modules-2.4-k7 - ALSA modules for kernel 2.4 on AMD K7
alsa-modules-2.4-k7-smp - ALSA modules for kernel 2.4 on AMD K7 SMP
alsa-modules-2.4.27-2-386 - ALSA driver modules
alsa-modules-2.4.27-2-586tsc - ALSA driver modules
alsa-modules-2.4.27-2-686 - ALSA driver modules
alsa-modules-2.4.27-2-686-smp - ALSA driver modules
alsa-modules-2.4.27-2-k6 - ALSA driver modules
alsa-modules-2.4.27-2-k7 - ALSA driver modules
alsa-modules-2.4.27-2-k7-smp - ALSA driver modules
alsa-oss - ALSA wrapper for OSS applications
alsa-source - ALSA driver sources
alsa-utils - ALSA utilities
alsamixergui - graphical soundcard mixer for ALSA soundcard driver
alsaplayer - PCM player designed for ALSA
alsaplayer-alsa - PCM player designed for ALSA (ALSA output module)
alsaplayer-common - PCM player designed for ALSA (common files)
alsaplayer-daemon - PCM player designed for ALSA (non-interactive version)
alsaplayer-esd - PCM player designed for ALSA (ESD output module)
alsaplayer-gtk - PCM player designed for ALSA (GTK version)
alsaplayer-jack - PCM player designed for ALSA (jack output module)
alsaplayer-nas - PCM player designed for ALSA (NAS output module)
alsaplayer-oss - PCM player designed for ALSA (OSS output module)
alsaplayer-text - PCM player designed for ALSA (text version)
alsaplayer-xosd - PCM player designed for ALSA (osd version)
amarok-gstreamer - GStreamer engine for the amaroK audio player
ams - Realtime modular synthesizer for ALSA
amsynth - two oscillator software synthesizer
ardour-gtk - digital audio workstation (graphical gtk interface)
aumix - Simple text-based mixer control program
aumix-gtk - Simple mixer control program with GUI and text interfaces
awesfx - utility programs for AWE32/64 and Emu10k1 driver
balsa - An e-mail client for GNOME
ecawave - graphical audio file editor
gamix - Graphical sound mixer for ALSA
gnome-alsamixer - ALSA sound mixer for GNOME
gom - A generic audio mixer (Base versions)
gstreamer0.8-alsa - ALSA plugin for GStreamer
hydrogen - Simple drum machine/step sequencer
jack-rack - LADSPA effects "rack" for JACK
ladcca-bin - LADCCA example clients
ladcca-dev - Development files for LADCCA
ladcca2 - LADCCA shared library files
ladccad - LADCCA server
libalsaplayer-dev - PCM player designed for ALSA (interface library, 
development files)
libalsaplayer0 - PCM player designed for ALSA (interface library)
libasound2 - ALSA library
libasound2-dev - ALSA library development files
libasound2-doc - ALSA library developer documentation
libasound2-plugins - ALSA library plugins
libclalsadrv - ALSA driver C++ access library
libclalsadrv-dev - Development file for libclalsadrv
libesd-alsa0 - Enlightened Sound Daemon (ALSA) - Shared libraries
libmikmod2 - A portable sound library
libmikmod2-dev - A portable sound library - development files
libosipua2 - User agent api built on top of osip stackaudio
libosipua2-dev - User agent api built on top of osip stackaudio
libpt-plugins-alsa - Portable Windows Library Audio Plugin for the ALSA 
Interface
libsdl1.2debian-all - Simple DirectMedia Layer (with all available options)
libsdl1.2debian-alsa - Simple DirectMedia Layer (with X11 and ALSA options)
libwine-alsa - Windows Emulator (ALSA Sound Module)
liby-dev - Y Sound Server Library Header Files
liby2-14 - Y Sound Server Library
mcp-plugins - LADSPA plugins designed for Alsa Modular Synth
muse - Qt-based midi/audio sequencer
pmidi - A command line midi player for ALSA
snd-gtk-alsa - Sound file editor (GTK+ user interface)
tapiir - A tool for real time audio delay and feedback effects
timidity - Software sound renderer (MIDI sequencer, MOD player)
ttf-alee - A Lee's GPL'd Hangul truetype fonts
wmix - Dockapp mixer for OSS or ALSA
xmms - Versatile X audio player that looks like Winamp
xmp-alsa - ALSA driver for xmp
yiff-server - Y Sound Server
zinf-plugin-alsa - ALSA plugin for ZINF
alsa-headers-0.4 - ALSA driver header files Version 0.4
alsa-headers-0.5 - ALSA driver header files (0.5)
alsa-modules-2.4.16-386 - Advanced Linux Sound Architecture (drivers)
alsa-modules-2.4.16-586 - Advanced Linux Sound Architecture (drivers)
alsa-modules-2.4.16-586tsc - Advanced Linux Sound Architecture (drivers)
alsa-modules-2.4.16-686 - Advanced Linux Sound Architecture (drivers)
alsa-modules-2.4.16-686-smp - Advanced Linux Sound Architecture (drivers)
alsa-modules-2.4.16-k6 - Advanced Linux Sound Architecture (drivers)
alsa-modules-2.4.16-k7 - Advanced Linux Sound Architecture (drivers)
alsa-source-0.4 - ALSA driver source Version 0.4
alsa-source-0.5 - ALSA driver source (0.5)
alsa-utils-0.4 - Advanced Linux Sound Architecture (utils)
alsa-utils-0.5 - Advanced Linux Sound Architecture (utils)
alsaconf - ALSA configurator
libarts-alsa - aRts Sound system (built with alsa support)
libasound0.4 - Advanced Linux Sound Architecture (old libraries)
libasound0.4-dev - Advanced Linux Sound Architecture (old development)
libasound1 - Advanced Linux Sound Architecture (libraries)
libasound1-dev - Advanced Linux Sound Architecture (development)
libfreeamp-alsa - ALSA plugin for FreeAmp
libkmid-alsa - aRts Sound system (midi/kmedia support libraries with alsa)
liby2 - Y Sound Server Library
pmidi-0.9 - A command line midi player for ALSA 0.9 series
vkeybd - Virtual Keyboard program
vlc-alsa - ALSA plugin for vlc
xamixer-0.4 - Graphical mixer for ALSA
sl-modem-daemon - SmartLink software modem daemon
yew:/tmp/seq24-0.6.2#

Re: [seq24-users] Compiling 0.6.2 on Debian Sarge...

[Rob B. <rc...@fi...>]

is there a seperate alsa development package in Debian?
anyone know?

cheers
rob

>I unpack the source, I run ./configure and I get...
>
>...
>checking for ALSA CFLAGS...
>checking for ALSA LDFLAGS...  -lasound -lm -ldl -lpthread
>checking for libasound headers version >=3D 0.9.0... not present.
>configure: error: Sufficiently new version of libasound not found.
>yew:/tmp/seq24-0.6.2#
>
>...but...
>
>yew:/tmp/seq24-0.6.2# dpkg -l | grep libasound
>ii  libasound2     1.0.8-3        ALSA library
>
>...and...
>
>yew:/tmp/seq24-0.6.2# dpkg -l | grep alsa
>ii  alsa-base      1.0.8-7        ALSA driver configuration files
>ii  alsa-utils     1.0.8-4        ALSA utilities
>
>Any advice would be appreciated.
>
>-Erik
>
>
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
>_______________________________________________
>seq24-users mailing list
>seq...@li...
>https://lists.sourceforge.net/lists/listinfo/seq24-users

---------------------------------------------------
http://filter24.org                art + technology

[seq24-users] Compiling 0.6.2 on Debian Sarge...

[Erik T. <eth...@ne...>]

I unpack the source, I run ./configure and I get...

...
checking for ALSA CFLAGS...
checking for ALSA LDFLAGS...  -lasound -lm -ldl -lpthread
checking for libasound headers version >= 0.9.0... not present.
configure: error: Sufficiently new version of libasound not found.
yew:/tmp/seq24-0.6.2#

...but...

yew:/tmp/seq24-0.6.2# dpkg -l | grep libasound
ii  libasound2     1.0.8-3        ALSA library

...and...

yew:/tmp/seq24-0.6.2# dpkg -l | grep alsa
ii  alsa-base      1.0.8-7        ALSA driver configuration files
ii  alsa-utils     1.0.8-4        ALSA utilities

Any advice would be appreciated.

-Erik

[seq24-users] Program Change

[Stephen C. <chu...@gm...>]

Hi everyone,

First let me say that seq24 is absolutely brilliant!   My old laptop
has been transformed into a nice little hardware MIDI sequencer.  This
is what I've wanted from sequencing for a long time - thanks Rob!

Anyway, one feature I would find very useful would be to have the
option to prevent program change messages from cycling within a loop.
For example, I'll play back a bass loop, tweak it in real-time, and
then the program change message is sent again when the loop repeats
and the patch is set to its saved state.  Is there a way around this?
Is it possible to send program change data to a channel before the
loop starts?

Regards,

Stephen

ps: I know this is not the place for this, but I would love to hear
some of the music everyone has been making with this amazing little
app.  Ciao

[seq24-users] some questions, thoughts, and a tiny patch

[Peter L. <pet...@gm...>]

A midi novice, I blundered into seq24 looking for a way to sync
alsa modular with hydrogen, and having tried this with muse and
rosegarden, I was relieved and impressed to find a light
and easy to use solution existed - thanks very much!

Inevitably, there's a couple of things I'm unclear about, and
some suggestions..

For one, I couldn't get the "loop playback" in the song editor
working. I right-clicked to set the right edge, left-clicked for
the left, and pressed the L-R loop button, then play, (in song mode,
of course..) but the cursor just sailed on past my right marker...?

The transpose menu in the sequence editor seemed to move
notes one less semitone than the advertised number, and
wouldn't transpose by an octave (though perhaps that's
easier done somewhere else).

I had a look at the code on this one, and I found that the following
made things work as I expected:

*** seqedit.cpp.orig    Wed Mar 16 02:15:25 2005
--- seqedit.cpp Wed Mar 16 02:17:08 2005
***************
*** 476,485 ****
      char num[6];
   
      holder2 = manage( new Menu());
!     for ( int i=-11; i<=11; ++i ){
   
          if ( i!=0 ){
!             sprintf( num, "%+d [%s]", (i<0) ? i-1 : i+1,
c_interval_text[ abs(i) ]  );
              holder2->items().push_front( MenuElem( num,
bind(slot(*this,&seqedit::do_action), transpose, i )));
          }
      }
--- 476,485 ----
      char num[6];
   
      holder2 = manage( new Menu());
!     for ( int i=-12; i<=12; ++i ){
   
          if ( i!=0 ){
!             sprintf( num, "%+d [%s]", i, c_interval_text[ abs(i) ]  );
              holder2->items().push_front( MenuElem( num,
bind(slot(*this,&seqedit::do_action), transpose, i )));
          }
      }

(just changing the for loop to run from -12 to 12, and printing 
i straight, rather than modified, so that a 1 semitone change appears
in the menu as a minor second, and a 12 semitone octave change 
as a "perfect 8th", which seems more correct .. :)

Also, I couldn't understand what "background sequence" would do ..?

If that's not already too much, here's my suggestions (ie feature
requests..:)

1) I'd like to be able to select multiple boxes in the performance
editor window, and do copy/move/delete (cut and paste) operations
on them, much as can be done for notes in the piano roll editor. Maybe
this could be done with the existing facilities, but having them only
apply to rows selected by clicking on them in the names column - at
least I found myself repeatedly trying to click on the names in the
expectation they would do ... something.

2) maybe a good way to approach the problem of doing multiple simultaneous
stop/start events in performance mode would be to allow multiple
selections in the main window - either ctrl-click for a mouse or navigate
the loop boxes via cursor keys and use a key combo to toggle the
selectedness of the current loop, showing selectedness by drawing
a border on the selected loops, maybe, then either use a key (space,
escape, return..?) or click a button (or maybe a menu) to
stop / start (or, hey! transpose all the notes at once... :)

Anyway, just some thoughts from a happy and grateful user, I hope
the project will flourish and grow - but not TOO much..! 

- Pete

[seq24-users] Crash on import...

[Erik T. <eth...@ne...>]

Hello, all.  New to seq24 here.

I'm not sure how seq24 is expected to behave when handed a MIDI file to 
import.  What kind of MIDI file does it want?  Yes, type 1, but are 
there length restrictions?  How does it split out data from multiple 
channels?

It's barfing when I try to import this MIDI (which is about two minutes 
long and has four or five channels): 
http://www.neoprimitive.net/jlucas/tmp/chernobyl.mid

ethorsson@yew:~$ seq24 &
[1] 10805
...
<I go to File | Open | select the file>
...
ethorsson@yew:~$
[1]+  Floating point exceptionseq24
ethorsson@yew:~$

This is with the Debian Sarge package of seq24 v0.5.3.

-E