SynthMaker

Massive packing bug

Archive · 2008 12 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

Nu Audio Science ·

OSM This has to be a bug Basically if you use a pack component then the first input has to have something going through it or the other three inputs do not work

Also it seems that even simple code as included in this OSM does not work when packed either

I originally posted this in the beta test forum but i have checked it in 1.09 too and it happens there too

I've stripped this out of our synth to make it easier to see whats goin OSM has beeen sent to Malc too

Hopefully this can get sorted quickly because packing is a very useful tool while optomising

NAS

MyCo ·

I don't get it... where is the problem? Your schematic is so big, that I don't know what you mean.

That's what you described, but it works here:

Nu Audio Science ·

Oh well If you had looked inside my OSM you would find that that isnt happening at all I guess i will track down where the issue is then

But then again i am not packing float data I am packing MONO data but that shouldnt make a difference

NAS

MyCo ·

well... as I said, I don't know where your problem is, because: 1. I don't know what you expect, that schematic should do 2. there are unconnected wireless inputs 3. there are no packs with an empty first input, like you described 4. the schematic is to big to find I bug, that you never exactly described (see point 1.)

Nu Audio Science ·

Nevermind im sure ill get it sorted Pointless even posting here

NAS

MyCo ·

sorry, that you think that I want to attack you... that wasn't my intention.

I just wanted you to know, that nobody could find a bug with a huge schematic and a missleading bug description.

You said that the bug appears when you disconnect osc1 (I've seen the post before you changed it ) 😈 But I still don't get it, shure there is no sound, but that's because the switches are all off, so you have to turn on osc 2 and or 3 and everything is ok

Nu Audio Science ·

Nope it isnt but dont worry Oddson delete this thread dude please I won't be reporting anything else

Cheers

NAS

EDIT Actually i sorted it out Something i had been told to do to save a little CPU was causing the problem

Basically if you have multiple streams attached to the same input on the mono pack it will send them all as long as the first connected isnt switched off So i needed to combine all the streams into a poly to mono before feeding the input on the pack

Seemed to a few people i spoke to that the pack being mono would be permanantly active because it is mono but this is not the case

MyCo ·

No, there is realy a bug... I post the schematic... it's a weird thing

MyCo ·

OK... here it is (attachement)...

it is a stripped down version of the file above. When you load it, the osc should pass through the second switch to input 2 of the pack module... but there is no sound. If you disconnect input 1 of the pack module, you get sound

Nu Audio Science ·

Yes it seems that the pack is a hybrid of poly and mono and multiple connections have to be connected before the poly to mono

It means using extra poly to monos to pack the signals but it works

Basically the pack 4 isnt always active like other mono components It only becomes active when the first connector on any given input is active

It can be worked around and i have posted the fix below Modified your Pack issue2 OSM

Fix

NAS

infuzion ·

Nu Audio Science wrote: Yes it seems that the pack is a hybrid of poly and mono and multiple connections have to be connected before the poly to mono

It means using extra poly to monos to pack the signals but it works

Basically the pack 4 isnt always active like other mono components It only becomes active when the first connector on any given input is active

It can be worked around and i have posted the fix below Modified your Pack issue2 OSM

Fix

NAS

Nice trouble shooting NAS! & good info for the WIKI

malc ·

Indeed, this is an issue with Poly to Monos being connected to a Selector or Multiplexer which switches them in or out of the audio path. It's independent of whether you use a Pack/Unpack.

We'll need to look at the compiling process to see if there's anything we can do about this.

NAS has highlighted a good workaround (have the P2Ms to the right of the selector/multiplexer).

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.