Ripple delete of empty space in TL doesn't move all clips

Note this bug nearly cost me many hours of work in totally trashing a TL. I caught be accident simply flipping between TL's and see it wasn't right.

Please what screen capture here that repro's the problem. watch carefully as not all clips, especially in V2/3 do or don't move. https://www.dropbox.com/s/xi5hh87iykq23 ... t.mov?dl=0

short ver : delete empty space in TL by selecting it, hit Del. it seems only items in V1 where empty space was move to the left, V 2 sort of, V3 no. other items in other tracks stay put.

Beta8, 10.13.6 release.

UPDATE 1: using Option Y select all the the left does NOT select all clips. Only 90% of them. Specifically the clips not getting selected are basic titles that were Option Drag duplicated in TL. I have saved the project and can send that off to whom ever needs it.

screen capture of bug : https://www.dropbox.com/s/r6szxki2cnfu8 ... d.mov?dl=0

S

Neither of these are bugs, both ripple delete and select clips forwards/backwards depend on track auto-select. You have it turned off for the third video track, hence the behaviour exhibited. You should check the manual for anything that seems untoward before labelling it a bug. And then read the thing cover to cover anyway, you'll learn a lot.

before insulting some one, and assuming they have read every page of a 1400 page manual.... I've actually read a good 50% of the manual - please be respectful. Resolve is hardly my first NLE either, I even did a multipart video series on it if you must know. Never mind 20 years UI/UX experience.

that said, if a "feature" operates in a way thats not obvious, not clear, or works in an obtuse way a user can't anticipate, or works in a way that flies in the face of convention, then yes its a bug. not the crashing kind, but one in which expected operation isn't happening.

the button for track selection looks like next / prev keyframe in any other app. I had to RTFM that. who ever would of guessed it ??? less than ideal design. the UI is designed to make the box around the Vx or Ax look and appear to be the track selector. Even still, track selection is a separate operation, a separate indicator that doesn't give up a clue what it does. if anything it misleads the user as to what it may do. realistically this is the _exact_ confusing mess other NLE's suffer from - 2 indicators that aren't clear when they come into play for any particular operation. They should be unified into a SINGLE indicator so there is no guessing.

none the less, the Select All to Right / Left should _ignore_ track selection. it should actually select all. if you don't want something to move, Lock the track, thats what track locks do. Again, this unexpected, unpredictable behavior because of a unclear UI is a bug to fix. R isn't the only NLE to suffer from this.

S

Neither of these are bugs, both ripple delete and select clips forwards/backwards depend on track auto-select. You have it turned off for the third video track, hence the behaviour exhibited. You should check the manual for anything that seems untoward before labelling it a bug. And then read the thing cover to cover anyway, you'll learn a lot.

Is there a bug here as well as perhaps an opportunity to improve the UI/UX? Sounded like there may have been a bug regarding selection of copied titles?

edit - I tried to reproduce the ALT-drag copy of a lower third but did not reproduce what I believe was reported by the OP.

One anomaly (?) that I did notice is that the 'Linked Selection' option seemed to work in the opposite manner to which I would have guessed. If 'Linked Selection' is disabled and you ALT-Y to select clips to the right, it would seem that disabled tracks are ignored, while if 'Linked Selection' is enabled, disabled tracks are respected.

I just tried this with R15 b8 - Had two clips, one on V1/A1 and the other on V2/A2. I disabled both A1 and A2. With 'Linked Selection' enabled, if I ALT-Y then neither audio portion of the clip is selected. If I disable 'Linked Selection' and then ALT-Y then both audio portions are selected (even though the tracks are disabled).

Call me silly, but I would have thought that 'Linked Selection' would have had the effect of forcing the audio to be selected along with the video even if audio tracks were disabled. Either this is a bug or there is something I am missing with this logic. I have not read the manual cover to cover - in fact, I have not read much of the manual so I am presenting this as an observation only.

before insulting some one, and assuming they have read every page of a 1400 page manual.... I've actually read a good 50% of the manual - please be respectful.

I insulted no one. I not only gave you the solution to your problem but I also gave good advice, and in return? Not even a shred of gratitude. I increasingly wonder why I bother, maybe next time I'll just leave you to flounder. And no, I do not assume everyone has read the entire manual, but as I said in my entirely reasonable previous post, it would be a good idea especially if you are doing paid jobs using Resolve. If people take offense at this advice that's their problem not mine.

that said, if a "feature" operates in a way thats not obvious, not clear, or works in an obtuse way a user can't anticipate, or works in a way that flies in the face of convention, then yes its a bug. not the crashing kind, but one in which expected operation isn't happening.

the button for track selection looks like next / prev keyframe in any other app. I had to RTFM that. who ever would of guessed it ???

