Page 2 of 2
Re: Compatibility NS Classic/EX (nspg) and NS2 (ns2p) patche
Posted: 11 Jan 2014, 14:41
by Mr_-G-
Of course the checksum will differ if you change a parameter. But different manufacturers compute the checksum differently (eg, including all sysex or just the data bytes, then added up and compute the checksum as the "result modulo 128"). The best way is asking Clavia directly. They should provide that information as it is no trade secret, but a functionality feature.
Re: Compatibility NS Classic/EX (nspg) and NS2 (ns2p) patche
Posted: 15 Aug 2015, 09:50
by mintyswirl
Are you f'n kidding me.
I just showed up to a professional, high-profile artist gig.
I have a Stage
They have a Stage 2
I can't load in my old programs
F you NORD!!!
THis is ridiculous it's not backwards compatible.
It's the FIRST thing you do is enable such simple details.
Unreal.
Re: Compatibility NS Classic/EX (nspg) and NS2 (ns2p) patche
Posted: 15 Aug 2015, 13:28
by RedLeo
The Stage 2 isn't an upgraded Stage, it's a completely re-designed instrument. There's no chance of any compatibility between the two.
Re: Compatibility NS Classic/EX (nspg) and NS2 (ns2p) patche
Posted: 15 Aug 2015, 17:24
by pablomastodon
mintyswirl wrote:Are you f'n kidding me.
I just showed up to a professional, high-profile artist gig.
I have a Stage
They have a Stage 2
I can't load in my old programs
F you NORD!!!
THis is ridiculous it's not backwards compatible.
It's the FIRST thing you do is enable such simple details.
Unreal.
Someone at your "professional, high-profile artist gig" skipped the part about being professional. Better you should complain about the backline operator or the TM who wrote the rider or yourself for having failed to specify.
A new instrument will necessarily have new features or else there would be little interest in buying the thing. Technology marches on and musicians want more out of their instruments and as hardware possibilities improve engineers are able to deliver more expansive and novel features. This necessarily results in differing program architecture, simultaneously rendering programs incompatible from one model to another. This is the nature of life in the world of keyboard electronics.
Re: Compatibility NS Classic/EX (nspg) and NS2 (ns2p) patche
Posted: 15 Aug 2015, 23:41
by RedLeo
pablomastodon wrote:Someone at your "professional, high-profile artist gig" skipped the part about being professional. Better you should complain about the backline operator or the TM who wrote the rider or yourself for having failed to specify.
This. But I suspect we are talking to empty air.
Re: Compatibility NS Classic/EX (nspg) and NS2 (ns2p) patche
Posted: 16 Aug 2015, 15:55
by pablomastodon
You're probably right, Red, but I still felt the need to address it for the possible benefit of some other unsophisticated/noob user who might otherwise think that this person had a valid point...
p
Re: Compatibility NS Classic/EX (nspg) and NS2 (ns2p) patche
Posted: 27 Apr 2021, 12:06
by cookie
Bringing this thread back to life, this maybe something we could look to add to the NS2 and NS3 program viewer :
https://ns3-program-viewer.herokuapp.com/
This would mean we would need support from a NS Classic owner to make few tests and share the nspg programs for comparison.
Any volunteers ?
Fred
Re: Compatibility NS Classic/EX (nspg) and NS2 (ns2p) patche
Posted: 23 Feb 2024, 19:38
by SuperTrooper
I exchanged my Nord Stage EX for a Nord Stage 3 last year. I took a backup of the EX and also downloaded my favorite presets as nspg files. I had the optimistic thought I could either upload my presets or look what the synth settings were and rebuild them. But both is a no...
Anyone any idea to view the contents of the nspg files in a usefull way? I don't mind recreating the presets based on the synth settings of the EX, but atm I got nothing...