Subject:Channel Converter

Posted by: Solon do Valle

Date:3/15/2005 7:08:14 AM

Channel Converter does not work on SF 8.0.
Is it a known bug, or my computer´s fault?
On SF 7.0, it used to work fine.

Subject:RE: Channel Converter

Reply by: Sonic

Date:3/15/2005 7:31:27 AM

Whoa nelly. There is a bug here.

I was going to ask for more details, but I just tried a bunch of cases and stereo-to-mono is indeed horked. It produces clipped garbage.

It works if you just use "Convert to specified output channels only". All other directions (m2s, s2s, m2m) seem to work, as well. Simple conversions from the status bar or file properties work for me, too.

This will certainly be addressed in the first update for 8.0, which usually appears a couple months after the initial release.

J.

Subject:RE: Channel Converter

Reply by: Spheris

Date:3/15/2005 9:17:44 AM

Several months?
Please tell me I read that wrong.......

Subject:RE: Channel Converter

Reply by: Sonic

Date:3/15/2005 9:27:53 AM

I said a couple months, not several. This shouldn't be suprising if you look at previous releases and when updates are posted.

J.

Subject:RE: Channel Converter

Reply by: Spheris

Date:3/15/2005 9:30:56 AM

Not surprising no, but for something like this (basic internal function) - it kind of goes without saying it wouldn't be outside the loop to think that we could hope for a more immediate fix. As far as a couple vis several, acid took several months before an update ( knock wood, I never saw any problems at all)

Without a specialised plugin like the s-1 etc, it's going to be a real ass biter for some people. But then again, maybe they'll hop right on it, rather than let it sit.

Subject:RE: Channel Converter

Reply by: Sonic

Date:3/15/2005 10:20:20 AM

Here's one easy workaround:

Pick any stereo-to-mono preset (or your own settings), but switch the "Output channels" control to stereo, process, then just convert to mono via the status bar (Left channel). Voila.

I'm sure there are several others, but this is probably the easiest.

J.

Subject:RE: Channel Converter

Reply by: Spheris

Date:3/15/2005 2:02:03 PM

Appreciated for the suggestions, it's not such a killer for me (the workaround does work - a little clunky but DOES work). But I've already had two people hit me about this today and had to step them through it. This is the second time in as many months I've ended up with egg on the face for pushing a switchover to sonys apps in the shop. Workflow is everything on timelines. Sony cut corners on this and now we have two corners to round to do what should be a no brainer. Things happen I know and if it was one of the new features I doubt I would have much to say to it than "shakedown period" the channels converter however is not a "new feature"

We had an unrelated similar thing happen with Vegas (bussing issue that cannot be fixed till 6.0 but we solved the workaround with it and got everyone happy by degrees) a while back that was kind of the same sort of iritating oops gaffe. Just a little frustrated with getting hit with gotcha's that make little to no sense - this one was just on first look so simple and fundamental a gaffe. It sort of seemed like an immediate patch would be simply for the sake of good will but then again...

But..Praise where praise is due.....Otherwise a dramatic improvement over 7.0 on most fronts. So I do want to throw that in there as well, my hats off to the developers for making many things work much better than any previous version - and a big fork to the QC team for dropping the ball on the basics. But Sonic, I want to personally thank you for pitching in a suggestion for temporary workaround until a patch comes down for it

Subject:RE: Channel Converter

Reply by: Sonic

Date:3/15/2005 3:07:07 PM

Turns out the cause of this is a change in compiler behavior between Visual Studio .NET 2002 and 2003. As you mentioned, these things happen. But they happen to more than "new features" because of things just like this.

To use the Channel Converter with no workarounds, you can try setting the internal pref called "Use SSE2 optimizations when available" to FALSE until 8.0a is released. Or use a Pentium 3 box, heh.

J.

Subject:RE: Channel Converter

Reply by: Spheris

Date:3/15/2005 3:11:58 PM

Cool, had a feeling it was something probably crazy goofy like that. I've heard that some things with VS.net get a little weird on varying processors. Seemed almost impossible to see it slipping past but gives me some pause as to what else might be affected by it

All good for now, any eta on an update

Subject:RE: Channel Converter

Reply by: Sonic

Date:3/15/2005 3:18:18 PM

I can't divulge a specific date, so I'll stand by my original and vague 'a couple months'.

J.

Subject:RE: Channel Converter

Reply by: Spheris

Date:3/15/2005 4:45:40 PM

Last question, if we disable SSE2, will that turn off SSE across the board (there was a question about if the P$ would still use the legacy SSE enhancements)

Subject:RE: Channel Converter

Reply by: Sonic

Date:3/16/2005 6:40:37 AM

Just SSE2.

Subject:RE: Channel Converter

Reply by: Spheris

Date:3/16/2005 8:34:29 AM

A gentleman and a scholar, I thank you.

Subject:RE: Channel Converter

Reply by: tibia

Date:3/20/2005 8:55:51 AM

I'm sure it's right in front of me, but where is the "Use SSE2 optimizations when available" setting? I cant' find it.

Subject:RE: Channel Converter

Reply by: Sonic

Date:3/21/2005 7:32:07 AM

Ths is an internal preference. If you hold down Ctrl+Shift while selecting Options->Preferences, the Internal tab will be exposed.

Be forewarned that these are internal for a reason and if you poke around in there too much, you''re bound to cause problems with your installation.

But the one I mentioned can safely be changed.

J.

Subject:RE: Channel Converter

Reply by: tibia

Date:3/21/2005 3:57:43 PM

Thank you. I'll be careful!