A few wishes...

[Thomas Grubb]

I'd love to see a couple of things (apart from the obvious things) in the next version that I miss from certain other programs:

1) after a bounce, mixdown or image is made, the maximum level is shown. I know it can be displayed in the file manager, but only after the waveform is generated which takes a fair while.

2) after a CD is burnt, a compare-to-image function would be useful - just a null-test to make sure the data on the CD is OK.

Cheers,
Tom

[charlienyc]

super idea on #2 Tom! it would remove all doubts as to whether the image was being generated correctly!

cheers,
-c

I'd love to see a couple of things (apart from the obvious things) in the next version that I miss from certain other programs:

1) after a bounce, mixdown or image is made, the maximum level is shown. I know it can be displayed in the file manager, but only after the waveform is generated which takes a fair while.

2) after a CD is burnt, a compare-to-image function would be useful - just a null-test to make sure the data on the CD is OK.

Cheers,
Tom

[Pierre-André Aebischer]

Hi,

Thanks for the suggestions, now registered in our Task Manager Database under the following references:

1) MT001396
2) MT001395

Cheers

[Bernhard Guettler]

2) after a CD is burnt, a compare-to-image function would be useful - just a null-test to make sure the data on the CD is OK.

Good ideas but #2 might be hard or impossible to implement, given the nature of Audio-CDs which even produced from the very best equipment always have errors, the question is just how many.
But the suggestion could be altered to a error-checking feature maybe instead, with definable limits, how many C1/C2 errors are acceptable etc.?

For a CD-Master without errors I only know of DDP as the way to go.

Cheers
B.

[Graemme]

I'd prefer to see a 'compare CD image to project that generated it' function

In my experience, the majority of Pyramix-related CD problems occur in the image generation phase. Nulling the image against the bus outputs that generated it is the safest.

Hopefully, people will still listen to the CDs they create, even if there's an automated method for 'data-checking' added to the software.

I'm not saying that you guys do this, but I'm amazed at the number of people who rely on the computer alone to check their final product!.

Best,

Graemme

[avi]

Yes, as well as Thomas' suggestions, I would welcome the addition - as Graemme says - of a "check image to project source" function.
From reading this message board it seems as though a variety of unexpected things can occur in generating an image in the first place, and it owuld be great to have some form of computer-validation that there wasn't a drop in the audio in the 71st minute for a brief while!


AVI

[Thomas Grubb]

Hi everyone,

Yes, checking to the original project would also make sense. I'm thinking of the function in Sequoia which does this (as you can burn directly without making an image, then "test and compare" the CD).

Bernhard, this would be more just a compare so that you don't get those calls saying the test CD has clicks in it or the last track drops out. I would imagine it would also be a pain doing a final listen, getting to the last track and then having a audio glitch and having to do the whole process from the start (as much as we like listening to our projects ...

Cheers,
Tom