With the full-blown manual of v1 available, I'm tempted, as I'm just commencing my foray into the Pronto Professional, to simply program it with v.1.

Have many users continued to use v.1 despite the existence of v.2? Pros and cons?

Thanks,

Nick

I started with v2, so I can't comment on the benefits of v1. There are however a large number of people that still prefer it due to some functionality being removed and replaced with newer techniques. This angered a number of long time pronto configurators as they relied on some of these techniques to quickly configure and deploy pronto programs. Hence they stayed with V1 due to the large amount of time that would have been required to convert their toolkits to the new version.

My recommendation: If you haven't built anything using v1, then don't bother with it. You're simply delaying the pain and suffering pre-existing v1 users are trying to avoid by not upgrading. Then there is always the possibility that Philips may decide to 'sundown' the v1 product. Sundown being 'buried', 'dead' and 'no longer supported'.

You can see multiple pages side by side in V1. Cannot do this in V2.

I have tested V2 but have not used it in production. Prefer V1 until you can see properties while a page is zoomed which V2 does not allow?

I agree with GuerillaBuild 100%. Whilst the v2 interface has some very annoying 'features', I think it provides a much more structured environment that v1. It particular, I find its distinction between 'devices' and 'activities' - a major difference between v1 and v2 - very helpful.

I tried to use V.2 but after 10+ years of programming Pronto in a "device" oriented environment I just don't like it. I don't care for the code database concept, I use pages in my devices to store my codes and link them that way. I guess I am just to used to the old way. I really hate that you can only see a page at a time and if you blow it up you can't see properties any more. This actually kept me from buying a 9800 to use in my theater.

Tom

For me

no link = no V2

I am happy with how the remote operates. Unless something extraordinary becomes possible that is not V1 supported I won't change. By extraordinary I mean like brouse web and pop corn.

Herb

The only thing I really like about V2 is that you can use custom fonts on the remote. I currently use PEPv2 only to download things to my TSU9800. Otherwise, I only use it to examine others broken or problematic files.

I used to participate in these forums on a daily basis. Unfortunately most of the posts these days relate to PEP v2 which I don't use, hence I don't post replies much anymore. Am simply not willing to spend time using v2 as I'd only be doing so in order to contribute to v2 related posts here. PEP v2 stands v1 up on its head. It's an attempt at reinventing the wheel and a bad attempt at that. PEP used to stand out from the pack in my opinion over the other remote control software out there I've used offered by other manufacturers. That's not the case any longer in my opinion per v2. For those of you that like v2 more power to you. It's all good. It's just not for me. I'm perfectly content to continue using v1 even if I can't take advantage of the new features offered by v2 in so far as it relates to what can be done with the remote as an end result.

I am with Lyndel in when I use PEP2, However I am contemplating biting the bullet as since I only do Prontoscript it doesn't much matter.

I agree, however I know of at least one manufacturer who has released their ProntoScript module saved as a V2 file, with NO V1 copy!!

I´m using PEP1 (PEP 2 only if no script for PEP1 is available).
Pronto I´m following for many years, but the design of PEP2 is unacceptable. I need several open pages because my programming is much visualized.
On my 24inch monitor the layout of PEP2 is not acceptable. Too small window for the active screen which I want to program. The difference is hard if you are used to work with PEP1. If you start with pronto system forget PEP1. Advantage of PEP2: the simulator is able to demonstrate scripts, not only pages/jumps like PEP1.
Hopefully PEP2 is becomming better main windows features like PEP1 soon.
PEP2 is faster in programming.
Until now no real need to change to PEP2.

Try dual 26" monitors and see just how small that 9600 page (640x480) or 9400 page (240x320) is and not being able to zoom and see properties is a SHOWSTOPPER.

Im a PEP1 man, but and there is a big but, i have no choice i have to go across to PEP2 TSU9800 and TSU9300 plus what ever new products come out, i took the leap to PEP2 kick and screaming :), but in the end its not that bad, i still miss links, but have got around that issue now, and some of the new scripts have to be loaded with PEP2, I miss the multipule pages on view :( but thats not going to change.

Its also very slow, but it gives me time to drink my cool beer, as its 28 deg over here at the moment :)), feel sorry for you guys in the northen hemisphere at the moment..

It can be too hot. We (in Melbourne) had the highest temperature ever recorded in any Australian capital city last Saturday - 46.4 deg C (That's 115.5 F).

Unfortunately that also meant we had our worst ever bushfires with 181 people offically dead and the final toll looks like it will be around 300. One town with 500 inhabitants had 100 people die.

At first not having the links was a giant pain in the ass. All my templates were designed with this technique, all codes were stored on hidden pages allowing easy linking to the proper device brand and model for the current project I was working on. Enter the TSU-9800 having no choice I started working with PEP2 at first I was completly confused, my entire concept of how to work with a Pronto was all backwards and upside down. After I forced my way through the first few however I began to see what they are trying to get at. The database for 232 codes greatly sped up my programming (it was a nightmare copying and pasting not to mention assigning ports on each and every code in PEP1).

All in all after some initial new learning learning curves I do really like PEP2 with the lack of multiple page views being the lone exception. The lack of button linking really isn't a big deal with the ability to drag codes to a button in a about 1 sec.