View Single Post
Old 09-29-2019, 02:40 AM   #9
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

I am really glad you improved this! Previous issue with slices being ignored instead of merged is now gone.

There are still some minor issues and improvements to be done:

glitch under this text (Win7)


----------
use "Remove silent areas"
Problem: the very first slice before the first gate opening is not removed
Expected: it should be removed because it does not meet the gate threshold

----------
set Leading or Trailing pad to a negative value
set Fade pad on
Problem: the fade is not created.
Expected: item edges are not moved and a fade is created in a length of a particular leading/trailing pad.

----------
move cursor in the Gate frame (Win7)
Problem: the help text at the bottom of the window flickers


----------
FR: add presets
reason: one time I want to split drums to hits, the other time I want to remove silences from voice, currently I need to readjust all parameters each time for each different task


----------
texts: some texts seems unpolished and neglected, also in relation to the overall nomenclature

"Min slice length:"[/B] and [B]"Min silence"
->either "Min. slice:", "Min. silence:" (notice dots and colons)
->or "Min. slice length:", "Min. silence length:"
->or "Min. slice len.:", "Min. silence len.:"
->or "Slice limit:", "Silence limit:"

"Gate threshold"
-> "Threshold"
("Gate" is already in the frame name, will match "Hysteresis")

"Write stretch markers to selected items"
-> "Add stretch markers to selected items"
(you use "Add" in other places; in the action list)

"Write stretch markers to selected items and add to grouped items"
-> "Add stretch markers to selected and grouped items"
(there is no difference between writing and adding here)

"Add transient guide markers to items"
-> "Add transient guides to selected items"
(you use "Transient guides" elswhere in the program; make clear it is now only to selected items)

"Set new items forced to beat timebase"
->"Set items timebase to beats (position only)"
(much more clearer, much less thinking needed, same as used in the action list)

"Auto-adjust snap offset to peak value within first:"
->"Set snap offset to peak value within first:"
(clearer, same as used in the action list)


----------
UI:

transient threshold:
add controls for transients to the main dynamic split window (makes it much faster to set, gate threshold is already there)
controls to add: sensitivity, threshold, zero-crossing, display threshold in items
remove button "Set transient sensitivity"


gate:
add option to display gate threshold in media items, both for threshold and hysteresis, similarly to how transient threshold is displayed

(note: there could be just one checkbox to toggle display of threshold in items both of transients and gate)


order of frames/controls within the window to mirror workflow:
1 - choose split points (transient, gates)
2 - set transient sensitivity
3 - set gate sensitivity
4 - tweak splits, silences
5 - set action to perform


All this would make using this tool much more bio-CPU-efficient, while those saved brain-cycles could be used on the music itself.
bFooz is online now   Reply With Quote