Test for 1.7

Forums

I’m starting a new thread; the other one was getting too full.

Note:
I’ve been running some tests, and the situation—now that an editor is available—has changed completely... it’s wild.
Having an editor was truly necessary.

For instance:
1_ You can now load a "loop sample" and edit it (trimming, reversing, inserting silences by lowering the gain, etc.).
2_ You create a loop clips.
3_ You unlink it (though that part isn't working yet) and adjust the pitch.
4_ Then, a new loop clips.

For a break, you take the original loop and create a variation by editing in silences or repetitions using the editor.
In just a few minutes, you can quickly build an interesting and complete soundscape.

It’s especially useful for urban music, electronic dance music, and other genres built around loops.

However, there is no warning when performing operations directly on the clip.

I understand that there is no simple solution, as these operations are not performed from memory but by reading the samples from the file.

If the user could at least see the disabled area—both on the clip itself and in the editor—they might realize on their own that a "merge" operation is required first.

Furthermore, by visually indicating the area where operations are disabled, the results would appear consistent.

I suggest using a striped pattern...

Just an idea.

Thanks, but it would also be necessary in the clip...

That’s actually where it feels most jarring in a situation like this.
You apply an effect, but visually, the result only covers half the space—what happened?
If there’s a visual indicator showing where the audio ends, it becomes much easier to understand, and the user will intuitively perform a "merge" before applying the effect... and then they’ll see that the full duration is available for the effect to be applied.

Permalink

I have already set out everything that, in my view, should be improved.

Thanks for everything.

Permalink

I believe we've already reached a milestone on this coming v1.7.x business...

now please, focus on bug spotting and squashing and only.

please abstain to ask on any--the smaller they can be--new features or options.

hyu.
cheers

Permalink

but it would also be necessary in the clip...

you mean on the main tracks view? but there's no compelling need for just that imo.

while on the new audio clip editor it surely helps to mark a non-editable zone, on the main arrangement view it's not quite or at all necessary for such markings: a flat line means silence and that is obviously what you get down the stream to all DSP processing and rendered when merging and/or exporting: a plain flat-zero signal aka. silence :)

hyu.
cheers

"it's not quite or at all necessary"

It is necessary...

If there were a visual indicator, such as a highlighted strip, marking the disabled area, that would align with expected behavior, and the user could handle it in various ways: either by performing a merge beforehand, or by simply removing the excess afterward and making adjustments.

As it stands, the user cannot understand what is happening because Qtractor provides no reference to indicate it.

The initial impression is that it’s a bug.
If a user sees an area, they assume it’s available for editing, it’s as simple as that. If an area is not editable, Qtractor needs to make that clear.

Another way to avoid it being perceived as a bug would be to allow editing in that area, though I suspect that would be significantly more complex to implement.

File attachments

It seems to be completely resolved.
I haven’t been able to cause the handles to disappear; they consistently show the same position in both the clip and the editor.

Thanks!

PS
One thing remains:
If the user doesn’t save the session, any audio files generated during editing will end up in undesirable locations.

However, this isn’t critical, so I assume it can wait.

It works better than I expected...
I was worried that it might just perform a simple import, which I would have accepted, as it’s still better than having files scattered everywhere. But this solution is ideal.

I just remembered one other thing that could potentially cause issues.

If we copy samples between audio clips and the channel counts don’t match, undesirable things happen.

If going from fewer channels to more... well, the result is undesirable, but not critical.
If going from more channels to fewer, however, Qtractor will crash.

Is it possible for the paste process to check the channel count in memory and adapt it to the destination?

For now, this is more than sufficient; it avoids issues when pasting content between clips with mismatched channels.

In the future, it might be worth adapting the paste function (similar to how tracks handle data—duplicating or omitting information—depending on whether the buses have a different number of channels).
Another option would be to add a channel-conversion tool to the existing set of tools... though the first approach makes more sense.

This is all assuming you see a clear benefit to it, of course...

It feels like it’s ready for release.

Fireworks!!!

Add new comment

The content of this field is kept private and will not be shown publicly.

Markdown

  • Parses markdown and converts it to HTML.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id> <img src alt height width> <strike> <pre> <p> <br>
  • Lines and paragraphs break automatically.

Filtered HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <b> <i> <pre> <img src alt height width> <strike>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
File attachments
Unlimited number of files can be uploaded to this field.
2 MB limit.
Allowed types: jpg jpeg gif png txt doc docx xls xlsx pdf ppt pps odt ods odp zip gz bz2 xz patch diff wav ogg flac ogv mp4 qtz.