1.7.8 update

[constellation]

What's new in this firmware?

[LPF83]

What's new in this firmware?

I'm guessing it may be similar to the recent OB6 update, where changes were needed for internal Sequential development matters but do not change anything from the end user standpoint.

[agusajs]

What's new in this firmware?

I'm wondering the same. They just upload it there and say nothing else...
Did anyone tried it already?

[Rich303]

1.7.8 is now replaced with 1.7.5.
The OB-6 got rolled back too.
I'm not sure what happened. But I'm concerned, having both synths. So I'll play it safe and downgrade.

[constellation]

My P6 had weird noise issues with 1.7.8.
Downgraded to 1.7.5 and everything seems back to normality..

[G3cd]

Downgraded to 1.7.5 and everything seems back to normality..

Note that some of the newer batches of the Prophet 6 came with Os 1.7.7 or 1.7.8 pre-installed.

These are NOT COMPATIBLE with Os 1.7.5 and downgrading those will brick them!

[gus]

What's new in this firmware?

I'm guessing it may be similar to the recent OB6 update, where changes were needed for internal Sequential development matters but do not change anything from the end user standpoint.

This is right  1.7.8 is an update for the production line, and has no new features/fixes. It can cause issues on older units, so we pulled it from the main site temporarily until we have a universal OS.

In short, there aren't any new features/fixes in 1.7.8. From the user standpoint, 1.7.8 and 1.7.5 are identical. If your unit ships with 1.7.8, do not downgrade. If you are on 1.7.5 and your unit works, no need to upgrade.

We are updating the text on our main site to reflect this, as some users have downgraded in confusion (which is understandable).

[LPF83]

Just a suggestion -- I think it would be beneficial for Sequential/Oberheim to develop an updater application that can detect serial number differences on the unit and make adjustments to the update process as necessary.  The problem with "send and forget" sysex dumps is that it's somewhat dangerous (and ultimately more costly to support) to rely on the customer to know which variation on the install process to use, or to read a lot of conditional if-then verbiage or similar.

[Johnny6]

My P6 had weird noise issues with 1.7.8.
Downgraded to 1.7.5 and everything seems back to normality..

Hey I just did the 1.7.5 update, via midiox.
It hung at the last countdown 1, but powered back up working fine.

I'm wondering what this comment meant:

>>You may need to reset your globals after updating (GLOBALS + WRITE).

from here
 
>>https://forum.sequential.com/index.php/topic,97.msg56445.html#msg56445


Is GLOBALS + WRITE really a button combination?  It doesn't seem to be.

I'm excited about all the updates to the arp and sequence sync, since my prev OS 1.2!

[Johnny6]

hope this is ok for the current topic

>>Feature: New Global Param: Arp Beat Sync On/Off. Global row 2 number 9

When I turn this ON, the arp syncs nice,, but then local/manually-played notes are disabled? until I turn arp off, then I can play notes.  Does that sound correct?  Seems weird. 

I would like to add some changing notes in the arp, manually,over the DAWs midi notes.

*there is some sequence of events btwn these
Global1 MIDI CLOCK = IN
Global2 Arp Beat Sync On/Off = ON
.. which results in the local keys stopping working, when arp is on,
until I turn global row 2 #9 off again, but I can't nail it down exactly. urgh

[thirteen_engines]

Hey I just did the 1.7.5 update, via midiox.
It hung at the last countdown 1, but powered back up working fine.

This is quite common with the P6. In fact, for the many updates that I’ve done, only once has it completed the countdown. Every other time it has “hung” at one. A reboot has always come up with the newly loaded firmware.

As far as the Globals + Write question goes, I think that must be an error. Simply tapping Globals a couple of times does the write function.

[Oblong]

You can reset globals on the P6 (and OB-6 and Trigon-6) by holding GLOBALS and hitting WRITE. You may be fooled because doing this puts you into the Global menu, which you must then exit by hitting GLOBALS twice more. However, you can easily verify that you have indeed reset globals just by checking any settings that may have changed.

So to answer your question - yes, holding GLOBALS and hitting WRITE does reset all global parameters. Simply hitting the GLOBALS button will lock in the default preset, but will not reset global parameters.

[thirteen_engines]

Thanks Oblong. I stand corrected about Globals + Write. It does indeed reset the globals.