(Fixed) beta 4.13 encode fails (in windows beta!!!!) (fixed)

[mdrodge]

((((not sure how relevant this part is but as you may remember we removed the .net startup string from the config file)))) (((( also its windows build 18237 ))) ((( all my encodes are h.265 10bit )))

most of the encodes now fail. some take a long time to fail and some fail straight away one or two (out of 10) complete without issue

i'm trying turning the worker process off but it will be a couple of days before i have any results. ((=if i don't post below then assume that worked ))

[RandomEngy]

There's an issue with items queued in older versions losing the destination path. I'm going to fix it in the next beta.

[mdrodge]

That's not what's happening. It's a fresh que. They just fail now. Maybe it's a windows thing. I'm not sure how to find out what's going wrong. Some times they work and some times they don't.

It's like when I use to encode on my fx8350 and i had the overclock at 4.8ghz. It seemed stable but would randomly fail encodes (so it obviously wasn't truly stable) The difference is I've been running this hardware like this for over a year and what's changed is the windows build but this build seems way more stable then the last 4 builds so i have no idea what is happening or how to address it.

On Thu, 20 Sep 2018, 9:10 pm David Rickard, notifications@github.com wrote:

There's an issue with items queued in older versions losing the destination path. I'm going to fix it in the next beta.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RandomEngy/VidCoder/issues/401#issuecomment-423316428, or mute the thread https://github.com/notifications/unsubscribe-auth/APvVEgyzrwMBEGJzz-c0cua2mOjF-oVcks5uc_YegaJpZM4WyfqC .

[RandomEngy]

I'm going to need more information than "they just fail" to fix it. Do you see any errors in the encode logs?

[mdrodge]

I know bud. How do i get a log? 😎

On Thu, 20 Sep 2018, 10:25 pm David Rickard, notifications@github.com wrote:

I'm going to need more information than "they just fail" to fix it. Do you see any errors in the encode logs?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RandomEngy/VidCoder/issues/401#issuecomment-423338552, or mute the thread https://github.com/notifications/unsubscribe-auth/APvVEmYtIHN6HT9oSnUk82MpxCp7rJUKks5udAezgaJpZM4WyfqC .

[RandomEngy]

Right click on the completed item and click "View encode log"

[mdrodge]

Ok I'll get back to you when/if the next one fails. Thanks

On Thu, 20 Sep 2018, 10:36 pm David Rickard, notifications@github.com wrote:

Right click on the completed item and click "View encode log"

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RandomEngy/VidCoder/issues/401#issuecomment-423341685, or mute the thread https://github.com/notifications/unsubscribe-auth/APvVEvtdzEKlRw8nlY3Bgh--0RR72iyAks5udApQgaJpZM4WyfqC .

[mdrodge]

Maybe there is a connection or maybe not but somehow the reported cpu usage in task manager is off. I think it only reports how much the first task is using. So if i run 4 tasks it'll say 22% just like it did with one task but now the total reported by the system is 89% with no other tasks running. With 88% usage limit set in the vidcoder settings this usage sounds good. But in task manager next to vidcoder it's 22% even if i expand it to view the individual process worker's it still doesn't add up.

On Thu, 20 Sep 2018, 11:05 pm matthew drodge, mdrodge@gmail.com wrote:

Ok I'll get back to you when/if the next one fails. Thanks

On Thu, 20 Sep 2018, 10:36 pm David Rickard, notifications@github.com wrote:

Right click on the completed item and click "View encode log"

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RandomEngy/VidCoder/issues/401#issuecomment-423341685, or mute the thread https://github.com/notifications/unsubscribe-auth/APvVEvtdzEKlRw8nlY3Bgh--0RR72iyAks5udApQgaJpZM4WyfqC .

[mdrodge]

After a few hours the ui breaks and I'm unable to see the window. I run the app minimised. It's been running since before the last email was sent. I opened it up to check progress but the window will not appear. I had the same problem a day or two ago. This makes it hard to work out what's done vs failed also i can't address why it's failing.

On Thu, 20 Sep 2018, 11:27 pm matthew drodge, mdrodge@gmail.com wrote:

Maybe there is a connection or maybe not but somehow the reported cpu usage in task manager is off. I think it only reports how much the first task is using. So if i run 4 tasks it'll say 22% just like it did with one task but now the total reported by the system is 89% with no other tasks running. With 88% usage limit set in the vidcoder settings this usage sounds good. But in task manager next to vidcoder it's 22% even if i expand it to view the individual process worker's it still doesn't add up.

