macros and sessionview

3 posts / 0 new
Last post
whitelight's picture
Joined: June 3, 2010

I mean little knobs that control more than one knob.
-Besides the metasurface and assignable in the same way and place
+different control for live (for values like the sustain of the bassline), hardwired for complex projects instead of changeable midi assignments

-The same window (divisible)
+optical feedback over the whole project in a livesession, usable with a tablet PC.

-Automateable (or recordable) for CD
+(instead of many automations with no global sense), or control it with midi assignments

-with grafic tools (form groups, lable them)

The same window(!): overview over the project;
-timeline snapshots(see discussion "Automation presets")
-container snapshots
-individual snapshots (choose "automate by project" or "automate for live")
-a little timeline, where you can drag and drop timeline snapshots in a relative length (you can decide live: press snapshots in the overview to play them next or drag it in the timeline to play them were you want)=>
This allows a technique for live patching, as the timeline playes only the draged snapshotes and is looping. Dragging out (deleting) is important then

whitelight's picture
Joined: June 3, 2010

This idea maybe solve the problem that you have no long automation-line with "automation presets" le_kzgl this forum;

A main line for automation that function like stone carver handles a stone. (its good for live and CD)
Every automationlane that is in there is endless. You first set your interval, the first automationpoint and the "last" to set the main form (slope). The interval is automatically marked and if you press on a copybutton it is pasted endlessly.
(If you make an automation-point outside, instead, the whole interval is marked (1st to 3rd)and you have a rise and a fall or the other way round.)
If the next point is between two (of them), then, the interval from the front one to the set one is marked. You can copy the interval or let the point alone. BUT: the copies uses the slope in relation to the maximum or minimum and are pasted in the higher interval until its end.
If you do not copy, but put the next point after the former it is the same as in big: you can put in in rises and falls.
The figures that grow are copied in every related copy, means:
The big interval, that was copied, carried over all points to its "kids",
the little one do the same with the points in its copies.

So: if you want normal points, do not copy.
Mulch remembers in my suggestion the first "multiplications", label the points after their succession and relation, and repeat what you do in their related , but all to the main slope of the higher interval.
If you want to copy and paste normal:
Thats the normal button in the main window, no repeat, no slope.

One trick is that you can adjust all main points afterwards: if you have marked an new interval (multiple related together), you can create a higher slope,
If not, all related are changed synchronically.
If one is marked only its slope is changed.
BUT: No "multiplication", so there is no new assignment.

Until yet: I don't know if this is logically said or if the whole idea is not logical, so say, what is good or if something is good

whitelight's picture
Joined: June 3, 2010

I make up my mind what could be further useful for live usage:

1.Timeline snapshots are more effektive, when they have different automations. Example; you want to rise noise in one snapshot, but you´ve wanted it do it by yourself, ´cause the snapshot loops and you have put the noises volume to a controller. You decide when the rise is breaking into the next part. But in the next part the noise should be at zero. Now the trick: You automate your noise-gain in the first timeline-snapshot with a makro in the following with a automationlane.

This example shows one problem. The controller is able to contoll more than one thing over time, But it jumps not to zero if the next value should be zero. A solution is that audiomulch stays at the value of interest until you "catch" this exact value with your controller, so you push it down for zero. Until then you can control the value. Maybe such a "catch" value should be define for every snapshot generally. So if the controller should keep the noise as its parameter, the "catch" value should be zero in the next snapshot. There must be a possibility to have no "catch" value.

To change automation you must first unautomate the parameter, because when you create a new snapshot what is automated is kept, for a better workflow.

2. It was mentioned above that a snapshot can loop for a rise. Maybe you can do this, Ross, by one sort of looppoints that we can place in the general sessionview,more than one pair and activate/ deactivate it per one midi button, and one pair looppoints per snapshot, which you can controll per another button