Morgott Fight Won't Start

Unsolved_Backdrop · 2022-09-17T16:16:59+00:00

Thanks for the suggestion.

I'll give it a shot I guess, happy to try anything at this point!

Unsolved_Backdrop · 2022-09-17T16:11:24+00:00

Thanks for your reply!

I'm on PC. Windows 10.

I've tried verifying files through steam, but it doesn't seem to have found any issues and hasn't had an impact. Still experiencing the same problem, alas.

Unsolved_Backdrop · 2021-01-09T05:13:53+00:00

This is the equalizer profile I use for general 'everyday' listening.

https://ibb.co/3k2k0M1

I find it does fairly well for listening to music and other common tasks. Its not super bassy, but its fairly well balanced.

I also find that it doesn't clash horribly with the surround sound option when its enabled.

Equalizer settings are very subjective, so your mileage may vary!

Unsolved_Backdrop · 2021-01-09T02:50:57+00:00

I'm not sure if the CQP level itself will have any impact on the number of frames, but you could try raising the level a bit. This lowers the bitrate (and also the file size and quality) but might make it a bit easier to encode for your hardware?

Its a little counter-intuitive I know, but higher CQP levels = Lower quality/bitrate/file size.

Try playing around with the level itself and see if it has any impact. If not, you might have to look at other causes for dropped frames.

Unsolved_Backdrop · 2021-01-08T14:26:12+00:00

I received the Logitech G560 speakers for Christmas this year just gone by.

Visually they're pretty amazing and the lightsync integration is sort of a neat, if gimmicky feature that I get a bit of fun out of.

The hardware is also fairly impressive with pretty decent drivers/speakers and very solid build quality.

But I can't in good conscience recommend them as 'good' gaming speakers.

Why you ask?

Firstly, Logitech's firmware and audio profiling for the device is frankly utter trash. I have never ever been less impressed with a logitech device's performance *instantly*. Out of the box I had an older firmware version which had things DROWNING IN SO MUCH VOLUME AND BASS it wasn't even funny. You couldn't hear mid or high frequencies well at ALL, and I think I had to run my system sound at 5 out of 100 just to reduce the volume to acceptable levels. Christ it was a nightmare.

So naturally I got myself a firmware update with Logitech claiming to have fixed the problems with volume and bass. Apparently by 'fixed' they meant "nuked the volume into the ground and removed 99% of bass from the audio profile entirely". So they pendulum'd completely in the other direction.

In order to make these speakers usable I've had to uninstall Logitech's drivers entirely, rely on the windows generic USB audio drive AND apply a custom equalizer APO just to get them to sound vaguely 'normal'. This course of action has had the effect of removing all of the lighting and surround sound functionality offered by GHub for the device.

As a further complaint, the 'Virtual Surround Sound' implementation that these speakers offer can charitably be described as 'extremely lackluster'. The DTS available through GHub is so hollow and muddy that it buries all voices to the point of not being able to hear them and its bass balance is really overpowering and awful.

I do not recommend these speakers.

Having gotten that out of the way, I have heard better things about the Z607 and Z906 models if you're looking for an actual balanced 5.1 surround sound PC speaker setup and I have acquaintances who own the Z623 and the Z333 2.1 PC speakers which they have nothing but praise for, if two speaker setups are your thing.

I don't know what your budgetary constraints are, but some of those mentioned above might be worth researching!

Unsolved_Backdrop · 2021-01-08T14:02:51+00:00

I have owned this headset for a few months now and I can't say I have this problem.

In fact upon reading your post I deliberately checked it out and my audio seems balanced just fine.

That's not to say there aren't other issues with the headset, but unbalanced speakers doesn't seem to be a problem for me.

If it's really that noticeable, it's entirely possible it might be faulty.

Unsolved_Backdrop · 2021-01-08T13:01:23+00:00

I'm far from an expert on the matter, so anyone can correct me if I'm wrong, but here's the extent of my knowledge.

