The official Novation forum

Cannot load firmware 1.4

As the Novation community has developed over the years, it has naturally found the bulk of it's voice on Social Media. To ensure we can be there to discuss and support you as best we can, we’ve decided to close the forum.

The conversation isn’t over, though. We’re waiting for you; come say hi.

Also, be sure to check out some of our friends.

As ever, thank you for your support.

Thanks for reading, The Novation Team

If you're having a technical difficulty, get in touch via http://bit.ly/NovationSupport and our technicians will get back to you as soon as they can!

39 posts / 0 new
Last post
virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49
Cannot load firmware 1.4

Hi, I am a new user, just received my UltraNova today.  I am having problems with it and decided to join the forum as I could not find a solution online.

First problem is I am unable to upgrade the firmware.  Out of the box, my UltraNova has firmware:  1.1.03 as displayed at boot up.

I downloaded 1.4, Automap 4.8 & Novation USB  Driver 2.7.   All of this is for OSX Mavericks 10.9.3.  I think the problem is something to do

with "Sandbox" which is denying access as shown here:

 

Quote:
Sandbox: coreaudiod(203) deny file-read-data /Library/Audio/Plug-Ins/Components/UltraNova Editor.component
Sandbox: coreaudiod(203) deny file-read-metadata /Library/Audio/Plug-Ins/Components/UltraNova Editor.component/Contents
Sandbox: coreaudiod(203) deny file-read-metadata /Library/Audio/Plug-Ins/Components/UltraNova Editor.component

 

In any case, when I run AutoMap, it can see I have an UltraNova, but the installer and the Librarian cannot.

If I run the installer, it will briefly flash up "checking UltraNova" and then proceed to install.  At the end of the process I get an option

to get an Update, or Skip.  If I click Update, it never does, but just keeps giving the menu over and over.  When I Skip, the Installer says

everything is successful, and I reboot.  After the reboot, I can load the Plugin into Mainstage 3.x (although it crashed 3 times) 

but I cannot do anything over USB.  As mentioned, Automap sees the UltraNova.  If I run the Librarian, it says "No Device found".

This is my quandrary.  I cannot update, cannot use the Plugin or the Librarian.  I have not tried to drive anything with the synth yet

as I wanted to upgrade it all first. I tried using the wall wart instead of Bus Power when installing and also have the USB direct into

my Mac Pro.  If I check Apple Profiler, the USB menu says the device is connected correctly.

 

Please advise so I get through this....

 

 

rachel

 

 

 

 

 

 

 

 

 

 

 

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Maybe you could try going in to 'Audio Midi Setup' within OSX and removing the ulltranova(s) device(s) within the midi screen and trying again.

 

Those file read errors are a bit concerning though.  Sounds like a mavericks 10.9.3 issue from a while back that i remember reading on the official apple forums - Let's hope not, as from memory people were really complaining about apple causing their once stable machine to run slow and unreliable and in some cases needing a restore from backups.

 

Is this a new install of Mavericks?  Are you able to get to 10.9.5?

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Ok, I am actually on 10.9.5 but it makes no difference. I also note the sandbox errors are for all my third party plugins, which actually load OK in Mainstage so that may be a red herring.

 

I tried a different USB cable, this time to the front port of my Mac Pro.  Still the same.  I deleted the UltraNova from AMS as suggested,
 Automap put it back.  Apparently I need to run Automap to run installer?  I can see Automap recognises my Synth, AMS can see it,
 Apple System Profiler can see the USB device as a Novation but the Plugin and Librarian do not detect a device at all.  I have ensured
 that I can install software from anywhere.   I suspect that the Librarian/Plugin and Installer problem are all related.  Is there an alternate
way ie sysex to load the update?  Interestingly, Sysex Librarian and Mainstage both see MIDI data correctly to/from UltraNova.  I have not
 tried Audio yet - I need to fix this immediate issue first.  Thanks for your input thus far!

 

rachel

 

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

I own a mininova and you can hold some buttons down to perform a manual firmware update - there doesn't appear to be such option for the Ultranova though (?!)

You can get the sysex file from the installer files by right clicking and showing package contents 'if' you can find a way of putting the ultranova into firmware update mode manually.

It would kinda make some (muddled) sense that the librarian and plugin can't see your ultranova if they are expecting it with the new firmware, so hopefully if you can update it all well be well then.

It's worth requesting support via this link as soon as you can, as it can take a few days to get a response:-

http://www.novationmusic.com/answerbase/en/contact.php

