Download Mix beta 2.5 created bye Homerdhalor
**Beta 2.5 update**
1 = skin added
2 = MP3 player correction
3= stabilized code on hits
4 = zoom added in portal scan and m3u "m3u zoom still being corrected" ok repared
5= sound added for each hit
6= escape added to exit full screen
7 = button added to remove the channel list and connection url during playback
8= in fullscreen mode channel list and connection url autocache
9= possibility to reset and put another url in m3u and scan
10 = ajout de la visibilité de l'upload du fichier dans le m3u
**known bug**
1= it can sometimes shift in the m3u player when you enlarge the window, but not in fullscreen
2= I will wait for your feedback
a few bugs have still been fixed and I will share them with you
It is common for executables created by tools like Auto PY to EXE to be detected as false positives by some antiviruses. Here are some possible reasons and solutions:
Suspicious behavior: Executables created by PyInstaller (used by Auto PY to EXE) may have behaviors that antiviruses consider suspicious, such as unpacking code at runtime.
Heuristics: Antiviruses often use heuristics to detect potential threats, which can lead to false positives for unsigned or uncommon executables.
Lack of reputation: Since your executable is not widely distributed, it does not have an established reputation, which can make it suspicious in the eyes of some antiviruses.
Possible solutions:
Sign your code: Obtain a code signing certificate and sign your executable. This can reduce false positives.
Submit your application to antivirus vendors: You can submit your application to major antivirus vendors to have it scanned and marked as safe.
Use alternative build tools: Try other tools like Nuitka or cx_Freeze that can generate fewer false positives.
Add your application to antivirus exceptions: For your personal use, you can add the executable to your antivirus exceptions.
Optimize your code: Make sure your code does not contain elements that could be considered suspicious (like unsecured network connections or system file manipulations).
Use reputable libraries: Avoid using little-known or potentially suspicious libraries.
Document your application: Provide clear documentation on what your application does, which can help when submitting to antivirus vendors.
It's important to note that these detections are likely false positives, but it's always a good idea to check your code to make sure it doesn't contain anything malicious or unintentional.
1 = skin added
2 = MP3 player correction
3= stabilized code on hits
4 = zoom added in portal scan and m3u "m3u zoom still being corrected" ok repared
5= sound added for each hit
6= escape added to exit full screen
7 = button added to remove the channel list and connection url during playback
8= in fullscreen mode channel list and connection url autocache
9= possibility to reset and put another url in m3u and scan
10 = ajout de la visibilité de l'upload du fichier dans le m3u
**known bug**
1= it can sometimes shift in the m3u player when you enlarge the window, but not in fullscreen
2= I will wait for your feedback
a few bugs have still been fixed and I will share them with you
It is common for executables created by tools like Auto PY to EXE to be detected as false positives by some antiviruses. Here are some possible reasons and solutions:
Suspicious behavior: Executables created by PyInstaller (used by Auto PY to EXE) may have behaviors that antiviruses consider suspicious, such as unpacking code at runtime.
Heuristics: Antiviruses often use heuristics to detect potential threats, which can lead to false positives for unsigned or uncommon executables.
Lack of reputation: Since your executable is not widely distributed, it does not have an established reputation, which can make it suspicious in the eyes of some antiviruses.
Possible solutions:
Sign your code: Obtain a code signing certificate and sign your executable. This can reduce false positives.
Submit your application to antivirus vendors: You can submit your application to major antivirus vendors to have it scanned and marked as safe.
Use alternative build tools: Try other tools like Nuitka or cx_Freeze that can generate fewer false positives.
Add your application to antivirus exceptions: For your personal use, you can add the executable to your antivirus exceptions.
Optimize your code: Make sure your code does not contain elements that could be considered suspicious (like unsecured network connections or system file manipulations).
Use reputable libraries: Avoid using little-known or potentially suspicious libraries.
Document your application: Provide clear documentation on what your application does, which can help when submitting to antivirus vendors.
It's important to note that these detections are likely false positives, but it's always a good idea to check your code to make sure it doesn't contain anything malicious or unintentional.
More Related Thread
Relate Threads