6.1.7.4 is awful on SPEED even on SD. DO NOT USE.

[MrGrackle]

Well, we are doomed. Just rollback with version 6.1.6.9. Unfortunately, you need to stick with version 6.1.7.4 but it's really really slow when it comes to MUXING. We will need to wait for a fix from streamfab.

I do understand this is a CAT and MOUSE game but hey, help!

Actually -- the processing and muxing is much faster on 6174, by a ton. I think you got something else going on there.

[quebecman]

Yes, speed is bad.
Most of my time is spent on Amazon lately with episodes of certain shows.
What I could do in prior versions was select 580p and not have to worry about long processing, but now no matter what resolution I pick it seems to go into processing long time.
For the shows which I maybe watch 2 times, 580 was fine.

Since they insist on doing the re-encoding and seems what we will be stuck with it, I agree with others we should be able to bypass and download as 580p without the long processing.
Like add a no re-encoding mode option check box or selection.
Also, it does seem they implemented a poor copy of clever get, although you can get things faster with that program, although they also have the same audio issue.

And like others I have no money to buy the 'other' program, and they are crazy taking bitcoin through PayPal of all places.

It's not the RE-ENCODE that is causing the issue but the software itself. I have an 7950x as CPU ans a big video card and even an SD is bad!

[NewMelle]

I don't have a hefty GPU, only a GTX 960 which is enough to handle the few legacy games I play twice a year and the processor is only an FX-6300 but it handles numerous instances of plugins in Reaper without breaking a sweat so it's all I need. If you compare apples to apples I didn't notice any speed improvements in 6.1.7.4 but now it takes twice as long to process even a low res video. If I compare apples to oranges (yes, I bought the orange as my apple is obviously spoiled) oranges takes half the time and at the specified audio settings I set.

I'm seeing a downward spiral here and have to agree with Chameleon in that it may never recover.

[KidJoe]

So you've got a $330 vid card, $400 processor and fiber i-net. Hooray for you! I'm sure the scum sucking suburbanites with fiber in town living so close together they rub asses would be quite impressed. Us dumb rural hicks in the middle of nowhere aren't good enough to run fiber to so we're stuck with ADSL, and barely that. Just not enough suckers in my neck of the woods to run fiber to..

Excuse the crap out of me for saying why it's possible I'm not seeing the same slowness as someone else is complaining about.

Wow.

I get your pissed at Fab. But I'm not Fab!!

I'm just a long time user, in the same boat as you, also angry they are still having DRM issues after all this time. And can't seem to fix Peacock and other bits. And trying to offer help if/when I can. I don't need to be here or try to contribute.

[NewMelle]

Well, then I may have taken it the wrong way then. I can't count how many times I've been told here and other places to upgrade to Win10/11 (I have a Win11 box, I just really don't like 10/11 so I seldom use it), your computer is too old, upgrade your GPU or upgrade CPU. I don't know how many times someone has rubbed their high end GamR machine in my face saying my rig is the problem even though the issue arose abruptly out of nowhere.

At best I get 9Mbs but usually around 8. I'm probably in the minority there. They WON'T run fiber down this road because there are no subdivisions on it, no big bucks to be made. 5 miles either way is fiber. Tried satellite which was a bad joke and they charged us $400 to tell them to FO. Here is single pair copper. Processing is what is eating the time, not necessarily downloads as I haven't noticed a huge difference and the longer processing is probably because I have an old GTX 960 GPU and an older FX-6300 CPU and some coders are coding for higher end hardware. However processing rarely eats more than 50% of the CPU. Now 6.1.7.4 is over processing 400x224 videos where the older versions did not. Download and done. SF more than met my needs with my current rig up until 01-25-24 and that's when things abruptly started going downhill and have been on a downward spiral since.

I used to work with a programmer named Loring. He was a real gem. One of those guys that is never wrong. Once he set up an Access database for an entire office to share. Yes, I said an entire office and I told him it would NOT work. At least 10 or 12 times a week or even more I was having to drive to the other side of the state to unlock the database. I would tell him time and again if you want to do that you'll want SQL. His reply was always "I've don't have a problem with it, you must be wrong." despite the fact he was the only person accessing his databases and my boss believed him. Until I quit and the boss had to go out there as many times a week. The boss apologized and begged me to come back. Fat chance. Maybe that's why my hocks go up every time I hear something like that.

Sorry I tied into you. I obviously took it the wrong way.

[Kattanders]

At best I get 9Mbs but usually around 8.

I don't have a high end machine either (CPU Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz) and only a 100Mbs broadband.
SF (Amazon) normally has a downstream of 12mbs. With the 6.1.7.4 downstream I got only 4 to 6 Mbs.
Processing time (encoding) around 40 minutes. Muxing seems similar.
As I could not download Project Peacemaker from Paramount+ Amazon Channel because of error 511 - tried it multiple times
with different source settings - I reverted to 6.1.7.3 and could download the video without problem (re-encoding mode of course)

Here are the required times for 1080p and 2 x audio tracks AAC with Version 6.1.7.3

Source file size: 2.13 gb (I had selected H.265)
Download started: 10:19
Proc stream file started: 10:22
Processing (encoding Video) started: 10:24
Processing Audio: 10:44
Muxing: 10:56
End: 10:58
Resulting file size: 2.6 gb

Source file size: 5.86 gb (I had selected H.264)
Download started: 11:22
Proc stream file started: 11:33
Processing (encoding Video) started: 11:38
Processing Audio: 12:03
Muxing: 12:15
End: 12:21
Resulting file size: 7.3 gb

As comparrison using hardware encoding (to H.265 which is even more resource hungry than coding H.264)
Converting to H.265/HEVC (Vidcoder with 2.300 average bitrate and Hardware Nvidia NVEC)
resulting Filesize: 2.21 gb
Duration: 16 min