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

Re: [seq24-users] Seq24-0.6.0-rc1 (compile errors (fixed!))

[po <po...@em...>]

On Wednesday 05 January 2005 16:17, rob buse wrote:

> I'm pretty sure that gtkmm-2.4 is a different beast than gtkmm-2.0
> and gtkmm-2.2.

Looks like you're right... not sure why I didn't grasp that when I was 
picking a version to download. I think I just couldn't find 2.0, so I 
went for the most recent stable release... so much for non-developers 
installing dev tools... hopefully someone can learn from my folly and 
save some trouble. :) Thanks for the tip.

> What distro are you using?  Gtkmm is set up in such a 
> way you can have 1.2, 2.0, and 2.4 installed in parallel.  You should
> be able to find 2.2 without any problems on any distro.

Using Slack 10.0 with kernel and some of the other packages from 
audioslack.com, but I like to build whatever I can myself, if only for 
the learning experience. The 2.2 source from gtkmm.org worked fine, and 
everything seems to be up and running now, so I'll go play with seq24 
and see if I can break something... ;)

Thanks again,

-- 

 yawfle

Re: [seq24-users] Seq24-0.6.0-rc1 (compile errors)

[rob b. <rc...@fi...>]

yawfle-

I'm pretty sure that gtkmm-2.4 is a different beast than gtkmm-2.0 and
gtkmm-2.2.  What distro are you using?  Gtkmm is set up in such a way you
can have 1.2, 2.0, and 2.4 installed in parallel.  You should be able to
find 2.2 without any problems on any distro.

cheers!
rob

> On Tuesday 04 January 2005 03:19, rob buse wrote:
>
>> hey everyone!
>>
>> Seq24-0.6.0-rc1
>
> Can't wait to try it, but running 'make' fails with these errors:
>
> ----------------
> seqdata.cpp: In member function `virtual void seqdata::on_realize()':
seqdata.cpp:105: error: use of class template `template<class T_return,
class
>    T_arg1, class T_arg2, class T_arg3, class T_arg4, class T_arg5, class
T_arg6, class T_arg7> class sigc::slot' as expression
> seqdata.cpp: In member function `void
> seqdata::on_size_allocate(GtkAllocation*)
>    ':
> seqdata.cpp:504: error: no matching function for call to `seqdata::
>    on_size_allocate(GtkAllocation*&)'
> /usr/include/gtkmm-2.4/gtkmm/widget.h:341: error: candidates are:
virtual void
>    Gtk::Widget::on_size_allocate(Gtk::Allocation&)
> ----------------
>
> Is it compiling ok for anyone else? Possible sources of problems on my
end might be that I have gtkmm 2.4 instead of 2.0 installed, and had to
edit the configure script accordingly (also tried symlinking
> gtkmm-2.4.pc > gtkmm-2.0.pc - either way configure is happy, but compile
fails, perhaps because of version compatibility issues?) I can't seem to
find gtkmm 2.0 at the home site - am I missing something? I'm looking
forward to using seq24, and appreciate any and all help, since I'm not
really all that good at this stuff. :)
>
> --
> yawfle
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's
fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>


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



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

Re: [seq24-users] Seq24-0.6.0-rc1 (compile errors)

[yawfle <se...@ya...>]

On Tuesday 04 January 2005 03:19, rob buse wrote:

> hey everyone!
>
> Seq24-0.6.0-rc1

Can't wait to try it, but running 'make' fails with these errors:

----------------
seqdata.cpp: In member function `virtual void seqdata::on_realize()':
seqdata.cpp:105: error: use of class template `template<class T_return, 
class
   T_arg1, class T_arg2, class T_arg3, class T_arg4, class T_arg5, class
   T_arg6, class T_arg7> class sigc::slot' as expression
seqdata.cpp: In member function `void 
seqdata::on_size_allocate(GtkAllocation*)
   ':
seqdata.cpp:504: error: no matching function for call to `seqdata::
   on_size_allocate(GtkAllocation*&)'
/usr/include/gtkmm-2.4/gtkmm/widget.h:341: error: candidates are: 
virtual void
   Gtk::Widget::on_size_allocate(Gtk::Allocation&)
----------------

Is it compiling ok for anyone else? Possible sources of problems on my 
end might be that I have gtkmm 2.4 instead of 2.0 installed, and had to 
edit the configure script accordingly (also tried symlinking 
gtkmm-2.4.pc > gtkmm-2.0.pc - either way configure is happy, but 
compile fails, perhaps because of version compatibility issues?) I 
can't seem to find gtkmm 2.0 at the home site - am I missing something? 
I'm looking forward to using seq24, and appreciate any and all help, 
since I'm not really all that good at this stuff. :)

