Ladies and Gentlemen,
hereby the Laborejo Software Suite releases updates for its programs in
the hope to be useful in your musical toolbox.
You can now download Agordejo version 0.3.0
https://laborejo.org/downloads/agordejo-0.3.0.tar.gz
All software is released under GPLv3.
Agordejo (Esperanto: 'place to set things up') is a music production session manager.
It is used to start your programs, remember their (JACK) interconnections and make
your life easier in general. It does not re-invent the wheel but instead uses the
New-Session-Manager daemon and enhances it with some tricks of its own, that always
remain 100% compatible with the original sessions.
Changelog Highlights:
* Remove "Quick" mode. As it turns out "Full" mode is quick enough. Port convenience features to full mode.
* More buttons for session control, previously only accessible through context menus.
* Add a timeline above running session to show global jack transport position. Also add controls to set the position.
Saving the timeline settings per session is done via nsm-data, which increases version from 1.0 to 1.1
* More functionality in the System Tray Icon (pure save, toggle individual client visibility)
* Double click on a crashed clients opens it again.
* Bugfixes, Quality-of-life improvements and data integrity checks
You can find all releases as sources here. Also check your distribution
for packages in a few days after this announcement, please.
https://laborejo.org/downloads/
For more information, a multi-language user manual, build instructions
and git access please visit
https://www.laborejo.org/agordejo/
Greetings,
Laborejo Software Suite
https://www.laborejo.org/
Agordejo 0.3.0 - NSM Frontend (Feature Release)
Moderators: raboof, MattKingUSA, khz
- Largos
- Established Member
- Posts: 630
- Joined: Mon Oct 05, 2020 12:21 pm
- Has thanked: 71 times
- Been thanked: 185 times
Re: Agordejo 0.3.0 - NSM Frontend (Feature Release)
Really nice updates. The system tray icon, is going to save some clicking through windows.
I did manage to break something. If the JACK server is restarted whilst the Agordejo client is open, then the playback controls won't work unless Agordejo is restarted as well.
I did manage to break something. If the JACK server is restarted whilst the Agordejo client is open, then the playback controls won't work unless Agordejo is restarted as well.
-
- Established Member
- Posts: 538
- Joined: Wed Oct 22, 2008 9:05 pm
- Has thanked: 35 times
- Been thanked: 94 times
- Contact:
Re: Agordejo 0.3.0 - NSM Frontend (Feature Release)
What do you suggest should happen if the JACK server restarts?
If JACK quits while the session is running all your audio programs will stop working, freeze or crash as well.
I always considered a running JACK an assumed given and it stopping akin to unplugging an external hard drive while working on it's files.
- Largos
- Established Member
- Posts: 630
- Joined: Mon Oct 05, 2020 12:21 pm
- Has thanked: 71 times
- Been thanked: 185 times
Re: Agordejo 0.3.0 - NSM Frontend (Feature Release)
This also happens when you restart jack when there isn't a project loaded, which was the situation when I found it. There's also no visual feedback from the program (as opposed to the error message upon a disconnect with a loaded project) It seems like there needs to be a way to reset a connection made in the program start up or do that connection when the project starts instead. I don't know enough about though.
-
- Established Member
- Posts: 538
- Joined: Wed Oct 22, 2008 9:05 pm
- Has thanked: 35 times
- Been thanked: 94 times
- Contact:
Re: Agordejo 0.3.0 - NSM Frontend (Feature Release)
Agordejo starts its own internal Jack-Client on startup. You don't see it in a patchbay because it has no ports, but it is there.
If you stop JACK afterwards the client loses connection to the JACK server. That is expected and outside the control of Agordejo
The solution is to just restart Agordejo. If there was no project loaded anyway then there is no further problem.
I consider this an extreme corner case. Stopping JACK while jack programs are running is a broken state, systemwide.
If you stop JACK afterwards the client loses connection to the JACK server. That is expected and outside the control of Agordejo
The solution is to just restart Agordejo. If there was no project loaded anyway then there is no further problem.
I consider this an extreme corner case. Stopping JACK while jack programs are running is a broken state, systemwide.