Your Universal Remote Control Center
RemoteCentral.com
Philips Pronto Professional Forum - View Post
Previous section Next section Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Topic:
PEP questions
This thread has 13 replies. Displaying all posts.
Post 1 made on Friday July 9, 2010 at 16:06
micro
Long Time Member
Joined:
Posts:
December 2004
23
I have been using a 3000 for a few years which has finally broken and have moved to a 9400 and have a couple of basic questions.

First off I have converted my 3000 config to the 9400 using the PEP 9400 (but it's B&W).
When I created my 3000 I used Daniel Tonks example and had a page for all my codes per device.

1) Can I have multiple projects open at the same time as I rebuild in color?
2) Is the correct way to store codes on the component page? And can I delete the Codes pages I have?

Thanks

M
Post 2 made on Friday July 9, 2010 at 16:54
Guy Palmer
Active Member
Joined:
Posts:
June 2008
648
There are two versions of the PEP software, version 1 and version 2. Although you probably used PEPv1 to convert your config, you should use PEPv2 to update it.

Assuming you are using PEPv2:

1) Can I have multiple projects open at the same time as I rebuild in color?

No, but you can merge the old and configs together whilst you edit the new one.

2) Is the correct way to store codes on the component page? And can I delete the Codes pages I have?

No, you should use the database as discussed in the manual.
Post 3 made on Friday July 9, 2010 at 18:59
Lowpro
Select Member
Joined:
Posts:
March 2004
2,044
There is no reason to use PEP v2 unless there are specific features that you desire only offered by PEP v2. At anytime you can open your PEP v1 XCF in PEP v2 and save it as a PEP v2 file. I don't use PEP v2 myself. In my case it would be a huge waste of time due to the gimped user interface and lack of core features always available per prior Pronto editors which I refuse to do without. I'm perfectly content to continue using PEP v1 in conjunction with the proper firmware. PEP v1 provides a far superior user interface for starters. Just compare the traditional tree/page view and properties window of PEP v1 to the reinvention of said items in PEP v2. PEP v1 is clearly superior in this regard. PEP v1 also retains many of the features all prior Pronto editors offered such as the ability to have multiple configuration files opened at the same time, the "Link" action, and the ability to store learned IR codes to buttons. I don't want to use the merge function for simple copy and paste operations between configuration files. I don't want to create a commonly used macro when I can just link to the action list of any button in my configuration file from a given button. I don't want to use My Database to store my IR codes. In a word, PEP v1 gives you a choice. PEP v2 does not. And as I stated in my opening comments, you can open a PEP v1 XCF in PEP v2 at anytime, then saving said file in PEP v2. Just keep in mind that once saved in PEP v2 that given file will no longer open in PEP v1.
LP Related Links:
View my profile to access various
links to key posts and downloads.
Post 4 made on Friday July 9, 2010 at 19:09
Guy Palmer
Active Member
Joined:
Posts:
June 2008
648
Micro,

Lowpro's views on PEPv2 versus PEPv1 are well known and rather idiosyncratic. PEPv2 is the modern version of the software and the only version that supports the various new features that Philips have been introducing, as well as (in my opinion) being far superior.
Post 5 made on Saturday July 10, 2010 at 02:09
buzz
Super Member
Joined:
Posts:
May 2003
3,351
micro,

I'm not sure exactly where you are in the process. Do you have a working program, with the old artwork? Are you working in PEP2?

If so, then the code pages are not necessary because the links to the codes have been removed. If you want to keep the code pages, simply hide them. Mostly, I have no need for code pages any more, but some of my more advanced ProntoScript programs are using code pages again.

In your TSU3000 days, changing a device, perhaps replacing a DVD player with a BluRay, would usually require tracking down all of the DVD codes and replacing them. Many of us used code pages to minimize this effort. Having all of the codes in one spot saved us the trouble of tracking down every button that may have used a DVD code.

The new database is device oriented and one can simply replace model x with model y and know that all of the codes are swapped.

Replacing artwork is somewhat easier now because one can use drag and drop from button to button. When I converted programs, I would define a course grid, drag and drop the new artwork on a button, then drag the button to a nearby grid intersection. This may not be the final location, but it is close enough to get a program converted and usable. Later, I can fine tune the locations.
Post 6 made on Saturday July 10, 2010 at 03:03
Lyndel McGee
RC Moderator
Joined:
Posts:
August 2001
12,385
PEPV2 does allow you to resize large graphics via drag handles without requiring an image editor. Downsizing is somewhat OK but upsizing should really be done with original images and a good image editor.
Lyndel McGee
Philips Pronto Addict/Beta Tester
Post 7 made on Saturday July 10, 2010 at 17:23
alpha
Long Time Member
Joined:
Posts:
September 2003
258
I also went from a 3000 to a 9400. In the end I wound up with a complete redesign. The transferred database was not easy to understand. In some cases there were no titles from codes I learned. So I started a new configuration. 90 % of the equipment I used is in the default database , which is much easier to use than the 3000. I would suggest once you get the 9400 working with the old codes start creating a new configuration from scratch.

Try out the new project tool. It might have everything you need to get started.

Once you start a new configuration file you can add equipment profiles to your "My Database" .

