[publié] Ladish 0.2
Coucou,
J'ai bien envie de faire un article sur Ladish pour sa version 0.2 .
On peut commencer par traduire le message d'annonce sur la liste LAD de Nedko Arnaudov.
Avec un lien vers sa page dédiée : Ladish.
Un lien aussi vers la vidéo de présentation (attention, 119Mo !].
Le message de nedko :
Citation :
The second milestone is reached et le résultat est un tarball que les braves âmes téléchargeront et essaieront. Il peut démarrer les applications et restaurer leurs connections. Les applications Level 1 sont supportées.
Faites attention au fait qu'il n'y a encore aucune applications qui a déjà implémenté le level 1. Si une application non-level-1 est démarrée au level 1, elle va probablement quitter à la sauvegarde du studio, car le signal par défaut pour SIGUSR1 va terminer le processus.
Cette preview offre également le support a2jmidid. Lancer le script a2j comme une application du studio.
C'est un logiciel de qualité beta, utiliser-me avec des précautions double.
Je voudrai remercier les utilisateurs des premières heures et spécialement Frank Kober pour leurs aides pour le test de la version git du code de ladish et pour les suggestions utiles qu'ils ont fournies.
Cette construction produit 3 composants opérationnels :
* ladishd - Le démon, un service D-Bus
* gladish - une interface graphique GTK
* ladish_control - Une interface en ligne de commande
Dans le tarball, vous trouverez aussi :
* flowcanvas-0.6.0
* LADI Tools (version svn)
* a2jmidid-6 (contient le script a2j à utiliser dans ladish)
* jack2 qui vient de la branche de développement ladi
La branche ladi de Jack2 contient des fixatifs pour 2 problèmes importants:
* Race that causes connection restore to fail sometimes during studio startup (http://ladish.org/ticket/28)
* A deadlock on studio start (http://ladish.org/ticket/35)
Avec un peu de chance, ces fixatifs seront intégrés dans la prochaine version de jack2 (1.9.5).
The jack2 ladi branch also contains the no-self-connect changeset that adds new engine option, for disabling self connect of apps. Default value for this option is to allow self connections.
Soyez sûr de configurer jack2 avec --dbus (et peut être avec --classic aussi).
Téléchargement:
http://ladish.org/download/ladish-0.2.tar.bz2
http://ladish.org/download/ladish-0.2.tar.bz2.sig
Page d'accueil: http://ladish.org/
Le plan de route : http://ladish.org/roadmap
-------------------------
LADI Session Handler or simply ladish is a session management system for JACK applications on GNU/Linux. Its aim is to allow you to have many different audio programs running at once, to save their setup, close them down and then easily reload the setup at some other time. ladish doesn't deal with any kind of audio or MIDI data itself; it just runs programs, deals with saving/loading (arbitrary) data and connects JACK ports together. It can also be used to move entire sessions between computers, or post sessions on the Internet for download.
Project goals:
* Save and restore sets of JACK (audio and MIDI) enabled applications.
* Provide JACK clients with virtual hardware ports, so projects can be transfered (or backups restored) between computers running different hardware and backups.
* Don't require session handling library to be used. There is no need of such library for restoring connections between JACK clients.
* Flow canvas based GUI. Positions of elements on the canvas are saved/restored.
* Allow clients to use external storage to save its state. This includes storing internal state to non-filesystem place like memory of a hardware synth. This also includes storing client internal state (client project data) in a way that is not directly bound to ladish project.
* Import/export operations, as opposed to save/load. Save/load operate in current system and may cause saving data outside of project itself (external storage). Import/export uses/produces "tarball" suitable for transferring session data over network to other computer or storing it in a backup archive.
* Hierarchical or tag-based organization of projects.
* List of JACK applications. Applications are always started through ladish to have restored runtime environment closer to one existed before project save.
* Distributed studio - network connected computers. Netjack configuration is part of the studio and thus is saved/restored.
* Collaborate with the X11 window manager so window properties like window position, virtual desktop and screen (multimonitor) are saved/restored.
Faites attention au fait qu'il n'y a encore aucune applications qui a déjà implémenté le level 1. Si une application non-level-1 est démarrée au level 1, elle va probablement quitter à la sauvegarde du studio, car le signal par défaut pour SIGUSR1 va terminer le processus.
Cette preview offre également le support a2jmidid. Lancer le script a2j comme une application du studio.
C'est un logiciel de qualité beta, utiliser-me avec des précautions double.
Je voudrai remercier les utilisateurs des premières heures et spécialement Frank Kober pour leurs aides pour le test de la version git du code de ladish et pour les suggestions utiles qu'ils ont fournies.
Cette construction produit 3 composants opérationnels :
* ladishd - Le démon, un service D-Bus
* gladish - une interface graphique GTK
* ladish_control - Une interface en ligne de commande
Dans le tarball, vous trouverez aussi :
* flowcanvas-0.6.0
* LADI Tools (version svn)
* a2jmidid-6 (contient le script a2j à utiliser dans ladish)
* jack2 qui vient de la branche de développement ladi
La branche ladi de Jack2 contient des fixatifs pour 2 problèmes importants:
* Race that causes connection restore to fail sometimes during studio startup (http://ladish.org/ticket/28)
* A deadlock on studio start (http://ladish.org/ticket/35)
Avec un peu de chance, ces fixatifs seront intégrés dans la prochaine version de jack2 (1.9.5).
The jack2 ladi branch also contains the no-self-connect changeset that adds new engine option, for disabling self connect of apps. Default value for this option is to allow self connections.
Soyez sûr de configurer jack2 avec --dbus (et peut être avec --classic aussi).
Téléchargement:
http://ladish.org/download/ladish-0.2.tar.bz2
http://ladish.org/download/ladish-0.2.tar.bz2.sig
Page d'accueil: http://ladish.org/
Le plan de route : http://ladish.org/roadmap
LADI Session Handler or simply ladish is a session management system for JACK applications on GNU/Linux. Its aim is to allow you to have many different audio programs running at once, to save their setup, close them down and then easily reload the setup at some other time. ladish doesn't deal with any kind of audio or MIDI data itself; it just runs programs, deals with saving/loading (arbitrary) data and connects JACK ports together. It can also be used to move entire sessions between computers, or post sessions on the Internet for download.
Project goals:
* Save and restore sets of JACK (audio and MIDI) enabled applications.
* Provide JACK clients with virtual hardware ports, so projects can be transfered (or backups restored) between computers running different hardware and backups.
* Don't require session handling library to be used. There is no need of such library for restoring connections between JACK clients.
* Flow canvas based GUI. Positions of elements on the canvas are saved/restored.
* Allow clients to use external storage to save its state. This includes storing internal state to non-filesystem place like memory of a hardware synth. This also includes storing client internal state (client project data) in a way that is not directly bound to ladish project.
* Import/export operations, as opposed to save/load. Save/load operate in current system and may cause saving data outside of project itself (external storage). Import/export uses/produces "tarball" suitable for transferring session data over network to other computer or storing it in a backup archive.
* Hierarchical or tag-based organization of projects.
* List of JACK applications. Applications are always started through ladish to have restored runtime environment closer to one existed before project save.
* Distributed studio - network connected computers. Netjack configuration is part of the studio and thus is saved/restored.
* Collaborate with the X11 window manager so window properties like window position, virtual desktop and screen (multimonitor) are saved/restored.