Results 1 to 11 of 11

Thread: Scan Converter Randomly closing with no error

  1. #1
    Registered User
    Join Date
    Dec 2018
    Location
    Michigan
    Posts
    5

    Scan Converter Randomly closing with no error

    We are running scan converter on 2 computers. The 2nd computer is pulling the first computers gameplay and putting it in a twitch stream mini window. Sometimes we can stream for 2-4 hours no issues and nothing changes and it closes with no error. Sometimes it closes with no error every 15-20 mins. Both computers lose the converter at the same time. Anyone have any ideas on why it would be randomly closing? It would be a lot easier to trouble shoot with a error code but we get nothing.

    Both computers specs are:
    Windows 10
    GEFORCE GTX 1080Ti - 11GB RAM
    16GB RAM
    Ryzen ASRock X370 Gaming 4K Motherboard
    Ryzen 7 1700X AMD
    WD Blue 2TB IHD
    500GB SSD
    Hyper 212 EVO fan
    Corsair CX 750M Watt Power Supply
    450 Watt EPS
    Installed the NDK toolkit 3.8 on both computers.

    Let me know if you need any other info to help resolve the problem.
    Thanks in advance!

  2. #2
    Registered User
    Join Date
    Dec 2018
    Location
    Michigan
    Posts
    5
    We have now installed it on a 3rd machine and pulled the stream from the first 2 computers to it to make sure it just wasn't overloading the other computer and it's still closing. Last night we went 4 hours with no close, today we had it up 5 mins and it closed already. The time it stays up and running is really random. It makes it hard to keep viewers when we lose the stream consistently. Again no errors with it.

  3. #3
    Does it depend on the game? If you run it on a system just setting at the Windows desktop (or with a different game) does it have issues? I'm just guessing at things to test, but if a trigger can be found that cases the problem, then there is something to close closer into or file a bug report on. Are the nVIdia drivers the latest version? Are all systems the same configuration as above?
    Kane Peterson
    Key Accounts Sales Engineer
    NewTek, Inc.

  4. #4
    Registered User
    Join Date
    Dec 2018
    Location
    Michigan
    Posts
    5
    We did update the nvidia drivers and it still closes. Also, side note it now closes adobe character animator too when it closes. We added animator in to make some animated sharks talk but when ndi converter closes on both our computers so does the adobe program so we have to restart both. Not sure what connection they have together or if that helps at all. Right now we are just mainly playing CS:GO but we will try a new game tonight to test that idea. I know we played rust the one night and I can’t remember if it crashed or not for sure so will try this and let you know. Last night it closed 4 times during streaming.

  5. #5
    Registered User
    Join Date
    Dec 2018
    Location
    Michigan
    Posts
    5
    It does close while just sitting there and no games/streams running. Rechecked video drivers on all 3 and they are indeed all up to date. Also, it closed while streaming RUST which is a different game then normal.

    When it runs it runs beautifully! We are loving it. Of course the constant stream dropping from it closing isn't helping us keep viewers but once we get this issue ironed out it seems to be the perfect necessity for what we are doing.

    Any other ideas to try?

    Thanks for the help.

    Another side note: It closes steam labs obs when it closes too. However it does not close Adobe Illustrator with it. It does close Adobe Character Creator with it though. Seems like everything it works with directly it closes when it does. Not sure if this helps at all lol.
    Last edited by zuddles; 01-04-2019 at 11:42 PM.

  6. #6
    Registered User
    Join Date
    Jan 2019
    Location
    Canada
    Posts
    1
    Hi! If you don't mind I'd like to join in on this conversation. The EXACT same thing is happening to me (just started using NDI a few days ago)
    Basically, same thing: I have a dual pc streaming setup, gaming PC runs NDI scan converter while the streaming PC runs OBS with the NDI Source plugin and streams it to twitch.
    My Specs :
    Gaming PC
    Windows 10
    GEFORCE GTX 1080
    32GB RAM
    Intel i7 8700k
    Samsung 970pro NvMe SSD

    Streaming PC
    Windows 10
    GEFORCE GTX 970
    16GB RAM
    Intel i7 7700k
    Samsung 970pro NvMe SSD

    I use a 1440p 144hz monitor on my Gaming PC, which is the main reason why I'm switching to NDI compared to capture cards.

    Both PC's have updated device drivers, windows updates, NDI runtime and VC redist and all that installed.

    At random times NDI Scan converter on my Gaming PC will just close, no error or nothing. When that happens OBS will close at the exact same time on my streaming PC (also there, no error at all). Just like OP said it's completely random, most of the times it happens within an hour of starting, sometimes within the first 5 minutes but yesterday I streamed for 3 hours before it crashed.

    Here's some things I've tried:
    -Using OBS with NDI plugin on my Gaming PC instead of Scan converter: Result was that OBS on my gaming pc will just crash and thus crashing my OBS on my streaming PC aswell.
    -Playing around with the refresh rates in the scan converter: ended up crashing on all 3 settings (use monitor refresh rate, 60 or 59.94p)
    -Tried letting my pc just sit idle, not using it at all: it still crashes, even with no other software/games open, it still crashes even when just staring at the windows desktop
    -I've reinstalled both the NDI tools and OBS on both PC's, no fix.
    -I've installed NDI Analysis and let a diagnosis run for my source, attaching a screenshot just showing you what happens when it crashes (probably doesn't help at all but it can't hurt)
    Click image for larger version. 

