Guess we cross posted, as I deleted my original, wrongly worded post and changed it to the 2nd one. I was originally thinking about the early 60hz discussion days and locked vs unlocked and just typed without brain in gear. I am using 48hz locked, as you wisely suggest and have been for some time. Under 1.03 I had problems though.

As for the update on tonight's viewing using f/w 1.04 beta, I can report that ALL of MY previous issues appear to be fixed. No menu problems, no more tearing, no framerate jittery issues and, so far, no audio problems on switching. Where I have occasionally thrown brickbats before due to the ongoing bugs, I now can offer thanks that 1.04 is working fine - for me at least and for now. Good work. Thanks Dale for your help and sorry about the confusion on my part. Thanks DVDO/Josh for the new firmware fixes.

I too continue to be happy with 1.04

Using ProntoProEdit NG (v 2.1.8.0) pasting in the code for Auto DI from your utility 2.0.84, saving the IR command and reopening it, definitely changes the last value from 0001 to 0064. I'll have a chance to find out later whether it stops it working and will post.

mine changes too, but it has always worked fine.... VP30 had issues.. which are now fixed... but no issues with me and VP50 (even though the pronto does change the codes)

mine changes too, but it has always worked fine.... VP30 had issues.. which are now fixed... but no issues with me and VP50 (even though the pronto does change the codes)
Great. I thought that would be the case as checking back, the codes for Disp Profile 1 & 2 both did the same thing and both work fine.

can anyone who moved from 1.01 to 1.04 and has framerate conversion done by the DVDO - has this FW improved the framerate conversion performance of the already solid 1.01 firmware?

just to make it clear, I have no problems with frame rate conversion now (my panel only accepts 1:1 @ 60hz and I live in a PAL country) .. I use framerate conversion a lot.... so any improvement is good news....

Thanks for the feedback on the pronto edit and IR code issue. I do believe (and I have been wrong once in my life when I though I made a mistake, but actually did not (:-)). that all of the IR codes generated by my utility are correct. There are problems with some of the processing of codes within the VPxx but that is clearly getting resolved and I know for a fact that DVDO is working to bring a uniform structure to all of their automation protocols (IR and RS232).

For those interested, the IR patterns are generated from the tables in the ini file which apply to both the VP30 and the VP50. The individual entries are coded by model, option and firmware revision. It is therefore important to have the correct model stated (e.g. VP50), the installed options stated (e.g. SDI), and lastly the firmware revision in use (least important for IR generation). That was the reason I added the front end customization to the utility.
Once again thanks for the feedback.

I used ProntoEdit 4.05 to create a .ccf file for my MX-3000. As I stated, all the codes I created work except for the Auto DI. Can someone verify that they have a working version that I can import into the MX-3000 editor? If the Pronto editor is the problem, does someone have another work around for my situation?

If the display simply repeated input frames to arrive at the 120 Hz display rate, then, no, it would not eliminate 3:2 judder. Each frame from the source which occurred 2 times would be shown 4 times by the display, and each frame from the source which occurred 3 times would be shown 6 times by the display.

That makes sense. Thanks, Dale. Would this 120hz picture actually look more juddery than 60hz, or about the same?

Thanks for the feedback on the pronto edit and IR code issue. I do believe (and I have been wrong once in my life when I though I made a mistake, but actually did not (:-)). that all of the IR codes generated by my utility are correct. There are problems with some of the processing of codes within the VPxx but that is clearly getting resolved and I know for a fact that DVDO is working to bring a uniform structure to all of their automation protocols (IR and RS232).

For those interested, the IR patterns are generated from the tables in the ini file which apply to both the VP30 and the VP50. The individual entries are coded by model, option and firmware revision. It is therefore important to have the correct model stated (e.g. VP50), the installed options stated (e.g. SDI), and lastly the firmware revision in use (least important for IR generation). That was the reason I added the front end customization to the utility.
Once again thanks for the feedback.


Barry, thanks again for all your hard work - your utilities & programmes make my set up much, much easier to use!

Cheers,

Marcelo

Cal87

For the Auto DI there are three cases, (1) a VP50, (2) Not a VP50 and ABTDI Installed and (3) Not a VP50 and ABTDI Not installed.

I assume that since you are posting in this forum, you have an ABT50 and the utility is setup with its model being VP50.

Just checking to try and help you.

The DI auto IR codes are the same for cases (1) and (2) but it is different for case (3). There are also more setting possibilities for a VP50 (1) than a VP30 with the ABTDI card (2) installed.

The one for case 3 (VP30 with no ABTDI102 card) used to be called "Film Mode" and the settings were (0)Off, (1)Bias, (2)Auto. At one time bias was referred to as "Film"

I just got around to loadiing 1.04 and it looks like everything is ace's so far and that includes 24hz for my RS1.
This is the first time I used Barry Gordon's "Loader" utility for my DVDO firmware upgrades. Painless and so simple compared to what I've been using.

Again, thank you Barry, DVDO.

There have been known issues with tearing as you describe with some versions of the VP50 software, but I thought those were limited to 24 Hz locked output. There's always a potential problem or two with unlocked output which is set to be nominally the same rate as the input. First of all, you will get dropped or repeated frames. Secondly, it may be possible to get tearing under certain circumstances as the output rate will always be a little different from the input if they're not locked. This should be very rare, though. You could try setting the unlocked output rate to 59.93 Hz or 59.95 Hz to see if that cures the tearing problem. In general, I would always recommend running in locked mode unless you have a good reason not to.

Based on what I know of the VP50 frame rate conversion hardware, I wouldn't think you could ever get tearing with a 60 Hz input and a 60 Hz locked output. There was a hardware bug introduced in v1.03 which could cause problems in this mode, but that should be gone in v1.04. I'm not sure exactly what was in the 1.01 release, though. It's more likely that you would get tearing in unlocked mode than in a 1:1 locked mode (i.e., 60 Hz in to 60 Hz out), but even that shouldn't happen unless there's a real bug of some sort.

My suggestion would be to try v1.04 running with 60 Hz locked output and see if that solves the problem. Also, if it's not too much trouble, try both projectors as that will remove the display as a factor.

- Dale Adams

Dale - thanks for the suggestion, setting it at 60Hz locked fixed my problems. I'm going to give the v1.04 upgrade a try anyways to see if it fixes the severe tearing in 24hz locked mode so I can send that to my RS1. In all honesty I have to try pretty hard to see any judder, but it's there if I look, so I'd prefer 24Hz for HD DVDs and BDs. Thanks again for your help!

Hi Barry

fwiw, it appears that I also can't get the Auto DI discrete to work - this is the code it generates


0000 006C 001B 0000 0064 0064 0016 0041 0016 0015 0016 0015 0016 0041 0016 0015 0016 0015 0016 0041 0016 0015 0016 0015 0016 0041 0016 0041 0016 0015 0016 0041 0016 0041 0016 0015 0016 0015 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0015 0044 0044 0016 0001


which is converted in PPE-NG to

0000 006C 001B 0000 0064 0064 0016 0041 0016 0015 0016 0015 0016 0041 0016 0015 0016 0015 0016 0041 0016 0015 0016 0015 0016 0041 0016 0041 0016 0015 0016 0041 0016 0041 0016 0015 0016 0015 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0015 0044 0044 0016 0064


INI file has
Model = VP50

I don't have a problem with any other discretes either, I use on/off, display profiles and inputs of course.

I've got what I suspect is a dumb question...I have a JVC RS1 and the VP50 Output Setup / Format option for 1080p-24 is grayed-out (disabled). Is there some conflicting setting I've got going on that disables it? Is this the output format other RS1 owners are using? I've installed firmware 1.04

I've got what I suspect is a dumb question...I have a JVC RS1 and the VP50 Output Setup / Format option for 1080p-24 is grayed-out (disabled). Is there some conflicting setting I've got going on that disables it? Is this the output format other RS1 owners are using? I've installed firmware 1.04

I think Josh posted it earlier. You have to go to framerate, set 60Hz to 24Hz locked, 24Hz to 24Hz locked, then I think you can go to format and select that.

I think Josh posted it earlier. You have to go to framerate, set 60Hz to 24Hz locked, 24Hz to 24Hz locked, then I think you can go to format and select that.

Thanks that enabled it. When I set the output format to 1080p-24 the VP50 Judder test pattern is pretty...juddery. It is much smoother on 1080p-60.

After combing through the last week or so of posts I see others are having this problem too on the RS1 with the VP50 internal test pattern. I verified through the "secret" RS1 menu that it is at 48Hz as others have noted it reporting when the VP50 is correctly set for 1080p-24. So chalk this up as a "me too" for that problem.

Thanks that enabled it. When I set the output format to 1080p-24 the Judder test pattern is pretty...juddery. It is much smoother on 1080p-60.

Are other RS1 owners getting smooth display of the Judder test pattern at 1080p-24?

Yes, I understand what you mean. But still the video output from a Blu Ray or HD DVD source has less judder when output is set to 1080p24 than when at 1080p60. Don't forget to set deinterlacing to 3:2 forced.

I just created a profile for 1080i60 input (to output 1080p24). But I noticed that when I've set the "Auto"-feature on, VP50 tries to use the same profile for 1080i50 too, which ofcourse causes a black screen.

Would it be possible to program the VP50 firmware so that it uses different auto profiles for 1080i50 and 1080i60?

I just created a profile for 1080i60 input (to output 1080p24). But I noticed that when I've set the "Auto"-feature on, VP50 tries to use the same profile for 1080i50 too, which ofcourse causes a black screen.

Would it be possible to program the VP50 firmware so that it uses different auto profiles for 1080i50 and 1080i60?

Yes it is possible. I have it working on my system.

You do not want a 1080i/50Hz input set to be output at 1080p24, there is no point. (This is assuming you have a 50Hz capable display.) You need to create a separate profile for 1080i50 to be output at 1080p50, enable the auto feature and then the VP50 will automatically set the right profile depending on the source. Hope this helps.

I just created a profile for 1080i60 input (to output 1080p24). But I noticed that when I've set the "Auto"-feature on, VP50 tries to use the same profile for 1080i50 too, which ofcourse causes a black screen.

Would it be possible to program the VP50 firmware so that it uses different auto profiles for 1080i50 and 1080i60?
As above, it will store different profiles for those two resolutions, just need to select a different one while in 1080i/50 - it should use it next time.

And the fact you're getting a blank screen suggests to me it's not using the same profile as for 1080i/60 though, since that doesn't give a blank screen. More likely it's using the default profile which is the wrong output or a res the screen doesn't support.

Re My (Barry's) Utility.

There is a new version located at my web site (www.the-gordons.net). I assume the post referring to the "Update Utility 2.0.84" was referring to my Utility program. Would make my life easier if all referred to it as "Barry's utility" until DVDO wishes to call it something else. No changes the in the "Firmware Loader" portion.


Yes sorry Barry, i was refering to your excellent update utility!

I hope you get credit from DVDO for this as it's superb and the work and support you do is very much appreciated, thanks! :)

No need to be sorry, and thanks for the nice words. And yes, DVDO has "compensated" me for the work I have done. They are, IMHO, one of the better companies out there.

Hi Barry

fwiw, it appears that I also can't get the Auto DI discrete to work .

Same here, AUTO does not work for me now with VP50 1.04 & Barry's Utility 2.0.124 with pronto RU980. I respectfully suggest either DVDO has messed it up, or the code has changed now with the additional new modes available.

As above, it will store different profiles for those two resolutions, just need to select a different one while in 1080i/50 - it should use it next time.

And the fact you're getting a blank screen suggests to me it's not using the same profile as for 1080i/60 though, since that doesn't give a blank screen. More likely it's using the default profile which is the wrong output or a res the screen doesn't support.

Thanks Craig and Choddo!

I created two profiles earlier: one for 1080i50 input (cable hdtv) and later I created one for 1080i60 (HD DVD & Blu-ray). It seemed like the VP50 used the latter (1080i>1080p24) for both. I have to try this again to verify, since it might be just my own fault. But it looked like VP50 can have only one automated profile for 1080i, not two separate for 1080i50 and 1080i60. I'll check this again.

Edit: I created another profile for 1080i50 and tried switching between 1080i50 and 1080i60 inputs and I think everything works very well now.

Another thing is the "between scenes combing effect" with Toshiba HD-XE1 HD DVD player. I described it in post 4205 (http://www.avsforum.com/avs-vb/showthread.php?p=10402776&&#post10402776). Any clues what is causing this? Has someone else noticed similar effect?

Edit: I updated XE1 with v1.5 firmware but it didn't solve this issue. The combing can be seen when scenes change and in fast motion. Weird thing is that I see it with 1080i60/1080p60 HD DVD but not with 1080i60/1080p60 Blu-ray (PS3). I think I'll still stick to sending XE1 and PS3 signal directly to my display: The combing makes HD DVD unwatchable and forced progressive cadence detection causes too long lag to PS3 games.

Is is possible to save a different outputs (connections) to the profiles?

At the moment i am using HDMI and RGBHV to my display but when i select the relevant input it stays fixed to what output i have used before, so i am having to go in to output settings and maunually change it to the correct output.

Reason i use both connections is i have to use HDMI for my HDMI inputs due to HDCP (until i can get a stripper) and use RGBHV for native and 1080P veiwing.

I think it would also be good if we could have more than 10 profiles, if this is possible.

it's great

Another thing is the "between scenes combing effect" with Toshiba HD-XE1 HD DVD player. I described it in post 4205 (http://www.avsforum.com/avs-vb/showthread.php?p=10402776&&#post10402776). Any clues what is causing this? Has someone else noticed similar effect?

Yes, it's like a bad transition between scenes... and sometimes it seems like the VP50 needs some seconds to get in sync again after that.

I have this effect with my XE1 and my PS3, BTW.

Do you also have this judder effect when applying the internal test pattern ("judder bar")?

Cheers,
Sandel

Yes, it's like a bad transition between scenes... and sometimes it seems like the VP50 needs some seconds to get in sync again after that.

I have this effect with my XE1 and my PS3, BTW.

Do you also have this judder effect when applying the internal test pattern ("judder bar")?

Cheers,
Sandel

Since you have this combing with PS3 too then I guess we can blame the VP50. I haven't yet seen it on my PS3 (tried also the movie "The Wild").

If I can see judder with the "judder bar" at 1080p24 it's really uniform. I think it should be normal that the bar is running smoother with 1080p60 since there's over double amount of movement information.

Ps, I updated my earlier post.

I finally got around to installing FW 1.04 (from 1.01). My display is the Panasonic 1000U.

With 1.01 I could output 1080P/24, but only at 48 Hz without tearing. At 24 / 24, the image looked better, but I would have to pause the movie then re-start whenever the tearing would occur (as many others have also reported).

With 1.04 installed, 1080P/24 + 24 looks beautiful. It’s rock steady I swear it looks better than it did before. I suspect that with 1.01 there were some frames getting dropped or some other funky thing happening that my eyes could make out, but not to the point where I could figure out what was happening. Now it’s a wonderful sight to see. I had thought the image looked great before (even with the tearing, although that was an irritant), but now I finally realize why so many videophile types praise 1080P/24.

I have not had time to sit through a whole movie yet, but with 1.01 installed, the tearing would happen about every five minutes or so. I sat through about 40 minutes of Sahara HD/DVD and it did not tear or anything. Even my SD satellite feed looks good at 1080P/24/24 whereas I would have to output 1080/60/60 before.

FYI - I have forced 2–3 de-interlacing selected.

Thanks DVDO for getting this thing fixed. I’m finally beginning to think this little magic box was worth the money.

Re IR codes and the DI Auto command

My utility generates all of the codes in the same manner, algorithmically based upon the codes parameters (the command code and the subcode). In the case of DI the command code is Hex 49, and the sub code for Auto is 6. I will agree that it does not work ( I have not personally tried it, but will agree with my peers), and I will discuss it with my firends at DVDO. I suspect it is a DVDO problem in that either the subcode is wrong, or something else is afoot. I know they are still doing work on unifying all of the IR and RS232 formats and protocols.

Thanks DVDO for getting this thing fixed. I’m finally beginning to think this little magic box was worth the money.

I feel the same way. DVDO has finally come through and the VP50 now seems to be living up to its advertised specs.

To put this in context, there are some disgruntled owners of the Crystallio 2 over on other threads and on the Pixelmagic forums. Some months ago I was just about to put the $ down for a Crystallio, only to read of image tearing problems with 1080p24 output and Constant Image Height Setups. This has not yet been resolved by Pixelmagic and may never be because of hardware limitations, however owners are optimistic of a solution

I have also read that there may even be some problems with the 1080p24 outputs of some Bluray players (directly connected without a VP50 in the loop) not interfacing with displays correctly. Has anyone else heard this?

To my mind, this all means that VP50 owners with 1.04 installed and displays correctly displaying 1080p24 should be very happy right now.

All we need now is the NR and sharpening adj.

Are the current VP50 settings saved when upgrading from 1.01 to 1.04?

Another thing is the "between scenes combing effect" with Toshiba HD-XE1 HD DVD player. I described it in post 4205 (http://www.avsforum.com/avs-vb/showthread.php?p=10402776&&#post10402776). Any clues what is causing this? Has someone else noticed similar effect?

Edit: I updated XE1 with v1.5 firmware but it didn't solve this issue. The combing can be seen when scenes change and in fast motion. Weird thing is that I see it with 1080i60/1080p60 HD DVD but not with 1080i60/1080p60 Blu-ray (PS3).It sounds to me like the signal from the XE1 is not a constant 3:2 pulldown signal, but rather suffers from either 'bad edits' or 3:2 cadence breaks of some type.

The forced 3:2 mode assumes that the input signal does have a 3:2 cadence, but it has to detect the phase of the signal (i.e., where in the 3:2 sequence the signal is). To do this it uses a very stringent criteria such that it's pretty much guaranteed not to mis-detect the correct phase. This all works great until there's a break in the cadence pattern. When that happens the VP50 continues on using the same 3:2 phase relationship it was previously using until it can identify the new 3:2 phase with a high enough confidence level that it will shift phase. Due to the the stringent quality requirements for it to re-lock to the new phase, there will be a period during which it combs. This period can very from a few frames to several seconds depending on the nature of the source signal.

This is one of the main differences between the 'auto' deinterlacing mode and the forced 3:2 mode. The 'auto' mode in particular is designed not to comb on cadence transitions while the forced 3:2 mode is virtually guaranteed to. This is one reason why the forced 3:2 mode should never be used on a source which does not have a very, very reliable 3:2 pulldown pattern.

On the surface, at least, it appears as if most of those who are having problems with the forced 3:2 mode on VP50 firmware v1.04 are using Toshiba XE1 players or an XBox with an HD DVD drive, and are located in 50 Hz countries. (There may also be some issues with PS3s, but these appear also to be occurring in countries with 50 Hz video standard.) Now, I don't know why that would matter, but it appears that there may be some difference between the Toshiba players sold to 50 Hz countries and those distributed to the US which is resulting in a 3:2 cadence disruption. (Some US XBox owners have also noted motion stutter problems, so the XBox itself may have some issue.) This shouldn't be hard to determine with an XE1 player and the right lab equipment, so DVDO should be able to reproduce this if they have one of these players.

- Dale Adams

Big thanks Dave!

I tried the other deainterlacing modes too (Auto, Film Biased...) but they all caused a lot of judder. Only "Forced 3:2" gave fluid motion, but with these "cadence breaks". I don't get any judder or combing when I connect the player directly to my display (Pioneer PDP-507XA), so there should be a way around this.

There have been rumours that Toshiba will enable 1080p24 output for XE1 this summer (which would propably solve this issue). But I've also heard that it's harder to get 1080p24 from HD DVD compared to Blu-ray, I haven't confirmed this though.

Is is possible to save a different outputs (connections) to the profiles?

At the moment i am using HDMI and RGBHV to my display but when i select the relevant input it stays fixed to what output i have used before, so i am having to go in to output settings and maunually change it to the correct output.

Reason i use both connections is i have to use HDMI for my HDMI inputs due to HDCP (until i can get a stripper) and use RGBHV for native and 1080P veiwing.

I think it would also be good if we could have more than 10 profiles, if this is possible.


Looks like my Profiles didn't save correctly, re-saved them and it works fine now!

Just another success report with 1.04, IR and menus are much more stable and thanks to reprogramming my pronto with Barrys Util most of my macros seem to actually work now. :)

Have tried some HDDVD, Bluray and DVD titles with Fixed 3:2 and 1080p60@24locked and all seems well with my Sony Pearl (OSD shows 1080p24 input). Watched a couple of films all the way thru (including Children of Men with it's shaky cam action) and had no image issues that I could see.

Tosh E1 HDMI 1080i, PS3 HDMI 1080p and Opp971 SDI 480i as sources.

does the VP50 passthrough PCM 5.1 via the Coax or Toslink ??????? or just 2.0 PCM

does the VP50 passthrough PCM 5.1 via the Coax or Toslink ??????? or just 2.0 PCM

Nothing will pass PCM 5.1 via coax or toslink. It is above the standard. I think it will do 2 channel.

You need HDMI for PCM 5.1.

I am using a VP50 with Coaxial/Toslink output to a Lexicon MC-1 as an audio processor. I get Dolby Digital 5.1, PCM 2.0, and DTS. The Dolby Digital comes from an HDMI input, The PCM from either Conponent or HDMI and the DTS from Component because that is what the sources supply.

I am not sure what PCM 5.1 is though, perhaps you could clarify.

The new software (1.04) solves all problems for me. From my Panasonic BD10 (1080i 60) via VP50 to Yamaha DPX1200 all judder is gone at 48p locked. I have also tested 24p locked, the projector has problems with this framerate and shows strange colors, but I still can see that there is no judder. I use "auto" and not forced mode.

The new firm also solves my audio problems. After switching sources (HDMI) the VP50 lockes on the audio of the new source quite reliably.

I am using a VP50 with Coaxial/Toslink output to a Lexicon MC-1 as an audio processor. I get Dolby Digital 5.1, PCM 2.0, and DTS. The Dolby Digital comes from an HDMI input, The PCM from either Conponent or HDMI and the DTS from Component because that is what the sources supply.

I am not sure what PCM 5.1 is though, perhaps you could clarify.

He’s referring to the Uncompressed PCM audio tracks off Blue Ray and HD/DVD disks (L-PCM).

No, Coax or Toslink can not pass these. Too much band width. I can only be passed via HMDI.

Someone else asked if settings were lost going from FW 1.01 to 1.04………NO, they are not lost. Or, at least mine were not lost.

It sounds to me like the signal from the XE1 is not a constant 3:2 pulldown signal, but rather suffers from either 'bad edits' or 3:2 cadence breaks of some type.

Dale,

The XE1 is the same as the A2 in the US.

With the original A1 playing my HD super speedway loop, the VP50 stays locked in auto mode. When playing the same test clip on the A2 (XE1), it drops on most of the loops. I suspect the A2 is not correctly creating the 2-3 output.

The last time I looked at this was last year. I will hook the A2 back up and take a look this week compared to the A1.

What is odd is my test is interlaced, with a physical pulldown, so it should be easier for the player to ouput correctly. I need to build both 24p and 60i versions to really debug.

I haven't made the plunge to Blu Ray or HD-DVD. I am "protesting" the two formats (for what good it will do me).

What I really want to see is a megachanger that will take any one of the two formats and play each of them equally well and hold a minimum of 300 disks. It will come, just have to wait. It is really nice when you can just select a DVD form the screen by title and have it automatically played with out having to go looking for it.

I will hook the A2 back up and take a look this week compared to the A1.

What is odd is my test is interlaced, with a physical pulldown, so it should be easier for the player to ouput correctly. I need to build both 24p and 60i versions to really debug.Thanks, Stacey!

- Dale Adams

Overall fw 1.04 has performed well for me. Last night I watched Smokin Aces on my A1 with the latest fw (2.2). I'm using Forced 3:2 and outputting 1080 24p to a JVC RS1. There were at least 3 brief episodes (seconds) where there was obvious stutter. The stutter was gone when I would replay the scene. Any ideas?

Re My (Barry's) Utility.

There is a new version located at my web site (www.the-gordons.net). I assume the post referring to the "Update Utility 2.0.84" was referring to my Utility program. Would make my life easier if all referred to it as "Barry's utility" until DVDO wishes to call it something else. No changes the in the "Firmware Loader" portion

The new version has a lot of fixes re IR code generation, mostly for the VP30 but also for the VP50. It now has an initial configuration utility that allows you to easily customize it for what you want and the equipment you own.

As Far as I can tell it generates IR patterns in the Pronto Hex format which are precisely to the specs/information provided by DVDO under NDA so please do not ask me for that data. I believe they plan to release a lot of it in the future as "Automation Protocol".

There was one lurking bug re searching for Com ports (in the case that the only com port on the PC was in use so none were found) that was also fixed.

I have gottent at least one report that when the discrete IR codes (which all end with 0001) are pasted into a Pronto Editor, the Pronto editor changes that value to 0064. I have not seen that and can not duplicate it with the pronto editor I use (iPronto Edit 2.5.2 and Pronto Edit 4.0.5). In any evnt is should make no difference That value is the amount of off time for the last IR burst and is then followed by IR being off until the next IR pattern is sent. ergo is can be almost anything. It does however control how quickly the next IR pattern can be sent, but the patterns the program generates are not Repeat patterns so it should not matter.

This version must be run with the assocaited version of the INI control file. It will then make a customized INI file for your use.

As usual let me know of any problems and I will assist/fix.

just upgraded from 1.01 to 1.04 using Barry's utility ... made the process so straight forward! 1.04 is working well... will do some more tests tonight... the remote control is much easier to use now with 1.04....

I just unpacked my new VP50, updated it to FW 1.04 and tested a few different sources. It seems to perform very well. I had no issues with the 1080p24 output. I am looking forward to watching my first 1080p24 2,35:1 CIH movie!

This is great!

I've recently got a VP50 (1.0 firmware) and with HDMI and component inputs its fine. However, I also have some old legacy bits of kit which use composite and s-video. Apart from the HDMI all of the inputs are connected via my Linn AV system (Kisto) with the 'watch' outputs from the Kisto (video, s-video, component) connected to the VP50 (this was to save re-routing leads - which is a hard job at the moment as it involves mostly dismantling my AV rack).

Prior to getting the VP50 I used another scalar to drive my Pioneer plasma but that didn't support HDMI and my new kit (including PS3) uses HDMI.

Since I've swapped over to the VP50 I've noticed that if I go into the EPG on my satellite (SKY) or terrestrial digital the VP50 can 'lose' the PAL and go into B/W - e.g. if I have the VP50 info display on the 576i PAL input changes to 576i B/W. When this happens the picture either displays in black and white or flickers between colour and black and white - then it will stabilize and be ok. I've also had the same effect when not using the EPG but rarely - going into the EPG is the best way to get the effect.

I'm going to check the connections and try the other scalar just to check i've not pulled the cables - other than that can anybody suggest what I could check or try setting in the VP50.

I've recently got a VP50 (1.0 firmware) and with HDMI and component inputs its fine. However, I also have some old legacy bits of kit which use composite and s-video. Apart from the HDMI all of the inputs are connected via my Linn AV system (Kisto) with the 'watch' outputs from the Kisto (video, s-video, component) connected to the VP50 (this was to save re-routing leads - which is a hard job at the moment as it involves mostly dismantling my AV rack).

Prior to getting the VP50 I used another scalar to drive my Pioneer plasma but that didn't support HDMI and my new kit (including PS3) uses HDMI.

Since I've swapped over to the VP50 I've noticed that if I go into the EPG on my satellite (SKY) or terrestrial digital the VP50 can 'lose' the PAL and go into B/W - e.g. if I have the VP50 info display on the 576i PAL input changes to 576i B/W. When this happens the picture either displays in black and white or flickers between colour and black and white - then it will stabilize and be ok. I've also had the same effect when not using the EPG but rarely - going into the EPG is the best way to get the effect.

I'm going to check the connections and try the other scalar just to check i've not pulled the cables - other than that can anybody suggest what I could check or try setting in the VP50.

loosing colour does look like a loose cable to me ... but only happening on EPG is indeed strange ..

the only times I had BW or pink & green was when I was sending RGB to a piece of equipment which only accepts YUV, or bad synch ... try unplugging and replugging the VP50 into the mains... it helped me....

I would like to report a bug with the 1.04 firmware, other then this bug, it works very well.

If I change from a source that uses the HDMI to pass the audio (my Sony DHG-HDD250)and then go to another device (such as one that uses Composite video with a stereo audio input) , the audio gets a little staticy and I need to shut down the VP50 for a second and turn it back on and all is fine. It did it once and thought, what is that then it happened a second and finally a third time, so I figure that it must be a bug.

Other then this, no problems with the new firmware. I no longer get audio dropouts via HDMI from my Oppo dvd player with a DTS audio CD, thanks for a job well done.

Jim

EDIT: Audio dropouts via DTS Audio discs with my Oppo are still there, just a reduced amount.

Jim,

Have you sent mail directly to DVDO? If not, you should as they may or may not read your bug report here.

Any update on the Auto DI descrete code issue with 1.04?

Jim,

Have you sent mail directly to DVDO? If not, you should as they may or may not read your bug report here.


Sent

loosing colour does look like a loose cable to me ... but only happening on EPG is indeed strange ..

the only times I had BW or pink & green was when I was sending RGB to a piece of equipment which only accepts YUV, or bad synch ... try unplugging and replugging the VP50 into the mains... it helped me....

Tonight I tried a direct s-video connection from my SKY box to the VP50 with the other video and s-video connections unplugged with exactly the same effect so my guess is the VP50 is having problems with 576i 50 input.

Anybody had any similar problems with 576i inputs.

Updated to 1.04; so far, everything is good. SD dvds look as good as ever, maybe even better. (tho I'm always a sucker for the halo effect.) No problems in 3 hours of SDTV, SD DVD, and BD playback.

Question for experts tho - am feeding 1080p -60 from PS3 for BD playback. Checking input menu, and PREP is on by default. Correct me if I'm wrong, but isn't applying PREP here just adding another layer of processing where it isn't needed? (In a quick comparison, didn't see any effect with or without it, but just curious.)

where does the VP50 store the inpute settings, for example (picture control settings and sound settings) ? does it store this by it self or in some profile ?
i think the output profiles are only for the output settings and the display profile are only for some input settings ?

where does the VP50 store the inpute settings, for example (picture control settings and sound settings) ? does it store this by it self or in some profile ?
i think the output profiles are only for the output settings and the display profile are only for some input settings ?

These settings are automatically saved and recalled.

Guess I'll try reporting this again..... Anyone have an OPPO 970 (HDMI)? Auto mode simply does not work with this device. The ony other device I had (until I got my xbox 360 elite) was a DISH receiver which is really on all of the time (making it select AUTO all the time - on or off). However, the 360 elite with HDMI works perfectly. Turn it off and the next prioritize device gets selected. The OPPO (when turned off) does not do this. The VP50 stays selected on that device even though the INFO screen shows NO SIGNAL. Could the 970 still be sending some type of signal to the VP50 (even though INFO states NO SIGNAL) It would make my setup easier if this would work. By the way, the 360 elite is sending 1080P HDMI to the VP50 which works great. Thanks. SJ

Guess I'll try reporting this again..... Anyone have an OPPO 970 (HDMI)? Auto mode simply does not work with this device.Ugh... I finally broke down and ordered a (refurbished) VP50 this week -- and, coincidentally, an Oppo 970 to go with it. :(

I guess I'll at least have another "data point" for you regarding this combo, sometime after they both arrive on Friday...

--John

WIll the OPPO play SACD and DVD-A over the HDMI? As long as it does 480i over HDMI it should work very well for SD DVDs with the VP50. I had one of the older OPPOs when I had my VP30 and that combination produced a nice picture from SD DVDS.

Tonight I tried a direct s-video connection from my SKY box to the VP50 with the other video and s-video connections unplugged with exactly the same effect so my guess is the VP50 is having problems with 576i 50 input.

Anybody had any similar problems with 576i inputs.

No, working well here. My 50 Hz sources in use are SDI, RGBs, S-video and composite. I had a similar incident earlier and rebooting the source(SAT tuner over RGBs) solved it.

These settings are automatically saved and recalled.

thxns josh, to as i understand it it saves the color and several other settings for each input ?

Having read the specs of the VP50, it seems to fit my needs perfectly - except for one thing. It appears that the VP50 is unable to process the aspect ratio signal present on pin 8 of the Euro SCART connector, meaning I would have to change aspect ratio manually when I switch channels on the SD receiver. That would be a major issue for me. Is there any way around this?

Sorry if this has been answered already.

I've recently got a VP50 (1.0 firmware) and with HDMI and component inputs its fine. However, I also have some old legacy bits of kit which use composite and s-video. Apart from the HDMI all of the inputs are connected via my Linn AV system (Kisto) with the 'watch' outputs from the Kisto (video, s-video, component) connected to the VP50 (this was to save re-routing leads - which is a hard job at the moment as it involves mostly dismantling my AV rack).

Prior to getting the VP50 I used another scalar to drive my Pioneer plasma but that didn't support HDMI and my new kit (including PS3) uses HDMI.

Since I've swapped over to the VP50 I've noticed that if I go into the EPG on my satellite (SKY) or terrestrial digital the VP50 can 'lose' the PAL and go into B/W - e.g. if I have the VP50 info display on the 576i PAL input changes to 576i B/W. When this happens the picture either displays in black and white or flickers between colour and black and white - then it will stabilize and be ok. I've also had the same effect when not using the EPG but rarely - going into the EPG is the best way to get the effect.

I have my DVB-C (Handan CV-5500HD @576p) connected to VP50 (PReP ON) and sent to my Pioneer plasma (PDP-507XA), both connections HDMI. Everything seems to work ok. I had to selected "AUTO" from Pioneer's HDMI Input menu to get the colors right, but I guess it was a different issue.

thxns josh, to as i understand it it saves the color and several other settings for each input ?

These settings are saved on a per input/per format basis. On the component inputs, for example, (Component 1 and Component 2) there are individual memories for 480i, 480p, 576i, 576p, 720p, and 1080i input signals.

Guess I'll try reporting this again..... Anyone have an OPPO 970 (HDMI)? Auto mode simply does not work with this device. The ony other device I had (until I got my xbox 360 elite) was a DISH receiver which is really on all of the time (making it select AUTO all the time - on or off). However, the 360 elite with HDMI works perfectly. Turn it off and the next prioritize device gets selected. The OPPO (when turned off) does not do this. The VP50 stays selected on that device even though the INFO screen shows NO SIGNAL. Could the 970 still be sending some type of signal to the VP50 (even though INFO states NO SIGNAL) It would make my setup easier if this would work. By the way, the 360 elite is sending 1080P HDMI to the VP50 which works great. Thanks. SJ

I have the 970. But I currently have all my sources routed to my reciever first then out to the VP50. I plan to change all that this weekend. Can you expand on your problem so I might duplicate it? I don't quite understand what you are doing, or what is happening.

These settings are saved on a per input/per format basis. On the component inputs, for example, (Component 1 and Component 2) there are individual memories for 480i, 480p, 576i, 576p, 720p, and 1080i input signals.

merci know i got it

@barrygordon

I have upgraded to 1.04beta and noticed that the discrete code for "Deinterlacinge Mode AUTO" does not work any more. FilmBias and Video work, but AUTO does not work.

@barrygordon

Also for me "Auto" doesn't work.
I would also like to suggestion to add "Force 2:2" mode to the list of DI Modes, because I can't find it.

Thank you for the excellent work done!

I have the 970. But I currently have all my sources routed to my reciever first then out to the VP50. I plan to change all that this weekend. Can you expand on your problem so I might duplicate it? I don't quite understand what you are doing, or what is happening.

OK. Let's say you have your 970 in the VP50 HDMI 1 (input) and other devices in other inputs (HDMI 2, component 1, etc.). Then you set the input priority to #1 for HDMI 1 (the 970) and #2 for another device, #3 for another, etc.... If you have the input select on AUTO and the 970 ON, it should select the 970 (because it is #1 in the priority list). When you turn the 970 OFF, the VP50 should then select the next active signal in the list (#2, #3, - whatever is on). On my setup, when I turn off the 970, the VP50 REMAINS on HDMI 1 (even the VP50 INFO screen shows NO SIGNAL). Make sense? SJ

Having read the specs of the VP50, it seems to fit my needs perfectly - except for one thing. It appears that the VP50 is unable to process the aspect ratio signal present on pin 8 of the Euro SCART connector, meaning I would have to change aspect ratio manually when I switch channels on the SD receiver. That would be a major issue for me. Is there any way around this?

Sorry if this has been answered already.There is no direct hardware support in the VPxx for this. But there is a complex workaround: make a separate hardware utility that senses this pin. Connect this device to the serial input of the VPxx. Emit the appropiate code when the device senses a change on pin 8. Some freaked-out Europeans made this device and maybe it is still for sale. Check out the avforums.com site.

Note: We could ask DVDO to directly use some pin on the serial input for this. Of course accompanied with a menu choice "Serial = Automation Protocol | SCART pin 8 emulation" :) I would happily pay $50 for this!

Note 2: Even better would be an "automatic vertical bar detection (MagicZoom Tm)": perform a linear zoom until the vertical bars are gone! But no kidding, wouldn't that be perfect!

Guess I'll try reporting this again..... Anyone have an OPPO 970 (HDMI)? Auto mode simply does not work with this device. The ony other device I had (until I got my xbox 360 elite) was a DISH receiver which is really on all of the time (making it select AUTO all the time - on or off). However, the 360 elite with HDMI works perfectly. Turn it off and the next prioritize device gets selected. The OPPO (when turned off) does not do this. The VP50 stays selected on that device even though the INFO screen shows NO SIGNAL. Could the 970 still be sending some type of signal to the VP50 (even though INFO states NO SIGNAL) It would make my setup easier if this would work. By the way, the 360 elite is sending 1080P HDMI to the VP50 which works great. Thanks. SJThis a known issue with the VP30 and seems to be on the "to fix" list. It has been suggested that the Oppo (and some other devices) maintains some kind of low level sync signal. There is some info in the VP30 thread.

OK. Let's say you have your 970 in the VP50 HDMI 1 (input) and other devices in other inputs (HDMI 2, component 1, etc.). Then you set the input priority to #1 for HDMI 1 (the 970) and #2 for another device, #3 for another, etc.... If you have the input select on AUTO and the 970 ON, it should select the 970 (because it is #1 in the priority list). When you turn the 970 OFF, the VP50 should then select the next active signal in the list (#2, #3, - whatever is on). On my setup, when I turn off the 970, the VP50 REMAINS on HDMI 1 (even the VP50 INFO screen shows NO SIGNAL). Make sense? SJ

Got it... I'll check that out this weekend and report back. I was waiting for the audio drop outs to get fixed before using the VP as a hub. I'm excited to try it again.

SJHT, I have the same problem with 1.00. I don't have an Oppo but am running DTV HD PVR, Tosh A1 hd-dvd, Panny BR and Snazzio media player on my HDMI ports.

Ahh, good info.

Bejoro,

What you are implying is that it worked under 1.xx but not under 1.04? If that is the case then I will safely say it is a DVDO problem as the IR codes generated are the same for any model VP50 independent of Firmware version. I will check with DVDO to ensure I have the right subcode (6) for auto

Ninja Rogue:

It is there. When you bring up the IR window (in the recent versions) it will show you the model of the equipment. If it says VP50 it is there. If it says VP30 and the ABTDI card is installed as an option (it will say that too) then it is there. if it is a VP30 without the ABTDI option then it is not there. I see it as the third one in the list for a VP50. What version of the utility are you using?

No, working well here. My 50 Hz sources in use are SDI, RGBs, S-video and composite. I had a similar incident earlier and rebooting the source(SAT tuner over RGBs) solved it.

When I tried the direct connection I switched off and re-started.

If you have a 576i 50 Hz source connected via s-video and/or video can you tell me your input setups for them so I can check with what I have.

Re DI codes on the VP50.

The following may be duplicated by anyone with my Utility. Why I didn't think to try this before is beyond me.

Try sending a DI command (might have to read my manual, but see the end of this note) to the VP50 and see what happens. This is with the utility connected to the VP50 over its RS232 port as if you were using the loader.

If the VP50 is currently seeing a progressive (non interlaced) signal on its active input the command has no effect as it shouldn't as there is probably no memory to store it in. The DI data is stored (I think) in a memory indexed by input and subindexed by signal type. No need to waste storage for progressive signals.

If the VP50 is seeing an Interlaced (e.g. 480i, 1080i) signal on its active input then all of the DI commands work WITH THE EXCEPTION OF AUTO. The VP50 returns a response of "Bad Command" when given the DI Auto command. Ergo the VP50 has an issue, the IR code is most likely correct (unless I was given the wrong sub code for Auto), and will do just what the RS232 code does (i.e. not work)

To send any data, right click on the item you wish to send in the right hand Pane (upper, middle or lower) and it will bring up a context sub menu of the legal values for that command. left click the value to send. Note the stuff in the data transmission display. 4 lines are normal, (1) the command being sent, (2) the reply to the command, The request for the current state, followed by the value being sent back. In the case of DI auto an extra line is shown showing that an error was returned. Double clicking in the data transmission display window clears it

I think this puts the DI auto issue to bed, at least in my ball park!

VP50 FW 1.04 Problem

I am curious if any one else is seeing this. About once a week I will completely lose audio. It happens only with the DVR's (SA8300HD) and when I am fast forwarding or skipping backwards. To get audio back I need to force an HDMI re-handshake between that DVR and the VP50 which I do by switching to another DVR input and then back. It always clears up. I suspect it is a DVR problem and not a VP50 problem but might be a nasty timing problem between them under certain conditions.

Barry just to me thinking out loud that sounds like a compatiblity issue there, it would be hard to know which is to blame :( thus is the life of HDMI :mad:

-Gary

Gary, I agree

Ninja.rogue, You are correct I misread. There is 2:2 even and force 3:2 but no Force 2:2

I just spoke to DVDO and they have confirmed (1) DI Auto does not work, it returns a bad command status (2) they left "Force 2:2" out of the DI command set. Both of these will be fixed in a future (hopefully next) release

Thank you Barry for taking the time to inquire.
Have a nice day

Ugh... I finally broke down and ordered a (refurbished) VP50 this week -- and, coincidentally, an Oppo 970 to go with it. :(

I guess I'll at least have another "data point" for you regarding this combo, sometime after they both arrive on Friday...

--John

I've got no problems with 576i or the oppo 970 via HDMI either with FW 1.04 ....

@barrygordon

DI AUTO issue:

Barry, thanks for examining this. Good to know that your great tool is working fine.
So, DVDO has to correct this issue (hopefully soon).

I am not sure whether this problem was already there in 1.01. I think I tested it after my upgrade from 1.00 but I am not sure.

Also for us - PAL users - it would be quite valuable to have a Force 2:2 DI ir code due to the fact that most of our DVDs will have to use this.

You mean it doesn't have one? Crap, that ain't good. I don't have too many PAL DVDs but I have a few animation and concert DVDs that are 30fps...

The "force 2:2" subcommand for the DI command being left out was an oversight. DVDO stated they will add it and fix DI auto.

The utility program INI file will just require a simple change in one line as soon as we know what the subcommand code is. The generator code will neeed no change.

I built the utility to be table driven as my experience in developing software for others (read that as specs I did not write) led me to the conclusion that flexibility and ease of change/correction is more important then speed of execution.

@Josh

Could you please let us know that you are aware of the "blinking white line issue" and are working on a fix please?

I have written an E-mail to DVDO Support but I never got an answer, it's several months ago.

I can see that the issue is still there with 1.04.

/Martin

@josh

same for me
i adresses this issue with firmware 1.0 back in oktober 2006 and just got mails your working on it and you will contact me.
last week i reask and just got the answer from aaron that DVDO is checking the status.

now are 7-8 month with this problem and no final answer.

i also send videos where the white blinking line was shown.

please fix this with 1.05ß i will also test a private beta if you send me one !!!!

Hmmm, no reply to my email for the audio issue from DVDO.

Just updated from 1.00 to 1.04. Was hoping to improving the PQ of Fox 720p shows. But looks like PReP doesn't support 720p. Why is that?

I believe because a 720i source does not exist and therefore you can not Prep 720P... SJ

you don't want to Prep 720p in that case anyway ;) it doesn't apply there

-Gary

Makes sense. Too bad, The Simpsons looks like crap on my local Fox channel. Combing, etc. PReP could really help.

for the guys with audio issue, i have noticed that the digital coax connection is sometimes dropping because of my refrigerator is turn on, so there is a ground probleme.

but this is not only related to the vp50 it's also on other devices.

Barry:

First, many thanks for Your marvellous tool. But one question: There are two IR codes for output format 1080p-50 and 1080p-60 but none for 1080p-24. Does such one exist, or is it not implemented yet for the VP50 ?

@barry:

is it possible that you could generate a CCF file from your tool ? or is it possible to generate a list which is to be read with the HEX2CCF tool and this is generating the ccf file for all commands ?

@Josh

Could you please let us know that you are aware of the "blinking white line issue" and are working on a fix please?

I have written an E-mail to DVDO Support but I never got an answer, it's several months ago.

I can see that the issue is still there with 1.04.

/Martin

same for me too .... still there....

I am sorry if this has been asked before, but does the VP50 use the same SDI-input as other Iscan products (VP30, HD+ etc)?

NORLL:

Yes it does. I took the sdi input out of my VP30 and plugged it right into the VP50. It actually works in the VP50 better (without the extra parts needed for the VP30)

very nice...

GinSonic.

That is correct. In the data I have from DVDO there are no output format settings for 24p. It will be trivial to add (change to ini file) when They implement and tell me what they are.

Pharados,

I have already generated a list of all the IR codes and it would be easy to have that capability made part of the released version. I even tried to use hextoccf tool but it did not like what I produced. Could you send me a sample of the hextoccf input that works and I am sure I can do what you are asking. Will take me a couple of hours as soon as I find the time.

@barry:

is it possible that you could generate a CCF file from your tool ? or is it possible to generate a list which is to be read with the HEX2CCF tool and this is generating the ccf file for all commands ?

…..

Pharados,

I have already generated a list of all the IR codes and it would be easy to have that capability made part of the released version. I even tried to use hextoccf tool but it did not like what I produced. Could you send me a sample of the hextoccf input that works and I am sure I can do what you are asking. Will take me a couple of hours as soon as I find the time.

Having such a CCF file with all the IR commands would be very helpful also for ‘non-Pronto’ people, like me. This would save me a lot of work if I could already import the codes for my Universal Remote Control (MX-3000) from an already available ccf file.
_____
Axel

Thanks that enabled it. When I set the output format to 1080p-24 the Judder test pattern is pretty...juddery. It is much smoother on 1080p-60.

Are other RS1 owners getting smooth display of the Judder test pattern at 1080p-24? Yes, I understand what you mean. But still the video output from a Blu Ray or HD DVD source has less judder when output is set to 1080p24 than when at 1080p60. Don't forget to set deinterlacing to 3:2 forced.
Hi, I'd like to circle back on this to validate that what I'm seeing is normal and optimal. Are all RS1 owners seeing jerky playback of the VP50 internal judder test pattern when outputting 1080p24? My understanding is this is strictly a test between the VP50 and RS1 irrespective of source and deinterlacing settings.

I can see the point that 24p could be less smooth than 60p and is more appropriate for film source...but it still feels counter to expectations that a test pattern would look worse on an optimal setting (24p).

So I just received my VP50 yesterday and have a quick question....

Acording to the manual it was suppose to include the USB-to-Serial Adapter and Rack Mount Kit. Did everyone else receiving these as part of thier package?

Mike

FYI.... I did order it thru an authorized reseller, just in case...


UPDATE: Talked to tech support and they say it was just a misprint in their owners manual (and their website - at least for the USB-to-Serial Adapter).

Hi, I'd like to circle back on this to validate that what I'm seeing is normal and optimal. Are all RS1 owners seeing jerky playback of the VP50 internal judder test pattern when outputting 1080p24? My understanding is this is strictly a test between the VP50 and RS1 irrespective of source and deinterlacing settings.

I can see the point that 24p could be less smooth than 60p and is more appropriate for film source...but it still feels counter to expectations that a test pattern would look worse on an optimal setting (24p).The things you want to look for here are that:

1) There is no tearing on the moving bar - i.e., the bar is always solid and not broken.

2) The motion from step to step is consistent in both the distance the bar moves and the time between each movement.

With a faster frame rate like 60 Hz you likely can't see the individual bar motion steps. However, at 24 Hz you probably can.

I suspect you're just reacting to the very low frame rate. 24 Hz can look quite juddery, particularly with this type of very high-contrast panning object. Also remember that this test pattern at 60 Hz updates a full 60 times per second and also doesn't have any 3:2 pulldown induced judder. 60 Hz should look much smoother than 24 Hz.

- Dale Adams

I sent this information to DVDO, but did not get a response. Figured it wouldn’t hurt to say something here in case Josh thought it might be helpful to pass on to engineering.

I had this problem with the white line across the top of my screen from my SD satellite feed (Dishnet 635) directly into the VP50 via S-vid. No other sources gave me this problem, just the 635.

When I re-routed this feed into my receiver first (Marantz SR8001), then out to the VP via HDMI, it went away. One function my receiver has, is it converts all non HDMI inputs to HDMI output.

If DVDO engineering has not figured out how to fix this bug, the problem may be somewhere in the conversion process to HDMI.

Okay I had some free time so the Utility is now updated to produce a hex file suitable for the Hex2CCF utility. It is on my web site (www.the-gordons.net). Please read the manual which has been updated with info on the file contents and how to use the HEX2CCF utility. I have included a copy of the HEX2CCF utility in the update package as it is not always easy to locate.

The one negative is that when generating the HEX2CCF file I do not generate all possible codes, but only those that are command enumerations. I do not generate IR patterns for commands that are ranges (e.g. Brightness). If you need those and want all possible IR codes, the utility will generate a list (txt file) which is similar to the hex file but contains things that the HEX2CCF utility does not like.

I bought the Xbox 360 Elite with the HDMI out. I connected it to the VP50. 1080i works perfectly but 1080p is not recognized. Any ideas?

Just to let you know 1080p with the PS3 works perfectly.

(on a side note, HDMI 1080i thru the VP50 looks considerably better than the component 1080i with the VP50 on my 45" Sharp panel. The picture appears to be much sharper. )

VP50 FW 1.04 Problem

I am curious if any one else is seeing this. About once a week I will completely lose audio. It happens only with the DVR's (SA8300HD) and when I am fast forwarding or skipping backwards. To get audio back I need to force an HDMI re-handshake between that DVR and the VP50 which I do by switching to another DVR input and then back.
This problem with HDMI audio has been around since the VP30, it is not unique to firmware 1.04. I have 3 different HDMI sources and it occasionally happens with all of them, so I doubt the problem is with your DVR. I don't think it ever occurred unless I was doing some operation such as FF, RW, menu, etc. The only solution I have found is the switching of inputs that you mentioned.

I bought the Xbox 360 Elite with the HDMI out. I connected it to the VP50. 1080i works perfectly but 1080p is not recognized. Any ideas?

Just to let you know 1080p with the PS3 works perfectly.

(on a side note, HDMI 1080i thru the VP50 looks considerably better than the component 1080i with the VP50 on my 45" Sharp panel. The picture appears to be much sharper. )

I have 1080P working perfectly between my Elite and the VP50. For some reason, it took a couple of times changing to it on the 360 to make it stick. However, since then it has worked great. SJ

I have 1080P working perfectly between my Elite and the VP50. For some reason, it took a couple of times changing to it on the 360 to make it stick. However, since then it has worked great. SJ

Do you mean, turning the VP50 on/off or just switching between inputs? Also, which version of the VP50 software do you have?

I suspect you're just reacting to the very low frame rate. 24 Hz can look quite juddery, particularly with this type of very high-contrast panning object. Also remember that this test pattern at 60 Hz updates a full 60 times per second and also doesn't have any 3:2 pulldown induced judder. 60 Hz should look much smoother than 24 Hz.

Well, as I mentioned earlier here, I have this motion stutter, too. And I don't think it's something normal.
I used to work as a movie theater projectionist and I'm pretty familiar with 24Hz stutter (or 48Hz stutter in that case). But what I see with the VP50 <-> RS1 is really worse that that.
It looks more like some kind of micro tearing...
I already sent an email to ABT about this and hope to have this problem solved in the not too distant future.

Cheers!

Well, as I mentioned earlier here, I have this motion stutter, too. And I don't think it's something normal.
I used to work as a movie theater projectionist and I'm pretty familiar with 24Hz stutter (or 48Hz stutter in that case). But what I see with the VP50 <-> RS1 is really worse that that.
It looks more like some kind of micro tearing...
I already sent an email to ABT about this and hope to have this problem solved in the not too distant future.

Cheers!
I am seeing the same thing as well. I'd assumed that it was "normal" - is there *anyone* out there seeing a "smooth" pan?

I bought the Xbox 360 Elite with the HDMI out. I connected it to the VP50. 1080i works perfectly but 1080p is not recognized. Any ideas?

Just to let you know 1080p with the PS3 works perfectly.

(on a side note, HDMI 1080i thru the VP50 looks considerably better than the component 1080i with the VP50 on my 45" Sharp panel. The picture appears to be much sharper. )

On a sort-of related thought, does the XBox 360 Elite enforce HDCP on game content, or just movie content? I have my VP50 connected to both a projector (HDMI) and an LCD monitor (VGA). If I just connected the Elite to the VP50 by HDMI, would I be able to transcode video to analog in the VP50 when playing a game?

Something I've been curious about.

Well, as I mentioned earlier here, I have this motion stutter, too. And I don't think it's something normal.
I used to work as a movie theater projectionist and I'm pretty familiar with 24Hz stutter (or 48Hz stutter in that case). But what I see with the VP50 <-> RS1 is really worse that that.
It looks more like some kind of micro tearing...If you look at the post of mine you referenced, you'll see that I was referring only to behavior with the VP50's judder test pattern. Are you seeing the behavior you describe above with the test pattern or with normal video material? If display of the test pattern is not clean, then display of normal video material won't be either.

- Dale Adams

I have just posted a version of the DVDO utility that directly generates Pronto CCF files for all IR commands that are enumeration types (e.g. Format, Input selection etc.), but not ranges such as Contrast or Brightness. Perhaps DVDO will eventually add "+1" and "-1" for commands that have ranges as their values. If that were the case then IR commands for those commands would make a lot of sense.

Feedback on any issues appreciated. Please read the manual it has been updated with information germane to this new capability.

Do you mean, turning the VP50 on/off or just switching between inputs? Also, which version of the VP50 software do you have?

I had to switch to 1080P on the 360 a couple of times. My projector had to sync up. Did not switch inputs on the VP50. I'm running the current beta 1.04. SJ

I have just posted a version of the DVDO utility that directly generates Pronto CCF files for all IR commands that are enumeration types (e.g. Format, Input selection etc.), but not ranges such as Contrast or Brightness. Perhaps DVDO will eventually add "+1" and "-1" for commands that have ranges as their values. If that were the case then IR commands for those commands would make a lot of sense.

Feedback on any issues appreciated. Please read the manual it has been updated with information germane to this new capability.

Barry thanks for all of your work on these. Is the program called GENIRDB on your website?

SJHT

No, that is an old program that can generate IR codes for almost any device any format.

The DVDO utility program is what you want. Go to the bottom of the home page, follow the link for downloads and documentation. Find the DVDO utility and download the upgrade. If you are running windows XP or better it is all you should need. Unzip everything in the archive to a single directory of your choosing. READ THE MANUAL. Run the exe. Fill in what you are asked for.

I have just posted a version of the DVDO utility that directly generates Pronto CCF files for all IR commands that are enumeration types (e.g. Format, Input selection etc.), but not ranges such as Contrast or Brightness. Perhaps DVDO will eventually add "+1" and "-1" for commands that have ranges as their values. If that were the case then IR commands for those commands would make a lot of sense.

Feedback on any issues appreciated. Please read the manual it has been updated with information germane to this new capability.
Thanks - when importing the CCF into PPE-NG, the button names are just numbers & the names of each IR command is "Learned" so there doesn't seem any way of knowing which button does what?

I had to switch to 1080P on the 360 a couple of times. My projector had to sync up. Did not switch inputs on the VP50. I'm running the current beta 1.04. SJ

I tried it again. I can switch between 1080i/1080p/etc. with no issues from the Elite/VP50. Works perfect every time after my projector resyncs. SJ

SJHT

No, that is an old program that can generate IR codes for almost any device any format.

The DVDO utility program is what you want. Go to the bottom of the home page, follow the link for downloads and documentation. Find the DVDO utility and download the upgrade. If you are running windows XP or better it is all you should need. Unzip everything in the archive to a single directoiry of your choosing. READ THE MANUAL. Run the exe. Fill in what you are aksed for (there is an option to only make the IR generator, but that IMHO is silly.

Thanks. SJ

So I just got the VP50 yesterday, but today I tried to upgrade the firmware and it seemed to hang part of the way thru... Now the VP50 says "Serious Error 5, contact your distributor"

:(

Also I was having some issues before I updated the firmware, where I can get the menu from the VP50 to display on the projector, but when I select HDMI1, HDMI2, etc... I never see any video from the connected device.

I tried to call DVDO tech support a little before 5pm, but it went to the ansering maching. I guess I will try back on Monday.

Mike

I am new to this. I have been a technophile for many years and decided yesterday to order a new VP50. Today I found this site and I just don't know what to say. I spent over 6 hours reading through the posts to find that this VP50 appears to be poorly designed, poorly implemented and modestly supported.

I can't believe people would spend over $2000 for a device with this apparent number of problems. It appears that there have been dozens to hundreds of posts regarding audio dropouts, lack of technical information on features, absence of features clearly promoted on the DVDO site, frustration, anger and disappointment with a project that so many had such high hopes for.

I am supposed to receive my unit tomorrow or Monday and I have an honest question?

Why should I keep the unit? I have seen very little optimism from the customer base regarding bug fixes, updates and a future where the customers actually can rely on their VP50's.

If I am wrong, show me. If there is a light at the end of the tunnel (and it is not a train coming headon...) show me.

I don't know about all of you, but I worked hard for my $2000 and I believe that a product manufacturer has an obligation to get the bugs fixed and the product working as advertised...otherwise what good is it and who needs the angst?

I don't mean to let the air out of anyone's balloon...but come on....I have seen this great wailing and gnashing of teeth in several months of posts.....

I would like to hear your comments....good....bad...or ugly..

And one more thing......I would really like to hear from ABT regarding their committment to their product....is that asking too much????

Mike

Plug it in and try it. Mess with it a little bit and decide for yourself.

I personally am glad I have the VP50. It definately improves the signal coming from a high end htpc that I built for hd movies.

I'm satisfied and I've been thru three or four dvdo scalers. If all you are in for is $2000, I think you got a bargain. By the time I consider what I've paid for scalers I have closer to $5000 in my VP50.

Still worth it. IMHO

Since the last Firmeware i am glad again. The VP50 is a great Unit.

Thanks for the last update!

every device or equipment has it's problems, i'm happy with my vp50 as it is, it could be better and i hope dvdo is working on it.


find in the world an equipment where 100% of the people are happy with. and i buy it. but this will never happen ! :D

When I had a plasma as my sole display device, I tried out an earlier DVDO processor and could not justify the expense.

Now I am very happily into front projection, I would not be without my VP50.
For me it does (and now very well after update to Firmware 1.04) -

1080 HDMI switching of 3 sources

6 profiles - for PAL DVD, Digital TV, Bluray and HDDVD with appropriate aspect ratios

aspect ratio management for a constant height setup

Picture controls for each input independent of the projector

Frame rate conversion to 1080p24

I agree that there have been some frustrations waiting for the firmware to catch up with advertised specs. But now, for me it does everything I want and will be staying in my system indefinitely.

Are you seeing the behavior you describe above with the test pattern or with normal video material? If display of the test pattern is not clean, then display of normal video material won't be either.
The judder is there in both cases, and it's most visible with the test pattern (the "judder bar").

Cheers!

The judder is there in both cases, and it's most visible with the test pattern (the "judder bar").Then, unless somehow ABT has broken the judder test pattern (which I suppose is possible, but I doubt it), there is either a display problem at this frame rate, or an incompatibility of some sort with the specific resolution/timing the VP50 is producing. You might want to try the different 1080p timings provided (i.e., 1080p60, 1080p48, etc.) running at a 24 Hz frame rate to see if this makes a difference to the projector.

- Dale Adams

Hi! I’m a VP50 owner from Italy. I used the unit without a problem for more than 3 months.

Some day ago I’ve upgraded to 1.04 firmware. The operation was successfully concluded and the processor seems to work.

But there’s a new problem: I use to unplug everything when not in use (before unplugging I switch off the vp50 with his frontal button). Now if I unplug the vp50 when I plug it back the screen is all messed up and I have noise from all audio outputs. At first the issue was resolved doing a factory default reset, but I’ve discovered that this is not necessary: If I unplug the power chord again and immediately plug it back everything works again. This happens ALL the time, if the vp50 is unplugged for more than 10 minutes when I plug it back it doesn’t work. Obviously I used to do the same thing (plug/unplug) in the past without a problem – this *before* upgrading to 1.04 firmware.

Any help or suggestion will be greatly appreciated.

Thank you,



Luigi

Why should I keep the unit? I have seen very little optimism from the customer base regarding bug fixes, updates and a future where the customers actually can rely on their VP50's.



One thing to consider is that the majority of posts in forums such as this are going to be from people having problems or asking questions about configuration. I think there is a much larger customer base (like me) who own the VP50 and either are not having problems with it or are not using the features causing problems.

I am new to this. I have been a technophile for many years and decided yesterday to order a new VP50. Today I found this site and I just don't know what to say. I spent over 6 hours reading through the posts to find that this VP50 appears to be poorly designed, poorly implemented and modestly supported.

I can't believe people would spend over $2000 for a device with this apparent number of problems. It appears that there have been dozens to hundreds of posts regarding audio dropouts, lack of technical information on features, absence of features clearly promoted on the DVDO site, frustration, anger and disappointment with a project that so many had such high hopes for.

I am supposed to receive my unit tomorrow or Monday and I have an honest question?

Why should I keep the unit? I have seen very little optimism from the customer base regarding bug fixes, updates and a future where the customers actually can rely on their VP50's.

If I am wrong, show me. If there is a light at the end of the tunnel (and it is not a train coming headon...) show me.

I don't know about all of you, but I worked hard for my $2000 and I believe that a product manufacturer has an obligation to get the bugs fixed and the product working as advertised...otherwise what good is it and who needs the angst?

I don't mean to let the air out of anyone's balloon...but come on....I have seen this great wailing and gnashing of teeth in several months of posts.....

I would like to hear your comments....good....bad...or ugly..

And one more thing......I would really like to hear from ABT regarding their committment to their product....is that asking too much????

MikeYou feelings are entirely understandably. I ordered a HD+ some years ago because this device was perfectly stable and did hardly contained any bugs (exception: discrete codes not working). Based on my very positive experience with the HD+ I upgraded to VP30 + ABT card. This turned out to be a mistake. Too many bugs for me and incredible delays in support. After a year (!) the most prominent bug (audio bug) was solved, but about six bugs are pending and hardly response from DVDO, despite detailed reports by mail (credit: except for Josh during a private beta audio test). Because the audio bug is solved, the device is finally usable, but I had to wait a looong time. These support problems made me decide not to spend my money on DVDO products again (credit: VP50 support seems better at the moment). My feeling it that DVDO is either not capable to support their scalers in a reasonable amount of time (if a top programmer leaves, a company like this could be in trouble), or made a management decision to minimize the time spent in their scaler support. But who knows? Maybe in a few months time support will be flowing like a spring river ;)

Then, unless somehow ABT has broken the judder test pattern (which I suppose is possible, but I doubt it), there is either a display problem at this frame rate, or an incompatibility of some sort with the specific resolution/timing the VP50 is producing. You might want to try the different 1080p timings provided (i.e., 1080p60, 1080p48, etc.) running at a 24 Hz frame rate to see if this makes a difference to the projector.

- Dale Adams

I too have an RS1 and may be experiencing something similar. On all of the HD DVDs I've watched since the 1.04 update I get occasional, brief episodes of obvious stutter. These do not recur when I replay the scene and typically only last several seconds. I'm outputting 1080 24p and have deinterlacing set to Fixed 3:2.

I have not looked at the judder test pattern but will do so tonight and report back.

EDIT: Audio dropouts via DTS Audio discs with my Oppo are still there, just a reduced amount.

I tired duplicating this bug and in my system the only time that I had audio dropouts was when the VP50 broke or achieved HDCP authentication with the projector. Here is my configuration:

Audio Chain: Oppo DV970HD -HDMI-> DVDO iScan VP50 -Coax-> B&K AVR507
Video Chain: Oppo DV970HD -HDMI-> DVDO iScan VP50 -HDMI-> JVC RS1

Although, DTS CDs don't require HDCP, an HDMI connection does. The easiest way to fix this would be to make a direct connection with an optical or coaxial connection from the Oppo to your AV receiver. If you have a universal remote, you could simply create a macro titled 'CD' or 'DTSCD', to simplify the switching.

OK. Let's say you have your 970 in the VP50 HDMI 1 (input) and other devices in other inputs (HDMI 2, component 1, etc.). Then you set the input priority to #1 for HDMI 1 (the 970) and #2 for another device, #3 for another, etc.... If you have the input select on AUTO and the 970 ON, it should select the 970 (because it is #1 in the priority list). When you turn the 970 OFF, the VP50 should then select the next active signal in the list (#2, #3, - whatever is on). On my setup, when I turn off the 970, the VP50 REMAINS on HDMI 1 (even the VP50 INFO screen shows NO SIGNAL). Make sense? SJ


I tried to duplicate this today after re-routing my cables. But where is this “Auto” input function? I do not see it anywhere.

I assigned all my inputs a priority, but the VP will not switch from one input to the other unless I select that input. Not a big deal to me a I use a macro set up to switch devises with my MX-850, but I supose the feature would be cool.

'Auto' input switching is available on the remote control, big button at the bottom right, and in the OSD, in the 'Input Select' menu at the very bottom.

Is it possible that I could have one dead HDMI input? :confused: I have tried moving my HDMI signal across the other three inputs without any issue. I even tried to use barrygordons utility to see if there was anything "interesting" going on with that input. The only thing I could tell (which was obvious) was that it wasn't seeing any signal. The LED on the front panel always stays red.

BTW, the firmware is upgraded to 1.04.

Anyone have any thoughts or ideas? Is this a hardware failure?

I too have an RS1 and may be experiencing something similar. On all of the HD DVDs I've watched since the 1.04 update I get occasional, brief episodes of obvious stutter. These do not recur when I replay the scene and typically only last several seconds. I'm outputting 1080 24p and have deinterlacing set to Fixed 3:2.

I have not looked at the judder test pattern but will do so tonight and report back.Well then you haven't experienced something similar since, again, my comments refer only to using the judder test pattern. By all means check out the behavior of the RS1 with this test pattern on the VP50 and let us know what you find. If you're seeing stutter on that, then you'll never see a stutter free image with HD DVDs as there's something more fundamentally broken in the chain than just converting 60 Hz 3:2 pulldown to 1080p24. Without having a VP50 and and RS1, though, I can't tell you whether it's a problem in the RS1, an incompatibility between the VP50's output and the RS1, or something else altogether. [Also note that I'm assuming here that the VP50 test pattern generator is working correctly, which I believe has been the case with every other output format tested to date.]

- Dale Adams

I can't believe people would spend over $2000 for a device with this apparent number of problems. It appears that there have been dozens to hundreds of posts regarding audio dropouts, lack of technical information on features, absence of features clearly promoted on the DVDO site, frustration, anger and disappointment with a project that so many had such high hopes for.

I am supposed to receive my unit tomorrow or Monday and I have an honest question?

Why should I keep the unit? I have seen very little optimism from the customer base regarding bug fixes, updates and a future where the customers actually can rely on their VP50's.
Not to diminish anyone's legitimate problems with their VP50s...

But keep in mind, that most of the problems affect a small minority of users and the VP50 is working great for most people.

It also has some unique features among video processors, and has by far the most versatile options for deinterlacing--PReP, low latency game modes, four different pulldown detection options (auto, film bias, forced, and disabled).

Try reading the threads for some of the other video processors, and you'll see that the sense of frustration exists for other products, too.

I tired duplicating this bug and in my system the only time that I had audio dropouts was when the VP50 broke or achieved HDCP authentication with the projector. Here is my configuration:

Audio Chain: Oppo DV970HD -HDMI-> DVDO iScan VP50 -Coax-> B&K AVR507
Video Chain: Oppo DV970HD -HDMI-> DVDO iScan VP50 -HDMI-> JVC RS1

Although, DTS CDs don't require HDCP, an HDMI connection does. The easiest way to fix this would be to make a direct connection with an optical or coaxial connection from the Oppo to your AV receiver. If you have a universal remote, you could simply create a macro titled 'CD' or 'DTSCD', to simplify the switching.

So with that setup, can you confirm the AUTO/select does not work with the OPPO 970?

I'm one of those with almost no problems with my VP50. I was running 1.00 until this week, bought the unit when it was first released. Was fine running 3 hdmi devices and one SDI.

I said almost because ever since I added a Panny BR player it messes with my Snazzio, with is DVI out using dvi->hdmi cable. I get no video out of the snazzio after using the Panny and had to unplug it. This was all under 1.00 FW. Have yep to try it on 1.04. Wasn't a big deal as I mostly watched HD-DVDs and not too many BRDs.

I only upgraded to 1.04 to get PReP. :)

I can not get the Auto input function to work at all. It stays on the last input, no matter what I’ve tried or how I set up the input priorities.

I personally don’t care, as I don’t want to use this feature. But others may want to fool with it.


I’ve watched about ten hours of different sources (B/R, HD/DVD, DVD, and satellite feed) after routing into the VP first, then out to my receiver. I am very happy to report that I have not had one single audio drop out, chirp or squeal. I’m a pretty happy camper so far.

1080P / 24/24 works flawlessly with forced 3/2 selected. 1080/60 works fine too.

Now what am I going to bitch about?? I guess it’s time to buy something else just so I can bitch.

I tired duplicating this bug and in my system the only time that I had audio dropouts was when the VP50 broke or achieved HDCP authentication with the projector. Here is my configuration:

Audio Chain: Oppo DV970HD -HDMI-> DVDO iScan VP50 -Coax-> B&K AVR507
Video Chain: Oppo DV970HD -HDMI-> DVDO iScan VP50 -HDMI-> JVC RS1

Although, DTS CDs don't require HDCP, an HDMI connection does. The easiest way to fix this would be to make a direct connection with an optical or coaxial connection from the Oppo to your AV receiver. If you have a universal remote, you could simply create a macro titled 'CD' or 'DTSCD', to simplify the switching.


It would be easy if they were on the same rack but with the VP50 and oppo in my rack in the basement and the Onkyo in a remote location (with a Coax already connected) to it, it is kind of difficult to do this. In my primary room, I use the 5.1 channel out to my preamp without problems. Running another 30' coax is not fun.

mdrew, I'm with you. The analog and sdi work fine with Auto. HDMI doesn't though.

I can not get the Auto input function to work at all. It stays on the last input, no matter what I’ve tried or how I set up the input priorities.

I personally don’t care, as I don’t want to use this feature. But others may want to fool with it.


I’ve watched about ten hours of different sources (B/R, HD/DVD, DVD, and satellite feed) after routing into the VP first, then out to my receiver. I am very happy to report that I have not had one single audio drop out, chirp or squeal. I’m a pretty happy camper so far.

1080P / 24/24 works flawlessly with forced 3/2 selected. 1080/60 works fine too.

Now what am I going to bitch about?? I guess it’s time to buy something else just so I can bitch.

You can use both the remote to select AUTO and the menu system. It is the last input in the list... SJ

mdrew, I'm with you. The analog and sdi work fine with Auto. HDMI doesn't though.
I think this has been covered before, but AFAIK the problem is due to the fact that many HDMI/DVI devices leave a clock signal actively running on their output even though the power has been switched to Standby. Unplugging the device(s) is the only way to disable to clock signal. My HD STB has this problem, preventing the AUTO function from working properly when one of the HDMI inputs is next on the priority list. It also affects AUTO standby as well of course. Like many others, I have programmed my Harmony Remote to do the input switching on the VP50/30.

You might want to try the different 1080p timings provided (i.e., 1080p60, 1080p48, etc.) running at a 24 Hz frame rate to see if this makes a difference to the projector.
Took me some time to check the different timings but they really make no difference to me. :(
Judder pattern and 24Hz video look just as juddery as before.

Took me some time to check the different timings but they really make no difference to me. :(
Judder pattern and 24Hz video look just as juddery as before.Thanks for checking. I'll see if I can get access to a VP50 to verify that the judder test pattern hasn't been broken somehow, and that it's really doing what it's supposed to be doing with a 1080p output at 24 Hz.

- Dale Adams

Thanks, Dale! :)

I'm trying to use the HDNet test pattern and the VP-50's half color bar test patterns to adjust saturation on my sat. box (HR20-700).

Yes, I do know there are problems with the HDNet test pattern, so I'm just using it as a guide, and will tweak picture later.

Anyone know if I should be using the 75 or 100 color bars with the HDNet (1080i) color bar test pattern?

Thanks!

Eric

How about using the ABT test disc that came with the VP50? I *think* that I recall seeing a judder pattern there. I haven't got a chance to actually try and see if 1080p/24Hz with forced 3:2 (using 480i HDMI out from the dvd player) will be any smoother. Has anyone else tried this? And will it matter?

Is it possible that I could have one dead HDMI input? :confused: I have tried moving my HDMI signal across the other three inputs without any issue. I even tried to use barrygordons utility to see if there was anything "interesting" going on with that input. The only thing I could tell (which was obvious) was that it wasn't seeing any signal. The LED on the front panel always stays red.

BTW, the firmware is upgraded to 1.04.

Anyone have any thoughts or ideas? Is this a hardware failure?


Will someone please reply to this? Thanks!

I'm trying to use the HDNet test pattern and the VP-50's half color bar test patterns to adjust saturation on my sat. box (HR20-700).

Yes, I do know there are problems with the HDNet test pattern, so I'm just using it as a guide, and will tweak picture later.

Anyone know if I should be using the 75 or 100 color bars with the HDNet (1080i) color bar test pattern?

Thanks!

Eric

Typically, it is the 75% Color Bars which are used on a setup DVDs. I will have to record the HDNet Test Patterns to verify but I would guess that they are 75% Color Bars, not 100%.

Is it possible that I could have one dead HDMI input? :confused: I have tried moving my HDMI signal across the other three inputs without any issue. I even tried to use barrygordons utility to see if there was anything "interesting" going on with that input. The only thing I could tell (which was obvious) was that it wasn't seeing any signal. The LED on the front panel always stays red.

BTW, the firmware is upgraded to 1.04.

Anyone have any thoughts or ideas? Is this a hardware failure?

This is certainly possible. Do you have any other HDMI sources that you can check the input with?

Well then you haven't experienced something similar since, again, my comments refer only to using the judder test pattern. By all means check out the behavior of the RS1 with this test pattern on the VP50 and let us know what you find. If you're seeing stutter on that, then you'll never see a stutter free image with HD DVDs as there's something more fundamentally broken in the chain than just converting 60 Hz 3:2 pulldown to 1080p24. Without having a VP50 and and RS1, though, I can't tell you whether it's a problem in the RS1, an incompatibility between the VP50's output and the RS1, or something else altogether. [Also note that I'm assuming here that the VP50 test pattern generator is working correctly, which I believe has been the case with every other output format tested to date.]

- Dale Adams

I tried the judder test on my RS1 and it appears to be working correctly. It is not smooth but there is no tearing. The bar appears to be moving in small, quick steps and each "step" appeared uniform. This was using 1080p24.

This is certainly possible. Do you have any other HDMI sources that you can check the input with?


I have both a Tivo Series 3 and a Toshiba XA2. Both work in HDMI2-4, but nothing is happening with HDMI1. I am local. Can I bring it to DVDO for repair?

Can I bring it to DVDO for repair?

Please arrange this with Tech Support, Help@dvdo.com or 1-866-423-3836 extension 333.

I tried the judder test on my RS1 and it appears to be working correctly. It is not smooth but there is no tearing. The bar appears to be moving in small, quick steps and each "step" appeared uniform. This was using 1080p24.

I experienced exactly the same thing.

How about using the ABT test disc that came with the VP50? I *think* that I recall seeing a judder pattern there. I haven't got a chance to actually try and see if 1080p/24Hz with forced 3:2 (using 480i HDMI out from the dvd player) will be any smoother. Has anyone else tried this? And will it matter?

The judder test pattern is smooth as silk with my display at 1080P/24 + 24 and 3:2 locked.

I tried the judder test on my RS1 and it appears to be working correctly. It is not smooth but there is no tearing. The bar appears to be moving in small, quick steps and each "step" appeared uniform. This was using 1080p24.That's the expected behavior if the display supports 24 Hz input (and assuming that the VP50's judder test pattern is working as expected).

The fact that each step appears uniform is good. The only remaining question is whether there is a uniform period between each step. Unfortunately, that may be hard to judge subjectively due to the low frame rate. Normally you could just 'eyeball' the motion to see if it's smooth and even. This works well with higher frame rates. However, one problem with judging smooth motion with this test pattern at 24 Hz is that the moving bar has very high contrast (i.e., white bar moving on black background). This type of high-contrast horizontal panning motion will typically appear to be jerky due to the low frame rate of 24 Hz even if there is a uniform step size and a uniform period between each step.

Can you tell if the motion you see with this test pattern is any different than what you see with a 3:2 pulldown source? In other words, does the test pattern appear to have the same periods stutter (it sounds like it does not), or is that unique to using the 3:2 sources?

- Dale Adams

The judder test pattern is smooth as silk with my display at 1080P/24 + 24 and 3:2 locked.Does the VP50's built-in judder test pattern look as smooth as the one on the ABT DVD? If so, then it sounds like there may be an issue of some sort with the VP50's 3:2 cadence detection of HD sources and/or conversion to 24 Hz output, or perhaps with the output of the HD DVD players being used (but that's not really clear at this point).

- Dale Adams

Please a need a help, a hint an advice: anything!
I've used the vpo50 for over 3 months upgrading from 1.0 to 1.01 without a problem.
Now i've upgraded to 1.04 and when i unplug the unit and then plug it back the video is all scrambled on all inputs, even if the vp50 menu are still clear and usable (with no positive effect on the scrambled video). The only ways to make it work again are: a hard reset, a soft reset or unplugit-plug it again, then it works, even for hours with no problem.
But when i unplug it again (i used to do this all the time) and then plug it back next day the error is there again!
I've re-installed firmware 1.01 and everythings works again without a problem. Someone suggest me that this strange behavior is because of an hardware failure: but why with 1.04 and NOT with 1.01..
I'm really confused, please advice.
Thank you,

Luigi

P.S. forgive my bad english

Have you tried going back to 1.04? I had a problem before with one of my firmware updates, not as extreme as yours but I had some problems. Once I reflashed it with the same firmware I was fine.

Can anyone from ANCHOR BAY or the "wicked" smart people give me a little bit of set-up help. I have the vp50 hooked up via hdmi to my dtv hr20 700. I have the output set to the pannys native res. I can only get a picture with 1080i-60. I do not see a picture difference at all. The HD looks like HD and the 480i looks like it did without the processor. I have heard great things about this processor and I am NOT VERY smart when it comes to the set up. Anyone have any tips to get the 480i looking better or MY WIFE IS GOING TO KILL ME. lol

Can someone please verify that the discrete for the VP50 auto deinterlacing works or not. I created the code from Barry's utility. I wanted to create a discrete for GAME 1 and AUTO. Game 1 works perfect, but AUTO does not seem to work. Thanks. SJ

SJHT

go back a couple of messages and find the one where I state that AUTO does not work and DVDO agrees that it does not work. It is on page 145 of this thread.

That's the expected behavior if the display supports 24 Hz input (and assuming that the VP50's judder test pattern is working as expected).

Can you tell if the motion you see with this test pattern is any different than what you see with a 3:2 pulldown source? In other words, does the test pattern appear to have the same periods stutter (it sounds like it does not), or is that unique to using the 3:2 sources?

- Dale Adams

OK - being a novice I need a specific example of a 3:2 pulldown source so I can try this.

OK - being a novice I need a specific example of a 3:2 pulldown source so I can try this.That would be pretty much any movie. ;) 24 Hz film sources are transferred to 60 Hz video using 3:2 pulldown. Consequently, nearly every feature film that's on DVD or HD media is shown on 60 Hz video using the 3:2 pulldown technique. (There are a few exceptions, but they're rare. Also, note that content such as some TV shows and concert video often does not originally come from film and is native 60 Hz.) Is there a specific movie with which you've seen motion stutter problems?

- Dale Adams

Please a need a help, a hint an advice: anything!
I've used the vpo50 for over 3 months upgrading from 1.0 to 1.01 without a problem.
Now i've upgraded to 1.04 and when i unplug the unit and then plug it back the video is all scrambled on all inputs, even if the vp50 menu are still clear and usable (with no positive effect on the scrambled video). The only ways to make it work again are: a hard reset, a soft reset or unplugit-plug it again, then it works, even for hours with no problem.
But when i unplug it again (i used to do this all the time) and then plug it back next day the error is there again!
I've re-installed firmware 1.01 and everythings works again without a problem. Someone suggest me that this strange behavior is because of an hardware failure: but why with 1.04 and NOT with 1.01..
I'm really confused, please advice.
Thank you,

Luigi

P.S. forgive my bad english
Hi Luigi,

I've just upgraded to Vs 1.04 myself (from vs 1.00). I guess you're not getting overun with replies to your query/problem because like me, I guess very few people remove the power from their VPs. For me for example, it would be very inconvenient to do so as getting to the power point into which the VP is plugged into is VERY hard to reach :eek: . Apart from other equipment, I also have a PVR attached to the same power board/mains filter/UPS, so pulling the plug on the whole HT setup is not on as the PVR makes recordings at any time.

So, sorry, I haven't tried doing this either, (and I'm guessing that maybe many of us don't want to either, just in case we have the same problem :o ), but it sounds to me like this could be a hardware problem. I can't remember from any of your previous posts on this problem, but have you emailed DVDO directly about it?

SJHT

go back a couple of messages and find the one where I state that AUTO does not work and DVDO agrees that it does not work. It is on page 145 of this thread.

Thanks. I missed that one.. and, by the way, your utility for generating IR hex is fantastic! SJ

Hi Luigi,

....
So, sorry, I haven't tried doing this either, (and I'm guessing that maybe many of us don't want to either, just in case we have the same problem :o ), but it sounds to me like this could be a hardware problem. I can't remember from any of your previous posts on this problem, but have you emailed DVDO directly about it?

HI, thanks for the reply. In fact i do not actually "unplug" my machines: i have a dedicated power line for all the hi-fi/ht hardware that i simply switch on/off alltogether.
I have emailed dvdo but had no reply so far.
The strange thing is that the vp50 reverted to 1.01 firmware show no problems at all. If it was an hardware problem than i should have it with any firmware release.
So confused ... :confused:

Have you tried going back to 1.04? I had a problem before with one of my firmware updates, not as extreme as yours but I had some problems. Once I reflashed it with the same firmware I was fine.


HI, i've flashed 3 times the vp50 with 1.04 but nothing changes. I haven't tried yet to reflash it from 1.01 to 1.04.
Also: i've noticed that the baud rate on the vp50 was higher than reccomended .. but the operation concluded succesfully ...

I've noticed that with "Forced 3:2" deinterlacing, I occasionally see what look like bief horizontal scan line type artifacts on screen during bright flashes of light such as explosions or camera flashbulbs. Has anyone else notice this?

HI, thanks for the reply. In fact i do not actually "unplug" my machines: i have a dedicated power line for all the hi-fi/ht hardware that i simply switch on/off alltogether.
I have emailed dvdo but had no reply so far.
The strange thing is that the vp50 reverted to 1.01 firmware show no problems at all. If it was an hardware problem than i should have it with any firmware release.
So confused ... :confused:
You'd think so but not necessarily - the new firmware might just expose a problem not noticeable with the old one. I'd be talking to my retailer to see if I could get a swap - is it still in warranty?

Have you also tried re-downloading the firrmware from dvdo to ensure the file is ok? Can't remember if they put a CRC check on them.

I've noticed that with "Forced 3:2" deinterlacing, I occasionally see what look like bief horizontal scan line type artifacts on screen during bright flashes of light such as explosions or camera flashbulbs. Has anyone else notice this?That sounds to me like the source has a break in the 3:2 pulldown sequence at the bright flash events. If so, then you may well see combing until the VP50 acquires the new 3:2 phase. (Either that or there's a problem with the forced 3:2 mode. :D ) What sources are you using when you see this behavior?

- Dale Adams

Josh I have seen the same when using forced 3:2 on what should be entirely film based professional studio DVD releases, like say "Dark Blue" I was watching last night, the video is not 24 fps like HD and BD, it is 480i 60, that is where the problem is I think, not with the actual mode

I do however still use forced 3:2 mode on HD-DVD and Blu-Ray and it is 100% perfect because those sources are actually 24 fps, I use film bias for film SD DVD's and it works perfectly the way I need it to

-Gary

You'd think so but not necessarily - the new firmware might just expose a problem not noticeable with the old one. I'd be talking to my retailer to see if I could get a swap - is it still in warranty?

Have you also tried re-downloading the firrmware from dvdo to ensure the file is ok? Can't remember if they put a CRC check on them.


Hi: i've tried to re-download it but the problem is still there.
I should pass by the warrantty, but i have a sensation that first they will load the only one official firmware release, that works ok. To call for warranty i suppose the firmware should be "official", a beta one will not do (can someone -Josh?- please confirm that?).

That sounds to me like the source has a break in the 3:2 pulldown sequence at the bright flash events. If so, then you may well see combing until the VP50 acquires the new 3:2 phase. (Either that or there's a problem with the forced 3:2 mode. :D ) What sources are you using when you see this behavior?

I'm seeing it on both HD DVDs and Blu-rays. The effect is very brief. It accompanies the bright flash.

Hi: i've tried to re-download it but the problem is still there.
I should pass by the warrantty, but i have a sensation that first they will load the only one official firmware release, that works ok. To call for warranty i suppose the firmware should be "official", a beta one will not do.
Luigi, to help put you out of your misery (and satisfy my curiosity as well :D ), I will unplug my VP50 now, just 9am my time, and plug it in again later this afternoon around 5pm. Will post the result as soon as the VP50 is up again. Stay tuned :) .

Is it possible that I could have one dead HDMI input? :confused: I have tried moving my HDMI signal across the other three inputs without any issue...
Anyone have any thoughts or ideas? Is this a hardware failure?
You might want to get a magnifying glass and a flashlight and inspect the problem socket. HDMI connectors not sturdy and it's possible you have a bent or broke pin. A few months ago I unplugged and replugged an HDMI cable and could no longer get a signal. When I inspected the cable I found that one of the pins in it had broken off. I've never had the same thing happen with the socket on a device, but given how small the pins are it's possible.

You might want to get a magnifying glass and a flashlight and inspect the problem socket. HDMI connectors not sturdy and it's possible you have a bent or broke pin. A few months ago I unplugged and replugged an HDMI cable and could no longer get a signal. When I inspected the cable I found that one of the pins in it had broken off. I've never had the same thing happen with the socket on a device, but given how small the pins are it's possible.

In this particular instance, it was a hardware failure and the unit has already been serviced and is back in Stan's (sda) hands.

Josh Z , I know this problem well, used to see it with my RP91 all the time. Usually at scene transitions. That's where the 3:2 gets broken. Used to see it on some explosions and bright flashes too. Don't know why. It's weird that you're seeing from HD-DVD/Blu Ray. Are you're players outputting 24p?

Please arrange this with Tech Support, Help@dvdo.com or 1-866-423-3836 extension 333.

Just to close the loop on this, I had a problem with HDMI1 on my VP50....no signal input capability. After contacting tech support I was first instructed to do a visual inspection of the board to ensure that there were no pins broken on the HDMI connector inside the unit. Next I was asked to do a "hard reset" of the unit. Neither of these actions corrected the problem :( , so it was off to DVDO with the unit.

I dropped it off with the expectation that I could pick it up in a couple of days. While grabbing a quick lunch, I received a call telling me the unit was repaired!

Apparently I had a bad input capacitor on HDMI1! It was quickly replaced and my VP50 is now back up and running. Thanks to Josh (through this forum) and Aaron at Anchor Bay/DVDO for their assistance and amazingly quick response to my issues. :D

That would be pretty much any movie. ;) 24 Hz film sources are transferred to 60 Hz video using 3:2 pulldown. Consequently, nearly every feature film that's on DVD or HD media is shown on 60 Hz video using the 3:2 pulldown technique. (There are a few exceptions, but they're rare. Also, note that content such as some TV shows and concert video often does not originally come from film and is native 60 Hz.) Is there a specific movie with which you've seen motion stutter problems?

- Dale Adams

I noticed several very brief episodes of stutter on Smokin Aces and Hulk on my HD A1. I looked at the setup options on the A1 and changed one of the picture settings from Auto to Film. I then watched all 3 hours of The Good Shepherd without any stutter. Perhaps the A1 was at fault.

I've noticed that with "Forced 3:2" deinterlacing, I occasionally see what look like bief horizontal scan line type artifacts on screen during bright flashes of light such as explosions or camera flashbulbs. Has anyone else notice this?
Yes, I have seen this. I saw it in the final fight scene of The Living Daylights, and during the thunderstorm in Tombstone (both DVD format). In these scenes, the light flashes were right in the middle of a shot, and the combing occurs just during and very briefly after the flash of light during a dark scene. It is very unlikely that there are cadence breaks at those immediate moments in the DVD source. Also, this occurred in "Auto" mode, not "Forced" for me. I'm still on firmware 1.0.

According to everything I know about 3:2 pulldown detection algorithms, I don't know why this would happen. Regardless of the lightness or darkness of a scene, if the 3:2 cadence is not disturbed, I'm not sure why combing would result.

I was renting the discs, so don't currently have access to them. I didn't bother testing them in other systems; I probably should have. I have a Faroudja DCDi player and an HQV Realta projector, and DScaler, so I should have experimented...was busy though :)

