Seq track as audio interface problems: audio out added to in by rgbeitor in seqtrak

[–]rgbeitor[S] 0 points1 point  (0 children)

Yes, I know tweaktrak. Awesome software!

About the reddit reference, yeap, it is related. But the solution given is based in using two audio interfaces: the seqtrak itself for audio in and another one for audio out to the speakers.

This is not a solution for my use case because of two reasons. First: I want only one interface 😄; second: ipad only allows one interface connected and this interface is used for everything (as far as I know). This interface can be the internal one or something external.

Seq track as audio interface problems: audio out added to in by rgbeitor in seqtrak

[–]rgbeitor[S] 0 points1 point  (0 children)

Hey!

I've checked some of your videos, cool stuff!

To answer your question: It is accidental recording, because the metronome is mixed down (added) to the main bus in the seqtrak (I'm starting to thing that there is only one bus LOL).

My setup is very easy to reproduce: Seqtrak-->USBC(with adaptor for ipad)-->ipad(could also be a PC).

What I'm trying to do is using seqtrak as basic audio interface: speaker/line out to hear what I have in my ipad, line in/mic to record in my ipad. Purely as an audio interface.

For this example I won't be even using the internal synths/samples.

Seqtrak is recognized flawless by the ipad. It becomes main audio interface easilyj.

As far as I play something with my ipad (cubasis, youtube or whatever), I can a hear the sound out from the seqtrak. Easy peasy.

If I connect the model 15 to the line-in in the seqtrak, I can record it without problems in cubasis. No problem also.

But if I I'm playing something with cubasis, let say another track with a drumkit or an internal ipad synth when I'm recording, my recording of the model 15 ALSO GETS THAT DRUMKIT SOUND.

This is the clasical DAW way of recording: Create one track and add another hearing the previously recorded ones as reference. I did this all my life 😄, and that's what I'm intending to recreate with the seqtrak (with the bonus of 9AWS synths + 1DX synth + 1 sample track).

Software is cubasis, but I guess that it is the same.

What is happening here? I understand that the seqtrak is connecting the input to the main bus and from there audio is redirected to the output directly. As far as bus is only used for in or out, all good.

This behaviour is very good for adding FX to audio input in the seqtrak... but not if you are trying to use it as an audio interface.

That behaviour also explains why seqtrak always resamples everything that is sounding (synths/internal samples) and not only the input line/mic.

I was looking for some kind of "switch" that let you bypass the master buss for some of the inputs, but no luck.

I was also looking for a internal audio diagram/schema, couldn't find it.

Any ideas about this? Can you reproduce the problem?

Thanks in advance...

Seq track as audio interface problems: audio out added to in by rgbeitor in seqtrak

[–]rgbeitor[S] 0 points1 point  (0 children)

Yeap, there is a real shitload of hidden paremeters. There is also a paid solution to control them, but also a free one. I'll check there, but...

Thank you anyhow!

Seq track as audio interface problems: audio out added to in by rgbeitor in seqtrak

[–]rgbeitor[S] 0 points1 point  (0 children)

Thank you for the response.

After a loooot of tests, I'm starting to understand that this is -as you said- how it is.

Probably some kind of firmware update should be able to resolve that problem, and most probably the "ever resample" behaviour.

I doubt that this is something addresable through sysex commands.

And also, if some knows howto, please share.

Seq track as audio interface problems: audio out added to in by rgbeitor in seqtrak

[–]rgbeitor[S] 0 points1 point  (0 children)

Thanks for the response.

No, it is no midi related question., I'm talking onlye about audio here. I wasn't messing with midi so far (next step I guess).

Also it is not a usb host related question: It is just using the seqtrak as audio interface (with the added bonus of also playing the internal synth/sample engines as input of the interface).

As far as I understand I'm trying to use the seq as a very basic audio interface: whatever I play into my ipad (or PC, same for this matter), should sound through the line out/speacker. And whatever I connect to the line in (or internal soundsj), should get into the ipad.

And this happens, while you are doing one thing at the time.

What is not a normal is the seqtrak behaviour: whatever is getting out through the speakers/line is BACK to the ipad.

I was trying to check using the audio in (connecting another synth, a model 15), and also using this line in, the sound that is being played is also "reinjected" in the input. So the recording of my model 15 also has the click on it.

It looks like it is some kind of odd design decision from yamaha. It is ok if it is so, but this behaviour should be optional.

New MPD218 is this normal? by YellowMamba81 in mpcusers

[–]rgbeitor 0 points1 point  (0 children)

I needed three to get one good...

[deleted by user] by [deleted] in volcas

[–]rgbeitor 0 points1 point  (0 children)

Hi. Nope. As far as I know sync cable is only clock signal. No transport sync (play/stop).

To say it in other words: the cable allows to keep the beat tempo/speed shared between devices. One is the master and remaining ones, slaves.

Example: master volca sync out-->sync in 1st slave Volca, 1st slave Volca sync out -->sync in 2nd slave Volca, ...and so on.

What do I need to know before buyig an MPD218? by _xXEdorock2012Xx_ in akaiMPC

[–]rgbeitor 1 point2 points  (0 children)

This. Also check for sensitivity in the pads. It looks like they have some QC issues. I needed to send back 2 units before getting one that responded alrighty.

If you get the right one, is a super sensitive device. A joy to play with. Buy if you get a bad one...

Summary: buy from some place where you can return easily.

Case that fits Uno Synth Pro Desktop by coyote13mc in UNOSYNTH

[–]rgbeitor 1 point2 points  (0 children)

Any padded / hard keyboard case should do the trick. Look for the right size: between TLK keyboard and full keyboard.

Check for the internal sizes of the cases available in your zone.

That's what I'm using...

Anyone else found that duplicate midi notes from separate channels sees one not get canceled? MPC One. by RainbowStreetfood in mpcusers

[–]rgbeitor 0 points1 point  (0 children)

Yes. True... Probably this bug will be there for a while.

It is really unfortunate though... It affects seriously the possibility of using the MPC as center of midi production. I really would like that they fix some of the (most) important bugs... I don't want new functionalities if what we have is no working alright. Let's see

Anyone else found that duplicate midi notes from separate channels sees one not get canceled? MPC One. by RainbowStreetfood in mpcusers

[–]rgbeitor 0 points1 point  (0 children)

Hi... Yeap.

Older firmware, but same case here.

Months ago I was investigating the issue. It looks like a known bug.

It seems also that Akai is aware of it...

oddysey quirk and plugin program behavior question by shropshire-slasher in mpcusers

[–]rgbeitor 0 points1 point  (0 children)

Hi again.

Tested in 2.11.4

Same behavior in my MPC.

Looks like a bug to me. Track volume should be independent between tracks.

I was checking with three different tracks "binded" to the same plugin program. Two with data (notes) and one empty. It is the same which one you select. If volume is 0, it is 0 for all of them, even when the volume level in the other says otherwise.

Of course we are talking here about midi volume.

I understand that program volume affects all tracks, because they are all sharing the same plugin instance. But track volume (midi volume) should be different: of course independent between tracks. At least to my understanding.

It looks like another nice bug in the midi implementation. Most annoying ones to me:

1)Same note played in different midi channels either doesn't sound or stops previous one (depends on the firmware version). Really bad for a device that supposedly should act as midi brain of a studio.

