seq24-devel — seq24 developers

[Seq24-devel] Testing Kepler34 - New Qt GUI for seq24

[oli_kester <oli...@zo...>]

Hi Guys

The Kepler34 project aims to provide a modern interface for the seq24 MIDI sequencer, with extra features added in support of creativity.

After a bit of a false start with the project using GTK2, I decided to build my own Qt GUI using the seq24 MIDI internals as a starting point. Thanks to Jeremy for inspiring this idea!

I've now got the project to a decent point, and would appreciate some feedback. Here are a few screenshots - 

http://imgur.com/a/wN2AA

As you can see, the program now uses a single window interface. It's also fully resizable. In the future, it will be possible to pop out each of those tabs to a separate window - they are implemented as separate Qt frame objects, making this easy to achieve.

Some feedback on the use of colour would be great - is the playback state of each sequence clear enough with the current setup?

Please note that quite a few of the buttons do not yet work, and the MIDI event editor has yet to be ported over - but the program works as a basic MIDI sequencer. 

It should be 100% compatible with seq24 MIDI files - but just to be safe, please back up before opening up any of your projects. Upon save, data about the sequence colouring is now tagged to the MIDI files after the usual seq24 values.

You can download a stable(?) package from here - 

https://github.com/oli-kester/kepler34/releases/tag/v0.1

Cheers!

Oliver

Re: [Seq24-devel] Kepler34 (seq24) testing

[Luke D. <luk...@gm...>]

Hi Oliver,

Sorry I've been a bit quiet. settling into new job and getting my home set
up back up and running.

Currenty got my mac back and functioning and so going to do some testing on
that.

about to upgrade my box to be a server and run a linux (kxstudio) in a VM
on the server so I will do some testing on that.
(Hopefully it won't take me to long to get things set up and I test out
your seq24 stuff soon)

- Luke

On Wed, Mar 2, 2016 at 5:04 AM, oli_kester <oli...@zo...> wrote:

> Hey all,
>
> So after lots of learning (and a bit of development!) I've now implemented
> a few of the first features for Kepler34, my project based on seq24.
>
> If you'd like to test, please download the master branch from here -
>
> https://github.com/oli-kester/kepler34
>
> The most significant new feature is an overhaul of how the song/live modes
> work. There is now no user preference between the two - the functionality
> is still there, but is now split contextually across the two play buttons -
>
> 1) Live mode - Triggered by clicking the green play button in the main
> window. This behaves just like the live mode in seq24; you can manually
> trigger loops as you wish.
>
> 2) Song mode - Triggered by clicking the blue play button in the song
> editor. This causes the program to play the song editor's data (as with the
> old song mode), but sequences can still be toggled in the main window to
> allow for live improvised changes.
>
> I have created a new blue play icon for the song editor to reflect these
> differences in functionality.
>
> There is now also a record button in the song editor - when this is
> enabled, any changes to sequence playback in the main window are drawn into
> the song editor. This allows you to set out a whole track just by recording
> live sequence triggers.
>
> I have also moved the config file into the .config folder, changed the
> default value for manual alsa ports, and added a recent files list.
>
> Hope this makes sense. If anything doesn't, just ask for clarification.
> Feedback on the features and implementation would be massively appreciated!
>
> Next I'll be working a single window mode into the GUI, and darkening the
> overall look and feel. There is a rough plan of the project features here -
>
> https://github.com/oli-kester/kepler34/wiki/Roadmap
>
> Thanks for your support!
>
> Best,
>
> Oliver
>
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Seq24-devel mailing list
> Seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-devel
>

[Seq24-devel] Kepler34 (seq24) testing

[oli_kester <oli...@zo...>]

Hey all,

So after lots of learning (and a bit of development!) I've now implemented a few of the first features for Kepler34, my project based on seq24. 

If you'd like to test, please download the master branch from here - 

https://github.com/oli-kester/kepler34

The most significant new feature is an overhaul of how the song/live modes work. There is now no user preference between the two - the functionality is still there, but is now split contextually across the two play buttons - 

1) Live mode - Triggered by clicking the green play button in the main window. This behaves just like the live mode in seq24; you can manually trigger loops as you wish.

2) Song mode - Triggered by clicking the blue play button in the song editor. This causes the program to play the song editor's data (as with the old song mode), but sequences can still be toggled in the main window to allow for live improvised changes.

I have created a new blue play icon for the song editor to reflect these differences in functionality. 

There is now also a record button in the song editor - when this is enabled, any changes to sequence playback in the main window are drawn into the song editor. This allows you to set out a whole track just by recording live sequence triggers.

I have also moved the config file into the .config folder, changed the default value for manual alsa ports, and added a recent files list.

Hope this makes sense. If anything doesn't, just ask for clarification. Feedback on the features and implementation would be massively appreciated!

Next I'll be working a single window mode into the GUI, and darkening the overall look and feel. There is a rough plan of the project features here - 

https://github.com/oli-kester/kepler34/wiki/Roadmap

Thanks for your support!

Best, 

Oliver

[Seq24-devel] seq24 0.9.3 released

[Guido S. <gui...@gm...>]

Dear all,

seq24 is a pattern based sequencer with strong live performance capabilities.

A new seq24 release is out published by the Seq24team.

  https://edge.launchpad.net/seq24/

This release fixes a few bugs and provides some minor
feature improvements.
All users should upgrade to 0.9.3.

Please find source tarballs on the release page:

  https://edge.launchpad.net/seq24/trunk/0.9.3


NEWS
====
seq24-0.9.3 (2016-01-24)

