23 posts / 0 new
Last post
Rej - Dev
Rej - Dev's picture
Offline
Joined: 12/18/2011 - 15:52
Caustic 2.1 beta 5

Getting close to a release candidate with this one, seems like most of the new issues are minor so that's a good sign. A few things of note for this build:

- I managed to trap the rare "new/load song = crash" bug I think a few of you were having, so I put in a fix for that. Hopefully that's the last we'll see of that nasty one.

- Please delete your config file because I've changed the default MIDI option to "disabled". I'm terrified of the potential of hardware issues related to MIDI and USB so I'm including instructions that the feature is experimental for now. If you do have MIDI hardware, please check that everything still works ok after you've enabled it again.

- This build uses a new way of handling song looping so please give that a good test, I think I've tested all the edge cases but it's possible I've forgotten some.

---------------------------------------------------

If you're just starting this beta program, have a good read of the Beta 1 thread for instructions, new features, and known issues before jumping in.

Beta expired, see Release candidate thread

The following issues should be fixed, please report back if they aren't:

- Coming back to the app with MIDI controller connected may cause reboots on certain devices. (workaround: MIDI should now be disabled by default)
- Longer patterns (>1 measure) on Bassline and beatbox don't appear the right size when placed in the sequencer.
- Play issues with notes at the beginning and end of patterns (see paulovski's post in beta 4 thread)
- Dragging pattern blocks in the sequencer doesn't auto-scroll correctly.
- Velocity slider in sequencer for bassline goes too far down.
- No accent or glide markings for bassline in sequencer pianoroll.
- Export takes forever and is corrupt if latency is set to "very low".
- Trimming measures gave incorrect results if the event were longer than 1 measure and being cut in half.
- Impossible to stretch a note that's right next to another in pattern editor.
- New notes in the sequencer piano roll are not sounded.
- Automation of new exponential envelope controls are incorrect (snap to different values)

-----------------------------------------

Caustic v2.1.0 Beta 5 - Known issues:

- The app might crash the first time you run it after it's finished extracting demo content. (i'll have to wait until next week to get my hands of some more test devices)

wardini
wardini's picture
Offline
Joined: 07/13/2012 - 17:13
Thanks Rej;

Thanks Rej;

No crash on first time start.  Have the day to run some tests.

Jason
Jason's picture
Offline
Joined: 03/23/2012 - 21:32
I'm on it....  

Ok, I did a very tiny song loop thingy, and let it ride for a few minutes, and I did notice occasional pops or inturruptions in the  audio...  I had the latency set to very low, so I kicked it up to medium; and it still does it.   Very simply loop no automation (oh that hurts)

-- Song File Test Here -- see if it happens on your gear. 

 

paulovski
paulovski's picture
Offline
Joined: 09/19/2012 - 06:13
Jason, I can only play your

Jason, I can only play your song with High latency without getting crackles.

I've still got boojeroo's export bug. 4.14 song exported fine with low and medium. A bit of extra as usual (in this case, silence). High cut out at 4.02 with an extra bit of silence. Very low just stopped at 2.08.

No MIDI system here to try. Everything else on the fix list working here.But,

Last night on beta 4, I was messing with automation on a one bar loop and I lost the Master output. Level indicators were showing up in the mixer for the tracks, but no master and no sound. I saved the track and reloaded. It was fine.

Today on beta 5, I lost the Master output while messing around with loop points. It saved fine.

 

Rej - Dev
Rej - Dev's picture
Offline
Joined: 12/18/2011 - 15:52
Hmm, what machine were you

Hmm, what machine were you automating, the bassline?

mekanism
mekanism's picture
Offline
Joined: 06/16/2012 - 19:34
Rej, the usb issue is gone!

Rej, the usb issue is gone! Must have been the midi default you changed. Thanks!

wardini
wardini's picture
Offline
Joined: 07/13/2012 - 17:13
This was my Caustic 2.1 beta

This was my Caustic 2.1 beta companion for the last week:

https://dl.dropbox.com/u/80156103/BOOTZADELLIC.caustic

I was trying to throw a bunch of different things at it  Caustic was really performing stellar. but my nook started stuttering  a little at the end when I added some simple automation..... even with high latency.. it's only a single core 800Mhz with 512 Ram so I thought it did pretty well considering.  really no issues at all with beta five. the export was resonable.  i did get a couple of save errors near the end when it stuttered ( i always chose 'wait' and it  never crashed) ...wonder if that is why the file is so large...or if it's all the 'Curly Q's' stuck in there. ;- } jblann1's test 5 loop runs fine here at very low latency .

 

paulovski
paulovski's picture
Offline
Joined: 09/19/2012 - 06:13
Nope. Not that. I was non

Nope. Not that. I was non real time automating a saw ramp with the subsynth cent control zooming in on 64ths. Because now I can. Thank you very much.( and there are 64 of them here, patterns and piano roll) It was a one measure loop and it cycled round about 4 times before the audio disappeared. Same symptom, 2 different causes, if that's what they were. I can't reproduce this at all. I'll let you know what I was doing if it happens again.

