Blackmagic Forum

I thought I would start a thread for some of the weirdness folks are seeing on the Fairlight page. Hopefully BMD can use this as a guide to correction.

No effects at all? Really?

The navigation shortcuts on the Fairlight page are...odd. I would expect to be able to use the same navigation shortcuts I use on the Edit page. In my case, Arrow Up/Down for clip navigation, and Arrow Left/Right for frame navigation. (We are editing to video, after all.) I can understand the addition of audio specific navigation, but these four basic operations should be present, functioning, and identical to those from the Edit page. One set of shortcuts working across the program.

I am happy to report that the Zoom shortcuts do work across pages.

Sadly, Marker navigation also does not function on the Fairlight page.

The Jump Left/Right commands don't operate as expected. While I can move from clip to clip with the commands, and the clips are 'selected' in the timeline, they're not selected in the Inspector. I would expect this to be so in order to make adjustments to each clip in turn as we quickly move between them. Instead, only the Track is 'selected' in the Inspector.

Track height isn't remembered. I have to keep putting it back where I want it.

Jim Simon wrote:The navigation shortcuts on the Fairlight page are...odd. I would expect to be able to use the same navigation shortcuts I use on the Edit page. In my case, Arrow Up/Down for clip navigation, and Arrow Left/Right for frame navigation. (We are editing to video, after all.) I can understand the addition of audio specific navigation, but these four basic operations should be present, functioning, and identical to those from the Edit page. One set of shortcuts working across the program.

I am happy to report that the Zoom shortcuts do work across pages.

Sadly, Marker navigation also does not function on the Fairlight page.

There are two overall design principles that the BMD team really needs to embrace.

1. Navigation features need to be available and consistent across all Pages as much as possible. For example, Shift -> moves one second forward on the Edit Page but does nothing on the Color Page. And the Fairlight Page is in its own world in terms of navigation and shortcuts, AFAICT.

2. We should be able to do everything with the keyboard. For example, there are a lot of instances where there is no way to tab to the next or previous field in a dialogbox, e.g. the one for creating a new timeline.

As a longtime Media Composer user, I am used to being able to use the keyboard for literally everything. That is the expectation that MC users switching over will have. On a big project, having to reach for the mouse is going to be a deal killer.

And of course I deeply appreciate all of the hard work and attentiveness from the BMD team. You guys are VERY VERY IMPRESSIVE!

I was trying to track down a panning problem, so I went to the Fairlight page.

The first strange thing is that it showed no audio in any of my audio tracks.

As I was hunting around for potentially redundant panning controls, I noticed that the controls in the track header area are all unlabeled and lack ToolTips. I can guess what mute and solo are, but the others? The numeric field can't be typed in, so if you change it, you have to fiddle with the mouse to return it to zero.

Not good, guys. Look at this:



Oh, and a tangential beef about this forum: When I upload a graphic and then press "place inline", that means PLACE IT INLINE. Not at the top of the message. Please fix that too.

Doubleclick the fader knob to reset to zero. Common practice in any DAW. You never mess with the numeric display. Its just there for convenience.

Thanks for the info. But what if you want to enter an exact value, perhaps repeatedly across multiple tracks? It's a text field, so it should function as one.

And let's face it, DAWs suffer from a lot of crappy common practices. Like using a "knob" metaphor in a GUI. Ugh.

PalmerWoodrow wrote:Thanks for the info. But what if you want to enter an exact value, perhaps repeatedly across multiple tracks?

That's where VCAs or Channel Groups would be used (not yet implemented).

The Timeline Track Gain value is merely a useful secondary indicator of Mixer channel fader position.
It is especially useful when the software Mixer is either on a second or third display further away from the operator, or when hidden (i.e. not displayed).

And let's face it, DAWs suffer from a lot of crappy common practices. Like using a "knob" metaphor in a GUI

Disagree.

When using a hardware console, the on-screen virtual knob translates to the action of the physical knob (especially when adjusting the physical knob and referencing in the software Mixer).

When constantly scanning hundreds of tracks in a session, a knob is a much better indicator of relative position than a numerical value believe it or not. The same is true for Pan, much clearer with a graphical representation than a numerical value.

