Replies: 2 comments
|
I think what you're asking for is a timeline that adapts when things get deleted from it, kind of like how you describe Audacity working. LosslessCut works differently in that you don't delete anything from the timeline, you just define segments to export. See #976
This is already how losslesscut works, you can define segments seg1 start-end and seg2 start-end etc, and export them.
This can be done by holding down the shift-key while dragging the start/end of a segment.
Zoom in/out on the timeline is already possible
not sure what that means
With all due respect if it was easy to use audacity's UI in LosslessCut, then you can probably just ask an AI like claude code to implement it for you in a fork of losslesscut with a few days of vibe coding :) Possibly related: #2892 |
|
Thank you, Mr. Finstad for replying to my observations. I hope that you are conversant with Audacity's keyword Frame. One frame represents one Sample (of the sampling rate). Your humour:
is accepted & appreciated. Hope it wasn't intended as a satire. But my observation could be better rephrased: Couldn't have LosslessCut been incorporated as a tool into Audacity, using its interface, for audio-only editing? That would have reduced your programming load a great deal. Audacity doesn't have Cut-Edit tool without re-encoding, which causes files to bloat up post-editing. Intuitively, your program, the audio cut-edit part, could have been incorporated as a tool within Audacity, it seems. I was considering the other way round, using LosslessCut audio section into Audacity, not having Audacity in LosslessCut.
Yes, checked the option. The Cntrl+Mouse scroll wheel on the timeline does the trick. Not activated by default. Perhaps to reduce undue processing. Thank you for dropping the hint. Observation of a Lacuna: A visual instruction Manual would have been a welcome addition. I am currently reading the Usage: Typical workflow. Thank you for creating this manual. A question: What does "seek back/forth" in your file, Usage: Typical workflow, mean? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I needed this application for the specific function intended.
Clue:
Audacity suffers from a drawback: every cycle of file-open,-edit,-save bloats up a file unlike the same with ffmpeg
The moot function of the application is Cutting-Saving audio sections from original files.
The wave interface of Audacity could have been incorporated to specifically select sections. In & Out. Or multiple clips of an audio track. Like:
Start1 to End1
Start2 to End2
& so on, … & to use mouse to select the sections to be cut.
Zoom In or Out of the wavetable interface like frames, using
scroll buttonsMouse's Scroll Wheel.Or remove specific sections using mouse selections, then the Delete Buttons to remove those sections, listen to the edited audio. Then save the edited file.
Audacity being a FOSS, the source code could have been used & important portions, replicated. Audacity doesn't have this facility to cut without decoding & re-encoding. This slot is perfectly fixed by the other software, like LosslessCut, mp3splt-gtk, etc. The audacity interface could have easily been used.
Alas!
It is as if the programmers got lost in the wilderness in the midst of creating the software.
The objective was partially lost, it seems.
I want to use an empowered, well-planned software & be empowered. I am not a critique, so far as destructive criticism is concerned.
I would like to observe the product improving, thus improving my objectives/outcomes.
All reactions