skarabee
skarabee's picture
Offline
Joined: 05/15/2012 - 07:52
Midi keyboards and

Midi keyboards and controllers working here. At least with the windows version.

Will test on the tablet.

bojeroo
bojeroo's picture
Offline
Joined: 06/08/2012 - 17:25
Yep, I'm seeing the export

Yep, I'm seeing the export bug still. Do you want the caustic file to test Rej?

Jason
Jason's picture
Offline
Joined: 03/23/2012 - 21:32
Ok, I've been tinkering

Ok, I've been tinkering around in beta5, nothing really fancy, but more function testing than anything (ParaEQ is a very nice addition to the IFX rack Rej)

At first I thought I found a problem, with audio squashing down from BassLine via the Master Comp I had set up, but after a bit of tweaking of Main FX bus feeds, the issue went away..... the audio mixing seems a little different than what my mental muscle memory was used to in 2.0.2, but I can get used to this.  I had connected and disconnected USB several times to transfer items back and forth from the pc (usually would crash Caustic before) and while a temporary hangup during data transfer, Caustic remained stable the entire time making this "song" 

Here's the source, if anyone wants to play with it or whatever. 

I did alot of pattern and sequencer editing while the song was playing and looping, strangley no audio pops or dropouts on the tablet.... no hiccups whatsoever.

-- TestSong Here --  again nothing fancy, just function testing...

I'm quite pleased with the results and major improvements and flexibility in this build, and am excited to push forward with the Builderz Project in 2.1

BTW, I've made a nice handful of new BassLine presets... it really rocks now.... presets should be available soon I'm sure

Rej - Dev
Rej - Dev's picture
Offline
Joined: 12/18/2011 - 15:52
As far as I remeber, the

As far as I remeber, the mixing code was not touched at all in this build.... nor was the compressor effect. The bassline was changed obviously, so maybe the difference is coming from there, but if you're not using effects of the LFO, it should sound pretty much the same as v2.0

And yes, I'll include your Bassline presets in the release.

This is also a call to anyone else who's made bassline presets they like to share with the world, I'd love a few more to include in the official release.

skarabee
skarabee's picture
Offline
Joined: 05/15/2012 - 07:52
midi working on Acer 500. I

midi working on Acer 500smiley. I tried to plug/unplug on the fly, while Caustic is running, no crash. When replugged, Caustic just ask if I want to use external midi, and let's roll. 

Cubase (and others daws) can't do it! If you remove or add a midi device, you have to restart Cubase...

Hats off to Rej!

Jason
Jason's picture
Offline
Joined: 03/23/2012 - 21:32
Regarding Rej's comment on my

Regarding Rej's comment on my little mixing oddity, it may have been the BassLine pushing something hard in there, heavy resonance or something... not a bug really, but after i tweaked a few things, it ran fine.

It's all good....

carl-alex
Offline
Joined: 11/08/2012 - 05:30
Further results from testing

Further results from testing at the last weekend...

Thanks to the community and the author of the application for your answers in the "beta 4" thread. Although, now I feel flamed a little bit, I want to apologize for my harsh postings. I work  for business conceptions of software products, and there one typically writes brief specifications as "the system must do...". Thus, apart from the foreign language, my suggestions may sound very crude. However, I do not mean anything personal. Rej, you do a very good job and already managed to bring the workflow of the note editors to a high level. I bought the app before some months and detected some shortcommings when trying to create some own music. And I must say that Rej added usable tools to overcome these problems. But I want to be a bit too perfect and am always thinking about improvements that fit well into the existing concepts. It is not my task to decide, what to do or when to do or how to do. If the "noise problem" (someone else also reported such things) in Windows gets away and the real bugs are solved, I will finally upgrade to the 2.1 release and also buy the new android version from google play. I did not know about the product / release strategie and the exact sense of the beta testing, so please forgive me for inadequate remarks. Keep things simple!

Today I will download the new beta, but I have not that much time to test this week. Yesterday, I compiled a new list of bugs and improvements. Probably this will be my last one - then I have "vomitted" everything out. (I have some additional things as real future requests and will place them into the according folder.)

 

Export of song to WAV:

- When a song is fully exported and a loop region was set before, then there arise problems after the loop region. Some tracks or some notes in the tracks are not played. When the loop region is reset and the export is repeated, the WAV file is fine. (In this context, I remember some problems with MIDI export in Caustic 2.0.2 (Android) when not all tracks were filled with sound machines. The application crashed and the written file was incomplete. I do not know, if this bug has been fixed with the new release.)

 

Function “Sound new notes”:

- This works fine (in pattern editors), but it behaves a little bit curious in the beatbox. The channel sample is triggered when changing the channel but at the first move also the old channel is played. I thought the preview velocity was 50% as in the beatbox mixer but the drums hit very loud when triggers are added or moved. (As mentioned above I recommend a preset velocity of 50% as in Caustic 2.0.2 for the beatbox tracks.)

- In the piano roll I did not manage to get a preview sound. (Should be corrected with beta 5, I will retest)

 

New bassline machine:

- The green level meter seams to get frozen after a note has been played.

- I did not recognize an effect of the new PWM mode in presence of a saw-tooth wave. (Perhaps this is physically correct.)