The important part of that statement is "when using a hardware console," which is not a GUI. In that case, you're using a physical interface and the display is just that: a display.

Like many (most?) people, I'm not using a hardware console.

I wasn't suggesting only having a numeric value, though. A slider-style control makes much more sense in a GUI. A circular control is cumbersome to operate with a mouse and cursor.

PalmerWoodrow wrote:A slider-style control makes much more sense in a GUI. A circular control is cumbersome to operate with a mouse and cursor.

Audio Plugins within Resolve, for example, allow parameter adjustment with the mouse hovered over the virtual control (e.g. EQ Band Frequency) and using the mouse scroll wheel.

Perhaps, implementing this functionality application wide (i.e. Clip EQ, Mixer channel fader, Mixer Dynamics Processor, et cetera) would alleviate some of the difficulty in adjusting circular controls via the mouse.

PalmerWoodrow wrote:But what if you want to enter an exact value, perhaps repeatedly across multiple tracks? It's a text field, so it should function as one.

The other option of course is to select the Audio Track and open the Inspector.



You can double click the Gain value and enter a custom value. There is also a handy reset to unity gain button provided.

Alternatively, drag over the Track Gain value while holding the left mouse button, to change the value in 0.20 increments.

Very small mouse movements will adjust in smaller 0.10 increments.

Total noob, so I may just be doing something wrong, but:

To record from an audio device in the Fairlight page.

Patch your audio input device (USB mic in my case) to a timeline track, then arm the timeline track.

Hit record.

Timeline colors red where recording is supposed to take place. Hit stop. However:

Nothing is recorded. Capture folder shows a file one frame long. Timeline shows nothing.

Using Media Composer with the exact same hardware setup, audio records fine. Audio created by Media Composer can be dragged into the media pool and plays fine.

So what am I doing wrong - I've followed the tutorial exactly.

Tony

Glenn Venghaus wrote:You never mess with the numeric display.

I prefer to, myself. Entering values is...more precise.

Reynaud Venter wrote:The other option of course is to select the Audio Track and open the Inspector.

A valid option...for now. But I would argue that in the relatively near future, every text field in the program that reports an adjustable parameter should accept keyboard entry.

Reynaud Venter wrote:Plugins within Resolve, for example, allow parameter adjustment with the mouse hovered over the virtual control (e.g. EQ Band Frequency) and using the mouse scroll wheel.

Which is great. Instead of misrepresenting the control in the GUI as a knob, we need a new standard to communicate the ability to change it with the mouse wheel. I think we have a pretty good standard to tell the user he can click and drag to change it, in the cursor that changes to <-> when you roll over the text field. That's pretty common between different applications.

I mainly object to the incorrect visual indication to the user that he's supposed to drag the cursor around in a circle, with no indication of what the correct way is. Maybe they should keep the circle but make it a display-only graphic that surrounds the text field, so you know not to try to turn it; but it still shows you where the current value resides within the total range. It will reflect the adjustments you make by clicking and dragging, spinning the mouse wheel, or turning the knob on your hardware console.

Glenn Venghaus wrote:Doubleclick the fader knob to reset to zero. Common practice in any DAW. You never mess with the numeric display. I'ts just there for convenience.

I just discovered that one today and I totally agree. You can double-click on the EQ and compressor knobs in order to reset them to unity, but not the faders (at least from what I saw).

I also think wherever there is a numeric display, it should be possible to select that field and type in a number, if you needed to (say) reduce a level by exactly -6dB or something, vs. moving the fader to get 6.21dB.

@marc,

So doublick the fader knob does not work for you ?
Works fine here and thought you where also on a mac so not os related.

The mouse scroll wheel does not work on the Fairlight page in version 14.0.0.078 under Windows 10 Pro.

The Mixer does not show all tracks by default. We have to manually expand it.

Additionally, the Mixer covers up the timeline. This is bad design. The Mixer should 'move' the timeline out of the way, much like the Meters do.