-- 
yawfle

[seq24-users] Seq24-0.6.0-rc3 + a request

[rob b. <rc...@fi...>]

alright..  rc3 is now out.  Window scrolling is much faster in the editor.

If anyone is using the new 0.6.0 and finds a bug, or you have any
problems, please let me know.  Please don't assume that anyone is going to
report them.  The user base is quite small, and I want to get to 0.6.0
with as little problems as possible.  So if you find a problem, shoot me
an email.

oh yea, I would like to know if people out there are using the new JACK
transport stuff with good results.

thanks!
rob




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

[seq24-users] Seq24-0.6.0-rc2

[rob b. <rc...@fi...>]

hey all..   fixed a few issues with that last release, most notably some
really slow drawing on the editor.

http://www.filter24.org/seq24/

cheers
rob.


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

[seq24-users] Seq24-0.6.0-rc1

[rob b. <rc...@fi...>]

hey everyone!

Seq24-0.6.0-rc1

New release with some major changes.
Reworked drawing code for sequence editor.
Now requires gtkmm-2.
Optional JACK Transport support.
Reworked note movement in sequence editor.
More standard file dialogs w/ filename tracking.
Added .seq24rc file for saving options and changing key mappings.


http://www.filter24.org/seq24/


cheers!!
rob :)

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

[seq24-users] bug report

[rezk <re...@ne...>]

Hi,Seq24 crashes while loading midi files that have empty tracks.
Simple checking for time while merging the track fixed the problem for me:
midifile.cpp,line 388
if (CurrentTime>0) {
      a_perf->add_sequence( seq, perf + (a_screen_set * c_seqs_in_set)  );
  }

Also, loading a file whith just one 16th note and program change event, crashed SEQ24 while trying
to open a pianoroll. It crashed at:
sequence.cpp ,line 1842
sequence::get_last_tick( )
{
    return m_last_tick % m_length;
}
because of arithmetic error (m_length=3d0)

Bye.

-- 
Easy pristup internetu bez prijave i dostupan odmah.
Saznajte vi=b9e na adresi http://www.iskon.hr/easy/

[seq24-users] gtkmm2

[Eric F. <the...@sb...>]

are there plans to support gtkmm2 in the future?

Re: [seq24-users] roadmap

[rob b. <rc...@fi...>]

>> Probably 3-4 months until 0.6.0.
> Uh, that's pretty far away. Can I send you patches if I make some? ;)

Well, I don't accept outside patches for seq24. And since jack transport
is going to require changing core components, its just something I would
much rather do.

cheers
rob



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

Re: [seq24-users] roadmap

[rob b. <rc...@fi...>]

>> The next major release of seq24 will give us the ability to be a jack
>> transport client.  I'm working on doing this now, but it might not be
>> done
>> for a little while.
> Great news! One question left - when? :)
> And an idea to make seq24 only jack-transport client (and left
> timebase master job for another program) is a good solution.

Probably 3-4 months until 0.6.0.




>> I don't have any plans to change the midi port handling.  As it is,
>> seq24
>> connects to all input ports and I really don't think that people want to
>> do this manually.  It's much nicer for users just to start up a
>> softsynth
>> and have it pop up on the available port menu.  I suppose lash support
>> could be added, but if you start up your softsynths in the same order,
>> and
>> load your seq24 file, it restores all the connections just as they
>> should
>> be.  If any of those softsynths die, and you restart them, they will
>> reconnect to seq24.
> But if you want to connect your patterns of one type (bass synth, for
> example) to another alsa client you should connect EACH pattern. And
> if we introduce one indirection level to midi outs we can just
> reconnect this very output, instead of each pattern, which in turn
> would be connected to appropriate virtual out (with an appropriate
> name, I suppose).

Yea, I guess it can be a pain to change a set of patterns to a new output.
 Perhaps I should set it up such that the output can be changed from the
popup menu on the main screen.  Then we don't have to open the edit window
for each change.  If we set it up such a way that you can just remap the
alsa port, your still going to have a problem if you want to change the
midi channel quickly.


> I mean ability to draw curve with a mouse, adding new CC events, using
> quantization period. Current event editor is not very comfortable (for
> me).

The way I'm planning on doing it is with a menu item, where you can select
to fill the current control code over the sequence and then you can just
adjust them with the mouse.  There will also be a menu item to thin out
recoreded control codes..   where is will remeove every other one or
sometime similar.


cheers
rob




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

Re: [seq24-users] roadmap

[rob b. <rc...@fi...>]

greetings!

The next major release of seq24 will give us the ability to be a jack
transport client.  I'm working on doing this now, but it might not be done
for a little while.

I don't have any plans to change the midi port handling.  As it is, seq24
connects to all input ports and I really don't think that people want to
do this manually.  It's much nicer for users just to start up a softsynth
and have it pop up on the available port menu.  I suppose lash support
could be added, but if you start up your softsynths in the same order, and
load your seq24 file, it restores all the connections just as they should
be.  If any of those softsynths die, and you restart them, they will
reconnect to seq24.
I really don't want to add another dependency to seq24 like lash.

I plan on adding a quantization function along with a host of other
functions like transpose, shift, fill random, fill LFO..   things like
that.

> I think
> some controller views need the ability to edit shape of overall curve
> in addition to single events.

I'm not really sure what you mean about CC event handling.  You have the
ability to edit the overall shape of the curve by drawing with the mouse,
and you have the ability to edit single events by selecting them and using
the mouse scroll wheel.  Perhaps I am missing what you mean?

cheers!
rob



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

[seq24-users] roadmap

[Dmitry B. <dsb...@gm...>]

Hello!
I'm planning to add some features to seq24.
And think it will be useful for all to discuss them :)

The main thing most of us are missing from seq24 is optional
jack-transport interaction. At least seq24 should start/stop
jack-transport. Providing timebase master is a complex matter, as
seq24 does not have "master track" which may provide tempo/meter
events. So, it needs some research here.

Another issue is midi port handling. Personally, I plan to redesign it
in the following way: you create any number of alsa output ports in
seq24 and direct your patterns to them, instead of external ports.
Now, to get some sound you just need to connect seq24's outputs to any
alsa midi inputs with some external tool (or seq24 itself). The main
benefits are more clean notion of outputs and possibility to add
lash/ladcca support.

And the last but not least is CC event handling. It would be useful to
add quantization on record. Another issue is CC event editor. I think
some controller views need the ability to edit shape of overall curve
in addition to single events.

Waiting for your comments.
--Dmitry

P.S. Rob, thank you for the great sequencer!

[seq24-users] seq24 0.5.3

[rob b. <rc...@fi...>]

Hey everyone-

seq24 0.5.3 is up for download.

Fixes:
 Fixed performance looping effecting live play mode.
Patterns can no longer be deleted or moved while they are being edited, no
longer seqfaults.
Save file now stores BPM
Added menu item to clear performance data.

cheers!
rob


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

Re: [seq24-users] Re: seq24-users digest, Vol 1 #9 - 1 msg

[Ethan <tel...@75...>]

> if you use debian, you might as well apt-get it  ;)
> if it isn't in your apt tree download the package manually from
> http://packages.debian.org/cgi-bin/search_packages.pl?keywords=seq24&searchon=names&subword=1&version=unstable&release=all
> because it's only in unstable...
> don't forget the dependencies!
> --K

Hah! I figured that out after I posted the message, I thought "Let me just
see if.... wow!" ... So now I'm recompiling kernel and wasting away hours
working to get Alsa + Sound stuff working, need to setup the modules to
work with my laptop! Will report results.

Seems like a pretty sweet program!

				-- Ethan

[seq24-users] Re: seq24-users digest, Vol 1 #9 - 1 msg

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

if you use debian, you might as well apt-get it  ;)

if it isn't in your apt tree download the package manually from

http://packages.debian.org/cgi-bin/search_packages.pl?keywords=seq24&searchon=names&subword=1&version=unstable&release=all

because it's only in unstable...

don't forget the dependencies!


--K

