This forum is for users to exchange information and discuss with other users about a TMPGEnc product.
In case you need official support, please contact TMPG Inc.
Pegasys Products BBS [ Sorted by thread creation date ]
I recently upgraded my laptop from Vista to Windows 7 and have to convert (via right click) the new Windows Media Center .wtv files to the old .dvr-ms format. TAW4 reads the resulting files, but the processing time for a 100 minute video is now over 2 hours. Before the upgrade, using the native dvr-ms files, TAW4 would go through a 100-minute video in 10-20 minutes. I have done this with about half-a-dozen converted wtv files, all with the same results. TAW4 is working normally with other file fomats, i.e. mpg and avi. Thanks for whatever help you can provide.
Here's the answer to my problem: my Hauppauge HVR-950 was not configured correctly for Windows 7. I had installed the standalone driver file, emp_voydrv_26322_27230.zip, but this was not sufficient. It was not until I installed the WinTV driver and WinTV v6 application update cd_4.8a.zip that the device started recording correctly. Both of these files can be found at the Hauppauge support page for this product: http://www.hauppauge.com/site/support/support_hvr950.html
Now TAW4 processes the converted dvr-ms files just fine.
Hi,
I'm using TMPG Express 4 for encoding movies to DivX-format for playing them on XBMC on my xbox. I just found out that the audio is scrambled (stuttering) when played.
Are there any settings that I can change to make the audio compatible with my XBMC?
It will not re-encode MPEG video as long as it's compliant with the DVD-video specs. I don't have a vob file handy right now, but I'm sure it will also not be re-encoded since vob files are just containers for MPEG video.
The Smart Rendering feature, as they call it, also applies to making Blu-ray and DivX projects.
I am interested in knowing whether TMPGEnc Authoring Works4 will allow for AC3 5.1 audio track present in the source input file be maintained in the divx authored project. I purchased Divx Author 1.5 from Divx site which is powered by pegasys before TMPGEnc released it seperately on their own. I have TMPGEnc DVD Author 2.0 and would like to upgrade to TMPGEnc Authoring Works 4. Currently Divx Convertor by DIVX allows maintaining AC3 5.1 Audio tracks and would like to be sure I can have 5.1 Channel AC3 Audio in my Divx menu based projects I create for my Divx Ultra certified DVD player.
I've been using TMPGEnc DVD Author since version 1.5. I recently upgraded to version 4 and found some difficulty in creating menus. I want a single still-picture menu that has links to play each track. I have 5 separate tracks.
By going through the Menu Wizard, I can only create a title menu that has a link to the track menu. And the track menu has the links to each track. Is there a way for me to delete the track menu and move the track links to the title menu?
Say I have an AVI that has a 16:9 movie on a 4:3 format. I would like to re-size it to fill the 16:9 space, eliminating the two black bars at the top and bottom, once it is imported in a track.
You can set various sizes in clip properties, but this would be a custom size.
I have a question, maybe a stupid one, but I am trying to use TMPGE 4 ex to convert this type of file ... E56.091201.HDTV.H264.450p-Angel.avi to a DVD standard, for i do not have blueray disc player. These files will play on my computer, but 4 express just hangs up, forever if I let it. Is this conversion not possible? I am running Win XP SP2 , on an AMD Atholon 2800 2.08 Ghz, and 2 GB ram. I know its old , any help or suggestions would be appreciated
After obtaining my license, just before the program starts I get the following consecutive errors:
Read error occurred at address 0BD9B805 of module 'UtilsCUDA.vme' with 00000000
Runtime error 204 at 0B842A2C
Runtime error 204 at 0B632A54
Runtime error 204 at 08982A2C
Runtime error 204 at 08982A7C
Runtime error 204 at 07972A18
Runtime error 204 at 07342A20
My computer is DELL XPS M1330 with NVIDIA 8400M GS, with latest drivers 195.62 (supporting CUDA 3.0)
Can you please check what is going wrong? Used to work ok with Vista 64bit and Windows 7 64bit with previous NVIDIA drivers...
I am the CUSTOMER and I demand YOU get in touch with NVIDIA to inform them that TMPGEnc does NOT work anymore with their latest driver series (which they incorporate CUDA 3.0 technology).
This forum is just users helping users; you won't get an official support response here. You need to use their support form to get in contact with a real support rep: http://tmpgenc.pegasys-inc.com/en/support/support.html
If I recall correctly, there's a problem with 4.0 XPress working with CUDA driver version 195. I think they'll recommend going with version 191 or earlier until a fix is released.
It happens to me as well. It is definitely caused by the new nVidia drivers. I've logged a bug report with the Technical Support. It's a bit odd that this new version they released yesterday didn't fix it yet. I was hoping it would.
even if i was from tmpgenc i can assure you that attitude and demanding them to sort it out, gets cusotmers naff all.
and from my experince with my clients and friends, those runtime errors happen when a kegen is used and is not a current one, when this is done and the user goes to open the software the message comes up, and at times the licence details come up.
how ever I am not in anyway statign this is the same case for you.
Ok, people, I've got a response from Pegasys by saying that their current TMPGEnc Xpress application is not compatible with the newest release of nVidia drivers (i.e. 195), because nVidia introduced a new version of CUDA (i.e. 3.0). People have only two options. They can either downgrade to the 191 version of nVidia drivers if they use CUDA capability or disable UtilsCUDA file in TMPGCEnc Xpress folder by renaming it.
I'm surprised though how Pegasys is so slow in updating their SW to follow CUDA evolution. nVidia announced the new version and released the development tools for a long time (at least since the middle of last year) and Pegasys didn't bother to update their SW to match it. Very sloppy, I must say.