Anyone with experience of either FCP7, Avid or Premiere. This is not a bug, it's a feature, and besides, the behaviour described would certainly not be classed as 'not obvious, not clear, or working in an obtuse way a user can't anticipate, or in a way that flies in the face of convention' to anyone who has worked with any of those editing packages.

less than ideal design. the UI is designed to make the box around the Vx or Ax look and appear to be the track selector. Even still, track selection is a separate operation, a separate indicator that doesn't give up a clue what it does. if anything it misleads the user as to what it may do. realistically this is the _exact_ confusing mess other NLE's suffer from - 2 indicators that aren't clear when they come into play for any particular operation. They should be unified into a SINGLE indicator so there is no guessing.

If something isn't clear, then this is the *exact* reason people should read the manual. There should be no guessing because anyone who is new to the software should arm themselves with all the knowledge they need before taking it on. It's not Resolve's job to spell out what everything does in the UI. It's an incredibly deep and powerful piece of software with a lot of secrets for those willing to put the effort into finding them. Video tutorials can get you started but rarely cover all you need to know about how a piece of software works, and if you've read half the manual that's great but it means there's still a lot you don't know (and even that's assuming you've remembered everything you've read so far, which is unlikely), so if something unexpected happens, rather than call it a bug and blame the software you should have the humility to question your own knowledge first.

none the less, the Select All to Right / Left should _ignore_ track selection. it should actually select all. if you don't want something to move, Lock the track, thats what track locks do. Again, this unexpected, unpredictable behavior because of a unclear UI is a bug to fix.

Maybe. Still not a bug though, it's a design choice and if you don't like it then submit a feature request to change it and see how many others agree with you.

One anomaly (?) that I did notice is that the 'Linked Selection' option seemed to work in the opposite manner to which I would have guessed.

This seems like a bug, yes, though not a new one as I just tested it out on Resolve 12.5.6 and got the same thing.

I increasingly wonder why I bother, maybe next time I'll just leave you to flounder.

Tom, Please don't stop helping people. Regardless of how the OP takes your advice, you have helped me sort out the issue I was also having with selecting clips.
Thank you so much for posting and pointing out the deselected tracks. Saved me a ton of time.

I increasingly wonder why I bother, maybe next time I'll just leave you to flounder.

Tom, Please don't stop helping people.

I second that!

before insulting some one, and assuming they have read every page of a 1400 page manual.... I've actually read a good 50% of the manual - please be respectful.

Actually, the manual is now 2632 pages long. For software as complex as Resolve, reading the manual is fairly important.

The behavior of how delete and clip selection works in the Edit page is very basic stuff, and it's something that's stressed on many intro tutorials. MixingLight.com is offering 5 hours of free Resolve tutorials right now, and they very definitely covered clip deletion, multiple timeline selection, moving clips around, and stuff like that in the editing sections.

For the record, I think Tom's intentions were good and nobody intended to be disrespectful. Sometimes, honest advice requires that you have a thick skin and understand that they're addressing the problem, not you personally.

Hi Marc

Tom was rather disrespectful because he assumed a bunch of things about me starting with assuming I'm semi-clueless about Resolve and other NLE's and that the magic answer is RTFM, not that the UI has issues.

Therefore let me digress for a moment - I did a 3-4 hr series on Resolve 8 for BMD. I've provided on site training and support for FCP6 & 7, M100 and Prem Pro, AE and combustion. I started editing on tape. Thats just to get started and I won't bother you with the rest unless you want to hear the rest outside of saying, one of the things I've done and even been paid to do is UI / UX work specifically around NLE's.

Track targets vs track selections is a needless complexity. FCP6 ( or maybe 4.5, its only 15 years ago ) had it right as the last NLE I've used that simply had track selections and that was it. there was never this competition between 2 confusing indicators that applied to some operations but not all. I've been a very big advocate of simply having track selection ( or an SINGLE indication of some sort ) to set what happens for the next edit operation. Remove the guess work of if a paste operation will use track selection or targets. This is especially acute when you move between NLE's on a regular basis and they do different things.

The track target, or is it active track indicator looks exactly like next / prev keyframe ( in a box ) used even within the resolve interface. its a totally confusing indicator.It looks like it should do something with keyframes from its design. Now if you happened to stumble into the info of what it really does, its VERY easy if you know this, but you can't expect every user has a month to try to RTFM in its reasonable entirety. You can't assume some one who's used 4 or 5 other NLE's is going to slog thru hours of beginner tutorials, 100's of manual pages to gleam a few odd tidbits like this out. No, if they are going to RTFM its going to be on more advanced features, media handling, how to output your project (maybe).

A good UI / UX design should require minimal manual reading if you already know how a NLE works. Thats the hallmark app creators strive for. Sometimes they succeed, sometimes they need feedback to change things to work in a more intuitive way. Discoverability and intuitiveness of UI/UX are important and shouldn't be dismissed as RTFM. The manual is important, but so is not having software so obtuse or unobvious that you have to read it for everything. basic things should basically work.

S