Oasys Wishlist

[elvisjohndowson]

Hi,
I would like to put in an enhancement request to add double touch functionality for the touchscreen in Disk Mode.

Example of the double touch functionality for the touch Screen in Disk Mode : Double Touch to go into a particular directory. Double touch to select file and pop up a file operation prompt (Load sample, etc,) based on the selected file extension. As long as your finger is on the touch screen, try to make it intuitive and not to make the user move his/her finger all over the touch screen.

Lazy/minimal movements translates to faster speed of operation for musically unproductive tasks (such as load, save, go into sub directories), you should ensure that the user spends as little time as possible doing musically unproductive tasks.

Elvis Dowson

[elvisjohndowson]

Hi,
I would like to put in an enhancement request for adding an option to the Global Mode to support memorizing the current list of multisamples loaded into RAM.

If support for scripting for specifying which multisamples is be to loaded at boot time is not planned in the near future, could you at-least add support so that the OASYS remembers all the multi-samples loaded into memory and stores it in a list and then re-loads all the RAM multi-samples when you reboot the OASYS? This should be fairly easy to do and would help us a lot, especially if we're working on sample library creation projects such as the OASYS Refill Project. This would also help people who store their multisamples on disk in an organized way and likes to load a set of multisamples from different locations.

It would be nice if the RAM multisample list could be save to hard disk and the user can choose which RAM multisample list to load at start-up, thereby resolving the scripting issue support for specifying which set of custom multisamples to load at boot time for the OASYS.

Elvis Dowson

[EJ2]

Hi,
I would like to put in an enhancement request for adding an option to the Global Mode to support memorizing the current list of multisamples loaded into RAM.

If support for scripting for specifying which multisamples is be to loaded at boot time is not planned in the near future, could you at-least add support so that the OASYS remembers all the multi-samples loaded into memory and stores it in a list and then re-loads all the RAM multi-samples when you reboot the OASYS? This should be fairly easy to do and would help us a lot, especially if we're working on sample library creation projects such as the OASYS Refill Project. This would also help people who store their multisamples on disk in an organized way and likes to load a set of multisamples from different locations.

It would be nice if the RAM multisample list could be save to hard disk and the user can choose which RAM multisample list to load at start-up, thereby resolving the scripting issue support for specifying which set of custom multisamples to load at boot time for the OASYS.

Elvis Dowson

You have my vote on that one.

[elvisjohndowson]

You have my vote on that one.

Thanks Eric. I realized that if Korg doesn't want to open up the OASYS and support a scripting interface, the next best thing they could do, was to internally support this by creating a list in memory for all the RAM samples and the locations it was loaded from. Now that I think about it, it is sufficient to store the absolute path of all the *.KSC files and load it in the order the *.KSC files are listed and load it at the time of booting the OASYS. Pretty simple, but saves a lot of time for a whole lot of people!!

Elvis Dowson

[elvisjohndowson]

Hi,
I would like to put in a feature enhancement request for adding an information tab for the design guidelines for a combi, as originally envisaged by the author of the combi.

This tab could hold information about the revision number of the combi, design pholosophy/motivation, controller assignments, playing suggestions and caveats.

Elvis Dowson

[medusaland]

Hi,
I would like to put in a feature enhancement request for adding an information tab for the design guidelines for a combi, as originally envisaged by the author of the combi.

This tab could hold information about the revision number of the combi, design pholosophy/motivation, controller assignments, playing suggestions and caveats.

Elvis Dowson

hi eric,hi elvis,

i totaly agree with you!

kind regards

medusaland

[bo.h]

OK KORG
point taken

the *ONLY* wish I have is the stuff thats in OS 1.2.x

OK?

[Drew FM]

Lets not get too carried away!

[bo.h]

well,
i thought the only resonable reason for the delay of the os is that korg is trying to teach us a lesson,
and i must say i feel a lot wiser now,
actually i think i am as wise now as i can get

[elvisjohndowson]

