Jump to content


Photo
* * * * - 3 votes

Advanced Automation Editor


  • Please log in to reply
30 replies to this topic

#26 joule

joule

    Guruh Motha Fakka is Levitating and Knows Everything About Renoise Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1834 posts
  • Gender:Not Telling

Posted 05 November 2016 - 23:06

Yes. Even though this would be a very slick improvement, perhaps it's worth considering further implications and maybe possible to refine the idea?

 

For example, what about having user definable set of "views", where automation from any track and dsp could be added to a view?

 

renoise.song().automation_views -- table

renoise.song():automation_view(1) -- table

renoise.song():automation_view(1):parameter(x) -> { track_index, device_index, parameter_index } or perhaps "parameter_object"

 

In the GUI this might be implemented in a song wide "Automation views" tab, that might not seem justified, though. The benefit would be to autogenerate views like "all automation in track" or "all reverb automation in song".


Edited by joule, 06 November 2016 - 01:20.


#27 Zer0 Fly

Zer0 Fly

    Guruh Motha Fakka is Levitating and Knows Everything About Renoise Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1256 posts
  • Gender:Not Telling
  • Location:Am Mind
  • Interests:Buddha

Posted 05 November 2016 - 23:24

This is a good ideas, I find it painful to sync 2 or more automation tracks in the current state.

 

Also it is painful to only have that red line indicating playing position...to sync automation graphs with note data, which is an essential task imho.

 

Fun thing is that the red line syncing depends on rotating position 90° to vertical to know your position in pattern. First I thought, a blast it you'll need time to get used, then I tried and it just worked. But it requires a lot of zapping to and fro in a pattern, because I find the easiest sync is with graphical markers, while counting through lines/grids decelerates workflow. So mark note ons/offs of chosen tracks in the automation editor somehow, it should help.

 

I say this, because I would find it useful to have visual representation of chosen automation graphs next to the note data. So...kind of dedicated automation tracks. You just click em, and have them at the bottom, then shift or ctrl click another and it will be above/below, and the graph tracks marked with color.  Please think about this if you ever think about making vertical wavefor view audio tracks, I think this would be somehow related. I repeat, 90° turning in the head sounds strange, but at least for me it works.

 

I think I even once dreamt that this feature was in my renoise, but I can't remember. Probably I woke up and then renoise was back to the normal state. Dreaming is so sad...



#28 Jalex

Jalex

    Big Masta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPip
  • 548 posts
  • Gender:Male

Posted 08 November 2016 - 03:45

Vertical and with individual oscilloscope

Edited by Jalex, 08 November 2016 - 03:47.


#29 Andrey Marchenko

Andrey Marchenko

    Super Advanced Member

  • Normal Members
  • PipPipPipPip
  • 191 posts
  • Gender:Male

Posted 18 November 2016 - 02:43

So yesterday i asked:
 

 

Is it possible that we will see ability to create non-linear automation curves across patterns? I mean now all locked in patterns and across patterns i can draw only straight lines. I know about tools that can generate exponential curves but this is not the same when you create curves by your hands.

 

 

And got official answer about : 

 

Right now, each automation envelope belongs directly to a specific pattern, and is therefore limited by the boundaries of the pattern itself. What you're suggesting would require a major overhaul of the entire automation system, and we have no plans to do that any time soon.

 

 

 

No, no and once again no. Sad. 


Edited by Andrey Marchenko, 18 November 2016 - 02:44.


#30 Raul (ulneiz)

Raul (ulneiz)

    Guruh Motha Fakka is Levitating and Knows Everything About Renoise Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1543 posts
  • Gender:Male
  • Location:Spain

Posted 18 November 2016 - 12:51

So yesterday i asked:
 

 

And got official answer about : 

 

 

 

No, no and once again no. Sad. 

 

I am commenting on this other topic related in some way. It is clear that Renoise "is parked". Possibly add some more feature and error correction. But waiting for them to fix important things of weight, is going to be very arduous and desperate.

 

I am coming to the conclusion that "Renoise 3.1" is considered the best possible by the Renoise Team, and to move forward, it will be a question of changing the bases of the same and programming from scratch. I already mentioned it once: philosophy is doing what is just and necessary to make it work. The best example is the Automation Editor. You can edit, but with just with the minimum, without advanced tools.

 

The Sample Editor was born this way, but it was perfected. It looks like the Automation Editor will still be abandoned, besides other things....


Edited by Raul (ulneiz), 18 November 2016 - 13:10.

:excl: Development of my tools: KangarooX120SamRenderPhraseTouch  |  GT16-Colors (old)

 

:excl: My API wishlist R3.1 (updated 24 July 2017):

Spoiler

 

:excl: My Renoise 3.1 wishlist (updated 26 September 2017):

Spoiler

#31 Ionix

Ionix

    New Member

  • Normal Members
  • Pip
  • 6 posts
  • Gender:Male
  • Location:france
  • Interests:drum'n bass,OST.
    Mechanics,coding,logo design.
    2 wheels

Posted 20 March 2018 - 04:56

"Global Automation" would be great....For a very professional result....

 

 

In my advice,the best place should be in a tab "Global" ,between "mix" and "sampler"

WaveForm audio track could also take place here.

The "zoomable" Global interface could look this:

 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

[1] [2] [4] [4] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x][x] [x] [x]   ->patterns sequence

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\___/\/\/\/\/\/\/\/\/\     ->Curve x  (ObjectType - Object id - [SubObject id] - Parameter id)

...............................................................................................................................................................................................................

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/_________/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\     ->curve 1  (Track - #3 - Flanger - Feedback)

...............................................................................................................................................................................................................

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\      ->curve 2  (Group - #7 - Compressor - Ratio)

...............................................................................................................................................................................................................

/\/\/\/\/\______\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\     ->curve 3  (VSTI - Moog - Filter Cutoff)

----------------------------------------------------------------------------------------------------------------------------------------------------------------------