Wierd Canopus Let's Edit Bug Figured Out

G

Guest

Guest
Archived from groups: rec.video.desktop (More info?)

Like many people, prior to version 1.06 of Let's Edit coming out last week,
I had the annoying problem that Let's Edit would crash every time I output
an AVI file. Unlike most people, however, once I had that crash after an
AVI file output, any further attempts to launch Let's Edit would cause a
prompt crash, until I rebooted the machine.

Once I had 1.06, the AVI file output problem went away (not that I
output AVI files very often), but over the past few days, I noticed that
the crashes on startup were still there, semi-randomly.

I believe I've just solved that problem. And I'm a little annoyed that
the Canopus support people didn't pick up the clue that was in my
very first messages to them on the topic.

I've got Visual Studio on my machine, and thus could drop into the debugger
when Let's Edit would crash. It reported a bogus access in the module
VELOCITY.dll. The question that should have been asked was "What is
VELOCITY.dll, and why is it being invoked by Let's Edit?" I had naively
assumed that it was some Canopus component. But no. It's a DXi "soft synth"
that was bundled with a Cakewalk audio package I've also got installed.

Let's Edit is capable of using DirectX audio plugins as filters on
audio tracks. That's a very nice feature. Unfortunately, Let's Edit
does not make the distinction between DXi effects and DXi synths
when it goes through the registry and opens them up. If I open an audio
effects dialogue in Let's Edit and check the settings on the "DirectX bridge",
my choices include not only all the numerous DirectX audio plugins I've
got for compression, reverb, EQ, distortion, etc., but also all of my
DXi software synthesizers: Reaktor, Tassman, Kontakt, Synth1, and...
"Velocity". As it happens, I never use Velocity (It's a software drum
machine, of which I have several others that I like better), so I de-registered
it using regsvr32.exe /u. Now I seem to be able to fire up Let's Edit
with impunity - and it also starts up noticably faster.

I believe that there are actually two bugs here. One is in Velocity,
because it is obviously thrashing around and crashing when it's being
probed or opened by Let's Edit as a DirectX effect, while none of my
other DXi softsynths seem to do so. But the other is arguably in
Let's Edit (and maybe other Canopus products). It's possible for a
host program to distinguish between DXi filters/effects and DXi synths.
I know this because Sonar does so. I've posted to Canopus' forum
and written to their UK tech support, strongly suggesting that they
teach Let's Edit to do the same. It would save time, memory,
and crashes.
 
G

Guest

Guest
Archived from groups: rec.video.desktop (More info?)

good lord! get a mac, you are beating your head against the wall with
that pc stuff. why even post this issue? crashes? why would it crash?
doesn't make much sense. get a mac and begin to have some fun with video.

http://www.apple.com/software/

http://www.apple.com/hardware/


"Kevin D. Kissell" <deletethisspamtrapKevinK@paralogos.com> wrote:

