[WiP] madVR support in MP1 (30 Viewers)

[joecrow]

So open that file and search for the IP and removed it, i think it should works

Got it, fixed it, thanks. Now I can start again on trying to get it working.

 

[Freuli]

Hi Sebastiii,

v445 stays black after switching the AVR off. On is working perfectly. Unfortunately I didn't store a log file yesterday. I went back to v444.

Regards
Markus

 

[Sebastiii]

@Freuli hi
Are you able to test this bin : [WiP] - madVR support in MP1 ?
Thanks.

 

[joecrow]

OK I got Auto3D working, well sort of (needs some refining). Basically I had to enable DMR in the network settings of the Philips TV then using the actual IP address for the TV in the Auto3D config with jointSpace v1 (the only option that really connects to my TV). It was then possible to generate and execute a command sequence but as per this post it was made difficult since the jointsSace v1 option does not have a 3D button although the TV remote does and so the sequence is much longer and clunkier than necessary.
UPDATE:-
Auto3D is detecting a 3DSBS and now automatically switching the TV to 3DSBS mode, however on stop it looks like a (non customizible) command sequence is triggered that does not work with the result that the TV is not returned to 2D mode and the MP GUI is not displayed correctly, still working on it.

 

[Freuli]

Hi Sebastiii,

446 is working perfectly! I started several times from standby, switched the AVR on and off, started Video with TV and with AVR and also wit and without bitstreaming. Even bitsreaming with TV didn't cause a hang up.

Well done!

regards
Markus

 

[Sebastiii]

Nice @Freuli logs looks good thanks.

 

[daWooky]

hi @Sebastiii
so far all good with v446 on my side too... runs with fcu image on test rig also with new lav/mad
mepo fcu option still needed
that new strg+s mad shortcut is quit useful...see new madvr 1050ti settings

 

[Sebastiii]

Great
I have noticed a rare case with audio so will put a new build on first post V447

 

[Sebastiii]

First post updated V447 will act like V446 but with the fix on audio side (analyse volume slider in timer was causing rare case where MP can crash lol)

 

[daWooky]

that unintentionally muted, sounds like a pretty nasty one^^ thanks, once again
and btw. those w10 388 nv drivers still drive me nuts...running days without problems but on the next day boot up, tv lost sync because the dumb driver somehow changed the display to a unsupported refreshrate... wtf. but a nice prank nvidia or ms. i had to admit...
and those annoying randomly display crashes

Spoiler: dwm.exe

18.01.2018 23:05 Application Error Anwendungsabsturzereignisse Error Name der fehlerhaften Anwendung: dwm.exe, Version: 10.0.16299.15, Zeitstempel: 0x7f22d77c Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000 Ausnahmecode: 0x80070057 Fehleroffset: 0x0000000000000000 ID des fehlerhaften Prozesses: 0x2c60 Startzeit der fehlerhaften Anwendung: 0x01d3909c7414422a Pfad der fehlerhaften Anwendung: C:\WINDOWS\system32\dwm.exe Pfad des fehlerhaften Moduls: unknown Berichtskennung: f6854616-5ed9-4b33-95c9-9ebb4bb391ab Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 1000
18.01.2018 23:05 Windows Error Reporting 0 Information Fehlerbucket , Typ 0 Ereignisname: APPCRASH Antwort: Nicht verfügbar CAB-Datei-ID: 0 Problemsignatur: P1: dwm.exe P2: 10.0.16299.15 P3: 7f22d77c P4: StackHash_7018 P5: 0.0.0.0 P6: 00000000 P7: 80070057 P8: PCH_45_FROM_KERNELBASE+0x0000000000006C74 P9: P10: Angefügte Dateien: \ Problemsignatur: P1: 187 P2: 1 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Angefügte Dateien: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180118-2305.dmp \\?\C:\WINDOWS\TEMP\WER-186471656-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER65FF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER660F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER661F.tmp.txt Diese Dateien befinden sich möglicherweise hier: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_187_d575f1aa56d5980e96c5947bd10f9d19b74ad53_00000000_cab_29adc507 Analysesymbol: Es wird erneut nach einer Lösung gesucht: 0 Berichts-ID: 8ce5755d-ddc6-4301-bcf6-a13ac4bab7f3 Berichtstatus: 268435456 Bucket mit Hash: 1001

gonna try my luck again with the 396 later.. hope dies last^^