according to nVidia's driver page, you are not using the latest drivers .. try these:http://www.nvidia.com/object/win7_winvista...96.21_whql.html
as for your graphics card, it should be able to handle CUDA, if it has at least 256MB of local memory
but to be honest, I wouldn't expect any miracles, since it seems to be equipped with a mere of 16 cores
Quote from: Maggi on 29 January, 2010, 11:20:10 AMaccording to nVidia's driver page, you are not using the latest drivers .. try these:http://www.nvidia.com/object/win7_winvista...96.21_whql.htmlNot sure they will work. Geforce 9300 isn't listed under supported products. I've been struggling previously to get newer releases to work on this. Note that while it's called Geforce 9300, it's a mainboard chipset based on a nForce 730i chip - Not to mix that up with the Geforce 9300 GS chip, which are entirely different.
GeForce 9 series:9500 GS, 9600 GT, 9200, 9800 GX2, 9500 GT, 9600 GS, 9300, 9800 GT, 9400 GT, 9300 GS, 9400, 9600 GSO, 9300 GE, 9800 GTX/GTX+
Quote from: Maggi on 29 January, 2010, 11:20:10 AMas for your graphics card, it should be able to handle CUDA, if it has at least 256MB of local memoryI have not yet verified with 100% accuracy that I have activated 256MB on it, but according to Windows, it seems that I have. I'll be back on this one
Quote from: Maggi on 29 January, 2010, 11:20:10 AMbut to be honest, I wouldn't expect any miracles, since it seems to be equipped with a mere of 16 coresWell it IS sold as having CUDA capability, so no matter how good it would ever perform it should, and I'll be glad if I could just get FlaCUDA up and running. It compresses better than native FLAC, so if it's just able to compress my lossless music even further I'm happy
Problem found: It's due to Microsoft's RDP-lameness. When using remote desktop, the graphics adapter is disabled and replaced by the one used for RDP.So thanks MS, I can't use CUDA programs using RDP!
CUETools.FlaCuda.exe -11 Priceless.wavFlaCuda#.91, Copyright © 2009 Gregory S. Chudov.This is free software under the GNU GPLv3+ license; There is NO WARRANTY, tothe extent permitted by law. <http://www.gnu.org/licenses/> for details.Filename : Priceless.wavFile Info : 44100kHz; 2 channel; 16 bit; 00:04:07.6270000Error : Exception of type 'GASS.CUDA.CUDAException' was thrown.
CUDA Device Query (Driver API) statically linked versionThere is 1 device supporting CUDADevice 0: "GeForce GTX 480" CUDA Driver Version: 3.0 CUDA Capability Major revision number: 2 CUDA Capability Minor revision number: 0 Total amount of global memory: 1576468480 bytes Number of multiprocessors: 15 Number of cores: 120 Total amount of constant memory: 65536 bytes Total amount of shared memory per block: 49152 bytes Total number of registers available per block: 32768 Warp size: 32 Maximum number of threads per block: 1024 Maximum sizes of each dimension of a block: 1024 x 1024 x 64 Maximum sizes of each dimension of a grid: 65535 x 65535 x 1 Maximum memory pitch: 2147483647 bytes Texture alignment: 512 bytes Clock rate: 0.81 GHz Concurrent copy and execution: Yes Run time limit on kernels: No Integrated: No Support host page-locked memory mapping: Yes Compute mode: Default (multiple host threads can use this device simultaneously)Test PASSED
Unhandled Exception: ErrorLaunchTimeout
Is FlaCuda with the "--verify" switch considered to be safe for archive use?
As far as I understand you use the parallel processors on the GPU find the best "next step" (don't know how it's called in FLAC terminology) and then execute it on the CPU.
Is this approach limited to FLAC or can similar computations of other audio/video formats use it?
*** FLAC 1.2.1 @ 4 threads ***level 8Total encoding time: 0:22.277, 124.90x realtime*** FlaCuda 0.91 ***-8 - -o %d --verifyTotal encoding time: 1:01.184, 45.47x realtime-8 --cpu-threads 2 - -o %d --verifyTotal encoding time: 0:50.529, 55.06x realtime-8 --cpu-threads 3 - -o %d --verifyTotal encoding time: 0:42.807, 65.00x realtime-8 --cpu-threads 3 - -o %dTotal encoding time: 0:42.011, 66.23x realtime-8 --cpu-threads 4 - -o %d --verifyTotal encoding time: 0:42.027, 66.20x realtime-8 --cpu-threads 4 - -o %dTotal encoding time: 0:41.356, 67.28x realtime-8 --slow-gpu --cpu-threads 4 - -o %d --verifyTotal encoding time: 0:37.939, 73.34x realtime
Is there anybody here who knows the math behind Cholesky decomposition used in ffmpeg as an alternative method of LPC coefficients search?This method is too slow for CPU, but i thought i'd give it a shot on GPU.The problem is, GPU doesn't do double precision very well.
Man, that's some fast encoding! Nice work!Is there any chance that tag writing will be added to the binary, so that it can be used with EAC?
Quote from: Mataglap on 29 July, 2010, 09:24:50 PMMan, that's some fast encoding! Nice work!Is there any chance that tag writing will be added to the binary, so that it can be used with EAC?You already can with metaflac. I gave an example here flacuda.exe & metaflac.exe in EAC
I have an 8800GT too but I was unable to get much above 70x, per my post above, with FlaCuda. Your results would beat my Q6600's benchmark of 125x. Am I missing something?