Once you've used the form to search for your query an option will appear at the bottom to request help via a form, generally you won't get any official technical support via this forum.

Better still give them a call and they are usually pretty helpful, at least in the UK they've always been good for me.

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Thanks - I have been to the contact form already.  I will do some poking around and see if I can load the FW or at least see if there is a hidden menu as I suspect there may be.  What key combinations are you selecting on the Mini to do this, as a starting point for me?!

 

rachel

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Ah cool.

Mininova instructions are right here:-

http://uk.novationmusic.com/answerbase/how-do-i-manually-update-the-firm...

 

Searched, but nothing for Ultranova - same synth engine, but ultimately different OS i imagine.

 

Have you considered installing the editor/librarian version that matches your current firmware?  Then from that upgrading?  i.e. just to prove if this is a firmware issue, as it may not be.

The more i think about it, why would the firmware update fail to work?  There has to be a bigger underlying issue at hand here.

 

One other thing, incase you have a permissions issue, Have you ran the repair disk permissions tool within the OSX disk utilty?

 

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Sorry just to add to this, try the latest 1.4b3 release from here:-

http://beta.novationmusic.com/releases/ultranova/

 

Looks like there was an issue with the firmware updater 'crashing' and was fixed from 1.4b1 onwards

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

I have made a little progress. I booted back to Snow Leopard and installed 1.1.06 with no problem.  Then I install 1.4b3 and I now have the Global Page reporting that the synth Startup OS is 1.1.03 and Current OS is 2.0.0. 

The problem is the Librarian still thinks that there is no device, but on the first try it actually displayed "My MiniNova" as having 3 banks

of sounds visible, but the "My UltraNova" was blank.  The Librarian definitely is not working properly nor is the installer.

I have got the synth integrated into Mainstage 3.1.1 now - it works as a controller with Local Off and triggers itself correctly.

The Plugin is not working - it occasionally crashes Mainstage when loading but does not react at all eg I cannot change patches,

nor can I run any edit controls, it is just not sensing the device. 

 

Thanks for your help!

rachel

 

 

 

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Novation sent me an sysex file to update with, that is the same as the 1.4b3 update, so it seems you can use SysexLibrarian on the Mac to push updates to the synth.  It has not resolved the Plugin/Librarian issues that mean I cannot use them yet.  This is an extremely fun
synth with great sounds nevertheless, so I am looking forward to doing a lot with it.  I am hoping there is a fix coming for this problem
so I can use the Librarian & Editor a bit.

 

rachel

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Ahhh.. So, how did you perform the update?  Do you just send it via sysex and the ultranova reacts automatically?  Or is there a far more mystical method that involves fresh tree bark and unicorn fur? ;)

And yes, hope it gets fixed soon for you too, but i've not read any other issues like this to be fair.  Don't suppose there's multiple instances running of the editor by mistake is there? Cause if you run more than one it can get itself confused and not connect to the synth in this instance.  Long shot, but thought i'd throw that in there.

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

We are at opposite ends of the time zone, so sorry this is slow!  Yes, I just sent the file supplied straight to my UltraNova with SysexLibrarian, so it clearly has a simple approach to firmware loading.  This is handy to know....

I think When I run the Librarian it is popping up two instances of the app,
one calls itself "Novation Librarian" the other "UltraNova Librarian".  One of the apps declares "no synth detected" and the other "no device detected",
plus one instance I can open the MiniNova folders in "My MiniNova" (even though it is an Ultra) and the other it is greyed out.  The Plugin does nothing, I cannot select any patches or program anything, it is just mute. No data is transmitted/received through the Plug at all.  But Device Aggregation works, and so does MIDI control of all my hardware, so it is  OK to use for now.  Everything works 100% under Snow Leopard though.  I am lucky to have one of the Macs that can dual boot both Snow Leopard AND Mavericks, which has saved
me more than once....

 

 

rachel

 

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Ah that's good to hear.

Be sure to get the free sound packs and try them using the librarian, there's some really good sounds in them, depending on your preferred genre of course.

http://uk.novationmusic.com/soundpacks

 

I'm a sucker for the 1992 - pack :)

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Ye, I have downloaded all the packs and several freelance ones already!  I own an OSCar, so when I saw "Huggett" in there, I knew something of what I am dealing with ;) I love this synth has envelope looping and wavetables. I will upload the soundbanks to Bank D temporarily, while I am waiting for some fixes.  I want to extract the patch names out to midnam format so I can have them visible in Mainstage....

 