Fixed Bugs
  * Fix LASH support (crash on 64 Bit systems)
  * Fix broken JACK transport with newer jackd version
  * Fix clock tick drift
  * Fix jack session commandline (obsolete --file option removed)

New Features
  * Non recursive make

General Changes
  * Some code cleanups
  * C++11 compatible compiler required



Cheers
Guido


-- 
http://wie-im-flug.net/
http://www.lug-burghausen.org/

Re: [Seq24-devel] Advice wanted - a project to upgrade seq24

[<ro...@fr...>]

Hello Oliver,

Sorry for the confusion, I meant to write a windows PC ...

But don't worry about me, I was giving this feedback for statistics.
If your project becomes the perfect App I need, and it only works on
Linux, then I will setup a Linux boot partition just for it ! :)

On a side note, I am starting to look into a setup with an iPad, and
there are some apps that start to be really usable for a live set.
Promidi is one of the apps that has most of the features I need (very
similar to Seq24).
You should check it out ... (any chance to port seq24 to iPad ? :))

Cheers,
Xavier.


----- Original message -----
From: "oli_kester" <oli...@zo...>
To: ro...@fr...
Cc: seq...@li...
Subject: Re: [Seq24-devel] Advice wanted - a project to upgrade seq24
Date: Sat, 19 Dec 2015 17:31:10 +0000

Thanks Xavier, I've downloaded that and will give it a test :)

The pattern / song mode switching is something I want to add - having to
dive into the prefs all the time gets old quick! And at the moment you
have to pause all playback too.

