Rusty, can a Part to Scene be done? Or Page to Scene?
It should be a feature of the machine, this way we could tweak until having something nice and then don´t have to dial each parameter one by one with the scene button held.
Rusty, can a Part to Scene be done? Or Page to Scene?
It should be a feature of the machine, this way we could tweak until having something nice and then don´t have to dial each parameter one by one with the scene button held.
Epic reply Rusty
I’ll buy anything you make if I find use for it and my economical situation allows it.
Carry on.
Peace
That. Overlap or not.
Would be v cool. I’m often pulling a few slices out of a long file and these files have to be loaded into flexs because of the clicky problems on statics. Means eventually doing some fiddly admin to free up memory. This feature would make the housekeeping easier
@mokomo wrote:
Feature: a python script that converts an OT/OE project file into an Ableton Project that plays just like on the OT and can be edited in Ableton (within strict constraints) … a python script that converts that Ableton Project back into an OT project
@rusty wrote:
That is not going to happen I’m afraid. Would rather be working on my own DAW / hardware.
In the below post, I explain how to print OT stems to Ableton. AFAICT, it’s the best you can do in Ableton. In my testing, it works great. There are a couple limitations, which I noted in the post. I imagine any sort of Ableton scripting would need to overcome these limitations, if possible.
Anything better will require @Rusty’s DAW thing.
Limitations
Yes. There is a couple of functions:
On a Part/Scene/Scene Track level; not individual pages; that is only six parameters.
Chainer operates on it’s own internal file format / structure; that fully handles Octatrack samples/slices.
So you can [ Import ] an existing Octatrack sample/sliced file; which will split into separate audio files based on the slices, then rebuild from those slices.
Tuesday
Don’t think it’s a joke, just a different product
It will be Tuesday for sure!
Would be awesome if there was trial version of the software!
Post v2 release, will be looking at providing a demo with limited functionality.
The tricky thing is to find the balance between allowing the flexibility and usage to allow the demo to provide/show the capabilities; whilst also restricting it in such a way that also ensures that the demo, is, well, just that, a demo.
What about a choice at startup that only allows 3 modules at a time to be unlocked or something?
Analytics, Options and Support
Just the fun ones huh? :-)
That would not be possible / viable.
Ryan: “I’ve got a feature request. I want a happy and peaceful life for Rusty”
@Rusty: “do you or do you not want v2?”
Great, and this can´t be done within the machine, can it?