DiyLightAnimation
Hardware => Lynx EtherDongle => Lynx Conductor => Topic started by: RJ on September 16, 2012,
-
The Conductor Beta has finished.
A conductor coop will be starting in the next couple of days so keep your eye out if you want to get a Conductor.
The Beta Testers all agree it is ready for release. I had a hard time getting the beta going good but I have had some great beta testers on it the least few months and I fell strongly you will like what we have put together for you.
This beta covered the Conductor and included the Android app which I will be posting to the Android market to download in the next week or so.
The Slave will be entering beta next and once it is done we will be ready to release it also.
If you are not familiar with the Conductor it is a standalone player for your shows to allow you to not need a computer to operate them. It gives you 16,384 channels of pixelnet and the audio from you mp3's. It has its own built in clock, calendar and it handles your scheduling for you. It can be used wirelessly with the use of cheap wifi devices and can be then controlled from you android devices also.
It also sends out sync packets which will allow you to add slaves to gain more channels or to seperate then show across yards ect.
If you need more info check out the intro training on it at:
https://vimeo.com/48223100
RJ
-
Congratulations, RJ!!! This is a great achievement that all will celebrate.
Thanks to the beta testers as well for stepping up to the challenge.
-
Woohoo!
-
Whoohooo
Sent from my Thunderbolt using Tapatalk 2.
-
Congratulations, RJ!!! This is a great achievement that all will celebrate.
Thanks to the beta testers as well for stepping up to the challenge.
+1
-
+1
Sent from my iPad using Tapatalk HD
-
You said it will do pixelnet, but what about dmx?
-
Congratulations, RJ!!! This is a great achievement that all will celebrate.
Thanks to the beta testers as well for stepping up to the challenge.
Like Steve post Congratulations!
-
This is just amazing, RJ.
-
You said it will do pixelnet, but what about dmx?
That is my question too.
-
You said it will do pixelnet, but what about dmx?
That is my question too.
I figure it will since the etherdongle can handle 2048 channels of dmx, I just wanna be sure.
-
Woo hoo.
I can't wait for the coop...
As for DMX, you can always use an active hub for one universe...
-
sweet thanks to all
-
RJ,
GREAT news! THANKS to you and all your testers.
Richard (from SoCal) :)
-
+1 <res.
-
You said it will do pixelnet, but what about dmx?
That is my question too.
I figure it will since the etherdongle can handle 2048 channels of dmx, I just wanna be sure.
The first post in this thread (http://diylightanimation.com/index.php?topic=5767.0) said it would handle 4 DMX universes with different firmware, not sure if that still applies, but if so, the active hub would not be needed.
-
The current firmware is PixelNet only. The DMX firmware has not been created. I wanted to get a final firmware for the conductor and slave before modifing it to be DMX.
The Slave firmware will be next, then the DMX firmware for both. All runs on the same hardware.
RJ
-
Thanks to everyone on this great accomplishment !!
-
Thanks RJ!! I know we all, including myself appreciate the dedication and hard work you and the other members put into designing and testing these things for us to play with!! <res.
-
The current firmware is PixelNet only. The DMX firmware has not been created. I wanted to get a final firmware for the conductor and slave before modifing it to be DMX.
The Slave firmware will be next, then the DMX firmware for both. All runs on the same hardware.
RJ
Slave and Conductor hardware are one-and-the-same?
Does that mean that the slave has (but does not use) the mp3 player?
That is good info to know before we sign up for the conductor (aka slave) coop.
-
IIRC, the slave is a scaled down conductor. I don't think that it has the MP3 player.
-
Rj states it is the same hardware. Are you saying the slave does not use the MP3 player or does not have the MP3 portion of the circuit?
The main question is...
Should we buy an extra conductor in conductor coop if we plan to use it as a slave so we are ready when the slave firmware is released or is the slave hardware different?
The Slave firmware will be next, then the DMX firmware for both. All runs on the same hardware.
RJ
-
It is not the same for the Conductor and Slave.
It is the same for pixelnet / DMX which is what is being discussed in the post.
RJ
-
can i get on list to beta test slave
-
Thanks for the clarification.
-
can i get on list to beta test slave
The beta testers are already in place.
But thanks for offereing!
RJ
-
Just a couple of questions, 1) What is the connection point on the ED? 2) Will it fit inside the case of the ED? Sorry if this info was available previously and I couldn't find it. Can we see pic's of the unit?
-
The large header on the right side of the board (opposite of the rj-45 connector)
Yes inside the case
Rick R.
-
Congradulations RJ!!!! .......................... <wd..
Thanks to all the beta testers!!
Leon
-
The current firmware is PixelNet only. The DMX firmware has not been created. I wanted to get a final firmware for the conductor and slave before modifing it to be DMX.
The Slave firmware will be next, then the DMX firmware for both. All runs on the same hardware.
RJ
Thanks for clearing that up for me so i don't blindly join the coop without unknowingly not being able to use it.
Depending on the price I may go ahead and get on the coop with the hopes of the DMX firmware being released before this season.
Thanks for all the hard work to you and all of our beta testers for putting up with all our ranting about it being released
Todd
-
The current firmware is PixelNet only. The DMX firmware has not been created. I wanted to get a final firmware for the conductor and slave before modifing it to be DMX.
The Slave firmware will be next, then the DMX firmware for both. All runs on the same hardware.
RJ
Thanks for clearing that up for me so i don't blindly join the coop without unknowingly not being able to use it.
Depending on the price I may go ahead and get on the coop with the hopes of the DMX firmware being released before this season.
Thanks for all the hard work to you and all of our beta testers for putting up with all our ranting about it being released
Todd
+1
-
Do you have any documentation on how to communicate to it? I can possibly write an iPhone app for this.
-
The current firmware is PixelNet only. The DMX firmware has not been created. I wanted to get a final firmware for the conductor and slave before modifing it to be DMX.
The Slave firmware will be next, then the DMX firmware for both. All runs on the same hardware.
RJ
Thanks for clearing that up for me so i don't blindly join the coop without unknowingly not being able to use it.
Depending on the price I may go ahead and get on the coop with the hopes of the DMX firmware being released before this season.
Thanks for all the hard work to you and all of our beta testers for putting up with all our ranting about it being released
Todd
Just to be clear - if you have an Active Hub (http://www.diylightanimation.com/wiki/index.php?title=ActiveHub16Use), you can get a DMX universe out of a pixelnet stream. I hope I understand this correctly...?
-
Just to be clear - if you have an Active Hub (http://www.diylightanimation.com/wiki/index.php?title=ActiveHub16Use), you can get a DMX universe out of a pixelnet stream. I hope I understand this correctly...?
Yes
-
The large header on the right side of the board (opposite of the rj-45 connector)
Yes inside the case
Thank you for the info Rick, I was hoping that was going to be the case(no pun intended).
-
Thanks RJ for all your hard work. And thanks to the beta testers too.
This is exciting news because last year we ran 5 yards with DMX connected wirelessly. We had hoped to do 5 yards this year with pixelnet added but, pixelnet is not (yet) wireless. Even if there was a slave I would have a problem because I need wireless communication between the yards. So, could I run 5 conductors, one for each yard, and start them all at the same time using a single DMX channel from a wireless Lynx Express for each conductor? All the yards have some DMX requirements so the LEs are already in place.
I am thinking that 6 conductors would be required since one conductor would be needed to generate the DMX start signal to the 5 other conductors and not do much else.
Any thought or opinions would be appreciated.
Thanks,
Rick S
-
Just to clarify, if someone already has say (4) Smart String Hubs ... and say each one is assigned a different pixelnet universe (4096 channels) ... and this conductor (an ED daughter board) outputs to the attached etherdongle (ED) ... and the Etherdongle then say connects to each of the 4 SS Hubs (pixelnet) ... you really already have the potential for (4) DMX universes on the SS Hub DMX OUT ports (1 DMX universe per SS Hub used) ... so you would just be converting them from pixelnet back into DMX at the SS Hub.
To me, making the conductor have DMX firmware seems like its got its place, but its a much more limited use because then your limited to DMX only and maybe just running a more conventional show with less RGB and no pixelnet, smart strings, right?
It seems that the way its going to work now, you get the maximum capability and the most flexibility, but you need to be able to get your sequences into the required sequence format for the conductor and onto a memory card first. And last I heard, that format was .xseq that xlights can converts into, correct?
-
Just to clarify, if someone already has say (4) Smart String Hubs ... and say each one is assigned a different pixelnet universe (4096 channels) ... and this conductor (an ED daughter board) outputs to the attached etherdongle (ED) ... and the Etherdongle then say connects to each of the 4 SS Hubs (pixelnet) ... you really already have the potential for (4) DMX universes on the SS Hub DMX OUT ports (1 DMX universe per SS Hub used) ... so you would just be converting them from pixelnet back into DMX at the SS Hub.
Yes, you are correct with an active SS Hub.
To me, making the conductor have DMX firmware seems like its got its place, but its a much more limited use because then your limited to DMX only and maybe just running a more conventional show with less RGB and no pixelnet, smart strings, right?
Yes, the DMX firmware to come later would be for a show without PixelNet.
It seems that the way its going to work now, you get the maximum capability and the most flexibility, but you need to be able to get your sequences into the required sequence format for the conductor and onto a memory card first. And last I heard, that format was .xseq that xlights can converts into, correct?
Yes, you get the most flexibility with PixelNet. You use Xlights to convert to the Conductor format which is filename.SEQ, i.e. the file type is .SEQ.
Denny
-
Or if you are using LSP you can export into .SEQ. With LSP you choose what controllers you want exported and where to begin and end the song with a slider. I wish there was an "All" checkbox on the controller choices and the slider seems like an extra step because I can't think of why anyone would only export a piece of the sequence.
-
Thanks RJ for all your hard work. And thanks to the beta testers too.
This is exciting news because last year we ran 5 yards with DMX connected wirelessly. We had hoped to do 5 yards this year with pixelnet added but, pixelnet is not (yet) wireless. Even if there was a slave I would have a problem because I need wireless communication between the yards. So, could I run 5 conductors, one for each yard, and start them all at the same time using a single DMX channel from a wireless Lynx Express for each conductor? All the yards have some DMX requirements so the LEs are already in place.
I am thinking that 6 conductors would be required since one conductor would be needed to generate the DMX start signal to the 5 other conductors and not do much else.
Any thought or opinions would be appreciated.
Thanks,
Rick S
You run the Conductor and Slaves wirelessly so that is not a problem. this is in fact the purpose for sending syncing packets and not the show data. It takes very little bandwidth and does not require a perfect wireless network to work well. It has built in fault tolerence if a sync packet or two or three are missed.
RJ
-
Thanks RJ for all your hard work. And thanks to the beta testers too.
This is exciting news because last year we ran 5 yards with DMX connected wirelessly. We had hoped to do 5 yards this year with pixelnet added but, pixelnet is not (yet) wireless. Even if there was a slave I would have a problem because I need wireless communication between the yards. So, could I run 5 conductors, one for each yard, and start them all at the same time using a single DMX channel from a wireless Lynx Express for each conductor? All the yards have some DMX requirements so the LEs are already in place.
I am thinking that 6 conductors would be required since one conductor would be needed to generate the DMX start signal to the 5 other conductors and not do much else.
Any thought or opinions would be appreciated.
Thanks,
Rick S
You run the Conductor and Slaves wirelessly so that is not a problem. this is in fact the purpose for sending syncing packets and not the show data. It takes very little bandwidth and does not require a perfect wireless network to work well. It has built in fault tolerence if a sync packet or two or three are missed.
RJ
So I could use the V1 or V2 TX/RX stuff for communications? IE, Conductor to first hub, then hub to wireless TX then wireless RX into each Slave?
Thanks,
Rick S
-
EtD requires ethernet, so you will need wireless compatable with ethernet......
-
Congratulations RJ. I know you've been working on this for awhile,and now to get it to this point of release must be a great relief and resolution. I, as do many, if not all appreciate the hard work from you and the beta testers.
Thank you for all that you do,
animal <res.
-
So I could use the V1 or V2 TX/RX stuff for communications? IE, Conductor to first hub, then hub to wireless TX then wireless RX into each Slave?
Thanks,
Rick S
No the Wireless DMX will not work with this. You plug little $35 -$50 Ethernet Wireless units into them and they use Wifi to communicate to each other. It also allows you to control the conductor from you android phone if you want.
RJ
-
No the Wireless DMX will not work with this. You plug little $35 -$50 Ethernet Wireless units into them and they use Wifi to communicate to each other. It also allows you to control the conductor from you android phone if you want.
RJ
Are the Ethernet Wireless units something you designed and there will be a coop for, or something generic that we get from a store?
-
Greetings,,,
http://diylightanimation.com/index.php?topic=8455.msg120628#msg120628
Keith
-
Ok From a non tech person.
Will the conductor run DMX and pixelnet out of it at the same time?
Of coarse when all the firmware is available.
Thanks for all the hard work RJ and all others that helped out.
You people amase me. No mediocre here.
-
Greetings,,,
An active hub can run DMX out at the same time as pixelnet, just as before.
Keith
-
Sorry none tech person here.
So out of the a conductor into a active hub
that can spit the signal into DMX and pixelnet.
From a conductor with out a active hub I will not be able to run both DMX and pixelnet signals?
Do I have that right?
-
Greetings,,,
The Conductor does not change the ability of the hubs, just where the sequence and music source is coming from. Active hubs have extra DMX capability that can be used in parallel with Pixelnet.
Keith
-
Sorry just not getting this.
If my show is in the conductor were every thing starts
can I run both DMX and pixelnet from the conductor
or do I need a active hub to get both DMX and pixelnet
signals.
In other words can the conductor hold both DMX and pixelnet programing?
Thanks
-
As I understand it, you need an active hub to get both as the pic on the active hub is what pulls the assigned channels out of the data stream that the Etd (with pixelnet firmware) is outputting.
-
the conductor doesn't change the outputs of the EtherDongle, it mearly replaces the computer, and sits on the etherdongle.
the etherdongle sends out pixelnet (with the pix firmware), or dmx, (with the dmx firmware),
if you're running pixelnet, then you need a active hub to get dmx (just like always)
the conductor just holds your show on a memory card, and sends the signals to the etherdongle. the etherdongle does all the communications to the rest of your show, just like always.
-
The conductor only supports pixelnet right now so if you need dmx you need to get it out of an active hub
-
I'm still not getting the question answered?
Let me put it another way.
The conductor replacing the computer.
Can the conductor hold both DMX and pixelnet firmware at the same time?
This would mean when the information comes out
of the conductor it has to be changed to ether DMX and pixelnet.
The question is how do you change the signal of the conductor to DMX and pixelnet signals at the same time. Using both at the same time.
Do you have to run two dongles ONE for each firmware DMX and pixelnet?
Thanks
-
I'm still not getting the question answered?
Let me put it another way.
The conductor replacing the computer.
Can the conductor hold both DMX and pixelnet firmware at the same time?
This would mean when the information comes out
of the conductor it has to be changed to ether DMX and pixelnet.
The question is how do you change the signal of the conductor to DMX and pixelnet signals at the same time. Using both at the same time.
Do you have to run two dongles ONE for each firmware DMX and pixelnet?
Thanks
Nope,
The Conductor stores your show (sequences, music) along with a clock for timing and scheduler. The output is still handled by the Etherdongle which outputs pixelnet (currently only pixelnet with DMX option later).
To put it another way. The EtherDongle is your horse and the Conductor is the saddle. The saddle does not change the way the horse moves. So the Conductor does not change the way the EtherDongle outputs. So to get DMX you will need the active hub
Line diagram
Conductor/Etherdongle --- Cat5 ---- Active Hub -----(outputs to SSC or DMX devices like LE)
Does that help?
Rick R.
-
Rick you used the word or.
So the conductor will not run a show with DMX and pixelnet at the same time?
So you will need two conductors to run the same show with DMX and pixelnet?
Is this right?
Thanks
Mort
-
RJ you used the word or.
So the conductor will not run a show with DMX and pixelnet at the same time?
So you will need two conductors to run the same show with DMX and pixelnet?
Is this right?
Thanks
Mort
The conductor has (will have) 2 firmware versions. DMX or Pixelnet.
The DMX firmware will produce 4 DMX universes or 2048 total DMX channels.
The Pixelnet firmware will produce 4 Pixelnet universes of 16384 total pixelnet channels.
If you are using pixelnet, AND you use smart string 16-port active hub, you have the ability to convert 512 of the channels on each hub to DMX. This ability to convert to DMX is a function of smart string ACTIvE hubs -- not of the dongle, nor the conductor.
-
Thanks Rick
Sorry about being a pain. Now every thing makes sense.
Ok sounds good. Very workable.
Thanks for all the great work guy.
Mort
-
Heh, now I think I am confused. <fp. Can you verify if I have this right:
The EtherDongle has two different firmware that can be loaded. One is for Pixelnet and the other is for DMX.
If you connect an EtherDongle programmed for Pixelnet to a 16 port active hub, the active hub can output the first 512 channels as DMX.
If you connect an EtherDongle programmed for DMX to a Combiner (used in reverse), the Combiner can output 4 DMX universes.
The Conductor takes the place of your computer running the sequencing program. Instead of your computer sending the control signals to the EtherDongle, the Conductor does that.
The Conductor has (will have) two different firmware that can be loaded. One for Pixelnet and one for DMX.
If your EtherDongle is loaded with the Pixelnet firmware, the Conductor needs to be loaded with the Pixelnet firmware.
If your EtherDongle is loaded with the DMX firmware, the Conductor needs to be loaded with the DMX firmware.
Is that the gist?
-
Heh, now I think I am confused. <fp. Can you verify if I have this right:
The EtherDongle has two different firmware that can be loaded. One is for Pixelnet and the other is for DMX.
If you connect an EtherDongle programmed for Pixelnet to a 16 port active hub, the active hub can output the first 512 channels as DMX.
If you connect an EtherDongle programmed for DMX to a Combiner (used in reverse), the Combiner can output 4 DMX universes.
The Conductor takes the place of your computer running the sequencing program. Instead of your computer sending the control signals to the EtherDongle, the Conductor does that.
The Conductor has (will have) two different firmware that can be loaded. One for Pixelnet and one for DMX.
If your EtherDongle is loaded with the Pixelnet firmware, the Conductor needs to be loaded with the Pixelnet firmware.
If your EtherDongle is loaded with the DMX firmware, the Conductor needs to be loaded with the DMX firmware.
Is that the gist?
Close but there is a problem.
The conductor does NOT have a pic on it so there is no firmware for it. The conductor is a add-on board to the EtherDongle. The EtherDongle gets a new firmware that supports the Conductor board and outputs pixelnet. Later RJ will release a DMX version for the Conductor/EtherDongle setup.
clear as mud?
Rick R.
-
Ah, so eventually the EtherDongle will have four different firmware versions:
Pixelnet output
DMX output
Pixelnet output with Conductor support
DMX output with Conductor support
Thanks, I think I got it now.
-
Ah, so eventually the EtherDongle will have four different firmware versions:
Pixelnet output
DMX output
Pixelnet output with Conductor support
DMX output with Conductor support
Thanks, I think I got it now.
isn't there just 4 firmwares for the pixelnet out?
the original makes the etherdongle respond to channels 1-16384
one for 16385-32768
one for 32769-49152
one for 49153-65536
-
I am more confused than ever now after reading this post. I have not yet built my Ether Dongle and was going to get it done this weekend and have ordered the conductor and trigger. I have seen a DMX code download for the ED, is this for straight DMX, 4 universes? And will it work with the conductor? I was looking to the conductor to save me buying another PC to use to run our show this year, I really don't want to tie down one of our two laptops in the house to the show. I will still use the conductor next year as I plan on starting into SS for pixelnet, but I am very confused at this point as to what stage the conductor and ether dongle are at.
-
I am more confused than ever now after reading this post. I have not yet built my Ether Dongle and was going to get it done this weekend and have ordered the conductor and trigger. I have seen a DMX code download for the ED, is this for straight DMX, 4 universes? And will it work with the conductor? I was looking to the conductor to save me buying another PC to use to run our show this year, I really don't want to tie down one of our two laptops in the house to the show. I will still use the conductor next year as I plan on starting into SS for pixelnet, but I am very confused at this point as to what stage the conductor and ether dongle are at.
The Etherdongle does have firmware to run 4 dmx universes. The conductor however is only sending pixelnet data at this time. It will be able to send dmx as soon as RJ finishes/releases the firmware for it. So to answer your question, yes the conductor will support dmx, just not yet. However, you can get dmx out by using the conductor with an ss active hub and pixelnet.
I hope this helps,
Grant
-
i was thinking that there were only 3 published etherdongle pixelnet firmwares, rather than 4 - e1.31 universes 1-32, 33-64, and 65-96 - which match the first three Chrisatpsu described. The conductor version need only address the first 4 pixelnet universes (e1.31 1-32, or addresses 1-16384, however you prefer to refer to it). each conductor/slave can have its own independent block of 4 universes - your software will need to be able to map the higher addresses to the appropriate sequence file.
the ether dongle in any configuration is only capable of putting out one type of data. It's either all pixelnet or all dmx. The actvie hub has a pixelnet to dmx converter that mirrors one of the eight 512 blocks of channels to a dmx output. At this time, there are no stand alone pixelnet to dmx converters.
The DMX conductor firmware is on the list for development, but the slave software is higher on the list...
RM
-
This is why I suggested to RJ that he not create DMX firmware for the Conductor or the EtherDongle itself for that matter. I believe that the better solution would be to create a converter board to do that. The grreat thing is that for the most part, it already exists on the active 16 port hub. It just needs to be seperated from it. This will cut the number of firmware versions (and revisions) in half and make it easy for people to use both and not have to attempt to locate one of their hubs near therr DMX devices and if they decide to stay with just DMX, they don't need to buid a full 16 port hub just to convert Pixelnet to DMX. But even if this new board never comes to pass, the active hub can provide all of the DMX channels someone would need and cut the workload for RJ in half.
-
I'd imagine that the code changes are relatively small to get DMX firmware... and that small change means saving $60+ for the active hub.
-
I was afraid of this... the extra complexity offered by more features will provide the argument to provide fewer features.
myself, i'm not so interested in the new dmx features within MY show, but I see a LOT of interest in this -- and I believe it is greatly important to people who blend RJ's equipment with non-RJ, standard-DMX equipment.
I'd argue that we need to do a better job to write clear manuals that crisply state the features and how it all comes together.
i am arguing that the extra features (especially DMX support) should continue to be developed. I think anyone that has played with this for a while feels that this is not rocket science, it makes sense, and there should be no technical reason why pixelnet and dmx should NOT coexist. the challenge is how to properly describe how it works so that newbies can get the same understanding.
-
I'd argue that we need to do a better job to write clear manuals that crisply state the features and how it all comes together.
With all the new toys/features that have been coming out, I would agree. I am willing to assist with this in any way I can.
-
So what I am hearing is that I definitely will not be doing an all DMX show this year using a conductor unless I buy an active hub to convert pixelnet right? Another hundred bucks worth of hardware to use the roughly 180 bucks worth of hardware in the etherdongle and conductor. Maybe my wife is right,drugs would be a cheaper hobby <;d
-
Maybe my wife is right,drugs would be a cheaper hobby <;d
ROFL
-
The lights would probably look cooler too!!!! ;D :o 8)
-
Anyone know what size SD card is coming in the CoOp? I can get Sandisk 32g class 4 for $11.....
Myk
-
Greetings,,,
Please do not substitute the card without being aware that it might not work. All cards are not alike in specs.
Keith
-
I understand that and have researched my SD card purchases in the past etc - but what size card are we getting is what my question was?
Myk
Greetings,,,
Please do not substitute the card without being aware that it might not work. All cards are not alike in specs.
Keith
-
They are compact flash cards with a high speed read. Don't remember the specs
-
8 GB compact flash card!
-
Thank you!
Myk
8 GB compact flash card!
-
I'm guessing that this is how things will fall out: the coop will include the approved CF part, and people will end up getting their own CF parts from another vendor.
as problems get reported, RJ and everyone else on the board will first ask: why CF card were you using at the time? and then they'll tell you to first reproduce the problem with the approved part -- before they can help you.
using the standard part (which RJ said will be purchased with coop prices and included in the coop) is just going to save you and all of the people who try to help you time.
-
Ya know, give me some credit - I am not stupid.
Do you not think the 1st thing I would try if I had problems was the orig card?
I want a backup, we have moist weather here in the winter and with the Etd/Conductor outside, the contacts are gonna corrode.......
-
Ya know, give me some credit - I am not stupid.
Do you not think the 1st thing I would try if I had problems was the orig card?
I want a backup, we have moist weather here in the winter and with the Etd/Conductor outside, the contacts are gonna corrode.......
I didn't call you anything. :)
I was just describing a future situation where a plethora of CF parts get added to the mix and a bunch of folks throw out the question: why does my conductor not work? ... and the first response will be: What CF are you using?
It won't be you, it will be the other guy with the problem.
Anyway, no offense meant.
-
Ok lets chill out!
DLA is not that kind of forum!
RJ
-
Easy guys.
Where those of us in the know, know, many folks that don't will make the mistake of buying something because it is cheap - not realizing that it isn't fast enough, needs the wrong voltage, or is just incompatible for no apparent reason...
Specs will follow, but for now rest assured that all the memory you need is coming with the device. After you get it, you can start experimenting to see if other parts work. The last thing we want to deal with is someone whining because they bought some memory on someone's recommendation and it just won't work.
Patience is a virtue. Coops require much...
This coop should run fast and those that got in should have everything soon enough.
RM
-
If you buy a different card there is about an 85% chance it will not function correctly. We put the card in the coop to prevent the issues. 8gb is plenty for an Conductor. it stores hours of shows.
Once the coop is over and you have yours if you feel you need another just buy the same thing.
RJ
-
This is why I like this site and the people here.
Every one is looking out for others.
Being a non tech person I don't get things right away.
RJ and all you guys that help out always think on a beginners mind set.
Bringing people up to speed.
Using murphy's law. What could go wrong will likely go wrong.
With out that mind set and the help and patience from the people at this site
I would have been lost a long time ago.
So I say thanks to all you at this site.
keep up the good work.
Mort
-
This is why I like this site and the people here.
Every one is looking out for others.
Being a non tech person I don't get things right away.
RJ and all you guys that help out always think on a beginners mind set.
Bringing people up to speed.
Using murphy's law. What could go wrong will likely go wrong.
With out that mind set and the help and patience from the people at this site
I would have been lost a long time ago.
So I say thanks to all you at this site.
keep up the good work.
Mort
+1
Rick S