Ludacrisvp

Not sure what happened but it eventually stopped recording random shows.

I’ve no desire to reboot to another OS to run eyetv3 (in fact I don’t believe I even have a copy of it). Big Sur can’t run anything less than 4. a workaround I’ve been using was to swap the eyetv binary from the retail version of 4 into the app bundle from one of the betas. That’s letting me bypass their time restriction on the beta, it doesn’t bypass license needs doing that (yes I have a valid license, had to buy it from the non US store as their US site has no mention of it). schedule wise I don’t have a subscription and have to have the tuner hit every channel to get the program guide from the provider. I was really hoping this hardware would have run via Plex and then I could bypass all this crap with eyetv but it doesn’t. I’ve been debating getting a HDHomeRun that has the ASTC 3.0 tuners (which handles 4K content) to deal with any OTA TV.

They actually advertise the export options of the beta on their product page (screenshot is from the beta). I don't recall if I used EyeTV3 to be honest, so i can't make the comparison. You can see this exportability is advertised just after the video editor portion. https://www.geniatech.eu/product/eyetv-4/

Anyone know where the scheduling is really controlled from? I set up a recurring recording for a show for the kids and they aren't as interested in it as expected, so I deleted the "Smart EPG" for it, but they keep getting recorded. I then removed all the 'eyetvsched' files from the EyeTV archive path, however they were automatically re-created a bit later. So this tells me there's some actual schedule done via some other means, anyone know what that is / where it is located?

As a previous user of EyeTV 4 Betas and using the export functionality, I've noted that the released version is quite different from beta in the export functionality. Exporting a video with the Beta is infinitely faster (better) and consumes less CPU vs the current production version. Production will use 600% CPU or more during an export. Beta will use about 250% CPU or less during an export, which again takes a few seconds for a 30 minute video, vs several minutes for the same video on production. Beta Format Options for export were limited to these 2 options: Native Formats (no re-encoding) - MPEG Program Stream - The fastest export option. For MPEG-1/2 content a program stream will be created. For H.264 content a .mp4 file will be created. For MPEG-4 or DivX content an AVI file will be created. Video: MPEG, 1920 x 1080, 29.97 fps Audio: Dolby Digital, Stereo, 48000 Hz Duration: 31:59, Estimated Size: 1.4GB (753 KB/sec) - MPEG Elementary Streams De-multiplexes and creates separate files for audio and video. This is an advanced formay for special applications. Video: MPEG, 1920 x 1080, 29.97 fps Audio: Dolby Digital, Stereo, 48000 Hz Duration: 31:59, Estimated Size: 1.4GB (753 KB/sec) In the production version it just lists out a file extension option and no details on what it is going to do and no options on how it should be exported. The video exports in production are re-encodes using ffmpeg. MP4 - (appears to be default export selection) (compression artifacts introduced from video re-encoding, audio re-encoded from AC3 to AAC audio, and has a larger file size vs source) -- ffmpeg -ss 00:00:00 -i EyeTV Archive/<showname>.eyetv/00000000253a2d18.ts -strict -2 -b:v 7000K -y -map 0:v -map 0:a Video/<showname>.MP4 MOV - (compression artifacts introduced from video re-encoding MPEG-4 mp4v stream, audio re-encoded from AC3 to mpeg AAC mp4a audio, and has a larger file size vs source) -- ffmpeg -ss 00:00:00 -i EyeTV Archive/<showname>.eyetv/00000000253a2d18.ts -strict -2 -b:v 7000K -y -map 0:v -map 0:a Video/<showname>.MOV MPEG - (compression artifacts introduced from video re-encoding MPEG-1/2 mpgv stream, audio re-encoded from AC3 to mpeg audio, and has a larger file size vs source) -- ffmpeg -ss 00:00:00 -i EyeTV Archive/<showname>.eyetv/00000000253a2d18.ts -strict -2 -b:v 7000K -y -map 0:v -map 0:a Video/<showname>.MPEG WMV - (compression artifacts introduced from video re-encoding MS MPEG-4 video v3 stream, audio re-encoded from AC3 to wma2 audio, and has a larger file size vs source) -- ffmpeg -ss 00:00:00 -i EyeTV Archive/<showname>.eyetv/00000000253a2d18.ts -strict -2 -b:v 7000K -y -map 0:v -map 0:a Video/<showname>.WMV WAV - not sure why one would want this format, but this flat out fails with EyeTV logging [Error Domain=转换失败,请检查源文件的编码格式! Code=0 "(null)"] leaving a 0-byte file in the export path. (The same video that could be exported via beta in a few seconds, takes a long time in the production version because it is being re-encoded.) Exporting in the beta just re-muxed the 'ts' transport stream files into a new mpg container with no-encoding keeping the original source quality, and the closed caption streams too, audio was also retained with the original format and quality. Why does the released retail copy of this program not offer the superior options for exporting video that was present in the beta? Why are there zero options for fine-tuning the exports that are being run on the retail copy that is using ffmpeg on the backend?