Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[scthom]

Well, after all of those great comments last week, I got to work over the weekend and managed to tackle all of the "shortcuts" in the previous version.

Version 1.2 is now available at http://members.cox.net/scot.thompson.  It will be posted on the JRiver plugins page soon.

It now updates the progress bar, and should work with up to 8 channels and 24 bit data.  Also, the memory limit was re-worked so large files should no longer be a problem.

The normal caveat applies:  it works for me, but it may not work for you.   Please let me know what you think or if you have issues.

[jgreen]

Just tried it out and it seems to work well.  I tried it on a short wav--success!  I tried a short wma/160/cbr--success.  Then I got cocky and went after the longest track I have:  2 hours 49 minutes (3 albums cut together).  The plugin chewed right through it, with one note:  the track was already WMA (lossless), which I believe acts like a vbr.  The file plays fine, but it reports distorted duration and bit rate (7:34 x 15,801).  I think this is a failure of the WMA "waymarkers" or "milestones"--whatever you call them--or a failure of the plugin to read them.

I just tried a 3:11 WMA (lossless) and everything went perfect--must just be the honkin daddy of a track I fed it before.

All in all, it works quite spiffy.  Congratulations and thanks, scthom! 

[scthom]

Then I got cocky and went after the longest track I have:  2 hours 49 minutes (3 albums cut together).  The plugin chewed right through it, with one note:  the track was already WMA (lossless), which I believe acts like a vbr.  The file plays fine, but it reports distorted duration and bit rate (7:34 x 15,801).  I think this is a failure of the WMA "waymarkers" or "milestones"--whatever you call them--or a failure of the plugin to read them.

Hmm.  Nothing in the encoder plugin calculates that.  That information is all calculated by the FLAC sdk functions.  In that case, there is nothing I can do short of looking to modify someone elses work.  The other possiblity is that it's the decoder plugin - that is what MC uses to read and write all of the metadata.

[scthom]

Hmm.  Nothing in the encoder plugin calculates that.  That information is all calculated by the FLAC sdk functions.  In that case, there is nothing I can do short of looking to modify someone elses work.  The other possiblity is that it's the decoder plugin - that is what MC uses to read and write all of the metadata.

In case anyone is interested, I have discovered that it most likely was the FLAC decoder plugin.  There are several places where Oblong hasn't quite followed the FLAC specification and overflows may occur.  One of these is the total samples field, which affects the duration and other possibly some other calculations.

[jgreen]

Good info, SC! 

Saw you'd checked in, thought I'd let you know that I continue to roadtest your plugin with stellar results!  Haven't seen a repetition of that issue, but I haven't done any long-duration conversions since.

Hope all goes well with you, and thanks again for your hard work!

[iCamp]

Thank you for all your hard work!