Bub

FastBikerBoy

You just didn't use the functions that were broken, such as Audio Snap, Snap To Grid....

See getting facts wrong always weakens an argument. Snap wasn't broken in X1, snap snapped i.e. it worked.

The bug that you are referring to was caused by the PRV resetting the snap to its value when it was opened. If you always opened a PRV and set the snap in that before starting work you would never ever even notice the bug. I know because that's exactly how I worked round it.

Snap To has been broken and fixed at least twice that I'm aware of. I rarely use PRV except at the very end just before I mix, and I can tell you the Snap To settings were altering while just in Track View. But, I never gave specifics about the Snap To ... I just said it was broken, which it was ... you added in all the extra intent.

We could go on like this forever but if it's been broken twice and there was a different bug to the one I described I can safely go in to denial mode because I never saw it. The bug I described above is the only one I ever saw in X1 relating to snap and that was a grid changing bug, not a not-snapping one.

I reported the bug and then posted that solution many, many times on here as you well know. Others chose to post about it in every thread and call those of us that could work round it liars........ oh and untalented.....

Hey, at least you've never been called a ****, moron, or the latest one, just a few minutes ago ... an illiterate. LOL!

Give it time.....

I certainly don't 'deny' bugs - so far I've reported 22 of them - but there's a big difference between 'bug' and 'broken' - I guess that boils down to your outlook on life. I'm definitely a very positive, glass is half full kinda guy. Probably why I'm so happy with X1..........

I couldn't get Audio Snap to work when X1 was released, could you? I couldn't get the snare sample that I use in 99% of my projects to work after they released the X1a patch, if that isn't broken I'm not sure what is. And honestly, there is no difference between a bug and something being broken. If I can't reliably use a function of the software, it's broke.

I don't know because I never tried but then I couldn't get Audiosnap to work in earlier versions either, although that may well have been operator error. If bug=broke I'd like to declare the step sequencer, PRV, snap, and drum maps all 'broken' in X1c. Of course they aren't but they do have bugs that have to be worked round. The only function in X1 I couldn't use because of a bug was the 'Print' function from the staff view.

Over exaggeration of bugs is just as damaging as denying them.......

There has been no over exaggeration of bugs on my part. I've just pointed out that there were some things that were and still are broken (or buggy if it makes you feel better) that everyone has on their system. Just because you don't use that function doesn't mean you get to claim it doesn't exist.

Anyway, this illiterate **** is going to go eat some supper you untalented hack. LOL!!!!!!

I'll be back later. :)

Thanks for the fun. :)

Bub.

I'm not claiming nothing exists but for example, if I come on here and declare that 'snap to' is now broke (because of two bugs) most people reading it are going to go try their snap, find nothing wrong with it and think I'm nuts. That's what I mean by exaggeration weakening an argument/claim. Nothing to do with the problem not existing just accurately refelecting what is wrong. It's more likely to get fixed that way.


Anyway good luck in your new job, and keep on visiting, who else will I spar posts with?

I'm glad I'm in a better mood now.

Am I still a pest?

If that's the case please feel free to use the Pest control spray in my avatar.

musicman100


This thread and goodby Sonar ... (other than the refreshing thread derails in here)

I think I saw that horse blink....... maybe some life there yet......

I've always been nieve... and have been made a fool of on some forums because of it. I don't let it change me, I thought and still think that we are mostly friends on this forum. People may get irritated and sometimes lose patience and that is fine, it is just life.
I have not seen the sort of stuff here I have seen of some guitar forums of yesteryear. The flame wars and really nasty personal attacks going as far as contacting someone's employer trying to get them fired. That sort of stuff happened in the late 90s and early 2ks on the Harmony Central Guitar Forums and some of the the spinoff forums. The best people, IMO, from the original HCGF ended up at what is now called the guitardiner.com but some of those same old people who caused so much trouble back then still constantly try to get in through different IPs etc. The mod there says it is a daily job keeping them out... SO, this forum really is a decent group of people here who may disagree on some things and get frustrated but it really stays civil. I'm sure this forum has had it's moments but even when a non-user complains about X1 they don't get the treatment I have seen people get for much less on other boards.
Ya'll even put up with me... laff and I learn a ot reading the threads here. If I have a question, I search and usually come up with an answer.
This thread could have turned really nasty, really fast but it didn't. Kudos.