The Mixer meters are set to Pre-Fader. These must be set to Post-Fader. As the only option, or as one option, doesn't matter. But Pre-Fader as the only option is not workable. We already have that in the Meters section. We must have a Post-Fader meter in the Mixer.

So here's another weird thing in Fairlight. Whenever I cut a clip with an audio transition at the end of the clip, Fairlight moves the front half that transition to the new cut point.

The transitions on the Edit page are as they were before the cut. The weirdness only shows on the Fairlight page. But that weirdness does regulate audio behavior.

Steps to reproduce.

1. Add two clips to the timeline.
2. Add an audio transition between them.
3. Make a cut on the first clip.
4. Go to the Fairlight page.

Currently using Studio 14.0.1 on Windows 10 Pro (1703).

Found another bug.

The Increase Audio Level keyboard shortcut does not work on the Fairlight page.

Well, to be precise, the only thing that can be done to a channel without affecting other channel(s) in a track is fade-in/fade-out.

I just encountered a tiny problem, which could be fixed in 12.5 in two seconds: recording to BM Video Assist 4K with one channel fed via XLR and the other via HDMI (yeah, i know, i should have brought two XLR microphones), I ended up with a stereo track with a 0.25 sec time shift between channels. I do not see an obvious way to fix it now, except copying both channels into a new track, selectively disable opposite channels in both tracks and then align the remaining channels. This is madness

The problem in more detail and screenshots are here:

viewtopic.php?f=21&t=66635

In Windows double clicking on the fader in both the Edit and Fairlight pages resets it to unity and the scroll wheel controls plug-in knobs on the Fairlight page, you don't have to "drag the cursor around in a circle". You can also double click on any numeric boxes in a plug-in and enter the value of your choice, all normal DAW practice. As to sliders on plug-ins, many are modeled on real hardware so the knobs are what you expect to see and use. Changing Knobs to sliders would mean all the plug-ins would have to have their GUIs changed. Something that is unlikely to happen. As a Pro Tools user for 23 years, give me knobs any day. I agree with what Reynaud has to say on the matter.

Charles Bennett wrote:scroll wheel controls plug-in knobs on the Fairlight page, you don't have to "drag the cursor around in a circle"

Then why are the depicted that way? As you note:

Charles Bennett wrote:many are modeled on real hardware so the knobs are what you expect to see and use.

And how are real knobs turned? You grasp their perimeter and turn them in a circle. Doing that with a mouse cursor is cumbersome. That's why we need some visual indication to the user of how the mouse can be used to adjust the value. What's the problem with that?

Charles Bennett wrote:Changing Knobs to sliders would mean all the plug-ins would have to have their GUIs changed.

Not necessarily. It depends on the plug-in API. With many, the plug-in doesn't draw the UI; it merely lists the types of controls it needs and the host application draws them. But I didn't say they should all change to sliders anyway. They should just indicate to the user how the mouse is really supposed to be used to adjust the value. If we're not supposed to roll the thing around in a circle, then the control might as well be a circular pie graph with something more informative in the middle.

One could probably argue the merits of either for ever. I see the point you are making though. A lot of the knob preference is historical as many of us come from using consoles where we were used to scanning the knob positions by eye and knew the effect of a certain position. DAWs like Pro Tools copied this form to make the transition to digital for us analogue oldies much easier.

PalmerWoodrow wrote:I was trying to track down a panning problem, so I went to the Fairlight page.

The first strange thing is that it showed no audio in any of my audio tracks.

As I was hunting around for potentially redundant panning controls, I noticed that the controls in the track header area are all unlabeled and lack ToolTips. I can guess what mute and solo are, but the others? The numeric field can't be typed in, so if you change it, you have to fiddle with the mouse to return it to zero.

Not good, guys. Look at this:

Fairlight.png

Oh, and a tangential beef about this forum: When I upload a graphic and then press "place inline", that means PLACE IT INLINE. Not at the top of the message. Please fix that too.

Hi,

"Can't Type in this field"

It's for automation.

BMD is unlikely to want to depart from the industry norm (knobs), but I wish values could be dynamically reduced or increased using the keyboard alone, for example, right/left cursor, rather than fighting the mouse and frequently losing. Same with Resolve sliders, in or out Fairlight.