rachel

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Interesting, I cannot send a system exclusive dump to Bank D - it is just not happening.  There does not seem to be a receive mode in the Global menu to permit it, I thought it might just accept the dump and load it to whatever Bank I have selected but playing the file via SysexLibrarian does not work, so I am on  Factory programs until I can get the Librarian to work...

 

rachel

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Here is an update:
I was unable to load certain Soundpacks from SysexLibrarian but could load others.
I was able to load Dino but not the others supplied by Novation e.g. 1992 & SuperNova.  Chuckie only partially loaded, giving me some patches but the rest “buffering INIT Patch” in the LCD.
I adjusted the buffer in SysexLibrarian, no difference.
I was able to load some third party patches dumped from someone else’s synth from online.
I was able to dump a patch, any bank, all banks, successfully to SysexLibrarian and surprisingly back again!
I was also able to load the Vocoder Updates A+B via SysexLibrarian.
I still cannot use the Plugin or the UltraNova Librarian - they just do not see my synth.

Can some of you guys help me out, by sending me all the Soundpacks, but dumped back from your UltraNova, but via SysexLibrarian, rather than the UltraNova Librarian? This is a test to see if I can.... 

This is very weird indeed….

Thanks for your help....

 

 

rachel

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

I just a little experiment, as I could not load the "1992" patches to my UltraNova.  What I discovered was the file supplied although a Bulk Sysex dump was just sending the one patch over and over to the temporary buffer, but not loading at all.  I did a comparison of the Novation System ID String in the 1992 file and of a Bulk Dump of INIT VOICE and came up with a discrepancy. 

I then created a text file with 128 Novation SysID strings in the format:

"F0 00 20 29 03 01 7F 01 00 10 00 04 00 09 07"

to

"F0 00 20 29 03 01 7F 01 00 10 00 04 7F 09 07"
and made a copy of the 1992.syx, which I then replaced the first 15 bytes of every patch with the required value, which gave me 40 Patches.

I was then able to load up the 1992.syx file into my UltraNova and it works fine with these patches. 

There is something about my synth that does not like the default Novation Soundpacks, they will not load without such editing for me.

I am going to proceed to edit the Soundpacks and load them up/convert them.  It would be interesting if another UN user could compare

a patch dump of their UN against the original Soundpack used to load it and look at the first 15 bytes of the file.

I would be interested if anyone has a similar problem - I am using firmware 2.0.0 (1.4b3).  I have to do this as I cannot still use the Editor/Librarian...

 

rachel

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Wow you're having to do a lot of work to get soundpacks on!! I only have a mininova so can't send you the banks, i'm sure someone out there may put them up tho?!

One thing - you've got write protect disabled in the global settings of your ultranova i presume?

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Yes, I disabled Write Protect!  I have clipped all the files that needed it and dumped them to & from the UltraNova with no problems.  I do not know what may have changed between file formats, but there was definitely a discrepancy, probably the same one that is stopping the Librarian & Plugin from working. Perhaps the UltraNova firmware 1.4b3 is a mistake that has made it over from the MiniNova code and thus mangled something in the software.  So, for now my dream of quickly knocking out patches using the editor is on hold until they get back to me.  It is a great synth though, but I will have to be patient I guess.  I am hoping I do not have to downgrade anything.  It all works 100% on Snow Leopard though.  It is not an option for me to go back however....

 

rachel

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

i imagine they'll ask you to remove everything related to the ultra, including all the support files etc. and then try a fresh install after that.

I've used the mininova editor/librarian (Which is pretty much the same software) with mavericks without issues so it's not the OS.

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Hmm, yes they did ask me to do all that, with the same result.  My Mac thinks I have a MiniNova, if you see the screenshot.  I think the UN firmware is OK, but something with the software loaded is not right. The Editor does not respond or send any MIDI commands

at all.  This is very strange indeed.  Everything works on Snow Leopard but I cannot work on that unless I want to go back to Logic 6 and all the pain of none of my other software working....

 

 

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Any chance you could screenshot your osx audio midi (Midi studio) window?

And click on the ultranova device within that and select 'Show Info' with the more 'more information' tab open, and screenshot that also?  It's got to do with how the device is identified in there, or it's midi channels etc. which is causing your problem.

 

Also, is Snow Leopard on the same physcial machine? i.e. does Snow Leopard and Mavericks share the same local drive?

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

