The Official Sequential/Oberheim Forum

SEQUENTIAL/DSI => Take 5 => Topic started by: tomcc on February 01, 2023, 02:11:57 AM

Title: Bug in the Take 5 Beta OS
Post by: tomcc on February 01, 2023, 02:11:57 AM
I updated to the latest Beta version and all is good. I loaded some patches I purchased and they went into the user banks 
 1 thru 8 patches 1 thru 16 all good . I copied these to banks 9thru to G (16) no problems then loaded another patch list into user banks 1 thru 8. All good . Now have all user banks loaded 1thru 16 patches 1 thru 16. 256 patches total.
When I go into Factory banks 1 thru 8 have Sequential factory patches total 128 factory patches.
When I go into Factory patch banks 9 thru to G (16) they are duplicate of what I have in the user banks.
If I make any changes and save to user banks 9 thru 16 they overwrite factory sound banks 9 thru 16.
So effectively the Factory banks 9 thru 16 are the same as user banks 9 thu 16.
 Has any one else found this to be the case or am I orbiting my own planet??
Please let me know if Im doing something wrong or is this a bug .
Cheers Tom
Title: Re: Factory bank same as User bank
Post by: doudou26 on February 02, 2023, 04:38:40 PM
yes it's the same for me, and when I try to access banks 9-16 in factory mode, factory led turns off...

That's why I created this thread :
https://forum.sequential.com/index.php/topic,6844.0.html
you should read it there are replies and tips, I'ven't already tried (lack of time)
Title: Re: Factory bank same as User bank
Post by: CyberGene on February 03, 2023, 12:49:45 AM
After some testing I can confirm the extended factory banks and the extended user banks are mirrored. Whatever you put in one gets mirrored in the other. Not sure if this is a bug or a feature but I hope it gets fixed, otherwise it would be rather disappointing.
Title: Re: Factory bank same as User bank
Post by: ElecStraTake on February 05, 2023, 09:57:29 AM
After some testing I can confirm the extended factory banks and the extended user banks are mirrored. Whatever you put in one gets mirrored in the other. Not sure if this is a bug or a feature but I hope it gets fixed, otherwise it would be rather disappointing.
Confirmed also on my side.
This is clearly a bug or at least not a feature.

If there are no extended factory banks, we should not been able to select factory banks from 9 to 16/G.
If there are really 8 extended factory banks (9 to 16/G) as stated by cbmd on GearSpace, then they should be different from the user banks 9 to 16/G.

@tomcc,
I don't know if it's possible to edit the thread title to make it clear that this is a bug in the beta OS.




Title: Re: Factory bank same as User bank
Post by: Quatschmacher on February 06, 2023, 03:03:19 AM
Best thing is to email support directly with your findings/bug report. It’s the only guaranteed way it’ll get picked up.
Title: Re: Factory bank same as User bank
Post by: tomcc on February 07, 2023, 12:37:25 AM
Cannot change topic title sorry. I have submitted  a bug report detailing what others have confirmed here.
Title: Re: Bug in the Take 5 Beta OS
Post by: Sacred Synthesis on February 07, 2023, 02:44:40 PM
I've changed the title of the thread as desired.
Title: Re: Bug in the Take 5 Beta OS
Post by: tomcc on February 07, 2023, 10:38:40 PM
Cheers appreciate title change, hopefully we may see some future updates that address the issue
Title: Re: Factory bank same as User bank
Post by: ElecStraTake on February 12, 2023, 10:24:47 AM
I have submitted  a bug report detailing what others have confirmed here.
Hello,
Have you received a feedback / an answer from the support ?
Title: Re: Bug in the Take 5 Beta OS
Post by: tomcc on March 27, 2023, 03:10:36 AM
I may have found another bug. I tried the alt scales and the only one working is the 1st equal temp scale . All the others are blank or play the same note across the keyboard and have ddddddddddddd written in the screen window. I had tried them before update and they were populated . Now most blank or corrupt. HMMMM.
 No answer from support as yet