It would be so much easier, just holding down a repeating key.

Charles Bennett wrote:One could probably argue the merits of either for ever. I see the point you are making though. A lot of the knob preference is historical as many of us come from using consoles

I get it. There's definitely a good medium between the recent fad known as "flat" UI graphics, which offers almost no demarcation of what's a control and what's merely static text or a decoration; and overdone "skeuomorphism," where you have ridiculous photo-realistic depictions of real-world objects that detract from their usability (and often don't make sense). Apple descended into this with asinine "leather" and "felt" textures in their UIs until going way, way too far in the other direction.

Sadly, most GUI controls were nailed in the '90s, but designers have regressed from those standards in a desperate effort to be different. They've forgotten how and why GUIs work. Buttons had simple shadows that indicated whether they were on (depressed) or off (sticking out). Tabbed dialogs were depicted properly, where the selected tab's entire area was shaded and clearly enclosed all the controls that were grouped together; if you want to see a poor and half-assed implementation of tabs, look at Resolve's render panel...

And this could go on and on too...

Jim Simon wrote:Whenever I cut a clip with an audio transition at the end of the clip, Fairlight moves the front half that transition to the new cut point.

This one appears to be corrected in 14.1.

Marc Wielage wrote:You can double-click on the EQ and compressor knobs in order to reset them to unity, but not the faders.

This one also seems to be corrected in 14.1.

Jim Simon wrote:The Mixer meters are set to Pre-Fader. These must be set to Post-Fader.

Thankfully, also fixed in 14.1.

On the Edit page, a single click on a Marker in the Edit Index will move the playhead to that marker.

On the Fairlight page, moving the playhead requires a double-click on the Marker. This needs to change to single click for consistency across pages.

Timeline navigation via numerical entry doesn't work on the Fairlight page. I cannot type a timecode I wish to go to, nor a relative change via + and - entry.

This needs to be addressed for consistency across pages.

The playhead does not Snap on the Fairlight page. (Yes, it's turned on.)

Navigation shortcuts (Next/Previous Frame or Clip) still do not function at all on the Fairlight page. This one's important, guys. JDI.

Resolve Studio 14.2
Windows 10 Pro (1709)

Playback does not stop at the end of the program on the Fairlight page. It just keeps playing, and playing, and playing...

On the Fairlight page, the Submixes appear to the right of the Main mix. That's...odd.

Hardware mixers typically have the individual channel mixes to the left, submixes to the right of those, and the Main farthest to the right. This makes reading the Main output easy, simple, and uniform across devices. It's always the rightmost fader/meter.

Fairlight should follow that paradigm.

On the Fairlight page, Dragging a clip's Fade Handle doesn't give a readout of Duration and +/- change like it does on the Edit page. That's pretty important data to have.

Jim Simon wrote:On the Fairlight page, the Submixes appear to the right of the Main mix. That's...odd.

This is actually how many audio post colleagues also prefer the Mixer layout.

Main Mixes, followed by the various Stems, followed by the various SubMix and finally the FX Busses.

It’s a layout that both I and many of my colleagues feel comfortable with.
In this case, I can’t agree with a change that would alienate the audio users of Resolve.

Reynaud Venter wrote:This is actually how many audio post colleagues also prefer the Mixer layout.

It makes it more difficult to see the Main though. It's gets lost in the jumble.

It's also just not logical. The inputs are on the left, feeding the submixes to the right of those, feeding the Main all the way to the right. It flows, left to right. Logical.

I still think this change is needed. It's a better way.

Jim Simon wrote:It makes it more difficult to see the Main though. It's gets lost in the jumble.

Perhaps reduce the Buss section to only display the Main Busses, with the Meters panel displaying the SubMix and Aux Busses.

There's no indication of clip volume levels when dragging the clip's Volume level on the Fairlight page, as there is on the Edit page.

The Up/Down arrows do not function on the Fairlight page at all.

The Left/Right arrows perform the function of the Up/Down arrows on the Fairlight page (Next/Previous Edit), but that leaves us with no way to Step one frame left or right.