Beatcutter Released! Detailed walkthrough vid (Winners announced)

Gavinski

I think my first audio example in my walkthrough was pretty musical too

celtic_elk

@Gavinski said:
I think my first audio example in my walkthrough was pretty musical too

That example nearly motivated me to buy Ripplemaker and FRMS, but I figured I’d better do one thing at a time. 😄 I still haven’t spent quality time with the last couple of BLEASS apps....

Gavinski

True though, after my first few days with this and going through cycles of 'I understand this' and then 'do I f*ck' I understand people's frustration. All I can do is repeat I'm glad I stuck it out

Gavinski

@celtic_elk said:

@Gavinski said:
I think my first audio example in my walkthrough was pretty musical too

That example nearly motivated me to buy Ripplemaker and FRMS, but I figured I’d better do one thing at a time. 😄 I still haven’t spent quality time with the last couple of BLEASS apps....

Nice!

telecharge

@Gavinski said:
Fair comment, that is exactly my project now these next few days, seeing to what extent it can be toned down, I'm getting there, I think, but it will take more experimentation to be sure

Godspeed, man. I look forward to your findings.

@gusgranite said:

@telecharge said:
To be honest, most of what I've heard so far sounds like trying to tune in a radio station in the middle of nowhere.

Erm, that's kind of what I'm after that no other app can deliver lol

@celtic_elk said:
I’ve found that to be very rewarding, and tremendously "musical" within my personal parameters.

Glad you both are liking the app.

@Gavinski said:
I think my first audio example in my walkthrough was pretty musical too

Well, I did use words like "mainly" and "most" with the hope that no one would take it personally. Apologies if I plowed too close to the cotton.

Gavinski

@telecharge said:

@Gavinski said:
Fair comment, that is exactly my project now these next few days, seeing to what extent it can be toned down, I'm getting there, I think, but it will take more experimentation to be sure

Godspeed, man. I look forward to your findings.

@gusgranite said:

@telecharge said:
To be honest, most of what I've heard so far sounds like trying to tune in a radio station in the middle of nowhere.

Erm, that's kind of what I'm after that no other app can deliver lol

@celtic_elk said:
I’ve found that to be very rewarding, and tremendously "musical" within my personal parameters.

Glad you both are liking the app.

@Gavinski said:
I think my first audio example in my walkthrough was pretty musical too

Well, I did use words like "mainly" and "most" with the hope that no one would take it personally. Apologies if I plowed too close to the cotton.

No no, you didn't and I didn't take it personally! You're right, most examples with this will sound like chaos cos there is a steep learning curve to getting control, and in still near the bottom of that hill lol but I'm a hella way higher up than most ppl, having had a week on the beta already

Gavinski

Now whether this is to your personal taste or not I don't know. But I could easily imagine doing a few variations of this, laying them down in a DAW, fading between them, maybe addinf more percussion and a bit of playing over the top, some ghostly piano maybe, and having something I would greatly enjoy listening to

Gavinski

Oops:

https://twitter.com/gavinski_s/status/1378535029010092032

celtic_elk

Very nice, @Gavinski!

Will

@celtic_elk said:
The realization that made this app start to make sense for me is this: each cell is a dynamically-triggered sampler. Each of the buses represent a stage in the sample/playback process: the input bus defines the sound source for a cell, the trigger bus defines the conditions for recording (trigger conditions, sample length), the control bus defines important aspects of playback (pitch, direction, how many times a cell plays before it empties, whether its first playback is delayed for one or more cycles), the sequence bus triggers playback (and can contribute to sampling as well, depending on how you set the trigger bus), and the output bus (which has two pages, one for effects/filtering and one for level/pan/EQ) handles downstream processing when a cell is played. Each trigger bus records no more than one cell when it fires; each sequence bus plays no more than one cell when it fires.

It gets complicated from there, obviously, but that’s the basic setup.

“It gets complicated from there.“ spurned a literal lol. The appending of “obviously” spurned another literal lol, once I got that far. Fwiw, I’m a “techie” by most people’s standards.