Luigi, to help put you out of your misery (and satisfy my curiosity as well :D ), I will unplug my VP50 now, just 9am my time, and plug it in again later this afternoon around 5pm. Will post the result as soon as the VP50 is up again. Stay tuned :) .
Well Luigi........all is well as expected (and hoped for :eek: ). All settings have been retained from their previous (before the 8 hr power off state) settings.

So, it looks like you have a hardware problem. One explanation why Vs 1.01 doesn't show the problem is that perhaps Vs 1.04 uses extra memory locations and/or maybe putting the FW in different memory locations which hithertoo were either unused or used for less critical operation(s).

I think this post should convince your retailer to give you an RMA for a replacement unit. Best of luck. :)

In Game Mode 1, and only Game Mode 1, the VP50 appears to detect and handle 240p. Here is my evidence for this:
I'm just following up on my post suggesting that the VP50 has 240p (old game) support.

<link to the original post> (http://www.avsforum.com/avs-vb/showthread.php?p=10337671&&#post10337671)

Nobody else confirmed or refuted my findings, so I experimented with it more. This time, I zoomed in as much as possible using the overscan and zoom controls, and also the zoom on my monitor, to check the deinterlacing behavior. In Game Mode 1 on both two SNES games and one NES game, there was absolutely no vertical "vibration" anywhere in the image (which would occur on any 480i source in high contrast areas in Game Mode 1). Sharp, high contrast edges were perfectly still everywhere in the image. In my mind, this confirms that the VP50 has true 240p support and from now on I will regard the VP50 as having such. Again, if somebody thinks I am mistaken, I will re-evaluate.

It's still not as high quality as DScaler's Old Game mode, because (1) the composite artifact reduction (such artifacts being visible even in S-Video) is not as good as DScaler's (in particular, this results in a visible "jump" occurring every couple of seconds, not seemingly relating to deinterlacing as it is present in all deinterlacing modes), and (2) the particular algorithm for diagonal edge interpolation in the VP50 seems to use hard thresholds in deciding the angle of interpolation, which results in constant speckly artifacts at random, in still areas, all over the image due to otherwise imperceptible noise in the signal (I'm not 100% certain but I think this is what is happening). For the same two reasons, I'm guessing that the 240p handling in the XRGB-2+ will look significantly better than that in the VP50, also, although I don't have one to test yet.