On Thu, 20 Sep 2018, 11:05 pm matthew drodge, mdrodge@gmail.com wrote:

Ok I'll get back to you when/if the next one fails. Thanks

On Thu, 20 Sep 2018, 10:36 pm David Rickard, notifications@github.com wrote:

Right click on the completed item and click "View encode log"

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RandomEngy/VidCoder/issues/401#issuecomment-423341685, or mute the thread https://github.com/notifications/unsubscribe-auth/APvVEvtdzEKlRw8nlY3Bgh--0RR72iyAks5udApQgaJpZM4WyfqC .

[RandomEngy]

Like it's blank, or just doesn't show at all? Not sure how to diagnose that bug.

[mdrodge]

Like it flashes up for a split second completely black then just vanishes. The preview from the start bar is also black.

On Fri, 21 Sep 2018, 4:55 am David Rickard, notifications@github.com wrote:

Like it's blank, or just doesn't show at all? Not sure how to diagnose that bug.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RandomEngy/VidCoder/issues/401#issuecomment-423405831, or mute the thread https://github.com/notifications/unsubscribe-auth/APvVElDc00s7pdyDsgNsKBqoKkpgkKU5ks5udGM-gaJpZM4WyfqC .

[RandomEngy]

It sounds like something is going wrong in the deeper system at that point. Like the WPF render engine has been corrupted. I'm not sure how I'd fix that. If you get some reliable steps to reproduce the issue I could maybe report it to the WPF team.

[mdrodge]

The steps to reproduce it are use the latest windows build. I appreciate that could prove a pain (the same reason I'm not just rolling back) (I seems to render every thing else just fine ((from 4k hdr video to games))

I'll just have to put up with the stable version of vidcoder until something changes.

Keep up the good work. Thanks for your time.

On Fri, 21 Sep 2018, 2:16 pm David Rickard, notifications@github.com wrote:

It sounds like something is going wrong in the deeper system at that point. Like the WPF render engine has been corrupted. I'm not sure how I'd fix that. If you get some reliable steps to reproduce the issue I could maybe report it to the WPF team.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RandomEngy/VidCoder/issues/401#issuecomment-423527223, or mute the thread https://github.com/notifications/unsubscribe-auth/APvVEgFLLISa9qt5ktKDT3Zk48Wpyf42ks5udOangaJpZM4WyfqC .

[RandomEngy]

So you just use the latest windows build and it happens? Do you also have to wait a few hours with it minimized? Does it happen when not minimized? Does it happen if the screen stays on? By latest build, you mean latest Windows Insider build, or latest stable? Narrowing it down could help fix it.

[mdrodge]

Ok these are good question it takes more than a few hours maybe 16. Minimised haven't tried not. I can't answer the rest of the questions. With each test taking a day.

On Fri, 21 Sep 2018, 11:54 pm David Rickard, notifications@github.com wrote:

So you just use the latest windows build and it happens? Do you also have to wait a few hours with it minimized? Does it happen when not minimized? Does it happen if the screen stays on? By latest build, you mean latest Windows Insider build, or latest stable? Narrowing it down could help fix it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RandomEngy/VidCoder/issues/401#issuecomment-423691465, or mute the thread https://github.com/notifications/unsubscribe-auth/APvVEug2oYY2w1WWdzjdvlWTLSZFksEGks5udW4vgaJpZM4WyfqC .

[mdrodge]

It looks like whatever it was has been patched in the new new build (18242) of windows anyway so i wouldn't waste any more time on it if i was you. I won't know %100 for a few days but the opening issue has disappeared.

Thanks for all your help. I'll leave you in peace now. 😁

On Sat, 22 Sep 2018, 8:07 am matthew drodge, mdrodge@gmail.com wrote:

Ok these are good question it takes more than a few hours maybe 16. Minimised haven't tried not. I can't answer the rest of the questions. With each test taking a day.

On Fri, 21 Sep 2018, 11:54 pm David Rickard, notifications@github.com wrote:

So you just use the latest windows build and it happens? Do you also have to wait a few hours with it minimized? Does it happen when not minimized? Does it happen if the screen stays on? By latest build, you mean latest Windows Insider build, or latest stable? Narrowing it down could help fix it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RandomEngy/VidCoder/issues/401#issuecomment-423691465, or mute the thread https://github.com/notifications/unsubscribe-auth/APvVEug2oYY2w1WWdzjdvlWTLSZFksEGks5udW4vgaJpZM4WyfqC .