Julien

 

 

^ Virtual Memory has nothing to do with System Memory.

 
^ Video Memory has nothing to do with System Memory.

^ Your CPU running low on resources has nothing to do with your System Memory.

If there's anything else I can straighten you out on Freddie just let me know.

Bub.

You might want to try reading them as well...

1) To the best of my knowledge, this speaks about reserved memory for the exclusive use of single application. Most programs are capable of sharing memory.

2) Speaks about memory... but not just RAM... and of course all photo shop users know that Photoshop uses 4 scratch disks to augment random access memory. You can use your 32GB of RAM and then you can have another terabyte of memory on "scratch disks".

3) Speaks about a Pro Tools feature where you may protect your project from being corrupted by a confused CPU by governing the percentage of CPU power that may be utilized by plug in running within that application. That dialog neither mentions "resources" or "memory".



all the best,
mike

My laptop's video memory lives virtually inside my system RAM.

And it can party at 1680 x 945 while pumping out mp4 thru hdmi at 1920 x 1080.

I think I have 4 GB total in this lap top.

Maybe I should go look?

:-)

mike_mccue


You might want to try reading them as well...

1) To the best of my knowledge, this speaks about reserved memory for the exclusive use of single application. Most programs are capable of sharing memory.

2) Speaks about memory... but not just RAM... and of course all photo shop users know that Photoshop uses 4 scratch disks to augment random access memory. You can use your 32GB of RAM and then you can have another terabyte of memory on "scratch disks".

3) Speaks about a Pro Tools feature where you may protect your project from being corrupted by a confused CPU by governing the percentage of CPU power that may be utilized by plug in running within that application. That dialog neither mentions "resources" or "memory".



all the best,
mike

1 That may have been true under XP but I don't think its true of Vista and Win 7. No more sharing of memory.
2 Not if there is not enough physical RAM to support that.
3 So you are saying that memory has nothing to do with the third issue?  Sorry I don't think you have a clue how PCs work.

If what you are saying is so why are those dialogs there.  All of them are related to memory issues. You can spin it any way you want but its all about memory.

John T


The ProTools one isn't memory related. It is as Mike describes it.

Yes it is if its a resource. If it is asking for the removal of a plugin for the system to work it has a lot to do with memory.  All processes including those imposed by a program in this case PT on how much the system can be allocated to a process goes to memory. Even that dialog box is in memory.

Freddie H


     HERE is a picture in LOGIC x32bit LOW on MEMORY! Today LOGIC are also in X64..  

and that's the proper application behavior, if something goes wrong and app cannot continue prompt user 
to save his data and then gracefully crash .  Logic programmer knows the programming standards.
Sonar, do you?
 

3 So you are saying that memory has nothing to do with the third issue? Sorry I don't think you have a clue how PCs work.

These are the kinds of statements we live to regret, especially when someone else has quoted it so you can't click "Edit Message" and take it back.

As for who has a clue about how PCs work, I think it's safe to say that by this stage in their evolution none of us do. I know I don't, and I've been a computer nerd since before PCs even existed.

Really, it's not, he's right on this. You can basically throttle how many CPU cycles you're willing to give to plug ins. You can set this low enough to throw this message with tons of memory space available. Really, look again, it doesn't even include the word "resources". It's quite a useful feature, as it happens. I wouldn't mind having something like that in Sonar.

I don't think you get what I am saying. Any action done on a computer requires memory to have it done. For example the idea of core parking requires memory to work. It may not be in that case in RAM but memory is used in the ROM.

Dave I stand by what I said. Everything done with a PC requires memory to do.

Again that is not the issue I was countering. I was saying it requires memory. And it does, Whether it requires a lot of memory or not it still requires memory. It doesn't matter in this case if it is not due to a lack of RAM that was not what I was addressing. Simply that all actions need memory.

ProjectM


 The argument was that 64-bit matters. Well, at least it doesn't hurt?

yeah, size matters told me once a woman at the bar - sometimes it hurts though...

 
Well, I'm off - and thanks for the memory