So throw 240p support in the list as yet another deinterlacing feature of the VP50 that distinguishes it from the other video processors (unless they have it too; I don't have access to any others to test).

I've noticed that with "Forced 3:2" deinterlacing, I occasionally see what look like bief horizontal scan line type artifacts on screen during bright flashes of light such as explosions or camera flashbulbs. Has anyone else notice this?

Josh Z , I know this problem well, used to see it with my RP91 all the time. Usually at scene transitions. That's where the 3:2 gets broken. Used to see it on some explosions and bright flashes too. Don't know why. It's weird that you're seeing from HD-DVD/Blu Ray. Are you're players outputting 24p?

I get this too with Toshiba HD-XE1 outputting 1080i60 (which then gets transformed to 1080p24 by VP50 and sent to Pioneer 7-gen plasma).

"Forced 3:2" gives smooth motion but introduces this combing effect with fast motion and between the scenes. The combing is also present in subtitles (which is propably a normal phenomenon). Other deinterlacing modes cause judder / lost frames. Framerate was set to locked 24Hz.

Well Luigi........all is well as expected (and hoped for :eek: ). All settings have been retained from their previous (before the 8 hr power off state) settings.

...


Escon, thanks for your help and support. I'll see what they tell me. Thanks again,

Luigi

P.S. 2 emails to help@dvdo .com and no reply yet. In the meantime i've meet on an italian forum other 2 users with the same problems only with different firmware revisions. :( :rolleyes:

Hi Luigi,

I saw your original post and sent you a PM, but I guess you have not seen it.

I have exactly the same problem as you. I reported the details to Aaron at DVDO and took the liberty of sending a copy of your post to confirm that this is not an isolated issue. He has already contacted me to confirm that they are looking into it and will come back as soon as possible.

The problem in my case only occurs with V1.04 firmware. There are no power down glitches with V1.0,1.01 or 1.03. As an engineer I have methodically gone through several cycles of re-loading and testing previous firmwares then back to 1.04. I even tried removing the SDI card in case there was a clash. From my side the problem is easily and consistently repeatable, so hopefully there will be a quick fix.
Your power up/down quick fix works.

I hope this helps to have your problem confirmed.

Dean


Escon, thanks for your help and support. I'll see what they tell me. Thanks again,

Luigi

P.S. 2 emails to help@dvdo .com and no reply yet. In the meantime i've meet on an italian forum other 2 users with the same problems only with different firmware revisions. :( :rolleyes:

Hi Luigi,

I saw your original post and sent you a PM, but I guess you have not seen it.

I have exactly the same problem as you. I reported the details to Aaron at DVDO and took the liberty of sending a copy of your post to confirm that this is not an isolated issue. He has already contacted me to confirm that they are looking into it and will come back as soon as possible.

The problem in my case only occurs with V1.04 firmware. There are no power down glitches with V1.0,1.01 or 1.03. As an engineer I have methodically gone through several cycles of re-loading and testing previous firmwares then back to 1.04. I even tried removing the SDI card in case there was a clash. From my side the problem is easily and consistently repeatable, so hopefully there will be a quick fix.
Your power up/down quick fix works.

I hope this helps to have your problem confirmed.

Dean

Hi Dean, sorry i missed you pm. Hopefully they will find a firmware based solution to this problem. I have the problem with 1.04 too. I've tried, just as you did, all the previous releases with no problem (other than the well-known firmware bugs as reported ie 24p bug). On other forums i've read of users having the same problem changing from 1.00 to 1.01, but that's not my (our) case.
Fingers crossed.
All the best,

Luigi

Hi Dean, sorry i missed you pm. Hopefully they will find a firmware based solution to this problem. I have the problem with 1.04 too. I've tried, just as you did, all the previous releases with no problem (other than the well-known firmware bugs as reported ie 24p bug). On other forums i've read of users having the same problem changing from 1.00 to 1.01, but that's not my (our) case.
Fingers crossed.
All the best,

Luigi
Hmm.. this is interesting - wonder why it's not affecting all units. I would expect that most users would not be powering down their units and that could account for the very few reports. But, I have tried it and had no problems.

The only commonality seems to be that only (mostly?) users in PAL country are affected, but hang on, I'm in PAL country (50Hz sources), so that's that one out of the window :confused:

Josh Z , I know this problem well, used to see it with my RP91 all the time. Usually at scene transitions. That's where the 3:2 gets broken. Used to see it on some explosions and bright flashes too. Don't know why. It's weird that you're seeing from HD-DVD/Blu Ray. Are you're players outputting 24p?

Both the HD DVD and Blu-ray players are outputting 1080i60 into the VP50. I see the artifact whether the VP50 is set for 1080p60 or 1080p24 output. It does not just happen at scene transitions. It's most bright flashes, no matter where in the scene they are.

@JOSH:

what about the white blinking line issue ? never heard from DVDO something, can you confirm this issue do you need more information ?whats up ? :mad:

We are aware of this issue.

We plan on addressing this issue.

If anyone has anymore feedback as to conditions that they can easily reproduce this issue, please forward them to help@anchorbaytech.com.

We are aware of this issue.

We plan on addressing this issue.

If anyone has anymore feedback as to conditions that they can easily reporduce this issue, please forward those to help@anchorbaytech.com.

hi josh, thxns for the statement. :)

