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:)
As for the onboard DP8000... Correct me if I am wrong, but I do believe they are sharing the one and only processor on the desk. As far as I know, or assume, the onboard DP's don't have their own CPU like the external DP's do. But I really don't know, as I can't find any confirmation documented anywhere.
In regards to the Arkaos Vs Axon.. Take your Axon and try scratching the H264 Content. Anything not playing back forewords and your gonna peg your processor. Feed it 32bit apple pro res files and try running just 4 1080P layers. You will probably see skipping and dropped frames. Most media servers require a certain list of file types and encoding or media compression. This was done so the manufacturer can control the types of files that you are allowed to play back based on what they designed their system to do. This means that sometimes you have to re-render content to make it compatible. Arkaos is one of the exceptions, as it will take almost any file type and compression. Its up to you as the programmer to choose the best file type for the type of playback you intend on using.
I can run 12 layers, with piled on realtime rendering effects, on 6 outputs of 1080P foreword compressed with H264 no problem.. But as soon as I try to run one H264 layer on one output backwards or scratch the content then I choke the system and it pegs the processor at 100% load. Or if I take 3 simple files 30 seconds long encoded with Apple Pro Rez at 32bit color and try and run just 4 layers regardless of output count it chokes the system. It's not just layer count, output count, or what realtime rendering your doing, since that's all being processed at the GPU... it has mostly to do with how much decoding the CPU has to do and how you intend on playing it back. It's the decoding of a compressed file that will hammer the CPU. My Arkaos Boxes are dedicated for just media work, the Bios have been tweaked, the OS has been tweaked and the only processes running are the only processes needed for the dedicated media work. It's as good if not better than your Axon or the Arkaos dedicated stadium server. Don't kid yourself, most if not all the media servers are running a stripped down version of Win or Mac OS, WITH ONLY THE NECESSARY PROCESSES RUNNING. The media server manufacturers offer the servers up as turn key solutions for someone who doesn't want to do their own system configuration. Its still nothing more than a Windows or Mac box running software. But more importantly, it's a separate system, designed specifically for manipulating and outputting media in realtime. Personally, I would like to see the Hog play to its strong points and not get labeled as a "Jack of all trades and a winner of none".
It's a good forum here and no reason to agree, if you disagree, so I respect your opinions.. Sure, more gear means more points of failure... But I don't feel comfortable adding extra load and tasks to the most important piece of hardware in the system...which is the control desk. Especially when I can use a dedicated media server.
As for the onboard DP8000... Correct me if I am wrong, but I do believe they are sharing the one and only processor on the desk. As far as I know, or assume, the onboard DP's don't have their own CPU like the external DP's do. But I really don't know, as I can't find any confirmation documented anywhere.
In regards to the Arkaos Vs Axon.. Take your Axon and try scratching the H264 Content. Anything not playing back forewords and your gonna peg your processor. Feed it 32bit apple pro res files and try running just 4 1080P layers. You will probably see skipping and dropped frames. Most media servers require a certain list of file types and encoding or media compression. This was done so the manufacturer can control the types of files that you are allowed to play back based on what they designed their system to do. This means that sometimes you have to re-render content to make it compatible. Arkaos is one of the exceptions, as it will take almost any file type and compression. Its up to you as the programmer to choose the best file type for the type of playback you intend on using.
I can run 12 layers, with piled on realtime rendering effects, on 6 outputs of 1080P foreword compressed with H264 no problem.. But as soon as I try to run one H264 layer on one output backwards or scratch the content then I choke the system and it pegs the processor at 100% load. Or if I take 3 simple files 30 seconds long encoded with Apple Pro Rez at 32bit color and try and run just 4 layers regardless of output count it chokes the system. It's not just layer count, output count, or what realtime rendering your doing, since that's all being processed at the GPU... it has mostly to do with how much decoding the CPU has to do and how you intend on playing it back. It's the decoding of a compressed file that will hammer the CPU. My Arkaos Boxes are dedicated for just media work, the Bios have been tweaked, the OS has been tweaked and the only processes running are the only processes needed for the dedicated media work. It's as good if not better than your Axon or the Arkaos dedicated stadium server. Don't kid yourself, most if not all the media servers are running a stripped down version of Win or Mac OS, WITH ONLY THE NECESSARY PROCESSES RUNNING. The media server manufacturers offer the servers up as turn key solutions for someone who doesn't want to do their own system configuration. Its still nothing more than a Windows or Mac box running software. But more importantly, it's a separate system, designed specifically for manipulating and outputting media in realtime. Personally, I would like to see the Hog play to its strong points and not get labeled as a "Jack of all trades and a winner of none".
It's a good forum here and no reason to agree, if you disagree, so I respect your opinions.. Sure, more gear means more points of failure... But I don't feel comfortable adding extra load and tasks to the most important piece of hardware in the system...which is the control desk. Especially when I can use a dedicated media server.
