Thx very much, I really appreciate your style of presentation. Not unnecessarily wordy, yet comprehensive and graspable. The tip re ignoring the template except for its very first position was excellent
I love this! Many thanks, as usual, for your overviews of Igor's wonderful creations. I think you could have titled this video as "The Matrix Glitched: BeatCutter for Mad Scientists".
…it is interessting, how the differant iOS channel creators are approaching this crazy new app 🤔 so one can get some new hints out of every video😳...and step by step you get the idea....thank you very much🙏🏻…
Thanks to you I now understand how those bus lines bounce across the matrix diagonally to reach 8 cells 🙏 What's the small grid below the Bus Modes for ?
Thank you so much for this, I don’t own this yet as I’m waiting for pay day, but I will admit to being a bit daunted and at times demoralised watching other people’s videos (no slight on them either!!) but this finally makes a lot of sense and I when I finally grab it I can at least go in with a bit less fear, because sound-wise this is hugely up my street!
Really enjoying so far, seems super clear as always Mark. I like your way of defining busses as a line connecting 8 squares. You have a great knack for explaining Igor's apps. This has become much clearer to me in the days since I made my own video, and I am greatly looking forward to seeing where I am witj it a week a month, a year from now. A deep app, an app for the ages, I love it dearly
Thanks Gavin, it worried me a bit that I managed to make a half-hour video about an audio app with hardly any audio in it :( I am not very good at actually generating stuff from these apps, however fascinating they are. But I hope I will do some more playing with this one, it produces some fascinating textures.
@@AlmostAviation I think it is fine - people, know that your style is more expository. I didn’t go into the matrix enough in my own vid because at that time I was still quite confused but it all became a lot clearer over the past few days as I have played with it more. Such a rewarding puzzle of an app
@@GavinskisTutorials The downside to that approach is that it breaks the numeric convention of the template, which introduces its own set of confusions.
I was hoping you were going to do a vid on this. I think some are making it sound more complicated than it is which may prevent people from trying to learn it in the first place. The manual is useful! I figured it out over the weekend!
Yes, the manual contains a lot (as always), but it needs a lot of reading and re-reading as you go. It's a shame it doesn't explain the matrix very well, or actually at all. It would be a mammoth process, but I think there would be a demand (if not a market) for a comprehensive manual to accompany Igor's suite of apps!
@@AlmostAviation I agreed. Also, I guess I didn't figure it all out lol. Did Igor have to tell you how the signal went through the cells diagonally? Or did I miss that in the manual? Anyway, you covered new ground. I think your approach to the order of things you cover makes it more understandable. Thanks!
@@Nomo_Popo No, I had to get that from Igor! He sent me a very useful (hand-drawn) diagram that made it clear and that should definitely be included in any proper manual. It might be discoverable but unfortunately the lines aren't drawn very clearly on the grid even when illuminated and more confusingly, where the bus is split over two diagonal lines it also draws a connecting line between the two, which makes it look like the bus touches lots of other cells.
@@AlmostAviation I realize this video is 2 years old now, but would you still happen to have that diagram Igor sent you and if so, could you post it for us pls?
They refer to the input sources that you have mapped to the numbered input buses. For example, I1 might be an audio file, I2 might be an input channel (mapped to one of C1, C2 C3 or C4). There is one more option, which is the input source labelled 'I1' on the input channel page. This is an indirection, so it maps the input to whatever source input bus 1 is mapped to. (I haven't checked if this indirection is resolved once at the time it is mapped or if it is dynamic.)
I finally worked out getting the effects and filters to work. One remaining confusion (for now :)) is how the app scans the audio files. If I enter a long audio file, say a couple minutes long, it doesn't seem to grab bits later in the file. Mostly I hear pieces from the beginning. I had assumed when you start it, it continually scans through the audio file grabbing bits and pieces based on the trigger and loops back around to the beginning, but it seems like it continually resets to the beginning. Do you know how that works internally? I read through the whole manual but couldn't find anything that explained it.
I can't say definitively, but my brief experimetns show it behaves as you expect - i.e. that it harvests the sounds from wherever it has gotten to in a linear play-through of the source file. I verified this by setting a single input and output bus, loading a very long file and letting it run. If you turn up the 'direct' slider on the INP page (but keep it quite low volume so you can distinguish it from the mangled output), you can hear the input file being played while watching the playback position on the waveform at the top of the screen. You will hear that the mangled playback slices gradually begin to catch up with the direct output. This behaviour may be obscured according to what 'repeat' and 'skip' settings you have on the CTRL page. These will be more or less unpredictable if you are using randomized templates or tweaking blindly.
perfect! and I appreciate it a lot. I didn't get it cause I thought my brain would reject it but with this video, I think I might actually be able to comprehend!
That's my goal! It is a bit disappointing that there isn't a better manual, although once I came to understand what's going on, I did niotice that much of the info is actually there, it's just not explained.
The filter and other effects work on a per-output basis, so if (as is usual) you have more than one output firing at a time it can be hard to tell if a specific effect is happening to any one output. Try arranging for only one output to be firing, then tweak the filter for that one. Here's a video showing an example: ruclips.net/video/ZnZxCD9iPfY/видео.html
@@AlmostAviation Wow! Thank you so much for this! I've spent 3 days trying to get some clarity on how all the pieces fit and was about to give up when I realized the effects didn't seem to work. I'll give this a go today. Per your suggestion, I haven't been using the templates. It does seem to confuse things if one doesn't understand the whole app. Most of Igor's videos show him setting things up using the template, but like you say it seems like a way to set the initial value from one page. I love the potential of this app, but I do wish the UI has less pages and more direct touch connections. To me, a lot of the complexity could be presented so it's easier to understand and operate. Thank you so much for taking the time to make this video and respond. There's still hope!
Thx very much, I really appreciate your style of presentation. Not unnecessarily wordy, yet comprehensive and graspable. The tip re ignoring the template except for its very first position was excellent
Thanks, I appreciate the feedback!
This video was such a game changer for me. Going to watch all of your scaper vids now. Thanks so much!
Woo, great!
I love this! Many thanks, as usual, for your overviews of Igor's wonderful creations. I think you could have titled this video as "The Matrix Glitched: BeatCutter for Mad Scientists".
…it is interessting, how the differant iOS channel creators are approaching this crazy new app 🤔 so one can get some new hints out of every video😳...and step by step you get the idea....thank you very much🙏🏻…
I waited for that!👍🏽Thanks for the focused explanations. Now I will „knock myself out“!🙃
A great addition to the growing number of videos on this headf*** of an app (and I mean that in a good way). Thanks.
Great!
Thanks to you I now understand how those bus lines bounce across the matrix diagonally to reach 8 cells 🙏
What's the small grid below the Bus Modes for ?
That's a map of which buses are muted or in Test mode.
@@AlmostAviation Thanks !
Nice demonstration...good explanation...thx🙏🏽🖤🙏🏽
Great, thanks!
Thank you so much for this, I don’t own this yet as I’m waiting for pay day, but I will admit to being a bit daunted and at times demoralised watching other people’s videos (no slight on them either!!) but this finally makes a lot of sense and I when I finally grab it I can at least go in with a bit less fear, because sound-wise this is hugely up my street!
A very fine explanation of something that can't be explained. :-)
Ha ha, but it's always worth trying :)
Really enjoying so far, seems super clear as always Mark. I like your way of defining busses as a line connecting 8 squares. You have a great knack for explaining Igor's apps. This has become much clearer to me in the days since I made my own video, and I am greatly looking forward to seeing where I am witj it a week a month, a year from now. A deep app, an app for the ages, I love it dearly
Bus route 🤣👍
Thanks Gavin, it worried me a bit that I managed to make a half-hour video about an audio app with hardly any audio in it :( I am not very good at actually generating stuff from these apps, however fascinating they are. But I hope I will do some more playing with this one, it produces some fascinating textures.
@@AlmostAviation I think it is fine - people, know that your style is more expository. I didn’t go into the matrix enough in my own vid because at that time I was still quite confused but it all became a lot clearer over the past few days as I have played with it more. Such a rewarding puzzle of an app
Move over Dr Frankenstein as Igor truly is the MAD SCIENTIST!
There’s a Test button on the Input bus as well, which should allow you to preview the inputs directly.
Yes, so there is :)
Yeah Scott, those test and solo/mute buttons are so useful. Took me a while to see how useful thkse test buttons are
And I totally agree those outer rings should be called A, B, C, D etc, not 1, 2, 3, 4...this confused me massively initially
@@GavinskisTutorials The downside to that approach is that it breaks the numeric convention of the template, which introduces its own set of confusions.
I love your humour!
Well, great :)
I was hoping you were going to do a vid on this. I think some are making it sound more complicated than it is which may prevent people from trying to learn it in the first place. The manual is useful! I figured it out over the weekend!
Yes, the manual contains a lot (as always), but it needs a lot of reading and re-reading as you go. It's a shame it doesn't explain the matrix very well, or actually at all. It would be a mammoth process, but I think there would be a demand (if not a market) for a comprehensive manual to accompany Igor's suite of apps!
@@AlmostAviation I agreed. Also, I guess I didn't figure it all out lol. Did Igor have to tell you how the signal went through the cells diagonally? Or did I miss that in the manual? Anyway, you covered new ground. I think your approach to the order of things you cover makes it more understandable. Thanks!
@@Nomo_Popo No, I had to get that from Igor! He sent me a very useful (hand-drawn) diagram that made it clear and that should definitely be included in any proper manual. It might be discoverable but unfortunately the lines aren't drawn very clearly on the grid even when illuminated and more confusingly, where the bus is split over two diagonal lines it also draws a connecting line between the two, which makes it look like the bus touches lots of other cells.
@@AlmostAviation I realize this video is 2 years old now, but would you still happen to have that diagram Igor sent you and if so, could you post it for us pls?
@@d.g.rohrig4063OK, look here: www.youtube.com/@AlmostAviation/community
I1..n correspond to the inputs of the audio interface?
They refer to the input sources that you have mapped to the numbered input buses. For example, I1 might be an audio file, I2 might be an input channel (mapped to one of C1, C2 C3 or C4). There is one more option, which is the input source labelled 'I1' on the input channel page. This is an indirection, so it maps the input to whatever source input bus 1 is mapped to. (I haven't checked if this indirection is resolved once at the time it is mapped or if it is dynamic.)
Haha bus route
I finally worked out getting the effects and filters to work. One remaining confusion (for now :)) is how the app scans the audio files. If I enter a long audio file, say a couple minutes long, it doesn't seem to grab bits later in the file. Mostly I hear pieces from the beginning. I had assumed when you start it, it continually scans through the audio file grabbing bits and pieces based on the trigger and loops back around to the beginning, but it seems like it continually resets to the beginning. Do you know how that works internally? I read through the whole manual but couldn't find anything that explained it.
I can't say definitively, but my brief experimetns show it behaves as you expect - i.e. that it harvests the sounds from wherever it has gotten to in a linear play-through of the source file. I verified this by setting a single input and output bus, loading a very long file and letting it run. If you turn up the 'direct' slider on the INP page (but keep it quite low volume so you can distinguish it from the mangled output), you can hear the input file being played while watching the playback position on the waveform at the top of the screen. You will hear that the mangled playback slices gradually begin to catch up with the direct output.
This behaviour may be obscured according to what 'repeat' and 'skip' settings you have on the CTRL page. These will be more or less unpredictable if you are using randomized templates or tweaking blindly.
perfect! and I appreciate it a lot. I didn't get it cause I thought my brain would reject it but with this video, I think I might actually be able to comprehend!
That's my goal! It is a bit disappointing that there isn't a better manual, although once I came to understand what's going on, I did niotice that much of the info is actually there, it's just not explained.
Im not able to get the effects or filter to work at all.
The filter and other effects work on a per-output basis, so if (as is usual) you have more than one output firing at a time it can be hard to tell if a specific effect is happening to any one output. Try arranging for only one output to be firing, then tweak the filter for that one. Here's a video showing an example: ruclips.net/video/ZnZxCD9iPfY/видео.html
@@AlmostAviation Wow! Thank you so much for this! I've spent 3 days trying to get some clarity on how all the pieces fit and was about to give up when I realized the effects didn't seem to work. I'll give this a go today. Per your suggestion, I haven't been using the templates. It does seem to confuse things if one doesn't understand the whole app. Most of Igor's videos show him setting things up using the template, but like you say it seems like a way to set the initial value from one page. I love the potential of this app, but I do wish the UI has less pages and more direct touch connections. To me, a lot of the complexity could be presented so it's easier to understand and operate. Thank you so much for taking the time to make this video and respond. There's still hope!