the issue is regardless what i do, everytime i have the white blinking line

PS3 1080p60 to 1080p60
PS3 1080P60 with prep to 1080p60
SDI 576i to 1080p60
HDMI 576p to 1080p60

i have never found a way to get rid of this thing

Hmm.. this is interesting - wonder why it's not affecting all units. I would expect that most users would not be powering down their units and that could account for the very few reports. But, I have tried it and had no problems.

The only commonality seems to be that only (mostly?) users in PAL country are affected, but hang on, I'm in PAL country (50Hz sources), so that's that one out of the window :confused:

Hi Phil,

The problem could be caused by a data corruption between volatile and non-volatile memory, so to test the unit you must remove all power for at least 10 minutes. This is needed because of the residual power remaining in the capacitors.

You could try again and let us know.

Thanks

Dean

Hi Phil,

The problem could be caused by a data corruption between volatile and non-volatile memory, so to test the unit you must remove all power for at least 10 minutes. This is needed because of the residual power remaining in the capacitors.

You could try again and let us know.

Thanks

Dean
Hi Dean,

Yes I did so for 8 hrs - please see my previous post (http://www.avsforum.com/avs-vb/showthread.php?p=10488077&&#post10488077) for details.

I upgraded to V1.04 on Friday. In the last 4 days, my video dropouts have increased significantly. About every 5 minutes, I have video dropout. The version that I was running before was 1.02 and did not have these problems. Anyone else experiencing this?

I upgraded to V1.04 on Friday. In the last 4 days, my video dropouts have increased significantly. About every 5 minutes, I have video dropout. The version that I was running before was 1.02 and did not have these problems. Anyone else experiencing this?
Yes, just once, although I'm a little behind you having upgraded only last Sunday. I did have occasional dropouts with Vs 1.00, but these were very sporadic only occuring about once or twice a week. My viewing comes mainly from SD broadcasts (576i) and Media Centre (720p).

BTW, did you follow up the FW installation with a hard reset (unplug, hold top 2 buttons down and replug whilst holding them down for a further few seconds)? Some people have claimed that it helped them when they struck a problem after an upgrade. I've never had to bother doing this, but it can't hurt.

So far I can report some positive things - sound dropouts gone and for some reason, better PQ on SD material. I also found that to get a correctly balanced picture, I did have to alter brightness, contrast and saturation a little from my previous Vs 1.00 settings (which of course were totally lost in the upgrade).

I can understand the potential need for unplugging the unit after f/w upgrade to allow dissipation of volatile memory - but - is it really necessary, or recommended, to do a full "hard" reset just bcz of f/w upgrade? Just curious, bcz I upgraded to 1.04 and unplugged (had to anyway since the computer and VP50 are not co-located), but did not do a "hard" reset. Seems to be working ok.

I can understand the potential need for unplugging the unit after f/w upgrade to allow dissipation of volatile memory - but - is it really necessary, or recommended, to do a full "hard" reset just bcz of f/w upgrade? Just curious, bcz I upgraded to 1.04 and unplugged (had to anyway since the computer and VP50 are not co-located), but did not do a "hard" reset. Seems to be working ok.

uh - in case anyone wants to confuse matters more, I have NEVER uplugged the VP50 after an upgrade - have gone to 1.01 and then to 1.04. I had to do a hard reset on the VP30 after addidng the ABT card, but that's a different matter.

Over the past two years, I've done my share (or more :)) of whining, but the one thing that has always gone smoothly (once I became familiar with TerraTerm) is the upgrade process. 'Course, having a loaded P4 with a genuine serial port probably doesn't hurt...

I didn't reset mine either. Should I?

I've used a Radio Shack, USB/R232 adapter with its driver and my POS lap top twice now. No problems at all.

Never unplugged mine either, is that something we're supposed to be doing?

Never unplugged mine either, is that something we're supposed to be doing?

Since it has always worked without, would have to guess that it isn't required. Mine always disply "reset" on the front panel afterwards, anyway. So I would only do it if the upgrade did not complete properly.

All discrete codes for the VP50 are now available in .ccf format here:http://www.anchorbaytech.com/support/documentation/automation.php

Also note that there is a macro for Panamorph Mode 1 and Mode 2 for those that are using Panamorphic, or anamorphic lenses.

Never unplugged mine either, is that something we're supposed to be doing?
Me neither...and I haven't had a problem.
If we were supposed to unplug, wouldn't DVDO direct us to? :confused:

Me neither...and I haven't had a problem either.
If we were supposed to unplug, wouldn't DVDO direct us to? :confused:

There is no reason to unplug the unit after doing a software update.

Yes, we would direct you.

Josh,

Any plans to improve Panorama mode? It has a lot of potential, but still needs tweaking.

BTW, PREP on 1.04 worked great for me, I was able to correct 2:2 deinterlacing artifacts from a DVD that was progressive only. Works as advertised :)

