[fixed] Volume goes maximum after fast forwarding (1 Viewer)

[Makaveli]

MediaPortal Version: 1.1.0 RC3
MediaPortal Skin: StreamedMP 1.1.0.1303
Windows Version: Windows 7 x64 Ultimate
CPU Type: Core i7 860
HDD: ST3320418AS & WDC WD20EADS
Memory: 6 GB
Motherboard: (?) Dell Vostro 430 PC
Video Card: nVidia GeForce 8600 GT
Video Card Driver: NVidia Drivers 197.45
Sound Card: Onboard
Sound Card AC3:
Sound Card Driver:
1. TV Card: Hauppauge WinTV-HVR-2200
1. TV Card Type: PCI-E
1. TV Card Driver: WinTV 1.3d
MPEG2 Video Codec: SAF 5.00
MPEG2 Audio Codec: SAF 5.00
h.264 Video Codec: SAF 5.00
Remote: Hauppauge (came with TV card)
TV: Samsung
TV - HTPC Connection: HDMI

After I fast forward through a recording and the normal playing starts again, the volume goes up to the maximum (if I set it to mute before, it stays muted).

Attached are the logs.

 

[diskeeper]

AW: Volume goes maximum after fast forwarding

I can confirm this

 

[romuz]

Hi
backup your core.dll in MP folder and replace with provided

Report if issue has gone or any side effect with volume present.

 

[diskeeper]

AW: Volume goes maximum after fast forwarding

it works for me, no problems.

 

[chemelli]

patch commited. Romuz

Simone

 

[Makaveli]

It doesn't work for me. Still the volume goes up to the max.

 

[elliottmc]

It doesn't work for me. Still the volume goes up to the max.

Another report with subliminal logs I see.

Come on, do you want us to fix this, or are you just trying to wind us up?

Romuz has taken the time to look at your logs and to propose a fix, which has been confirmed by one other user.

When you replaced core.dll, did you have MPTray.exe running? This could prevent you over-writing core.dll. Maybe you didn't actually replace the file. Of course, I am only guessing.

Mark

 

[Makaveli]

It doesn't work for me. Still the volume goes up to the max.

Another report with subliminal logs I see.

Come on, do you want us to fix this, or are you just trying to wind us up?

Romuz has taken the time to look at your logs and to propose a fix, which has been confirmed by one other user.

When you replaced core.dll, did you have MPTray.exe running? This could prevent you over-writing core.dll. Maybe you didn't actually replace the file. Of course, I am only guessing.

Mark

Oh come on man.. the logs are attached in the first post. Although I don't think you can find anything about the volume in there, maybe other loglines can point into a direction of the problem.
And overwriting a file isn't that hard, so I think I can manage that... so you right about the guessing part.

If I can help by testing a file, solution or anything, I'm more than willing to do that. That's why I posted that the core.dll didn't fix the problem in my case. What more is there to say to that?!

 

[elliottmc]

It doesn't work for me. Still the volume goes up to the max.

Another report with subliminal logs I see.

Come on, do you want us to fix this, or are you just trying to wind us up?

Romuz has taken the time to look at your logs and to propose a fix, which has been confirmed by one other user.

When you replaced core.dll, did you have MPTray.exe running? This could prevent you over-writing core.dll. Maybe you didn't actually replace the file. Of course, I am only guessing.

Mark

Oh come on man.. the logs are attached in the first post. Although I don't think you can find anything about the volume in there, maybe other loglines can point into a direction of the problem.
And overwriting a file isn't that hard, so I think I can manage that... so you right about the guessing part.

If I can help by testing a file, solution or anything, I'm more than willing to do that. That's why I posted that the core.dll didn't fix the problem in my case. What more is there to say to that?!

Well, I assume that the reason Romuz was able to fix the problem so quickly was as a result of something in your logs. Maybe I am incorrect in this assumption.

I know you posted logs with the original core.dll, but the logs with the new version may provide a different story that will help someone fix this.

Bottom line - we do ask for logs, and this is for a very good reason. Clearly this core.dll fixes the problem for some users. We need help from other users if we have a chance of fixing this in all situations.

Mark

 

[Makaveli]

Ah, so maybe that can be asked in a normal fashion... because I do want this to be fixed and I want to help with it as well.

I will run MP in debug mode post the logs here.