Thanks. As I sometimes create programs where I can toggle between a Panel A setup and a Panel B setup, the move from one panel to the next might be possible with a morph across a single Layer Scene, but some might prefer the capability to start with each Panel being assigned a Layer Scene to switch back and forth.Nord33 wrote:Seems like a pretty nice idea. There is probably no need for A&B from S3 to different layer scenes on S4, but only A&B from S3 to A&B engines on S4 as it has those. Synth C would be the only one "unassigned", but as you said, that already does half of the work if not more.
Designing the tool to import the program bundle is a great idea. I think conversion of the synth settings of basic sounds like a sawtooth vintage synth and samples barely tweaked (mellotron samples) could be nearly identical, however anything beyond 1:1 matches would just be ballpark settings of the OSC, while AMP and ENV filters, LFO, and Effects could be easily mapped IMO.florence wrote:yes great idea.
[dream=ON]
Could even be included in the Nord Sound Manager, when connected to NS4, import program/bundle from NS3 and magic it convert it to NS4...
[dream=OFF]
now wondering if a 100% conversion will be possible. From NS2 to NS3 the Synth section was already different, example FM quite impossible to translate...
I share the same concerns regarding commitment, though I think increased sales would well offset the cost. Sharing the structure of their program files could drive development of many tools by third parties, however that would add another cost element to the NS4 purchase decision if not "free". Though I would definitely consider purchasing a tool to save me hours of programming time, that tool would have to be very good, whereas offering a tool for free also allows the opportunity to say "don't expect the conversion to be perfect" (however, for many programs focused on piano and/or organ, they could be). A synth conversion presetting my AMP and ENV (both ADR), LFO, and Effects are straightforward; estimating the OSC is where Nord just needs to get us in the ballpark.maxpiano wrote:I share the same view with @anotherscott and let's remember that also for other brands like Yamaha (and maybe also Korg) conversion tools were initially an independent external SW developer initiative; it would be enough if Nord would make the structure of their Program files and/or Sysex public (what @florence had to reverse engineer by himself instead, while other companies often include that in the MIDI Implementation specs) then the responsibility of the conversion tool would be left on the potential developer, even if with some risk for the brand also in this case (in fact also for the NS2/3 Program Viewer Clavia asked @florence to put a disclaimer statement on the File Viewer for Nord Stage website)anotherscott wrote:Yeah, they've never done it before, even when the fundamental architecture of the board was much more similar (i.e. two slots of sounds, each with a piano, an organ, and a synth), so I doubt they'd do it now, even though the effort people have put it their old patches is something that stops people from upgrading, and even something "in the ballpark" would be a great time-saver. Maybe Nord feels that the resources required (e.g. having to hire another programmer to do it) would cost them more than the incremental sales they would get, especially if they know that the final result would indeed be something only very roughly in the ballpark, and so they also know they would get a lot of complaints about what a bad job it did, further reducing the potential upside of those increased sales.florence wrote:yes right, would be starting point only. But question is will Nord put time and resource for such feature? Was never the case in the past...
I agree. I just want something that's going to just get me close, though many converted programs could be almost identical.florence wrote:agree... now 3rd party software would be a simple option if really ALL parameters are documented Sysex... Reverse eng file format is not really sustainable at long term, even if I spent really lot of time for the previous iteration. And would not be ready when users really need it, aka in the short coming months... So only Nord can provide something, and could be very, very simple for them...
Yes, adding the functionality to NSM to output the settings of a program, or even a spreadsheet of the settings of all programs, would be excellent. I think there's real value to Nord in easing the transition to the NS4 - maybe developing the tool and handing it over to the public with documented Sysex could benefit them in sales while allowing them to also walk away from future commitment.cookie wrote:I'm very pessimistic.
I've seen Nord's feedback and "help" on the Nord Stage File Viewer program. That could have been a great opportunity to come up with new features in NSM or other tools, but unfortunately, the small company doesn't bother with that.
Fred
I'm a Nord fan. I can be critical at times, but I haven't worked with a better keyboard for covering everything I do. I recognize it's not a good business model to offer "gifts" that turn into future obligations, so perhaps we can simply ask that Nord consider putting the time into a tool that can be handed off to its loyal customers and benefit them as well
