Hi, everyone...
I'm trying to use the svg inkscape plugin. I think that it is a very good idea the possibilty of insertion and modifying svg files whitin in Cin.
Unfortunately the svg file when imported in Cin has no transparent background.
If that same file is imported in gimp, it has it's background transparent. So that tells me that even if the svg format has no implementation of transparency by default, the Inkscape svg file tell gimp that this particular file has no background.
Of course I can have a green background in that file and remove via Chroma key filters but this add a layer of work and complexity...
Or perhaps I'm missing something to get imported the Inskcape svg file with transparency.
Any help or hint will be welcome.
Tanks
Armandux
Hi, GG is looking at this yet today (my computer has been unavailable all day so late in seeing this). I think I remember having looked into this before but do not remember the result.Â
Update: continuing tomorrow. It may be a result of an update in Inkscape that has not been propagated in Cinelerra, but we are not sure yet.
Turns out that the changes are due to "upgrades" in inkscape. When cinelerraGG needs to update the image file, it runs a batch inkscape command like this:
[root@xray svg]# inkscape --without-gui --export-background=0x000000 --export-background-opacity=0 -d 96.000000 /tmp/bs.svg --export-png=/tmp/bs.svg.png
Warning: Option --without-gui= is deprecated
Warning: Option --export-png= is deprecated
** (org.inkscape.Inkscape:29472): WARNING **: 15:50:21.060: Fonts dir '/root/.config/inkscape/fonts' does not exist and will be ignored.
Background RRGGBBAA: ffffffff
Area 0:0:1280:720 exported to 1280 x 720 pixels (96 dpi)
The log indicates that the changes introduced damages to cin.
I have upgraded the new.svg default image, and revised the command:
[root@xray svg]# inkscape --export-background=0x000000 --export-background-opacity=0.001 -d 96.000000 /tmp/bs.svg --export-filename=/tmp/bs.svg.png
** (org.inkscape.Inkscape:29491): WARNING **: 15:50:49.791: Fonts dir '/root/.config/inkscape/fonts' does not exist and will be ignored.
Background RRGGBBAA: ffffff00
Area 0:0:1280:720 exported to 1280 x 720 pixels (96 dpi)
The changes avoid the warnings, and the opacity is back to 00.
Still, these are damages to the interface. The opacity is wrong,
and the export code used to not depend on the X server running.
There may be limits to what works from a batch job.
1) The without-gui and export-png features are deleted/renamed.
2) The program could fail on a batchrender if X is not running.
3) The export-background-opacity has been changed from 00 to ff.
Â
(Previous reply written by GG.)
The changes to fix the transparency problem for now will be checked in and available in the October 31 builds. If you need the changes earlier than that, we can create a static tar build for whichever Operating System you are using.
Â
Thanks so much for reporting this deficiency -- it is how we can keep up with the changes needed.
Â
P.S. The October builds will also include an "drag select" to select multiple edits on the timeline and also to easy deselect multiple edits as you mentioned in a previous forum topic.
Hi Armando,
could you check which Color model are you using, please?
You have to use a RGBA or YUVA format for the alpha channel.
Check it in, Menu-> Settings-> Format..., Video area, Color model.
In my test with Cin_20200930 and Cin_20200531, and Inkscape_0.92.4 it works right (my OS is UbuntuStudio_16.04).
Â
PS:
Sigh-sigh. I am also here.
Thank you for your kind help. I always use RGBA model, because I use a lot the Tittle/text plugin to sobreimpress text to image.
I'm using ubuntustudio 20.04 and Inkskape 1.0, and as phyllis have pointed wisely it is a new implementation of the inksape file that causes this issue in Cin.
Anyway thank you.
Armando