There is already MIDI pattern control I believe, but you have to set it
all up in a text file (I'm yet to use it). I want to make this more
accessible with MIDI learn.

By PC, do you mean you run Seq24 on Windows? I've been wondering if
dropping Windows support (at least for the duration I'm working on this)
might be necessary to avoid fighting compatibility issues with my new
features. However, if lots of people run it on Windows then I'll have to
seriously consider keeping support!

Thanks

Oliver

---- On Thu, 10 Dec 2015 11:48:07 +0000 <ro...@fr...> wrote ---- 
 > Hello Oliver,
 > 
 > Nice project ! :)
 > 
 > If it can be of any help, when searching for advanced features
 > developped on top of seq24, I came upon this :
 > http://www.subatomicglue.com/seq24/
 > I suggest you at least install it and run it, it also gives other ideas
 > of improvements.
 > Some of the features that you want to implement may even have been
 > developped in this project.
 > 
 > If I can add my two cents :), I would add the capacity to switch between
 > pattern and song mode while playing. (so that with a band, you can
 > launch the song, play the instruments, have one of the musicians come up
 > to the PC, switch to pattern mode for more improvisation, and when
 > finished, switch back to song mode to finish the song with the other
 > instruments)
 > 
 > Also, maybe control groups and patterns with a midi device ?
 > 
 > My music computer is a PC, and I would definitly use your project with
 > this switch capacity and groups (which have been implemented in the
 > project I mentioned above).
 > 
 > Good luck, and keep us posted !
 > 
 > Cheers,
 > Xavier
 > 
 > 
 > ----- Original message -----
 > From: "oli_kester" <oli...@zo...>
 > To: seq...@li...,
 > lin...@li..., ahl...@gm...,
 > rc...@fi...
 > Subject: [Seq24-devel] Advice wanted - a project to upgrade seq24
 > Date: Wed, 09 Dec 2015 20:17:23 +0000
 > 
 > Hi Seq24 developers, 
 > 
 > For my final year university project, I am taking on an overhaul of
 > seq24. Below is an excerpt from my project proposal - the list of
 > features I would like to implement - 
 > 
 > [quote]
 > 
 > << Basic (simple changes that should be quick to address) >>
 > - Swap default on midi autoconnect to second value (add to config file)
 > - Song / loop mode switch in main UI 
 > - Recent files list 
 > - Move config file to .config folder in /home
 > - Label keys correctly on loops past bank 1
 >  
 > << Medium (bug fixes, smaller new features) >>
 > - Don't take scene change inputs when renaming loops
 > - With dual screens, remember window placement
 > - Darken Song mode (overall dark theme like Ardour?) 
 > - Fix glitch with overlaps in loops
 > - Session manager fixes
 > - Toggle loops in song mode
 > - Click time bar to position transport
 > - Draw and re-position snap in song mode should behave identically
 > - Add one shot loops
 > - Decrease size of grid in song mode
 > - Add name of scene to the side when in song view
 > - Add autosave function
 > - Midi send if halfway through note (can be enabled / disabled in    
 > preferences)
 > - Draw whole notes instead of cutting off early in song mode loops
 > - Add configurable defaults for note length/ grid snap      
 > - Add note stop/panic button 
 > - Loop colouring
 > - Fix bug where certain slots cannot contain loops
 > 
 > << Challenging (significant new features) >>
 > - Add Box select in song editor (REAPER style) 
 > - Add redo in song mode
 > - Add Record in song mode
 > - Allow splitting of song loops at mouse pointer
 > - Zoom in song mode
 > - Window title should just have the song name
 > - Fix jack sync bug/reset button
 > - Relative velocity altering (REAPER style)      
 > - Add a double / half timing switch for live performance
 >  
 > Where I note “REAPER style”, I plan to source inspiration from the
 > REAPER audio workstation I use under Windows (http://reaper.fm/). The
 > “Ardour” I mention is a Linux audio workstation, and probably the most
 > significant audio project on Linux (http://ardour.org/). 
 > 
 > [end quote]
 > 
 > What do you all think? I have a decent amount of programming experience,
 > but little in the field of audio and no knowledge of GTK+. My tutor
 > suggested that it might be necessary to drop Windows support to make
 > this feasible in the three months I'll be working on it - might this be
 > true?
 > 
 > What is the state of the Launchpad repo? This project will be open
 > source too and I'll happily have my changes pulled back into the main
 > seq24 codebase if people are happy with them.
 > 
 > It'll also be great to have a few people test it during development.
 > I'll send a separate email out to users too.
 > 
 > @Chris Ahlstrom - I'm aware of your current Sequencer64 project, and
 > might use it as my codebase instead of seq24 - please get in touch.
 > Building it as I type!
 > 
 > Any advice greatly appreciated, 
 > 
 > Best, 
 > 
 > Oliver
 > 
 > 
 > 
 > 
 > ------------------------------------------------------------------------------
 > _______________________________________________
 > Seq24-devel mailing list
 > Seq...@li...
 > https://lists.sourceforge.net/lists/listinfo/seq24-devel
 > 
 > ------------------------------------------------------------------------------
 > _______________________________________________
 > Seq24-devel mailing list
 > Seq...@li...
 > https://lists.sourceforge.net/lists/listinfo/seq24-devel
 > 

Re: [Seq24-devel] Advice wanted - a project to upgrade seq24

[oli_kester <oli...@zo...>]

Thanks Xavier, I've downloaded that and will give it a test :)

The pattern / song mode switching is something I want to add - having to dive into the prefs all the time gets old quick! And at the moment you have to pause all playback too.

There is already MIDI pattern control I believe, but you have to set it all up in a text file (I'm yet to use it). I want to make this more accessible with MIDI learn.

By PC, do you mean you run Seq24 on Windows? I've been wondering if dropping Windows support (at least for the duration I'm working on this) might be necessary to avoid fighting compatibility issues with my new features. However, if lots of people run it on Windows then I'll have to seriously consider keeping support!

Thanks

Oliver

---- On Thu, 10 Dec 2015 11:48:07 +0000 <ro...@fr...> wrote ---- 
 > Hello Oliver,
 > 
 > Nice project ! :)
 > 
 > If it can be of any help, when searching for advanced features
 > developped on top of seq24, I came upon this :
 > http://www.subatomicglue.com/seq24/
 > I suggest you at least install it and run it, it also gives other ideas
 > of improvements.
 > Some of the features that you want to implement may even have been
 > developped in this project.
 > 
 > If I can add my two cents :), I would add the capacity to switch between
 > pattern and song mode while playing. (so that with a band, you can
 > launch the song, play the instruments, have one of the musicians come up
 > to the PC, switch to pattern mode for more improvisation, and when
 > finished, switch back to song mode to finish the song with the other
 > instruments)
 > 
 > Also, maybe control groups and patterns with a midi device ?
 > 
 > My music computer is a PC, and I would definitly use your project with
 > this switch capacity and groups (which have been implemented in the
 > project I mentioned above).
 > 
 > Good luck, and keep us posted !
 > 
 > Cheers,
 > Xavier
 > 
 > 
 > ----- Original message -----
 > From: "oli_kester" <oli...@zo...>
 > To: seq...@li...,
 > lin...@li..., ahl...@gm...,
 > rc...@fi...
 > Subject: [Seq24-devel] Advice wanted - a project to upgrade seq24
 > Date: Wed, 09 Dec 2015 20:17:23 +0000
 > 
 > Hi Seq24 developers, 
 > 
 > For my final year university project, I am taking on an overhaul of
 > seq24. Below is an excerpt from my project proposal - the list of
 > features I would like to implement - 
 > 
 > [quote]
 > 
 > << Basic (simple changes that should be quick to address) >>
 > - Swap default on midi autoconnect to second value (add to config file)
 > - Song / loop mode switch in main UI 
 > - Recent files list 
 > - Move config file to .config folder in /home
 > - Label keys correctly on loops past bank 1
 >  
 > << Medium (bug fixes, smaller new features) >>
 > - Don't take scene change inputs when renaming loops
 > - With dual screens, remember window placement
 > - Darken Song mode (overall dark theme like Ardour?) 
 > - Fix glitch with overlaps in loops
 > - Session manager fixes
 > - Toggle loops in song mode
 > - Click time bar to position transport
 > - Draw and re-position snap in song mode should behave identically
 > - Add one shot loops
 > - Decrease size of grid in song mode
 > - Add name of scene to the side when in song view
 > - Add autosave function
 > - Midi send if halfway through note (can be enabled / disabled in    
 > preferences)
 > - Draw whole notes instead of cutting off early in song mode loops
 > - Add configurable defaults for note length/ grid snap      
 > - Add note stop/panic button 
 > - Loop colouring
 > - Fix bug where certain slots cannot contain loops
 > 
 > << Challenging (significant new features) >>
 > - Add Box select in song editor (REAPER style) 
 > - Add redo in song mode
 > - Add Record in song mode
 > - Allow splitting of song loops at mouse pointer
 > - Zoom in song mode
 > - Window title should just have the song name
 > - Fix jack sync bug/reset button
 > - Relative velocity altering (REAPER style)      
 > - Add a double / half timing switch for live performance
 >  
 > Where I note “REAPER style”, I plan to source inspiration from the
 > REAPER audio workstation I use under Windows (http://reaper.fm/). The
 > “Ardour” I mention is a Linux audio workstation, and probably the most
 > significant audio project on Linux (http://ardour.org/). 
 > 
 > [end quote]
 > 
 > What do you all think? I have a decent amount of programming experience,
 > but little in the field of audio and no knowledge of GTK+. My tutor
 > suggested that it might be necessary to drop Windows support to make
 > this feasible in the three months I'll be working on it - might this be
 > true?
 > 
 > What is the state of the Launchpad repo? This project will be open
 > source too and I'll happily have my changes pulled back into the main
 > seq24 codebase if people are happy with them.
 > 
 > It'll also be great to have a few people test it during development.
 > I'll send a separate email out to users too.
 > 
 > @Chris Ahlstrom - I'm aware of your current Sequencer64 project, and
 > might use it as my codebase instead of seq24 - please get in touch.
 > Building it as I type!
 > 
 > Any advice greatly appreciated, 
 > 
 > Best, 
 > 
 > Oliver
 > 
 > 
 > 
 > 
 > ------------------------------------------------------------------------------
 > _______________________________________________
 > Seq24-devel mailing list
 > Seq...@li...
 > https://lists.sourceforge.net/lists/listinfo/seq24-devel
 > 
 > ------------------------------------------------------------------------------
 > _______________________________________________
 > Seq24-devel mailing list
 > Seq...@li...
 > https://lists.sourceforge.net/lists/listinfo/seq24-devel
 > 

Re: [Seq24-devel] Advice wanted - a project to upgrade seq24

[<ro...@fr...>]

Hello Oliver,

Nice project ! :)

If it can be of any help, when searching for advanced features
developped on top of seq24, I came upon this :
http://www.subatomicglue.com/seq24/
I suggest you at least install it and run it, it also gives other ideas
of improvements.
Some of the features that you want to implement may even have been
developped in this project.

If I can add my two cents :), I would add the capacity to switch between
pattern and song mode while playing. (so that with a band, you can
launch the song, play the instruments, have one of the musicians come up
to the PC, switch to pattern mode for more improvisation, and when
finished, switch back to song mode to finish the song with the other
instruments)