Again, I’m totally and completely charmed by how complex this app seems. Thankful this app (and it’s creator and it’s purchasers) exist. Not everything should be easy. And, sometimes (usually?), complexity is just part of the deal.

Fingolfinzz

@Gavinski said:
Oops:

https://twitter.com/gavinski_s/status/1378535029010092032

What that bit crushing sound from the app? It sounded really cool

Gavinski

@Fingolfinzz said:

@Gavinski said:
Oops:

https://twitter.com/gavinski_s/status/1378535029010092032

What that bit crushing sound from the app? It sounded really cool

Well, it has a decimate effect, but it also has a thing called Bitmasking which is similar

Gavinski

@syrupcore said:

@celtic_elk said:
The realization that made this app start to make sense for me is this: each cell is a dynamically-triggered sampler. Each of the buses represent a stage in the sample/playback process: the input bus defines the sound source for a cell, the trigger bus defines the conditions for recording (trigger conditions, sample length), the control bus defines important aspects of playback (pitch, direction, how many times a cell plays before it empties, whether its first playback is delayed for one or more cycles), the sequence bus triggers playback (and can contribute to sampling as well, depending on how you set the trigger bus), and the output bus (which has two pages, one for effects/filtering and one for level/pan/EQ) handles downstream processing when a cell is played. Each trigger bus records no more than one cell when it fires; each sequence bus plays no more than one cell when it fires.

It gets complicated from there, obviously, but that’s the basic setup.

“It gets complicated from there.“ spurned a literal lol. The appending of “obviously” spurned another literal lol, once I got that far. Fwiw, I’m a “techie” by most people’s standards.

Again, I’m totally and completely charmed by how complex this app seems. Thankful this app (and it’s creator and it’s purchasers) exist. Not everything should be easy. And, sometimes (usually?), complexity is just part of the deal.

It definitely does get complicated, but for sure Celtic Elk is right that - as long as u stick to one audio source and keep it simple - you can learn a lot by working through the template values one by one

drcongo

I just bought it, though I’m fairly convinced I won’t have the staying power. During purchase the App Store shows the developer name iMusicAlbum in all caps, which my brain can only see as I MUSICAL BUM

Fingolfinzz

I think I’m going to buy this just for the challenge of figuring it out, and it sounds really far out there. Also for those who have bought the app, make sure to leave a rating cos some jackass left a one star review cos they didn’t understand the app

gusgranite

Toastedghost

@Gavinski said:

@Toastedghost said:

@ALB said:
It seems to be a bit hard on cpu for me. Sort of cool all the same. I wish that the matrix worked somehow a bit more like the Apematrix grid, rather than just being a visual representation.

For me I wish you could push on the nodes outside the matrix to physically turn them on and off.
I sometimes find that the internal triggers do not fire as I would have liked.

The main thing I found is that if u aren't getting enough sounds try raising the values on the slider knobs in the 8 trigger windows. Also pay attention to the speed the sequencer circles are moving on the matrix. If top slow you may need to adjust things in sequencer tabs. Also, sometimes I fins that somehow my inputs are set up wrongly and I have accidentally set a file as an input when not using files, or set a channel as an input that is not receiving audio. There are tons of pitfalls in this in the first few days but it is worth the effort, I'm really glad I struggled through

This is definetely worth the struggle, though I too at first must confess I thought, “what the hell I’ve I just bought?”. Again though and in fairness this is probably true of most apps I own. I wish also that the windows sometimes appear as separate windows (though again in truth an impossible task, bearing in mind how many windows this monster has), though it would be great if the matrix window could stay open whilst fiddling with the sliders. That way their would be more of a “Ah now I see what that does” moments. For me I also wish the windows had maybe a different coloured header both in the main window and when open, thus there would be more clarity. A red tiltled window could represent “Inputs” and so on. The otherthing I also discovered is it is beginning to force me into a new way of working. I intiallly find that I open an app and within moments I want to capture the results. I tend to sample with Enso, firing an instrument with midi from either Moziac or Riffer and then develop a bank of samples. I adopted the same strategy at first, but then but then found that “Beatcutter” rewards a live playing approach, difficult as that is with the state of my fingers, this can produce some incredible results, though it is a little like being delayed in time, those results are delayed, in a wait of some seconds sometimes even minutes. Could I play it live at the next Open Electro Night? Do I have the balls? Only time will tell. Though as we slow pull out of these crazy times this is the app I will use for my performance of “Out of the blue” a performance with actors, dancers and a soundcape, which investigates mental health, technologys’s impact, and how to awake. Thanks for listening to my ramblings.

