![]() Open the EyeTV Programs window, choose the Recordings section, and select the video recording you wish to archive by clicking on it once to highlight it."To burn a disc from within EyeTV, using Toast: is there any way to talk with a live representative of the publisher after all this? I would really like to encourage them to make the drag and drop option easy to use!Īctually, the "Official, official" way in the EyeTV 3 User Manual specifies drag and drop: Perhaps that added information is giving Toast indigestion. That extra data is added to the ".eyetv" file. I usually have EyeTV set to add formatting for viewing by iPhone and iPad. So it probably introduces fewer artifacts and is certainly faster. That method does avoid the double re-encoding when exporting to a ".dv" file from EyeTV, then moving it to an iDVD project for burning. I played with burn settings and the ONLY reliable way to do it is to leave re-encoding set to Automatic (the default). This can be dragged into or opened by Toast. The export is quite fast because it doesn't involved re-encoding. In EyeTV choose File:Export, then choose MPEG Program Stream (not MPEG Elementary Streams) as mentioned by Digital Guru above. I did find some recommendations on the Elgato site: Look like I'm a beta tester again.Īs far as I can tell, drag and drop from EyeTV to Toast cannot be made reliable with the EyeTV files I have to test with. The whole reason I got the new version of Toast was to make the process very simple. I'm not too keen on a lot more experimenting. Keep in mind that it did not give me any error message. I suspect that Toast 11 has serious flaws. I'm not optimistic that there is an easy solution. This appears to be a software problem, perhaps in EyeTV, but more likely in Toast. ![]() The second two hour show was equally successful via iDVD. I tried turning off verification, recording at 4x (way reduced speed), etc.įinally, I figured out how to move iDVD from another computer, Exported in iDVD format from EyeTV, launched with iDVD, set up the menu screen and burned it. Then it indicates that it has started writing and that it will be done in a couple minutes. Then it starts multiplexing again at 0%, briefly. Next it indicates that it is multiplexing and gets up to about 13%. The first progress message indicates that it is Encoding. I tried the second two hour show and got maybe 30 minutes of it.īy the way, I'm running Mac OSX 10.8.2 on a MacBook Pro Retina purchased a few months ago. There were no warnings issued by Toast and I ended up with 16 minutes of my two hour show on DVD. So I launched EyeTV and Toast, dragged the first EyeTV program over to the Toast video pane, verified there would be enough space on a regular size DVR disc and pressed "Burn". I was looking for a straightforward, no-frills way to transfer a couple EyeTV programs to DVD. (I had owned Toast 10 and earlier versions.) So, I purchased the current version of Toast Titanium 11.1_1072 and downloaded it. Anyway, given that the PC desktop connected to the same router as the Mac is working just fine and not getting the error message, I dunno what i ought to be doing about router ports at this point.My EyeTV3 version 3.5.6 (6920) software documentation suggests an easy way to burn a DVD of my program. The PC desktop gave no error message, the Mac gave the message that I mentioned (although followed by the message that sets out the access key and says the configuration can't be reached from the internet, about which I don't care), and the PC laptop is caught up in a "failure to update" loop that I will have to address by uinstalling and reinstalling. I am at work now, but just tested remotely the server settings on the three versions of JRiver that are on computers connected by ethernet to my router (a PC laptop, a PC desktop, and the MacBook Pro). I manage ports on the router rather than on the individual computer, which, I guess, is how it's usually done. I am a bit confused about the port numbering issue. This time, I got the same error message when testing connection on the Mac, but was able to connect and run things headlessly using Gizmo without a problem and despite the error message.
0 Comments
Leave a Reply. |