Also, maybe control groups and patterns with a midi device ?

My music computer is a PC, and I would definitly use your project with
this switch capacity and groups (which have been implemented in the
project I mentioned above).

Good luck, and keep us posted !

Cheers,
Xavier


----- Original message -----
From: "oli_kester" <oli...@zo...>
To: seq...@li...,
lin...@li..., ahl...@gm...,
rc...@fi...
Subject: [Seq24-devel] Advice wanted - a project to upgrade seq24
Date: Wed, 09 Dec 2015 20:17:23 +0000

Hi Seq24 developers, 

For my final year university project, I am taking on an overhaul of
seq24. Below is an excerpt from my project proposal - the list of
features I would like to implement - 

[quote]

<< Basic (simple changes that should be quick to address) >>
- Swap default on midi autoconnect to second value (add to config file)
- Song / loop mode switch in main UI 
- Recent files list 
- Move config file to .config folder in /home
- Label keys correctly on loops past bank 1
 
<< Medium (bug fixes, smaller new features) >>
- Don't take scene change inputs when renaming loops
- With dual screens, remember window placement
- Darken Song mode (overall dark theme like Ardour?) 
- Fix glitch with overlaps in loops
- Session manager fixes
- Toggle loops in song mode
- Click time bar to position transport
- Draw and re-position snap in song mode should behave identically
- Add one shot loops
- Decrease size of grid in song mode
- Add name of scene to the side when in song view
- Add autosave function
- Midi send if halfway through note (can be enabled / disabled in    
preferences)
- Draw whole notes instead of cutting off early in song mode loops
- Add configurable defaults for note length/ grid snap      
- Add note stop/panic button 
- Loop colouring
- Fix bug where certain slots cannot contain loops

<< Challenging (significant new features) >>
- Add Box select in song editor (REAPER style) 
- Add redo in song mode
- Add Record in song mode
- Allow splitting of song loops at mouse pointer
- Zoom in song mode
- Window title should just have the song name
- Fix jack sync bug/reset button
- Relative velocity altering (REAPER style)      
- Add a double / half timing switch for live performance
 
