If they (BW and S64) do it for profit, then the one that offers the most for the least will win out. If they do it for the community and for the love of doing it, then it really doesn't matter. I do Video and Audio Engineering, 64bit works very nice for me. On the computers I have that work with 32 bit, they have a 32 bit OS on them.
It's all going to be moot in 2010 anyway. CP/M is going to make a comeback and blow *nix out of the water. -JJ |
Quote:
I guess there will be other tasks, like highly computational ones (maybe statistics and such) that might profit from 64bit, but I have not tested it. |
Quote:
Do you have some commandline examples available that can be used as computational benchmarks? Using ffmpeg would be cool. Eric |
Quote:
|
Quote:
I use the script on MPEG files that I record with Kaffeine from DVB-T and cut with dvbcut. With "German" as default name for the sound as you can see :) EDIT: As you can see some stuff is hardcoded that I don't change, like ogg quality, the mentioned German audio and also that the name of the input-mpeg file has to end with "mpg", which has to be omitted when given as parameter. I call it like that: Code:
dvb-convert.sh "Name of the video without dot ending" 1100 "528:560:8:8" Code:
#!/bin/bash |
Please take the values I gave with a little bit of caution. I know I had really serious gains in the past, but did a little test to give some real life real video values. It happened like it had to happen, the gain with my chosen video file was much smaller (14,0 fps on my Slackware 12.1 system versus 16,73 fps on Slamd64 12.1, same video file, second pass of a x264 encoding, values taken at 14 % of the whole film so the sample was about 12,5 minutes long).
I suspect the values might differ significantly with the source video files, that's the best vague reason I can give for my result. |
Quote:
I have done two different encodings on the same machine, an AMD Athlon 64 3700+ with 1,28GB RAM. Source material was a recorded DVB-T stream of about half an hour. I used mencoder from mplayer 1.0rc2 with xvidcore 1.1.3, lame 3.97 and x264 snapshot from 20080718. Encoding 1: 2-pass conversion to x264, video encoding only. Encoding 2: 2-pass conversion to xvid and mp3 at the same time. Code:
Encoding 1, x264, video only But I think that it might serve as a hint on how much circa your encoding with 64bit might increase. Not that much as I thought first, but it's not neglectable as well. Thanks for listening. Any questions? ;) |
Quote:
Your point of view would change drastically. IF 1.)you had a 64bit compatible computer this means that it has 64bit data paths to at least the hard drive,video adepter and most importantly the memory as well as a 64bit CPU (of course ) 2.)you installed a 64bit distro what ever 64bit distro my 2 cents as long as you have this point of view is that you should stay out of this subforum until you lose your present point of view I know that I already replied to that post I'm just in one of those moods |
@Rob - chill out dude. SqdnGuns is entitled to his opinion, as is every member here. While he may be a bit controversial on occasion, he's not a troll and is helpful - as are you. Telling people to get out of any forum or subforum is never a good idea and gets you tarred with the same brush.
So let's all be friends, eh. I'll even help you out: SqdnGuns, what makes you hold that opinion, since so many other members would clearly disagree? |
Thank You
they could ask me to stay out of the youbumtoo subforum any time any distro with out root access is not linux |
Since Patrick has already complimented Arny for what he has done on BlueWhite64, I would assume that when the time comes, Patrick will just join up with what Arny for one has done and bring it into the fold. Very talented guy, easy to work with and responds very quickly to any questions. Highly recommend this distro. Very nice to work with.
|
PAtrick never complimented arny for the work he has done. He wished him luck in his efforts to create his 64bit port: http://www.bluewhite64.com/e107_plug...ewtopic.php?56 but that was around the time bluewhite64 went public, so nothing was known about how it was created. There is no reason for Bluewhite64 to have any advantages over other 64bit ports like slamd64 (which is what Bluewhite64 is based on), the 64bit Vector or any other version.
They're all derivatives of Slackware. A Slackware 64bit release, will be Slackware. Eric |
Quote:
|
Yes it's great to see x64 Slackware in current, but what does that have to do with Bluewhite64? As far as I know arny has done a lot of hard work as well, why isn't he thanked for that too?
|
Quote:
Excellent work and SUPPORT, Arny! |
All times are GMT -5. The time now is 12:54 AM. |