blackbox 3.0 beta feedback (current version is 2.9.1)

[focal sounds]

hallo everybody

in 2.9.1

im not seeing seq.midi out to drive external synth

am wrong?

thanx

Me neither. I have no midi out options from the pads info section.
I used to be able to set each pads midi out channel that corresponds with my external gear.
I now only have a global midi out setting in tools.

PLEASE HELP!

EDIT:
I'm reading up on it now in the 3.0 beta release notes. I believe the answer is in there.

[jayneural]

Yes but I think it's supposed to be on the sequences now.

Personally I also liked being able to assign a PAD to a MIDI out though.

That allowed me to start with testing my project with sounds from external synths, then sample them and include them into my project.

[focal sounds]

Me too .. but the new arrangement for midi/seq has some pros.
It's nice that we can now have a more dedicated midi area linked to the sequences.
Though I preferred being able to trigger multiple midi channels from one sequence - which now you can't (unless I'm missing something?)
Each sequence is only able to trigger one midi channel. So it uses up more sequences. Saying that - there is now the A,B,C,D parts to each sequence.
I'm gonna keep playing around with it...and report back.

[renacuajo]

i also think that each pad should keep the possibility of assigning a MIDI OUT channel... sometimes i like to play samples that also control external gear without having to program a sequence! that was actually one of the main reasons i bought the Blackbox when it came out and that really made it stand out from the other samplers in the market (to my knowledge).

Please bring this option back in the final release version!!!!!

[Stewartcz098]

Sorry if this has already been posted but just a comment on the new Song mode. Perhaps I haven't got my head around it yet and, to be honest, I really liked the old Song mode. But, is it the case that you now can't have a sequence starting, say, half way through a Scene (like, recording it in)? You would have to create a new Scene with that sequence on it? I'm also unsure why scenes are automatically tied to the length of a pad that is selected to it - if I want a pad to play through a whole song, that seems to mean I am limited to only one Scene and therefore can't have sequences coming in/out at certain points throughout a song. Is that correct, or am I just not understanding the new interface? Thanks!

[focal sounds]

So from what I can tell.
The Seq page now acts as both a multitude of sequences and a kind of midi thru for triggering external gear - whether being sequenced or not.
This is kind of cool - though slightly confusing as it's using an already dedicated page call SEQ. In hindsight there could have been a midi page.
Still experimenting with it though. Thanks for the update though. I'm unsure if I'll keep this version or roll back.

[upwardspiral]

Lost in Translation:

I noticed something strange in the way old projects are transformed to the new midi-seq format in 2.9.1. A lot of my compositions are merged funny. This happens when there are multiple SEQ in the old firmware dedicaded to the same PAD / Sample. Now there are merged sequences with all the data of prior seperated sequences. Please fix it so these keep being solo instances.

[Steve]

We have not fully addressed backward compatibility yet.

[jgartner]

Is the 3.0 beta still available for download? I can't seem to find the link.

[Steve]

It is. The current version is 2.9.1. You can find it in the blackbox downloads.

[woozy9]

Hey team. Quick idea for the UNDO function. You have BACK button free on the Keys/Slices page. You can set this to UNDO. Would be very convenient. Like you play with slices or keys and can instantly undo it without jumping back to the SEQ page.

[johanduner]

Hi! I'm logged in but there's no download link to beta 3.0 only 2.9.1. What's up?

[-thus-]

This has caused some confusion. 2.9.1 IS the beta version of 3.0.

[focal sounds]

First of all, thx for keeping upgrading this little beast !!!

Lets cut straight into it !

1-Not having a midi IN channel selector per sequence pad is making all of this beautifull update unusable for me.
(Funny how such a small thing can make a disaster in a setup)

I need to have multiple midi input per sequence for my NDLR wich use 4 different midi output for each of is 4 tracks that are sent to 4 different synth.
Only having 1 midi Sequence in/16 out channel (3.0 beta) compare to 16 midi Pad in/16 out (2.15) is a BIG downgrade, at least for me.

2- For live performance switching my midi instrument to the sequence page without 1 midi in per Sequence is a BiG No No for me.

In (2.1.5) i would assing all of my 16 Roland Boutique to a Pad each.
Exemple( Pad1 / Midi in 1 / Midi out 1)
( Pad2 / Midi in 2 / Midi out 2)
(Etc till 16)

And from an external midi device i could select one of my 16 synth. Having this moved to sequence, i would need to have a "Midi Sequence channel selector" (For each 16 sequence pad ) unless there is a midi cc to activate that ?

