Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
aj [2015/06/02 04:35]
slackermedia created
aj [2021/06/03 19:48] (current)
Line 1: Line 1:
-[[{arrowp.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​position:​absolute;​top:​0;​left:​0;​}slackbuilds|]] 
  
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​position:​absolute;​top:​0;​margin-left:​2.5em;​}ardour|]] 
  
 ====== AJ-Snapshot ====== ====== AJ-Snapshot ======
  
-[[http://​aj-snapshot.sourceforge.net|Aj-snapshot]] is the simplest-possible ​session ​logger for JACK.+[[http://​aj-snapshot.sourceforge.net|Aj-snapshot]] is the simplest-possible ​connection ​logger for ALSA and JACK.
  
 <WRAP notice prewrap 50%> <WRAP notice prewrap 50%>
Line 42: Line 40:
  
 The solution is //session management//,​ and there are several approaches. As usual with Slackermedia,​ you should find the solution that works best for you; aj-snapshot is only one option of many. The solution is //session management//,​ and there are several approaches. As usual with Slackermedia,​ you should find the solution that works best for you; aj-snapshot is only one option of many.
 +
 +Aj-snapshot is not so much a session manager as it is a connection manager, which is part of session management. If you enjoy the modular approach to multimedia, then you may find that using aj-snapshot along with careful and deliberate file management is all the //session management//​ you need.
  
  
Line 53: Line 53:
 Aj-snapshot is not a tool you use early in your work, since it's basically useless until you have something to take a snapshot of. Once you have configured a rig that you like, then take a moment to take a snapshot of your routing setup: Aj-snapshot is not a tool you use early in your work, since it's basically useless until you have something to take a snapshot of. Once you have configured a rig that you like, then take a moment to take a snapshot of your routing setup:
  
-<​code ​bash+<​code>​ 
-$ aj-snapshot ​rig.aj+$ aj-snapshot ​foo.aj
 </​code>​ </​code>​
  
-where ''​rig.aj''​ is the filename that will be created for the snapshot. This file can be stored any where, and it's up to you how to organise your files; Slackermedia recommends storing your snapshots with your music project files.+where ''​foo.aj''​ is the filename that will be created for the snapshot. This file can be stored any where, and it's up to you how to organise your files; Slackermedia recommends storing your snapshots with your music project files.
  
 If a file with the same name exists in the destination directory, aj-snapshot offers to overwrite it. Force aj-snapshot to overwrite existing files with the ''​-f''​ (''​--force''​) option. If a file with the same name exists in the destination directory, aj-snapshot offers to overwrite it. Force aj-snapshot to overwrite existing files with the ''​-f''​ (''​--force''​) option.
Line 67: Line 67:
 When you need to resume work on a project, you should start JACK, any graphical JACK frontend that you use (such as [[patchage|Patchage]] or [[qjackctl|QJackCtl]]),​ your DAW, and any applications you are using external of your DAW (stand-alone synths and effects), and then run aj-snapshot:​ When you need to resume work on a project, you should start JACK, any graphical JACK frontend that you use (such as [[patchage|Patchage]] or [[qjackctl|QJackCtl]]),​ your DAW, and any applications you are using external of your DAW (stand-alone synths and effects), and then run aj-snapshot:​
  
-<​code ​bash+<​code>​ 
-$ aj-snapshot --restore ​rig.aj+$ aj-snapshot --restore ​foo.aj
 </​code>​ </​code>​
  
Line 75: Line 75:
 When you restore connections with aj-snapshot,​ the default behaviour is to //leave all existing connections untouched// and to add the connections from the snapshot file on top of those. If you want to restore the exact state of the system, you must tell aj-snapshot to remove all existing connections before doing the restore: When you restore connections with aj-snapshot,​ the default behaviour is to //leave all existing connections untouched// and to add the connections from the snapshot file on top of those. If you want to restore the exact state of the system, you must tell aj-snapshot to remove all existing connections before doing the restore:
  
-<​code ​bash+<​code>​ 
-$ aj-snapshot --remove --restore ​rig.aj+$ aj-snapshot --remove --restore ​foo.aj
 </​code>​ </​code>​
  
 You can use ''​--remove''​ (''​-x''​) to remove all existing connections without any further action. You can use ''​--remove''​ (''​-x''​) to remove all existing connections without any further action.
  
-<​code ​bash>+<​code>​
 $ aj-snapshot -x $ aj-snapshot -x
 </​code>​ </​code>​
- 
  
 =====Things Not Logged by Aj-Snapshot===== =====Things Not Logged by Aj-Snapshot=====
  
 +Aj-snapshot only takes a snapshot of Alsa and Jack connections (hence its name, AJ Snapshot). This means that aj-snapshot affectively knows where all the virtual cables and plugs are going, but it knows nothing about the virtual devices on either end of those cables.
  
 +If you connect **zynaddsubfx**,​ loaded with the **Space Oberpad** patch, to an **Calf** reverb unit set to **Tunnel**, and then to Muse for recording, the all aj-snapshot knows is: ''​zynaddsubfx -> Calf -> Muse''​. It knows nothing, as you can see, about the synth patch loaded into the synth, the type of effect in the Calf rack, or the profile loaded into that effect in the Calf rack. That could change the sound of your music pretty thoroughly, so it's important to understand that aj-snapshot is a connection manager, not a true session manager.
  
 +To keep track of the state of your synths and effects, you must save setting or session files (different applications will call them by different names) per application,​ per song. Furthermore,​ if you design your own sounds or effects, you may also need to save those as personal banks.
  
 +This produces a lot of files containing a lot of important information,​ and if you choose to live your artistic life this way (and there are many reasons that you may want to), without an all-in-one DAW to keep track of all of this for you, you //must// devise a clear and consistent method of keeping all of this data for each composition distinct and safe.
 +
 +For more information on project management, read about Slackermedia'​s [[planter|Planter]] file system tool.
  
 <WRAP tip> <WRAP tip>
 **See Also** \\ **See Also** \\
-QJackCtl \\ +[[qjackctl|QJackCtl]] \\ 
-Non \\ +[[non|Non]] \\ 
-JACK \\ +[[jack|JACK]] \\ 
-Cadence+[[http://​kxstudio.sourceforge.net/​Applications:​Cadence|Cadence]] 
 +</​WRAP>​ 
 + 
 +<WRAP centeralign>​ 
 +<wrap fa>​[[abcde|R]]</​wrap>​ <wrap fa>​[[start|S]]</​wrap>​ <wrap fa>​[[ardour|Q]]</​wrap>​
 </​WRAP>​ </​WRAP>​
  
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​float:​right;​}ardour|]][[{arrowp.png|border:​0;​background:​none;​width:​0;​float:​right;​}slackbuilds|]]