I got a problem transcoding DTS to AAC, I think I had this problem before too. It crashes during initialization so the log doesn't get updated. I get an error with azidts, The instruction at XXXXX referenced memory at XXXXX. The memory could not be quot;readquot;.
So I checked to see if I have the ac3dtssrc.ax file, and nope I didn't have it. So I went to Gabest's website to get it and couldn't find it anymore, I only found a file called dtsac3source.ax. I checked with Gabest and he said that was the only file he ever had?? Suggested me to rename it to ac3dtssrc.ax and try BeSweet again. I did that but still got the error. So is this problem with the ac3dtssrc.ax file or something else?
I am using BeSweet b25, registered copy of WinDVD 4 Platnum, and all the latest Nero files. Also everything was working for me till I updated the BeSweet to b25.
Any ideas? Please help me...
Did you register the AC3DTSsrc.ax filter? (regsvr32 ac3dtssrc.ax).
p.s. How are you using BeSweet 1.5b25 with azidts? The latest version of besweet.dll on Dg's site is b23.
Yes I did register it, made sure again as well. The BeSweet I downloaded from DSPGuru's website had the name: BeSweet v1.5b25. The very top link under beta.
I think I should rephrase my question:
Is dtsac3source.ax from gabest the same as ac3dtssrc.ax?
You can't transcode DTS with BeSweet. You need to use azidts. software2.htm#audio
Originally posted by jk888
I think I should rephrase my question:
Is dtsac3source.ax from gabest the same as ac3dtssrc.ax?
I think it is a newer build. At least newer than the one in the azidts package. Furthermore you need BeSweet.dll and the latest is 1.5b23 as KpeX stated.
But I think your problem is somewhere else: You posted you have WinDVD 4 Platinum. You need WinDVD 4.5 or later. The 4.0 filters can't be used from outside of WinDVD to transcode DTS.
Regards,
tiki4
My WinDVD is 4.5 Platinum, I reinstalled it just in case. I have the latest BeSweet b23 dll, it was included inside the BeSweet b25 package, but just in case I downloaded the b23 dll directly from DSPGuru's site again. I tested it and still same problem.
Here's what happened:
then right at that point I get error message from azidts:I have a feeling that azidts v0.1 doesn't work with BeSweet b23 dll.
It worked on my machine. azidts 0.1/BeSweet.dll 1.5b23/WinDVD 4.5 Platinum/WinXP SP1.
Dunno what's going wrong on your end.
tiki4
P.S.: Make sure you really use bsn.dll 0.2 from the b23 package. I guess the newer bsn.dll 0.21 won't work with BeSweet.dll 1.5b23.
Originally posted by tiki4
P.S.: Make sure you really use bsn.dll 0.2 from the b23 package. I guess the newer bsn.dll 0.21 won't work with BeSweet.dll 1.5b23.
true.
Thx for the help tiki4, and DSPguru. I tried bsn 0.2 and yes that finally worked for me. Just wondering, why was there a bsn 0.21 anyways? If BeSweet doesn't work with 0.21 then maybe it should be removed from the BeSweet b25 download package, cause it really adds to the confusion for users.
Originally posted by jk888
Thx for the help tiki4, and DSPguru. I tried bsn 0.2 and yes that finally worked for me. Just wondering, why was there a bsn 0.21 anyways? If BeSweet doesn't work with 0.21 then maybe it should be removed from the BeSweet b25 download package, cause it really adds to the confusion for users.
It works with besweet 1.5b25, not with b23, which is the latest dll available atm (and needed for azidts).
First off when you download b25 from DSPguru's website it doesn't have a besweet.dll file in the package, you have to download b23 dll separately near the bottom of betas. So b23 and b25 is the same thing.
Next I have tried bsn 0.21 with the latest BeSweet b25 package with the following command line:
quot;F:\BeSweet\besweet.exequot; -core( -input quot;f:\DVD1\test.dtsquot; -output quot;f:\DVD1\test.mp4quot; -logfilea quot;F:\BeSweet\BeSweet.logquot; ) -bsn( -6chnew -config ) -ssrc( --rate 44100 )
This fails and gives me same error has mentioned in my very first post, with the exception that the memory error box says it's from besweet.
I also tried this command line with bsn 0.21 and latest BeSweet b25 package (I had to add azidts 0.1 manually from Doom download site to get it to work, maybe it should be included in the BeSweet package):
quot;F:\BeSweet\azidts.exequot; -core( -input quot;f:\DVD1\test.dtsquot; -output quot;f:\DVD1\test.mp4quot; -logfilea quot;F:\BeSweet\BeSweet.logquot; ) -bsn( -6chnew -config ) -ssrc( --rate 44100 )
This failed the exact same way as my very first post.
Just a side note, the nero config comes up fine for both instances.
So as DSPguru already mentioned, bsn 0.21 does not work with BeSweet. When I tried bsn 0.2 everything works great. Now if someone can get 0.21 to work then prove me wrong.
Ah, please think before stating such claims!
bsn.dll 0.21 works with BeSweet.exe 1.5b25. Period.
The changes from 0.2 to 0.21 are that BeSweet now automatically resamples to the right sampling rate when using the Nero HE-AAC codecs. Thus a -shibatch() section is totally unnecessary when using 1.5b25. Maybe that stuff crashes, because you try to load shibatch.dll twice.
azidts only works with BeSweet.dll. The latest is 1.5b23 which only works with bsn.dll 0.2. Take it as given and wait till DSPGuru finds the time to release a new BeSweet.dll.
tiki4
Ok sorry I take back my comment, I mistaken that BeSweet b25 is the same as b23. But either way I couldn't get b25 to work, I checked everything even tried without the -shibatch() line, and even tried deleting the neroipp.dll. BeSweet worked for me all the way till b25 came out so I don't know why it works for some and not for me. But now b23 works and the only difference is that b25 auto gets the correct sampling rate, which I know how to pick for myself, so I'll stick with that.
The biggest problem with using BeSweet period is that it needs many separate files from various different developers, then you have to worry about different versions conflicting with each other. Most users will never get BeSweet to work mainly because it's missing files from the start, and they don't know where to find them.
DSPGuru is a ingenious developer and I am grateful for his work on BeSweet. But alas BeSweet is not user friendly, and probably only a very very select few people in this forum will get it to work. BeSweet is a great accomplishment but few will ever appreciate it's usability.
I think most users (even in this forum) use it in a package like GordianKnot, AutoGK, DVD2SVCD only to name a few...
They never care how to install it, actually.
On the other hand, it is not that difficult to set it up manually. If you stick to the BeSweet FAQ: Get 1.4 stable and unzip it to some directory, get 1.5b25 and unzip it on top. Now you have everything to go. If you use the GUI, just unzip it into this directory as well.
As you are someone who is encoding to AAC you may consider yourself as one of the few quot;electquot; persons who do so. I must admit that this is a more complex setup, as you need third-party libraries. However, the problem does not lie on the side of BeSweet. From Nero 6.0.0.23 the behaviour of the AAC codec has somewhat changed. Up to 6.0.0.19 (I think) it was enough to put aac.dll, aacenc32.dll and NeroIPP.dll into the BeSweet folder. Now from 6.0.0.23 the AAC codec look for the location of NeroIPP.dll in the registry. The easiest way to get it to work is to install (lastest) Nero package and just copy aac.dll and aacenc32.dll to your BeSweet folder. Nero registeres NeroIPP.dll correctly in the registry. You must admit that this quot;inconveniencequot; is not the fault of DSPGuru.
Now it is very likely that the behaviour of the Nero AAC codec changes again in the future and that DSPGuru finds or not finds the time to adjust bsn to the new situation. This is the price you pay for a very convenient, high-quality encoding solution which is in no way supported by the company selling Nero Digital with their software solution.
Just some thoughts...
tiki4
Originally posted by tiki4
I must admit that this is a more complex setup, as you need third-party libraries. However, the problem does not lie on the side of BeSweet. From Nero 6.0.0.23 the behaviour of the AAC codec has somewhat changed. Up to 6.0.0.19 (I think) it was enough to put aac.dll, aacenc32.dll and NeroIPP.dll into the BeSweet folder. Now from 6.0.0.23 the AAC codec look for the location of NeroIPP.dll in the registry. The easiest way to get it to work is to install (lastest) Nero package and just copy aac.dll and aacenc32.dll to your BeSweet folder. Nero registeres NeroIPP.dll correctly in the registry. You must admit that this quot;inconveniencequot; is not the fault of DSPGuru.
I wonder why foobar works transcoding AC3 to AAC without putting the Nero .dlls in the foobar folder?
The 3rd party files from sources such as Nero are a small issue. What really bothers me is the packages from DSPguru's site lacks required files such as azidts (because the GUI creates scripts using it). dtsac3source.ax from gabest is a really really hard to find on the net, most users won't know to visit his site, and if you get a crash from missing that file you won't know the error was due to it being missing. And the part about unzipping BeSweet 1.5 over 1.4, I didn't know this till now, there's no documentation on the site or on the readme; there's a post on the forum but it's hardly layed out chronologically for newbies to understand (most newbies don't visit forums).
I knew about BeSweet 3 years ago, but I only got it to work 1 year ago, I went through hell and back to learn every single misc. thing to get it to work finally. Sorry if I am complaining too much but I am just fustrated to my neck with BeSweet.
I really wish more people would be able to convert stuff to AAC like I am. Yes as you said AAC transcoding is very complicated, and I am the only very very few people to release Xvid movies with AAC. But I just wish there is an easier way so more people can do it, so I don't have to write a 5 page document to get other movie enthusiasts to do it right... so we can share quality movie with high quality AAC audio...
Alot of the stuff I am asking for is simple to impliment and would save users alot of time and fustrations. I don't think I am asking for too much either because we're at the point of just getting the program to work. Thx for letting me blab on, I hope if DSPguru has time he would consider these suggestions, but either way I continue to use and support his work on BeSweet.
Originally posted by bobsc
I wonder why foobar works transcoding AC3 to AAC without putting the Nero .dlls in the foobar folder?
foobar2000 does not use the dlls directly but uses the Nero API (AFAIK). Thus you just need a full install of Nero to transcode in foobar2000. I still think that this is the reason for the slightly different behaviour. Maybe Case on HA can offer more information (I think he programmed the Nero encoding plugin).
@jk888:
Well,
there are easier ways than BeSweet, it's just less quality. 3ivx DirectShow filters are based on libfaac. Thus you get multichannel LC-AAC but the quality should be way off (at least according to listening tests performed at HA). Also you can easily decode to 6ch AIFF in BeSweet and encode this file in Nero, 2 steps but no fiddling with 3rd party libraries. The probems with azidts. Well, just use GK and you have everything you need on your hard disk. I know this is rather difficult, but you had rather bad luck I guess. BeSweet worked for me from the very beginning and as I always use the CLI I never bothered me with the GUI very much. Good luck in the future, though.
tiki4
@jk888
Please reread the forum rules, and the disclaimer on the Doom9's homepage. This forum is only for assisting you in exercising your fair use rights, not to assist in any kind of piracy. Consider this a warning.
I didn't specify what kind of movies, the term movies could also mean personal movies, therefore you don't need to warn me. |
Post at 2011-4-15 16:38
| This Author's Posts Only