Hi,
I would like to see support for loading samples stored in the REX2 (Recycle's) file format.

The REX2 files contain the audio data of a stereo loop, the slice information and the original tempo. These files, when used with a sampler or computer program that can read REX2 files (such as Propellerhead Reason or Cubase), you can adjust the tempo and pitch independently of each other. This would be very useful for drum loops imported from sample CDs.

I recall that Dan had mentioned Stephan M. Bernsee in a post of his and it's interesting to note that his formant based pitch shifting algorithm is currently being (or already is) implemented in Cubase. So, I wonder if it's likely that Korg is also considering implementing REX2 support and including Stephan's algorithm for the OASYS? In any case, supporting the REX2 file format and being able to adjust the tempo and pitch independently of each other would be great.

I know that the OASYS sampler has support for tempo and pitch based operations, but would it be possible for someone to elaborate a bit more on the similarities and differences between what Reason/Cubase does and what the OASYS can currently do, in terms of independent adjustment of the tempo and pitch?

I mean, is it possible to increase a sample drum loop's tempo in real-time simply by turning the tempo knob and have everything work file if you use REX2 samples? Can this be implemented on the OASYS? If so, it would be astounding!!

Elvis Dowson

[elvisjohndowson]

Hi,
I would like to have the ability to audition and play back sample stereo files from the internal hard disk or a sample CDROM, prior to loading a stereo sample into memory. This is very important because the OASYS supports only 8.3 characters for the file name and tends to rename longer filenames resulting in a re-ordering of te original samples as read from a CDROM contraining, for example, wave sample data.

For example, if on my CDROM I have two sample files:
Anticipation01_121_C
Anticipation02_121_C

When I read this from the OASYS, it will show me
Anticip1.wav (corresponding to Anticipation02_121_C)
Anticipa.wav (corresponding to Anticipation01_121_C)

So as you can see, the file ordering has changed. When going through a large sample library set, I need to have a laptop next to me and need to double check to see if the correct samples were loaded into memory.

I am also have such a hard time with the 8.3 filename restriction. I have to keep renaming the original sample and the newly created multisample to its original name each time. This is quite tedious when attempting to create new OASYS programs from a sample library (wave/aiff format).

A feature to copy/paste text would also be helpful, when renaming samples and multisamples. Right now, I have to re-type each and everyone from scratch. I spent three hours importing and renaming only a subset of samples/multisamples from a sample CDROM this way yesterday. I have one more sample CDROM that I need to convert to the OASYS format but it has more samples that need to be processesed.

I am left with the feeling that there are a lot of features missing from the OASYS that seriously hamper the productivity of users doing production work (e.g. large number of samples to process and work with at the time of import).

All this pre-processing should be done either completely on the OASYS or on a PC. The sysex MIDI implementation for the OASYS is currently not published, which makes creation of a PC application difficult and the OASYS right now doesn't seem to be so user friendly to someone attempting to work on editing and pre-processing a large set of raw samples. Something should be done to address this point.

Elvis Dowson

[danatkorg]

Hi,
I would like to see support for loading samples stored in the REX2 (Recycle's) file format.

Yes, I'd like to see this too!

Note that REX files are basically a set of samples combined with MIDI data to play the samples. Tempo changes happen by changing the tempo of the MIDI data; pitch changes happen by transposing the samples (just like playing samples from the keyboard). No fancy real-time pitch/time processing is required; that's what makes it such an elegant solution to loop playback.

The OASYS already has a time-slice feature which uses this approach: it automatically slices a loop, and creates MIDI data for playback in the sequencer. It would be nice, however, to be able to load REX data directly, and also to be able to play time-slice samples with their MIDI data in Program and Combi modes, as well as Sequencer mode.

Best regards,

Dan

[Daz]

The sysex MIDI implementation for the OASYS is currently not published, which makes creation of a PC application difficult and the OASYS right now doesn't seem to be so user friendly to someone attempting to work on editing and pre-processing a large set of raw samples. Something should be done to address this point.

The sysex spec is only part of the puzzle when it comes to building multisamples & programs. The actual information required by a developer to create tools to work with KSC/KMP/KSF files is in the back of the Param Guide. I've previously used similar set of the information from the back to the Triton param to create a KSF -> WAV converter, so I know it's enough to code against.

Daz.

[milkojnr]

I would second that request for REX2 file import please!!!

Dan do you magic and make it happen!!!!

[elvisjohndowson]

Hi,
Thanks for the replies, guys!! As I delve deeper into the OASYS, I'm starting to notice little things that affect productivity, especially when doing repetitive operations on the sampler.

Some other things affect the OASYS in general, the most important one being the 8.3 file name restriction.

I guess its probably going to take about 2 years for this platform to mature further. It probably already is quite mature right now, for all the stuff it was originally indended to do, but I think it has to undergo rigourous field use and for feedback from the field to be incorporated back into the product and that make take another 2 years, priovided revelant feedback is incorporated back into the product.

Elvis Dowson