How severe are the iPC issues with 3.2.3?

Firewood1Firewood1 Registered User, Hog Beta
Hello,

For anyone who has been in the "For Sale" section of the forum you'll have noticed i'm looking for an iPC to purchase (or Hog 3 if the price is right).

I have used Hog 3's and iPCs a lot but have yet to use them since the last major release 3.2. I had no issues back then with the iPC, but have now read so many negative posts about DMX freezing when using encoder wheels etc.

My question is basically, is this an across the board fundamental problem with all iPCs, or something just a handful of people are experiencing? Is there a particular age of console that is being affected that I should avoid?

If it's a case of spend a bit more and end up with a problem free Hog 3 & DP8000, then I would much rather do that than end up with a cheaper iPC that frustrates the life out of me.

I have enough frustrations with jobs on MA's...I want a Hog for a trouble free life! :-)

All advice gratefully received. Apologies if this has been discussed already. I have looked deep into the forum but have not found specific details.

Thanks in advance....

Comments

  • XOP15XOP15 Registered User, Hog Beta
    edited February 2012
    I'm running 7 universe's on an IPC running v3.2.3 with a DP8000, no issues what so ever, system is solid and very stable. IPC is a 2005 model.
  • Firewood1Firewood1 Registered User, Hog Beta
    edited February 2012
    Thanks for your reply. That's very interesting and pleasing to hear. So are you networked to an external DP8000? I wonder if other people's issues are related to using the direct outputs on the back of the console, or perhaps with much larger rigs.
  • XOP15XOP15 Registered User, Hog Beta
    edited February 2012
    I have 7 crammed universe's from a networked DP8000, not using the desks internal DP8000, show is pretty cue heavy too and I've not noticed any performance issues's

    Ive not run a show off 3.2 using the internal DP/ Super widget but I have Running 3.1.9 with 4 internal universe's and 4 from a USB super widget with not issues.
  • cmuenchowcmuenchow Registered User, Administrator, HES Staff
    edited February 2012
    Colin,

    Thanks for your post. The fact of the matter is the current issue on 3.2.X with the iPC is that our re-arc of wheel messages in 3.2.0 did put some extra stress on CPU processing whereby the desktop process can take CPU time away from the internal DP8000 on the iPC when turning encoder wheels moderately fast or with a lot of fixtures. We are still actively working on patching this issue but as you will read on the forums an external DP8000 will not suffer this problem because it does not share CPU resources with the iPC's desktop. Most iPC users effected by this have reverted to 3.1.9 and are running there until we can patch this on 3.2.X.
  • Hugovd89Hugovd89 Registered User
    edited February 2012
    c_muenchow wrote: »
    Colin,

    Thanks for your post. The fact of the matter is the current issue on 3.2.X with the iPC is that our re-arc of wheel messages in 3.2.0 did put some extra stress on CPU processing whereby the desktop process can take CPU time away from the internal DP8000 on the iPC when turning encoder wheels moderately fast or with a lot of fixtures. We are still actively working on patching this issue but as you will read on the forums an external DP8000 will not suffer this problem because it does not share CPU resources with the iPC's desktop. Most iPC users effected by this have reverted to 3.1.9 and are running there until we can patch this on 3.2.X.

    I,ve also had these problems with a dmx4 widget and HogPC on a recent Intel I5 notebook with Windows XP, While on another but same model notebook with Windows 7 I had no issues.
  • Firewood1Firewood1 Registered User, Hog Beta
    edited February 2012
    Hi Chris,

    The fact that this seems to be a case of the CPU becoming overloaded at times, would this mean that the console should be fine if working well within the limitations of its onboard DP8000? For example, if I were just using the 4 direct outputs, without utilising an additional Super Widget, would this hopefully make running v3.2.3 possible?

    I guess what i'm asking is what is your idea of lots of movers? Does this issue occur mostly when the desk is running 8 crammed universes internally?

    The desk I have found and am likely to purchase has had the motherboard, CPU, RAM and HDD changed to that of the Full Boar, so should this also help to improve matters?

    Thanks very much for your input. Hopefully you have also seen my other recent posts with regards to effects!

    Cheers

    Colin
  • James DikeJames Dike Registered User
    edited February 2012
    We are running our iPC without upgraded hardware. Now that our minor static issue is solved, the on,y issue I see with 3.2.3 is when programming there is a lag between the encoders and DMX activation. It does not occur when running shows. Our rig consists off 600 dimmers and 40 Vl's running off all 4 universes of internal widget. Most shows are busked running 20 live cue lists and the programmer live as well.
    I am probably pushing the old hardware, but all these issues, are mostly irritants then critical errors (like typing faster then e desk can keep up with).

    My 2 cents

    James
Sign In or Register to comment.