I went to launch the portable app and a splash screen presented itself then disappeared, and after waiting several minutes nothing happened. I then opened the task manager to see InfraRecorder was sitting there and running but no GUI so I then ended the task and tried again and got same results. Should there be some list of some sort that will let users know which apps aren't currently compatible with Windows 10 to possibly prevent users from upgrading and rendering their commonly used apps useless.
New: Run-Command (Dec 2, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads Nov/Dec!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Did you run the portable zip from the InfraRecorder site?
It opens fine for me on Win10 Pro x64.
http://infrarecorder.org/?page_id=5
Odd enough I just tried both 32 and 64bit portable versions from their site and they do launch. So its something wrong with the portableapps version thats causing it to not launch.
Has anyone looked into this or am I the only one experiencing the inability to get the portableapps version of InfraRecorder to work on a Windows 10 x64 machine. As stated in previous comments, the portable versions offered on the devs site (http://infrarecorder.org/?page_id=5) appear to work. Its just the portableapps version that wont launch, well it launches, shows a splash screen and presents no GUI yet you can see the processes running in the task manager. Thought I'd resurrect this thread as I had to ditch the portableapps version and now start using the portable version supplied by the dev. Not something I'd like to do, as I prefer to use the portableapps launcher where all my preferred apps are stored. But I do hope this issue can be fixed or at least looked into.
I get same results here but where the launcher app
ears to be a special one not usual PA one Not sure if I cna figure where issue is?
“Be who you are and say what you feel because those who mind don't matter and those who matter don't mind.” Dr. Seuss
I have a Windows 10 x 64 and a Windows 10 x 32 and on both systems the same problem with InfraRecorder: When I started it I could see it in the task manager but there was no window to work with the program; all I could do was to terminate it in the taskmanager - not very useful.
I searched the internet and found a solution that worked for me:
Before the start of InfraRecorder, delete the files called Setting.xml (there are threee of them; I deleted them all!).
Then I started Infrarecorder, and look and behold, everything was normal again.
A file Data/settings/Settings.xml was created by the programm; I have not yet tried to understand this, but InfraRecorder works allright!
That is odd, it appears that this bug has been reported on their sourceforge page (three times) as well http://sourceforge.net/p/infrarecorder/bugs/
from what I read on the sourceforge forum seems to be more related to problems encountered after having managed to get the UI to show. The bug mentioned here is the UI not showing to begin with. What happens afterwards, or not, is a different subject.
EDIT: I did find one post related to UI not showing, but the same person mentioned that this only happened after several UI lockups when attempting to open a system folder. So this might also be caused by a corrupted file resulting from the many times he had to task kill the app
Com o Windows10, aconteceram alguns problemas: ao atualizar deu erro; algumas aplicações não funcionam como é o caso do Infrarecorder, o VLC, ... espero que ultrapassem este problema rapidamente, pois sou adepto das aplicações portáteis.
Since this post I had downgraded to Windows 7 as not to lose any functionality of my currently used apps. While using the tried and true Windows 7 I looked more into the matter I was having with Windows 10 and Infrarecorder, which was whenever launching the app via portableapps the GUI was never launched yet in the task manager you could see it was running. So, after a few Google searches I came across a method which appeared to be successful for those that had the same occurring problem. Which was to delete the settings.xml file, which can be found at this file path; while substituting "X" for whatever your drive letter is, X:\PortableApps\InfraRecorderPortable\App\InfraRecorder\settings.xml prior to launching the application. And now that I am back on Windows 10 it appears to be working.
as you need to delete the file everytime before starting.
Some testing reveals the problem is not with InfraRecorder itself, but is strictly caused by the included PortableApps launcher.
Starting either the 32 or 64 portable versions directly downloaded from the offical site ( http://infrarecorder.org/?page_id=5 ) works perfectly fine on Win10x64 (caveat: the settings file will however then be created in the respective program folders)
More Permanent Solution Found (for whatever it is worth, considering other, more serious issues)
If, like me, you found that you need to delete the settings.xml file everytime before starting the launcher then do this
The problem seems to be caused by the splash screen check.
Go to the Other\Source folder, you will find a file InfraRecorderPortable.ini.
Open this file in your preferred ASCII editor and remove the value for the option DisableSplashScreen=false to read just DisableSplashScreen= and save the file in the same folder as the portableapps launcher.
The check for a splash screen is not needed since the splash screen can already be disabled within the program itself.
Also, if you only run the 64bit but still want to keep the 32bit version handy, download the portable 64bit version from the original site.
unpack the content from the downloaded zip file in the app folder and rename the extracted folder to InfraRecorder64.
The included launcher is however not smart enough to decide which version to start depending on your platform, you will need to change the inifile to point to the desired InfraRecorderDirectory.
Alternatively, you could just skip the launcher altogether since the executables in the respective App folders already keep the settings within their own executable folder when started without the launcher.
EDIT: Resulting from a reference made earlier to the sourceforge bug forum, it seems that even after having managed to get the UI showing, you will run into more serious issues. I'm sorry to have to confirm these issues. In it's current state the progam is almost non-usable.
In my case, the file selector for images causes the progam to totally lock up when accessing the folder dropdown, it doesn't show any of the drives in This PC, so basically the only thing you can do is dump whatever it is you want to burn, on your desktop, and open it from there...
Well, I'm not even gonna risk wasting a DVD trying to find out if that will still work...
Thanks for your information
I think, disabling the Splash-Screen with the ini has nothing to do with the welcome-screen that you can disable This one is displayed by the PA.c-Launcher (PAL) and does not interfere with InfraRecorder at all as it is displayed even before InfraRecorder is launched. Btw. you can disable all PA.c splash screens with one switch in the options of the PA.c-Platform.
The 64-bit hack should be working as a local portable installation. It does not work on a flash drive when you encounter a 32bit system. The Launcher can do that in a more elegant way (PAL-Manual here). InfraRecorder has no 64-bit part for now as it simply is not needed afaict (I use the 32bit version without any restrictions on 64bit Win7/8/8.1 for years now).
I hate to necro-post but this still seems to be an issue. At first I bought into the corrupt installation theory until I installed it on a new Windows 10 machine from the PortableApps repository. I've read this thread and the solution seems inconclusive. I've tried deleting settings files and disabling splash screens, and although I can get the app to come up invariably it stops working the next time it is run.
Is there a permanent fix? Any help would be appreciated.
This issue should be fixed in 0.53 Rev 2. Note that you may need to fully uninstall and then install the new version for it to work properly. This revision has a greatly simplified launcher using PAL compared to the old custom launcher.
Sometimes, the impossible can become possible, if you're awesome!