Title: Re: Bug in the Take 5 Beta OS
Post by: tomcc on March 27, 2023, 08:08:47 PM
Gus from support reached out and emailed the Alt tunings  sysex file which loaded fine. So if any one has similar issues reload the file and good to go
Title: Re: Bug in the Take 5 Beta OS
Post by: ElecStraTake on March 27, 2023, 10:23:06 PM
Would you mind sharing this Alt tuning sysex file ?
Thanks.
Title: Re: Bug in the Take 5 Beta OS
Post by: tomcc on March 28, 2023, 02:32:31 AM
Here it is
Title: Re: Bug in the Take 5 Beta OS
Post by: CyberGene on March 28, 2023, 07:39:34 AM
Where are Sequential representatives posting more often, here or on Gearspace? To me it seems the new firmware development has unfortunately been abandoned and the firmware developer is not posting here anymore. Does anyone have some more information?
Title: Re: Bug in the Take 5 Beta OS
Post by: Oblong on March 28, 2023, 11:16:20 AM
Hi there. I can verify that software development on the Take 5 has not been abandoned. You can keep an eye on the Take 5 forum subject thread to see when new public beta OS versions are released. The release of a public beta assures that we are currently working on a new production release, as is the case here.

Since we are a small company, we are generally quite busy with development of new instruments and OS updates for already released models.

Some of us post on GS, but you will find more frequent drop-ins here on our own forum.

I hope this helps.
Title: Re: Bug in the Take 5 Beta OS
Post by: CyberGene on March 28, 2023, 01:31:42 PM
Hi there. I can verify that software development on the Take 5 has not been abandoned. You can keep an eye on the Take 5 forum subject thread to see when new public beta OS versions are released. The release of a public beta assures that we are currently working on a new production release, as is the case here.

Since we are a small company, we are generally quite busy with development of new instruments and OS updates for already released models.

Some of us post on GS, but you will find more frequent drop-ins here on our own forum.

I hope this helps.

Thanks, that's reassuring. I love my Take 5 and knowing that the firmware will be finalized and the small beta bugs will be eliminated is a great news. Keep up the good work!
Title: Re: Bug in the Take 5 Beta OS
Post by: tomcc on April 06, 2023, 07:46:18 PM
Just completed the OS update to vers 2 and can confirm that the issue of having both extra banks as duplicates has been resolved.
 Once the latest update done and factory banks loaded they are the same initially but any saved changes only affects the user bank. The same as any Seq user banks. So this bug I reported on earlier has been sorted.
Thanks guys . Appreciate your efforts.
Title: Re: Bug in the Take 5 Beta OS
Post by: happyrat1 on December 03, 2023, 03:28:48 PM
Just completed the OS update to vers 2 and can confirm that the issue of having both extra banks as duplicates has been resolved.
 Once the latest update done and factory banks loaded they are the same initially but any saved changes only affects the user bank. The same as any Seq user banks. So this bug I reported on earlier has been sorted.
Thanks guys . Appreciate your efforts.

I've had the 2.0 update for about 2 weeks now.

MIDI problem with Logic Pro.  Using USB MIDI logic can read MIDI input, but does not output back to Take5.

Works fine with my other synths, including a Rev 2 so It's not a software issue.

I believe the problem is connected to the Soft MIDI Thru that is omitted from the new firmware.  In fact, MIDI Thru does not even exist anywhere in the global menus.

Please fix this issue quickly.

Thanks in advance.

Gary ;)

Title: Re: Bug in the Take 5 Beta OS
Post by: lewisfrancis on December 03, 2023, 04:55:28 PM
I've had the 2.0 update for about 2 weeks now.

MIDI problem with Logic Pro.  Using USB MIDI logic can read MIDI input, but does not output back to Take5.

Works fine with my other synths, including a Rev 2 so It's not a software issue.

I believe the problem is connected to the Soft MIDI Thru that is omitted from the new firmware.  In fact, MIDI Thru does not even exist anywhere in the global menus.

