Xmedia Recode stopped working and crashes
miffed
"Xmedia Recode" is mostly a front end to ffmpeg for converting videos
from one format to another and with many other features.
<http://www.xmedia-recode.de/index.html>
I downloaded and installed portable v2.2.4.2 of Xmedia Recode last week
following Yrrah's [UPDATE] post about it.
I used it for 2-3 days to do 20 odd conversion tests and it worked fine.
It produced some good results, I especially like the frame trim option.
But on the 3rd day when I clicked the shortcut to start it, the
"XMedia Recode.exe" ran but then crashed out before the GUI appeared.
I rebooted and tried again, same problem.
I checked Task Manager and saw the executable appear for maybe 5-10
secs before disappearing.
It looks like a programming error in Xmedia Recode.exe.
I e-mailed the author 3 days ago at <sup...@xmedia-recode.de> and sent
him a copy of the program crash dump a day later. I've received no
reply from him. That may be because he doesn't speak English, I dunno.
Is there a solution or do I dump this program from my system?
TIA
miffed
>Did you install it or use the portable version? Try uninstalling it
>and downloading the portable version and see what happens. It might
>crash again as there could be a dll conflict somewhere. One way to
>check is to use Sysinternal's Process Explorer and check the threads
>that are run when the Xmedia exe program is running.
It was the portable version that I originally installed and it ran OK
for two days. But you may be right about a possible conflict arising.
I've now downloaded and installed the setup version and - hey - the
program runs AND the GUI comes up :-))
I think you may mean Sysinternal's Process Monitor? I ran this and
it's all mumbo jumbo to me. Lots of "name not found" entries and other
stuff that looks kinda odd. But that applies to a lot of processes,
not just Xmedia Recode!
>The same thing recently happened to me with SuperAntispyware. I had
>to uninstall and reinstall. I think it might be because of a registry
>cleaner I used. I'm pretty advanced with handling the registry and
>deleting proper keys and strings, but you never can be quite sure.
>
>Have you used a registry cleaner (or any file cleaner) recently?
Yikes! I run a reg cleaner every night! I have also considered this as
possible cause of the problem. From now on I'll examine all reg entries
highlighted for deletion before actually deleting them and err on the
side of caution.
I sure hope this newly installed version stays running OK because the
program is actually quite good with some neat features...some of my
tests included small MPG vids being converted into FLV with no loss of
quality but a huge saving in disk space.
Thanks for some good ideas.
M.L.
>>Did you install it or use the portable version? Try uninstalling it
>>and downloading the portable version and see what happens. It might
>>crash again as there could be a dll conflict somewhere.
>
>It was the portable version that I originally installed and it ran OK
>for two days. But you may be right about a possible conflict arising.
>
>I've now downloaded and installed the setup version and - hey - the
>program runs AND the GUI comes up :-))
This is exactly why I'm not a fan of many portable versions. Too
crashy in my experience.
pooky
news:3tpb36d99qmtgsq6u...@4ax.com:
> This is exactly why I'm not a fan of many portable versions. Too
> crashy in my experience.
>
My experience is precisely opposite.
miffed
>>It was the portable version that I originally installed and it ran OK
>>for two days. But you may be right about a possible conflict arising.
>>
>>I've now downloaded and installed the setup version and - hey - the
>>program runs AND the GUI comes up :-))
>This is exactly why I'm not a fan of many portable versions. Too
>crashy in my experience.
I don't have much experience of crashing but many so-called portable
apps still write to the registry which makes them non-portable
according to most peoples' understanding the term.
In some cases, the only benefit one gets is that they usually don't
have an installer process and will run out of the box, but that by
itself doesn't make it portable IMO.
-miffed
miffed
>miffed <nowhere@there> wrote
>> Yikes! I run a reg cleaner every night!
>
>That's probably what caused the program's inability to run.
Quite likely. It may have been a program I use weekly to thorougly wash
the system: NirSoft's "CleanAfterMe", which can dig quite deeply.
It raises a question about whether Xmedia portable version I installed
is truly portable. I'm still waiting to hear from the author but I don't
hold out much hope.
Whatever, the installer version is now working OK for the moment.
-miffed
miffed
>miffed <nowhere@there>:
>
>> many so-called portable
>> apps still write to the registry which makes them non-portable
>> according to most peoples' understanding the term.
>>
>> In some cases, the only benefit one gets is that they usually don't
>> have an installer process and will run out of the box, but that by
>> itself doesn't make it portable IMO.
>
>registry.
Assuming you've checked that out and aren't guessing, it adds weight to
the view that there was a problem with the v2.2.4.4 portable build which
the sudden new release of v2.2.4.4 may resolve.
-miffed
miffed
>>Whatever, the installer version is now working OK for the moment.
>>
>
>The only way you can tell is to clean your system by uninstalling the
>program, and using a program such as Regseeker or Nirsoft's scanner to
>search for all references to Xmedia Recode, and other key dll's in the
>program directory. Once again, be careful as to what's deleted and
>keep Regseeker backups or an entire Erunt backup of your registry
>before editing.
>
>Then when you think you may have deleted all references to the
>program, use Zoft's Uninstaller to monitor what happens to your
>registry after starting the portable version of Xmedia Recode. That
>would mean running Zsoft before extracting the portable zip file, and
>again after running and closing the program to finish the analysis.
>The view the zulog file.
I'll keep that advice handy thanks. Meanwhile the installer version is
still working OK and I note a sudden new release v2.2.4.4 has been
released which I speculate resolves the previous problem I reported
with the portable build.
-miffed