View Full Version : CoreCodec/H.264 Codec "CoreAVC"
bob0r
31st August 2008, 13:37
try 177.83
Did. same result.
Or install lastest PowerDVD 8 build 2018
Think i have?
http://www.cyberlink.com/multi/download/dl_patch_623_1_ENU.html
CyberLink.2021U_DVD080729-02(Ultra).exe or is there any newer?
Sorry for being off topic, but it seems i am the only one with this problem??
Edit:
I guess this issue could be split to here: http://forum.doom9.org/forumdisplay.php?f=15
BetaBoy
31st August 2008, 15:38
Thx for the feedback all! We are gonna let the debate go on for the moment and get 1.8 out the door. So with that, below is the changelog for CoreAVC 1.8. We will be releasing CoreAVC Standard and Professional Editions for now.
CoreAVC H.264 Video Codec - Version 1.8.0.0 (20080831)
- Add: About tab
- Add: Help tab (describing filter options)
- Add: Picture levels adjustment tab
- Add: System Tray icon
- Add: Support for AVC Lossless 4:2:0 (officially)
- Add: Support for new standard aspect ratios
- Fix: Rearranged options tab
- Fix: Renamed Blend deinterlace to Single Field
- Fix: Fix Bob deinterlacing with Matroska files
- Fix: Fixed Aggressive Deinterlace function
- Fix: Better recovery point handling
- Fix: Improved filter stability (lots of changes)
On CoreAVC 64.... its done as well, however Haali still need to do work on the 64 bit splitter. A 64 bit version of 'Time Codec' is done however, but we won't release that till the splitter is as well.
So this begs the question... release CoreAVC 64 with the 32 bit splitter? Thoughts?
cyberbeing
31st August 2008, 18:13
Is the 64bit splitter going to be free and posted on Haali's site (http://haali.cs.msu.ru/mkv/) or is it only going to be bundled with CoreAVC and require registration or something?
If it's the former then I wouldn't see any issue with releasing CoreAVC 64bit with the 32bit splitter as long as it works considering that someone could easily grab the 64bit splitter when it's released. If it's the latter and the splitter isn't going to be freely available then I think you should wait and release them together.
amango
31st August 2008, 19:13
Question: Do I need a 64 Bit-application to use the 64 Bit-edition of CoreAVC ?
For example, Mediaportal is only available in 32 Bit. Do I have to use the 32 Bit-version of CoreAVC or can I use the 64 Bit-version? (I have Vista x64).
BetaBoy
31st August 2008, 19:16
Haali's splitter has always been free... nothing is gonna change that (Also if you did not know Haali is one of the lead CoreAVC Filter developers). To take advantage of 64bit everything should be 64bit within the playback chain. IE: codec, splitter, player.
ChronoCross
31st August 2008, 19:47
Haali's splitter has always been free... nothing is gonna change that (Also if you did not know Haali is one of the lead CoreAVC Filter developers). To take advantage of 64bit everything should be 64bit within the playback chain. IE: codec, splitter, player.
I thought you couldn't connect a 64 bit app to a 32-bit app. Isn't that the reason you need to use 64-bit filters with avisynth 64-bit? or 64-bit apps with megui 64-bit?
cyberbeing
31st August 2008, 19:50
I knew you had hired Haali awhile back but I thought he was only dealing with splitter and possibly player issues but not the CoreAVC decoder itself.
I'm assuming you probably have access to an alpha 64bit splitter. Is there a noticeable performance hit between the 32bit and 64bit splitter? Are the 32bit Haali splitter and 64bit decoder fully compatible and stable with each other? How does it behave with say the 64bit Gabest (granted I far prefer Haali's) MKV splitter which can be found via the MPC-HC project?
Also how much time are you talking about for the 64bit splitter to be ready? 1 month? 3 months? 6 months? 1 year? More/Less?
If you released CoreAVC 1.8 64bit now, would you be able to release CoreAVC 1.8.1 with some sort of minor feature addition or bugfix by the time the 64bit splitter is ready?
Emilot
31st August 2008, 20:42
Thx for the feedback all! We are gonna let the debate go on for the moment and get 1.8 out the door. So with that, below is the changelog for CoreAVC 1.8. We will be releasing CoreAVC Standard and Professional Editions for now.
On CoreAVC 64.... its done as well, however Haali still need to do work on the 64 bit splitter. A 64 bit version of 'Time Codec' is done however, but we won't release that till the splitter is as well.
So this begs the question... release CoreAVC 64 with the 32 bit splitter? Thoughts?
So, where can we download it???:thanks:
kemuri-_9
31st August 2008, 21:00
I thought you couldn't connect a 64 bit app to a 32-bit app. Isn't that the reason you need to use 64-bit filters with avisynth 64-bit? or 64-bit apps with megui 64-bit?
that's right, windows doesn't allow cross talk between 32bit and 64bit apps unless you actually do bistream piping between them.
i use MPC-HC x64, so i could see some coreavc x64 usage by adding it as an external filter.
clsid
31st August 2008, 21:14
i use MPC-HC x64, so i could see some coreavc x64 usage by adding it as an external filter.MPC-HC can use external filters without the need to explicitly add them in the options. Simply disabling the internal decoder is enough.
Is there a noticeable performance hit between the 32bit and 64bit splitter?The splitter uses very little resources. So performance is a non-issue.
If you released CoreAVC 1.8 64bit now, would you be able to release CoreAVC 1.8.1 with some sort of minor feature addition or bugfix by the time the 64bit splitter is ready?No need for that. CoreAVC and Haali Media Splitter are two separate items.
BetaBoy
31st August 2008, 21:14
Correct... was just talking with the guys here and they confirmed it as well. So I'll ping Haali on his 64 bit version.
cyberbeing
1st September 2008, 07:00
Is there a noticeable performance hit between the 32bit and 64bit splitter?The splitter uses very little resources. So performance is a non-issue.I assumed this to be the case but I forgot that you had to use a 64bit splitter with the 64bit decoder so my question was kind of pointless.
If you released CoreAVC 1.8 64bit now, would you be able to release CoreAVC 1.8.1 with some sort of minor feature addition or bugfix by the time the 64bit splitter is ready?
No need for that. CoreAVC and Haali Media Splitter are two separate items.
Well the point was that CoreCodec bundles Haali Splitter with the installer for ease of use and it goes back to the question of whether it makes sense to release CoreAVC 64bit now or wait for Haali's 64bit splitter. If they released it without Haali's 64bit splitter then it likely wouldn't get bundled with the installer until the release of CoreAVC 1.8.1 and less tech savvy people might not realize how to get Haali's splitter by itself and blame CoreCodec for any splitter or lack-of-splitter issues they are having.
Now if they could have 1.8.1 ready by the time Haali's 64bit splitter is ready then it would probably make sense just to wait and release CoreAVC 64bit then. If Haali's 64bit splitter would be ready in the next month or so it would also make sense to probably just wait and release CoreAVC 1.8 64bit then. If the wait is longer then that and 1.8.1 in nowhere in sight, then it wouldn't really make sense to delay CoreAVC 64bit any longer.
BlackSun
1st September 2008, 10:15
We are proud to announce that we are sending emails containing your personal download link for the new CoreAVC 1.8! I am updating the trial version in about five minutes.
Changelog:
- Add: About tab
- Add: Help tab (describing filter options)
- Add: Picture levels adjustment tab
- Add: System Tray icon
- Add: Support for AVC Lossless 4:2:0
- Add: Support for new standard aspect ratios
- Fix: Rearranged options tab
- Fix: Renamed Blend deinterlace to Single Field
- Fix: Fix Bob deinterlacing with Matroska files
- Fix: Fixed Aggressive Deinterlace function
- Fix: Better recovery point handling
- Fix: Improved filter stability
bob0r
1st September 2008, 14:52
Issue for 2.0 or 1.8.1:
[02:01] * jarod wonders...
[02:01] (jarod): why Some.Video.HDTV-x264-2008 Framerate..[ 59.940 fps ]
[02:01] (jarod): drops so many frames in MPC, while CPU is not even feeling it
[02:01] (jarod): 15% usage
[02:02] (jarod): sounds like a bug to me
[02:27] (ChronoCross): ffdshow results?
[02:27] (ChronoCross): any stutter?
[15:44] (jarod): ffdshow does the same
[15:44] (jarod): drop frames, and ofcourse not use all cores
[15:45] (jarod): this is a serious coreavc bug
Most frames are dropped when the buttom menu in MPC is opened by mouse over, or when i switch to fullscreen and back.
So this could be some serious Windows and/or DirectShow bug aswell, maybe we need a work around.
Fact remains: CPU is hardly doing anything, and its still dropping frames.
This video is 1280x720, the same issue i reported before to BlackSun with World in Conflict Nuke (1080p60).mkv, i figured that was just too much, but it seems its a general bug with 50+ frames?
CruNcher
1st September 2008, 15:19
do you experience any dropouts in the Exclusive VMR9 Rendering Mode (this should prevent any GUI stuff interfering on XP) ?
tough the droping when caling GUI stuff in XP seems absolutely normal i also experience that guess one thing that has been fixed in Vista ;)
CiNcH
1st September 2008, 15:24
This video is 1280x720, the same issue i reported before to BlackSun with World in Conflict Nuke (1080p60).mkv, i figured that was just too much, but it seems its a general bug with 50+ frames?
When I tested the trial back at the Euro 2008 I also noticed frame drops with 720p50 ORF 1 HD. But most of the time the glitches were not very well visible.
D.A.S.
1st September 2008, 15:52
- Add: System Tray icon
Add: Show tray icon.
Value - yes:no
BetaBoy
1st September 2008, 17:37
D.A.S. welcome.... with a newb post like that, how about adding something of value yourself? Adding CoreAVC as tray icon _IS_ of value (and requested) as sometimes ppl have multiple windows open and want an easy way to get back to the filter properties (alt+tab) once they make a change.
Guest
1st September 2008, 17:43
I think he was asking you to add an option to enable/disable the tray icon, not dissing the feature.
DigitalDeviant
1st September 2008, 17:57
I think he was asking you to add an option to enable/disable the tray icon, not dissing the feature.
Seems a poor way of requesting it, so I'll properly request it.
Could you please add a feature to turn off/on the tray icon since some of us don't need it. I have too many tray icons as is w/ ffdshow audio/video and haali's splitter and I don't need to access any of CoreAVC's properties during playback.
BetaBoy
1st September 2008, 18:25
Got it.... me bad... wondered why he regged a year ago only to post now. But yes, an icon disabling feature is planned in the next release.
I had also discussed with Haali a more universal means for 'current' Codec access (codecs that are currently in use) with the splitter (that's the intent of the current tray icon). I'll ping him again on this.
BetaBoy
1st September 2008, 18:31
I just published the CoreAVC Filter properties Guide: http://www.coreavc.com/index.php?option=com_content&task=view&id=42&Itemid=1
We have more planned to add to it including links, pics, etc. with each release leading to 2.0.
Disabled
1st September 2008, 18:44
I just published the CoreAVC Filter properties Guide: http://www.coreavc.com/index.php?option=com_content&task=view&id=42&Itemid=1
You got a small error there. The screenshot around "Input Formats" shows the "Input Levels". But nice overview - about the same as in the help screen...
You might also want to have a link in the properties dialog pointing to that website.
TheShadowRunner
1st September 2008, 18:51
So forced tray icon in 1.8 huh.. what the hell :/
BetaBoy
1st September 2008, 18:51
Disabled... thx for the catch/suggestion... Change has been made.
D.A.S.
1st September 2008, 18:55
I think he was asking you to add an option to enable/disable the tray icon, not dissing the feature.Yes. Something alike as in Haali Media Splitter.
Guest
1st September 2008, 18:58
Hey Dan, a while ago I asked about an SDK for using CoreAVC programmatically in DGAVCDec. You referred me to your engineers but they have failed to follow up with me. Do I take it then that you have no interest in this idea?
BetaBoy
1st September 2008, 19:03
neuron2.... It must have gotten lost in the shuffle here. I just sent you a followup email CC'd the guys here about it.
dead_screem
1st September 2008, 20:12
I experience a few bugs with 1.8 and WMP 6.4. When opening AVC video files (mkv, avi etc..) with WMP 6.4 the new tray icon disappears as soon as I mouse over it. In addition, opening the new help tab in codec properties, all the text is highlighted and the text window is scrolled all the way down. None of this happens if I try to play the file with WMP11 or MPC for example.
And possibly related to the WMP 6.4 icon bug, If Haali's splitter is set to Enable Thumbnail Extraction, when I click on a file in explorer it loads the thumbnail in the side pane just fine but as soon as I click on the file the tray icon shows for a split second. so if I doubleclick the file real fast it won't open, instead it acts as if I only clicked on the file once to perform a file rename. It's as if that coreavc tray icon blocks the file from being doubleclicked? If I click the file once, and wait for the trayicon to disappear I can then doubleclick to open the file.... disabling thumbnail extraction in haali can workaround this, but only for mkv files. The few avi AVC files I have exhibit this problem as well. And windows has no disable thumbnail extaraction option for AVI AFAIK...
None of this nonesense happened with 1.7. Thumbnail extraction worked fine and didn't cause any double click problems.
TheShadowRunner
1st September 2008, 23:45
The "resolution change" bug is still there.
how to reproduce: open any video with h264 stream and simply change the monitor resolution: -> the video will be frozen with crazy artefacts under the new resolution. (really bad when using Reclock)
This problem started after 1.6.5.
It can be fixed by opening Coreavc properties, making a fake change in there and press "Apply". the video will then be refreshed.
please fix. also don't forget to add a feature to HIDE the tray icon.
Thanks.
BetaBoy
2nd September 2008, 02:19
Great work guys keep the reports coming!
Snowknight26
2nd September 2008, 04:36
Was a 64-bit version of Haali Media Splitter released with CoreAVC 1.8.0.0? Only pertains if an x64 version of CoreAVC was released though.
BetaBoy
2nd September 2008, 06:15
No.... only Haali's 32bit version from March was included. What we plan to release with CoreAVC 64 is the filter and 64 bit versions of Haali's Splitter and TimeCodec.
Also with 1.8... I am keeping a list of the CoreAVC reported/confirmed bugs at the CoreCodec forums ( http://www.corecodec.com/forums/index.php?topic=1266.0 ), but it looks like 1.8.1 will be coming pretty soon so no need to add them to the tracker.
3ngel
2nd September 2008, 17:09
@Betaboy
I would like to go from standard to pro. I have to pay the entire price or there can be an "upgrade" option (paying the difference or whatever)?
Moreover i second definetivly the option to remove the tray icon. Too much of them indeed.
BetaBoy
5th September 2008, 00:21
ok all... 1.8.1 is in QA... so a few things....
- We have fixed all the reported bugs (although WMP 6.4 still needs testing)
- We have disabled the tray icon and added an option to enable it
- We have also enabled the 'Preferred decoder' by default (as we assume you have purchased it and want to use it by default)
I'll let you all know how things are going.
Dark Shikari
5th September 2008, 00:34
ok all... 1.8.1 is in QA... so a few things....
- We have fixed all the reported bugs (although WMP 6.4 still needs testing)
- We have disabled the tray icon and added an option to enable it
- We have also enabled the 'Preferred decoder' by default (as we assume you have purchased it and want to use it by default)
I'll let you all know how things are going.Any update on Predictive Lossless support?
BetaBoy
5th September 2008, 04:38
Dark Shikari.... You have a few samples?
Dark Shikari
5th September 2008, 05:09
Dark Shikari.... You have a few samples?Only the sample I originally uploaded, but here's a 7zip file with that sample, a patch for ffmpeg to add (hopefully) compliant decoding, and an mplayer executable using that patch. Download (http://www.mediafire.com/?etqtcziuwyt).
BetaBoy
5th September 2008, 06:15
Got it thx... 4:4:4 will be in 2.0 (including predictive) but I'll see what we can do.
G_M_C
5th September 2008, 08:54
Any update on Predictive Lossless support?
Got it thx... 4:4:4 will be in 2.0 (including predictive) but I'll see what we can do.
DS: When's that (and 4:4:4 / High10 support etc.) gonna be in x264 ;) ?
Dark Shikari
5th September 2008, 09:06
DS: When's that (and 4:4:4 / High10 support etc.) gonna be in x264 ;) ?Predictive will be in as soon as a publicly available decoder supports it ;)
4:4:4 will be in as soon as someone volunteers to write that mess.
High10... ugh... anyone want to rewrite all the intra pred, DCT, iDCT, and MC? :eek:
G_M_C
5th September 2008, 09:25
Predictive will be in as soon as a publicly available decoder supports it ;)
4:4:4 will be in as soon as someone volunteers to write that mess.
High10... ugh... anyone want to rewrite all the intra pred, DCT, iDCT, and MC? :eek:
:p
That's why i asked;
4:4:4 / High10 support in CoreAVC would not be very usefull when there are no (reguarly used) encoders to actually build such files. ;) Mainstream video doesnt even work with "xvYCC" / Deep Color yet (Even if you have hardware that supports it, there are no actual disks/sources "in the wild"), so from that point of view it's not really usefull implementing stuff like that at all.
I imagine that 4:4:4 etc. will mostly be used on (very) high end equipment, for ex. in movie studio's, and I really doubt that those studio's would have need for something like CoreAVC.
So all in all; I cannot see the real need for that support in CoreAVC yet, DXVA might be a much more usefull time-investment.
Dark Shikari
5th September 2008, 09:31
4:4:4 I can imagine would be very useful for graphics, 8-bit games, etc.
BetaBoy
5th September 2008, 12:03
Dark Shikari.... I should have also said off the bat that that we 'do' support Predictive Lossless in the current CoreAVC 1.8 (unofficially)... and that sample is the same as the last one you had posted (its 4:2:0 not 4:4:4).
Also... We feel here at CoreCodec that you can see more use for 4:4:4 then 4:2:2.
G_M_C
5th September 2008, 15:14
[...]
Also... We feel here at CoreCodec that you can see more use for 4:4:4 then 4:2:2.
True, offcourse you can see that difference. But i have not seen 4:4:4 in the wild yet, and I have no idea when those clips will become more mainstream. That why i asked myself about the usefullness of developing a decoder for such clips, and DS responded to my thoughts ;)
BetaBoy
5th September 2008, 16:09
Well I agree 'Now/Short term', No. I'm thinking 1+ years from now. Imho, the key for its initial adoption is 'when' x264 supports it, and as Dark Shikari mentioned its gonna require a lot of work as it is for us with CoreAVC 2.0 as well. But decoding is cakewalk compared to encoding ;-)
Dark Shikari
5th September 2008, 16:43
Dark Shikari.... I should have also said off the bat that that we 'do' support Predictive Lossless in the current CoreAVC 1.8 (unofficially)... and that sample is the same as the last one you had posted (its 4:2:0 not 4:4:4).
Also... We feel here at CoreCodec that you can see more use for 4:4:4 then 4:2:2.Ah, well that's even better, then I can get around to committing predictive lossless sometime soon. And as I said, it is the same as the last one I posted.
I do see more use for 4:4:4 than 4:2:2, simply because 4:2:2 is mostly an "interlaced thing," and I'm not a big fan of interlacing... :cool:
G_M_C
5th September 2008, 16:45
Well I agree 'Now/Short term', No. I'm thinking 1+ years from now. Inmo, the key for its initial adoption is 'when' x264 supports it, and as Dark Shikari mentioned its gonna require a lot of work as it is for us with CoreAVC 2.0 as well. But decoding is cakewalk compared to encoding ;-)
HAs the look and feel of "chicken & the egg" situation. But good that at least someone is thaing the lead.
Because after interlacing (and I do hope that finally dies allready), colormetry-differences and NTSC vs. PAL situations are finally starting to die out, it's the colorspaces where the advancement in better quality lies imho.
allouh
6th September 2008, 03:23
wrong place for me to post.
sorry
Ranguvar
6th September 2008, 03:45
The problem is most likely not CoreAVC, but your encode. Either your source is VFR, the framerate was set improperly, or something screwed with the audio.
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.