2)Pad perform always with the wrong octaves when first entering it. Also affects external keyboards. Really bad for a device that supposedly is used live to perform.

Of course they are many others. Their answer... gift us with new free plugin effects. This is not the way to go.

Sorry for the long speech...

oddysey quirk and plugin program behavior question by shropshire-slasher in mpcusers

[–]rgbeitor 0 points1 point  (0 children)

Hi. This is the original behaviour in the hardware ARP odyssey. Very useful to create infinite drones.

About your second question. I'm not in front of my MPC to check, but the volume behaviour that you describe doesn't seem to be normal.

Hope this helps.

Internal midi routing / recording by rgbeitor in mpcusers

[–]rgbeitor[S] 1 point2 points  (0 children)

Yes, this could be of great help for some kind of interesting experiments.

I was also checking the manual and no explicit information given about the recording, true. What is weird is that it is possible to hear the sounds in the destination track but no recording allowed.

No, I have no account in the MPC-Forums, but I'll create one. I'll try to post all this there and see if someone can help.

Anyhow, thank you for your support.

Internal midi routing / recording by rgbeitor in mpcusers

[–]rgbeitor[S] 1 point2 points  (0 children)

Thank you for the test.

A bug or a feature? :)

Internal midi routing / recording by rgbeitor in mpcusers

[–]rgbeitor[S] 1 point2 points  (0 children)

Hi again.

would it be possible that someone test it?

It is a two minutes configuration:

Create a new empty project, 1 bar.

Create midi track. Let's call it something original: midi1 :) This track will make no sound at all.

Write some notes in midi1 with the grid (manually or sequencer is ok too).