All discrete codes for the VP50 are now available in .ccf format here:http://www.anchorbaytech.com/support/documentation/automation.php

Also note that there is a macro for Panamorph Mode 1 and Mode 2 for those that are using Panamorphic, or anamorphic lenses.

Thanks Josh. This is what I was looking for.

____
Axel

Hi Josh

I see that the VP30 beta with passthrough support has been posted - I wonder if you could give us an idea when we might see the next beta of the VP50 with passthrough.

Also, I see that the 1.04 release is now "production" rather than beta. Is it any different than the beta release?

thx

pete S

@josh:
i saw at your website the following notes:
These are the known issues, which will be addressed in a forthcoming release:

* Discrete code for ‘Auto’ deinterlacing mode does not work.
* No Discrete code defined for ‘Forced 2:2’ deinterlacing mode.
* Discrete codes for Input Aspect Ratio presets 5-10 do not work.

isn't it possible to added more issues which are known like the white blinking line etc. ?

this will take some asking and asking out of this (and other) forums ?

Thanks, the Pronto/VP50 ccf fiile is much appreciated.

I just upgraded from 1.04 beta to the "final" 1.04 - and now 1080p/24 works flawlessly!!!
Even the internal judder test bar now moves smooth as silk :)

Cheers, folks!

Still hoping for the option to disable progressive cadence detection (to eliminate the latency for game consoles), if this hasn't been added to 1.04 final yet.