Where I note “REAPER style”, I plan to source inspiration from the
REAPER audio workstation I use under Windows (http://reaper.fm/). The
“Ardour” I mention is a Linux audio workstation, and probably the most
significant audio project on Linux (http://ardour.org/). 

[end quote]

What do you all think? I have a decent amount of programming experience,
but little in the field of audio and no knowledge of GTK+. My tutor
suggested that it might be necessary to drop Windows support to make
this feasible in the three months I'll be working on it - might this be
true?

What is the state of the Launchpad repo? This project will be open
source too and I'll happily have my changes pulled back into the main
seq24 codebase if people are happy with them.

It'll also be great to have a few people test it during development.
I'll send a separate email out to users too.

@Chris Ahlstrom - I'm aware of your current Sequencer64 project, and
might use it as my codebase instead of seq24 - please get in touch.
Building it as I type!

Any advice greatly appreciated, 

Best, 

Oliver




------------------------------------------------------------------------------
_______________________________________________
Seq24-devel mailing list
Seq...@li...
https://lists.sourceforge.net/lists/listinfo/seq24-devel

[Seq24-devel] Advice wanted - a project to upgrade seq24

[oli_kester <oli...@zo...>]

Hi Seq24 developers, 

For my final year university project, I am taking on an overhaul of seq24. Below is an excerpt from my project proposal - the list of features I would like to implement - 

[quote]

<< Basic (simple changes that should be quick to address) >>
- Swap default on midi autoconnect to second value (add to config file)
- Song / loop mode switch in main UI 
- Recent files list 
- Move config file to .config folder in /home
- Label keys correctly on loops past bank 1
 
<< Medium (bug fixes, smaller new features) >>
- Don't take scene change inputs when renaming loops
- With dual screens, remember window placement
- Darken Song mode (overall dark theme like Ardour?) 
- Fix glitch with overlaps in loops
- Session manager fixes
- Toggle loops in song mode
- Click time bar to position transport
- Draw and re-position snap in song mode should behave identically
- Add one shot loops
- Decrease size of grid in song mode
- Add name of scene to the side when in song view
- Add autosave function
- Midi send if halfway through note (can be enabled / disabled in     preferences)
- Draw whole notes instead of cutting off early in song mode loops
- Add configurable defaults for note length/ grid snap      
- Add note stop/panic button 
- Loop colouring
- Fix bug where certain slots cannot contain loops

<< Challenging (significant new features) >>
- Add Box select in song editor (REAPER style) 
- Add redo in song mode
- Add Record in song mode
- Allow splitting of song loops at mouse pointer
- Zoom in song mode
- Window title should just have the song name
- Fix jack sync bug/reset button
- Relative velocity altering (REAPER style)      
- Add a double / half timing switch for live performance
 
Where I note “REAPER style”, I plan to source inspiration from the REAPER audio workstation I use under Windows (http://reaper.fm/). The “Ardour” I mention is a Linux audio workstation, and probably the most significant audio project on Linux (http://ardour.org/). 

[end quote]

What do you all think? I have a decent amount of programming experience, but little in the field of audio and no knowledge of GTK+. My tutor suggested that it might be necessary to drop Windows support to make this feasible in the three months I'll be working on it - might this be true?

What is the state of the Launchpad repo? This project will be open source too and I'll happily have my changes pulled back into the main seq24 codebase if people are happy with them.

It'll also be great to have a few people test it during development. I'll send a separate email out to users too.

@Chris Ahlstrom - I'm aware of your current Sequencer64 project, and might use it as my codebase instead of seq24 - please get in touch. Building it as I type!

Any advice greatly appreciated, 

Best, 

Oliver

Re: [Seq24-devel] [Branch ~seq24team/seq24/trunk] Rev 134: Avoid usage of recursive make

[Sebastien A. <ac...@fr...>]

On 04/08/2014 11:44 PM, Guido Scholz wrote:
>
> $ autoreconf --version
> autoreconf (GNU Autoconf) 2.69
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+/Autoconf: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>,
> <http://gnu.org/licenses/exceptions.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by David J. MacKenzie and Akim Demaille.
>
>
> I am on a Ubuntu saucy (Mint 16).

Could you please check your version of automake ?
The %D% feature (aka %reldir%) was actually introduced with automake-1.14.
( see: https://blog.flameeyes.eu/2013/06/autotools-mythbuster-what-s-new-in-automake-1-14 )
The %D% expands to the relative path of the included file, at autoreconf time (not at build time).
Make will not see them.

This feature allows nesting modules, while avoiding the specification of redundant nested paths *and* avoiding the use of recursive make.
 

> By the way %-patterns in make files are a GNU extension.

I know ; but AFAIU those are not 

Cheers,
Sebastien

PS: sorry for the double-post, I'm struggling with my email client and my two email addresses (one of which getting my mails rejected "waiting for moderator approval").

Re: [Seq24-devel] [Branch ~seq24team/seq24/trunk] Rev 134: Avoid usage of recursive make

[Guido S. <gui...@gm...>]

Am Tue, 08. Apr 2014 um 22:53:57 +0200 schrieb Sebastien Alaiwan:

> Hi Guido,

Hi Sebastien,

> Thanks for your feedback and sorry for the trouble!
> 
> Which version of autoreconf are you using?
> It seems to work on my system:

$ autoreconf --version
autoreconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>,
<http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.


I am on a Ubuntu saucy (Mint 16).

By the way %-patterns in make files are a GNU extension.

Guido

-- 
http://wie-im-flug.net/
http://www.lug-burghausen.org/

Re: [Seq24-devel] [Branch ~seq24team/seq24/trunk] Rev 134: Avoid usage of recursive make

[Sebastien A. <ac...@fr...>]

Hi Guido,

Thanks for your feedback and sorry for the trouble!

Which version of autoreconf are you using?
It seems to work on my system:

ace@ANTEC seq24 % autoreconf -fi && echo OK
OK
ace@ANTEC seq24 % autoreconf --version
autoreconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.
---
Autoconf 2.50 chosen by Debian wrapper script.
For information and tuning advice see autoconf(1).
ace@ANTEC seq24 %





On 04/08/2014 10:38 PM, Guido Scholz wrote:
> Am Tue, 08. Apr 2014 um 22:18:48 +0200 schrieb Guido Scholz:
>
>> Am Tue, 08. Apr 2014 um 19:05:29 -0000 schrieb no...@la...:
>>
> Hi Sebastien,
>>> Merge authors:
>>>   Sebastien Alaiwan (ace17)
>>> ------------------------------------------------------------
>>> revno: 134 [merge]
>>> committer: Sebastien Alaiwan <ac...@fr...>
>>> branch nick: seq24
>>> timestamp: Tue 2014-04-08 21:04:20 +0200
>>> message:
>>>   Avoid usage of recursive make
>>> renamed:
>>>   man/Makefile.am => man/Module.am
>>>   src/Makefile.am => src/Module.am
>>>   src/pixmaps/Makefile.am => src/pixmaps/Module.am
>>> modified:
>>>   Makefile.am
>>>   configure.ac
>>>   man/Module.am
>>>   src/Module.am
>>>   src/pixmaps/Module.am
> here is an other bug:
>
> $ LANG=C make dist
> make  dist-bzip2 dist-gzip am__post_remove_distdir='@:'
> make[1]: Entering directory `/home/guido/src/c/gtk/seq24/trunk'
> make[1]: *** No rule to make target `font.h', needed by `distdir'.
> Stop.
> make[1]: Leaving directory `/home/guido/src/c/gtk/seq24/trunk'
> make: *** [dist] Error 2
>
>
> due to the missing path for "font.h":
>
>         src/event.cpp \
> ->      src/font.cpp font.h \
>         src/globals.h \
>
> Guido
>
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment 
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
>
>
> _______________________________________________
> Seq24-devel mailing list
> Seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-devel

Re: [Seq24-devel] [Branch ~seq24team/seq24/trunk] Rev 134: Avoid usage of recursive make

[Guido S. <gui...@gm...>]

Am Tue, 08. Apr 2014 um 22:18:48 +0200 schrieb Guido Scholz:

> Am Tue, 08. Apr 2014 um 19:05:29 -0000 schrieb no...@la...:
> 
Hi Sebastien,
> 
> > Merge authors:
> >   Sebastien Alaiwan (ace17)
> > ------------------------------------------------------------
> > revno: 134 [merge]
> > committer: Sebastien Alaiwan <ac...@fr...>
> > branch nick: seq24
> > timestamp: Tue 2014-04-08 21:04:20 +0200
> > message:
> >   Avoid usage of recursive make
> > renamed:
> >   man/Makefile.am => man/Module.am
> >   src/Makefile.am => src/Module.am
> >   src/pixmaps/Makefile.am => src/pixmaps/Module.am
> > modified:
> >   Makefile.am
> >   configure.ac
> >   man/Module.am
> >   src/Module.am
> >   src/pixmaps/Module.am

here is an other bug:

$ LANG=C make dist
make  dist-bzip2 dist-gzip am__post_remove_distdir='@:'
make[1]: Entering directory `/home/guido/src/c/gtk/seq24/trunk'
make[1]: *** No rule to make target `font.h', needed by `distdir'.
Stop.
make[1]: Leaving directory `/home/guido/src/c/gtk/seq24/trunk'
make: *** [dist] Error 2


due to the missing path for "font.h":

        src/event.cpp \
->      src/font.cpp font.h \
        src/globals.h \

Guido

-- 
http://wie-im-flug.net/
http://www.lug-burghausen.org/

Re: [Seq24-devel] [Branch ~seq24team/seq24/trunk] Rev 134: Avoid usage of recursive make

[Guido S. <gui...@gm...>]

Am Tue, 08. Apr 2014 um 19:05:29 -0000 schrieb no...@la...:

Hi Sebastien,


> Merge authors:
>   Sebastien Alaiwan (ace17)
> ------------------------------------------------------------
> revno: 134 [merge]
> committer: Sebastien Alaiwan <ac...@fr...>
> branch nick: seq24
> timestamp: Tue 2014-04-08 21:04:20 +0200
> message:
>   Avoid usage of recursive make
> renamed:
>   man/Makefile.am => man/Module.am
>   src/Makefile.am => src/Module.am
>   src/pixmaps/Makefile.am => src/pixmaps/Module.am
> modified:
>   Makefile.am
>   configure.ac
>   man/Module.am
>   src/Module.am
>   src/pixmaps/Module.am

this change breaks the usability of autoreconf:


$ autoreconf -fi
src/Module.am:5: error: bad characters in variable name '%C%_seq24_LDADD'
Makefile.am:9:   'src/Module.am' included from here
src/Module.am:9: error: bad characters in variable name '%C%_seq24_SOURCES'
Makefile.am:9:   'src/Module.am' included from here
automake: warning: compiling '%D%/seq24.c' in subdir requires 'AM_PROG_CC_C_O' in 'configure.ac'
Makefile.am:9:   'src/Module.am' included from here
src/Module.am:7:   while processing program '%D%/seq24'
src/Module.am:9: warning: variable '%C%_seq24_SOURCES' is defined but no program or
src/Module.am:9: library has '%C%_seq24' as canonical name (possible typo)
Makefile.am:9:   'src/Module.am' included from here
src/Module.am:5: warning: variable '%C%_seq24_LDADD' is defined but no program or
src/Module.am:5: library has '%C%_seq24' as canonical name (possible typo)
Makefile.am:9:   'src/Module.am' included from here
autoreconf: automake failed with exit status: 1


This can be fixed by replacing "%C%" and "%D%" by the appropriate paths.

Guido

-- 
http://wie-im-flug.net/
http://www.lug-burghausen.org/

[Seq24-devel] MIDI Control Data

[Luke <luk...@gm...>]

Hi Developers,

Thanks for your hard work. I'm not sure if this is specifically a bug, 
or just a lack of a feature?
I'm also uncertain whether I should be sending this to you or to the 
user mailing list.
When editing control data or inputting notes for that matter, no midi 
messages are sent. This means I cannot use the ardour3 midi learn 
feature to assign that control data to a parameter in ardour.

I hope this would be something that could be done easily, or it is just 
something I am missing.

Thanks for your time, eager for a reply

Sincerely

Luke Digance

Re: [Seq24-devel] [Bug 929251] [NEW] can't change tempo/bpm while playing as jack master

[Guido S. <gui...@ba...>]

Am Thu, 09. Feb 2012 um 01:34:13 -0000 schrieb Allan Klinbail:

> Public bug reported:
 
> Hi,

Hi Allan,

> I'm hoping this is still under development.. but lack of activity doesn't have my hopes up. 
> seq24 is almost perfect as MIDI sequencer .. have even been able to sync it with hydrogen (which has limited MIDI capacity but makes for a good complimentary drum machine) 
> 
> Using seq24 0.9.2 and jack 1.9.8 (jackdmp)
> 
> I don't know if this is a problem with  the jack tranport mechanism or
> if it is a problem with the seq 24.. however it would be awesome if it
> were possible to change the tempo while playing in jack mastermode.

this issue is connected to an internal change of the jack API and was
discussed on the seq24 mailinglists some time ago. I personally have no
deep insight to what happens there in seq24 and goes wrong in relation
to current jack (1 + 2) versions and most probably I will not find time
to dive into that topic in the next future.

May be some other developer can help out (CCed to the list).

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

[Seq24-devel] Python Sequencer

[Ivan H. <ihe...@ki...>]

Hi folks.
Some time ago I made a small python module to read and write alsa midi 
data and later used that to make a python sketch of ideas i was trying 
to implement in Seq24, specially in those fields that I was missing my 
old tracker experiences.
It's quite unpolished and lacking a lot of features, but can be used to 
try ideas in python before starting the hard work of coding in c++ into 
seq24.

If someone is interested the code is at

http://www.desfonema.com.ar/dseq-0.3.tar.bz2

Cheers
Ivan

Re: [Seq24-devel] manual_alsa_ports option not working in 0.9.2

[Guido S. <gui...@ba...>]

Am Thu, 02. Dec 2010 um 23:23:47 +0200 schrieb Jaakko Sipari:

Hi Jaakko,

> Ok, the problem seems to be that Seq24 overwrites the command line
> parameters when reading the config file. The manual_alsa_ports
> configuration option works when read from seq24rc.

its fixed in the repository right now, but a little bit strange to get
this "Reading [/home..." message, running a "seq24 --version" command.

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [Seq24-devel] manual_alsa_ports option not working in 0.9.2

[Guido S. <gui...@ba...>]

Am Thu, 02. Dec 2010 um 22:57:13 +0200 schrieb Jaakko Sipari:

> Hi!

Hi Jaakko,

> I just built the 0.9.2 version of Seq24 and it seems that the
> --manual_alsa_ports (or -m) option doesn't work like it used to. No
> alsa ports are created for midi output (or output). Is there a
> replacing option or is this a bug?

I am not aware of having changed this, so may be this is a bug.

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [Seq24-devel] manual_alsa_ports option not working in 0.9.2

[Jaakko S. <jaa...@gm...>]

On Thu, Dec 2, 2010 at 10:57 PM, Jaakko Sipari <jaa...@gm...> wrote:
> Hi!
>
> I just built the 0.9.2 version of Seq24 and it seems that the
> --manual_alsa_ports (or -m) option doesn't work like it used to. No
> alsa ports are created for midi output (or output). Is there a
> replacing option or is this a bug?
>
> I haven't checked the code yet to see for myself what's changed, but
> though I'd still give a quick heads up on this.
>
> BR, Jaakko
>

Ok, the problem seems to be that Seq24 overwrites the command line
parameters when reading the config file. The manual_alsa_ports
configuration option works when read from seq24rc.

BR, Jaakko

[Seq24-devel] manual_alsa_ports option not working in 0.9.2

[Jaakko S. <jaa...@gm...>]

Hi!

I just built the 0.9.2 version of Seq24 and it seems that the
--manual_alsa_ports (or -m) option doesn't work like it used to. No
alsa ports are created for midi output (or output). Is there a
replacing option or is this a bug?

I haven't checked the code yet to see for myself what's changed, but
though I'd still give a quick heads up on this.

BR, Jaakko

[Seq24-devel] [ANN] seq24 0.9.2 released

[Guido S. <gui...@ba...>]

Dear seq24 users,
a new seq24 release is out published by the Seq24team.

  https://edge.launchpad.net/seq24/

This release fixes a few bugs and provides some new features which
mainly extend session functionality; for details please have a look
at the news list below.  All users should upgrade to 0.9.2.

Please find source tarballs on the download page:

   https://edge.launchpad.net/seq24/+download

For ready made packages Ubuntu users may refer to my PPA:
  
  https://edge.launchpad.net/~gscholz/+archive/ppa  


NEWS
====

seq24-0.9.2 (2010-11-27)

Fixed Bugs
  * Fix tooltip usage for older GTK versions (GTK_MINOR_VERSION < 12)
  * Fix sched_param memory leaks
  * Fix doubled key event for screen set name line

New Features
  * Add support for jack session, patch provided by Torben Hohn
  * Add interrupt handler for SIGUSR1 to enable LADISH level 1 support
  * Add interrupt handler for SIGINT to ask for unsaved file changes
  * Remove "-f" command line option to be replaced by a simple <filename>
    argument (see "seq24 --help" for more information)

General Changes
  * Add mnemonics for bottom line widgets in main window and label for
    screen set name edit line
  * Add missing command line parameters to help message, display short
    options as well
  * Add command line option for program version
  * Add missing command line parameters to man page
  * Remove complaints about file read error if configuration files do not
    exist
  * Cleanup configure.in: remove unused variables, harmonize option
    enabling/disabling
  * Some code cleanups


Enjoy
Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [Seq24-devel] [seq24-users] Re : Time for a 0.9.2 release

[Guido S. <gui...@ba...>]

Am Fri, 26. Nov 2010 um 21:37:22 +0000 schrieb ihe...@ki...:

Hi Ivan,

> I woud be happy to see a new release. I hate installing a new ubuntu desktop and finding I don't have all the new features on the repository.
> Also someone knows how to make a ppa?

you can use mine:

  https://edge.launchpad.net/~gscholz/+archive/ppa

It provides a 0.9.1 release.

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [Seq24-devel] [seq24-users] Re : Time for a 0.9.2 release

[<ihe...@ki...>]

I woud be happy to see a new release. I hate installing a new ubuntu desktop and finding I don't have all the new features on the repository.
Also someone knows how to make a ppa?
Cheers
Ivan Hernandez - Kiu System Solutions

-----Original Message-----
From: Frank Kober <goe...@ya...>
Date: Fri, 26 Nov 2010 21:30:58 
To: <seq...@li...>; <seq...@li...>; Guido Scholz<gui...@ba...>
Subject: [seq24-users] Re :  Time for a 0.9.2 release

Hi Guido et al,

I have been using bzr rev 74 for a long time and was quite happy with it. The overdue 0.9.1 was therefore very welcome and you guys did a great job on it.
The current bzr looks fine as far as I can see, except that I do not get automatic jack transport connection when I start with the corresponding options --jack_transport and --jack_master. That seemed fine in 0.9.1. 

Do you confirm this?

Regards
Frank


--- En date de : Mer 24.11.10, Guido Scholz <gui...@ba...> a écrit :

> De: Guido Scholz <gui...@ba...>
> Objet: [seq24-users] Time for a 0.9.2 release
> À: seq...@li..., seq...@li...
> Date: Mercredi 24 novembre 2010, 22h56
> Dear developers and users,
> I am more or less ready for the next release round (before
> I will go
> away for an other job). This is what was assembled
> according to the NEWS
> file:
> 
> 8<-------------
> 
> Fixed Bugs
>   * Fix tooltip usage for older GTK versions
> (GTK_MINOR_VERSION < 12)
>   * Fix sched_param memory leaks
>   * Fix doubled key event for screen set name line
> 
> New Features
>   * Add support for jack session, patch provided by
> Torben Hohn
>   * Add interrupt handler for SIGUSR1 to enable LADISH
> level 1 support
>   * Add interrupt handler for SIGINT to ask for
> unsaved file changes
>   * Remove "-f" command line option to be replaced by
> a simple <filename>
>     argument (see "seq24 --help" for more
> information)
> 
> General Changes
>   * Add mnemonics for bottom line widgets in main
> window and label for
>     screen set name edit line
>   * Add missing command line parameters to help
> message, display short
>     options as well
>   * Add command line option for program version
>   * Add missing command line parameters to man page
>   * Remove complaints about file read error if
> configuration files do not
>     exist
>   * Some code cleanups
> 
> 8<-------------
> 
> It is the right time now to run some tests of the code
> which is
> currently only available from repository. The next release
> will be
> published in a few days if not stopped for what ever
> reason.
> 
> Guido
> 
> -- 
> http://www.bayernline.de/~gscholz/
> http://www.lug-burghausen.org/
> 
> -----La pièce jointe associée suit-----
> 
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance
> To Win $500!
> Tap into the largest installed PC base & get more eyes
> on your game by
> optimizing for Intel(R) Graphics Technology. Get started
> today with the
> Intel(R) Software Partner Program. Five $500 cash prizes
> are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> -----La pièce jointe associée suit-----
> 
>_______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
> 


      

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
seq24-users mailing list
seq...@li...
https://lists.sourceforge.net/lists/listinfo/seq24-users

[Seq24-devel] Time for a 0.9.2 release

[Guido S. <gui...@ba...>]

Dear developers and users,
I am more or less ready for the next release round (before I will go
away for an other job). This is what was assembled according to the NEWS
file:

8<-------------

Fixed Bugs
  * Fix tooltip usage for older GTK versions (GTK_MINOR_VERSION < 12)
  * Fix sched_param memory leaks
  * Fix doubled key event for screen set name line

New Features
  * Add support for jack session, patch provided by Torben Hohn
  * Add interrupt handler for SIGUSR1 to enable LADISH level 1 support
  * Add interrupt handler for SIGINT to ask for unsaved file changes
  * Remove "-f" command line option to be replaced by a simple <filename>
    argument (see "seq24 --help" for more information)

General Changes
  * Add mnemonics for bottom line widgets in main window and label for
    screen set name edit line
  * Add missing command line parameters to help message, display short
    options as well
  * Add command line option for program version
  * Add missing command line parameters to man page
  * Remove complaints about file read error if configuration files do not
    exist
  * Some code cleanups

8<-------------

It is the right time now to run some tests of the code which is
currently only available from repository. The next release will be
published in a few days if not stopped for what ever reason.

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/

Re: [Seq24-devel] [PATCH] support for jack-session API

[Guido S. <gui...@ba...>]

Am Thu, 11. Nov 2010 um 15:29:32 +0100 schrieb torbenh:

Hi Torben,

> clientname should be deterministic.
> using pids in clientnames is bad practise, and people regularly complain
> about this.

your patch is in, thanks. I had to add a define in perform.h. Currently
I have no setup to test the result (means: jack session working).

Guido

-- 
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/