is there in the next update a pixel mapping or what are the plans? it will be useful even if you have only 20 sunstrips or led fixtures the video you do with a media server but for those little things very handy:)
[QUOTE=Buzz313th;73200]As per the specs on the HES website, the H4 is on an Intel I5, the FB on an Intel I3, both I believe are Dual Core, not quads.
Where do you see this info? I could not find it. As far as I know the H4, FB4, & RH4 all use the same AMD processor. Slightly different motherboards between the models, but the same processor on all of them, but maybe I am thinking of the onboard DP-8000 processor on all of them.
[QUOTE=Buzz313th;73200]I have two Arkaos MMP servers that are running overclocked dedicated I7 quads with matched Boards, 16gigs of fast ram and a top of the line AMD firepro card and I have no problem choking those machines if I try, especially when I'm sending to a pixelmap instead of just a video surface . Sure, the H4 will never be a replacement for a Media Server, but I don't think you realize the amount of processing at the CPU, that's required to simply decode a compressed video file and then convert it to DMX data for a mapped surface. Sure, the H4 could do it, but either way you look at it, your gonna be taking from peter to pay paul and the control response from the desk is gonna suffer. It may be unnoticeable, or completely noticeable. In the end, unless your running a very low resolution Pixelmapped Effect, your gonna end up using a media server anyway.
Arkaos isn't really any kind of an accurate benchmark for anything Hog related.....apples to oranges....if you want to go that way I have run Ivy Bridge i7 AXON servers with 9 layers of full HD (1920x1080p) and all 32 FX running crossfades as well as visual FX running crossfades, etc.....the CPU never got above 30% or so...GFX and HDD were all performing well this way too....in short the severs were not even breathing hard....a Windows or Mac computer is burdened with all kinds of things a dedicated OS system like Hog or AXON doesn't have to worry about. Will it take system resources to run video files? Of course it will, but with the current hardware being what it is I highly doubt we would see any noticeable lag in performance.
I do agree that any type of truly "heavy duty" pixel mapping should be done via media server or dedicated product interface/processor.
[QUOTE=Buzz313th;73200]Doing an LTP, HTP or switchable Artnet or DMX merger at a node, IMHO, is actually as easy and intuitive as it would be if you were running the media and a fixture patch out of the console.
I disagree with you there too. More pieces of gear in the system mean more potential points of failure. It would be far more elegant and streamlined to have all of this contained within the desk via software.
[QUOTE=Buzz313th;73200]Pixelmapping from the desk is indeed a cool feature, but if it gets in the way of the control desk doing it's primary job, then it's more of a hindrance.
Agreed, but as I stated above I highly doubt this will be an issue given the current hardware spec on the desks.
[QUOTE=Buzz313th;73200]As per the specs on the HES website, the H4 is on an Intel I5, the FB on an Intel I3, both I believe are Dual Core, not quads.
Where do you see this info? I could not find it. As far as I know the H4, FB4, & RH4 all use the same AMD processor. Slightly different motherboards between the models, but the same processor on all of them, but maybe I am thinking of the onboard DP-8000 processor on all of them.
[QUOTE=Buzz313th;73200]I have two Arkaos MMP servers that are running overclocked dedicated I7 quads with matched Boards, 16gigs of fast ram and a top of the line AMD firepro card and I have no problem choking those machines if I try, especially when I'm sending to a pixelmap instead of just a video surface . Sure, the H4 will never be a replacement for a Media Server, but I don't think you realize the amount of processing at the CPU, that's required to simply decode a compressed video file and then convert it to DMX data for a mapped surface. Sure, the H4 could do it, but either way you look at it, your gonna be taking from peter to pay paul and the control response from the desk is gonna suffer. It may be unnoticeable, or completely noticeable. In the end, unless your running a very low resolution Pixelmapped Effect, your gonna end up using a media server anyway.
Arkaos isn't really any kind of an accurate benchmark for anything Hog related.....apples to oranges....if you want to go that way I have run Ivy Bridge i7 AXON servers with 9 layers of full HD (1920x1080p) and all 32 FX running crossfades as well as visual FX running crossfades, etc.....the CPU never got above 30% or so...GFX and HDD were all performing well this way too....in short the severs were not even breathing hard....a Windows or Mac computer is burdened with all kinds of things a dedicated OS system like Hog or AXON doesn't have to worry about. Will it take system resources to run video files? Of course it will, but with the current hardware being what it is I highly doubt we would see any noticeable lag in performance.
I do agree that any type of truly "heavy duty" pixel mapping should be done via media server or dedicated product interface/processor.
[QUOTE=Buzz313th;73200]Doing an LTP, HTP or switchable Artnet or DMX merger at a node, IMHO, is actually as easy and intuitive as it would be if you were running the media and a fixture patch out of the console.
I disagree with you there too. More pieces of gear in the system mean more potential points of failure. It would be far more elegant and streamlined to have all of this contained within the desk via software.
[QUOTE=Buzz313th;73200]Pixelmapping from the desk is indeed a cool feature, but if it gets in the way of the control desk doing it's primary job, then it's more of a hindrance.
Agreed, but as I stated above I highly doubt this will be an issue given the current hardware spec on the desks.
