in Search
Untitled Page

ARCHIVED FORUM -- April 2007 to March 2012
READ ONLY FORUM

This is the first Archived Forum which was active between 17th April 2007 and 1st March February 2012

 

Latest post 08-10-2009 2:36 PM by Ezz. 6 replies.
Page 1 of 1 (7 items)
Sort Posts: Previous Next
  • 08-07-2009 12:44 PM

    • Ezz
    • Not Ranked
    • Joined on 03-04-2008
    • Posts 10
    • Bronze Member

    Picture-in-Picture Issue

    Hi All,

    I was just reprogramming my BEO5 using the new version 3.x software and noticed that if you modify the source buttons (eg. change the TV button by add an Icon instead of displaying text "TV"), save the configuration and then cycle back through the tabs (i.e. select "choose products" -> "connections" -> "logos" -> "edit" and finally "view") to check the configuration. If you then test any of the picture in picture options in the view tab the "picture-in-picture" command is missing?

    Cheers,

    Errol

  • 08-07-2009 4:19 PM In reply to

    Re: Picture-in-Picture Issue

    You are correct, it is another of the outstanding software bugs in the Beo5 Configuration Tool

    Regards Keith....

  • 08-08-2009 5:44 AM In reply to

    • Ezz
    • Not Ranked
    • Joined on 03-04-2008
    • Posts 10
    • Bronze Member

    Re: Picture-in-Picture Issue

    Keith,

    Thanks for the reply and I thought the tool was (a) An great improvement and (b) My configuration was perfect :-(

    Is there any way of adding the icons to the GlobalKeySpecification.xml such that is automatically uses these at buildtime and hence avoids omitting Picture-and-Picture command if you change the source icons?

    The other problemette still seems to be if you enable "DVB-T/S UK", then goto back and select "Set Source Logical Connections", "DTV" now reads "TV". This may just be a display issue and not impact the config!

    Finally, I built a Hitachi.xml which works well but I struggling when creating a hardkey command using the NEC format. How take something like:

            <source_subItem stName="HITACHI\Vol +" stCaption="Vol +" stMenuCaption="Vol +" stScreenType="0" stIR="NEC:GlobalManual=1#IRSEQUENCE=NEC#BITS=111101010000101010110111010010001#ALTBIT=#MARKFLANK=578#SPACEFLANK=578#SPACE2FLANK=1708#PRESIGNALHI=8993#PRESIGNALLO=4496#Pause1=65000#Pause2=65000#Carrier=38#REPEATSIGNAL=1#Comment=NEC 32bits" stLeave="Rel 1" stIRVideoOp1="F0:TV:" stIRVideoOp2="F0:TV:" stIRVideoOp4="L_F0:TV:" stIRVideoOp5="F0:TV:" stIRVideoOp6="F0:TV:" stIRAudioOp1="F0:RADIO:" stIRAudioOp2="F0:TV:" stIRAudioOp4="L_F0:TV:" stIRAudioOp5="F0:RADIO:" stIRAudioOp6="F0:TV:" stIRVideoOp5Link="L_F0:TV:" stIRVideoOp6Link="L_F0:TV:" stIRAudioOp5Link="L_F0:RADIO:" stIRAudioOp6Link="L_F0:TV:" stIRVideoOp2Av="F0:RADIO:" stIRVideoOp4Av="L_F0:RADIO:" stIRVideoOp6Av="F0:RADIO:" stIRVideoOp6AvLink="L_F0:RADIO:" nPage="1" nX="426" nY="70" nWidth="213" nHeight="25" nRowFinal="3" nColumnFinal="2" />

    and turn it into a hardkey format (ie. wheelleft)?

     

    Cheers,

    Errol

  • 08-10-2009 3:22 AM In reply to

    Re: Picture-in-Picture Issue

    Errol,

    I agree that the version 3.0 tool has many functional improvements, unfortunately it has also created several major software bugs including issues which did not exist in the previous version.

    You certainly could add items to the GlobalKeySpecification.xml and whilst it should work I would not recommend it because it may well show up unknown issues because it would not have been tested with the current tool version. In my view, the best and safest way is to add your requirements to the product XML file because most things you would wish to do on a regular basis would be associated with a product, whether B&O or 3rd party.

    I have not looked at the "DVB-T/S UK" issue you raised but I expect that this is associated with the fact that on later Beovisions the TV button can be assigned to TV and the software team have assumed this is a fact for all TV's when it is far from true.

    With regards to your Hitachi.xml source line for volume up which I can confirm has a standard NEC protocol address code of HEX 50AF and the vol+ command code of 12ED.

    If you are going to use the firmware generated NEC code as you have done, then you need to know about a flaw (software bug) in the repeat code section which means it does NOT conform to the NEC spec. This means about 40% of products which use the NEC protocol will not work correctly, but I have produced a workaround for the problem which works 100%.

    When you press a button it sends a code with the standard start bit of a pulse of 9 milli seconds and a pause (space) of 4.5 milli seconds. If you hold the button it does NOT send the command again, but sends a start bit of 9 milli seconds followed by 2.25 milli second pause then one (1) data bit. The problem is that the Beo5 sends a standard pause of 4.5 milli seconds so the receiver thinks its the start of a new command when it is not. See the diagram below to fully understand the situation.

     

    Having said all that when it comes to volume up and down you don't want a repeat signal at all, you want one seperate signal per click as you turn the remote wheel and that's the next problem to overcome because it still does a repeat signal when you don't want it.

    I have created a Hitachi Generic XML file for you to test and look at the code which resolves your problem.

    The following hard keys only have been programmed STEPUP, STEPDOWN, VOLUME UP, VOLUME DOWN, PLAY, STOP and you can download it from HERE

    Extract the file from the ZIP file and extract to C:\ which will automatically put the file in the correct directory of the Beo5 Configuration Tool

     

    Regards Keith....

  • 08-10-2009 7:00 AM In reply to

    • Ezz
    • Not Ranked
    • Joined on 03-04-2008
    • Posts 10
    • Bronze Member

    Re: Picture-in-Picture Issue

    Hey Keith,

    Thanks! It it's all good and is working like a dream.

    I've tried to add an image into the product.xml (i.e. stImage) but it still displays the text string value. I'm not sure if it's possible or I need some other command?

    Thanks your the man.

    Errol

     

  • 08-10-2009 9:28 AM In reply to

    Re: Picture-in-Picture Issue

    Errol,

    You cannot just add stImage="fred" you have to define "fred" in the resources section at the begining of the file

    For example:-

    <resource>
        <image stName="fred" stFile="Images\Button.bmp" />
    </resource>

    Regards Keith....

  • 08-10-2009 2:36 PM In reply to

    • Ezz
    • Not Ranked
    • Joined on 03-04-2008
    • Posts 10
    • Bronze Member

    Re: Picture-in-Picture Issue

    Keith,

    Soz! School boy error I was added the stImage command to the product line instead of source_item line. All is working as you've suggested thanks again for your help.

    Regards,

    Errol

Page 1 of 1 (7 items)