INTERACT FORUM

Many thanks Alex

I don't know why it doesn't work : I have noticed that Output is active on your screenshot; perhaps I have forgotten something.
What kind of settings do you have for the output/input parameters ?

Madien

No I was speaking about the I/O options on JRiver. I assume I have set something wrong to have this "harsh" noise and all I/O in red.
Madien

im sorry, i dont use that plugin.
i assume though, that sound i good when you dont use the plugin?
now when you use the plugin and you click on the by pass button. what happens?

 
gab

If you're using Win7 or Vista, did you try WASAPI?

We're talking with Lynx now, so don't give up.

Have you tried MC's DSP features?

it seems to be working for me. more or less out of the box. had to turn off the output format in mc because the plug in did not like 48 kHz, 24 bit , 4 channel. but that did not give any i/o problems, just a message at the top about unsupported format.

nice plug in though.

 
gab

oh.. what i also thought. did you use the vst or the directx plugin?

Let me throw my hat into the ring as having problems with Ozone and MC 15 as well.  I've been using Ozone for years with previous version of MC, however 15 is giving me fits with it.  I am able to get it working, albeit not without issue.

Are you using it as a VST?  If possible, try that instead of DirectShow.

Also, changing the buffering slider in Options > Audio could make a difference.  Very small buffering values (like 0.05 seconds) will move smaller chunks through the DSP at a time for latency reasons.  Of course, the DSP plugin should support any size block.

Finally, it might be worth contacting the maker of Ozone.

Thanks.

Okay, here we go... 

Are you using it as a VST?  If possible, try that instead of DirectShow.

I'm not sure which way I added it (probably DirectShow), but it doesn't do anything if I try to add it as VST (probably because it's already in the list.  How can I remove it from the plug-in list, so I can re-add it?

Also, changing the buffering slider in Options > Audio could make a difference.  Very small buffering values (like 0.05 seconds) will move smaller chunks through the DSP at a time for latency reasons.  Of course, the DSP plugin should support any size block.

Tried 5 seconds and things really got bad (restarted MC to test).

Tried 1 second and the problem clip played fine the first try (restared MC to test).... however, when immediately changed to another file to play, MC crashed (saved the log).  Restarted, tried to play the same thing again, switched tracks again, and boom... another crash.  Restarted, played a known good file first (played fine), switched to that same problematic file and got the double-speed/skipping problem.

Tried .05 seconds and garbage (similiar to 5 seconds).

Finally, it might be worth contacting the maker of Ozone.

I don't think this is a solution, since Ozone works perfectly in all my other audio programs/workstations, without any issue whatsoever.

Force a single output format (channels, bit depth, and sample rate) in DSP Studio > Output Format.

Does that make a difference?

I had tried messing around with this before, but didn't have any luck, as Ozone didn't like the output format.  I think I just figured out why... I tried setting it to simple 16-bit/44k and, most importanly, 2-channels.  Tried with various bitdepths/sample rates and all worked through Ozone and everything plays fine (including the problematic ones).  Interesting.  Since I only use this particular machine for house audio, this will work fine.

So that leads me to two other questions:

1) I've maxed out the samplerate/bitdepth and it seems to handle it, although at this maxed out setting I get a little buffering stutter from time time.  Lowered it to 24/96k and haven't noticed any thus far.  So any drawbacks/benefits to using higher?  Not sure what combination is best suited here.  I listen to mainly MP3s/AACs/CD-rips.  Haven't really got into these ultra-high quality formats just yet.

2) On each restart of MC, I have to go into Ozone and select my settings again.  I seem to recall I had fixed this in MC 14, but can't recall how.  Possibly to do with it being directshow vs. VST (in which case, it goes back to above... how to remove it as direct show and re-add it as VST)?  I'm really thinking this difference might be the cause of all the problems, since I never had to use this "Output Format" plugin before to get Ozone to work fine.

Just a note... until I enabled this "Output Format" plug-in, switching tracks/advancing was almost instaneous.  Now there is a noticable delay.  I went in and dropped the buffering to around a second and it actually made a big difference.  Might even try a lower setting.

Thanks so much guys.

You're talking to JRiver here, but it isn't clear this is a JRiver problem.

Maybe uninstall and reinstall Ozone or double-check the Ozone settings really carefully.  Use Ozone as a VST if possible. (click 'Add Plugin' in DSP Studio, remove Ozone, then add again by browsing to the Ozone VST)

AH HA!  There is the option to Uninstall (who would have thought it would be hidden under "Add Plug-in..").

Did that.  Added Ozone back as VST and wholla.  No problems whatsoever.  Even disabled the "Auto Output" plugin and all files (including the troubled ones) playback fine.  As I said before, this was what I thought was the most likely reason this was having trouble, but I didn't know how to remove it.  Note that I did not uninstall/reinstall Ozone itself from the system.  I use Ozone in a lot of high-end audio workstation tools, but all of them use it as VST.

And, as I predicted, it remembers your presets/settings upon restart when it is being used via VST.

Does the wiki contain the information about removing a plug-in?  I noticed an old thread on here asking that question, but it was never answered.

Thanks you guys.