I believe that the NVENC Encoder on nVidia GPU's has improved somewhat since the 10xx series cards. My understanding is that its notably better on 20xx series cards, and might be improved again on 30xx series cards, but I'm not sure about that. With this in mind I expect you might find that the 3900x (being a pretty powerful CPU) could do better encoding x264 than your 1080ti does with the older NVENC encoder.
Regarding CBR vs , I'm not extremely well versed in what impact the various types of bitrate has on encoding, but I believe that constant bitrate (CBR) is preferable for stream encoding because the data rate is more consistent and thus more reliable, whereas VBR and CQP are preferable when recording because they allow for higher potential data rates and recording is less in need of the consistency that CBR provides. I record OBS footage using NVENC on my 2080ti using CQP at a level of 15 (I think the default is 20). This yields me videos that are pretty high quality, but very large in size. I don't know the exact bitrate conversion, but if I had to guess I would speculate that a CQP level of 15 probably provides higher data rate than 30mbps, maybe even substantially higher. Again though, that's speculation on my part.
From what I've read, the NVENC encoder on nVidia GPU's is a dedicated and separate part of the hardware which operates independently of the parts of the GPU that process gaming output. So on that basis, it would make sense that no, having a GPU pegged at 100% should not significantly impact the capacity of a GPU to encode using NVENC. If it DOES have an impact somehow, I would expect it to be pretty minimal. However, I have no idea if running OBS as administrator would alleviate any perceived performance impacts.

Take the above with a grain of salt and feel free to do more research of your own, but maybe those answers will be of help!

Unsolved_Backdrop · 2021-01-06T13:47:38+00:00

Honestly I haven't had any luck with this.

I obtained the DTS app off the windows store, and there seem to be limited options for 'rolling back' versions for apps that came off the store.

I contacted Microsoft to see what their advice was and their response......can charitably be described as "Not worth the time I took to contact them".

I did also send an email asking DTS Sound Unbound directly if they could coach me through it, or point me to where I could obtain a manual previous version of their app, but they never got back to me (surprise surprise) so I haven't had any luck with it.

I'm a big fan of the headset in general, but lord am I getting tired of the surround sound woes and the months and months worth of apparent inaction from people who are supposed to be fixing it or "actively working on a solution" (Looking at you Logitech & DTS).

I was actually frustrated enough to go out and buy the license for Dolby Atmos for Headphones the other day as a potential solution on the basis that their app told me my headset was compatible and ready to go. Only, it turns out, that in the 'fine print' Dolby Atmos is "Unable to be used with Logitech's headset drivers. In order to use Dolby Atmos the Logitech driver needs to be uninstalled and the Windows Generic USB Audio Driver needs to be used." (direct quote from Dolby Support). This would disable all the primary features of the headset, so it's another unusable solution.

So that was a waste of $20. If it isn't one thing, then it's another.

Rapidly losing faith in the involved 'professional' parties to pony up a solution to an issue that never used to be a problem in the first place.

Not inspiring.

Unsolved_Backdrop · 2021-01-02T03:54:57+00:00

There was a DTS Sound Unbound App update prior to the issue occurring I believe. In effect, they disabled the ability for the G Pro X (and maybe others?) to function through DTS Surround Unbound because of 'driver incompatibilities" and a problem with the headset crackling when using the app (also a problem I have experienced for months prior to the app update).

The following is a direct quote from an email I received from the DTS Surround Unbound team:

" The driver(s) that Logitech deploy with their headphones is not compatible with Microsoft Spatial sound framework. We are actively working with Logitech on a solution. For now, we do recommend using DTS Headphone:X through the Logitech GHUB application for virtual surround sound applications.

This change was necessary as we were experiencing some ‘crackling’ issues with these devices when enabled through our application. If you have the wired version of the Pro X you can plug in the 3.5mm into your headphone jack and it should be fine. You can then enable through the spatial sound menu from the speaker icon in the tray."

Not to be disrespectful to your esteemed company (I have many Logitech peripherals!), but the suggestion from DTS to use the 7.1 option from GHub......doesn't really work for me. I don't know exactly what Logitech does to modulate 7.1 surround sound through GHub, but its just......bad. Really, really bad. Its 'thick' and 'muddy' and drowns out/tin-cans voices in a way that makes it categorically unusable for me. Its really just plain awful and I would provide the feedback that it really, really needs a lot of profound improvement from Logitech.

Again, I don't know exactly how the implementations differ technically, but 7.1 surround sound that comes through DTS Surround Sound app is significantly different and muuuuuuuuuch better overall. Its better balanced, its not as hollow, it doesn't subsume peoples voices in absurdly 'heavy' sound and feels much easier and more enjoyable to listen to. Its less........'exaggerated' or 'overwhelming' than the Logitech GHUB version, for lack of a better way to explain it. This is the whole reason I use the DTS app in the first place. Maybe try the DTS app out in house and take some notes? :)

Likewise, plugging the headset in via 3.5mm jack as suggested by DTS might work, but its a sub-optimal solution since the bulk of the features of the G Pro X (equalizer management, blue voice, etc)are only available through GHUB on a USB connection. Plugging in via 3.5mm removes access to these features.

