Which Magewell device exactly?
Magewell Pro Dual Capture. Pro Capture Dual HDMI - Magewell
I ended up lucking out as the 2 port does not have the obnoxious fan (like the quad card).
This card is literally the Cadillac of capture cards - it just works on Ubuntu Linux. Black magic is a nightmare.
Bought a Magewall dual m.2 in 2018 for a ridiculous price. Never did get it to work for these DVR applications.
Is that the mini? Do you still have access to it?
I don't recall what I did with it, returned it or put it in the garage.
Do you have a link to where you purchased this?
I scored mine on ebay. They don't have stock left, unfortunately.
Well Amazon has 3 left... of course it costs $578 USD.
Look closely at buying options. There is one for $245 (Used-like new)
Totally worth 250 IMO if you can score one! It's been absolutely flawless.
EDIT: just keep in mind you will need a decent GPU for re-encoding. The device outputs raw by default which I was not able to ingest into Channels. Going to look at the SDK to see if the device output can be changed to mpeg2 by default and bypass ffmpeg.
For those using Fire devices to capture from there is a "Still Watching Setting" that needs to be turned off under Preferences > Data Usage Monitoring ... I was recording a marathon and the Screen went blank after hours of recording.
3 Likes
Do any of these ADB commands fix that?
adb -s %device% shell settings put global window_animation_scale 0
adb -s %device% shell settings put global transition_animation_scale 0
adb -s %device% shell settings put global animator_duration_scale 0
adb -s %device% shell settings put secure sleep_timeout 0
adb -s %device% shell settings put system screen_off_timeout 2147460000
If not, do you happened do know the adb command so I can add it to my pre-configuration script.
I had used your maintenance script previously on both my Fire devices, and I just went into Data Usage Monitoring, and both my Fire devices were still set to turn off after 4 hours if there's been no input from the remote.
1 Like
No they won't and I do not know the ADB command ... changed it manually.
And that fully takes care of the "are you still watching problem"? Is there an equivalent for other devices like shield and one?
That setting is on the fireOS level, I am pretty sure the liveTV streaming apps (Hulu Live, YTTV, etc.) have their own timeouts that are managed seperately.
Is anyone seeing random recordings that have a really long incorrect length, like 1,300 minutes? They're still somewhat playable but usually end up not working during playback.
I've seen two in the last week and I wonder if it has something to do with how the stream is being transferred from the device.
This is from a Uraytech HD encoder, firmware version is 2.06 using TS stream.
When I was using HDMI for Channels, I was constantly getting recordings that were too long or short - they were fixable by doing the "Fix Video Timestamps" operation manually when the recording was complete - now that I have moved over to the ADBTuner method, the recordings do not exhibit this problem - I think it has to do with the fact that there is a transition in resolution/frame rate when you see the no signal screen, then the splash screen, then finally the show - with ADBTuner, for some reason (faster tuning and the fact that the YTTV app does not exit) this doesn't happen
Tuning across network tuners, MacOS and also Linux with Magewell have not seen that. What is your setup?
2 Likes
What they should do is create a way to tune using the HDHomeRun APP and capture VIA HDMI built into channels DVR... I already do this using NEXTPVR backend in Channels. I already capture HBO and Showtime using the HDHomerun APP to HDMI.
1 Like