#278

No worries on that front, I don’t intend to use w/synth or w/delay at all since I bought it for the tape purposes as it was advertised to be. Thanks for the clarification. Thought I was going crazy!

:slight_smile:

#279

I upgraded this morning, and spent some time playing around with w/tape. Seems much more stable :slight_smile: It would be nice to have an ii command for tape clear if that’s possible. It seems like the only missing ii command for w/tape IMHO.

Thanks @Galapagoose for keeping going at this.

#280

I’m pretty OK with deleting 3 hours of audio requiring a manual step :slight_smile:

1 Like
#281

It already exists, but you need to update to the crow 2.1RC in the top post.

This is why the command is ii.wtape.WARNING_clear_tape().

7 Likes
#282

Ah super stuff! And a nice clear command name too :slight_smile:

1 Like
#283

Makes me wish there was a dual channel W/2 :wink: pair of these is high up on my wishlist

4 Likes
#284

A la Disting, the W/EX?

1 Like
#285

This!
A with with with.
W/W/W/

Edit: SLASHES – WHIMSICAL RAPS

3 Likes
#286

I didn’t know this was a thing! Thank you!!

1 Like
#287

Does anyone have the new crow rc? The link up top doesn’t seem to be working… I saw @Justmat doing some lovely things with w/2 and crow over on instagram and it got me jonesing to try it out…

3 Likes
#288

The link seems to be working now!

2 Likes
#289

Bizarre, I’m still getting the GitHub 404 octocat at the crow link… I’ve cleared caches, history, opened fresh browsers… I may just have to wait for it to sort itself out.

EDIT: Sign in to GitHub for access

#290

I also get the 404 page for Crow 2.1RC. Speaking from previous experience with GitHub, that usually means I don’t have permission, so maybe the RC isn’t actually set to public?

1 Like
#291

It looks like it’s downloadable if you’re logged into github, but 404s if you are not. I also noticed it’s not listed under Releases for the repo.

1 Like
#292

Wow, you’re right! Since this isn’t my work computer, I wasn’t logged in. But it works when I am. :thinking:

#293

Ah that makes sense - it’s a link to an automated build which isn’t really meant as a ‘release’, just a quick way to share in-progress updates without requiring me to go through the whole release process for each beta. I’ll wrap up the crow release today so it won’t be an issue, but have noted that those files aren’t publicly accessible.

3 Likes
#294

I’m getting some weird behavior in W/Tape when trying to set loop_start and loop_end - it seems to only ever make the loop smaller, and it’s never what I tried to set it to. It doesn’t seem to matter whether or not it’s playing. Setting timestamp directly seems to work quite well, though!

1 Like
#295

@Galapagoose, Is this correct/working as intended?

ii.wtape.get('loop_start') returns 0.001220778
while sitting on the loop_start point and issuing ii.wtape.get('timestamp') returns 23.71721

getting loop_end returns a seconds value as expected.

@license i think loop_start and loop_end are called to set the loop points to the current position/timestamp. i don’t think you can pass a position as an argument.

1 Like
#296

@license justmat is correct. loop_start and loop_end set the loop points to the current playhead. if you want to set them to a timestamp you can just chain the two commands (though perhaps a delay will be required? let me know):

-- make a 4 second loop starting at 23.4 seconds
ii.wtape.timestamp( 23.4 )
ii.wtape.loop_start()
ii.wtape.seek( 4.0 )
ii.wtape.loop_end()

@Justmat thanks for the report. i will take a look at what could be causing this. It’s quite possible start & end are flipped.

8 Likes
#297

this is soooo much easier to use than the cue system, imo. just keep up with your timestamps and recalling loops is easy peasy!

2 Likes