1. Create a New Activity. Use previous designs or a template. ( In this case a Sony DVD PLAYER )
2. Enter the Pronto Database and add equipment profiles (Sony DVD ) to your "My Database" .Close it .
3. Then in the building Blocks section under Equipment Codes select the equipment(Sony DVD ) for that activity.
4. Drag and drop the codes to buttons.

Use the Chanel Macro Action to auto-magically add Number Codes to buttons with numbers.
If you use the Television logo Buttons to go to a channel like SYFY , ABC, HBO, BBC
1. Label the button as the Chanel number.
2. Select " none " for the size of the font.
3. Use the Chanel Macro Action.
4. Select the equipment.
5. add a delay (.20 ) seconds
Once the equipment and the delay is selected just use the action on each button.

You could design an activity with codes from all of your equipment. Each page is a device. As a backup, I have one too . It has my original codes from the 3000 . But I don't use it for editing the config. I usually drag and drop from the database. Once you get use to it it works faster.

Check out some of the designs in the file area. And don't forget that now that you have a Color remote you can use some of the 7000-7500 color configurations with modification.

Last edited by alpha on July 10, 2010 17:50.
Project Boredom 2 is here. [Link: mediafire.com]
------------------------
Check Version 1 & 2 out in the files section.
Post 8 made on Sunday July 18, 2010 at 21:40
Lowpro
Select Member
Joined:
Posts:
March 2004
2,044
On July 9, 2010 at 19:09, Guy Palmer said...
Micro,

Lowpro's views on PEPv2 versus PEPv1 are well known and rather idiosyncratic. PEPv2 is the modern version of the software and the only version that supports the various new features that Philips have been introducing, as well as (in my opinion) being far superior.

Yes, I am the lone voice here on the forums it seems with respects to my preference of PEP v1 over PEP v2. That being said, I don't appreciate being mischaracterized. PEP v2 may be the "modern" version of the software and the only version that supports various new features that Philips has introduced or will introduce, but that doesn't make it the right choice for everyone. And as I pointed out twice in my prior reply, one can open their PEP v1 XCF in PEP v2 at anytime if they decide they'd rather use PEP v2.
LP Related Links:
View my profile to access various
links to key posts and downloads.
Post 9 made on Monday July 19, 2010 at 00:14
Guy Palmer
Active Member
Joined:
Posts:
June 2008
648
On July 18, 2010 at 21:40, Lowpro said...
I don't appreciate being mischaracterized.

And I mischaracterised you how?
Post 10 made on Monday July 19, 2010 at 11:46
Lyndel McGee
RC Moderator
Joined:
Posts:
August 2001
12,385
Guy,

Micro called LowPro's views idosyncratic. That's what he's pointing out.
Lyndel McGee
Philips Pronto Addict/Beta Tester
Post 11 made on Monday July 19, 2010 at 15:50
Guy Palmer
Active Member
Joined:
Posts:
June 2008
648
How is the word "idiosyncratic" mischaracterising LowPro's views? As he himself says "I am the lone voice here on the forums it seems with respects to my preference of PEP v1 over PEP v2".
Post 12 made on Tuesday July 20, 2010 at 02:31
Tamvegas
Long Time Member
Joined:
Posts:
September 2005
24
I just got a TSU9600 a week ago and am at the beginning of the learning process. I've had a TSU7000 for several years and borrowed greatly from Daniel Tonk's program as well as very heavily from LowPro's for his DVD carousel library macro's, visuals etc.
The process of translating this into PEP2 is a bit daunting and I wonder if doing the initial translation is going to be much easier in PEP1? I do miss being able to have 2 files open at once and having a similar interface to ProntoProNG. Although I also see advantages to PEP2.

I would like to ask LowPro how well his DVDGallery translated to PEP1.1 and also ask for any tips on re-creating the macros etc.
I have installed both PEP1 and PEP2.
Lastly, I have already updated my 9600 to the latest firmware. Is this still compatible with files created in PEP1.1? Or do I need to revert to an earlier firmware?
Thanks for any advice and I apologise to the OP for a slight thread hijack :-).
Post 13 made on Tuesday July 20, 2010 at 13:33
adrian ballard
Founding Member
Joined:
Posts:
May 2001
68
Just to throw in my .02...
When I migrated to the 9400, I tried both editors and looked @ the pros and cons of each. My final decision was to utilize PEPv1 for the majority of the 'build'. I did abandon the 'hidden page of codes' concept and implemented the use of the custom device database in PEPv1. My reasoning for this is fairly straightforward:
I can build whatever I want in PEPv1 (utilizing the DB of course) and prefer to do so as I still prefer the GUI over PEPv2. I can do any ProntoScripting I want under PEPv1 (it just may not run in the simulator). So I design and SAVE under PEPv1. Then when its upload time, I open it with PEPv2, tweak the WiFi settings (WPA) and upload.
That way I get the best of both worlds.....
Post 14 made on Tuesday July 20, 2010 at 23:35
Lyndel McGee
RC Moderator
Joined:
Posts:
August 2001
12,385
For all of you who might be contemplating PEPV1.

One issue with later firmware you will want to consider is...

If you have ProntoScript in firm keys note that you MUST use a version of the firmware earlier than 7.1.21 or else you MUST recode your firm key scripts as onPress handlers that are initialized at page or activity level.
Lyndel McGee
Philips Pronto Addict/Beta Tester


Jump to


Protected Feature Before you can reply to a message...
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now.

Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.

Hosting Services by ipHouse