Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001
- User Since
- Jun 1 2018, 3:52 AM (165 w, 6 d)
Thanks, just wanted to double check
@Harley Acheson (harley) I see that current design is a bit confusing, do you think this should be confirmed?
Sorry, missed that file is included here. I can confirm that this file uses huge amount of memory, so I will close this report. @Alaska (Alaska) provided good analysis here.
I was able to reproduce with 2.93.2, no issue in master.
First I thought this is trolling, then I laughed, finally watching video without sound, I guess this is real issue.
I have confirmed this, because we have function BLI_filename_make_safe so it can be used perhaps with RNA set function. Path would be sanitized if you would enter it through file browser. In this case, path is also ammended, but there is report for that too - T88193
I think this is same issue as T69762 as far as shading glitches goes, mesh has some faces with degenerate geometry.
Can you upload sample .blend file with image so we can reproduce here?
I watched my GPU utlization and it never came above 2%.
This was intentional change in 3.0, see rB3b6ee8cee70. You should see message that says, you may expect loss of data due to opening newer file. It is specifically due to vertex groups refactor.
This will probably be issue in more places than render output.
@jordi torres (jordi_torres) does Ctrl+Shift+Alt+A work without factory settings?
Do you use default keymap? If so is it modified by you? What @Eugene Du (APEC) suggested is good idea to check, but I would expect you to notice that it does something different.
I missed the file, so I was trying to reproduce with default cube.
I think it would be nicer design, if there would be only sequence_editor.display_stack() function and you can provide either sequence or None. So you can do sequence_editor.display_stack(sequence_editor.meta_stack[-1]) to go up one level for example.
There are 2 issues, but no bug as far as I can see:
- VSE is on "same level" as compositor, so if both have content, you have to choose one or another in Post Processing panel in Output Properties. See https://docs.blender.org/manual/en/dev/render/output/properties/post_processing.html#post-processing
- Image input node is set to 1 frame, so it doesn't play whole sequence
I can't reproduce this issue.
I am not sure if this is bug, because this seems to be caused by overlapping faces between original geometry and hull. So you can add transform node with scale of 0.999999 to resolve this overlap.
All these issues are resolved, so closing the report
Thanks for nice list.
Can't reproduce this issue. I assigned Ctrl+Shift+Alt+A and it works.
Tue, Aug 3
This will be fixed in 2.93.2 which is release candidate now, but you can download it from https://builder.blender.org/download/daily/
Hmmm not sure if I would be happy with transform widget that UV editor uses, I would expect it to follow image orientation, but perhaps this is just matter of implementation.
Cropping could perhaps be done with modifier key.
Technically this never worked properly, but arguably rBd373b43f07f5 made it a bit worse. Got some initial fix ready, will continue tomorrow to cover more edge cases.
VSE should be able to use DNA defaults, but this wouldn't resolve this issue for some properties like blend mode mentioned here.
Currently strips don't snap to themself, because this is bit more tricky to handle when more strips are selected.
Yes this indeed looks like a mistake, I missed the point that in light theme this color is already different.
Just don't define arguments, you don't need. Like this:
I asked because of statement:
I also observe that it does not detect any graphics card
Can confirm, I think this would be nice to resolve, even though it may not be bug technically. So will check how this can be resolved and if this proves to be difficult I may classify this as known issue
Mon, Aug 2
I can reproduce the issue, but strangely it dissappears when showing frame numbers instead of time. This is the case in all editors not only VSE.
Thanks I almost forgot to close this
So far I have checkedperformance and don't see any regression here
Can you upload movie file here as well? I suspect this would be seek bug
I think this is intentional, but looks to be incorrect anyway.
Sorry, I must have been doing something wrong, I have re-checked and I see curves now. I see they are normalized too. I would probably suggest using different color for 0 line. I find it distracting when it is same as current frame. Personally I would go for 1px thin darker line in same hue as strip body. Or not draw it at all if it is still distracting.
It's when you drag handle beyond strip content so it outputs static image. Kinda sorta, but in context of snapping that boundary is the hold offset.
Patch is correct, so I accept.
Fri, Jul 30
Can you link where this was reported? This probably fixes the issue of availability, but either I don't know how to use use_stamp_sequencer_strip, or it is broken. So I just want to have more context before I check more in detail.
Thu, Jul 29
I have already applied this patch so it's probably best to respond (already...).
Can't really say why. I guess this could be changed
- Nor seq_speed_effect_target_frame_get shoul be static :/
- Oops, seq_effect_speed_rebuild_map is not static
- Use static qualifier
- Clarify seq_effect_speed_rebuild_map return value
- Fix memleak
Wed, Jul 28
Do you use Pulseaudio as output sound device? Check in User preferences > System > Sound.
- remove unrelated change
- Add only overwrite mode to header.
- Add a description for show_grid property