how export all clip separate with multiple file?
-
- KVRian
- 524 posts since 16 Mar, 2017
If there is a feature change to support this, the most obvious thing to do is to add an "Export each clip as a separate audio file" option to the window that appears when you ask to "Render the selected clip".
The scripting API should really be beefed up a bit. You can get a clip object, but all API calls are against the "Waveform" object?????
Why can't I "clip.renderWithOptions(options...)"??? Or "clip.moveToTrack(track)"???
The scripting API should really be beefed up a bit. You can get a clip object, but all API calls are against the "Waveform" object?????
Why can't I "clip.renderWithOptions(options...)"??? Or "clip.moveToTrack(track)"???
-
- KVRist
- Topic Starter
- 35 posts since 17 Feb, 2019
To clac,
We think that it is a wonderful function.
And it seems that it is cool to create sample packs.
It can be completed without interrupting the recording work every time.
And it will be able to complete the export and editing with W10 which is easy to use interface and operability.
I have tried using Reaper before, but because it was dazzling, we choose W 10.
However, I did not know the export function.
That is what we want of the W10.
We think that it is a wonderful function.
And it seems that it is cool to create sample packs.
It can be completed without interrupting the recording work every time.
And it will be able to complete the export and editing with W10 which is easy to use interface and operability.
I have tried using Reaper before, but because it was dazzling, we choose W 10.
However, I did not know the export function.
That is what we want of the W10.
-
- KVRist
- Topic Starter
- 35 posts since 17 Feb, 2019
To fde101,
exactly. Just having it there seems to be quite a difference.
As for the API, It is an obfuscation as if you are looking for 6pt words from the 100th page of a thick dictionary. ..
And why is not it?
We hope expect export and clip enhancements to be made to the API.
exactly. Just having it there seems to be quite a difference.
As for the API, It is an obfuscation as if you are looking for 6pt words from the 100th page of a thick dictionary. ..
And why is not it?
We hope expect export and clip enhancements to be made to the API.
-
- KVRist
- Topic Starter
- 35 posts since 17 Feb, 2019
Well, contact from support!
We want to think that it was good to say this.
"We will add some improved rendering options to the backlog and hopefully we can add it at some point."
by Tracktion Software Team
We cited this to prevent being misunderstood by our words.
Do not you think this is very nice thing?
We do not know when it will be, but we will gladly bless that it will come.
We want to think that it was good to say this.
"We will add some improved rendering options to the backlog and hopefully we can add it at some point."
by Tracktion Software Team
We cited this to prevent being misunderstood by our words.
Do not you think this is very nice thing?
We do not know when it will be, but we will gladly bless that it will come.
-
- KVRian
- 524 posts since 16 Mar, 2017
ok, this is not perfect, but it might help.
On the Settings tab goto Keyboard Shortcuts and show the script editor using the Show Script Editor button at the bottom. Click Add a new macro at the top of the script editor, name it something like "Separate Clips" and paste the code from the code box below into the editor.
After this, DUPLICATE your edit (select it on the Projects page and click "Create a Copy").
Open the copy of the edit, select one of the tracks, and do a select all (Command + A on the Mac, I would guess Control + A on Windows but not sure).
In the menu, go to Run Script -> User Macros -> Separate Clips (or whatever name you gave it in the script editor).
That should move all of the clips onto separate tracks and to the beginning of the tracks so you can then export them using the "Render each track to a separate file" option.
Again, probably not perfect, but it is something anyway.
On the Settings tab goto Keyboard Shortcuts and show the script editor using the Show Script Editor button at the bottom. Click Add a new macro at the top of the script editor, name it something like "Separate Clips" and paste the code from the code box below into the editor.
After this, DUPLICATE your edit (select it on the Projects page and click "Create a Copy").
Open the copy of the edit, select one of the tracks, and do a select all (Command + A on the Mac, I would guess Control + A on Windows but not sure).
In the menu, go to Run Script -> User Macros -> Separate Clips (or whatever name you gave it in the script editor).
That should move all of the clips onto separate tracks and to the beginning of the tracks so you can then export them using the "Render each track to a separate file" option.
Again, probably not perfect, but it is something anyway.
Code: Select all
// Separate Clips onto Distinct Tracks
// Select the tracks first
var tracks = Tracktion.getSelectedEditElements('track');
Tracktion.showMessage('' + tracks);
for (var i = 0; i < tracks.length; ++i)
{
var track = tracks[i];
var clips = Tracktion.getClipsFromTracks (track);
if (clips.length > 0)
{
Tracktion.deselectAll();
Tracktion.addObjectsToSelection(clips[0]);
Tracktion.moveTransportToStart();
Tracktion.moveStartOfSelectedClipsToCursor();
}
for (var c = 1; c < clips.length; ++c)
{
Tracktion.deselectAll();
Tracktion.addObjectsToSelection(clips[c]);
Tracktion.moveStartOfSelectedClipsToCursor();
Tracktion.cutSelected();
Tracktion.moveTransportToStart();
Tracktion.insertTrack('audio');
Tracktion.paste();
}
}-
- KVRist
- Topic Starter
- 35 posts since 17 Feb, 2019
To fde 101.
You accomplished! congratulation. This is a wonderful macro.
We must apologize for this late reply. we are sorry.
We were busy looking for a place to move.
But we tried this macro and I am moved by all the clips moving!
Anyway, we should report this to the macro thread. to "Compilation of Working Macros"
Do you mind if we report on that topic? of course. We write. It's Mr, Fde 101 made. not we.
Do not you want to be reported?
That's a real wonderful achievement. You accomplished.
You accomplished! congratulation. This is a wonderful macro.
We must apologize for this late reply. we are sorry.
We were busy looking for a place to move.
But we tried this macro and I am moved by all the clips moving!
Anyway, we should report this to the macro thread. to "Compilation of Working Macros"
Do you mind if we report on that topic? of course. We write. It's Mr, Fde 101 made. not we.
Do not you want to be reported?
That's a real wonderful achievement. You accomplished.
-
- KVRist
- Topic Starter
- 35 posts since 17 Feb, 2019
Well, we were investigating whether it could be done from zsh or BASH as another method.
Apparently it seems to be possible by Sox command. We do not know if it will deteriorate.
However, we have created the following syntax as sh.
This is the syntax to cut the recorded sound with silence. No silence is not deleted.
If it detects 0.5 seconds of silence exceeding 1%, it cuts it.
If the length of the sound is decided, you can use the following syntax.
In the specified number of seconds, the example cuts every 5 seconds.
These will automatically attach a sequential number to the name.
We are not familiar with zsh and BASH. This is a script unrelated to Waveform, but it will work just fine anyway.
However, to do with operability and WF, that macro is best.
All clip export of WF 10 will be easy anyway! Bless you.
Apparently it seems to be possible by Sox command. We do not know if it will deteriorate.
However, we have created the following syntax as sh.
Code: Select all
for file in ./*.wav; do; sox $file $file silence -l 0 1 0.5 2% : newfile : restart; done;
If it detects 0.5 seconds of silence exceeding 1%, it cuts it.
If the length of the sound is decided, you can use the following syntax.
Code: Select all
for f in *.wav; do; sox $f $f trim 0 5 : newfile : restart; done
These will automatically attach a sequential number to the name.
We are not familiar with zsh and BASH. This is a script unrelated to Waveform, but it will work just fine anyway.
However, to do with operability and WF, that macro is best.
All clip export of WF 10 will be easy anyway! Bless you.
-
- KVRian
- 524 posts since 16 Mar, 2017
It's not that I really mind it being there, but given that I never checked to see how it behaves when there are folder or submix tracks in the document, I'm hesitant to classify it as a "working macro" without some further testing and possibly refinement.thintrne wrote: Tue Mar 05, 2019 12:27 pm we should report this to the macro thread. to "Compilation of Working Macros"
Do you mind if we report on that topic? of course. We write. It's Mr, Fde 101 made. not we.
Do not you want to be reported?
It does sound like it is working for your use case, however, so glad if that helps.
-
- KVRist
- Topic Starter
- 35 posts since 17 Feb, 2019
We are sorry. indeed. We will quit write topic about this.
We think. It is rude to Mr fde 101 to introduce without confirming it.
However, we were very saved. Thank you very much. It was good to create this topic.
Have a nice day.
We think. It is rude to Mr fde 101 to introduce without confirming it.
However, we were very saved. Thank you very much. It was good to create this topic.
Have a nice day.
