Zprocess and 1.3.11

[grits]

I can't get Zprocess/Ztranscode working since the upgrade to 1.3.11. I've tried the last stable, and the pre-release. I've toggled to "interact with desktop" off and on again. I'm currently testing zprocess 2.0.341 and ztranscode 2.1.301 with an avi file. It doesn't work on the pc or the MVP. Could you list a step by step of completely removing and then reinstalling the latest version? Thanks.

[grits]

I've attached the only logs I found. This was from running zprocess on the pc.

[zehd]

I can't get Zprocess/Ztranscode working since the upgrade to 1.3.11. I've tried the last stable, and the pre-release. I've toggled to "interact with desktop" off and on again. I'm currently testing zprocess 2.0.341 and ztranscode 2.1.301 with an avi file. It doesn't work on the pc or the MVP. Could you list a step by step of completely removing and then reinstalling the latest version? Thanks.

Regardless of the service set to Interact, it should all work manually, where it does not involve GB-PVR at all...

Manually, I would start ZTranscode, load a file and click 'start'. Click View Output to confirm the video is being created and is viewable. If not, then don't bother with anything GB-PVR... you have to fix this.

Most likely, you are not using the defaults, or not using the correct versions of transcoder. Really - even on a slow machine, you should get something -- it just might not be fast enough.

To get to this point it doesn't matter if it is installed in GB-PVR correctly...

Uninstall

Start ZProcess2.exe, click GB-PVR Settings, Click Remove Refs, Close ZProcess.

Run RemoveAllZProcess.reg

That's it...

Certainly it seems like MEncoder is not firing correctly. I noticed this in your logs...

From the Transcode log, in the header...
Yours:

Code:

MEncoder 1.0rc2-4.2.1 (C) 2000-2007 MPlayer Team
CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (Family: 15, Model: 2, Stepping: 7)
CPUflags: Type: 15 MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.

Mine:

Code:

MEncoder 1.0rc2-4.2.1 (C) 2000-2007 MPlayer Team
CPU: AMD Sempron(tm) Processor 3100+ (Family: 15, Model: 44, Stepping: 2)
CPUflags: Type: 15 MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.

I don't believe that the difference in processor is the problem. What I see is that the 3DNow flags are marked 0 for you and 1 for me. I have no idea but it might be that the suggested build of MEncoder is having trouble with your processor.

If you wish to try a different version of MEncoder, maybe RC1:
http://www3.mplayerhq.hu/MPlayer/releases/win32/

I'd like to see what flags you see....

Mine:

Code:

MEncoder 1.0rc1-3.4.2 (C) 2000-2006 MPlayer Team
CPU: AMD Sempron(tm) Processor 3100+ (Family: 15, Model: 44, Stepping: 2)
CPUflags: Type: 15 MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 0 SSE2: 0
Compiled with runtime CPU detection.

BTW, You can have different directories for your MEncoders versions. You just swicth directories in the config |Paths sub form...

----

Remember, I'm grasping at straws here. I'd like confirmation from other people with a P4 chip and 3Dnow:0 and ZProcess Manually transcoding...

[grits]

I uninstalled, reinstalled, then ran ztranscode. The first time I did this I got a dialog box that said "53 File not found" with an OK button. When I run ztranscode it hangs and does not produce an output. When I remove the latest pre version, and reinstall the last stable version, ztranscode runs fine. Attached is the latest transcode.log

[grits]

When I run it through the MVP with the last stable 2.0.278, it starts but then chokes and sends me back to the list of videos. The transcode.log for the test through the MVP is also attached.

[zehd]

I'm sorry for the confusion. The reason the Transcode log is almost useless, is that it won't show why the transcoder chokes. (It's the transcoder (MEncoder/FFmpeg) that is choking, not ZProcess.

When using 278, the logs I need are all over the place. Many (including the ZProcess2.log and fps.log) are located in your [Recordings directory]/MVP_Cache folder

Within the App's folder is a few other logs, transcode.log, dimensions.info, RunTranscode.cmd, ZERITECH_RegSettings.txt

The latest Prerelease, copies all the important logs into the [App]/Logs folder. It makes it easier to zip and send everything...

Don't bother trying anything with the MVP until ZTranscode is running properly manually.

Sorry for the 53 error. I can't quite track it, but I don't think it happens when working with the MVP, and only during first run of ZProcess/ZTranscode. It resumes, and doesn't seem to cause any other trouble, so I would ignore it.

---

Now, I prefer you troubleshoot with only the latest prerelease. There's lots of fixes and enhancements. Yes, maybe bugs too, but working pretty good. I don't believe your are experiencing a bug though....

I would suggest removing references to ZProcess so that when you try viewing a non mpeg with the mv, only the default ffmpeg will run. And BTW, does it run?

Try unchecking 'Lock to MVPScreenPosition' in the Trans2MVP profile. (Remember to save)

[grits]

Yes, when I remove all references to zprocess, the avi runs through the MVP, but really big, hence why I would like to get this to work. OK, I deleted everything and installed the prerelease. zipped logs folder attached from just trying to run zprocess on the pc. It doesn't. In fact, when I click View input it doesn't even do that. Just for reference, the last stable zprocess did work. I haven't changed anything and the prerelease doesn't. I'll try the Mplayer rc1 version next.

[grits]

OK, I have it working now. I unchecked "Lock to MVP position", and ztranscode ran from the PC. Then I tried running it through the MVP and it worked perfectly. Hope this info helps. Do you want the logs from my successful runs?

[zehd]

OK, I have it working now. I unchecked "Lock to MVP position", and ztranscode ran from the PC. Then I tried running it through the MVP and it worked perfectly. Hope this info helps. Do you want the logs from my successful runs?

No we're good. Definitely found the issue. I'll have to make the fix stick... and release it. Thanks for your patience