I am booting Mavericks off its own SSD.  I boot Snow Leopard off a 500Gb SATA disk.  The two Systems are seperate.  I only use SL for 32bit stuff like Unitor Editor control, as I have 4 of them.  I have also included the AMS aggregate device to show it is working properly.  The UltraNova shows up as a MIDI Interface:

Thanks for looking into this.  It has me totally stumped.

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

I'm stumped too, and it's starting to bug me lol.

One thing i will say is that i sometimes get a problem with the mininova being detected, it doesn't happen very often but it's happened a few times and i noticed that a second device appears in my midi studio when this happens, and it has a different icon to the usual one, which is how i know something odd has happened.. 

This is not very scientific i know, but maybe this is a global thing that can be applied in your situation also?!  I don't know! :-/

All i can think right now is to unplug your ultra, and remove that device in the MIDI studio screen, then plug it in to a different usb port and see if that works - because that's what i've done to rectify the issue in the few rare occurences i've had an issue.

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Hmm, yes - I have tried that now and it is still the same issue.  I am going through log files and reinstalling the bundle.  I wonder if there

is a conflict of something within one of the packages?

 

rachel

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Another thing of course, is to remove the Novation midi driver:

1. Unplug the ultra

2. Remove ultranova from MIDI Studio

3. Remove 'NovationUSBMidiDriver.plugin' from Library/Audio/MIDI Drivers

4. Restart

5. Reinstall Novaiton software again.

6. Plugin and see what happens.

 

This must be a real pain for you! :(

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Yep, just went through this all again - same result. I cracked open the Installer .pkg and noted what is installed in the Bundle, so I removed everything listed.  It seems the USB & MIDI Drivers get installed as well, so they are not required as a separate download.   The thing is the Installer "blips" over checking the device and then I have to "Skip"which means it is not sensing it at all. But then everything is in place and the core MIDI & Audio features work just fine.  It has to be a problem with something to do with System Exclusive.  I do not understand why the Soundpacks did not load without me modifying them, I don't get that what I output via Sysex works just fine.  When I updated this, I did it incrementally, installing 1.1.6 then skipping 1.3 and going to 1.4, then via the sysex file given to me by Novation, to 1.4b2 (2.0.0).    Yes, it is a real Pain.  I love the synth itself and have no problems programming it, but the Librarian is certainly important to me so I know how to organise it!

 

rachel

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Are novation still in communication with you?!

Trouble is i don't know how the editor and/or librarian strike up that initial communication, one would suspect MIDI ID and then once the device is located SYSEX data is sent to confirm.

If that's breaking down somewhere, i guess there's a few routes that data travels through, CoreMidi and Novation Midi driver being the main two.  But without knowing for sure this is near impossible without you keep messing about deleting/adding stuff and restarting etc.

 

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Yes, they have been keeping in touch, which is very reassuring.  I am working through the issues, because it mostly works makes it more difficult to diagnose!

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

That's good to hear!  Hopefully they get you sorted out soon!!

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

I have tried everything now, so I am in Novation's hands.  I have zapped the PRAM, deleted all installed pkgs, cleared the .kext caches, deleted the Saffire MIDI Driver (don't need it) so there are only the absolute drivers, plugins & kexts required to run my system and AMS setup.

 

rachel

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Have you tried vast amounts of wine and crisps?!  Sometimes known to work ;)

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

The crazy part, it *almost* works, that is to say, the problem everyone else would have, ie audio & MIDI on the USB works great,

a dumb thing like detecting the device is whacky.  I am not sure if the Touch feature is working on mine, either.  Despite all this the keyboard action is brilliant and it has meshed into my setup now, so I am not sending it back...

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Isn't the touch used for animation toggle on/off on the ultra?  Is that not working for you?

And yes, you would imagine any problem would be with the audio over usb etc.  Out of curiosity what midi channel is your Ultranova set to? 

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

The synth is set to MIDI Channel 1. I realised  what you said about the Animate function and yes, it is working!

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Hi there, I just wanted to post here how I resolved my problem myself, through a bit of OS sleuthing.

It may well help someone in a similar predicament.  I have sent the same information to Novation, for their support team.

...

Hi there,
I just wanted to let you know, I believe I have solved the problem with the UltraNova Librarian & Editor.
 
As I come from a Systems background, I always run my Mac with HFS+ Case Sensitive Filesystem.   I ran a dtruss against the Librarian and found
it was failing on a Novation component like so:

… 

sudo dtruss  -a "/Applications/Novation\ Librarian.app/Contents/MacOS/Novation\ Librarian”

