I owe BB an apology from the first post, I of all people should have realised the intent of this post, let's see if i can make up for it.
NOTE: if your display has less than say 500 channels then little of this is likely to apply if your PC runs windows well.
All my notes refer to Vixen 2.5
1000 pixels are not that expensive and that is instantly 3000 channels above what you had, multi thousand channel counts are about to be common.
All of the above is spot on. Think of the Vixen Grid as a giant spreadsheet with cells.
A Sequence 100 seconds long and 100 channels will have
100ms = 100,000 cells
50mS = 200,000 cells
25ms = 400,000 cells
Now make it 1000 channels
100ms = 1,000,000 cells
50mS = 2,000,000 cells
25ms = 4,000,000 cells
Now 5000 channels
100ms = 5,000,000 cells
50mS = 10,000,000 cells
25ms = 20,000,000 cells
Scary isn't it.
1. hope it does
2. Win64 will be required for large counts
3. Personally try and limit them but they must be considered.... install a low overhead AV is a good thing.
4. Absolutely, Vixen is good but not perfect at releasing memory.
I know people love to reuse and reuse, but maybe adopting a large pixel feature like a tree is also time to redo a lot of the show. just a thought.
1. near perfect way to test for ability to sequence, the only thing i would do is fill the entire sequence with a Random effect so all cells contain real data.
NOTE save a bunch of files at the desired channel count and then load them up in Manage Program, see note below.
2. Agreed back up your files.
Sounds somewhat right however there is a difference between being able to sequence and able to manage the program and load the program.
I've seen memory usage peak at 30% higher than expected as the sequences are loaded into memory both when manageing programs and loading shows.
For 2010 and 2011 i found that 16Gb of RAM worked well with 8k-10k channels and 25mS timings. A jump to 20k channels for 2012 will see me lift RAM to 32Gb.
Cheers
Phil




Reply With Quote
Bookmarks