Open TerminatorSAW2k opened 1 year ago
I'll look into it when I'm back on my Windows machine
@TerminatorSAW2k, open your config.toml file. It will likely be full of 'Null' after setting via GUI. Delete the contents and paste the example from the FlexASIO github. Save.
FlexASIO GUI should now load. I saved a new test file as FlexASIOGUI.toml and the contents looked good so I am not sure what caused the initial error for me (FlexASIO_GUI not loading)
Unfortunately, the suggestions don't help, it doesn't even generate the .toml files.
Therefore, the error will not be due to a non-existent .toml file.
I have also tested your solution, the gui overlay is not displayed on the Client 1, on another PC it works perfectly.
Looks like this may have to do with the Nett library which is not being developed any more. Will have to figure out how to easily replace it
Give the 0.35 release a try. I've replace Nett with Tomlyn. Also, delete your current flexasio.toml file if possible (or rename it) see: https://github.com/flipswitchingmonkey/FlexASIO_GUI/releases/tag/v0.35
Hello, thank you for the quick update.
However, the error is still present on my client even after the new update.
I think it is also due to .net.
Here are the errors from the event viewer:
Protokollname: Application Quelle: Application Error Datum: 29.10.2022 12:14:09 Ereignis-ID: 1000 Aufgabenkategorie:(100) Ebene: Fehler Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Computer: DESKTOP-9GG4TR2 Beschreibung: Name der fehlerhaften Anwendung: FlexASIOGUI.exe, Version: 1.0.0.0, Zeitstempel: 0x6331eb0e Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.19041.2130, Zeitstempel: 0xb0fac6c9 Ausnahmecode: 0xe0434352 Fehleroffset: 0x000000000002cd29 ID des fehlerhaften Prozesses: 0x1e88 Startzeit der fehlerhaften Anwendung: 0x01d8eb7f2ea57ffe Pfad der fehlerhaften Anwendung: C:\Program Files\FlexASIOGUI\FlexASIOGUI.exe Pfad des fehlerhaften Moduls: C:\Windows\System32\KERNELBASE.dll Berichtskennung: b5aa1db3-c05e-4357-bd64-6d5d89c30320 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Ereignis-XML:
strange :(
The funny thing with my office PC (Client 2) runs the tool 1A without problems, even the new version.
Hello I was able to solve my problem.
Error 1 was with me I have 2 users USER Windows folder one with the name and one with info ... for the online Windows account.
But the FlexAsio Config file had to be in the info user name, then it was recognized correctly.
I'm just surprised that the Gui had not recognized the 2 user accounts but only the account with the username without info...
My Asio LINK PRO routing software has apparently previously also blocked the GUI for normal call, this had only worked when I the Config FlexAsio file in the user account: "Info" had stored.
Now I can call the Gui directly in the Asio Link PRo at any time for configure and change as desired.
Thanks for your help and effort.
Hello, i have a Problem with this tool:
The flex asio gui does not start when used again.
How i can fix it?
This is the information I have from the event display:
Protokollname: Application Quelle: Windows Error Reporting Datum: 24.10.2022 14:53:25 Ereignis-ID: 1001 Aufgabenkategorie:Keine Ebene: Informationen Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Computer: DESKTOP-9GG4TR2 Beschreibung: Fehlerbucket 1494313614435414010, Typ 4 Ereignisname: APPCRASH Antwort: Nicht verfügbar CAB-Datei-ID: 0
Problemsignatur: P1: FlexASIOGUI.exe P2: 1.0.0.0 P3: 62b2fac5 P4: KERNELBASE.dll P5: 10.0.19041.2130 P6: b0fac6c9 P7: e0434352 P8: 000000000002cd29 P9: P10:
Angefügte Dateien: \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FA8.tmp.mdmp \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4268.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER42B7.tmp.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER42D4.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4314.tmp.txt
Diese Dateien befinden sich möglicherweise hier: \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FlexASIOGUI.exe_f0138a15e9cb96ec3edc8ed59928d49da24924d_adcf0c17_a4f9d6aa-d0d9-489c-95a8-63df4c19293c
Analysesymbol: Es wird erneut nach einer Lösung gesucht: 0 Berichts-ID: 450550fe-7790-44fa-8197-5a8870e999bb Berichtstatus: 268435456 Bucket mit Hash: 8f87e7ef004374ecd4bcde50ab73effa CAB-Datei-Guid: 0 Ereignis-XML: