re: X32 Discussion
I am very well aware of code bloat. It has annoyed me for many years. I am one of the older sound people here. And I have worked with electronics before there were Personal Computers. I had to load up a mainframe test computer off of punched paper tape once when someone turned off a breaker that they weren’t supposed to touch. This was testing components for a XXXXXXX, I could tell you about it but then I would have to …. Well you know how the rest of that goes. And yes I have also been trained to do that. I also used to troubleshoot Microprocessor based systems in hexadecimal. Ever heard of a Yuccalizer?
I use the generic term DSP to refer to the overall system. I didn’t think I needed to be any more specific then that.
They didn’t expand anything. To make it look like there are 100 more scenes it is just storing it on the computer you would have hooked up to it using Xcontrol. It might be a quicker way to get to another 100 scenes bit it is a clumsy way of doing it as far as I am concerned. I am stubborn and I don’t want to put the show at risk by having to have a working computer hooked up to the console just to get it to work. Striking it every night and getting it back again every day. I also don’t want to load up another set of scenes at any time during a show, even at intermission. I am asking a lot for a board in this price range and all anyone has to say is it can’t do it and we never planned on it doing all of that and then we are done here.
Look into their file structure and in particular look at all of the files it takes to store the scenes, one file per scene. But also look at the file that stores all of the console state data with an ascii editor. If you need me to tell you where it is I will do that in a PM, someone can really mess up the console badly if they were to play with that one. But it might give a clue as to what might be able to be done in the future with the X32.
I hope this clears up a few things.
DSP and memory are two separate items. But, they are related.
DSP (Digital Signal Processing) requires processing time.
Memory is finite, too. However, it can be allocated differently.
Maybe Behringer figured out a way to store more data, in the same amount of space.
As an aside, it used to be, programmers were very good at designing efficient software, because hardware was so limiting. (Both in memory and processing.) It’s still limiting, but not like it was 30+ years ago. Quite frankly, a lot of programmers today don’t have the same skills as those in retirement now, because those skills aren’t as critical. (That’s why we have so many Windows applications that leak memory. Quite frankly, it’s just poor programming.) I digress.
In any event, I believe we're only talking about Scenes within a Show. Worse case, there might be points in the production where maybe you could load another Show.
Eric H.
I am very well aware of code bloat. It has annoyed me for many years. I am one of the older sound people here. And I have worked with electronics before there were Personal Computers. I had to load up a mainframe test computer off of punched paper tape once when someone turned off a breaker that they weren’t supposed to touch. This was testing components for a XXXXXXX, I could tell you about it but then I would have to …. Well you know how the rest of that goes. And yes I have also been trained to do that. I also used to troubleshoot Microprocessor based systems in hexadecimal. Ever heard of a Yuccalizer?
I use the generic term DSP to refer to the overall system. I didn’t think I needed to be any more specific then that.
They didn’t expand anything. To make it look like there are 100 more scenes it is just storing it on the computer you would have hooked up to it using Xcontrol. It might be a quicker way to get to another 100 scenes bit it is a clumsy way of doing it as far as I am concerned. I am stubborn and I don’t want to put the show at risk by having to have a working computer hooked up to the console just to get it to work. Striking it every night and getting it back again every day. I also don’t want to load up another set of scenes at any time during a show, even at intermission. I am asking a lot for a board in this price range and all anyone has to say is it can’t do it and we never planned on it doing all of that and then we are done here.
Look into their file structure and in particular look at all of the files it takes to store the scenes, one file per scene. But also look at the file that stores all of the console state data with an ascii editor. If you need me to tell you where it is I will do that in a PM, someone can really mess up the console badly if they were to play with that one. But it might give a clue as to what might be able to be done in the future with the X32.
I hope this clears up a few things.