Opened 12 years ago
Closed 6 years ago
#2306 closed enhancement (fixed)
Vividas Demuxer for IPLEX
Reported by: | ryszardzonk | Owned by: | |
---|---|---|---|
Priority: | wish | Component: | avformat |
Version: | git-master | Keywords: | vividas |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Vividas is the demuxer used by iplex.pl video streaming site and probably other sites as well. Patches for it are floating around, but it would be nice if it could be included in the ffmpeg git tree as well. I have tested this patch with version 0.10 and confirmed it is working http://sd-xbmc.googlecode.com/files/0001-Vividas-support-for-IPLEX-for-current-ffmpeg.patch
There is also update availavle for version 0.11 https://gist.github.com/3770979 which works with 1.0. In form of patch located here http://pastebin.com/9bwHUJF2
Please review and add it in the tree
PS I am not developer so if changes are required to the patch Krzysztof Klinikowski or Tomasz Jezierski whom worked on those patches are probably more appropriate guys to ask about it
Change History (7)
comment:1 by , 12 years ago
follow-up: 3 comment:2 by , 12 years ago
@cehoyos
my friend there is no need to scream.
First of all IMHO ticket is about adding the demuxer to the ffmpeg that at the moment is not present in the tree therfore as such should be valid as enchacement or wish regardless of whether the patches already exist or not.
Secondly I pointed out to the patches to make everyone looking for them have the links for them available in one location.
And third I did exchange few e-mails with Tomasz about a month ago asking him whether he will would like port the patch to the git, but ATM he was not all that interested as XBMC for which it was designed uses 0.10 tree for now which simply worked for him, but my believe is that if the request of porting of the patch comes from one of the ffmpeg developers it could carry more weight than mine request/s and hence the proposition. What I can do is to forward the e-mails in the matter but they are in Polish so might not be all that helpfull
Last but not least porting the patch to git is likely that all there is to do is to make few changes to the ABI in the patch which are likely quite simple for one of the ffmpeg devs whom did make those changes for number of the other demuxers already in the tree
Please correct me if I am wrong
comment:3 by , 12 years ago
Replying to ryszardzonk:
my friend there is no need to scream.
I didn't
First of all IMHO ticket is about adding the demuxer to the ffmpeg that at the moment is not present in the tree therfore as such should be valid as enchacement or wish regardless of whether the patches already exist or not.
Yes, if you provide a sample.
comment:4 by , 12 years ago
Keywords: | vividas added |
---|---|
Status: | new → open |
Several samples are in http://samples.ffmpeg.org/archive/container/unknown/
comment:5 by , 6 years ago
Resolution: | → invalid |
---|---|
Status: | open → closed |
Available patches are invalid.
comment:6 by , 6 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Version: | unspecified → git-master |
Samples exist.
$ ffmpeg -i unknown+unknown+unknown+unknown+casinoroyale_210.viv ffmpeg version N-92659-geade85b Copyright (c) 2000-2018 the FFmpeg developers built with gcc 6.4.0 (GCC) configuration: --enable-gpl --enable-libxml2 --enable-gnutls libavutil 56. 24.101 / 56. 24.101 libavcodec 58. 42.100 / 58. 42.100 libavformat 58. 24.100 / 58. 24.100 libavdevice 58. 6.101 / 58. 6.101 libavfilter 7. 46.101 / 7. 46.101 libswscale 5. 4.100 / 5. 4.100 libswresample 3. 4.100 / 3. 4.100 libpostproc 55. 4.100 / 55. 4.100 [vivo @ 0x3f22500] Format vivo detected only with low score of 1, misdetection possible! [vivo @ 0x3f22500] unknown packet type 7 unknown+unknown+unknown+unknown+casinoroyale_210.viv: Invalid data found when processing input
comment:7 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Fixed in d06aae732c16bd4c490c6dfa35cc2a35129c640f.
Replying to ryszardzonk:
So why did you open this ticket instead of asking them to send the patch to ffmpeg-devel?
Seriously: If you want to make this a valid ticket, please provide a sample, if you want this fixed, either send a patch (against current git head!) to ffmpeg-devel or ask the developers of the patch to do it.