Just to be Clear the 3.0 beta is way more Functuonal IF and ONLY IF i can have a midi IN/OUT per sequence Pad

3- Bug with Keys page ....
Once again i assing my 16 Roland boutique
to 16 different sequence pad with 16 different midi channel

-If using an external midi controler and selecting one of the 16 sequences (to select 1 of my 16 synth) everything is fine, notes are playing

If i use the Keyboard from the Keys page, notes will not send midi notes to my synth
- UNTIL i manualy input a single note in the sequence midi page.
-then i have to Switch the sequence from A to B to not ear that note and its Working.

Long story short Keyboard from Keys page will not work until there is at least one midi note in a sequence.

Finaly !!!
Thx Soooo Much to everyone at 1010music to not stop working on holder product to push the new ones !!!

Sry for my bad english
Cheers From Quebec Canada !!!

Plus One for this.. Regarding the midi in/out per pad and per sequence. It put a fork in my set up also...

[Andrie]

missing the option to transposes midi sequences + and - a few octaves as a bare minimum

[bobthomas]

I want to change the volume for playback. But I cant find anything. it destroys my monitors.

[dertranb]

if you are using only output 1, use the headphone volume. if like me you want to use the 6 outputs, buy 3 passives mini volume controllers, and that's it. (unfortunately it's 35 Euros each, but in my set up they saved my ass) https://thumbs.static-thomann.de/thu...od/490893.webp

[-thus-]

1. A small mixer (I have one made for stereo audio devices by Maker-Hart) is essential for any setup.
2. This thread is not the appropriate place to discuss this because it is unrelated to the topic. Create a thread in General so that others can benefit from your question and the answers people provide.

[Kaaareeegar]

Thank you 1010 team for the developments, wanted to appreciate as i write.

At present on 2.9.1 the 3.0 beta, and wanted to feedback with the song scenes. As much as the old song sections gets the flack, i really enjoyed the workflow it had and was looking forward to that being developed further. I like the current song scenes too but its dissappointing to not find qualities the song sections had it previously that not having it rolled over at present. And finding a good balance between the two.

precisely the ability to record a scene with changes to sequences and capture that for playback once the recording stopped.

another design feedback, being if this scene is the way forward, then surely the limitation of having only 16 has to be increased. I feel possibility of atleast 64 scenes would be a good place to work with ?

even with the older sections workflow, i missed having the possibility to loop within sections and not only loop one section. For eg just looping section 2 to section 6 while having section 1 to section 8 for playback. in the older workflow there were ways one could dive further and program this possibility. But especially with the current scenes workflow and seeing this as a way to move forward. This interscenes looping could only enhance the song making workflow in design.

[Junglejingle78]

I roll back to 2.1.5 for now

but charge pst in 2.9.1 is supa fast
awesome..
thanx

[Steve]

precisely the ability to record a scene with changes to sequences and capture that for playback once the recording stopped.

Can you explain more about this?

More scenes are coming.

[Kaaareeegar]

In the old song sections, lets say in section A, having 32 bars. While its selected and i press rec and play, i could then on the sequences page activate and deactivate cells and once i stopped recording, it saves the performance in that section. And when i just play section A again, it has all my selections recorded in the same order. It also had pre record sequences on the sections like we have over here now in scenes, where sequences are selected before hitting record / play, only with song sections one could capture the selections as its recording and have the performance saved in it.

With song sections one could build up on sequence selections as it was recording and playing. Really fun workflow.

[Kaaareeegar]

More scenes would be great, looking forward to it.

[jayneural]

Wish :

As it is still in the MIDI features category, any chance we get parameter automation recording over sequences ? I see the feature is quite requested and I guess mentioned in the survey as well that's why I won't post a new request in the wishlist.

For now I kinda hack that by resampling and loading the flattened tracks on another project or directly into my Bluebox, but it's a bit of a workflow killer, especially when you want to do the final mixing refinements on the device.

If it's easier to implement, editing would be done by simply re-recording the selected parameter. Not necessary to build an automation drawing UI, well if possible it would be welcome of course.

[Prydal]

hey, i just tried playing slices with the beta, and can't seem to get it to work`?

It always just keeps triggering the same slice, no matter what note i play.
tried it with midi keyboard aswell internal keyboard.

any help how to properly do that now?

[jayneural]

You’re ô the wrong octave. I think it starts at C3 or C4.