I know today was your deadline, so I've been thinking a lot about how to help you.
I've never seen behavior like this from Waveform, and every time and of us (including you) applied a logical explanation, it proved not to be!
Glad you seem to have done a workaround--I can assure you that's going to happen to all of us at some point, no matter what products we use!
The good news is your setup seems to work just fine on your other projects, so let's hope this is just another one-off solution. For what it's worth, and I hope I'm not sounding patronizing because I mean it, but your screen shots earlier show a very clean, organized workflow and excellent discipline. This normally prevents weirdness, but this time...well, not sure what that was.
Please keep in touch in the event this problem comes back. I'm surprised none of the veterans here did their usual thing of "Eh, you need to check that obscure box in the properties window" and suddenly it all works.
(Edit: this was my 666th post. Hope that's not a bad sign!)
Rendered file goes mute after some time whereas playback works
-
- KVRAF
- 1595 posts since 9 Jan, 2018
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
I think, unless we are SURE of what is happening, we all hesitate to tick (or recommend) those obscure setting changes; because they can come back to haunt you!
However, there are a few common ones that really SHOULD be set (or unset) by default. Like:
1. Run audio engine while stopped. Not sure why you would NOT want to do that, and novices get confused.
2. Menu by default should INCLUDE the properties window. DON'T hide it by default! By the time you are comfortable
with Waveform, you THEN know if/how to hide.
Default install settings really should be set for the novice; to ease their pain. The rest of us have already struggled and figured it out. Plus, it's a one-time thing.
However, there are a few common ones that really SHOULD be set (or unset) by default. Like:
1. Run audio engine while stopped. Not sure why you would NOT want to do that, and novices get confused.
2. Menu by default should INCLUDE the properties window. DON'T hide it by default! By the time you are comfortable
with Waveform, you THEN know if/how to hide.
Default install settings really should be set for the novice; to ease their pain. The rest of us have already struggled and figured it out. Plus, it's a one-time thing.
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRAF
- 1595 posts since 9 Jan, 2018
100% agreed, Peter! And Scotofil definitely seems to have a solid workflow--so I doubt it's a settings issue. But I've seen many a Waveform user come into a bizarre situation like this and point out something totally simple and obvious that fixes the situation.
I have a sinking feeling that Scotofil will never identify what happened here, but it looks like a workaround met the project deadline. And if Peter didn't solve the problem, I don't feel like this was something I should have known!
I have a sinking feeling that Scotofil will never identify what happened here, but it looks like a workaround met the project deadline. And if Peter didn't solve the problem, I don't feel like this was something I should have known!
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
