BleepBloop

[KingArgyle]

Sorry, I've been on the road for the last week and without internet access.

Anyway, BleepBloop won't work on the MVP because of the way it is designed.

On a PC it uses the default sound device that is in the PC to play the sounds. It does this by capturing the KeyDown event messages before they are put on the Windows Queue. After processing them, it passes them onto windows so that the events may be processed by the various plugins and functions within GBPVR.

[jam40jeff]

OK, that is how my Jukebox plugin was working too, because the MP3 decoder I am using can play more files than the built-in GB-PVR one. Now I have conditional code to use this only if GB-PVR is being run on a computer, and play the file through GB-PVR if on an MVP.

[KingArgyle]

Actually, I started working on an implementation for the MVP, but because of the way the MVP and GBPVR interoperate, it wasn't going to work. Mainly because only one audio file can be played at a time. This would have caused problems for those that are using their MVP as an audio jukebox, because everytime BleepBloop would start to play it's file, it would stop the current audio file to play it's sound. Same thing for watching a video.

So it's more a limitation of the MVP than it is the way BleepBloop is designed.

[jam40jeff]

Yeah, that's what I've found with the Jukebox plugin. There are just some things that can't be done on the MVP.

[KingArgyle]

Just uploaded a set of three sound files for Bleep Bloop. These follow a cartoon theme so watch out for falling anvils.

http://www.bladerhq.com/pmwiki/pmwiki.ph...BleepBloop

[reven]

lmao, classic

[stefan]

I installed BleepBloop a *long* time ago. Never got it to work, couldn't figure out why, and never bothered investigating it. I even forgot about it. Yesterday, I thought I should try to switch from "direct access" style remote controlling to using ir.exe. All of a sudden my tv started bleepblooping =) Cool, and it actually does make me know if a remote command was received or not. So far so good. An unexpected feature of ir.exe is that every time I shut down my tv, gbpvr jumps into net radio mode :-) *That* I must investigate more =)

[j3flight]

I installed BleepBloop a *long* time ago. Never got it to work, couldn't figure out why, and never bothered investigating it. I even forgot about it. Yesterday, I thought I should try to switch from "direct access" style remote controlling to using ir.exe. All of a sudden my tv started bleepblooping =) Cool, and it actually does make me know if a remote command was received or not. So far so good. An unexpected feature of ir.exe is that every time I shut down my tv, gbpvr jumps into net radio mode :-) *That* I must investigate more =)

Do you have a philips tv?
If so you have the same problem that I do...

Unfortunately, the Hauppauge remote and some philips remotes use similar IR signals and, well, they can interfere with one another. In fact, all the number buttons on my philips remote can also act as the Hauppauge number buttons. Strangely enough, the same is not true of the reverse...

Not much you can do about it, short of getting a new TV.

Jason

PS If you read the top of irremote.ini, the hauppauge developers mention this exact problem.

[stefan]

Yes, I have a Philips tv. It's not too big a deal, it seems to only affect me when I shut off the tv... what is more strange (at least to me) is that it only happens if I use ir.exe, not when I use "direct access to hauppauge remote"?

[valkokir]

Just tried bleepbloop for the first time and I really like it.

I also have a philips TV. You can solve the IR conflict problem by commenting out the old hauppauge remote.

right near the top of irremote.ini are the following lines

; map RC5 System Codes to button "name" lookup table
; Note: 0 (classic remote) conflicts with standard "philips" TV remotes
[SystemCode]
;0=HCWClassic
31=HCWPVR


obviously hauppauge is aware of the issue as their file even says it.
Notice the semi-colon before "0=HCWClassic" this removes functionality of the old Hauppauge remotes and eliminates the conflict. I have a PVR-250 and therefore the newer remote. the HCW classic remote should just be the one that came with their old WinTV go cards, etc.

Make sure you save irremote.ini and then restart the ir program before testing