> Like many people, prior to version 1.06 of Let's Edit coming out last week,
> I had the annoying problem that Let's Edit would crash every time I output
> an AVI file. Unlike most people, however, once I had that crash after an
> AVI file output, any further attempts to launch Let's Edit would cause a
> prompt crash, until I rebooted the machine.
>
> Once I had 1.06, the AVI file output problem went away (not that I
> output AVI files very often), but over the past few days, I noticed that
> the crashes on startup were still there, semi-randomly.
>
> I believe I've just solved that problem. And I'm a little annoyed that
> the Canopus support people didn't pick up the clue that was in my
> very first messages to them on the topic.
>
> I've got Visual Studio on my machine, and thus could drop into the debugger
> when Let's Edit would crash. It reported a bogus access in the module
> VELOCITY.dll. The question that should have been asked was "What is
> VELOCITY.dll, and why is it being invoked by Let's Edit?" I had naively
> assumed that it was some Canopus component. But no. It's a DXi "soft synth"
> that was bundled with a Cakewalk audio package I've also got installed.
>
> Let's Edit is capable of using DirectX audio plugins as filters on
> audio tracks. That's a very nice feature. Unfortunately, Let's Edit
> does not make the distinction between DXi effects and DXi synths
> when it goes through the registry and opens them up. If I open an audio
> effects dialogue in Let's Edit and check the settings on the "DirectX
> bridge",
> my choices include not only all the numerous DirectX audio plugins I've
> got for compression, reverb, EQ, distortion, etc., but also all of my
> DXi software synthesizers: Reaktor, Tassman, Kontakt, Synth1, and...
> "Velocity". As it happens, I never use Velocity (It's a software drum
> machine, of which I have several others that I like better), so I
> de-registered
> it using regsvr32.exe /u. Now I seem to be able to fire up Let's Edit
> with impunity - and it also starts up noticably faster.
>
> I believe that there are actually two bugs here. One is in Velocity,
> because it is obviously thrashing around and crashing when it's being
> probed or opened by Let's Edit as a DirectX effect, while none of my
> other DXi softsynths seem to do so. But the other is arguably in
> Let's Edit (and maybe other Canopus products). It's possible for a
> host program to distinguish between DXi filters/effects and DXi synths.
> I know this because Sonar does so. I've posted to Canopus' forum
> and written to their UK tech support, strongly suggesting that they
> teach Let's Edit to do the same. It would save time, memory,
> and crashes.
 
G

Guest

Guest
Archived from groups: rec.video.desktop (More info?)

Paul Theyrl <pvt@mit.edu> writes:

> good lord! get a mac, you are beating your head against the wall with
> that pc stuff. why even post this issue? crashes? why would it crash?
> doesn't make much sense. get a mac and begin to have some fun with video.

Hereby nominating Paul for the MUPM award this month.
His dedicaton and long hours of helpfull posts have earned him:

MOST USELESS POST of the MONTH status
 
G

Guest

Guest
Archived from groups: rec.video.desktop (More info?)

"Paul Theyrl" <pvt@mit.edu> wrote in message news:eek:vThc.24$vS4.32018@news.uswest.net...
> good lord! get a mac, you are beating your head against the wall with
> that pc stuff. why even post this issue?

Because that way, the next poor bastard can save himself some number
of hours by searching Google.

> crashes? why would it crash?

Because a poorly written module is being invoked with some parameters
that it doesn't know how to handle by a poorly written host program that
doesn't know how to detect incompatible modules.

> doesn't make much sense. get a mac and begin to have some fun with video.
>
> http://www.apple.com/software/
>
> http://www.apple.com/hardware/

Thanks for the free ad for Apple, but video processing is at best the third most
important thing I do with my computers. Some of the others require software
that only runs on PCs, or software that runs so many times faster on an
Opteron than on a G5 that it isn't even funny (i.e. Native Instruments' Reaktor).

There's also the question of pricing. I was a militant Mac owner and PC
refusenik when I lived in the US, but Mac hardware and sofware pricing
here in Europe is even more rediculously inflated than in the US, whereas
PC component prices are about the same here as there.

I'm very happy for you that you have the money to keep yourself in Macs,
and a problem set that fits them. They're really nice friendly machines.
 
G

Guest

Guest
Archived from groups: rec.video.desktop (More info?)

On Thu, 22 Apr 2004 14:14:19 -0500, Harry Putnam <reader@newsguy.com>
wrote:

>Paul Theyrl <pvt@mit.edu> writes:
>
>> good lord! get a mac, you are beating your head against the wall with
>> that pc stuff. why even post this issue? crashes? why would it crash?
>> doesn't make much sense. get a mac and begin to have some fun with video.
>
>Hereby nominating Paul for the MUPM award this month.
>His dedicaton and long hours of helpfull posts have earned him:
>
>MOST USELESS POST of the MONTH status

I second that nomination.

Bunghole