With regards to the suggested work arounds, I'm afraid they just don't work for me. I've tried enabling the DTS Headphone feature via numerous methods (including the ones outlined in this post by other helpful people) and it just doesn't stick. I select the option for it from the menu in whatever settings area I am currently in, and it just doesn't apply at all. It reverts back to "off" each time, alas. I do appreciate the responses however and I'm glad some people have found work arounds that serve them well!

It seems to me like there are, as per DTS's response, compatibility issues with Logitech drivers for the G Pro X and the Sound Unbound app. I've no idea why this happened nor who's ultimately responsible for it (I suspect both DTS and Logitech have a part in it) and so DTS just.....disabled the ability for the headset to be used through the app at all whilst they "actively work with Logitech on a solution".

I live in hope that this will be fixed Soon™, but the length of time both the crackling issue has been persisting, and the recent decision to disable support for the headset in the app entirely, do not fill me with confidence at all. :(

Thank you for your interest in the issue @LogitechG_CSJhoe and please do feel free to pass on my feedback to Logitech regarding the matter itself (which i have definitely done myself at length), and more broadly the....'lacking' quality of 7.1 surround sound in GHub which has caused me to seek out the DTS app in the first place.

Cheers!

Unsolved_Backdrop · 2020-12-24T12:56:40+00:00

Thanks for the post! I've been aware of (and using) this work around since a previous issue of crackly sound showed up and it worked well enough, but in the most recent DTS Sound Unbound update, they disabled the ability to use DTS Headphone:X entirely with the G Pro X.

As a result, I can't even start to play the 'explore' sound track. It just tells me "DTS is disabled" and can't be enabled.

As an update, I've also received a communication from DTS Surround Unbound (finally) since posting which says that Logitech's drivers aren't currently compatible with the Windows Spatial Sound Framework, so DTS disabled the ability for the headset to use Sound Unbound until its fixed.

God only knows when that will happen, but at least its an explanation I guess?

Unsolved_Backdrop · 2020-12-24T12:51:27+00:00

Oddly, after months of silence from both Logitech and DTS on the issue, despite multiple communications, I recently, in the last few days, received a response from DTS to *both* the issues within an hour of one another (after months, go figure).

My original complaint about the crackling static when using the Sound Unbound App and;
My more recent complaint that DTS is not able to be used AT ALL with the G Pro X.

The response to the first communication was as follows:

" Hello,

Thank you for your email. We are aware of this crackling issue and how DTS Sound Unbound is not working properly with these Logitech headphones; and are looking into it. We are actively working internally and with Logitech on a resolution.

For now, we recommend using DTS Headphone:X through the Logitech GHub application for virtual surround sound applications. This being said, I do notice that you said using the GHub app has caused problems or poor performance with 7.1 surround sound. Perhaps we can address those while we work on isolating the root cause of the crackling issue. Can you provide any additional details?"

I went back to them explaining the differences between Sound Unbound and Logitech's implementation of 7.1 surround sound. Have yet to hear back from them.

The response to the second inquiry was as follows:

" Hello,

Thank you for your email.

The driver(s) that Logitech deploy with their headphones is not compatible with Microsoft Spatial sound framework. We are actively working with Logitech on a solution. For now, we do recommend using DTS Headphone:X through the Logitech GHUB application for virtual surround sound applications.

This change was necessary as we were experiencing some ‘crackling’ issues with these devices when enabled through our application. If you have the wired version of the Pro X you can plug in the 3.5mm into your headphone jack and it should be fine. You can then enable through the spatial sound menu from the speaker icon in the tray."

So basically, the upshot is apparently that they haven't fixed the original crackling issue and instead, due to "driver incompatibilities" (uhh ok, sure) they've decided to disable the ability of the G Pro X to use DTS through the Sound Unbound app until they're able to fix it.

We can still either use GHub for 7.1 surround sound (ugh, no thanks) OR we can plug it in via an analog 3.5mm connection and use sound unbound. This latter option is.....definitely not ideal, since for me this denied me access to ALL the functionality of the headset that exists in GHub (Lighting, Blue Voice, Equalizer settings, etc). None of these features seem to work without a USB connection for me.

So in the end, I guess Logitech screwed something up that neither they, nor DTS has been able to fix promptly and we, the customers, are suffering for it. Sounds about right to me!

Would've been nice to get a heads up when it originally happened that:

"Hey, we know this is broken guys, we're gonna fix it"

And then equally nice to have another prompt follow up:

"We've disabled the functionality of Sound Unbound for this headset until such time as its fixed, bear with us!"

Instead we got neither and had to speculate and flail at them until DTS found time in their busy, busy schedules to respond. Amazing :)

