Netcam Studio Crashing / swscale-3.dll?

A new approach.
I started from the beginning and the swscale-3.dll is part of FFmpeg indicating the coding/encoding of the stream. It crashes on all installations on different machines. It works using VLC. I suggest the following.

  1. In the Settings there is a tab called Decoding/Encoding. Under Decoding Settings you have 3 choices; buffered, unbuffered and VLC. Change to for example VLC and restart NCS X, really Exit.
  2. It is an onvif cam and the new version NCS 1.3.6 have a new system for onvif detection that works really good. You can download it here and run it and add the cam using the onvif tab.

VLC must be in the same library as NCS, in your case Program Files (x86).

-Henrik

Does it also happen without recording at all ?

Does the camera that is used when it crashes provide audio ? What are the audio settings (from the camera UI) for this camera ?

I suppose that this swscale library is the one responsible for rescaling or converting frames / packets so potentially for converting audio. It could be that it crashes if the audio format / codec is not supported properly by netcam studio.

Switching to VLC mode (rather than BUFFERED / UNBUFFERED) will totally bypass the FFMPEG part of netcam studio for decoding the streams from your camera so most likely it won’t crash anymore but it also won’t help in fixing it.

If it still crashes after switching to VLC mode then most likely it means that it crashes not because of decompressing the stream from this cameras but during re-encoding (for recording or streaming audio or streaming in MPEG4).

Thanks guys!

I’ll try the new version. I’ll try to address one variable at a time. Version, then settings, then onvif profile/detect, and then audio

Yes, this camera did have audio. Oh and here’s some more info from other events.

EventData>
129105308219
5
CLR20r3
Not available
0
NetcamStudioX.exe
1.3.5.0
57230fa5
NetcamStudioX
1.3.5.0
57230fa5
df4
8
System.BadImageFormatException

C:\Users\xxx\AppData\Local\Temp\WER1AF.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_NetcamStudioX.ex_c860b14fe54d53f9cdc5bc397e29b53ffeaf3d1e_d68a6499_8d5a0ccb

0
847a9630-efd2-4b0d-a8b9-3f140cc02766
0
fb7ac21ba70b98002bbba3e47ddfd113


129105308219
5
CLR20r3
Not
available
0
NetcamStudioX.exe
1.3.5.0
57230fa5
NetcamStudioX
1.3.5.0
57230fa5
df4
8
System.BadImageFormatException
C:\Users\xxx\AppData\Local\Temp\WER1AF.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_NetcamStudioX.ex_c860b14fe54d53f9cdc5bc397e29b53ffeaf3d1e_d68a6499_8d5a0ccb
0
847a9630-efd2-4b0d-a8b9-3f140cc02766
0
fb7ac21ba70b98002bbba3e47ddfd113


and

NetcamStudioX.exe
1.3.5.0
57230fa5
KERNELBASE.dll
10.0.10586.162
56cd45b4
e0434352
0000000000071f28
114ac
01d1b142f638c577
C:\Program Files\Netcam Studio - 64-bit\NetcamStudioX.exe
C:\WINDOWS\system32\KERNELBASE.dll
847a9630-efd2-4b0d-a8b9-3f140cc02766



One more tidbit… wonder if this is the issue. I have both the 32 and 64 bit versions installed…They appear to share some of the same configs or something… hmm…

I suggest you remove all that have with NCS to do!! Then install the 64 bit versionn on the Win10 machine(I assume). Thec above error is really f*** up :slight_smile: . In ProgramData - Moonware … there are 3 files that you should remove as well.

32 & 64-bit can live together. I really suspect a funky audio or video format / codec which is not well implemented to be the cause.

A funky codec on the camera? really? on a cheap Chinese off brand rebaged camera? Surely, you must be joking. :slight_smile:

it was a polite way to say a sh****y implementation of a compression codec or non-standard values :slight_smile:

But no i wasn’t joking, for instance if it’s AAC in our side that it’s not well implemented, because the good quality AAC decoders are GPL and therefore we cannot use them, we have to rely on crappy ones…

I am not quite sure I am done with this, but we give up here?

Well if we have access to the camera (including its rtsp stream) then we can check further, otherwise not much more we can do…

Hey guys… I’m going to try to beef up the network to that location. The bumpy connection may contribute to the issue.
Thanks for hanging in here.