Complaint Amazon, Netflix... DRM-Fix

[Exxar]

They didn't. They uncompress the full resolution video, then re-encode it at the same resolution. I also assumed they were upscaling low resolution video, as the StreamFab reps have never explained it very well. Germania did in posts #40 and #44 of this thread:

https://forum.dvdfab.cn/forum/software-support-english/youtube-to-mp3-youtube-video-downloader/438278-hulu-location-bug?p=438821

It's not an ideal workaround, as the original video stream (and maybe audio stream?) is re-encoded, adding more compression artifacts. They re-encode as H.264, which can be done more quickly than H.265, but still takes a significant amount of computing time on your computer. StreamFab hasn't disclosed the encoding settings they use (e.g. preset, CRF) for the re-encode, but they probably have to sacrifice quality to get a reasonable encode time. Some have reported the program crashing or locking up during the re-encoding. I used it a few times to download season 7 episodes of Young Sheldon from Amazon. The results were satisfactory, but that's with current year video produced by digital cameras (hence low noise and easy to compress) and each episode only 20 minutes long. For the time being I'm using version 6.1.6.7.

Strange, because I've noticed when I select an episode (just tried it with that new Fallout series), I select the highest resolution (2.5GB file size), and if I immediately go to the download tab, I can see it analysing the video. And when it starts downloading, for just an instant, it shows it's downloading a 5XX MB file and then it jumps to a 2.5GB file.
The download is very quick too, like it would normally take to download a real 5XX MB file (nowhere near what it would take to download a 2.5GB file), and then it needs time to recode, and the result is a 2.5GB file.
So I really think it's downloading a low res video, and just rescaling it to an "HD" video.

[Cats4U]

Not even the latest release 2 days ago but 3/10 release and maybe the forked ffmpeg too. Wish they utilize the latest MKV merge instead of an older 68.0. I wouldn't say zero development since they may have incorporated them, but they still have to test and ensure the overall application/UI works as it should

What's stopping you from using the latest mkvmerge.exe? I changed that and other things with each SF update because they like to use old program versions. I've done it for about the last 2 years. Never had a problem caused by it. I'd love to update Python up to 3.12.3, but they have StreamFab hard-coded to use 3.8. Python 3.8 is set to be depreciated come October, if I'm not mistaken. They had to quick upgrade Python to 3.8 last year (after I told them about it) because 3.7 depreciated then. I don't know why they didn't upgrade to the latest Python at the time (which was 3.11.) They never bothered to remove the Python 3.7 directory from SF. Very sloppy coders. The source is probably all spaghetti. Could be the reason why it takes them so long to fix anything.

The following is my cheat sheet to remind me what programs to use and where to put them. I've done it so often that I really don't need the cheat sheet anymore.

Bin1 from latest shared BtbN nightly FFMPEG - Bin contents only
Bin2 from latest non-shared (static) BtbN nightly FFMPEG - ffmpeg.exe only
Main from latest MKVToolNix and MediaInfo - mkvmerge.exe and mediainfo.dll only
Tube from latest Arias2c and AtomicParsley - arias2c.exe and atomicparsley.exe only

Add Tube to C:\Program Files\DVDFab\StreamFab\YouTubeDL
Add Bin1 to C:\Program Files\DVDFab\StreamFab\YouTubeDL
Add Bin1 to C:\Program Files\DVDFab\StreamFab
Add Bin2 to C:\Program Files\DVDFab\StreamFab
Add Main to C:\Program Files\DVDFab\StreamFab
[* Do exact order shown *]

The only development they've ever done on ytdl.exe (YouTubeToMP3Process.exe) is that they use the source, add two SF-related commands (one being about a cache and the other I forget), recompile and name it YouTubeToMP3Process.exe.

[smithbrad]

The interesting thing is that in late January when the DRM change went into effect and StreamFab didn't have an update for it, we assumed it was because they didn't take it seriously enough and were late to the game. Especially, when the competition came out with a fix. However, 2.5 months later with no fix in place that assumption doesn't necessarily carry any weight anymore. The truth is they could have started working on it back in November, like the competition supposedly did, and it still wouldn't have mattered because whether it be 2.5 months or 5 months, they've shown no indication that they can resolve it.

I've only been using StreamFab for 14 months, but I feel I used it pretty heavily during that time and got my money's worth. If they can't fix Amazon, then I hope they at least manage to keep some of the other streaming services working well enough so I can at least pull some other titles from time to time. I'd go with the competition to support Amazon, but I'm not into paying with crypto currency, so they will need to fix their ability to pay using other methods. I do, however, feel bad for those that dropped a bunch on StreamFab and haven't been able to reap enough benefits yet. Like "Chameleon", I'm starting to believe this is a crippled product that will never again be what it once was.

[fabuloustream]

6.1.7.2 is a fraud, for the most part. The lines highlighted in blue in the changelog are the result of simply installing the latest version of ytdl.exe (renamed YouTubeToMP3Process.exe in SF). They did zero development themselves, but are taking full credit for the hard work in adding more sites that the YTDL developers did.

Not even the latest release 2 days ago but 3/10 release and maybe the forked ffmpeg too. Wish they utilize the latest MKV merge instead of an older 68.0. I wouldn't say zero development since they may have incorporated them but they still have to test and ensure the overall application/UI works as it should

[Chameleon]

The whole program is made up of other developers' hard work, from YTDL to both MKV programs and others.

[NewMelle]

Until the release notes CLEARLY state the DRM issues have been addressed I'm not going to waste the the time to uninstall and reinstall. I spent far too much time troubleshooting something that is undeniably broken and likely unrecoverable. I still use SF for episodic TV since it offers more options and I rarely go beyond 480p for that. Star Trek Discovery and Star Trek Strange New Worlds being the exceptions. For that and Amazon movies I've moved on. At least until those guys get their balls caught in a vise anyway. I'm sticking with 6.1.6.7 as well.

[Cats4U]

6.1.7.2 is out. No mention of Amazon or Netflix, but they have fixes and features for others.

I don't care as much about these fixes and features, *IF* they have a TEAM of developers, some of whom are not dedicated to the DRM issues. BUT from the past discussions, that appears to not be the case.

DRM for Amazon and Netflix needs to be their TOP priority. Put everything else, even "quick to fix" bugs to the back burner until this is fixed.

6.1.7.2 is a fraud, for the most part. The lines highlighted in blue in the changelog are the result of simply installing the latest version of ytdl.exe (renamed YouTubeToMP3Process.exe in SF). They did zero development themselves, but are taking full credit for the hard work in adding more sites that the YTDL developers did.

[JeffDavis]

I find it very interesting they decided to recode low res video to low res video in 1080p

They didn't. They uncompress the full resolution video, then re-encode it at the same resolution. I also assumed they were upscaling low resolution video, as the StreamFab reps have never explained it very well. Germania did in posts #40 and #44 of this thread:

https://forum.dvdfab.cn/forum/software-support-english/youtube-to-mp3-youtube-video-downloader/438278-hulu-location-bug?p=438821

It's not an ideal workaround, as the original video stream (and maybe audio stream?) is re-encoded, adding more compression artifacts. They re-encode as H.264, which can be done more quickly than H.265, but still takes a significant amount of computing time on your computer. StreamFab hasn't disclosed the encoding settings they use (e.g. preset, CRF) for the re-encode, but they probably have to sacrifice quality to get a reasonable encode time. Some have reported the program crashing or locking up during the re-encoding. I used it a few times to download season 7 episodes of Young Sheldon from Amazon. The results were satisfactory, but that's with current year video produced by digital cameras (hence low noise and easy to compress) and each episode only 20 minutes long. For the time being I'm using version 6.1.6.7.

[Air]

Its over with SF. It would be a miracle if it worked again the way it should. Better look for alternatives.

[Chameleon]

I am giving odds it will take years, if ever. This program is kaput.

[fabuloustream]

With it being almost 2.5 months since the DRM change and no adequate solution for two of the top streaming sites, it seems logical, to me at least, that it isn't a prioritization issue. We've gone from a period of no solution to a hack re-encode solution to working on other issues.

To me, this indicates that they just don't currently have the needed expertise in-house. Otherwise, they would have done what most have asked and forged through it until completed, and not done these interim steps. Which means they either need to:
(1) find the necessary expertise,
(2) buy a solution (if that is an option), or
(3) another viable option to the DRM issue
(4) assume their current stance and hope they don't lose too many customers.

Regardless of which of the above, they need to try to keep the lights on as best as possibly, which seems to be their approach, by using what resources they have to solve what problems they can. All we can do is hope they are working on a plan for 1-3.

I agree with this. While other users want developer(s) to focus only on the DRM issue, I prefer the latter. They would have a list of issues/enhancements etc and would prioritize and weight each whether if it was quick win-win or item that requires more time. They would have already been testing internally for days and validate if it fixes the issue or provide a workaround that make the cut to be release. This is just how the software development is with some dependencies whether they find a solution in house or relies on others. If the developer just focus on DRM, we will not have any releases in between and that would piss off more users or give the impression that they aren't trying to fix other modules meanwhile. If you look at DRM as a whole, this doesn't only affect this but others as well or even from popular scene groups this year.

I welcome the new release with added support to select video and audio for other modules, a step to standardize all the modules similar to Amazon module.

[smithbrad]

With it being almost 2.5 months since the DRM change and no adequate solution for two of the top streaming sites, it seems logical, to me at least, that it isn't a prioritization issue. We've gone from a period of no solution to a hack re-encode solution to working on other issues.

To me, this indicates that they just don't currently have the needed expertise in-house. Otherwise, they would have done what most have asked and forged through it until completed, and not done these interim steps. Which means they either need to:
(1) find the necessary expertise,
(2) buy a solution (if that is an option), or
(3) another viable option to the DRM issue
(4) assume their current stance and hope they don't lose too many customers.

Regardless of which of the above, they need to try to keep the lights on as best as possibly, which seems to be their approach, by using what resources they have to solve what problems they can. All we can do is hope they are working on a plan for 1-3.

[KidJoe]

6.1.7.2 is out. No mention of Amazon or Netflix, but they have fixes and features for others.

I don't care as much about these fixes and features, *IF* they have a TEAM of developers, some of whom are not dedicated to the DRM issues. BUT from the past discussions, that appears to not be the case.

DRM for Amazon and Netflix needs to be their TOP priority. Put everything else, even "quick to fix" bugs to the back burner until this is fixed.

[NewMelle]

Maybe if they refunded a token amount per week until it's fixed so we at least know they are working on it and interested in fixing it, like even $2 per week

I think it's high time to hold the dev's paycheck until he/she/they fix the problems.

It's more likely you'd pull crocodile teeth with tweezers.

[Exxar]

I find it very interesting they decided to recode low res video to low res video in 1080p. For what? It only takes longer now to download a video. Communication is key in a situation like this, and that is lacking. A lot!


And how come Streamfab isn't working for Amazon? The competition fixed that months ago!


I think it's high time to hold the dev's paycheck until he/she/they fix the problems.