0tolerance4silence

I can’t even remember when was the last time I didn’t like a glitch maker...

Gavinski

@drcongo said:
I just bought it, though I’m fairly convinced I won’t have the staying power. During purchase the App Store shows the developer name iMusicAlbum in all caps, which my brain can only see as I MUSICAL BUM

😂😂😂😂😂

ghost_forests

@telecharge said:

I think for this app to be successful, it needs to be shown to be musical. Otherwise, it will have limited appeal.

“musical” is a highly subjective term 😜

Gavinski

Ok guys, if u want to hear me doing a bit of comical singing / rapping, this is probably your only ever chance 😂😂😂:

https://twitter.com/gavinski_s/status/1378655048620646401

Listening now to your track @gusgranite, very very nice! Once for the doubters

Gavinski

@Toastedghost said:

@Gavinski said:

@Toastedghost said:

@ALB said:
It seems to be a bit hard on cpu for me. Sort of cool all the same. I wish that the matrix worked somehow a bit more like the Apematrix grid, rather than just being a visual representation.

For me I wish you could push on the nodes outside the matrix to physically turn them on and off.
I sometimes find that the internal triggers do not fire as I would have liked.

The main thing I found is that if u aren't getting enough sounds try raising the values on the slider knobs in the 8 trigger windows. Also pay attention to the speed the sequencer circles are moving on the matrix. If top slow you may need to adjust things in sequencer tabs. Also, sometimes I fins that somehow my inputs are set up wrongly and I have accidentally set a file as an input when not using files, or set a channel as an input that is not receiving audio. There are tons of pitfalls in this in the first few days but it is worth the effort, I'm really glad I struggled through

This is definetely worth the struggle, though I too at first must confess I thought, “what the hell I’ve I just bought?”. Again though and in fairness this is probably true of most apps I own. I wish also that the windows sometimes appear as separate windows (though again in truth an impossible task, bearing in mind how many windows this monster has), though it would be great if the matrix window could stay open whilst fiddling with the sliders. That way their would be more of a “Ah now I see what that does” moments. For me I also wish the windows had maybe a different coloured header both in the main window and when open, thus there would be more clarity. A red tiltled window could represent “Inputs” and so on. The otherthing I also discovered is it is beginning to force me into a new way of working. I intiallly find that I open an app and within moments I want to capture the results. I tend to sample with Enso, firing an instrument with midi from either Moziac or Riffer and then develop a bank of samples. I adopted the same strategy at first, but then but then found that “Beatcutter” rewards a live playing approach, difficult as that is with the state of my fingers, this can produce some incredible results, though it is a little like being delayed in time, those results are delayed, in a wait of some seconds sometimes even minutes. Could I play it live at the next Open Electro Night? Do I have the balls? Only time will tell. Though as we slow pull out of these crazy times this is the app I will use for my performance of “Out of the blue” a performance with actors, dancers and a soundcape, which investigates mental health, technologys’s impact, and how to awake. Thanks for listening to my ramblings.

Great ramblings. I literally said to Igor an hour ago, it is such a pity you can’t see what the hell is happening with the sliders as you press the template numbers. I stick by my assertion - great app, bad interface. But wow, it is hella fun, I think he made a winner here after all.

Prog1967

@Gavinski said:
Oops:

https://twitter.com/gavinski_s/status/1378535029010092032

@Gavinski this sounds great. What did you do here?

Gavinski

@Prog1967 said:

@Gavinski said:
Oops:

https://twitter.com/gavinski_s/status/1378535029010092032

@Gavinski this sounds great. What did you do here?