Please fix this issue quickly.

Thanks in advance.

Gary ;)

Hey Gary, my T5 with the v2 firmware works fine for me in Logic using the USB connection for MIDI. Are you sure you have the T5 set as the destination in the External MIDI plugin?
Title: Re: Bug in the Take 5 Beta OS
Post by: happyrat1 on December 06, 2023, 06:49:00 PM
I've had the 2.0 update for about 2 weeks now.

MIDI problem with Logic Pro.  Using USB MIDI logic can read MIDI input, but does not output back to Take5.

Works fine with my other synths, including a Rev 2 so It's not a software issue.

I believe the problem is connected to the Soft MIDI Thru that is omitted from the new firmware.  In fact, MIDI Thru does not even exist anywhere in the global menus.

Please fix this issue quickly.

Thanks in advance.

Gary ;)

Hey Gary, my T5 with the v2 firmware works fine for me in Logic using the USB connection for MIDI. Are you sure you have the T5 set as the destination in the External MIDI plugin?

I've tested and retested my MIDI configuration.

A recording made previously with the take 5 refuses toplay but I have the audio recorded as well and with audio muted, aven with take 5 soloed it can record MIDI but not play it back.  Also in my system Numa Compact 2x,  Prophet rev 2 16,  ASM hydrasynth,  Boss DR880, Behringer RD8, Alesis Samplepad Pro and Arturia Keystep Pro.

Everything behaves predictably except the Take 5.

Any other thoughts?

Gary...

Title: Re: Bug in the Take 5 Beta OS
Post by: happyrat1 on December 06, 2023, 07:05:48 PM
Also should mention that MIDI 2.0 is disabled in Logic as well as Hydrasynth.
Title: Re: Bug in the Take 5 Beta OS
Post by: lewisfrancis on December 07, 2023, 09:31:31 AM
I've had the 2.0 update for about 2 weeks now.

MIDI problem with Logic Pro.  Using USB MIDI logic can read MIDI input, but does not output back to Take5.

Works fine with my other synths, including a Rev 2 so It's not a software issue.

I believe the problem is connected to the Soft MIDI Thru that is omitted from the new firmware.  In fact, MIDI Thru does not even exist anywhere in the global menus.

Please fix this issue quickly.

Thanks in advance.

Gary ;)

Hey Gary, my T5 with the v2 firmware works fine for me in Logic using the USB connection for MIDI. Are you sure you have the T5 set as the destination in the External MIDI plugin?

I've tested and retested my MIDI configuration.

A recording made previously with the take 5 refuses toplay but I have the audio recorded as well and with audio muted, aven with take 5 soloed it can record MIDI but not play it back.  Also in my system Numa Compact 2x,  Prophet rev 2 16,  ASM hydrasynth,  Boss DR880, Behringer RD8, Alesis Samplepad Pro and Arturia Keystep Pro.

Everything behaves predictably except the Take 5.

Any other thoughts?

Gary...

There are multiple ways to connect and record external MIDI devices in Logic, which led to much confusion on my part when I first started. Still does, frankly, because some things work as expected in regular MIDI tracks but do not in tracks using the External MIDI Plugin, but the latter method is the easiest to work with.

Which method are you using, and how are your external MIDI devices connected to your Mac? I assume the T5 is connected via USB, which is how I currently connect mine. Most of the rest of my devices are connected via a MIDI Express 128 multiport interface where each device has a dedicated port.

If using the External MIDI plugin method, have you confirmed that the MIDI track that is not playing back on the T5 is actually assigned to the T5 in the External MIDI Plugin?
Title: Re: Bug in the Take 5 Beta OS
Post by: happyrat1 on December 07, 2023, 05:28:50 PM
I've had the 2.0 update for about 2 weeks now.

MIDI problem with Logic Pro.  Using USB MIDI logic can read MIDI input, but does not output back to Take5.

