![]() If that turned out to be the case, any additional bits used by a higher setting would be totally wasted and would skew the required quality versus required typical bitrate ratio heavily and compromise efficiency with no gain whatsoever in perceived quality. The OP may not be able to distinguish, say, -V3 (~175Kbps) from a lossless source for all we know. Don't bother at all with anything lower.Īs quality is in the ear of the beholder, I don't think that's a safe suggestion to make personally if efficiency is still to play a relevant part in the equation. I don’t think Apple or any of the other player makers are going to change to accommodate Wavelab VBR files if everybody else is adding headers when making the files.Quote from: shadowking on 14:20:51 For quality preference over size, I suggest V1 (200.260k), V0 (220.290k) even b320. I could see that as a reason to leave it to the players, but everybody else adds the VBR header when making the files, and iTunes (and the other players) don’t deal with the files as VLC appears to, so iTunes and the others will continue to display the wrong times and the playhead will be wrongly affected. PG, is the reason Wavelab doesn’t add the VBR header for simplicity of the files and to let the players take care of this? After seeing how VLC deals with the playlist (doing the calculations and displaying the correct time only after the file is put into play?). Thanks so much for the comment folkfreak, I fully agree. Its really sad that one have to use a free external programm instead of the expensive programm one has bought for audio editing.īut I already know how this ends: “No fault in Wavelab, we make everything right, the other programms are faulty” Thats the reason I only export to wav in wavelab and do all things MP3 in foobar2000. That’s still a different issue.īut the lack of VBR headers in the Wavelab files when all others seem to have added it by now, should be addressed. VBR MP3s made in all these programs are correctly indicated as VBR in the other players, with correct times).Īs a note, fixing the VBR header in Foobar doesn’t fix the clicks that occur in Wavelab continuous lossy file transitions. (the other encoding programs I’ve tried being iTunes MP3, XLD LAME, Sonnox Fraunhofer, Foobar LAME, xRecode LAME. But Wavelab is still the only program that makes MP3 VBR files that exhibit these issues at all from what I can tell. ![]() Wavelab LAME only seemed to have problems with OS times in the earlier thread. The mistimes in players only seem to happen with Wavelab Fraunhofer, and only sometimes. I have example files: 11-14 second Wavelab Fraunhofer VBR files that are seen as 3 seconds in iTunes (partially) and Foobar2000. The Wavelab VBRs can be fixed with the “fix VBR mp3 header” tool in Foobar2000 (see first attached pic), but one shouldn’t have to do this. No other program I find besides Wavelab makes VBR MP3’s that are not identified correctly or have time problems like this. ![]() In VLC Playlists (a program PG mentioned in the Wavelab 8 thread), Fraunhofer times are also often initially wrong, and only become right as each file is played. (the time discrepancy is what prompted the Wavelab 8 thread). And Wavelab’s Frauhofer VBR MP3s are also oftentimes displayed with incorrect times in iTunes and Foobar2000 players, which messes up the playhead in those players. In these programs, Wavelab VBR MP3s are identified as CBR. It would seem that Wavelab is probably the only program that still makes VBR MP3s (both Fraunhofer and LAME) that are not identified as VBR by two of the only programs that identify CBR vs VBR: Foobar2000 and xRecode. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |