Discussion in 'CloneDVD mobile' started by Peer, May 21, 2012.
Before or after Slyce?
Sooner than Slyce
We are going to release a new CloneDVD mobile this week I'm told.
The migration away from the old mobile engine is moving along quite well as this is the very same engine concept to be used in Slyce. 1806 was the biggest jump in that direction and we see mobile as less rigid now and the new processing is able to better handle difficult DVDs. Eventually we will totally drop FFMPEG as the root engine as this has more or less reached an end of life point.
Since the mobile conversion part of slyce uses the same engine the new clonedvd mobile uses it could be at the same time. But don't pin me down on that
Verstuurd van mijn HTC Sensation XE with Beats Audio Z715e met Tapatalk
Thank you for the update, Frank. I was wondering why I seemed to have been experienced slightly more encoding errors with 1806 than I was experiencing with 1802. Now I know and am waiting for the next revision to "stress test" it with my backlog of encoding I put off doing.
I was more lazy about encoding than waiting for error correction, I have more than enough ripped stuff to watch already ripped.
I can say for sure that the >1806 release will pick up a lot of errors.
There are still some DVDs that will not process but the product is becoming more and more tolerant and less rigid in trans-coding. Don't expect the next release to be a magic wand. There are parallel activities between the engine migration in CDm and the development of the process for Slyce.
I don't want to appear pushy, but are there any news about the next (beta) release of CloneDVD mobile?
Fernando is very busy with Slyce at the moment and is trying to squeeze out an official release for mobile.
To qualify my original statement, the migration going on in Mobile now will form the BASIS for the next engine release as we move away from FFMPEG. 1806 mobile is a lot more tolerant that previous versions but there are many "unsolved" authoring problems and this coming release will pick up many of the errors submitted by the automatic reporting routine.
@Frank I'm curious - you say you are moving away from FFMPEG and developing a new engine I assume you are talking about a encoding/decoding (transcoding) engine? Is the "next engine" an in-house developed engine or an open source alternative? Will Slyce be using an open source engine for transcoding (namely x264) or an in-house developed engine? Sorry if my use of the terms encoding/decoding/transcoding are incorrect or out of context. Thanks.
What is slyce?
Slyce: Slysoft's Soon released Blu-ray Backup Product. Topic v1.2
Separate names with a comma.