Works fine with my other synths, including a Rev 2 so It's not a software issue.

I believe the problem is connected to the Soft MIDI Thru that is omitted from the new firmware.  In fact, MIDI Thru does not even exist anywhere in the global menus.

Please fix this issue quickly.

Thanks in advance.

Gary ;)

Hey Gary, my T5 with the v2 firmware works fine for me in Logic using the USB connection for MIDI. Are you sure you have the T5 set as the destination in the External MIDI plugin?

I've tested and retested my MIDI configuration.

A recording made previously with the take 5 refuses toplay but I have the audio recorded as well and with audio muted, aven with take 5 soloed it can record MIDI but not play it back.  Also in my system Numa Compact 2x,  Prophet rev 2 16,  ASM hydrasynth,  Boss DR880, Behringer RD8, Alesis Samplepad Pro and Arturia Keystep Pro.

Everything behaves predictably except the Take 5.

Any other thoughts?

Gary...

There are multiple ways to connect and record external MIDI devices in Logic, which led to much confusion on my part when I first started. Still does, frankly, because some things work as expected in regular MIDI tracks but do not in tracks using the External MIDI Plugin, but the latter method is the easiest to work with.

Which method are you using, and how are your external MIDI devices connected to your Mac? I assume the T5 is connected via USB, which is how I currently connect mine. Most of the rest of my devices are connected via a MIDI Express 128 multiport interface where each device has a dedicated port.

If using the External MIDI plugin method, have you confirmed that the MIDI track that is not playing back on the T5 is actually assigned to the T5 in the External MIDI Plugin?

I'll run more tests on the weekend.

All connections are USB.  The MIDI works for the Arturia sequencer routed via USB to the T5  via Midifire, a Mac software MIDI Router so the Mac is sending rerouted info to the T5 successfully.

I see nothing different about my configurations for my other synths.  I have successfully recorded and played back MIDI sequences with logic configured to use the input channels on all synths as well as the Arturia sequencer before the update with totally predictable results.  There have been logic pro updates as well recently but this seems to be specific to the T5.

I am still suspicious that MIDI implementation is buggy because of the absence of MIDI thru control in the Globals Menus.

THAT sticks out like a sore thumb.

Am I missing something?

Gary

Title: Re: Bug in the Take 5 Beta OS
Post by: lewisfrancis on December 07, 2023, 05:51:26 PM
I've had the 2.0 update for about 2 weeks now.

MIDI problem with Logic Pro.  Using USB MIDI logic can read MIDI input, but does not output back to Take5.

Works fine with my other synths, including a Rev 2 so It's not a software issue.

I believe the problem is connected to the Soft MIDI Thru that is omitted from the new firmware.  In fact, MIDI Thru does not even exist anywhere in the global menus.

Please fix this issue quickly.

Thanks in advance.

Gary ;)

Hey Gary, my T5 with the v2 firmware works fine for me in Logic using the USB connection for MIDI. Are you sure you have the T5 set as the destination in the External MIDI plugin?

I've tested and retested my MIDI configuration.

A recording made previously with the take 5 refuses toplay but I have the audio recorded as well and with audio muted, aven with take 5 soloed it can record MIDI but not play it back.  Also in my system Numa Compact 2x,  Prophet rev 2 16,  ASM hydrasynth,  Boss DR880, Behringer RD8, Alesis Samplepad Pro and Arturia Keystep Pro.

Everything behaves predictably except the Take 5.

Any other thoughts?

Gary...

There are multiple ways to connect and record external MIDI devices in Logic, which led to much confusion on my part when I first started. Still does, frankly, because some things work as expected in regular MIDI tracks but do not in tracks using the External MIDI Plugin, but the latter method is the easiest to work with.

Which method are you using, and how are your external MIDI devices connected to your Mac? I assume the T5 is connected via USB, which is how I currently connect mine. Most of the rest of my devices are connected via a MIDI Express 128 multiport interface where each device has a dedicated port.

