|
The .WTV files are HUGE, 2 gig for a half hour show, 3 gig for the hour long ones.
I use MC-TV Converter.
Yeah, I got the 530 also. Might be over my head. Deleted the ftp acct. for now.
There's no way that I know for me to chop the WTV into sections.
I will try tonight to convert to .ts and see what's what. TS had the same result
EDIT: Sorry, I didn't see that you guys wanted the project files. I'll get on that.
Added Packed and zipped - psd and the original mpeg
http://wismotorsports.net/download/project.zip
|
|
I already did the uninstall/install thing. Just applied 2405 Beta. Did a short (2.40 minutes) clip, 238 MB. At the end, using Media Player Classic, it ran on past the time, in silent mode, playing what was cut out. Then I fired it up in VLC, got to the end and locked up. Then, tried again in MPC, and it went silent and stopped, at 2:40. Weird. Win7 reports the time as 3:05.
http://wismotorsports.net/download/Produce.mpg
Addedacked and zipped - psd and the original mpeg
http://wismotorsports.net/download/project.zip
|
|
Define small? Seconds, or minutes?
|
|
29.970 for both.
It gets weirder.
If I view a sample 6 min cartoon I did in Media Player Classic, it plays fine, although the time is listed wrong.
Play it in VLC and I see the end, where it should have been cut it wasn't, but the sound is muted.
Media Info attached for the 6 minute vid
|
|
PD12 version 12.0.2230
SR VDE131028-01
Windows 7-64 Pro, fully updated.
Trying to edit TV recordings to edit out commercials, etc. WTV files, which I convert to mpg, using another program. If I try and use PD12 to "directly" edit WTV files, it creates a M2TS file, which I assume is the editable file, and the audio sync is off. Mostly 1080P recordings.
So, anyway, when I edit out what I don't want in the files, then PD12 gives me the option to use SVRT. I most definitely WANT to use it, as it is blinding fast. BUT, the resulting file is time coded wrong, and some cuts are mysteriously back in. By time coded wrong, I mean the length of the file is wrong. Should be 1:54:23, for example, shows actual time of 1:23:56. Then scroll in the produced file to the end, and some of what was cut from the end is there, with no sound. If I try and reload it to PD12, I can only go to the 1:23 mark, nothing after. Short of uploading a 2 hour 1080P file, it will be hard to reproduce.
Also, when producing, percentage done goes OVER 100%. It will go to around 106%.
Any ideas? My thought at this time is to do a format, rebuild. NOT what I want to do right now.
Also, I upgraded from PD10, thought maybe it was some hanger on from there. Uninstalled 10 and 12. Ran the CLCleaner program mentioned here, manually deleted ALL CyberLink folders, reinstalled 12.
|
|
Same problem here, sort of. Just refreshed my machine. Clean install, and now my preview is loooowwww resolution. For the life of me I can't figure what changed. I'll try the registry hack, worth a shot.
Nope, still low res.
Weird, it's only when I drop it to the timeline. In the media library all is good. Then I drag it down to the timeline, and the resolution drops.
Win7-64
AMD HD 6770
I-5 2500K
16 g memory. Terabytes of space
|
|
http://forum.imgburn.com/index.php?showtopic=6376
Much discussion on the imgburn forums. You will NOT like what you read here.
I personally would like to know what error burning gave you. I think most users here don't trust the burning aspect of PD10. Myself, I have no problems. But then I have a fairly new system.
|
|
Are you sure they are +R DL. If memory serves (and it's been years since I used imgburn) the layer split warning occurs with -R DL.
|
|
http://www.ngohq.com/news/19259-beware-of-driver-sweeper-on-windows-7-a.html
|
|
11.9 works, but from everything I have read, only a clean install will revert it properly. I'm just gonna wait for the next driver update, hopefully it will be fixed. It is seeming as though ALL apps are affected, so I imagine the volume level for a fix will increase
|
|
The latest AMD update "forked" it all up. Reverting to an older driver will NOT fix it. Apparently, some key in the registry is messed up and retained, even if you un-install the package. Someone else on here got it to work by doing a clean install of Win7 and sticking with the previous driver. So in a word, the rest of us wait. Maybe the next updated driver package will fix it. It's not just PD10, DVDFab also lost the AMD acceleration. But in my experience, YMMV, it's just as fast without it.
|
|
Thanks Shrek, I thought I was the only one...
|
|
For the OP Grant: In preferences, under Hardware Acceleration, in the lower right corner it will show what is available. For the Intel, I believe it is OpenCL, and there is a check box at the top for it. If you have a discreet card, say AMD or Nvidia, the appropriate icon would also show at the bottom.
|
|
If this belongs elsewhere, say so and I'll move it, or delete it. But, I see where some members don't use acceleration, I am guessing they feel it monkeys with the output? And, does anyone else have the AMD acceleration lost since the last driver update (1-28-12, or thereabouts)?
|
|
Don't know if this helps or not. I also have an I-5 with integrated graphics. My ripping software uses it for acceleration. But PD10 "seems" to ignore it, and goes for my AMD Graphics card. Which is fine, or was. Since the latest AMD Media Codec update, PD10 shows Hardware Acceleration "unavailable". I had thought PD10 would use the I-5 graphics to accelerate, but I can't seem to locate if there is a place to set that. That said, with the 64 bit engine, it is still screaming fast, without the acceleration.
|
|
I "think" I remember one of the regulars here saying that the download of PD10 is preferred over a boxed version. Is this correct, and why? Warming up the plastic....
|
|
Diverse opinion is always welcome. The day I start NOT learning something new is the first day of my death. Sorry if it came across as contentious. Cheers and New Years glee
|
|
I think you might be confusing the paging file with the temp variable. I still use a paging file, but it is hard coded to a specific size. Never changes. Once I upgrade from 8 to 16 gig, it will be gone. Period. As far as Windows not reporting drive space on the fly, I think I would need to see proof of that. Anyway, I have 2 gig free, on C:, and I don't think that would be enough. But in D:\temp, it is literally LITTERED with tmp files from PD, which I am very annoyed to report are NOT cleaned up after closing. I did see a setting about cleaning up after "X" amount of days. That would be acceptable, if PD used it's own folder, or at least one you could designate. I'll have to revisit that. And I will stand by my assertion, you CAN use a SSD, even a small one, if you manage your space efficiently. Running Win7 Pro, 64 G SSD, 2 gig free. Oh, and due too flooding in Thailand, still using my old 250 G for data storage. And temp files
|
|
Trying to edit and then convert some mpeg2 videos, captured from TV source, to mp4. The videos have 5.1, but I can't find an option in PD to Produce to mp4 using/keeping the 5.1. Is this not available?
|
|
Well, hate to shock you all I have no temp files on "C". All are successfully being created in the D:\temp folder. I did change PD to auto save to a folder on D: also. I ran the trial, edited a file (90 min HD mpeg2), exported as a PS3 compatible mp4, all while checking the "C" drive, and the available space never changed. So I am viewing this as a success! FWIW, maybe others could change their 'temp' variables to another drive to verify this. Oh, and "MyDocuments" is also ONLY on the "D" drive, so the cyberlink created subs in there ended up on the "D" also. I used the Location Mover tool for that. I do have a few more questions before I fully commit, but I will search the forums first, and then I will create a new post if needed. And it is the support by USERS here, along with the user add content on MyDirector that has leaned me heavily towards this product. Cl should give the active members here some bling or SOMEthing Oh, and did I mention how FAST this program runs? And yes, to all the people with troubles, I went out of my way to crash it. Couldn't do it. Yet
|