Only for the Initiates (and Grand Masters ofc)

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!

Permalink

1_
Every time an audio file is modified, a new file is created. Is this the intended final behavior?

This will quickly fill up our hard drives in just a single session.

The MIDI editor only creates a new file when strictly necessary, otherwise overwriting changes within the existing file—even though space is not a major concern with MIDI.

I believe audio editing should work the same way.

A new file should only be generated upon the first edit after opening the editor; subsequent edits should simply overwrite the existing file.

The same logic should apply if you close and reopen the editor. While new files might still be created for safety, the total number of files would be reduced exponentially.

2_
When copying and pasting an audio clip (now that an editor is available), the expected behavior, consistent with MIDI, is the creation of linked clips or instances. This would allow for looping, where editing a single sample automatically updates all its instances.

1_ ... Every time an audio file is modified, a new file is created. Is this the intended final behavior?

yes.

The MIDI editor only creates a new file when strictly necessary, otherwise overwriting changes within the existing file—even though space is not a major concern with MIDI.

I believe audio editing should work the same way.

that would be nice, but not feasible I'm afraid.

audio clip files are not kept the in same way as MIDI clips, for which all events are kept in memory, all the time; audio files are not, and never will, should I add, so sorry.

A new file should only be generated upon the first edit after opening the editor; subsequent edits should simply overwrite the existing file.

unfortunately that is not possible

most of all, you need to cope with undo and redo's, so that the only current practical way to go with this is having a complete unique file for each edit change.

that's is the way of how the new audio clip editor works, yes, pretty naive and brute force indeed, but that's what we have here and ain't gonna change so soon.

2_
When copying and pasting an audio clip (now that an editor is available), the expected behavior, consistent with MIDI, is the creation of linked clips or instances. This would allow for looping, where editing a single sample automatically updates all its instances.

well, that might be a thing in the near future, we'll see about that when the dust settles down.

but more importantly, all of this questions boils down to a simple truth of life: don't ever use the new audio clip editor to edit large, or heaven forbids, BIG files although it will be perfectly possible to do so, you will end spoiling trashing disk space, not to tell of your human time while doing so.

hyu.

cheers.

You’ve convinced me.
Considering that we have the split and merge tools available, allowing us to edit only the specific segment needed, the current approach is actually quite efficient.

Thanks for clearing up the doubts :)

Permalink

At the moment a double click (or a shortcut) opens the audio editor. I can then open the old properties dialog.
There's no shortcut for the old properties dialog.

In most cases I want to edit something in the properties dialog. So I'd like to have the reverse thing: double click opens the properties and there I have an icon to open the audio editor.

My proposal:
Add an icon in the audio clip properties to open the audio editor and add a switch in view->options->audio to reverse the logic, i.e. what opens first at double click.

Still to do:
Update the "properties" icon in the editors.
(I assume you're already aware of this, but a quick reminder never hurts! XD)

I find this a very satisfactory solution.
I like that the "edit" button doesn't appear in the main toolbar, since the obvious way to access it is by clicking on the clip. Including it there as well wouldn't add any value.

Thanks a lot, Rui. This is taking on an incredible color.

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.