Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
We made a new machine with Atomix LT 4BNC and dvs 184.108.40.206.
Then you can no longer do stopAll.
Does disabling the player in ingexgui prevent the crashes?
we have a PC with ingex: a gigabyte maiboard z77x-ud5h, video card ZOTAC GTX580, atomix lt 4BNC and dvs sdk 4.3 .0.10.
Malfunction of kde blocks of the video.
Removed ZOTAC GTX580 and put a fx quadro1400 old but okay.
Ingex worked badly:
1 - Unable to lock the capture. Even though we were using CTRL + C did not stop the capture.
2 - Ingex gui crashed after being opened.
3 - if you started the gui ingex the black window and EE did not close it. Necessary to restart the machine.
Removing the sdk 220.127.116.11 and 18.104.22.168 installed. Better functioning. Sometimes he gets stuck on everything having to restart the PC. There is no raid on this machine.
2 hard disk: 1 video and 2 system.
If we start the machine dvs_setup restart the ingex is better but not stable. But when we launch ingex gui and EE is often a block of the player window and then lock ingex gui.
I forgot open suse 11.4 to date.
What do you think the problem? Atoms? SDK? Mainboar? or all?
Do you have Nvidia drivers installed?
How much RAM do you have on the motherboard?
Do the problems happen before you try recording?
Yes, I have installen nvidia driver from repositorie of sus from openssuese 11.4
8GB OF RAM.
Today I have this problem
Ingex gui displays timecode stuck
Ingex gui freezes and also capture crashes.
Other times there are errors of time code.
The other 2 machines with centaurus not give nesun problem.
There is a software to test the centaurus?
The firmware is updated.
What messages do you see from capture process (dvs_sdi)?
sspagna, have you configured the dvs_sdi to the 4BNC audio mappings? They differ from the Centaurus and Atomix LT boards.