Let's Talk
Posted: Fri Jan 14, 2011 9:33 am
If you are experiencing any issues or have any suggestions for the beta version of Har-Bal 3.0, please feel free to post them here.
Cheers
Earle
Cheers
Earle
The Official Har-Bal Forum
https://www.har-bal.com/ipw-web/bulletin/bb/
https://www.har-bal.com/ipw-web/bulletin/bb/viewtopic.php?t=1073
I don't understand the point of moving the reference.yodonsen wrote:Hi
1. Double arrow in main window for moving the traces up and down is a very welcome addition, would be nice to be able to do the same for the reference traces if necessary![]()
Can you give more detail on how you expect it to work with right mouse clicks?1. Biggest problem for me is a lack of right click functionality. You should be able to delete and create splits and copy filters via a right click menu. Deleting/resetting filters from segments and channels is a bit confusing as it stands. The new filter dialogue isn't clear whether it will delete Left, Right, Mid or Side filters (or all of them) from segments or the Outer filter.
Sliders take up a bit of room but not much different from HB2.3. It's entirely consistent with 2.3 being a carbon copy of it. The room aspect I can accept to an extent though I don't see it as a big issue because you can maximise the screen and it then takes the full screen. At that size I find the graph display decidedly large, and monitors seem to be getting bigger by the day. Not a high priority.2. Sliders on left for vol, gain and air take up a lot of room. They could be smaller and have the option for text box entry for precise values.
Well, I've pointed out my views on this many times. What many in the audio software game call slick skinned interfaces, I call trash. I actually prefer the software design guideline that says that the UI should adhere to the UI principles of the OS. That is how Har-Bal is written and will continue to be written. It adds no value in my opinion and is a complete distraction on my already stretched development time.3. The actual window for working in appears greatly reduced compared to HarBal 2.3 (largely due to the overviews at the top). The interface could be less cluttered and I think the overviews at the top could take up less room vertically. Also, it still looks very Windows95 (Not the most important concern but people do care about that sort of thing).
Your getting into the territory of future releases. The UI is NOT going to substantially changed for this release.4. Users should be able to name/label the Segments. This should be displayed in the main window, especially useful for knowing whether you are editing a segment filter as opposed to the main "Master" (Outer) filter.
Doesn't need to be that complex. As per above, the grey bar shows the position of the visible timeline in the entire track. You have segment A selected, You want to selected segment B. Click and drag the upper grey box so that it overlays the segment you want to select (you can see that from the segment markers in the upper bar). then click on the lower bar and you've selected your segment. Is two operations that complicated?5. Switching between segments is a pain. As it stands, you have to use the "double arrow" to come out of current segment, it involves too many clicks and too much mouse movement and I felt a bit lost at times. There should be an unzoomed overview at the very top at all times with the splits so you can select between them at will.
A standard waveform view is not presented because Har-Bal is not designed as a wave editor. It isn't part of the design spec and I don't see any reason to make it so. There are dozens of capable audio editing applications out there and if that is what you want to do then you should use one.6. A standard waveform view would be nice to have at the top (as in many Audio Editors). The peak and average trace could be overlaid and it should be there at all times to allow faster selecting / switching between segments. This would make it clearer to see what segment you are working on and for navigating in general. A click and vertical drag (as in ableton live) would work better for zooming in and out to fine tune the splits etc.
I don't understand this. The outer filter is applied in addition to the splits. It is mean't as an overarching filter for the entire track. I can't see why you would ever want to copy the out filter response into a split. Can you explain to me why this would be a good an necessary thing?7. If you create a master "outer" filter first (before making any splits), then you should have the option of applying that master filter to the newly created segments and leaving a new blank outer filter, OR, create the splits with new blank filters and keeping the existing master filter.
Fair point.8. Users should be able to delete segments rather than the splits. Otherwise you can't choose whether the left or right segment adjacent to the split is the filter that is kept after deletion! If the existing behaviour is to be kept, then the user should be able to choose which filter is kept (the one to the left of the split, or to the right).
Again, can you explain why it is "absolutely essential" to be able to copy filters between Left, Right, Mid and Side? I fear you may misunderstand the workings of this. The way I see it you would never want to do this!9. I can't see any way to copy filters between Left, Right, Mid and Side or between segments either. This is absolutely essential, and again should be accessable via a right clicked context menu in the main window.
It's proposed for the future.10. Meters!!! On the far right you could have peak and Average meters all the way up the screen as in most audio editors. You could even use Green and Yello to reinforce the intuitiveness of referring to peak and average.
Good point.11. In the same way you can quickly navigate through the different views using Alt-1, Alt-2 and Alt-3, you should also have shortcuts to toggle through L, R, Mid and Side filters (Freq response views).
You jumped ahead a few versions here. Beta means feature complete - No new features. You've proposed some major features here that are actually already slated.Workflow Improvements from 2.3 that should be implemented in 3:
--------------------------------------------------------------
1. Multiple references and files open at once would be ideal: each track of an album on separate tabs would have been a great improvement and would allow a faster workflow with greater cohesiveness throughout an album mastering project.
2. Plug-in slots on the output would be great for letting users choose their own compressor and/or limiters etc. I think a lot of users want this and it really shouldn't be difficult to implement.
good pointUndesirable behaviour:
----------------------
1. When zooming into the waveform, making an edit resets zoom to global.
The point here is that toggling compression toggles the focus markers on the histogram plot which includes the effect of gain. If we didn't include the limiter gain then the display is not consistent with what you hear. It is a feature, even though a not perfect one.2. Turning off Dynamics turns off the limiter/Gain too. This reduces functionality of the match loudness feature. An option to adjust the gain of the reference instead of the file that is being edited when using the match loudness command would also be good and would largely bypass this limitation.
You don't need to hold down the left mouse button to delete a split. Click on a split (ie, mouse down and mouse up). Note how it displays inverted. That means it's selected. Now press delete and it's gone.3. Selecting splits and moving them seems ok but holding down the left mouse button whilst deleting doesn't work in bootcamp on my macbook. This is something to do with the macbook keyboard having backspace as opposed to delete - in Bootcamp you have to hold down the function key as well as backspace to get a delete command. This is hard to do whilst holding down the mouse button but doesn't work in any case making it impossible for me to delete a split. A right click to select and delete would work better I think. Same goes for the Ctrl-S command for creating splits, a right click and select "create split" would be more intuitive.
H'mmm. Would you not expect that to be the case. You don't get something for nothing.Other observations:
-----------------------
1. Analysis takes considerable longer than previous versions, it would be great to be able to select a folder (say your album of tracks to be mastered (plus another folder of references) that can be analysed as a batch while you go off to make a coffee or whatever![]()
Match loudness takes into account the effect of HB dynamics.2. I'm not sure about the Dynamics tab at all as of yet. I understand how to use the nodes to create a transfer function but have to mentally convert the process into the standard compressor input output graph in my head! I'm sure with more time and experimentation that this way of working could become more natural and intuitive to me thoughThe lack of metering doesn't help and it would seem logical to implement the match loudness function for the effect of compression!
I don't know if you realise but I personally find the whole concept of multiband compression completely screwy. I have no intention of ever implementing it. When the documentation for HB3 is done you'll no doubt see my reasoning.I would have thought that if HarBal was to implement Dynamics control, the best way to do it so would be to integrate it in a multiband fashion (similar to Paul Frindles DSM). When the Peak and Average traces are farther apart there is greater dynamic range and being able to compress in certain ranges to get a more even looking trace would be a great way to adjust dynamics. I'm not sure that wide band compression implemented in this unusual way is going to be easy for many people to grasp.
Computational complexity is the reason it isn't done. It takes quite a bit of re-processing to account for it and it was considered not that important at this point in time. That's not to say it won't ever be implemented but managing multiple segments and accounting for that is complex enough for a software engineer like myself to get ones head around and not make design mistakes. When HB3 is more mature and better understood then it may well be included.The effects of compression isn't represented in the traces and this seems to go against the "giving eyes to the ears" idea behind harbal. It would be far cooler if you could somehow control the effect of compression by either boosting the average trace (whilst leaving the peaks relatively the same), OR, reducing peaks whilst maintaining the average. Of course this would involve having to represent the effects of compression on the traces.
I realise that many hours have gone into the current compression scheme and that there is likely no way that you could or would implement this behaviour at this point. It would be amazing though hey?
Could you elaborate on what that might be ? : - )HarBal wrote:There's quite a few major things left out of this version simply out of lack of time.