Compile USER AUDIO DRUMS?

I've worked in some AUDYA's, and I am faced with a problem.
It's very uncomfortable to associate USER AUDIO DRUMS when I'm making a new pattern. Especially when you have many user audio drums files on the HD.
I Have tried searching the files numerically when I'm using the the pattern edit, but... without success.

Is not possible to complile them first in STYLE COMPILER?

Thanks

(This is my first posting. Sorry, I'm Portuguese and I'm using a translator)

No..... it's impossible....

But you can you search the files numerically?
In the manual says it's possible ... I tried in 2 Audya's, but without success = /

I think also it is impossible.....

The best way:- When you create USER AUDIO DRUMS, name the drums with a partial name of the style - e.g Soca_A@100.wav (this is used for the STYLE - SOCA, variation 'A'). This way, you can quickly search for any audio drum you want to associate with a style.

Unfortunately, AUDYA cannot associated audio drums that are within a Folder in the USER AUDIO DRUMS folder - otherwise you could simply categorize into folders and have each style have it's own folder with corresponding files within each folder.

Thanks,

AJ

Yes, I understand.
The only problem is that many files, it takes a long time looking for them!

Aj, is expected soon an update of the style compiler?

I think it would be very helpful to have this function.

Thanks

I have a atyle that i cannot add user audio drum.I save and all perfect but when i load the style i get "N" on the style name on menu.Why happen this?

I think when "N" appears, is because the converted pattern is not compatible.

Is not compatible with what? I created the style with audya style compiler.

really? =/ you have compiled the pattern in style compiler via midi file or SD5 style?

midi-file why?

Because it's really strange appear the "N", compile in Style Compiler via MIDI file.

yes indeed and only if i add the user áudio drum

And when you use the AUDIO DRUMS (internal)
It's the same?

AJ can not answer? He should know why it happens...

with the internal everything is fine.Im waiting for a AJ answer

Your wav's files have: 44.1 kHz, 16-bit?

yes