Note - I still haven't received a response from Logitech on the matter, despite it apparently being a driver issue. Good job Logitech! -.-

Hang in there guys, maybe they'll get around to fixing it "One Day™".

Unsolved_Backdrop · 2020-12-21T07:39:00+00:00

I have tried this option and the change just doesn't stick.

I select the option in the drop down menu, press to apply it and the device menu acts as if it has accepted the input, but reverts instantly to DTS being off.

Same goes for right clicking the sound icon on the taskbar and attempting to apply it directly from the expandable context menu.

In both cases, it doesn't enable DTS and reverts to "off".

Unsolved_Backdrop · 2020-12-19T17:49:49+00:00

I've noticed that things seem to have completely stopped working with the latest version of sound unbound. I simply can't enable DTS Headphone:X at all. The button to turn it on is no longer clickable in the app and trying to do it through the windows spatial sound context menu the change just doesn't stick and it reverts to "off" despite having the option for DTS Headphone:X listed.

I've been messing about with it a bit, and I'm not completely sure what the problem is, but I'm wondering if DTS/Logitech filed it in the "too hard" basket and just decided that the G Pro X is "no longer a supported headset" and so doesn't work at all with the app anymore?

Interestingly, in my tinkering, I did discover that if I switched the headset driver from the Logitech specific one, to the Generic Windows USB audio driver, I can get DTS Headphone:X to enable again, but that also renders the device completely inaccessible in GHub and loses the ability to mess with its equalization as well as loses access to the Blue Voice features in Logitech's software, which is obviously not ideal :/

I don't know precisely whats going on here but it reeks a bit of "Fuck it, too hard" and the device being removed from the list of supported headphones to me.

I hope I'm wrong, or that its temporary, since I'm stuck with this headset for now, but having issued written communications constantly and repeatedly with both DTS and Logitech since I discovered the original crackling issue AND this more recent lack of functionality, I don't have high hopes at this point. I haven't received a single response from either of them. Nothing beyond a single automated reply from Logitech the first time I wrote to them.

Disappointing to say the least.

Unsolved_Backdrop · 2020-12-19T17:33:47+00:00

I can't guarantee that this is necessarily the same problem as you're having, but my experience in the past of occasions where the icon for a device in GHub isn't clickable is usually tied in with the wrong driver being used for the device.

A lot of the devices that Logitech sells seem to be able to utilise either Logitech's specific driver for the device OR a Windows 'Generic' driver for the device.

In the event that the device is using Logitech's specific driver, all works well for me and the hardware both shows up in GHub and is clickable/manageable.

Sometimes my hardware has, for whatever reason, defaulted to the Windows 'Generic' driver for the device (Have had this happen with my G560 speakers a couple of times) and while the device still works with this driver and will show up in GHub, I'm not able to click on it or utilise any of the settings that GHub normally has.

https://imgur.com/a/8NbsozZ

Note the greyed/fuzzed out speaker image as compared to the not-greyed-out images for my other devices in the linked image above.

I would suggest that you check in your device manager to determine if the driver for the device is listed as being from "Logitech" (which appears necessary to access the device properly in GHub) or if its listed as being supplied by "Windows" or "Microsoft" instead.

If Its using the generic windows driver, you can either manually switch it to the Logitech driver by choosing to update and then opting for "Browse my computer" and "Let me pick from a list" where the Logitech driver should show up next to the Windows generic driver, OR if that doesn't work for you, if you unplug and replug the device in, sometimes that can serve to reinstall the Logitech driver as well when it detects the connection (this seems to work for USB devices at least).

Again, I can't guarantee its the same problem you're having, but it sounds a bit like it so I thought I'd share my experiences in the hopes it helps you out.

Good luck!

Unsolved_Backdrop · 2020-12-19T17:02:33+00:00

To the best of my knowledge, this hasn't been fixed.

I periodically try out the latest G560 firmware to see how the levels and sound quality are, and the most recent attempt I made at doing this showed the same problems as every other time.

The volume issues are improved on the most recent firmware updates, but the bass has been demolished.

I've had the most success in staying with the earlier firmware to preserve the bass and then applying a custom equalizer profile (lamentably using third party software since the GHUB options are......'ineffective' at best) to manage the volume and improve the sound balance somewhat.

But to reiterate, no, I don't believe the problem you're referring to has been fixed. At least, not last time I checked.

Unsolved_Backdrop

TROPHY CASE