If using the External MIDI plugin method, have you confirmed that the MIDI track that is not playing back on the T5 is actually assigned to the T5 in the External MIDI Plugin?

I'll run more tests on the weekend.

All connections are USB.  The MIDI works for the Arturia sequencer routed via USB to the T5  via Midifire, a Mac software MIDI Router so the Mac is sending rerouted info to the T5 successfully.

I see nothing different about my configurations for my other synths.  I have successfully recorded and played back MIDI sequences with logic configured to use the input channels on all synths as well as the Arturia sequencer before the update with totally predictable results.  There have been logic pro updates as well recently but this seems to be specific to the T5.

I am still suspicious that MIDI implementation is buggy because of the absence of MIDI thru control in the Globals Menus.

THAT sticks out like a sore thumb.

Am I missing something?

Gary

Huh, not familiar with Midifire -- is that an Apple Audio MIDI Setup replacement? Maybe that's where your problem lies, it's certainly a difference in our setups and I have no problem getting the T5 to respond to Logic MIDI across the USB interface.

Not sure why you are focused on the soft-through feature. I guess it'd be nice to have but it's not something I would need.
Title: Re: Bug in the Take 5 Beta OS
Post by: Oblong on December 07, 2023, 05:55:54 PM
It's good to note that the soft thru feature could be allowing a MIDI feedback loop to form. We usually advise shutting off any soft thru-type functionality.

There's also the really great iConnectivity Mio, an affordable USB-to-MIDI DIN cable type interface, just sayin!
Title: Re: Bug in the Take 5 Beta OS
Post by: happyrat1 on December 08, 2023, 12:50:22 PM
Actually it's my understanding that MIDIfire is actually quite a popular Soft MIDI Router on the mac and there are prpecious few out there to choose from.

I believe it's origins might lie in the JACK audio connection kit popular in so many linux dustributions.

I use it frequently but I have tried with it running or turned off and no difference.

All previously said in this thread has been tested with MIDIfire running or not.

I think Oblong sees my train of thought and this will have to be left til the next firmware upgrade.

The omission of USB MIDI Thru Opetions in the Globals Menu tells me that this was not implemented properly to spec in the first place.

Gary ;)
Title: Re: Bug in the Take 5 Beta OS
Post by: Oblong on December 08, 2023, 01:24:22 PM
Actually, the Take 5's USB MIDI functionality is complete, and is the same as our other instruments. In 99% of cases like this, the issue lies with DAW software and/or MIDI routing setups. Local Off is helpful, as is making sure you are not allowing MIDI loopback to occur.

Always a good idea to reach out to support@sequential.com if you have continued issues.
Title: Re: Bug in the Take 5 Beta OS
Post by: happyrat1 on December 08, 2023, 08:50:31 PM
Actually, the Take 5's USB MIDI functionality is complete, and is the same as our other instruments. In 99% of cases like this, the issue lies with DAW software and/or MIDI routing setups. Local Off is helpful, as is making sure you are not allowing MIDI loopback to occur.

Always a good idea to reach out to support@sequential.com if you have continued issues.

Then why does the problem not rear its ugly head when using the Rev 2 16 at the same time?  Take 5 on channel 7 and Prophet on channel 12?   DAW configurations are identical.
Title: Re: Bug in the Take 5 Beta OS
Post by: happyrat1 on December 08, 2023, 08:53:42 PM
Firmware 1.0.0.2 did not exhibit this behaviour.
Title: Re: Bug in the Take 5 Beta OS
Post by: lewisfrancis on December 10, 2023, 11:38:14 AM
Then why does the problem not rear its ugly head when using the Rev 2 16 at the same time?  Take 5 on channel 7 and Prophet on channel 12?   DAW configurations are identical.

Why are you bothering to set a MIDI channel for the Take 5? Is it not connected to your machine via the USB bus?
Title: Re: Bug in the Take 5 Beta OS
Post by: happyrat1 on December 10, 2023, 02:08:06 PM
Then why does the problem not rear its ugly head when using the Rev 2 16 at the same time?  Take 5 on channel 7 and Prophet on channel 12?   DAW configurations are identical.