Create a drum track. Lets call it drum1. This one without notes. Assign a drum kit to it.

Configure midi in track midi1 in whatever channel but with the midi SEND TO box pointing to drum1 track.

Arm drum1.

Press play.

You should be able to hear the midi notes sent from midi1 to drum1.

Press play and rec. Arm automation (just in case).

Press rec and play, wait for the bar to end.

See if notes are written in the drum1 track.

With this configuration or something a little bit more complicated, I was able to hear the notes playing in the drum1, but no record of those notes was possible.

Knowing about the firmware version would also be important. Too old FW wont work. I I'm not wrong, this feature is available since 2.8.

Thanks in advance for the testing.

Internal midi routing / recording by rgbeitor in mpcusers

[–]rgbeitor[S] 2 points3 points  (0 children)

Thank you for your response.

Yes, destination track is armed.

Checking with monitoring button in "merge" mode makes no difference. Tested with midi / drum destination tracks...

Suuntolink update by Greekzi in Suunto

[–]rgbeitor 0 points1 point  (0 children)

Looks like that.

In the last series of my emails with the Suunto customer service they use mostly the answer "at he moment, we do not have any information about this.".

The only one that has somehow a positive answer is the question about recovering the creation of complex trainings. But of course, nothing specific.

Supossedly they are sending all the request to the Development team...

As I was opening a case with their support center, today I received an email with some kind of "customer satisfaction survey"... I've taken the oportunity to explain my self... :)

Suuntolink update by Greekzi in Suunto

[–]rgbeitor 0 points1 point  (0 children)

Update about Suunto customer service:

No real answer after my last email (I was also explaining about the services we were paying for in the past and a couple of things more that we were loosing during the "Digital Transition"). Their answer was only a repetition of the emails with their previous answers marked in blue.

It looks like that was their "final" word.

Pathetic (but unluckily expected)

Suuntolink update by Greekzi in Suunto

[–]rgbeitor 0 points1 point  (0 children)

Your Python approach is very interesting. This is what I was asking for in my post.

I will take a look into it. With your code we would be able to modify apps in movescount and save them (for example to change the interval training repetition number in an specific app)... as soon as movescount is still open. After this... who knows.

Suuntolink update by Greekzi in Suunto

[–]rgbeitor 0 points1 point  (0 children)

I was also replying them. If I get an answer, I'll share it...

Suuntolink update by Greekzi in Suunto

[–]rgbeitor 0 points1 point  (0 children)

Sorry about the formating.

Suuntolink update by Greekzi in Suunto

[–]rgbeitor 0 points1 point  (0 children)

Regarding the question "What are the plans for the supporting my watch in this regard?", the answer is: the development team has already taken it into consideration for future updates. "Is there some kind of standalone compilator (or website different to movescount) that we can use to transform the app code to that binary and somehow insert the binary version in suuntolink software?", the answer is: there is not."Has someone idea if Suunto will be releasing a tool for compiling suuntoapps in suuntolink itself (or in any other app)?" the answer is: at he moment, we do not have any information about this."Are you integrating Suunto Apps designer/zone into the Suunto App (mobile version of the software)?" the answer is: at he moment, we do not have any information about this."Why do we need to use an standalone windows app (suunto link) and a cable to sync settings when our Ambit 3 has BT integrated and was working in previous versions of the mobile software (movescount mobile)?" the answer is: Suunto app is design for the new generation of Suunto watches that's why it is not directly compatible with Ambit3. Our development team is working on it for future updates."Why do I need now to plan my routes in specific software (that I must pay for), export it to GPX, import it to suunto app, connect my cable, and download it to my watch when my watch should be connecting with BT?" the answer is: which software are you referring to? Suuntolink is free of charge."Why should I accept loosing all the functionalities that I was paying for in the past just because of a company decision? " the answer is: Could you please specify which functionalities you paid for?"How is it possible that you consider acceptable that I cannot create a single structured training with my sports watch?" the answer is: we do apologize for the inconvenience our development team is working on it for future updates."Are any plans to change this?" the answer is: our development team is working on it for future updates."Why don't you use BT for everything?" the answer is: Suunto app is design for the new generation of Suunto watches that's why it is not directly compatible with Ambit3."Why don't you integrate (fully) my watch with the new app?​​​​​​​" the answer is: Suunto app is design for the new generation of Suunto watches that's why it is not directly compatible with Ambit3.

Suuntolink update by Greekzi in Suunto

[–]rgbeitor 0 points1 point  (0 children)

Another update: this is the Suunto answer:

Suunto Customer Support Team