Media Player - 32-bit better than 64-bit ? (resolved)
Posted: Sun Apr 29, 2018 7:17 am
Normally, I upgrade all software from 32-bit to 64-bit without hesitation, but I have a scenario here
which makes me wonder if it is perhaps better to stay with a 32-bit version (on a 64-bit system).
I am classical portable freeware user, with a media player on a USB stick,
which I use on different PC. My preferred media player is Sm Player (64-bit),
whose core engine is actually MPlayer. This is like those many media editors or converters,
where the handler program (such as XMedia Recode) uses a certain core engine (such as FFmpeg).
Here is where I ran into my dilemma: I started using some extra commands (via command-line)
for MPlayer via Sm Player (it allows that via Preferences), such as: unsharp masking, deband, quaility denoise, etc.
About the same time, I realized the my core engine MPlayer is 32-bit, so I upgraded it to 64-bit (for "better perfomance").
Now, if I use more than one extra command, my video begins to "stutter" on certain PCs only (those with less CPU power),
and by "stutter" I actually mean an audio-video desynchronization - audio beginns to lag behind video by a few seconds or more.
Analysis: should I just blame the extra commands, or did the 64-bit version contribute to the "stutter" at all ?
I do not have the right tools or the right knowledge to answer this. That is why I am posting this here.
Theories: (1) I know that a 32-bit version would likely lead to slower processing of CPU-intensive tasks, such as re-encoding videos. This "delay" would not show in video conversion (the conversion would just complete a bit later), but would likely show in a live perfomance - such as playing or broadcasting videos - as a "stutter" or with audio lagging behind video. According to this theory, a 32-bit version is more likely to cause the video "stutter" or audio-video desynchronization than a 64-bit version. The only reason I did not see this before is because I was not using multiple commands. Stay with the 64-bit version ! (2) On the contrary, a 64-bit application is more resource intensive on a 64-bit system (it uses the full potential of the system), and this higher use or resources contributed to the video "stutter" (together with the use of multiple commands). Switch back to the 32-bit version of the MPlayer core engine and the video "stutter" will be less likely to occur.
Which of the two theories is correct ?
Can You think of any other example where there is a benefit in keeping a 32-bit version of anything on a 64-bit system ?
I know that John Haller was slow to jump on the 64-bit "band-wagon", did You see some examples in his forum ?
which makes me wonder if it is perhaps better to stay with a 32-bit version (on a 64-bit system).
I am classical portable freeware user, with a media player on a USB stick,
which I use on different PC. My preferred media player is Sm Player (64-bit),
whose core engine is actually MPlayer. This is like those many media editors or converters,
where the handler program (such as XMedia Recode) uses a certain core engine (such as FFmpeg).
Here is where I ran into my dilemma: I started using some extra commands (via command-line)
for MPlayer via Sm Player (it allows that via Preferences), such as: unsharp masking, deband, quaility denoise, etc.
About the same time, I realized the my core engine MPlayer is 32-bit, so I upgraded it to 64-bit (for "better perfomance").
Now, if I use more than one extra command, my video begins to "stutter" on certain PCs only (those with less CPU power),
and by "stutter" I actually mean an audio-video desynchronization - audio beginns to lag behind video by a few seconds or more.
Analysis: should I just blame the extra commands, or did the 64-bit version contribute to the "stutter" at all ?
I do not have the right tools or the right knowledge to answer this. That is why I am posting this here.
Theories: (1) I know that a 32-bit version would likely lead to slower processing of CPU-intensive tasks, such as re-encoding videos. This "delay" would not show in video conversion (the conversion would just complete a bit later), but would likely show in a live perfomance - such as playing or broadcasting videos - as a "stutter" or with audio lagging behind video. According to this theory, a 32-bit version is more likely to cause the video "stutter" or audio-video desynchronization than a 64-bit version. The only reason I did not see this before is because I was not using multiple commands. Stay with the 64-bit version ! (2) On the contrary, a 64-bit application is more resource intensive on a 64-bit system (it uses the full potential of the system), and this higher use or resources contributed to the video "stutter" (together with the use of multiple commands). Switch back to the 32-bit version of the MPlayer core engine and the video "stutter" will be less likely to occur.
Which of the two theories is correct ?
Can You think of any other example where there is a benefit in keeping a 32-bit version of anything on a 64-bit system ?
I know that John Haller was slow to jump on the 64-bit "band-wagon", did You see some examples in his forum ?