Username:
B
I
U
S
"
url
img
#
code
sup
sub
font
size
color
smiley
embarassed
thumbsup
happy
Huh?
Angry
Roll Eyes
Undecided
Lips Sealed
Kiss
Cry
Grin
Wink
Tongue
Shocked
Cheesy
Smiley
Sad
<- 1  -   of 38 ->
--
--
List results:
Search options:
Use \ before commas in usernames
Edit history:
Patrick: 2013-05-05 05:59:14 am
Quote from Carcinogen:
not exactly conducive to encoding SDA video

I guess that is why it is not going to be done.
Let's assume this feature is added to yua: 'open the resulting file in a batch script of your choice': would there be people contributing scripts? In the same way that many people contribute a few patches to open source programs, I mean. Edit: That on the 'download page' it says 'check this post for scripts which can split the file into parts, upload to youtube (if that works)', etc. I think I would be able to contribute a batch script for windows that uses ffmpeg to do the splitting, other things that I feel might be automatable are youtube uploads, dropbox uploads.
unless i'm missing something, you can do all that right now with the cli. e.g.

Code:
yua --d1 --f2 --3d --interlaced --input=lol.avi --output-basename=my_awesome_run
your_batch_script.bat my_awesome_run_HQ.mp4
Edit history:
Patrick: 2013-05-08 03:22:31 pm
I was wrong: no one expressed interest, therefore it does not deserve implementation into the GUI.
That confuses me. Really, no one posted: 'Automatically upload to YouTube? That's so convenient, I can let it encode from 8pm into the night and then just post the link next morning.' Confusing. *shrug* ... :-D
For the 0.5% ^^ who are interested, I found this: http://code.google.com/p/youtube-upload/

Thanks for the CLI, btw. :-)

Btw @Carcinogen: a splitting script is not relevant for YouTube - except if you have uploaded illegal stuff in the past, IIRC: get permission here
i just noticed that phaeron got back to me and it may be relevant to snow or other people interested in >= 4 gb wav. this isn't really yua-related but it was discussed in this thread earlier.
just a note that alpha 10 (not yet released) preserves more chroma data in iq+. so don't be alarmed when you see yuv444 stuff appearing on the front page. i made an executive decision. response to people complaining about incompatibility will be the same as it's always been: use one of the sda recommended players, e.g. vlc.
thethrillness.blogspot.com
Quote from nate:
just a note that alpha 10 (not yet released) preserves more chroma data in iq+


Just to double check, this will only affect PC runs since IQ+ would be > 720p? I have to agree with this decision if this is true.
Not a walrus
Quote from TheThrillness:
Just to double check, this will only affect PC runs since IQ+ would be > 720p? I have to agree with this decision if this is true.


IQ is still capped at 720, but XQ can go 1080. So 360/PS3/WiiU runs captured with appropriate hardware might be affected. Not sure if any of the current capture methods do anything but 420.
Edit history:
TheThrillness: 2013-05-26 02:38:13 pm
thethrillness.blogspot.com
I know the Intensity Pro does 4:2:2 and I think the SC-500N1 is 4:2:2 to. I think 4:4:4 should be used for XQ since 4:4:4 would just be a waste (maybe yua can give an option for you to choose what input format you used).

I'm also scared that if 4:4:4 is used, there might be some color issues going from a 4:2:0 (or 4:2:2) source to a 4:4:4 encode. I might be wrong though.
Why are you against it? It's not like there should be a lot of problems with going from 4:2:0 to 4:4:4 since it would be adding colour information and not removing (at least, in the ideal world).
Edit history:
Sir VG: 2013-05-26 05:06:23 pm
Sir VG: 2013-05-26 05:00:02 pm
Fucking Weeaboo
I'm testing out Yua alpha 9 with .ts files, which is what PC-Free Mode exclusively uses on the new AverMedia Live Gamer Pro (PC mode encodes in either .ts or .mp4 with the program). So far Yua is handling it like a champ, but having that trimming ability will definitely help, since VirtualDub can't open .ts files natively. I hear DGIndex can allow you to stream in those files via AVS but haven't gotten to test that though. (Edit: The version included with anri-chan in the dgmpgdec150 folder fails, but the dgavcdec109 one opens it, but the AVS file fails to open in VirtualDub.)

Glad to know it works though, because this is gonna be a new easy way to record PC games, since it's basically no longer dependent on your CPU and hard drive speed as a bottleneck for stuff like FRAPS.
thethrillness.blogspot.com
Quote from Mystery:
Why are you against it? It's not like there should be a lot of problems with going from 4:2:0 to 4:4:4 since it would be adding colour information and not removing (at least, in the ideal world).


I was under the impression that if your source is 4:2:0 you simply can't just set it to 4:4:4 for any benefit. It is still going to be 4:2:0 to the human eye. Guessing again but I think 4:4:4 will just make for larger sized encodes since more "redundant" data is being held.
there is no chroma upsampling. the only change is that yua will no longer downsample for iq/xq. this is the actual code used:

Code:
        AVPixelFormat low_fi_colorspace = AV_PIX_FMT_YUV420P;
        AVPixelFormat high_fi_colorspace = low_fi_colorspace;
        if (AV_PIX_FMT_YUV420P != original_colorspace) {
                if (AV_PIX_FMT_YUV422P == original_colorspace) {
                        high_fi_colorspace = AV_PIX_FMT_YUV422P;
                } else { //probably rgb input
                        high_fi_colorspace = AV_PIX_FMT_YUV444P;
                }
        }

it's yuv and not rgb because rgb x264 via ffmpeg is fucked up right now.

sir vg: trim support already exists in a primitive form - unless you meant more than two trim points in which case oops, yet another feature i have to finish.
Edit history:
ballofsnow: 2013-05-26 08:09:04 pm
Do any filters you use force you to down-sample? Was annoying with avisynth.

For LQ/MQ/HQ, playing by ear or do you have a time in mind of when to also upgrade these?
nope. all input is converted to rgb32 (padded rgb24) and then converted again for output. it's kind of retarded but i'm pretty sure the conversion routines i use are so good that there is not a perceptible loss of information from the single trip through rgb. and anyway i figured that working in rgb all the time would be a hell of a lot better than working in yv12 all the time, cough cough.

probably can't bump the lower qualities (especially mq) until there is near universal support. in particular i think neither apple nor microsoft platforms have it out of the box currently. will probably be many years ... can maybe theorize about tv/film versus computer sources and how the former are privileged in computers and the irony thereof because the computer software is made by computer software companies, not film or tv companies. but people have to get paid somehow i guess - unless you work for sda and then you're doing what's right, beautiful and/or elegant.
We probably won't ever see 4:4:4 support in consoles/external equipment/default players on windows/mac (linux is another matter, though). Maybe some niche external players will have it, but by far, I don't think we'll ever see it in the majority. For pcs, the default players kinda suck and probably will always continue to do so, but on the other hand, there are always GOOD media players which can handle everything you throw at them. Sticking with a stock media player these days is probably not a good idea for pcs, so pushing 4:4:4 there is probably fine.
For anything less than hd, external media players will probably handle most things thrown at them just fine, although not other colorspaces. But when it comes to hd, they all bark at one thing or another, so I just tend to reencode everything for mobile consumption to make sure it can handle it. Doing so, we really don't have to worry about colorspaces...
Not a walrus
My only issue is that if some IQs will be 4:4:4 and some won't, I think the ones that are should be tagged in the filename as such. Otherwise there's no real way to know without downloading the file, maybe copying it to a device, and then whoops it won't play. Not sure that's a good idea.
A good point, I think.
A tag in the filename and a note on the download page that it won't play on external devices, perhaps. A tag in the filename is useful to distinguish between downloaded files, but it sure isn't user friendly. A quick note on how to reencode the run to play on external devices might be in order, too.
Fucking Weeaboo
Oh cool, completely missed the trim menu. Guess I wasn't really looking for it since the opening post says "no support yet for cropping or audio commentary." But adding multiple points may be needed since the device I'm using records in PC mode on FAT32 SD cards, so I'd assume it would auto-break at 4GB (about an hour of recording at 720p in my estimates) and I don't know if I would get overlap or missing frames or such. I've got a few things to play around with on this new recording device, but both Greenalink and I have one and are spending time with it in seeing what can/can't be done with it.

So good that it can trim, but may need more trim points or may possibly need a way to merge multiple files, if a way doesn't exist right now. I'll keep posting on what I find.

(That being said, the test video I recorded and encoded looks good in MQ and outstanding in HQ.)
The 320x240 stuff is what gets zoomed by full-screening.
That is where the biggest gains from using 444/422 are, IMO.
good point. i didn't even think about that. i was mostly thinking of small colored text and other color details in pc games, especially 2d ones like the rks series.
alpha 10.

appending and more than two trim points.

i rewrote synchronization, statid, and several other things for this release. as such it will be less stable than people became accustomed to with alpha 9. if you don't care about appending or multiple trim points and you're not planning on helping me find bugs then you should probably skip this release.

some info about appending:

- appended segments of different dimensions are all resized to the largest dimensions of the lot. width and height are independent (!).
- similarly, no frames are dropped, and frames are inserted only between segments. this means the output is vfr.
- if you append segments with different framerates (even by .001 fps), yua may crash on encode. let me know if this happens to you and i will try to do something about it.
- yua attempts to standardize on a number of audio channels. this, like everything else, is probably buggy.

trimming:

the functionality is changed. you select what you want to delete and then hit the delete key. you can do this as many times as you want to trim down your video.

other changes:

- custom statid image: place an image called statid.png in the same directory as the yua program. it must already have the correct aspect ratio for what you're encoding (thanks sir_vg)
- as previously mentioned, iq+ now preserves the full chroma resolution of the input, even if it is > 4:2:0. also, even if the input isn't > 4:2:0, if the output is d4, iq+ will be 4:4:4, so you can encode iq for old school game videos and get something that looks much better fullscreen (thanks gyth)
- some minor ui tweaks and other stuff i've forgotten
Fucking Weeaboo
Yay for custom statIDs! Smiley
Edit history:
IsraeliRD: 2013-06-07 09:52:39 pm
IsraeliRD: 2013-06-07 09:47:18 pm
IsraeliRD: 2013-06-07 09:45:40 pm
IsraeliRD: 2013-06-07 09:27:24 pm
IsraeliRD: 2013-06-07 09:26:54 pm
Dragon Power Supreme
Been waiting for this release. Gonna test and let you know how goes.
Edit: Few requests:
1) Can we get a 'save project' where it saves the project, the videos etc. so it can load much faster? I just accidentally pressed open instead of append without realising and lost the last 15 minutes of videos appending.

2) It would be nice if we can also enter the frames we want to trim, since I have those ready from VDub. apparently i can't select a bunch of them and delete at once. manual work it is.
... in retrospect I should've started at the end and deleted the frames from back to the start since I have the numbers of frames I want from VDub.

3) When loading videos, can we load several videos all at once? It would be easier for me to select all 20 videos and let yua load them (since they are properly numbered, there shouldn't be any problems in organising them).
The bad part is yua needs to load every video to figure out what's going on so it kills the most amount of time.

4) Would love it if yua remembered settings such as last file load location I'm currently appending 20 videos which are like 4-5 clicks away (I start on desktop, then have to click on My Computer -> G:/ -> SDA -> TPI -> video every time). Settings like encoding would be great to save as well (so you can save several configurations, and just load your favorite for different things).

More to come.

Edit 2: Why is yua saying XQ is required (and it's in red) when I know IQ is the best I'll get out of this FRAPS recording. It's in 1024x768 30fps. It has no problems encoding when XQ wasn't selected but yeah. Odd.
HELLO!
"same directory as the yua program" makes no sense on Mac OS but  I'm patient (I'm also skipping this release since I don't care about appending or multiple trim points Smiley
Edit history:
Patrick: 2013-06-08 06:20:11 am
Patrick: 2013-06-08 06:20:04 am
Patrick: 2013-06-08 06:19:56 am
Patrick: 2013-06-08 06:19:50 am
edits in blue
The shortcut C-S-[ does not work on the QWERTZ layout in windows, since [ is AltGr+8 and AltGr=C-A, so the shortcut would be C-S-C-A-8. lol

3) You can copy the path of the folder in the explorer and then paste it and then press Return into the text field to save the first clicks.