- The “Mute” and “Solo” buttons appear a bit bulky and different as those of the other machines. I think this is in sake of a better button layout, so maybe the best would be to just shorten the text to “M” and “S” and leave both buttons at its positions.

 

Piano roll sequencer:

- When loading a Caustic file, the keysize is set to “big”. At startup of the application, the saved configuration is read.

 

Pattern editor, grid resolution property:

- In my opinion, this is not really needed. A pattern obviously can contain any note within a 1/192 grid independent of what is stated in the pattern property. When a caustic 2.0.2 song is imported into 2.1 and saved again, the new file cannot be loaded into 2.0.2, thus the grid reduction does not serve for compatibility reasons.

 

Pattern editor, hierarchical pattern properties:

- Yesterday, for the first time, I saw that there are tabs, e.g. “SUBSYNTH”, “BANK: A”, “PATTERN: A1”, and that you can long-press on a bank button to get to the second tab. I think this aims at defining default properties at different levels. But up to now, I do not see any logic in the implementation. (Maybe this is a known todo in the actual release.)

 

Idea: Unified selection approach

While testing, I got a new idea, how the selection in all editors could be unified:

- At the place of the “All” icon in the pattern editor, the “Multi” icon of the sequencer editors could appear and use the same implementation.

- Whenever no note trigger is selected, the “None” icon could be automatically replaced by the “All” icon. Even in the sequencer this could be applicable when a loop region has been set up. (However the latter feature is not necessary due to the new time tool.)

 

Idea: Unified zoom / grid approach:

- The touch/click “note length” indicator (with circulation through the grid levels) in the pattern editor and the “zoom” keys in the piano roll sequencer (together with the new short display of the note length) could be replaced by a (space saving) combined GUI element similar to the “polyphony” switch: using “plus” and “minus” buttons the user could jump through the grid levels in both directions, a display field would show the actual grid resolution.

 

paulovski
paulovski's picture
Offline
Joined: 09/19/2012 - 06:13
Pattern Grid Resulution

I guess it depends on what kind of music you make a bit, but I reckon, most of the time, people will be using 16ths and above and only needing access to 64ths and that, as and when. Being able to limit the grid resolution means that you can flick through the more likely note lengths quicker with the grid button.

I had a loop set up in my export experiment. No missing notes here.

Caustic to home and back again. Every now and again, Caustic comes back with a different (recently loaded) song.

subshift
subshift's picture
Offline
Joined: 09/02/2012 - 14:41
Hi,

Hi,
It gets greater and greater. I'm also very happy that the new/load crash bug is fixed, because I had it on several occasions.

However, one new "issue" on my device (transformer prime) : the orange vertical line that follow the song playing is late in all pattern editors. It is *not* late in the piano roll or the sequencer. (It seems to be 1/4 bar late w.r.t. the sound being played.)

Cheers!

mekanism
mekanism's picture
Offline
Joined: 06/16/2012 - 19:34
I'm currently having an issue

I'm currently having an issue where no matter what machine and measures, hitting play starts about 3/4 of the way through the length of the measures even after hitting stop. Always starts from about 1/4 from the end.

Rej - Dev
Rej - Dev's picture
Offline
Joined: 12/18/2011 - 15:52
To be clear mekanism, do you

To be clear mekanism, do you mean the orange bar is 3/4 of the way through, or playback of notes starts at 3/4 ?

I did find a bug with the orange bar (it's meant to be offset by latency , but this calculation was wrong)

 

Bacon
Offline
Joined: 04/25/2012 - 10:12
Copy/paste in the pattern

Copy/paste in the pattern editors doesn't seem to work anymore. I created a four-bar pattern in PCM Synth and added some notes to the first bar. I then chose SEL > ALL, then EDIT > COPY > PASTE. When I tried to drag the copied notes to their intended destination all notes except the one I was holding got deselcted so I could only drag one note at a time. I tried this repeatedly and had the same result every time.

Copy/paste used to work in one of the other betas. I don't remember which one I tried it in before, though.

Rej - Dev
Rej - Dev's picture
Offline
Joined: 12/18/2011 - 15:52
You're right. Good catch, I

You're right. Good catch, I'll get right on it.

I think I broke it when I fixed the "can't stretch a note that's next to another" bug, I'll try to do it right this time...

Rej - Dev
Rej - Dev's picture
Offline
Joined: 12/18/2011 - 15:52
Thanks for these. Some have

Thanks for these. Some have already been fixed, some are new and some will probably not get fixed for this .0 release.

I guess one of the problems with beta testing new features without a manual that defines how they're supposed to work is that things will get missed. Case in point: the hierarchical pattern properties. I never said how they were supposed to work and actually, most of it wasn't even hooked up, I completely forgot!  Yes, they're meant to work as a quick way to set a property on a whole bank or even the machine. I have now added the support code for this so thanks for spotting it.

Rej - Dev
Rej - Dev's picture
Offline
Joined: 12/18/2011 - 15:52
Closing this one as there's a

Closing this one as there's a new version out .

Comment clarifying bug in here can be made there.

Topic locked