Jump to content


Photo

New Tools: Iterative Quantize And Groove Tool


  • Please log in to reply
31 replies to this topic

#26 ffx

ffx

    Guruh Motha Fakka is Levitating and Knows Everything About Renoise Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2852 posts
  • Gender:Not Telling
  • Interests:Renoise Sidechain

Posted 19 August 2016 - 23:24

Update, added at least now note column fx movement... See post above.

 

It still does not move the track fx. So still a note movement which consists of a midi command will result in chaos. I skipped this, because I am not sure how to handle it properly. Let's say there are two note columns, one with a midi command:

    inst               inst      
    |  pan             |  pan 
    |  |  del.         |  |  del.
    |  |  |  note fx   |  |  |       track fx
    |  |  |  |         |  |  |       |
C-4 01 40 90 0000  E-4 01 M1 C0 0000 4000

Groove tool now moves the notes down by 40 ticks:

C-4 01 40 D0 0000  --- -- -- -- ---- 4000   <- destroyed midi command
--- -- -- -- ----  E-4 01 M1 00 0000 0000

In this scenario, should the M1 stay in line 1, without a note, only instr. num? so only stay, 1. if notes still left in line 1 + 2. a midi command was used in pan?

 

Could the devs give me some information/discussion on how to properly handle those cases?  Are you planning to improve the midi command handling anyway? 

 

How do I know which track fx column belongs to the midi command? Is it always the first one?


Edited by ffx, 20 August 2016 - 00:14.


#27 Roppenzo

Roppenzo

    Big Daddy Member

  • Normal Members
  • PipPipPipPipPipPipPip
  • 433 posts
  • Gender:Male
  • Location:Netherlands

Posted 24 February 2017 - 03:06

tried to downgrade this tool to <ApiVersion>3.0</ApiVersion> , but it gives me :

main.lua:467: unknown property or function 'effect_number_value' for an object of type 'NoteColumn'
stack traceback:
[C]: in function '_error'
[string "do..."]:47: in function <[string "do..."]:35>
main.lua:467: in function 'read_values'
main.lua:904: in function 'GrooveTool'
main.lua:5: in function <main.lua:4>



someone can help me?
House Music All Night Long. - Say What?

#28 ffx

ffx

    Guruh Motha Fakka is Levitating and Knows Everything About Renoise Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2852 posts
  • Gender:Not Telling
  • Interests:Renoise Sidechain

Posted 24 February 2017 - 11:50

You need to use the old version for old Renoise, not my modified, since it accesses fx columns, which AFAIK were not available before?



#29 Roppenzo

Roppenzo

    Big Daddy Member

  • Normal Members
  • PipPipPipPipPipPipPip
  • 433 posts
  • Gender:Male
  • Location:Netherlands

Posted 24 February 2017 - 16:42

does not work either :-(
House Music All Night Long. - Say What?

#30 joule

joule

    Guruh Motha Fakka is Levitating and Knows Everything About Renoise Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1412 posts
  • Gender:Not Telling
  • Location:Sweden
  • Interests:music, philosophy, engineering

Posted 16 March 2017 - 11:37

Found this tool now! It's a great concept and implementation, but seems a bit buggy..

 

* Have the tool opened. Enter pattern data. Move sliders. The newly entered pattern data will vanish. Most likely because the tool caches the pattern data in order to 'remember' out of bounds notes on the first line.

* Also there are some quirky GUI behaviors when changing cycle length. No biggie..

* Automatically extracting the groove settings from the selected patterntrack would be more sleek. It seems the tool tries to do that, but when you reopen the gui the groove is applied one more time?

* Also, when trying to extract the groove, use a rounding principle for delay values to determine what the original position (slider) was, instead of just using the line index of the note.

* Doesn't seem to follow the selected track.

 

Further suggestions:

* Load midi as groove template. Parse beat (slice markers) as a groove template.

* Should imo have an option to retain delay values that are already present. (e g, first apply a "timing" groove.. then apply a swing groove, for example)

* Strength slider (multiplier).

 

 

Mind if I have a look?


Edited by joule, 16 March 2017 - 11:56.

  • Roppenzo likes this

#31 ffx

ffx

    Guruh Motha Fakka is Levitating and Knows Everything About Renoise Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2852 posts
  • Gender:Not Telling
  • Interests:Renoise Sidechain

Posted 16 March 2017 - 12:13

Sure, the author of the tool doesn't even answer anymore, it seems...

#32 Roppenzo

Roppenzo

    Big Daddy Member

  • Normal Members
  • PipPipPipPipPipPipPip
  • 433 posts
  • Gender:Male
  • Location:Netherlands

Posted 16 March 2017 - 15:23

Further suggestions:
* Load midi as groove template. Parse beat (slice markers) as a groove template.


that would be awesome!
House Music All Night Long. - Say What?