Name:	2019-01-06_19-12-27.jpg 
Views:	23 
Size:	106.7 KB 
ID:	143828
    -Just to note, the NDI scan converter will still crash even when I'm just looking at a preview in OBS, I don't have to actually be live for it to crash.

    I'm not sure what else to try here, if you have anything that help or that you want me to try, let me know I'm down to try anything at this point.

  7. #7
    Registered User
    Join Date
    Dec 2018
    Location
    Michigan
    Posts
    5
    I decided to try using obs studio on my 2 comps then put obs studio on the 3rd and have the 3rd pull the other 2 comps as a NDI source. Of course it randomly closes too.

    I finally, finally got a crash report from the obs studio which I have included below. Maybe it's runtime 3.8 causing it being that it is the only consistent piece between all 3 machines and every which way I have tried this lol. So to recap here is everything I've tried:

    We made sure all the video drivers were up to date.
    Made sure all NewTek stuff was allowed through firewall/defender/antivirus as well as SLOBS client folder and OBS.
    Installed NDI Runtime 3.8
    Made sure windows C++ redistributable was up to date
    Disabled 3rd party overlays.
    Ran everything as administrator
    Installed everything as administrator
    Tried the obs studio plugin obs-ndi 4.5.3 per streamlabs help guide found here: https://support.streamlabs.com/hc/en...s/360002835654

    First scenario was 2 comps of above specs in first post. Ran converter on 1 and streamlabs obs one 2. Pulled 1 gameplay and audio to 2 through streamlabs obs as a NDI source. Randomly closes.
    Brought in 3rd computer. Installed Converter on 1 and 2 and Streamlabs obs on 3rd. Pulled ndi source through streamlabs on 3rd from 1 and 2. Randomly closes.
    Installed OBS studio on 1 and 2 with obs studio ndi plugin. Tried to pull this as a NDI source to streamlabs on 3rd. Randomly closes.
    Tried above scenario with all 3 running obs studio (No streamlabs at all) and closes but we got 2 crash reports from comp 2 and 3 that match. Comp 1 didn't generate a crash report. That report is below.
    In all scenarios above we ran as admin/non admin and had the 3.8 installed for all trials.
    Also, we tried running these above scenarios with games, different games and without games (Sitting idle) and it will close still.

    Side notes:
    Closing is completely random and has no recurring time. Sometimes its 5 mins and sometimes we have made it 4 hours without a close.
    When it closes...it closes all the programs connected to it. So if NDI Converter is running on comp 1 and 2 and comp 3 has obs or stream labs running it closes all of them at the same time. I find this really strange. If we have Adobe Character Creator connected it will also close them too. It does not close the game we are playing or other programs not associated with the stream, like Adobe Illustrator.


    Crash report partial copy (I have the whole thing if it needs to be sent somewhere):

    Unhandled exception: c0000005
    Date/Time: 2019-01-06, 22:04:45
    Fault address: 7FFD0BC4963C (c:\program files\newtek\newtek ndi 3.8 runtime\v3\processing.ndi.lib.x64.dll)
    libobs version: 22.0.2 (64-bit)
    Windows version: 10.0 build 17763 (revision: 195; 64-bit)
    CPU: AMD Ryzen 7 1700X Eight-Core Processor


    Thread 6F90 (Crashed)
    Stack EIP Arg0 Arg1 Arg2 Arg3 Address
    0000002AE78FFB88 00007FFD0BC4963C 000001A0C36333C0 0000002AE78FFC59 000001A0CDAA1470 0000000000000000 processing.ndi.lib.x64.dll!0x7ffd0bc4963c
    0000002AE78FFB90 00007FFD0BC4DE4B 0000000000000000 0000000000000000 000001A0CE818400 00000000047FE79D processing.ndi.lib.x64.dll!0x7ffd0bc4de4b
    0000002AE78FFCC0 00007FFD0BC4C969 0000000000000000 0000000000000000 0000000000000000 0000000000000000 processing.ndi.lib.x64.dll!0x7ffd0bc4c969
    0000002AE78FFCF0 00007FFD937F7E94 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffd937f7e94
    0000002AE78FFD20 00007FFD939DA251 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffd939da251

    Thread 664C
    Stack EIP Arg0 Arg1 Arg2 Arg3 Address
    0000002AE671C368 00007FFD8FDF9904 0000000000000000 000001A0BD2F1910 000001A0BD2ECFD0 00007FF64B2A0F00 win32u.dll!0x7ffd8fdf9904
    0000002AE671C370 00007FFD926AF5CD 000001A0BD2ECFD0 000001A000000003 0000000000000000 000001A0BD2F1A08 user32.dll!0x7ffd926af5cd
    0000002AE671C3B0 00007FFD0D297C01 00007FF64B2A0F00 0000000000000000 000001A0BD2B2D00 000001A0CE2A7C00 qt5core.dll!0x7ffd0d297c01
    0000002AE671F530 00007FFD0DF7AA69 0000000000000000 0000000000000014 000001A0BD2AC470 000001A0BD2AC470 qwindows.dll!0x7ffd0df7aa69
    0000002AE671F560 00007FFD0D247442 000001A0BD2B1060 0000000000000000 0000002AE671FA60 00007FFD0D347F98 qt5core.dll!0x7ffd0d247442
    0000002AE671F5E0 00007FFD0D24AB3A 00007FF64B33E239 0000000000000000 0000002AE671FA60 000001A0CE2DB4A0 qt5core.dll!0x7ffd0d24ab3a
    0000002AE671F650 00007FF64B10112C 0000000000000000 000001A0BD2CE610 000001A000000000 0065006C00000002 obs64.exe!run_program+0x75c
    0000002AE671F960 00007FF64B103770 0000000000000000 0000000000000000 0000000000000000 000001A0BD2ABE00 obs64.exe!main+0x660
    0000002AE671FB30 00007FF64B258194 0000000000000001 0000000000000000 0000000000000000 0000000000000000 obs64.exe!WinMain+0x154
    0000002AE671FBC0 00007FF64B257272 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs64.exe!__scrt_common_main_seh+0x106
    0000002AE671FC00 00007FFD937F7E94 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffd937f7e94
    0000002AE671FC30 00007FFD939DA251 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffd939da251
    Last edited by zuddles; 01-06-2019 at 08:30 PM.

  8. #8
    'the write stuff' SBowie's Avatar
    Join Date
    Feb 2003
    Location
    The stars at night are big and bright
    Posts
    19,077
    Curious. Might I suggest you post a bug report: https://forums.newtek.com/showthread...Reporting-Bugs
    --
    Regards, Steve
    Forum Moderator
    ("You've got to ask yourself one question ... 'Do I feel lucky?' Well, do ya, spammer?")

  9. #9
    Registered User
    Join Date
    Sep 2013
    Location
    Atlanta
    Posts
    221
    FWIW, happening on both of my Macs as well as the W10 PC in here.

  10. #10
    'the write stuff' SBowie's Avatar
    Join Date
    Feb 2003
    Location
    The stars at night are big and bright
    Posts
    19,077
    Quote Originally Posted by dhodlick View Post
    FWIW, happening on both of my Macs as well as the W10 PC in here.
    As there is a strong possibility that this is related but different, given the platform, please open a bug case for the issue as seen under OSX.
    --
    Regards, Steve
    Forum Moderator
    ("You've got to ask yourself one question ... 'Do I feel lucky?' Well, do ya, spammer?")

  11. #11
    NewTek Engineering QA VideoEng QA's Avatar
    Join Date
    Sep 2011
    Location
    San Antonio
    Posts
    161
    We have been working with two users who were encountering this same issue. This appears to be caused by something on the network sending out a malformed (not to spec) mDNS response, this is why it hits both sides (send/receive) simultaneously. Tons of appliances/devices send out mDNS traffic. We made some changes to make our code to make it more robust when a malformed mDNS packet comes across the network so we should no longer have this issue.

    Below are new beta builds of NDI 3.8 Tools and NDI 3.8 Runtime. Both of these have the change I mention above. You will need to run the Tools install on your system running ScanConverter and the Runtime on your OBS/streaming system.

    NDI Tools 3.8 190110
    http://new.tk/NDITools190110

    NDI 3.8 Runtime 190110
    http://new.tk/NDIRT190110

    We are currently vetting these new NDI builds for public release (along with new mac versions). We will try to have them live by the close of business today. If possible I would love to receive some feedback from some of the users in this thread (while using these new builds) to make sure we are speaking about the same problem.
    NewTek Engineering QA
    For bug reports, feature requests, or technical inquiries: https://fogbugz.newtek.com/default.asp?pg=pgPublicEdit

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •