pipstyles
Comments
-
@dendy great info. I’ll likely chop guides into sections. @Stiksi I just tried doing a 129 bar trim, with automation ending at bar 129, so the last audio event starting at the 100 point rather than ending there. Idea being, like you suggested, 100 maps to 127 out of 128. This time the track gets ahead of the click though.…
-
@Stiksi Yes, I figured an off-by-one would be a good avenue to explore, so I tried parts trimmed to 127 and 129 in length too. They had the same issue of drifting behind the click. The 129 bar version was taking longer to be noticeable, hence ending up settling on 129bars + 1beat.
-
Me too. I also tend to treat the automations as their own parts, on separate tracks, so they can be muted, moved, repeated etc etc independently of the notes. That can make A/B comparison a lot easier too.
-
Feature: guide track It would very handy to have a very simple audio track up with the tempo track to act as a guide track. It could just have volume, pan and mute. This might also serve as useful testing for Matt to check on the core functionality of the full IAP audio tracks - playback stability, sync, mix etc.
-
That has worked, thanks! It does seem broken on filters 1 or 2 though. I tried @dendy suggestion about the xy pads (correct, the default was that) but remove those controls didn’t alter the behaviour or WS mode on filter 1 and 2. So, WS filter on the global filter works fine. Edit: yes! Default filter envelope was causing…
-
Are you planning to make as both input (the master out?) and output (a track input I guess?)
-
I’m hoping for a free "guide track" feature at least, grouped with the tempo and timesig tracks. The sample chopping is real chore when working with a demo to click someone has sent me.