750/0x599c:      2932       9      4 workq_kernreturn(0x20, 0x0, 0x1)         = 0 0
  750/0x597d:   2297779      10      6 open_nocancel("/Library/Audio/MIDI Drivers/NovationUSBMIDIDriver.plugin/Contents/Resources/HIDI.bundle\0", 0x1100004, 0x10A35A765)         = -1 Err#2
  750/0x597d:   2297795       7      2 stat64("/Library/Audio/MIDI Drivers/NovationUSBMIDIDriver.plugin/Contents/Resources/HIDI.bundle/Contents\0", 0x7FFF5FBFE998, 0x7FFF5FBFEA7F)         = -1 Err#2
  750/0x597d:   2297806       5      2 stat64("/Library/Audio/MIDI Drivers/NovationUSBMIDIDriver.plugin/Contents/Resources/HIDI.bundle/Resources\0", 0x7FFF5FBFE998, 0x7FFF5FBFEA7F)         = -1 Err#2
  750/0x597d:   2297818       5      2 stat64("/Library/Audio/MIDI Drivers/NovationUSBMIDIDriver.plugin/Contents/Resources/HIDI.bundle/Support Files\0", 0x7FFF5FBFE998, 0x7FFF5FBFEA7F)         = -1 Err#2
  750/0x597d:   2297822       5      2 stat64("/Library/Audio/MIDI Drivers/NovationUSBMIDIDriver.plugin/Contents/Resources/HIDI.bundle\0", 0x7FFF5FBFEF18, 0x7FFF5FBFF02B)         = -1 Err#2
  750/0x597d:   2298018     102     79 lstat64("/Applications/Novation Librarian.app/Contents/Resources/InitPatch.syx\0", 0x7FFF5FBFF3D0, 0x2800)         = 0 0
  750/0x597d:   2298044      19     11 open("/Applications/Novation Librarian.app/Contents/Resources/InitPatch.syx\0", 0x0, 0x1B6)         = 5
0

An “ERR2” is a “not found” Linker error.  The Librarian was seeking a Component that was named differently on my Mac due to the Case Sensitive filesystem.  I made a Symbolic Link like so, to test my theory:

sudo ln -s Hidi.bundle HIDI.bundle
Password:
muse:Resources rachel$ ls -la
total 96
drwxr-xr-x  3 root  admin    238  2 May 01:23 .
drwxr-xr-x  4 root  admin    170  4 Nov 04:44 ..
lrwxr-xr-x  1 root  admin     11  2 May 01:23 HIDI.bundle -> Hidi.bundle
drwxr-xr-x  3 root  admin    102  4 Nov 04:44 Hidi.bundle
-rw-r--r--  1 root  admin  14700  4 Nov 04:44 ReMOTE.png
-rw-r--r--  1 root  admin  10999  4 Nov 04:44 Speedio.png
-rw-r--r--  1 root  admin  15023  4 Nov 04:44 X-Station.png

Upon running the Librarian, I was able to Connect to My UltraNova and it is successfully detected.
Further, I was also able to connect to the Plugin Editor and control my synth with it perfectly!

 

Hopefully this information will help others with my problem...

 

 

rachel

skijumptoes
Offline
Last seen: 1 year 4 months ago
Joined: 03/26/2013 - 13:22

Oh wow good work!!  Pretty sure that will help someone along the line too.

Reminds me of the day i migrated SQL from windows server to CentOS (running ext3) and everything stopped working due to case sensitivity, i make sure anything i code now is case sensitive - 'Fool me once' and all that jazz. ;)

Pleased you've sorted it anyway, there ain't no way i was going to guess at that being a fix lol!!

virag0
Offline
Last seen: 1 year 9 months ago
Joined: 04/22/2015 - 10:49

Yes, I am very pleased with myself ;) My reward is diving into the editor and having fun with it....  The Editor/Librarian together work great now.

Thanks for your help as well....

 

rachel

crystalmsc
Offline
Last seen: 1 year 6 months ago
Joined: 03/27/2013 - 14:12

This is strange, I got a syx file from novation UNF2_0_0.syx with an instruction to send it to the Ultranova using MidiOX. It's now intalled perfectly, but the OS shows:

Current O/S version 2.0.00

Startup O/S version 1.0.02

Is this normal? Because I thougt the latest was OS 1.4b3.

The Editor is V1.4b3 running on Windows 10. Please clear me out about this. Thank you.

crystalmsc
Offline
Last seen: 1 year 6 months ago
Joined: 03/27/2013 - 14:12

Just got a confirmation from Novation that everything is ok. Cheers!