Frankly, I'm not sure! 😂

drcongo

I can’t get any sound to come out of it. Dropped it in an FX slot on NS2 and hit random many times.

Gavinski

@drcongo said:
I can’t get any sound to come out of it. Dropped it in an FX slot on NS2 and hit random many times.

You probably don’t have the inputs set up right. Set all the input buses to Ch 1, then go to template, change the 1st position to ‘x’ then try pressing randomise. You will need to watch my video and/or read the manual, this app is a bit complicated to even get the basics, but once u have those you can randomise til your heart’s content

Gavinski

Below are the names of the lucky winners of the Beatcutter (iMusicAlbum / Igor Vasiliev) Giveaway. I have grown to LOVE this app over the last few days, despite the interface. If you are having problems, stick with it, read the manual, rewatch my vid. I have lots of Beatcutter tips and tweets on my Twitter. Beatcutter’s not for the lazy or impatient, as none of Igor’s apps are.

There is a great helpful thread on the audiobus forum here if you have questions:
https://forum.audiob.us/discussion/44507/beatcutter-crowdsourcing-the-learning-curve#latest

Here is a link to a funny little Twitter clip of me singing/rapping/talking through Beatcutter. I dunno about you, but i lolled 😀:

https://twitter.com/gavinski_s/status/1378655048620646401

Ok, the winners are:
EZmpc - Synthscaper
andrwmh - Beatcutter
Skip Hunt - Beatcutter
Pixelhog! - Beatcutter
Jonathan Aran - Synthscaper

Thanks for your support folks, big thanks especially to those who were kind enough to donate through PayPal recently, big up! If you are watching this after the event, make sure you subscribe so you don't miss out on future vids. I usually have free copies of apps to give away.🤞

Please remember folks to help out the channel by not watching these behind an ad blocker, as I am sure you do not want to exploit your dear old Gavinski any more than YouTube is already exploiting him 😉. Thank you for your support.

Don’t forget you can follow me on Twitter at @gavinski_s. If you want to help me and Igor out, a retweet or like of this would be great:

https://twitter.com/gavinski_s/status/1377940501685395457

This tweet is an ambient example: you don't need to add beats or use beats in your processing, you can go for pure soundscaping:

https://twitter.com/gavinski_s/status/1378019038874501122

Also, if you enjoy the channel and would like to show your appreciation, my PalPal is
https://paypal.me/GavinskisTutorials I am very happy when people support me in this way, and will certainly take the time to email you to thank you personally if you do 🙏. Quite frankly, the very generous donations of some viewers are the only things that are enabling me to continue spending so much time researching new apps and making my walkthroughs, so huge thanks to you all - you know why you are and you are hugely appreciated.

Oh and here is a bonus for y'all: a very clear description of how the app works in one paragraph, written by Celtic Elk at the Audiobus Forum. (Be there or Be Square btw, it is a great resource!)

'The realization that made this app start to make sense for me is this: each cell is a dynamically-triggered sampler. Each of the buses represent a stage in the sample/playback process: the input bus defines the sound source for a cell, the trigger bus defines the conditions for recording (trigger conditions, sample length), the control bus defines important aspects of playback (pitch, direction, how many times a cell plays before it empties, whether its first playback is delayed for one or more cycles), the sequence bus triggers playback (and can contribute to sampling as well, depending on how you set the trigger bus), and the output bus (which has two pages, one for effects/filtering and one for level/pan/EQ) handles downstream processing when a cell is played. Each trigger bus records no more than one cell when it fires; each sequence bus plays no more than one cell when it fires.

It gets complicated from there, obviously, but that’s the basic setup.'

👍👍👍

Gavinski

@skiphunt @Pxlhg i will DM u two ur codes

Gavinski

Well, tried to DM skiphunt, turns out the bugger is ignoring me so I can’t send him messages 😂, how do u like that 😛😁

reasOne

@Gavinski said:
Well, tried to DM skiphunt, turns out the bugger is ignoring me so I can’t send him messages 😂, how do u like that 😛😁

Haha uh oh!!