Hi WOK,

Some of the things you mention will eventually get fixed.

I'd recommend you to sign in the LE Beta program in case you aren't. During this Summer we'll probably have new LE beta releases and you'd be a great beta tester. Send me an email to fran ( a t ) ycrdi ( d o t ) com if you are interested.

By EDIT mode you mean the VAST editing, right? or are you talking about the EASY Editor (PARAMETERS page)?

The LE has an EASY editor but then you can get deeper into VAST editing.

The scope of the LE was just to have the EASY editor. That's what we released in 1.00 and that's what we wanted for that product. But users kept asking for the deeper editing and we finally enabled it in 2.00. Some of the parameters in the VAST editor are overriden by the Parameters on the EASY editor, so they might not do much because of that. And that's ok, but they should not crash of course, and that's what we need to fix. But always have in mind that the VAST editing for the LE is just a gift.

Related to playing live with the LE, well, I wouldn't recommend anybody to do VAST editing live in a concert. I'd recommend to have your programs and setups ready and play them live but editing live is something I'd never do with any keyboard. You can see many bands using the PC3LE live without any problem, including Bruce Springsteen or Hall and Oates, to name a few big ones. So, don't have doubts about the LE playing live just because some extra deep editing capabilities are flaky.

Hi,
I found out the same bugs as WOK with my PC3LE last OS version ... but I have other question.
In Bootloader Menu I chose Run Diags and started on the first test field (I think it is test memory, I am not with my LE now); this test wrote 2 rows about testing and ... that was all, 1 - 5 minutes without result, without reaction, exit button did not fuction, nothing, it only helped turn off main switch. Btw. other tests ran without problems to the end.
Is that normal or did I make some wrong?
Thanks for your answer

Hi petersoon,

For diags information better contact support via www.kurzweil.com . They know about those details.

I'd recommend you to sign in the LE Beta program in case you aren't.

I feel like a beta tester already

By EDIT mode you mean the VAST editing, right?

No. Select P53 "Lords B3", activate Percussion (SW6), press EDIT, press BASIC, change output gain, BANG.....

Related to playing live with the LE, well, I wouldn't recommend anybody to do VAST editing live in a concert. I'd recommend to have your programs and setups ready and play them live but editing live is something I'd never do with any keyboard. You can see many bands using the PC3LE live without any problem, including Bruce Springsteen or Hall and Oates, to name a few big ones. So, don't have doubts about the LE playing live just because some extra deep editing capabilities are flaky.

Imagine you bought a car, and always when you switch on the lights and then want to change the radio station, the car stops. And the salesman says "we wouldn't recommend anybody to change the radio stations during driving. We'd recommend to have your radio stations ready before leaving the garage".
Would you buy a car from that company again

We are not talking about a small bug that might happen after 20 strange function calls. We talk about a basic editing function that makes the complete user surface of the keyboard hang.
I never had this with any keyboard I owned in 20 years. And the bug is known at Kurzweil and their only answer is: "..yes we are aware and planning an update but no date has been set for release. My best guess at the moment is it will still be a few months.." (last OS update is one year ago )

Bugs like this could be acceptable at a 50$ Arduino DIY project or a Windows Shareware, but not in a 1000$ Keyboard meant for professional usage. And I just encountered them after some hours of use. What else may be under the hood?

Hi,

I hear you.

First, to everyone in this forum, whatever I write here is not on behalf of the company, just my opinion as an engineer. So, take it as such.

I expect that some of those edit KB3 issues on the PC3LE will be fixed during this Summer. That's what I think it might happen. I'd expect some Beta releases when things are being fixed, so, seeing those Beta releases will be the first sign that those bugs are being addressed. It's great that you are in the Beta group so that we could check directly with you to make sure those issues are fixed.

Thanks,

Is it also a bug, that in Setup mode I can not pan the A-Piano and most orchestra sounds? (Page PANVOL > EntryPan does nothing or changes the sound just a bit when grand piano, strings etc. are selected for the zone)

Hi,

That's not a bug.

Setups send MIDI pan properly, internally and externally.

MIDI pan is just a part of the pan system.

Programs respond to pan in different ways as you can see inside VAST in all the pan parameters they have (go to the OUTPUT page). Plus, effects can also affect panning.

Hi,

That's not a bug.

Setups send MIDI pan properly, internally and externally.

MIDI pan is just a part of the pan system.

Programs respond to pan in different ways as you can see inside VAST in all the pan parameters they have (go to the OUTPUT page). Plus, effects can also affect panning.

OK, so I make a setup with a split of an organ and a piano.
Now I want the Piano at Output L, the organ at output R. How do I do this? Even with "FX Allocate" 1:N 2:N, "AUXFX1/AUXFX2" Override: yes, Chain: None, Send: 0 it doesn't work.
So in Setup mode, the PAN parameter does not override the output pan setting of a program? Then it's pretty useless - I have to make a separate program for each piano or orchestra sound that I want to pan in a different way in a Setup than in a Program ?!

Hi,

So in Setup mode, the PAN parameter does not override the output pan setting of a program?

Correct. It is much more flexible than just that. In Setup mode, you just send MIDI pan.

In VAST, pan is much more than just MIDI pan. Read the PC3LE manual page 6-37.

For example, an important part about this:

Pan Mode
When the mode is Fixed the pan position remains as defined with the Pan parameter, ignoring
MIDI pan messages. When the mode is +MIDI, MIDI pan messages (MIDI 10) will shift the
sound to the left or right of the Pan parameter setting. Message values below 64 shift it left,
while those above 64 shift it right. A setting of Auto assigns the pan setting of each note based
on its MIDI note number. In this case, Middle C (MIDI note number 60) is equivalent to the Pan
parameter’s setting. Lower notes shift increasingly left, while higher notes shift increasingly
right. A setting of Reverse shifts low notes right, and high notes left. MIDI pan messages will
also affect the pan position when values of Auto and Reverse are selected.

But always have in mind that the VAST editing for the LE is just a gift.

I wouldn't bother looking twice at PC3LE if it wasn't for that gift. I don't see much value in this kind of product without full editing in 21st century.

Hello,
for a long time, year and half, nothing happened about fixing bugs of 2.1 OS for PC3LE. I am really disappointed of this, and I have a filling that that OS 2.1 will be the last one for PC3LE.
I will be very happy that I am wrong.
Good luck for all Kurzweil users.

Hi,

We are working in fixing those issues that have been reported.

....

My LE7 is running flawless. Good work kurzweil.

I think OS of LE7 and LE6 should be the same. So do you have 2.10 and trying the above (select KB3 organ, change percussion, enter edit mode, change anything (volume, leslie, overdrive) = crash ?