Why are you bothering to set a MIDI channel for the Take 5? Is it not connected to your machine via the USB bus?

USB MIDI is an industry standard spec and channels and device IDs are still used to route MIDI signals properly over the USB Bus.

Gary ;)
Title: Re: Bug in the Take 5 Beta OS
Post by: lewisfrancis on December 10, 2023, 03:39:04 PM
Then why does the problem not rear its ugly head when using the Rev 2 16 at the same time?  Take 5 on channel 7 and Prophet on channel 12?   DAW configurations are identical.

Why are you bothering to set a MIDI channel for the Take 5? Is it not connected to your machine via the USB bus?

USB MIDI is an industry standard spec and channels and device IDs are still used to route MIDI signals properly over the USB Bus.

Gary ;)

You must use channels if using MIDI DIN connections and daisy-chaining, or when controlling a multitimbral device, but fwiw that's unnecessary when using the Take 5's USB interface in Logic -- you can just set the track MIDI Destination to the Take 5 and not have to worry about channels anymore. It's a beautiful thing.

Title: Re: Bug in the Take 5 Beta OS
Post by: happyrat1 on December 11, 2023, 01:17:54 PM
Then why does the problem not rear its ugly head when using the Rev 2 16 at the same time?  Take 5 on channel 7 and Prophet on channel 12?   DAW configurations are identical.

Why are you bothering to set a MIDI channel for the Take 5? Is it not connected to your machine via the USB bus?

USB MIDI is an industry standard spec and channels and device IDs are still used to route MIDI signals properly over the USB Bus.

Gary ;)

You must use channels if using MIDI DIN connections and daisy-chaining, or when controlling a multitimbral device, but fwiw that's unnecessary when using the Take 5's USB interface in Logic -- you can just set the track MIDI Destination to the Take 5 and not have to worry about channels anymore. It's a beautiful thing.

It's not that beautiful.  It changes an industry standard with unpredictable results.  Case in point, multisynth setups.
Title: Re: Bug in the Take 5 Beta OS
Post by: lewisfrancis on December 11, 2023, 02:22:20 PM
Then why does the problem not rear its ugly head when using the Rev 2 16 at the same time?  Take 5 on channel 7 and Prophet on channel 12?   DAW configurations are identical.

Why are you bothering to set a MIDI channel for the Take 5? Is it not connected to your machine via the USB bus?

USB MIDI is an industry standard spec and channels and device IDs are still used to route MIDI signals properly over the USB Bus.

Gary ;)

You must use channels if using MIDI DIN connections and daisy-chaining, or when controlling a multitimbral device, but fwiw that's unnecessary when using the Take 5's USB interface in Logic -- you can just set the track MIDI Destination to the Take 5 and not have to worry about channels anymore. It's a beautiful thing.

It's not that beautiful.  It changes an industry standard with unpredictable results.  Case in point, multisynth setups.

How so?
Title: Re: Bug in the Take 5 Beta OS
Post by: happyrat1 on December 11, 2023, 03:25:39 PM
BUG SOLVED!!!

It was a PEBKAC Error.  ::)

Problem Existed Between Keyboard And Chair!!!  :-[

I suddenly realized that I hadn't reset my globals after the update!!!

THAT SHOULD BE A LARGE PRINT WARNING at the end of the page.

I suddenly recalled a similar problem with a Rev2 update last year and it hit me like a ton of bricks.

I apologize for any insinuations against the firmware but truth be told it is a surprisingly easy error to make with occasionally devastating consequences.

Forewarned is fore armed as they say :)

And all's well that ends well.

Thanks for your efforts.

Gary ;)
Title: Re: Bug in the Take 5 Beta OS
Post by: Oblong on December 11, 2023, 04:09:39 PM
Glad to hear there was a simple solution! To note, we always advise resetting globals on all update docs.