On Tue, 14 Sep 2004 20:57:18 -0700,
seq...@li...
<seq...@li...> wrote:
> Send seq24-users mailing list submissions to
>         seq...@li...
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/seq24-users
> or, via email, send a message with subject or body 'help' to
>         seq...@li...
> 
> You can reach the person managing the list at
>         seq...@li...
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of seq24-users digest..."
> 
> Today's Topics:
> 
>    1. compilation problems? (Ethan)
> 
> --__--__--
> 
> Message: 1
> Date: Tue, 14 Sep 2004 23:34:52 -0400 (EDT)
> From: Ethan <tel...@75...>
> To: seq...@li....
> Subject: [seq24-users] compilation problems?
> 
> Hello everyone, I'm in love with Seq24 and haven't even gotten it to
> compile yet. Looking to use it Saturday to run a laser projector
> (solenoids driven by midi noteon/off commands). Figure I will test it on
> some of my midi modules as well :-)
> 
> Anyways, I think I satisfied the prereqs, although I ended up with gcc +
> gcc2.95 and gcc 3.0. I'm using Debian 2.4.20 on a fairly slow notebook
> that has a GAME/midi uart.
> 
> Upon compilation I get this:
> 
> make[2]: Entering directory `/root/seq24-0.5.2/src'
> source='options.cpp' object='options.o' libtool=no \
> depfile='.deps/options.Po' tmpdepfile='.deps/options.TPo' \
> depmode=gcc /bin/sh ../depcomp \
> g++ -DHAVE_CONFIG_H -I. -I. -I.     -g -O2 -I/usr/lib/gtkmm/include
> -I/usr/inclu
> de/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include
> -I/usr/X11R6/include
> -I/usr/lib/sigc++-1.0/include -I/usr/include/sigc++-1.0 -Wall -c -o
> options.o `t
> est -f 'options.cpp' || echo './'`options.cpp
> options.cpp: In method `class string options::uc_2_hex_string(unsigned
> char)':
> options.cpp:277: `right' undeclared (first use this function)
> options.cpp:277: (Each undeclared identifier is reported only once
> options.cpp:277: for each function it appears in.)
> options.cpp:281: `uppercase' undeclared (first use this function)
> make[2]: *** [options.o] Error 1
> make[2]: Leaving directory `/root/seq24-0.5.2/src'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/root/seq24-0.5.2/src'
> make: *** [all-recursive] Error 1
> ninja:~/seq24-0.5.2#
> 
> I am going to see if I can get GTKmm-1.2.9 or better, that seems to be the
> one unknown.
> 
> Any suggestions?
> 
> --
>                                // Ethan O'Toole
>                                // http://users.757.org/~ethan
> 
> --__--__--
> 
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
> 
> End of seq24-users Digest
>

[seq24-users] compilation problems?

[Ethan <tel...@75...>]

Hello everyone, I'm in love with Seq24 and haven't even gotten it to
compile yet. Looking to use it Saturday to run a laser projector
(solenoids driven by midi noteon/off commands). Figure I will test it on
some of my midi modules as well :-)

Anyways, I think I satisfied the prereqs, although I ended up with gcc +
gcc2.95 and gcc 3.0. I'm using Debian 2.4.20 on a fairly slow notebook
that has a GAME/midi uart.

Upon compilation I get this:

make[2]: Entering directory `/root/seq24-0.5.2/src'
source='options.cpp' object='options.o' libtool=no \
depfile='.deps/options.Po' tmpdepfile='.deps/options.TPo' \
depmode=gcc /bin/sh ../depcomp \
g++ -DHAVE_CONFIG_H -I. -I. -I.     -g -O2 -I/usr/lib/gtkmm/include
-I/usr/inclu
de/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include
-I/usr/X11R6/include
-I/usr/lib/sigc++-1.0/include -I/usr/include/sigc++-1.0 -Wall -c -o
options.o `t
est -f 'options.cpp' || echo './'`options.cpp
options.cpp: In method `class string options::uc_2_hex_string(unsigned
char)':
options.cpp:277: `right' undeclared (first use this function)
options.cpp:277: (Each undeclared identifier is reported only once
options.cpp:277: for each function it appears in.)
options.cpp:281: `uppercase' undeclared (first use this function)
make[2]: *** [options.o] Error 1
make[2]: Leaving directory `/root/seq24-0.5.2/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/seq24-0.5.2/src'
make: *** [all-recursive] Error 1
ninja:~/seq24-0.5.2#

I am going to see if I can get GTKmm-1.2.9 or better, that seems to be the
one unknown.

Any suggestions?

--
                               // Ethan O'Toole
                               // http://users.757.org/~ethan

Re: [seq24-users] max pattern length...

[Florian S. <mis...@gm...>]

On Fri, 10 Sep 2004 01:05:31 +0200
Florian Schmidt <mis...@gm...> wrote:

> 6] would it be difficult to make the loop range in the song editor be
> snappable to something different than 4 4/4 measures?

one 4 too many

flo

[seq24-users] max pattern length...

[Florian S. <mis...@gm...>]

Hi,

i some questions:

1] is it possible to have 8 measures of 7/8 in a pattern? I mean right
now it's possible to use a pattern of length 7/1 which is the same
period as 8 measures of 7/8, but the measure bars are at the wrong
spots..

2] is the maximum limit of the pattern length arbitrarily chosen? Or are
there technical reasons against making patterns as long as the computers
memory permits..

