Move clip from timeline to a bin

[GoogleCodeExporter]

Say I have clips (which were clipped from another clip) on a timeline... I'd 
like to be able to move them to a bin =)

Original issue reported on code.google.com by lkjoel...@gmail.com on 21 Jan 2014 at 12:45

[GoogleCodeExporter]

You can save clips and they go to the range tab. I haven't tried to put those 
in a bin, though.

Original comment by lapetti...@gmail.com on 21 Jan 2014 at 9:36

[GoogleCodeExporter]

oh, thanks!! still not optimal though =( (it would be easier for me to have a 
bin of clip ranges)

Original comment by lkjoel...@gmail.com on 22 Jan 2014 at 6:45

[GoogleCodeExporter]

Did you try putting them into a bin after you saved them? Just wondering b/c I 
haven't been on for a couple of days (working on sketches but not editing yet). 
I'll want to drop those in a bin, too. I even put my stuff I won't use in a 
'rubbish' bin =). Let me know if you can/can't but SAVED ranges in a bin, if 
you try it.

Original comment by lapetti...@gmail.com on 23 Jan 2014 at 4:38

[GoogleCodeExporter]

I tried, yes, but I don't think it's possible. So I have a lot of ranges in the 
range log, and I right-clicked one of them, and the only menu item that seemed 
to be remotely helpful was "Display in clip monitor". I clicked that, but then 
I couldn't find a way to put a clip in the clip monitor to a bin =/

And yeah, I agree, I want to have a "rubbish" bin too... just have a lot of 
bins of clips I use (have multiple bins, for sorting purposes), or don't use 
(or rather, clips I'll _most likely_ not use =P).

Original comment by lkjoel...@gmail.com on 23 Jan 2014 at 7:03

[GoogleCodeExporter]

Another thing that you could try/I will try is to render your clip and have it 
save to the import tab (I forgot what it's called) then I bet you could move 
that into a bin. It's not an ideal workflow but maybe a work around?

Original comment by lapetti...@gmail.com on 23 Jan 2014 at 8:58

[GoogleCodeExporter]

Yeah, that would most likely work. But the range log seems like a better 
workaround (because then, you can still easily edit effects, edit ranges, plus 
it's easier to put in/out, etc...)

Original comment by lkjoel...@gmail.com on 23 Jan 2014 at 9:23

[GoogleCodeExporter]

I get what you're saying. I was just suggesting a workaround to get the clip 
into a bin. I agree that it would be better to leave it in the range log.

Original comment by lapetti...@gmail.com on 24 Jan 2014 at 2:38

[GoogleCodeExporter]

For the next release there are going to be some enhancements for "Range Log" 
functionality that may help you with your desired work flow:

1) You will be able to create named groups of Range Log items. So there is 
going to be a:
- "Group Starred Items" button after which you will be prompted to give group 
name
- some way to destroy group with or without destroying items it has
- a combo box with "All, <User defined group1>, <User defined group2>..." 
selections that change the displayed Range Log items

2) It will be possible to drag'n'drop a Range Log item into Timeline to create 
a clip

3) Timeline clips will have "Save Clip Range as Range Log Item" selection in 
pop-up menu available.

4) There will be "Use Comments as Clip names" check box so that when you 
drag'n'drop or append Range Log items into Timeline these items will be 
differentiated from original media clips if so desired.

I believe these will help using "Range Log" more effectively to manage saved 
clip ranges.

I won't make it possible to save clip ranges as Bin items because Flowblade has 
decided to provide Range Log functionality for this purpose.

Original comment by janne.li...@gmail.com on 27 Jan 2014 at 8:23

• Changed state: Seediscussion

[GoogleCodeExporter]

Ah ok, I see, thanks! Could I also recommend the functionality of being able to 
drag'n'drop a clip _to_ the range log? That would seriously help, because 
displaying a clip in the clip monitor, then clicking the "add" button on the 
range log is not very efficient =P

Thanks for all your work on this, btw ^^

Original comment by lkjoel...@gmail.com on 27 Jan 2014 at 3:37

[GoogleCodeExporter]

Feature will be available in 0.14.

Original comment by janne.li...@gmail.com on 3 Apr 2014 at 9:25

• Changed state: FixedInRepository

[GoogleCodeExporter]

Original comment by janne.li...@gmail.com on 18 Jun 2014 at 2:56

• Changed state: Fixed