Re stream

Must be from a certificate authority (see Request an SSL certificate for Wowza Streaming Engine from a certificate authority). Self-signed certificates aren't supported. Wowza StreamLock™ certificates are fully supported (see Get SSL certificates from the Wowza Streaming Engine StreamLock service). You must specify the domain name when addressing the origin server. The origin IP address can't be used. If you don't specify a port value when addressing the origin server, port 443 is used. The live stream repeater will fail to connect to a non-SSL-protected destination port on the origin server. It will repeatedly try to connect. Connection failures like the following will be reported in the Wowza Streaming Engine logs: WARN server comment - LiveMediaStreamReceiver.secureConnectionValidation: SSL Connection was not established: wowzs://[wowza-ip-address]:1935/myApplication/_definst_/myStreamEach stream that's played through this application uses the primary and secondary origin URL values to locate the Wowza Streaming Engine origin server for the stream.3. Publish the source streamAfter configuring the origin and edge servers, publish a live stream to the application on the Wowza Streaming Engine origin server. Refer to the following resources for help with publishing a live stream from various cameras and encoders to the Wowza Streaming Engine origin server: Connect live sources Re-stream with Wowza Streaming EngineNote: When re-streaming, playback on the edge server fails if a .stream file on the edge server has an identical name to the source .stream file on the origin server, so ensure that there are no .stream files on the edge server with the same name as .stream

Doesn't mean I am not being nice. RvdH Senior user Posts: 3650 Joined: 2008-06-27 14:42 Location: The Netherlands Re: BUG: ClamAV 0.104.0 does not work Post by RvdH » 2022-02-09 10:11 Question is, will that change break backwards compatibility?With what version that INSTREAM command was introduced? Why on earth they decided the delete it? They could just leave STREAM command there as alias for INSTREAM command CIDR to RegEx: d-fault.nl/cidrtoregexDNS Lookup: d-fault.nl/dnstoolsDKIM Generator: d-fault.nl/dkimgeneratorDNSBL Lookup: d-fault.nl/dnsbllookupGEOIP Lookup: d-fault.nl/geoiplookup RvdH Senior user Posts: 3650 Joined: 2008-06-27 14:42 Location: The Netherlands Re: BUG: ClamAV 0.104.0 does not work Post by RvdH » 2022-02-09 11:17 I think there is more to it then just changing STREAM with INSTREAMPrior 0.104.x clamav reported the PORT to connect toAfter that HMS send the STREAM command over port 1483The CLAMAV would reply back with another stream on port 1081:Code: Select allPORT 1081stream: Eicar-Signature FOUNDWith this INSTREAM change the whole PORT part seems to be to be left out, which result in HMS failing with the UNKNOWN COMMAND error CIDR to RegEx: d-fault.nl/cidrtoregexDNS Lookup: d-fault.nl/dnstoolsDKIM Generator: d-fault.nl/dkimgeneratorDNSBL Lookup: d-fault.nl/dnsbllookupGEOIP Lookup: d-fault.nl/geoiplookup RvdH Senior user Posts: 3650 Joined: 2008-06-27 14:42 Location: The Netherlands Re: BUG: ClamAV 0.104.0 does not work Post by RvdH » 2022-02-09 11:21 lord_dragonus wrote: 2022-02-09 11:15I already answered your questions on GitHub: should discuss it there.For record, this is my answer:Hello @RvdHout,it's marked as deprecated since February 11th 2009: ... b19bc9dR50The commands are slightly different: INSTREAM acceptes the data on the same communication port, whereas STREAM just send a new temporary port for the data to send to.Since the INSTREAM command has been added 2009 too, there is no problem for backward compatibility. So all ClamAV versions since 0.95 should work with INSTREAM.Thx, i'm gonna play with this....lets see where it gets me CIDR to RegEx: d-fault.nl/cidrtoregexDNS Lookup: d-fault.nl/dnstoolsDKIM Generator: d-fault.nl/dkimgeneratorDNSBL Lookup: d-fault.nl/dnsbllookupGEOIP Lookup: d-fault.nl/geoiplookup jimimaseye Moderator Posts: 10162 Joined: 2011-09-08 17:48 Re: BUG: ClamAV 0.104.0 does not work Post by jimimaseye » 2022-02-09 11:30 Also, even though STREAM is "deprecated" since 2009 it still continued to work up to 0.103. So what change was