I just upgraded from 1.04 beta to the "final" 1.04 - and now 1080p/24 works flawlessly!!!
Even the internal judder test bar now moves smooth as silk :)

Cheers, folks!

That is quite curious..... v1.04 is the same regardless if you downloaded it while it was Beta or Production.

Still hoping for the option to disable progressive cadence detection (to eliminate the latency for game consoles), if this hasn't been added to 1.04 final yet.

New features, require new version numbers. This will be in the next Beta release of the VP50.

That is quite curious..... v1.04 is the same regardless if you downloaded it while it was Beta or Production.

Now that's funny!
Any idea what might have gone wrong the first time installing the "beta" then?

The only difference I remember:
I had a power failure while upgrading the first time, so I had to reboot the unit several times to be able to load the firmware again.
But then it worked...

Now it's a total new "24p" experience for me... :-)

That is quite curious..... v1.04 is the same regardless if you downloaded it while it was Beta or Production.

Well, at least you could have fixed the AUTO discrete ;) Thanks for all of your support for the VP50. SJ

New features, require new version numbers. This will be in the next Beta release of the VP50.
No problem, just good to know it's coming. :)

The only problem I've noticed in my usage of 1.04 is that sometimes it will still show an enlarged image on the screen(something like 1/4 of the image fills the screen) and I'll have to switch to another input and back for the picture to show properly. This has happened a few times, not as often as the previous beta, and mainly with the PS3. Although I think it happened at least once with my XA2. I'm outputting 1080i from my VP50(the PS3 and XA2 input 1080P into the VP50). Other than that, which is very minor, 1.04 has been rock solid in my usage.

Aaron, this is exactly what happens with my setup, too.
Except for this, it works like a charm.

New features, require new version numbers. This will be in the next Beta release of the VP50.

Excellent! After that I can happily route all PS3 Blu-ray and game content through VP50.

And when this "1080p24 combing problem" with Toshiba XE1 will be fixed either by Toshiba or ABT, then I can route all my signals through the unit.

That is quite curious..... v1.04 is the same regardless if you downloaded it while it was Beta or Production.

Does this mean that there is no reason to download and update to the new final 1.04 f/w, as it is exactly the same as the beta with no changes whatever? I would prefer not to do it unless there is some reason.

That is correct. They are identical files.

Now I am confused! If they are identical, how come Sandel finds the internal judder pattern to be "smooth as silk" at 1080p/24Hz with the prod version but not the beta one?

I have the beta one loaded and my judder pattern is anything but silky smooth. No tearing but definitely jerky.

That is correct. They are identical files.
Hmm..this is interesting - I'd like to be certain too. I appear to be getting more frequent Video blackouts (on SD 576i component - haven't noticed it on other inputs yet) with Vs 1.04 than I had with Vs 1.00 - longer in duration too, up to 3 seconds - sound not affected during blackout. If the Vs 1.04 production version is different from the Beta aone, I might give the production one a try. Does an "upgrade" from 1.04 to 1.04 retain your settings?

I hope so. When I went from 1.03 to 1.04 my settings were kept. I guess I'll go ahead and apply it at 9pm. Since I've caught up to realtime watching stargate tonight.

Now I am confused! If they are identical, how come Sandel finds the internal judder pattern to be "smooth as silk" at 1080p/24Hz with the prod version but not the beta one?

I have the beta one loaded and my judder pattern is anything but silky smooth. No tearing but definitely jerky.

Are you sure it's not your display? The judder bar is silky smooth for me as well, any format the display will accept (including 1080P/24+24Hz)

Are you sure it's not your display? The judder bar is silky smooth for me as well, any format the display will accept (including 1080P/24+24Hz)
My display is the JVC DLA-RS1. It seems to accept a 1080p/24Hz perfectly well and film based material seems smooth. The internally generated judder bar is another matter however.

Anyone else with the RS1 seeing a silky smooth judder bar at 1080p/24?

