Arturia Forums
Harware Legacy versions => Origin => General Discussion on Origin => Topic started by: Philippe on May 04, 2012, 09:28:14 pm
-
Hello all Origin users,
A Pre-Release 1.4 firmware is available for download at the following link:
http://www.arturia.net/filesharing/www/?action=d&id=15945434468675757169853685009
We'd like to have your feedback on this version. About the reliability, and about the new features too. If you decide to install this pre-release and find bugs, please contact me.
Thanks and have fun.
-
If I install this to test and I don't like it, can I easily roll back to 1.3, or will I be stuck with this until the stable version is ready?
Andreas
-
You can go back to 1.3.50. But if you save a preset with the new 1.4.0 version it won't be loadable when you go back to 1.3.50. So you should backup first your current presets.
-
Is there any new presets that show the new features like SEM modules?
-
Not yet.
-
I have a version ready but it is insufficiently tested. What I plan is to call for volunteers to test this firmware release. I still need to proceed to some additional tests of the updater (Origin Connection) on different platforms and OS's versions. Should be online tomorrow friday May 4.
Thank you Philippe. You are the man of your word !
BTW, it is late in France now, and here you are still answering forum posts. I hope you are drinking something good... 8)
-
Thanks for clarifying the rollback option Philippe. I've downloaded the update and will try and find time to install and test it next week.
BTW - are any of the 1.3 bug fixes that you mentioned earlier MIDI control related?
Andreas
-
There's a known bug on the version which is available for download. It is a navigation bug in the MULTI page. The new "Multi Level" control is located on the left of the page as you can see in the screenshots in the release notes document contained in the archive. When navigating from a slice to this new control using the left arrow switch you will get stick on the first left slice (slot1). To Reach this new level control on the left you need to navigate using the right arrow until the 4th slice.
-
Something wrong here:
I tried to update my Origin but the process seems to freeze at the beginning. First it asks to reboot O and then to click OK. After powerswiching Origin goes to "Firmware Update" mode but after clicking OK nothing seems to happen in Origin Connection. It says "Progress: Current Step: Rebooting Origin 0%". At the bottom of Connection window, there's "No Origin Found"...
EDIT: I am trying it in Mac OS 10.6.8.
When it gets stucked in such early stage, does it make Origin unstable?
Any ideas how to proceed from this problem?
-
No, the Origin should be stable in that case.
If you haven't tried it already I suggest that you disconnect every MIDI sources - other than the USB port - that may be connected to Origin. Then switch and restart Origin. Wait until the OS has fully started. Then launch Origin Connection. Usually that does the trick when I encounter the same problem. Another possibility is to try the update from another computer, possibly running Windows.
-
I did all tricks Philippe suggested, but still I could not update on mac. However then I tried it on PC and update went fine.
About version 1.4:
I had some problems with my old presets, they sounded different. I don't know exactly what else, but at least it affected to some FX parameters. And because I need all the time my presets, I could not go further with it. So now I am back with 1.3.5
Anyone else have tried it?
-
Hello there
I installed it yesterday, on my lion mac, installation went fine. I have big problems with my older patches, those created on 1.3.5 are ok, those created before seem to be loaded but i can see their name and the keyboard follow is disable so they sound mono and always the same note all across the keyboard until i modify the keyboard follow again. Origin connection is quite unstable too.
I tried the new modules, they are amazing, the fx system seems to be great too, it's a great PRE-update til the problems will be solved.
Later
-
One thing was sure: new OS messed up delay settings and I use it a lot in my presets. At the moment it would have asked too much work to fix all those presets. But more crucial thing: (at least) one multipreset had audiocrackles or dropouts and it seemed to have less polyphony than before. This was a final reason to go back to 1.3.5 and fast. Also, for some reason some presets clearly sounded different and I am not sure that it was only because of new FX system (which seems to mess up some preset FX settings). Most striking difference was with one organ preset, it sounded really different...?
-
I installed the update from windows xp without any problems.
So far I've only played with the SEM Filter, and didn't pay attention to other stuff.
I love the sound of the new SEM filter !
I noticed that if you just want to Change the filter in the Rack or Patch view, the SEM filter doesn't show up in the menu. You have to remove the filter you want to change, and then add the SEM filter.
I need to do a more thorough check-up later.
I hope the new handling of FX doesn't affect the polyphony...
-
Installed the update on Windows 7 64-bit Pro. No problems at all, very smooth.
I've not noticed any changes to preset sounds, everything seems ok on that score.
I've played with the Voice Processor module. When I play the keyboard, the triggers advance the VP steps; when I use the arp, the triggers advance the VP steps; but when I use the sequencer, the triggers do not advance the VP steps :-( More generally, why isn't there a trigger input on this module? I was expecting to be able to trigger this from an LFO, from the sequencer, from anything :-( Am I missing something here? Not really very useful to me if it doesn't have a trigger input I'm afraid.
Andreas
-
Oh, take that back about preset sounds - just noticed that all the effects had been removed from the stadiumMg preset by the update...
Andreas
-
OK, something strange is going on...
Some patches just "fizzle out" after a few seconds, and you can't hear the sound until you change the preset. To be specific, It happened with SuperSaw examples posted on presets and templates zone : http://www.arturia.com/evolution/smf/index.php?topic=5724.0 (http://www.arturia.com/evolution/smf/index.php?topic=5724.0)
The first preset from the group seems to be ok, but others fade away after a few seconds and you can't retrigger the sound.
I also have a preset I've been working on that makes a crackling noise when the joystick is moved. The joystick controls the cutoff and resonance settings. I can't say if that was also happening before with 1.3.5 though...
As far as the FX, yes, it does seem that the settings have changed somehow.
-
Also noticed that even with multieffects disabled I get effects being applied in Multi mode and I can'd see where they're coming from! So, for example, I have a prog with chorus and reverb but no echo (it's a simple mod of heavenly guitar). Plays fine as a single program. Load it into a multi and suddenly it has an echo on it, but there are no multieffects enabled...
Sorry, I'm going back to 1.3...
Andreas
-
Hi Philippe,
Have you any idea what's going on here with those problems all of us have encountered? I can understand that new FX system can mess up presets but what about those crackles or sounds going suddenly silent or having less polyphony? These sound quite serius problems...
P
-
I'm on vacation for the week so it's not easy for me to diagnose your problems because of course I don't have an Origin with me.
Maybe some words about the new MULTI_FX mode vs the "old" one (let's call it SLOT_FX):
- obviously, when in SINGLE mode, everything run (or should run) exactly the same way as in 1.3.50
- when in MULTI mode and SLOT_FX (everything appears greyed in the Multi -> FX page) everything run (or should run) exactly the same way as in 1.3.50. The slots comes in the multi with their effects. EAch slot may own up to 3 effects.
- when in MULTI mode and MULTI_FX (everything appears coloured in the Multi -> FX page) then all the effects and their parameters are part of the multi, and none of these effect settings are saved in the slot. The slot itself is unchanged, that means that when you switch back to the SLOT_FX mode, then the effects programmed in the slot show up. When you switch to the MULTI_FX mode, then all the effects are replaced by those programmed in the multi. In MULTI_FX each slot owns 2 effects connected in serial, 2 effects are global AUX fx, and 2 more effects are global MASTER fx.
- when you load a 1.3.50 multi preset, then the effects programmed in the slots become the effects that will be saved in the multi. Any change made here are saved in the multi and leave the slot presets unchanged.
- when you switch to MULTI_FX, the FX1 and 2 of the slots are connected in serial and they keep their settings. The slot FX3s are discarded. The 4 global FX are empty (or Bypass). Then you can choose to load effects in the AUX and MST locations.
- the settings of the FX1 and 2 of each slot are shared between the SLOT_FX and the MULTI_FX mode.
On my laptop computer I have a simulator of Origin. On this simulator I can reproduce the bug of M0010 which looses its FX settings, but this occurs only when it is loaded as a slot in a multi. It occurs also with some other presets but not all. I'll have a look at it asap.
I cannot check what's going wrong with the SuperSaw presets because the simulator cannot work with a sound bank but with individual files such as those used by the real hardware. I'd be interested to know if this happens when the presets is loaded in SINGLE mode or in MULTI mode (on a slot). An also what are the SERIAL/PARALLEL settings in the Program page.
About the crackles with the joystick I cannot reproduce that with the simulator. It may happen on the machine but it didn't when I played with the joystick the day I posted this version (last friday). I'd need more precise information and data. The best thing to do in that case is to send me the preset showing the problem.
Concerning the VoiceModulator: it is designed to change the output variation when a note ON is received. This is how it works within the OBSem and the module has been ported from that soft synth. Using the Sequencer step changes to trig a variation change would make the VoiceModulator a totally different kind of module. It would indeed be redundant with the Sequencer itself. Anyway I'll ask the guys who "invented" this module their mind about it.
And finally (for this post at least), if you notice a change on the sound on some preset, please send it to me even if it is a factory preset. It may have been changed and possibly corrupted if you saved it under the new 1.4. firmware. And the best would be to have the 2 versions of the preset if that makes sense. I mean the version before the update (should be in the backup) and the one after the update.
-
Too bad I don't have two Origins, one running 1.3 other 1.4, to really check these issues... ;)
Switching OS and comparing presets isn't very easy. Anyway I had a very short time with 1.4 so now it's hard to tell very liably, but I think the problems are in Multi mode. If anybody still have 1.4 I would also like to hear that are those problems also in Program mode?
And to Philippe: have your vacation without too much thinking about these issues...!
-
I disagree that adding extra trigger inputs to the VoiceProcessor would make it redundant wrt the sequencer. The VP has multiple output sets. If it could be triggered from an LFO that would make it a powerful modulation source...
But, as JacksonP said, enjoy your holiday, don't think about this stuff!
Andreas
-
I disagree that adding extra trigger inputs to the VoiceProcessor would make it redundant wrt the sequencer. The VP has multiple output sets. If it could be triggered from an LFO that would make it a powerful modulation source...
Andreas
No closed door.... I'm taking note of your feature request and I'll forward it to our product manager. Adding a TRIG input is easy, but in your case I should also add an extra parameter that tells the module to go to the next variation out when a NOTE_ON happens, or when a TRIG happens. As you can see looking at the VoiceProcessor GUI that there's not many room to draw it.
-
Philippe,
I have installed 1.4 onto my Origin Keyboard and have noticed something strange but am unsure whether I have misunderstood what is happening or the software has a bug.
I have a patch with a long sustaining note and a slow 16 step sequence on Sequence 1 connected to trigger the Oscillators (Sequence 2 & 3 are not connected).
Sequencer Step 1 is switched on (and it's light is on), steps 2-16 are switched off (lights are off) to not trigger the Oscillators.
If steps 2-16 are switched off and all their encoder parameters are at 0 then no sound is heard except the correct one triggered by step one, but if I move any of encoders 2-16 to anything other than 0 then the oscillators are correctly not triggered but the envelope is, which can be clearly heard because the Step one note is still sustaining.
Is this a bug, or am I operating the sequencer incorrectly?
Any help would be appreciated. Thank you.
-
i have the startup tempo set for 80, but it always comes up 120 no matter what program i use. it worked fine in ver 1.3. just beta testing, and playin around.
-
Hi Chimpy,
If I am understanding you correctly, the behaviour is the same with the sequencer under v1.3 too.
If the sequencer trigger is off for a step, then no trigger is sent, but the value of the step is still sent, causing pitch changes. This surprised me, I had assumed that if the trigger was off for a step, then no information would be sent at all for that step. It seems like turning the trigger off for a step is similar to having a slide into a step.
After thinking about it for a bit, I can kind of see why it might be logical for the sequencer to behave like this, but overall it seems to me to be a bug, or at least unwanted behaviour.
Andreas
-
Thanks Andreas,
I couldn't recall whether the same behaviour occurred in V1.3, but it's nice to know that I'm not alone in thinking it a bit odd.
Chimpy.
-
This is the expected behavior. I'd think that this is consistent with the rationale behind the Origin Sequencer. Origin attempts to emulates a real analog step sequencer. On a real hardware (and Origin is a real hardware ;)) you would use a cable and connect the STEP output of anyone of the 3 tracks to some modulation input. If you needed one of the 3 TRIG output, you would proceed the same way and connect a 2nd cable to some trig input in your patch. There's no reason for the analog step signal to be active because there's a trig enabled for the step. Moreover, if it were working the way you suggest we would have to enable the trig on each step to get all the steps active.
What you may be missing is a "mute" option that would enable you to mute a single step.
Or maybe it's me who is missing something here? :)
-
Yes, I think a step mute option is what some of us feel is missing :)
Andreas
-
phillipe:
http://www.doepfer.de/Dark_Time_e.htm
-
I agree holografiqueI I have a Dark Time sequencer too, when the Step is Off then it is definitely Off and doesn't send any data at all.
Thank you everbody for your thoughts and contributions.
Chimpy.
-
Hello Origin users,
I'm sorry but I will not be able to provide the 2nd pre-release today as I posted yesterday. I'll try to finalize this 2nd pre-release asap. Hopefully could be ready on monday or tuesday.
-
I personally think releasing during or at the beginning of a week makes more sense since pre-mature issues (bugs) can be dealt with instantly instead of letting people get all upset over a course of the weekend.
-
Philippe,
Are we getting anything to play with for the weekend...? ???