3] can seq24 use mlockall() to lock it's memory into physical ram? I
read about the --priority switch. Does it switch to the SCHED_FIFO
scheduling class?

4] How probable is support for jack_transport?

5] In what spots of the code would i have to look to add a list of
recently used files to the file menu and make the file selector remember
the last used path? And also a Save As.. and Save menu entry with the
known semantics would be nice, right?

6] would it be difficult to make the loop range in the song editor be
snappable to something different than 4 4/4 measures?

TIA

flo

[seq24-users] Jack transport

[<axe...@we...>]

Hi, i tried seq24 on the AGNULA DeMuDi Distro. It really is a cool piece of software but i was wondering why jack transport is not implemented? are you planning to include this feature in one of the next releases?  that could make seq24 the sequencer of my choice ...

Regards, axel
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193

[seq24-users] Re: seq24 0.5.1

[Peter N. <pn...@ya...>]

Hi,

I also noticed there's a slight lag that definitely
happens at the end or beginning of each 4-beat
measure.  Compared it to rosegarden which also doesn't
seem to have super-tight timing, but in rosegarden
there wasn't a noticeable pattern to it like there is
in seq24.  this was using the 'demudi' music
distribution which comes with low-latency kernel and
seq-24 0.5.0.  tried to compile the newer version but
it wanted a newer version of libasound which I
couldn't manage to get.  Also on that system, seq-24
would exit with a Floating Point exception/error
trying to load any MIDI file, including ones saved out
of seq-24.  I'll try the new version with Red Hat when
I get a chance.  

I like the interface a lot.  I'd love to be able to
group multiple sequences together and activate them
all together with 1 button.  Maybe there could be a
special kind of sequence that could have seq-24 itself
as its MIDI target (for starting/stopping other
sequences), I suppose you'd have to check for feedback
loops but then you could do all kinds of crazy things
without changing too much.  Also it would be nice if
the Performance editor could record what you do on the
sequence screen (or maybe it can do these things
already and I just couldn't figure that out).  nice
job --Peter

[seq24-users] seq24-0.5.2

[rob b. <rc...@fi...>]

hey everyone!

There is a new version of seq24 up.  http://filter24.org/seq24

It takes care of hanging notes found in 0.5.1.
I'm not really sure how I missed that bug. :)

cheers!
rob



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

Re: [seq24-users] seq24 0.5.1

[rob b. <rc...@fi...>]

What sort of kernel are you running?  does it have the low latency patches?
could you run ./seq24 --stats and give me the output.

thanks
rob

>
>Cool, gonna try it.. BTW: i had a problem with seq24 0.5.0: When using a rapid stream of notes [64th or 32th at high tempo] i can hear a periodic timing issue. it seems that two notes of each 4 bar measure fall on the same spot.. 
>
>i attached a seq24 file which might be useful to test it. just use any synthesizer [preferably one that schedules midi events correctly as to avoid jitter] and playback the simple sequence...
>
>thanks..
>

Re: [seq24-users] seq24 0.5.1

[Florian S. <mis...@gm...>]

On Sun, 11 Jul 2004 11:48:46 -0400
rob buse <rc...@fi...> wrote:

> 
> I finally finished up 0.5.1
> 
> Changes:
> 
> Added a button in the editor for separate note length.
> Mouse wheel can now step values in editor.
> A few more bug fixes.
> 
> http://www.filter24.org/seq24/

Cool, gonna try it.. BTW: i had a problem with seq24 0.5.0: When using a rapid stream of notes [64th or 32th at high tempo] i can hear a periodic timing issue. it seems that two notes of each 4 bar measure fall on the same spot.. 

i attached a seq24 file which might be useful to test it. just use any synthesizer [preferably one that schedules midi events correctly as to avoid jitter] and playback the simple sequence...

thanks..



-- 
Palimm Palimm!
http://affenbande.org/~tapas/wiki

[seq24-users] seq24 0.5.1

[rob b. <rc...@fi...>]

I finally finished up 0.5.1

Changes:

Added a button in the editor for separate note length.
Mouse wheel can now step values in editor.
A few more bug fixes.

http://www.filter24.org/seq24/

cheers!
rob


-- 
------------------------------------------------------------
  music + technology :                    www.filter24.org

[seq24-users] seq24 0.5.0

[rob b. <rc...@fi...>]

seq24 v 0.5.0 has been released.
check out http://www.filter24.org/seq24

-- 
------------------------------------------------------------
  music + technology :                    www.filter24.org