ffmpegX used to be my go-to for video encoding... and it still has that potential, if Major has some big things up his sleeve that he's been keeping hush-hush for years. But frankly, applications like Handbrake have suited me fine for quite some time in ffmpegX's absence. It'll take some convincing to draw me back, but I'll keep apprised of where ffmpegX goes in the coming weeks/months.
If Major wants to really wow me, he'll tackle an area relatively neglected by most encoding apps: robust handling of stylized subtitles ((advanced) substation alpha) with regards to burn-in on encoding. It's an anime fan niche to be sure, but frankly with how jam-packed the encoder app scene is these days maybe appeasing a subculture would be a smart way to stand out.
Possible issue with H264 videos under 10.5.8 with version 4.2.0:
Symptoms: All H.264 video muxed into an .mkv container come up as green screens when played on Quicktime (7.6.6) with Perian installed (1.2.1), will not play through MPlayer OSX Extended rev13, but will play through VLC (1.1.2). Xvid video appears unaffected by the muxing process and plays fine in an .mkv container regardless of application.
Steps: Open MKVMerge. Add existing .mkv file with H.264 video. Choose desired streams. Mux. Once completed, open file in applications listed.
Note: H.264 video (identical to problem files) muxed into an .mkv container under previous builds of MKVMerge, played through the same applications, work without issue.
Pacanug- Are you also running 10.5? Unless my memory deceives me, I remember previous builds listing 10.6 as a requirement- When I saw 10.5, I was surprised but thought nothing of it and was actually happy to see it. Maybe this is where some of the issues are arising from?
Well if it's not OS-based as an issue, and seeing as how numerous applications vary on handling the outputted files, I'm thinking that it may be a systemic issue within the build of MKVToolsnix that somehow applications with looser or broader tolerances can handle, while others cannot. This is something that the dev should be made aware of, though whether they check these comments or not is something I am not sure of.
No problem. I'm still wondering what the developer's feedback on this issue is. Has anybody tested the latest version (4.3.0) with 10.5/10.6 and had positive results using the methods of error reproduction I posted above?
I've also noted that the dev team behind the WDTV product line put out a recent beta firmware upgrade to address issues pertaining to MKVMerge... I'm wondering if this issue extends beyond OSX and has permeated throughout all of the varying OS builds?
This is a jack-of-all-trades application, but a master of very little when it actually comes down to it. The handling of .ogm files is wonderful to see, and the ease of file extraction really sings to me as I am constantly tinkering with the streams of my files, but there's so many bumps all over the place that leave me scratching my head, such as a lackluster interface and feature set when actually converting files (a lack of automatic bitrate calculations becomes a bother, as well as the half-assembled height/width bar that leaves some of my .h264 files oddly squished when the original file under Quicktime has differing normal size and current size, natively).
In a way I suppose that I keep coming back to this application because the more efficient and robust ffmpegx has all but kicked the bucket and I am hoping to see the same sorts of innovation that that old and decaying application brought, but... maybe they are just two separate and differing things all together. It's a sad feeling knowing that I need to jump to a Windows partition to do even the most rudimentary of tasks with AVC files if I want exacting quality, but it just seems that for now that is the way it is.
not entirely interested in ditching azureus in favor of transmission, because quite frankly, the lack of a peerguardian-esque plug-in or feature just kills the deal. let's be honest, bittorrenting to the average user isn't exactly a by the books, legal deal, and transmission leaves the average user far more exposed to snooping IP's than azureus does with its SafePeer plug-in.
for quick, low profile/legal downloads, sure, transmission is good. for everything, no way. azureus, hands down.
Coincidentally, I verified that the batch of DVD+R DL's from RiDATA were without error or issue with the inner workings of OSX just tonight by using Apple's Disk Utility application. It handled the burn fine and reported back zero errors. The content was the exact same as what I wanted Burn 2.3u to handle. Very odd.
Burn handles my other standard DVD's just fine, so I guess that I'll just go to the Disk Utility in the future if I want to burn a DL. Too bad it cost me 2 DVD+R DL's to find out the proper course of action...
Encountered major error when burning RiDATA DVD+R DL. Application hung indefinitely in "closing session" phase before verification could begin. Allowed copious amounts of time to see if app would fix itself. It didn't. Quit yielded no results; force quit disappeared UI but app hung in dock. DVD would not mount on desktop nor eject by any means. Force rebooted, but DVD still in burn mode would not allow the computer to reboot. Cut power, rebooted. DVD would not mount nor eject. Rebooted again, this time holding eject button at chime. Worked. Following link has screen cap of error report: http://tinyurl.com/qu4ssc
application will not start up, period. no action on the dock, nothing. no blips from Activity Monitor either. running G4 533 dual processor (Digital Audio), 768 RAM, OS 10.3.9, all updates current.
[Version 1.0.2]
Please login or create a new MacUpdate Member account to use this feature
+3
ffmpegX
If Major wants to really wow me, he'll tackle an area relatively neglected by most encoding apps: robust handling of stylized subtitles ((advanced) substation alpha) with regards to burn-in on encoding. It's an anime fan niche to be sure, but frankly with how jam-packed the encoder app scene is these days maybe appeasing a subculture would be a smart way to stand out.
+2
MKVtoolnix
Symptoms: All H.264 video muxed into an .mkv container come up as green screens when played on Quicktime (7.6.6) with Perian installed (1.2.1), will not play through MPlayer OSX Extended rev13, but will play through VLC (1.1.2). Xvid video appears unaffected by the muxing process and plays fine in an .mkv container regardless of application.
Steps: Open MKVMerge. Add existing .mkv file with H.264 video. Choose desired streams. Mux. Once completed, open file in applications listed.
Note: H.264 video (identical to problem files) muxed into an .mkv container under previous builds of MKVMerge, played through the same applications, work without issue.
+20
+20
+1
+20
http://jonthn.free.fr/MKVtoolnix/
+20
I've also noted that the dev team behind the WDTV product line put out a recent beta firmware upgrade to address issues pertaining to MKVMerge... I'm wondering if this issue extends beyond OSX and has permeated throughout all of the varying OS builds?
+1
MKVtools
In a way I suppose that I keep coming back to this application because the more efficient and robust ffmpegx has all but kicked the bucket and I am hoping to see the same sorts of innovation that that old and decaying application brought, but... maybe they are just two separate and differing things all together. It's a sad feeling knowing that I need to jump to a Windows partition to do even the most rudimentary of tasks with AVC files if I want exacting quality, but it just seems that for now that is the way it is.
Newspeak
Transmission
for quick, low profile/legal downloads, sure, transmission is good. for everything, no way. azureus, hands down.
Firestarter FX
Burn
DRErrorStatusKey = {
DRErrorStatusAdditionalSenseStringKey = "Focus servo failure";
DRErrorStatusErrorKey = -2147352542;
DRErrorStatusErrorStringKey = "The device failed to respond properly, unable to recover or retry.";
DRErrorStatusSenseCodeStringKey = 04;
DRErrorStatusSenseKey = ;
};
DRStatusCurrentSessionKey = 1;
DRStatusCurrentSpeedKey = 3324;
DRStatusCurrentTrackKey = 1;
DRStatusPercentCompleteKey = -1;
DRStatusProgressInfoKey = {
DRStatusProgressCurrentKPS = 3250.39599609375;
DRStatusProgressCurrentXFactor = 2.299999952316284;
};
DRStatusStateKey = DRStatusStateFinishing;
DRStatusTotalSessionsKey = 1;
DRStatusTotalTracksKey = 1;
The error list continues for a while. Can post more data if needed.
+20
Burn handles my other standard DVD's just fine, so I guess that I'll just go to the Disk Utility in the future if I want to burn a DL. Too bad it cost me 2 DVD+R DL's to find out the proper course of action...
Burn
XsTrimmer