4.38 is here!!!

Antonym wrote:

distortedtekno wrote:it's something i wouldn't care about, as i save to hard disk and never use the internal flash memory.

i wonder if jj could scrap the whole "save to internal mem" thing and make autoload only from mem card or HD so as to free up room for stuff like 300,000 notes and other such maximizations

you know, i think that would be alot more valuable on the internal memory aswell...

i think that and a few other things should be stored on the I-memory, push the idea and see what we can come up with for it.

hes talking about what recycle does when it generates midi files. i wish the mpc did this too. if i could slice my sample, set bars, and convert the hits to a sequence preserving the groove.. that'd be nice..

Rise of EPC wrote:convert slice to sequence?
load to program where you left off?? it doesnt already.. enlighten me.

jhs wrote:hes talking about what recycle does when it generates midi files. i wish the mpc did this too. if i could slice my sample, set bars, and convert the hits to a sequence preserving the groove.. that'd be nice..

a lot of the needed code is already there:

the 1k already recognizes transients (Y) on the timeline (X)
converting and outputting as MIDI-data is just the next step...

didn't someone ask about groove-DNA midifiles to give your own
midi another groove, lately? It would be totally logical to implement
a "generate, load and save" function for Groove-DNA files when
adding a kind of Recycle on the mpc

yeah, i might have to get on this bandwagon too:

'built in recycle' is an _awesome_ idea.

Antonym wrote:

distortedtekno wrote:it's something i wouldn't care about, as i save to hard disk and never use the internal flash memory.

i wonder if jj could scrap the whole "save to internal mem" thing and make autoload only from mem card or HD so as to free up room for stuff like 300,000 notes and other such maximizations

pure speculation on this, but i think the internal memory would be separate from the memory chips used to store the os, if only to prevent data corruption of the os.

Does anybody think this is possible...?

Allowing more than 128mb ram

Maybe 256 or even 512 not that its an absolute need,,,but it would be pretty cool if this was available. Of course this would only be possible if the ram limit was in the software and not a hardware issue.

Can anyone with more knowledge on the 1000 in depth shed some light on this?

Thanks in advance

sleepersriddle wrote:yeah, i might have to get on this bandwagon too:

'built in recycle' is an _awesome_ idea.

that would pretty much seal the deal for me I mean I'm already sold on jj, the 1000 and the os, but it would effectively turn my mpc into my laptop and my laptop into my desktop. that shit would be so **** dope

studio hermit wrote:Does anybody think this is possible...?
Allowing more than 128mb ram

Can anyone with more knowledge on the 1000 in depth shed some light on this?

Thanks in advance

128 Mb is a hardware (addressing) limitation.

anyone else scared their mpc1k's gonna just blow up from all the cool stuff it can do. i mean like literally - overheats then POW! haha

I'M NOT TRYING TO SOUND CRAZY BUT WHAT EXACTLY DO THE 300,00O NOTES DO? LIKE WHATS THE ADVANTAGE OF IT? I HEARD ABOUT IT FOR A WHILE BUT I NEVER HAD THE CORRECT UNDERSTANDING OF IT!!!!

it's 200,000 more than 100,000 notes that you can use in your sequences for midi cc's, qLink data, pong scores...

I think the internal flash should be used to save the startup splash screen bitmaps.

elektrik_muz wrote:I think the internal flash should be used to save the startup splash screen bitmaps.

or else, a series of bitmaps, so you can watch videos on the 1k too! come on, is it a drum machine, or a toddler's toy?

elektrik_muz wrote:I think the internal flash should be used to save the startup splash screen bitmaps.

i would like this too. is a sensless but funny feature, but as i don't boot with my cf too often, a bmp-boot from the internal memory would be awsome. then i could use the internal memory only for 'tools' like metronom-sounds, my boot-bmp and some pgm-presets.

---------------------------------
Bug fix: New OS Ver4.39 9-Feb-2007
---------------------------------
1. [NAME EDIT]
　NUMERIC mode does not work.

2. [GRID]
　Track TYPE=DRUM
　When cursor is on a PAD number, even if it strikes PAD, sound does not come out.

3. [TRIM]
　　F6[EDIT]
　　SILENCE
　　F4[RETRY] does not work.

Changes
1. [GRID]
　A track name is displayed while pressing F1[TRACK].

2. [GRID]
　Track type=MIDI
　Piano roll scale change.
　 From TC value Change into SHIFT+F3[ZOOM IN] SHIFT+F4[ZOOM OUT]

3. [Q-LINK]
　NOTE ON mode
　　VELOCITY is added.

4. [MAIN]
　while NEXT SEQ is standing by. NEXT SEQ is replaced shortly after pressing a START key.

4.39 is out !!