This is unambiguously MPEG-2 Transport Stream format. Despite source format still is MPEG-2 ffmpeg will read it and create result in correct MPEG-2 Transport Stream format. VLC plays it correctly.2. I created copy of "Direct Stream Copy" FFmpeg Engine preset and named it "Direct stream copy MPEG-2 PS". It is in attachment. Place it in HandySaw installation folder. In it I've added output format setting "-f dvd", so this preset will copy any source media regardless its format to MPEG-2 PS format files.Of course do not forget to select it in HandySaw Preferences FFmpeg_DirectMPEG2_ini.zip ( 0 KB | 694 Downloads ) Dmitry Sinitsyn,Davis Software WWW IP Logged Davis Forum Administrator Offline Admin Posts: 79 Location: Ukraine Joined: 08.11.2005 Gender: Re: No Audio in Scene Files (HandySaw DS 4.1) Reply #21 - 12.12.2016 at 16:45:30 Print Post Ha!You're right!VLC fails with your result and with my result files.I'll test this more. But I guess this is VLC problemThank you. Dmitry Sinitsyn,Davis Software WWW IP Logged oscar New Member Offline I Love YaBB 2! Posts: 9 Joined: 12.12.2016 Re: No Audio in Scene Files (HandySaw DS 4.1) Reply #20 - 12.12.2016 at 16:39:06 Print Post You are indeed right in everything you say. But there is something strange because with VLC there is no sound and the audio codec information provided by VLC is different from that of the original file. IP Logged Davis Forum Administrator Offline Admin Posts: 79 Location: Ukraine Joined: 08.11.2005 Gender: Re: No Audio in Scene Files (HandySaw DS 4.1) Reply #19 - 12.12.2016 at 16:25:56 Print Post For me this is a good file. With audio.It played by MPC HC without problemsBTW Google play it with audio too Dmitry Sinitsyn,Davis Software WWW IP Logged Davis Forum Administrator Offline Admin Posts: 79 Location: Ukraine Joined: 08.11.2005 Gender: Re: No Audio in Scene Files (HandySaw DS 4.1) Reply #17 - 12.12.2016 at 15:51:26 Print Post Result looks fine for me from begin and from end some time)Can you share some of you result "bad" files with me?Best case is process log file + result video file Dmitry Sinitsyn,Davis Software WWW IP Logged

RvdH Senior user Posts: 3650 Joined: 2008-06-27 14:42 Location: The Netherlands Re: BUG: ClamAV 0.104.0 does not work Post by RvdH » 2021-09-19 18:13 Changelog says northing about a breaking change in how clamd should work, except for maybe:Added the %f format string option to the ClamD VirusEvent feature to insert the file path of the scan target when a virus-event occurs. This supplements the VirusEvent %v option which prints the signature (virus) name. The ClamD VirusEvent feature also provides two environment variables, $CLAM_VIRUSEVENT_FILENAME and $CLAM_VIRUSEVENT_VIRUSNAME for a similar effect. CIDR to RegEx: d-fault.nl/cidrtoregexDNS Lookup: d-fault.nl/dnstoolsDKIM Generator: d-fault.nl/dkimgeneratorDNSBL Lookup: d-fault.nl/dnsbllookupGEOIP Lookup: d-fault.nl/geoiplookup RvdH Senior user Posts: 3650 Joined: 2008-06-27 14:42 Location: The Netherlands Re: BUG: ClamAV 0.104.0 does not work Post by RvdH » 2021-10-13 15:36 You should really ask ClamAV people, apparently they have changed something that breaks compatibility CIDR to RegEx: d-fault.nl/cidrtoregexDNS Lookup: d-fault.nl/dnstoolsDKIM Generator: d-fault.nl/dkimgeneratorDNSBL Lookup: d-fault.nl/dnsbllookupGEOIP Lookup: d-fault.nl/geoiplookup mattg Moderator Posts: 22497 Joined: 2007-06-14 05:12 Location: 'The Outback' Australia Re: BUG: ClamAV 0.104.0 does not work Post by mattg » 2022-02-08 23:06 Did you start an issue on hMaislerver's github ?If not, can you please... Just 'cause I link to a page and say little else doesn't mean I am not being nice. RvdH Senior user Posts: 3650 Joined: 2008-06-27 14:42 Location: The Netherlands Re: BUG: ClamAV 0.104.0 does not work Post by RvdH » 2022-02-09 10:11 Question is, will that change break backwards compatibility?With what version that INSTREAM command was introduced? Why on earth they decided the delete it? They could just leave STREAM command there as alias for INSTREAM command CIDR to RegEx: d-fault.nl/cidrtoregexDNS Lookup: d-fault.nl/dnstoolsDKIM Generator: d-fault.nl/dkimgeneratorDNSBL Lookup: d-fault.nl/dnsbllookupGEOIP Lookup: d-fault.nl/geoiplookup RvdH Senior user Posts: 3650 Joined: 2008-06-27 14:42 Location: The Netherlands Re: BUG: ClamAV 0.104.0 does not work Post by RvdH » 2022-02-09 11:17 I think there is more to it then just changing STREAM with INSTREAMPrior 0.104.x clamav reported the PORT to connect toAfter that HMS send the STREAM command over port 1483The CLAMAV would reply back with another stream on port 1081:Code: Select allPORT 1081stream: Eicar-Signature FOUNDWith this INSTREAM change the whole PORT part seems to be to be left out, which result in HMS failing with the UNKNOWN COMMAND error CIDR to RegEx: d-fault.nl/cidrtoregexDNS Lookup: d-fault.nl/dnstoolsDKIM Generator: d-fault.nl/dkimgeneratorDNSBL Lookup: d-fault.nl/dnsbllookupGEOIP Lookup: d-fault.nl/geoiplookup RvdH Senior user Posts: 3650 Joined: 2008-06-27 14:42 Location: The Netherlands Re: BUG: ClamAV 0.104.0 does not work Post by RvdH » 2022-02-09 11:21 lord_dragonus wrote: 2022-02-09 11:15I already answered your questions on GitHub: should discuss it there.For record, this is my answer:Hello @RvdHout,it's marked as deprecated since February 11th 2009: ... b19bc9dR50The commands are slightly different: INSTREAM acceptes the data on the same communication port, whereas STREAM just send a new temporary port for the data to send to.Since the INSTREAM command has been added 2009 too, there is no problem for backward compatibility. So all ClamAV versions since 0.95 should work with INSTREAM.Thx, i'm gonna play with this....lets see where it gets me CIDR to