No librarian?

[Dewdman42]

what is missing to you in order to write a librarian?

[kimsnarf]

In the midi documentation, I only found everything I need to write an editor (unuseful of course), but not a librarian...Or I need to change my glasses, or you have the complete documentation.

You should be able to access all sounds (registrations, live sets, tones) through the temporary area (for the selected sound) by changing the selected sound (program/bank change). It should therefore be possible to loop through all sounds (i.e. their edited parameters) and store them remotely. The send and receive SYSEX uses the same format, so in theory you should be able to upload the stored sound back again to the temporary area.

What I have not found is a way to automatically save the parameters, so with this solution the user probably has to manually upload one sound (e.g. registration) at a time and store it on the synth itself (with the write button).

Uploading multiple sounds in one step probably has to go through an SVD file and a USB stick. And the user still has to import and store the sounds on the synth itself. I have found some code for working with the SVD format on the GAIA, so hopefully the basic structure will be the same on the Jupiter.

In any case, getting an overview of the dependencies between registrations, live sets and tones is the first and most important step, since this allows the user to decide what to keep and what to delete without breaking any dependencies. So that is what I am working on now. :)

If you have the time, I (and surely others) would be glad if you joined this effort. It is a shame that this great synth is lacking a good way to manage sounds, but that is what independent enthusiasts are for. Let's get to it! :)

[piangio]

[quote][/quote]

[ostrovitch]

what is missing to you in order to write a librarian?

with the bankselect I think I could bring a registration in the temporary area, then I could update
the temporary area (these infos are provided). But if I want to store the sound in memory, I didn't find any code to say I want to write the temporary area to such or such place Inside the memory.

[Dewdman42]

hmm that is not good news. I will see what I can find out too.

[cello]

On the Facebook Jp-80 page, someone's just posted a response from Roland UK about the librarian...

Just to let you know I am preparing a report for Japan to prove that a librarian is essential for the Jupiter 80/50.
All our planet staff are onto it and if you can send me an official email requesting this along with other pointers/requests etc I will add this to my work.

[ostrovitch]

On the Facebook Jp-80 page, someone's just posted a response from Roland UK about the librarian...

Just to let you know I am preparing a report for Japan to prove that a librarian is essential for the Jupiter 80/50.
All our planet staff are onto it and if you can send me an official email requesting this along with other pointers/requests etc I will add this to my work.

Thanks for the info.
Hope, if a day Roland Japan would decide to write a librarian for JP50/80, it won't be only for mac.
If they can't live without apple, at least I hope it could be on Ipad.

[PauloF]

On the Facebook Jp-80 page, someone's just posted a response from Roland UK about the librarian...

Just to let you know I am preparing a report for Japan to prove that a librarian is essential for the Jupiter 80/50.
All our planet staff are onto it and if you can send me an official email requesting this along with other pointers/requests etc I will add this to my work.

Thanks for the info.
Hope, if a day Roland Japan would decide to write a librarian for JP50/80, it won't be only for mac.
If they can't live without apple, at least I hope it could be on Ipad.

Maybe if we can add all JP-80 owners in this forum to that request/manifest, maybe Roland will take a close look to it... Just wondering

[ostrovitch]

Maybe if we can add all JP-80 owners in this forum to that request/manifest, maybe Roland will take a close look to it... Just wondering

Why not? But I'm afraid in Roland's mind they gave the JP80 up yet.

1 Year before I wrote to them on Roland CE site about the librarian, I even didn't receive any
answer.
An Engineer who worked on the Jupiter80 project told me in Roland Japan,
they know users are expecting a librarian, and they know how it's important.
Result, they didn't develop any librarian for the JP80/50, so it means as they "design the future", they don't care about past.
But I'll remember them next time I'll buy a synthesizer.

[RayS]

ostrovitch,... If Roland doesnt care about customers who purchased what they created in the past, then why should we care about what Roland produces in the future? Customer service, loyalty are what makes a company continue to stay in business. Roland's reputation is only as good as its customer service. I damn sure don't need to spend over 3K on a keyboard that isn't going to be supported

[ostrovitch]

ostrovitch,... If Roland doesnt care about customers who purchased what they created in the past, then why should we care about what Roland produces in the future? Customer service, loyalty are what makes a company continue to stay in business. Roland's reputation is only as good as its customer service. I damn sure don't need to spend over 3K on a keyboard that isn't going to be supported

Agree with you, but now, their attitude seems to show they care more about future customers.
And it's why my next synth won't be Roland, or at least if a day I buy a Roland synth again, it means
I'm 100% sure the synth is 100% complete the day I buy it, as I can't trust them for the future.

[trommis]

I'm afraid that this is the Korg OASYS story again: The OASYS was marketed as "future proof" (what a joke). It was supposed to live for years due to frequent software upgrades. The sequencer was not very good (for a $ 10.000,- machine) and upgrades was promised. What Korg did as a response to owners demands, was to dscontinue the OASYS (built like a tank), with the bug ridden "plastic fantastic" Kronos....

Official statement from Korg: "The OASYS was to expensive to make, and to few was sold".

I think this is what the future will be for the Jupiter 80 as well. Users are fed up with lack of support (a librarian is one of the many things the JP80 really needs).

I hope I'm wrong, but I'm afraid that I might be right......

[RayS]

As far as I am concerned all the current flagship synths are problems. Motif has a very difficult user interface, navigation problems with a 1970s button layout, OASYS hardware was outdated when it when it was released, Kronos is a bug-city plastic piece of crap, and now the Jupiter...

One thing for sure is I think the Jupiter is definitely the best pick of all the current lineup.

[PauloF]

As far as I am concerned all the current flagship synths are problems. Motif has a very difficult user interface, navigation problems with a 1970s button layout, OASYS hardware was outdated when it when it was released, Kronos is a bug-city plastic piece of crap, and now the Jupiter...

One thing for sure is I think the Jupiter is definitely the best pick of all the current lineup.

Just no librarian...

But I suspect that this need will be addressed shortly ;-)

[Dewdman42]

Hmm, I think you may be right here. its not possible for ANYONE to write librarian for the JP-80 unless Roland updates the midi implementation to include a midi command for writing the current temporary memory to preset slots, which it does not appear to include now, or some info on how to write to the preset data areas.

so if anyone from Roland tries to you tell you that 3rd party should write librarian, the response is, we can't, their keyboard does not support it with the current firmware. That is also, unfortunately why nobody from Roland can do it either, unless/until the engineers that actually update the JP-80 itself will recognize this deficiency and update the firmware, which I feel is highly unlikely to happen.

So we should all get used to the idea that the JP-80 is probably never going to have a librarian.

The next possible way to deal with this is to reverse engineer the file format used on the USB stick and try to write something that can manipulate that, but no matter what could be done that way after a lot of work, it would be hoaky and inconvenient to use, compared to a normal librarian over midi.

what is missing to you in order to write a librarian?

with the bankselect I think I could bring a registration in the temporary area, then I could update
the temporary area (these infos are provided). But if I want to store the sound in memory, I didn't find any code to say I want to write the temporary area to such or such place Inside the memory.