How Audio tracks are displayed, can it be improved?
Just posting a few thoughts and wondering if anyone else has noticed this or feels the same way..
Something about Cinelerra (of all types) that has always really bothered me is the handling of Audio tracks.. It is not my intention to be critical of anyone's work these are observations not judgements.
- Why do the waveform tracks have to be so large and take up so much screen space? If you look at other NLE's one of the major things that really makes Cinelerra's unconventional UI look 'ugly' and outdated is the sheer size, number and visual bulk of the Audio tracks in the timeline view.
- Why can't the vertical size of Audio tracks be independently sized apart from Video tracks, often when actively working on multiple Video tracks it would be nice to make Audio tracks much much smaller to get them out of the usable screen space.
- Why aren't stereo tracks just one visual 'lane' on the timeline with 2 waveforms in one lane? I've never seen any other application that displays true stereo tracks as individual mono tracks..
- How often do people ever need to independently edit each track of a stereo track? to me splitting a stereo track into 2 mono waveforms should be a rarely needed menu option instead of how Cinelerra displays by default.
- Almost every other NLE I've tried puts mono or stereo Audio tracks in one lane of the timeline and Audio effects are applied to one or both Audio tracks with one visual instance of the plugin, no need to attach a plugin to one channel of the stereo track and then apply a copy of the plugin other to the other channel.. Audio tracks in an NLE should really behave like Audio tracks do in any other Audio application like a DAW. For instance in something like Ardour or Audacity 99% of plugins are stereo and the pin connections of how many channels to process are invisible to the user, if you have a stereo track and you apply a stereo plugin the right and left 'pins' are automatically routed, if you drop a stereo plugin on a mono track then it will just connect one side or the other. Since Cinelerra now has the amazing and (very unique in the NLE world) feature to process with LV2 plugins it would be nice if it behaved like virtually every other host of Audio plugins and just let you apply one visual instance of the plugin and let the application invisibly handle the pin routing and automatically apply the effect processing to however many channels are in the 'lane'
I'm sure like many things simplifying how Cinelerra works with Audio visually will conversely be tortuous on the coding side of things so maybe this isn't feasible to even look into. I truly believe that both visually and operationally Cinelerra's very unorthodox handling and displaying of Audio is a stumbling block to it's adoption by new users. Cinelerra doesn't need to be Lightworks, or Vegas or Kdenlive but there is an industry accepted way that Audio is presented in an NLE and if the coding side isn't impossible I think aligning Cinelerra to a more normal workflow for Audio would be very beneficial..
Just my thoughts, Stay safe and stay healthy everyone!
Wow, this is a lot to think about! All I can say is that "why can't the vertical size of Audio tracks be independently sized apart from Video"? might be easily programmed.
As a visual example here is a screenshot I took that is on my website for AV Linux, this is Cinelerra on two 1920x1200 monitors and I'm still cramped for space in the timeline window, the display of Audio waveforms is eating up more than 66% of the visual space! For me this example is a pretty simple project, often I have 5-10 Audio/Video tracks, If I didn't have a dual-head setup and was using a laptop I honestly don't think I could use Cinelerra for making music videos..
Hello Glen... and fellow Canadian.
I agree with you, the soundtracks take up too much vertical space. In my case I use three 1920x1080 monitors and in the case of this project with four cameras and mixers. It is only by folding all the sound tracks into lines except the one used at each moment that I can display and visualize all my tracks that are useful for editing.
Well, GG agrees that it has inconvenienced him too. I have scheduled him to look at this next after he finishes up BT 71 Videoscope improvements.
Started discussing possible solutions but have nothing concrete yet. One thing is for sure is that we do not want to lose the current methodology so have to come up with an alternative choosable option. Because it is already the 18th, gg does not want to start coding anything this complicated and involved this late in the month, so will plan on starting first thing next month.
Meanwhile, I do not know if you are aware of doing this to temporarily save space for the audio tracks.
1 - go to the View pulldown and uncheck "Show assets" -- this will leave only the title bar showing when you load media for all tracks
2 - in the patchbay to the left of each track, click on the right-facing arrow (on the left side of the patchbay area) of each track that you want to see; for example the video tracks and NOT the audio tracks. The right facing arrow will now be a down-facing arrow.
3 - at any time you can click the down arrow to not see that track except the title OR at any time you can click the right-facing arrow to see that track again. Note that when you add a plugin or perform certain operations, the track is automatically expanded to see everything, but you can easily turn it on and off.
I definitely support Glen's views on this 110%, but I am another user coming at it from a DAW workflow perspective. Having to worry about accidentally losing sync between channels of a pair of mono channels (and also manually arming and disarming two channels for what my brain instinctively considers one audio stream) is a constant frustration to me.
I would also again suggest that a breakable 'lock to channel x' feature would be a godsend. cinelerra has come an INCREDIBLY long way over the last several months, but any major editing operations i perform leave me still fraught with terror at the possibility that I have forgotten to arm or disarm something. I still routinely break sessions and have to throw away hours of work because of this.
Thanks for additional feedback -- it helps for us to get perspective and reasoning behind user requests. But I got to say if you really want to feel "fraught with terror" start looking at the audio timeline program code that has been in place for 20 years and think about changing it to meet current expectations. That is what GG says is really scary!! But he is going to try to come up with something new anyway.
As mentioned elsewhere, we run this website, its infrastructure and developments on a voluntary basis and pay for this project out of our own pocket. The honorary character of this project shall remain, we are not looking for profit. We live the open source and free software idea.
Nevertheless, many people have expressed the wish to support us and we don't want to deny this any longer. For this reason I am setting up a donation page this weekend, so that everyone who wishes to do so can make a contribution and support us. If we can get a pizza and maybe occasionally a small beer together with the donations, then we are happy about it and will enjoy it on weekends when the server and the related services are maintained and new content is created.
I think that groups should not be present by default in the timeline space (as a kind of reserved area) but rather be able to be created, as needed and at will, to join as groups the sound and image tracks that we prefer to see associated in this way on the timeline. These grouped tracks could cohabit on the timeline with other non-grouped tracks.
Ideally, it should also be possible to de-group tracks during the editing process to make them independent if it is realized that this would be more practical for the rest of the editing process.
Just a quick note that a new feature has been added to provide a DAW-like capability for stereo/multiple audio tracks. It has been discussed in the Bug Tracker/Feature Request and the mailing list but I was not sure if you read those. Anyway, it has been only minimally tested and a less than 2 page document is temporarily at:
In that same testing directory, are static tar builds for Debian 10, Mint 18, and Mint 19.