Forums
I'll leave you this here: current git head has some lurking features, waiting for your kind judgement
but still, the plan goes like this:
- next coming v1.6.5, won't get those whatsoever;
- v1.7.0 will be The One ;)
meanwhile and for what is this all about, you ask?
hint: start build with cmake -DCONFIG_AUDIO_EDITOR=ON.. and maybe you'll get initiated to the cause ;)
wholly cheers!
Clip Edit
Nice. When I double-click on a clip then I get the new audio editor and the clip is displayed with the playhead.
When I press F4 or right-click -> Clip -> Edit then it opens, too, but the window scrollbar is far right.
F4 doesn't always work.
re. Clip Edit - F4
dang!
on the main tracks window, F4 is set for both File>Properties... and Clip>Edit..., dunno since when, prolly long ago, and it's wrong!... :/
now, we have to decide:
what's best for you?
re1. Clip Edit - F4
In the Spanish translation, F2 appears under File > Properties; it seems this may have been the default value in the past.
That should be the shortcut to File > Properties, and F4 for Clip/Edit
The audio editor is very exciting...
However, it is riddled with bugs.
I think we need to come up with a testing plan if we don’t want to lose our minds.
I would start with the editing actions of selecting and dragging.
1_ If you select and drag backwards... it works. But not forwards. Copy/cut and paste operations (which can achieve the same result) do work correctly.
2_ If you drag the fade-out to the very beginning, the handle (the grab box) disappears. This happens both on the clip itself and within the editor.
re2. Clip Edit - F4...
yes, I do remember that as well, but somehow it got spoiled and just can't remember since when...
let's make a deal--no-orange-skin-guy here whatsoever--and make it File>Properties... F2 back again?
on the other issues that plague the novelty audio clip editor & stuff, yes, bugs galore, and that's the whole purpose of the said initiated announcement here...
thankful you listened
cheers
re3. Clip Edit - F4...
F2 back again?
That makes sense for my; in fact, most languages—with the exception of English—might never have changed and could still be using F2.
...
As for the bugs... I’d prefer not to report any more until those two are fixed, just to keep things separate.
Regarding fade-ins/fade-outs: I wouldn’t include that in the editor; it’s a clip-level function.
If it were to be added, it should be a separate, destructive tool.
In any case, adding such a tool isn’t urgent right now—especially since it can already be handled at the clip level before exporting... at least, that’s how I see it.
Once all the basic editing issues are resolved, would continue, starting with general issues (such as clip refreshing, which doesn’t occur during standard editing) and then addressing each tool individually.
F4 and drag frames
I’ve just seen the fixes for F4.
I realized that my initial assumption—that the behavior I saw on my installation (where it appeared as F2) was due to the language setting—was incorrect; it was actually due to the configuration.
That configuration has been in place for less than a year, so the change happened less than a year ago. I’m just mentioning this out of curiosity.
Regarding drag-and-drop for frames... I’ve noticed that dragging frames is functionally identical to cutting and pasting the selection when you start dragging.
Since the cut-and-paste functions work well, perhaps the drag-and-drop mechanism for frames could simply call those existing methods instead of duplicating the logic.
Just a thought.
re. drag frames...
but they do exactly that!
what exactly are experiencing wrong when drag-moving the selection in-place? having a different result to cut-and-paste? can you elaborate on the difference of the result?
seeya
re. what exactly are experiencing wrong
re2. what exactly are experiencing wrong?...
despite your telling so i don't see anything wrong about that: remember that move-drag is functionally equivalent to cut+paste in immediate succession: you drag-move (=cut) and then drop (=paste); the selection range is simply deleted (cut) before it's inserted on the new location (which is consequentially displaced by the delete).
the fun fact is, if you move-drag a region and drop it exactly before its begging or after its ending, as like shown in your animations, you end up with the very same situation that you had before the move, as if nothing changed; try to move a bit further after (or before) at least longer than the selected region length: then you can say whether if it's wrong or right :)
cheers
This behavior is confusing…
This behavior is confusing and undesirable.
If it worked as you describe, the dragged area should visually disappear from its original location and then reappear in the target area—effectively performing a "cut and paste" operation, where the element lands exactly where it is dropped.
When a selection is dragged, it should disappear from its original position; upon release, it should appear within the boundaries of the rectangle representing it. Clearly, when the waveform is dropped, it does not appear where it is expected to.
The definitive proof that this behavior is incorrect is that it does not function visually—nor in terms of x-coordinates—in the same way as a "cut and paste" operation, even though it should.
When the rectangle (representing the dragged waveform) is released, the waveform is not there. It fails to appear where it is dropped, which is incorrect.
There is no way to justify otherwise; this is an objective fact. My task is to report it.
If you do not consider this a bug, let’s move on to the second report:
When dragging a fade-out to the beginning of a clip—if "snap" is enabled—the grab handle moves outside the clip, where it becomes inaccessible.
re3. what exactly (drag frames...)
I’ve been comparing this behavior with other editors (KWave, interestingly Tenacity/Audacity doesn’t have a drag function), and you were right (once again XD). The logic is correct; what’s incorrect is the graphical representation of the functionality.
The dashed selection rectangle shouldn’t shift until the mouse pointer moves beyond the edges of the blue selection area.
The mouse pointer should appear in the center of the selection—not at the corner—and then move toward the edges.
The dashed area shouldn’t shift until the mouse pointer moves past one of its edges.
That said, my logic was also correct—it was just a different approach.
PS
Getting this functionality to work well from a visual standpoint is complicated—and, clearly, it doesn’t work well right now.
When you factor in "snapping," even if we managed to get it working, the experience would be cumbersome and confusing for the user, as they would need to be able to move elements beyond the...
However, a approach cut/paste drag assisted would work well; it would be simple to implement and would also help simplify the codebase.
I know I’m being annoying. Please understand that I say this out of respect, even if it might not always come across that way.
re. This behavior is confusing…
yes, but not a bug--it's just working as designed.
you may just opt not to use it or press the Esc key, if found inadvertently falling through the rabbit hole ;)
now moving to the next reported issue: latest git head has some mitigation, please check it out.
cheers
Confusion resolved
In case you’re interested:
https://github.com/rncbc/qtractor/pull/547/changes
re. Confusion resolved...
or is it adding even more confusion?
with your proposed change, when moving the selection to after its initial location it seems to have some undesirable results--it inserts at the wrong point imnsho.
furthermore, your pictured examples above are not making anything clear, quite the contrary:(
sorry but thanks anyway.
re1. Confusion resolved...
It simply compensates for the difference.
That is the logic, and it shouldn’t yield an incorrect result.
The logic calculations have not changed.
I need to conduct in-depth listening tests. But visually, the results appear identical to a "cut and paste" approach.
That is what I am trying to show in the video—though without much success, as it is difficult to present clear, understandable graphical examples.
PS
As expected, it also works perfectly in terms of audio.
The rectangle now represents the waveform, whether dragged forwards or backwards, in the same way.
As far as I’m concerned, this is resolved for my; I just wanted to share.
Best regards
dragging fade-out to beginning
If done from the clip, they work in the clip, but break in the editor and vice versa.
re. dragging fade-out to beginning...
oh yes, that may come from having different visual time-scales on the main tracks/clips view and the clip editor views...
due to this difference it might happen for you to bring the fade-out handle to the very beginning on the clip editor and it will fall outside the clip in the main view, becoming partially invisible--on those cases when it becomes totally inaccessible on the main view you'll have to resort back to the clip editor to change it again...
or use the classic clip properties dialog anyway; speaking of which the later can even make the fade-in/out handles totally invisible on both views, provided you take any to the possible extreme (exact clip length); in these cases you can only use the clip properties dialog to change the handles back again into view...
as said, this was simply mitigated, not perfectly solved; also note that you may opt out of this in the first place by turning View > Fade In/Out off on the clip editor menu; your call :)
hth.
re1. dragging fade-out
The curious thing is that before the audio editor, this didn't happen. The truth is that with this fix, it still doesn't happen—not even when accessed from the clip.
Refreshing the clip when effects/tools are applied to it
The clip exhibits inconsistent refresh issues, depending on its size. Sometimes it refreshes correctly, while at other times it only refreshes when the playhead passes over it...
I suspect you’re going to tell me that it’s working as expected—though this behavior doesn’t exactly inspire confidence.
re. Refreshing the clip when effects/tools are applied to it...
no, this is a very different scenario, and taking by its face value is not working as expected.
please do detail as much as you possible can what are those refresh issues you're talking about
thanks
re1. Refreshing
I have deleted the existing configuration (inherited from Qtractor 1.6.4) and generated a new one.
Everything is now working as expected, even with QSS loaded.
I will keep an eye out in case it happens again.
!!! New Clip MIDI/Audio
Now open the project properties. ?¿?¿
Related to the F4 matter.
New Clip Bug affects 1.65
Reminder, since it is an important bug that affects the next version as well.
re. New Clip Bug affects 1.65...
acknowledged
EDIT: wait... you're showing a first call to Clip/New... on a brand new untitled session; on those cases, the Session Properties dialog is rightly shown at first to give it a name.
this has been normal behavior since... ever! (regardless of version or line branch)
only after that, the clip editor is then shown, something that only makes sense for MIDI clips; for audio clips the regular clip properties should be shown instead (and not an empty blank audio clip editor, which is what's been tamed as of now:)).
thanks
Erratic Tool Reverse
When used to reverse, it shortens the sample duration, deletes parts of it, or produces completely erratic results.
Interestingly, this is the most requested feature, and it ought to be the flagship of the new editor.
The other features, by contrast, seem to work well—aside from previously mentioned screen refresh issues in clips.
Separate commands and icons for "Edit Clip" and "Clip Properties
I have always felt there was a slight inconsistency regarding the "Edit Clip" command, as, in the case of audio, it would open "Properties" instead of an editing interface.
These should have always been separate commands.
That is why my "Edit Clip" icon features both a pencil (for editing) and a gear (for properties).
Now, with the audio editor, we find that the "Clip Properties" command is missing from the "Clip" menu.
This new command—along with its own icon—needs to be added.
While the command "Propierties" is available within the editors themselves, it currently uses the "Edit" icon rather than one specifically designed for "Properties".
re. Clip/Properties...
yes, with the new audio clip editor in place, the Clip/Properties... is now accessed through the File/Properties... on the said audio editor main window menu... just like the (old) MIDI clip editor case, if that stands as a sibling case... ;)
there never was a Clip/Properties... option; it just happens that, for audio clips, Clip/Edit... was the entry point for it (and still is on the v1.6.5 line); however, not on this new audio clip editor front line (towards v1.7.0, remember?).
cheers
re1. Clip/Properties...
I know there never was one... but isn't it necessary?
In any case, it’s not a bug, but rather something useful: being able to access properties without having to go through the editor.
Inconsistent selection when changing the zoom
re. Inconsistent selection when changing the zoom...
now that's gross!
but tomorrow will be another day ;)
cheers
Add new comment