My display is the JVC DLA-RS1. It seems to accept a 1080p/24Hz perfectly well and film based material seems smooth. The internally generated judder bar is another matter however.

Anyone else with the RS1 seeing a silky smooth judder bar at 1080p/24?

I believe that nearly all of the RS1 owners, myself included, have not found the judder test to be smooth. As you point out, though, film based material is smooth.

Decided after the upgrade to firmware 1.04, to run a default settings to start again from scratch, as i re-sorted my connections to use HDMI where possible to the VP50 and now have the following set up....

SkyHD - HDMI 1 - Auto output
Oppo 970 - HDMI 2 - Auto output
PS3 - HDMI 3 - Auto output
Xbox360 - Component 1 - 1080i

From VP50 - HDMI - 50PHD8 1080i

I am trying to set the VP50 to switch output to 1080i@50 for Pal and 50hz source video/film and 60hz for NTSC and 60hz source video/film.

Now i have run into a problem i had a while back, which is when my selected source changes resolution output (SkyHD) or from 50 - 60hz or from 60 - 50hz (Oppo), i loose picture and can only get it back by turning the display off and back on.

I tried using auto profile, set to on and this only makes things worse and the VP50 starts selecting wrong profiles with mostly a blank picture.

I also found that if i have just setup and saved a profile (say profile 4) for a particular input, no matter what other input i select to stays on or selects the last saved profile (profile 4).

I have tried a default settings again with just the SkyHD connected set up the resolution again for SD output and saved that to profile 1 and set up for HD output and saved that to profile 2 but still goes blank.

I tried the same with the Oppo 970 saving 60hz - profile 1 and 50hz - profile 2 and again picture is lost when the oppo switches FR.

Cannot get this to work and keep the output on, seems to loose HDCP with the display but the indicator stays solid blue.

Am i doing this all wrong?

Please help:(

Do you have 10 profiles per input or is it 10 profiles for all inputs?

What settings do you configure if 2 sources will be inputting the same resolution and FR as to not get interference from the two?

Any help appreciated.

Decided after the upgrade to firmware 1.04, to run a default settings to start again from scratch, as i re-sorted my connections to use HDMI where possible to the VP50 and now have the following set up....

SkyHD - HDMI 1 - Auto output
Oppo 970 - HDMI 2 - Auto output
PS3 - HDMI 3 - Auto output
Xbox360 - Component 1 - 1080i

From VP50 - HDMI - 50PHD8 1080i

I am trying to set the VP50 to switch output to 1080i@50 for Pal and 50hz source video/film and 60hz for NTSC and 60hz source video/film.


So you only need 2 Display Profiles. One for 1080i-50 output and one for 1080i-60 output.

To create a Display Profile, first set up all of the parameters in the 'Output Setup' menu that you would like to save (format, framerate, sync, aspect ratio, ....). Then Save the Display Profile, making a (mental) note as to which one is 1080i-50 and which is 1080i-60. Now, you want to switch the 'Auto - Display Profile' feature on. Now switch to each source, and select the Display Profile that you would like, 1080i-50 or 1080i-60, based on the signal coming from the source. These are automatically saved on a per input per format (480i-60, 576-50, 720p-50, 720p-60, 1080i-50, 1080i-60, 1080p-24, 1080p-25, 1080p-50, 1080p-60, VGA-SXGA@60HZ on the HDMI inputs for example). For example with the Oppo play an NTSC DVD and select the Display Profile that is 1080i-60 and then play a PAL DVD and select the Display Profile that is 1080i-50. The VP50 will automatically recall the Display Profile that you have last selected based on the input and input format. So, if while watching a PAL DVD someone changes the Display Profile to 1080i-60, it will stay that way until it is fixed.

So you only need 2 Display Profiles. One for 1080i-50 output and one for 1080i-60 output.

To create a Display Profile, first set up all of the parameters in the 'Output Setup' menu that you would like to save (format, framerate, sync, aspect ratio, ....). Then Save the Display Profile, making a (mental) note as to which one is 1080i-50 and which is 1080i-60. Now, you want to switch the 'Auto - Display Profile' feature on. Now switch to each source, and select the Display Profile that you would like, 1080i-50 or 1080i-60, based on the signal coming from the source. These are automatically saved on a per input per format (480i-60, 576-50, 720p-50, 720p-60, 1080i-50, 1080i-60, 1080p-24, 1080p-25, 1080p-50, 1080p-60, VGA-SXGA@60HZ on the HDMI inputs for example). For example with the Oppo play an NTSC DVD and select the Display Profile that is 1080i-60 and then play a PAL DVD and select the Display Profile that is 1080i-50. The VP50 will automatically recall the Display Profile that you have last selected based on the input and input format. So, if while watching a PAL DVD someone changes the Display Profile to 1080i-60, it will stay that way until it is fixed.


Thanks for the fast reply Josh! :)

Understand it better now, thank you.

I will report back when i manage to try setting them up again as the missus is hogging the plasma, watching Eurovision at the moment :(

I have a problem with the VP50 in my CIH setup (XE1 + VP50 + HD1 + ISCO II)
Been desperately trying to fix it all day long, but it doesn't seem to work.

These are the aspect ratio settings I'm using with the VP50 (for the vertical stretch):

Input Frame AR: 16:9
Frame Active: 2.35:1
Output Display: 2.35:1
Screen: 2.35:1

I also tried the other possible solution:

Input Frame AR: 4:3
Frame Active: 1.78:1
Output Display: 16:9
Screen: 16:9

Both are giving me the same result. The image geometry is correct, but about 20% of the image get cropped off at the top and the bottom of the screen.

There is another way for CIH setups though with the VP50 that involves the 4:3 stretch mode (respectively the panaroma function), but that gives me an awful image. Image geometry is correct and nothing gets cropped off, but the sides of the picture are heavily distorted, so that it is simply unwatchable.

Now my question is: Is there a way to stretch the image vertically WITHOUT cropping off 20-25% of the image top and bottom and WITHOUT using the 4:3 stretch mode CIH which causes these weird distortions?

I bought the VP50 primarily for this one reason. Please don't tell me that it doesn't really have a proper vertical stretch function and that I have to live with the cropped off image :(

no the VP50 will not make you live with that, I use it on a 2.40:1 system, but I use a CRT projector so no stretch involved, someone else will respond soon with what you need to punch in ;)

-Gary

The image geometry is correct, but about 20% of the image get cropped off at the top and the bottom of the screen.If you have a 2.35:1 source and your projector is showing a 2.35:1 image, how can the geometry be "correct" and yet you're still losing a significant portion of the image? What do you mean when you say "The image geometry is correct"?

Both of the methods you list should give you the right result - i.e., the entire 2.35:1 source image fills your 2.35:1 screen. I would tend to use the first one as it more accurately represents your system configuration. Have you checked other VP50 settings which could provide additional image scaling, such as vertical zoom or overscan?

- Dale Adams

sounds to me simply like a 1.78:1 image is being viewed in 2.35:1 mode, thus perfect geometery but cut off top and bottom ;)

-Gary

If you have a 2.35:1 source and your projector is showing a 2.35:1 image, how can the geometry be "correct" and yet you're still losing a significant portion of the image? What do you mean when you say "The image geometry is correct"?

Both of the methods you list should give you the right result - i.e., the entire 2.35:1 source image fills your 2.35:1 screen. I would tend to use the first one as it more accurately represents your system configuration. Have you checked other VP50 settings which could provide additional image scaling, such as vertical zoom or overscan?
With "correct image geometry" I meant that the image is not vertically or horizontally distorted, and that the geometry is the same as it would be without the ISCO and the VP50.
Changing the other VP50 settings didn't help.

sounds to me simply like a 1.78:1 image is being viewed in 2.35:1 mode, thus perfect geometery but cut off top and bottom
I think that describes it quite good. It looked like a zoomed up 1.78:1 image.
I've fixed the issue by now, the XE1 was the problem. I was watching Hulk which is "Widescreen 2.35:1" due to the cover. When I was done checking and double-checking all of the VP50 settings, I tried changing the "TV shape" in the XE1 setup menu from 16:9 to 4:3 letterbox and that finally worked (though I don't really understand why). Correct image geometry and no cropped off image parts anymore. The only strange thing is that the HDDVD menu text is a bit blurred in the 4:3 letterbox mode. That doesn't seem to affect image sharpness though, so it's not a problem.

Thanks for your help guys :)

The Hulk is not a 2.35:1 movie - at least not the HD DVD version I have. It is 1.78 or 1.85, can't remember which.

The european version is, at least the case says it is.
I had the same problem with Riddick, which is 2.40:1 according to the case.

Hulk is 1.85:1 and is incorrectly labled, Riddick is 2.35:1 and is labled correctly

-Gary

These are the aspect ratio settings I'm using with the VP50 (for the vertical stretch):

Input Frame AR: 16:9
Frame Active: 2.35:1
Output Display: 2.35:1
Screen: 2.35:1


This is the recommended way to set up a 16:9 projector that has an anamorphic lens and a screen that is 2.35:1 for content that is 2.35:1. For example, with The Hulk, which is not a 2.35:1 movie (http://www.imdb.com/title/tt0286716/), you will lose information at the top and bottom of the screen with these settings. This will also happen with the menu of a 2.35:1 move, which is 1.78:1. The correct setting for The Hulk would be everthing above, but the Active AR would be set to 1.85:1. Optimally there is a way to move the anamorphic lens out of the way in these conditions, either manually or motorized, so that you can also use all of the resolution and brightness of the projector. In this case, you would need to change the Display and Screen AR back to 16:9.

Hulk really is 1.85:1. I wasn't even considering that since I was convinced it is 2.35:1, and stubbornly tried to make it work with my setup. So it was all my bad.Kind of embarassing lol :o
Thanks again for your help!

So you only need 2 Display Profiles. One for 1080i-50 output and one for 1080i-60 output.

To create a Display Profile, first set up all of the parameters in the 'Output Setup' menu that you would like to save (format, framerate, sync, aspect ratio, ....). Then Save the Display Profile, making a (mental) note as to which one is 1080i-50 and which is 1080i-60. Now, you want to switch the 'Auto - Display Profile' feature on. Now switch to each source, and select the Display Profile that you would like, 1080i-50 or 1080i-60, based on the signal coming from the source. These are automatically saved on a per input per format (480i-60, 576-50, 720p-50, 720p-60, 1080i-50, 1080i-60, 1080p-24, 1080p-25, 1080p-50, 1080p-60, VGA-SXGA@60HZ on the HDMI inputs for example). For example with the Oppo play an NTSC DVD and select the Display Profile that is 1080i-60 and then play a PAL DVD and select the Display Profile that is 1080i-50. The VP50 will automatically recall the Display Profile that you have last selected based on the input and input format. So, if while watching a PAL DVD someone changes the Display Profile to 1080i-60, it will stay that way until it is fixed.



Thanks for the fast reply Josh! :)

Understand it better now, thank you.

I will report back when i manage to try setting them up again as the missus is hogging the plasma, watching Eurovision at the moment :(


I have set the VP50 up with the correct profiles last night, for all my sources mentioned before and it's working with everything BUT SkyHD (HDMI). :confused:

I have set the SkyHD SD (576P)output - VP50 HDMI 1 input to profile 1 (1080i@50 - 50 locked) and again for the HD (1080i) output - VP50 HDMI 1 also to Profile 1 but get the blank screen again when changing from SD to HD or vice versa.

Using the front display on the VP50 it shows the correct profile has been selected and the status light stays solid blue but no output from the VP50 to the Display( No VP50 Menus can be displayed, PHD8 display shows no signal).

Switching the display off and back on recovers the picture back.

If i navigate the Sky menu very slowly to change from a SD channel to a HD channel it sometimes works correctly and the image is displayed but this happens rarely with 2 or 3 attempts before it works only once. :confused:

Any help with whats wrong Josh?

I have set the VP50 up with the correct profiles last night, for all my sources mentioned before and it's working with everything BUT SkyHD (HDMI). :confused:

I have set the SkyHD SD (576P)output - VP50 HDMI 1 input to profile 1 (1080i@50 - 50 locked) and again for the HD (1080i) output - VP50 HDMI 1 also to Profile 1 but get the blank screen again when changing from SD to HD or vice versa.

Using the front display on the VP50 it shows the correct profile has been selected and the status light stays solid blue but no output from the VP50 to the Display( No VP50 Menus can be displayed, PHD8 display shows no signal).

Switching the display off and back on recovers the picture back.

If i navigate the Sky menu very slowly to change from a SD channel to a HD channel it sometimes works correctly and the image is displayed but this happens rarely with 2 or 3 attempts before it works only once. :confused:

Any help with whats wrong Josh?


Managed to fix the problem, works perfectly fine now after performing a little surgery on the Panasonic HDMI board.

Help!

I just got a VP50 and trying to get it working with a Toshiba HD-A1 and PS3 but I'm running into issues and can't figure out the problem.

First w/ the Toshiba connected and its HDMI input selected the VP50 says there is an unkown signal detected. (Green LED) The ouptut on the Toshiba is set for 1080i and HDMI out is enabled. If I switch to component video it shows up. Also just a note, if I by-pass the VP50 and just go to my receiver I can see the output so I con't think its a Toshiba issue.

If I try to connect the PS3, I don't even get the HDMI output detected on the VP50. The status LED stays Red. :( Again if I just connect the PS3 to my receiver I have no issues.

I was worried that maybe I just had a bad VP50 (even though I just recevied it back from being repaired, the updating of the firmware failed due to a HW failure), but I was able to connect my HTPC via HDMI and it showed up with no problems.

Please if anyone can shed some light on what I might need to do.

Managed to fix the problem, works perfectly fine now after performing a little surgery on the Panasonic HDMI board.

I haven't followed your problem, but why are you using a HDMI board for the PHD8? It has a 1366x768 res and only the DVI board supports that. Something I have missed here? The VP should normally be much better in scaling and deinterlacing than the PHD8.

I haven't followed your problem, but why are you using a HDMI board for the PHD8? It has a 1366x768 res and only the DVI board supports that. Something I have missed here? The VP should normally be much better in scaling and deinterlacing than the PHD8.

I've only had the VP for a short time and initial impressions i've had so far is that i get the best picture sending the PHD8 higher resolutions rather than pixel mapped.

From what i've seen so far via RGBHV @ 1366x768 is a less detailed picture, RGBHV @ 1080i/p is more detailed and so have gone with 1080i HDMI for the benefit of a digital connection rather than analogue.

I tried mapped via DVI but ran into a few teething problems here with the DVI board.

I will be looking at it again when i have more time to play with the settings and connections but soon i will be pairing the VP50 with a 1080P display when i get one around sept, possibly one of the new Pioneer 508 displays.

As I've been getting used to my new VP50 over the last few days, one thing I've thought odd is its behavior with "Auto" deinterlacing while watching NBA playoff games on TNT. These are broadcast in 1080i, which I'm deinterlacing and scaling to 720p (unlocked, into a Sanyo PLV-Z4 projector) with the VP50. Explicitly switching to "Video Mode" deinterlacing looks okay, but "Auto" causes some odd motion blur. Most of the time "Auto" is fine, but I noticed that when a player makes a quick move, such as passing the ball or breaking past a defender, he briefly seems like he's in one of the "Matrix" movies - almost leaving a "ghost" or "trail" of his motion for a split-second.

Like I said, I've learned to just manually set the VP50 to "Video Mode" deinterlacing for these games, but I'm curious:

1. If anyone else has noticed this behavior;

2. Is there something particularly "confusing" about basketball in 1080i that makes it difficult to auto-detect as video, rather than film?

Thanks!

--John